How to resolve issues with dynamic disks on Windows machines after replicating on VMware
Challenge
Windows virtual machines with dynamic disks may experience issues if replicated with an external VMware agent.
Although successfully replicated, these VMs may have their RAID-massives in
Resyncing or
Failed states after having been launched in Cloud site.
Solution
Please perform these steps to put disks in the
Healthy state
again:
- if a RAID-massive is in the Failed state and some of its disks are shown as Missing or Foreign, right-click on a "foreign" disk and select "Import Foreign Disks" to run the procedure. Disks will be added and their state will change to Resyncing.
- if a RAID-massive is in the Resyncing state but is not showing any progress, right-click on one of the disks and select "Reactivate volume". This will show the sync progress. After sync has been completed, disks will be marked as Healthy.
Related Articles
Replication with VMware agent fails with the message: Backup creation failed with code 500
Challenge Replication with VMware agent fails with the following error message: "Backup creation failed with code 500, reason: Command '['umount', '/tmp/e9dc80e9-0a54-4991-9003-edeffd7e4920']' returned non-zero exit status 32" Cause In case of using ...Why Windows replication fails with Hystax VMware Replication Agent - quiesce failure
Challenge Replication fails when a Windows machine is being replicated with Hystax VMware Replication Agent with the following error message: "Backup creation failed with code 500, reason: An error occurred while quiescing the virtual machine. See ...How to check that a failed replication is caused by VSS issues
Cause A failed replication on Windows may be caused by a range of preceding internal issues affecting the source machine. A properly functioning Volume Shadow Copy Service is one of the main prerequisites for a successful replication. Solution Access ...How to replace Windows replication agent's config file in case a machine is shown offline in ACP
Challenge A machine is shown offline in ACP, although the source instance is running and has been replicated successfully before. Cause The replication agent's config file might have become corrupted during an unexpected termination of the repman ...Replication fails with an error: "Failed to create backup on device. Internal library error. Failed build snapshot sequence"
Challenge Replication fails with the following message in Acura's Events section or in the agent's logs: "Failed to create backup on device <...>: Internal library error. Failed to filter snapshots Failed to find end snapshot(<...>). Failed build ...