Link Search Menu Expand Document
Elastio Docs

Enhancements, Fixes, and Known Issues 09/27/2022

The following enhancements, fixes, and known issues are found in this release, dated 09/27/2022:

New features & enhancements

  • Extended recovery testing to include a filesystem check with a CLI command. The filesystem check supports Windows file systems: NTFS, FAT and Linux file systems: EXT2-4, XFS. (for detail see this page)
  • Extended recovery testing to include an integrity check with a CLI command. The integrity check validates the recovery point internal structures. (for more detail go here)
  • Added automation that detects newly created EC2 and EBS assets and applies the appropriate backup policy. This assures that all EC2 and EBS assets are continually protected without user intervention.
  • Improved Windows block restore performance for multi-terabyte volumes.
  • Optimized background jobs requests to queue jobs.
  • Improved the deploy and update process to support the new features above securely without user intervention.
  • Improved the terraform deployment process when deploying a large number of Cloud Connectors.

Bug Fixes

  • The “Import snapshot” button on the Dashboard failed in some occasions.
  • In some occasions the EBS backup would fail with: “Task failed to start”.
  • In some cases multiple backup jobs that are run concurrently would fail with an OOM error. This was fixed.
  • The restored EBS volume would not always appear in the Assets tab. This has been fixed.
  • Removed a memory leak in Scalez engine to optimize performance under high load.
  • Block backup would sometimes fail with “Failed to initialize com security” error. This was fixed.
  • Block mount failed to start in some cases on Linux. This was fixed.
  • EC2 iscan error “Tool xfs_repair exited with non-zero code 2 and std err” would sometimes occur. This was fixed.
  • IO error would sometimes occur in file recovery point iscan job. This was fixed.
  • Foreground import snapshot was given a proper job type to be recognized by the tenant backend.
  • The failed jobs would continue being updated. This was fixed.
  • Timeout errors would occur in some cases in Scalez. This was fixed.
  • An error “No such file or directory (os error 2)” would sometimes occur in filesystem check background job. This was fixed.
  • FSecond mount of the same recovery point would fail on Windows due to mount point conflict. This was fixed.
  • iscan failed to scan a device with unmountable partition due to lack of a file system. This was fixed.

Known Issues

Dismounting from within the mount point can lead to terminal freeze on some systems or the mount point not actually getting dismounted. It is recommended to dismount from outside the mount point.