9.4 Troubleshooting Workload Replication

Problems or Messages	Solutions
Recoverable error during replication either during Scheduling Taking Snapshot of Virtual Machine or Scheduling Reverting Virtual Machine to Snapshot before Starting.	This problem occurs when the server is under load and the process is taking longer than expected. Wait until the replication is complete.
Workload issue requires user intervention	Several types of issues might cause this message. In most cases the message should contain further specifics about the nature of the problem and the problem area (such as connectivity, credentials,. After troubleshooting, wait for a few minutes. If the message persists, contact PlateSpin Support.
All workloads go into recoverable errors because you are out of disk space.	Verify the free space. If more space is required, remove a workload.
Slow network speeds under 1 MB.	Confirm that the source machine’s network interface card’s duplex setting is on and the switch it is connected to has a matching setting. That is, if the switch is set to auto, the source can’t be set to 100 MB.
Slow network speeds over 1 MB.	Measure the latency by running the following command from the source workload: ping ip–t (replace ip with the IP address of your Forge VM). Allow it to run for 50 iterations and the average indicates the latency. Also see Optimizing Data Transfer over WAN Connections.
The file transfer cannot begin - port 3725 is already in use or 3725 unable to connect	Ensure that the port is open and listening: Run netstat -ano on the workload. Check the firewall. Retry the replication.
Controller connection not established Replication fails at the Take Control of Virtual Machine step.	This error occurs when the replication networking information is invalid. Either the DHCP server is not available or the replication virtual network is not routable to the Forge VM. Change the replication IP to a static IP or enable the DHCP server. Ensure that the virtual network selected for replication is routable to the Forge VM.
Replication job does not start (stuck at 0%)	This error can occur for different reasons and each has a unique solution: For environments using a local proxy with authentication, bypass the proxy or add proper permissions to resolve this problem. See Knowledgebase Article 7920339. If local or domain policies restrict required permissions, follow the steps outlined in Knowledgebase Article 7920862. This is a common issue when Forge VM is affiliated with a domain and the domain policies are applied with restrictions. See Group Policy and User Rights.
After a Windows Update, some files in the C:\Windows\SoftwareDistribution folder are not transferred to the target machine during incremental file-based replication.	This is a Microsoft Windows common practice: For optimization purposes, some files are marked for deletion in the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\BackupRestore\FilesNotToSnapshot registry key to prevent them from being included in VSS snapshots. See the Microsoft Developer Network article, Excluding Files from Shadow Copies for more information. Generally, these files are used to install Windows updates before they are deleted and are no longer necessary after the update. If you choose to restore these files, run Windows Update on the target machine after failover to repopulate the SoftwareDistribution folder.