Troubleshooting: Disaster recovery from AWS region to AWS region

The following table lists some of the issues that you may come across while recovering virtual machines from AWS region to AWS region

Table: Issues list while recovering virtual machines from AWS region to AWS region

Issue description	Solution
Post migrate replication become inactive for some of the Windows workload.	Steps to resolve this issue: Get IP address of the migrated instance from AWS Console. Log in to the instance remotely. Check if the replication state is STOPPED. Perform Resync operation on respective resiliency group. This would trigger full synchronization for the workload to maintain data integrity.
On AWS based virtualization target region; you may see inactive replication state on migration of Linux workloads For a protected workload; respective target instance copy on AWS region of Linux workload; then you may see replication state being inactive post migration with instance status check failed at 1/2 and VM screen shot displaying VM in emergency mode and system log has XFS corruption warning.	Steps to resolve this issue: Refer the Solution link to resolve the issue. Check the instance and replication state after performing above steps. Note: This is a known Issue for Linux workloads with XFS filesystem https://access.redhat.com/solutions/1194613
Editing the resiliency group, might failed after detaching volume from workload; if the removed volume is still visible from inside the operating system.	Steps to resolve this issue: For Linux based systems; even after removing the volume from the workload; it is still visible in the operating system; so it is recommended to perform explicit re-scan disk operation and make sure that the detached volume is not visible in the operating system. You can refresh the host from Resiliency Platform console and then edit the resiliency group.

Issue description

Solution

Post migrate replication become inactive for some of the Windows workload.

Steps to resolve this issue:

Get IP address of the migrated instance from AWS Console. Log in to the instance remotely.
Check if the replication state is STOPPED.
Perform Resync operation on respective resiliency group. This would trigger full synchronization for the workload to maintain data integrity.

On AWS based virtualization target region; you may see inactive replication state on migration of Linux workloads For a protected workload; respective target instance copy on AWS region of Linux workload; then you may see replication state being inactive post migration with instance status check failed at 1/2 and VM screen shot displaying VM in emergency mode and system log has XFS corruption warning.

Steps to resolve this issue:

Refer the Solution link to resolve the issue.
Check the instance and replication state after performing above steps.

Note:

This is a known Issue for Linux workloads with XFS filesystem https://access.redhat.com/solutions/1194613

Editing the resiliency group, might failed after detaching volume from workload; if the removed volume is still visible from inside the operating system.

Steps to resolve this issue:

For Linux based systems; even after removing the volume from the workload; it is still visible in the operating system; so it is recommended to perform explicit re-scan disk operation and make sure that the detached volume is not visible in the operating system. You can refresh the host from Resiliency Platform console and then edit the resiliency group.

Troubleshooting: Disaster recovery from AWS region to AWS region

Feedback

Feedback