How to move from classic to modernized VMware disaster recovery
This article provides information about how you can move/migrate your VMware replications from classic to modernized protection architecture. With this capability to migrate, you can successfully transfer your replicated items from a configuration server to an Azure Site Recovery replication appliance. This migration is guided by a smart replication mechanism which ensures that the complete initial replication is not performed again for non-critical replicated items, and only the differential data is transferred.
- Movement of physical servers to modernized architecture is not yet supported.
- Movement of machines replicated in a Private Endpoint enabled Recovery Services vault is not supported yet.
- Recovery plans will not be migrated and will need to be created again in the modernized Recovery Services vault.
- Prepare the required infrastructure.
- Prepare the classic Recovery Services vault.
- Prepare the modernized Recovery Services vault.
Move replicated items
Follow these steps to move the replicated items from classic architecture to modernized architecture:
Navigate to the classic Recovery Services vault and open Replicated items.
Select Upgrade to modernized VMware replication. The Pre-requisites details are displayed. Ensure you read through the prerequisites and then select Next to proceed to configure the migration settings.
Select the modernized vault you plan to move to, machines from the current vault which will be moved to the modernized vault and an appliance for each of them.
Select Next to review and make sure to check Maximum migration time.
Select I understand the risk. Proceed to move selected replicated item(s) check box.
You can monitor the migration jobs in the Site Recovery jobs section of the vault.
Allowed actions during migration and post migration
During the migration of machines
During the migration of a replicated item, continuous replication may get broken for some time. Replication continues as soon as the migration is complete. During migration, you will be allowed to do Failover operation. The last available recovery point will be present for selection and can be chosen for replication.
While the migration is in progress, you can only perform Failover operation. Once the migration is complete, data will start replicating using the modernized architecture and the new vault. All the operations will be available for you to perform from the new vault.
If the migration fails, then we will automatically rollback the changes and ensure the replication starts again from the classic vault.
Post migration operations from Classic vault
Failover and Disable replication operations will continue to be available from the classic vault even after migration is performed successfully. The classic vault will continue to exist till the retention period of last available recovery point has expired. Once the retention period is up, the vault will be cleaned up automatically. During this time, recovery points from both the vaults can be used for failover. It will depend on your failover needs to select a proper recovery point.
Till deletion of classic vault, you will continue to get charged for the retention points. Once the deletion has been done, no charges will be associated to the classic vault.
After migration, if the failover is performed using the classic vault, then the replicated items present in the modernized vault will be automatically cleaned up. Once done, all the further operations, such as commit, re-protect, failback, will only be possible via the classic vault.
Submit and view feedback for