Problems or Messages |
Solutions |
---|---|
Active Directory Domain Services are not available after a failback (Windows) |
Active Directory Domain Services might not come up after a Failover, if chkdsk errors occur. Two avoidable causes of chkdsk errors are:
To avoid these issues, follow these best practices described in Section 16.1, Prerequisites for Workload Protection before you run the first full replication. |
During failback, the wrong NICs are mapped and failback hangs |
Use one of the following workarounds to allow the failback to complete successfully:
|
X2P Failback of Linux Workloads Causes Failure of the X-Server Graphical Interface |
The issue is caused by a reconfiguration of the failed-over VM when VMware tools are installed. To correct this, use the following command to find the files with the string BeforeVMwareToolsInstall in the filename: find / -iname '*BeforeVMwareToolsInstall' After you identify all such files, move them back to their original locations, then reboot the workload to fix the workload's X Server interface. |
During failback to physical, the target Windows machine becomes unbootable |
The networking tasks performed on the second boot for target Windows machines in failback to physical scenarios can be problematic in the following scenarios:
For failback to physical scenarios to target Windows machines, Forge provides two light networking configuration settings for the PlateSpin Forge Server that optimizes the network configuration process on the target machine during the second boot and helps avoid situations that can cause a target Windows machine to become unbootable. See Section 7.4, Configuring Behavior for Installing Network Drivers on Target Physical Machines at Failback. |