This section deals with certain recommendations and workarounds for resolving the errors that are encountered on a Volume Replicator and Hyper-V configuration.
Note: |
All Volume Replicator operations can be performed on a Hyper-V MSCS configuration except the volume shrink and restore operation. This is by design and expected. |
Some recommendations are as follows:
Before performing a restore operation, ensure that virtual machines are shut down and original volumes are not in use. If virtual machines are not shut down and a restore operation is performed forcefully, then I/O device error is seen on the data disk which is under replication. Due to this no I/Os occur on the volume on the guest (Hyper-V) which is under replication. Data volume state becomes unpredictable at this stage. System Eventviewer on the guest shows "Failed to flush data to the transaction log. Corruption may occur." This error gets resolved after restarting the virtual machine.
During migrate operation, the virtual machine must be shut down. If after shutting down the virtual machine and performing a migrate operation returns error, check for open handles on the volume that the virtual machines use. The vmms.exe and System processes may have open handles on volumes. Ensure to close all open handles before performing a migrate or restore operation. The volumes can also be forcefully dismounted before a migrate or restore operation to close all open handles. However, this may cause I/O errors.