Migrating a resiliency group
Migration refers to a planned activity involving graceful shutdown of physical and virtual machines at the source data center and starting them at the target data center. In this process, replication ensures that consistent data of the assets is made available at the target data center which could be the on-premises or cloud data center. In Veritas Resiliency Platform, the migration of assets is achieved by grouping them in a resiliency group, configuring disaster recovery for the resiliency group, and thereafter performing the migrate operation on this resiliency group.
Consider the following:
If you perform the recover operation, then you must perform the Resync operation before you migrate back to the production data center.
If the Enable reverse replication option is not selected, then before migrating the virtual machines to the target data center and after migrating back to the source data center, you need to perform the Resync operation.
If the recovery data center is Azure cloud, then after you migrate from the cloud data center to the on-premises data center, you need to refresh Azure cloud to rediscover the cloud-based objects.
During the migrate operation, virtual machines on the source data center are gracefully shut down. If you manually shut down the virtual machine before performing the migrate operation, and if the shut down was not graceful, then the migrate operation may fail. This is applicable when the replication technology is Resiliency Platform Data Mover and the target data center is in cloud.
When you upgrade from an earlier version to version 3.2 or later, then after performing the migrate operation, a risk is raised. This risk is regarding the changes in NIC configuration when you migrate to any cloud data center. Suppress this risk while the resiliency group is online on cloud. Migrate back to the on-premises data center and then edit the resiliency group to fix the NIC configuration.
Ensure that the Data Mover connection status is Connected, Data State is Consistent, and Replication State is Active.
It is recommended to stop or disable NetworkManager on RHEL hosts having multiple NICs. This is required if the recovery data center is AWS, Azure or Google Cloud Platform.
For VMware virtual machines, ensure that the network mapping of all the required port groups, or subnets across the data centers is complete.
For Hyper-V virtual machines, ensure that the network mapping of all the required virtual switches across the data centers is complete.
See Creating network pairs between source and target data centers.
If the recovery data center is in AWS, Azure or Google Cloud Platform then ensure that the network mapping of all the required subnets across the data centers is complete.
If the recovery data center is in cloud, then you need to set the SAN policy to either OnlineAll or OfflineShared based on whether you have shared or non-shared disks. For more details refer to Microsoft Documentation.
If the status of the virtual machine on the recovery data center is not correctly displayed, then you need to refresh the cloud discovery or the virtualization server discovery.
For the replication technology HPE 3PAR Remote Copy, ensure that for VMware virtual machines the config.vpxd.filter.hostRescanFilter value is set to false.
To migrate a resiliency group
- Navigate
Assets (navigation pane) > Resiliency Group(s) tab
- Double-click the resiliency group to view the details page. Click Migrate.
- Select the target data center and click Next.
If the Migrate operation fails, check to know the reason and fix it. You can then launch the operation. The operation restarts the migrate workflow, it skips the steps that were successfully completed and retries those that had failed.
Do not restart the workflow service while any workflow is in running state, otherwise the operation may not work as expected.
For more information on troubleshooting specific scenarios,
More Information