x360Recover 10.16.0 is a feature release focused on a major overhaul to migrations and vault recovery. This release also includes internal functionality enhancements, and the elimination of partner-facing bugs
Summary of new features
Legacy migrations have been completely refactored to use the resumable replication mode
Vault-to-appliance recovery now offers the option to select a base image/snapshot for recovered data
- A protected system's time zone is used when virtualizing that protected system
- Snapshots ‘In-Use’ by Virtual Office, Cloud AutoVerify, or Recovery Center now are visible in the vault UI
Summary of bug fixes
- Legacy Python packages with security vulnerabilities are updated
- Issue with AutoVerify where previous shadowcopy volume might be mounted if the machine reboots while performing chkdsk has been fixed
- Web service threads on Management Portal are optimized to reduce memory consumption
- Automatic Updates will apply agent updates even if updates are blocked by in use snapshots (Agent updates do not require reboot of the device)
- Issue where ‘Completed’ replication jobs do not show 100% complete in some cases is resolved
- Fixed issue with Cloud AutoVerify continuing to perform testing after a D2C endpoint has been converted to an appliance endpoint
- Issue is resolved with some Unicode characters in protected systems stats causing Management Portal Reporting to crash
- Fixed scoring of local cache verification which had been showing failed after 72 hours if no new backup had occurred
Starting with release 10.16.0, appliance-to-appliance and vault-to-vault migrations support direct ingestion of the migrated data.
This direct ingestion of recovered data allows for resumable recovery of a protected system when migrating from a vault back to an appliance.
These enhancements mean that migration between devices over the network is now performed in a single step.
- Data is no longer staged on the target device in the aristosbay folder
- Increased storage space (to first store the migration data, and then separately ingest it) is no longer needed, since data is ingested directly to the storage pool in a single pass.
Other benefits of this enhancement include (a) interrupted transfers can be re-tried and (b) data already sent to the target device will be resumed in place on the next attempt.
For more details on performing migrations of protected systems between appliances and vaults, see Migrate from one device to another in x360Recover
- Migrating to a new appliance
- Migrating to a new Axcient vault
Migrating to a new private vault
Select a base image during vault-to-appliance recovery
During vault-to-appliance recovery, you can now specify which snapshot on the vault you wish to use as the base image. (The base image is the oldest snapshot to be retried on the appliance. )
Specifying a base image allows you to recover a smaller subset of the protected system data to the appliance than is present on the vault. (This is particularly helpful when your appliance has limited storage space. )
Like resumable migration (described above), vault-to-appliance recovery data is now directly ingested into the receiving appliance. This eliminates the need to first stage the data and means you no longer need to double the disk space available during the recovery process.
Auto Update Best Practices
We recommend that you Enable Auto Update on the Settings -> Update Manager page on each of your x360Recover devices.
We also recommend that you enable Auto-Enable Remote Assist When Upgrading so that remote access will be available to our development team should something go wrong with your upgrade.
- This will ensure that your x360Recover devices are updated with the latest software enhancements in a timely fashion, and that the Support team will have a short window of time to access and repair any troublesome devices without requiring user intervention.