Open topic with navigation

Failing back a full-server workload

After your target has failed over and becomes your source, you can stay with that configuration long term. However, in some instances, it may be necessary or desired to go back to using the original hardware after you have failed over. Use the following process to failback to your original (or other) hardware.

1. Because your new source is on the network, you must make sure your original source is unique on the network to avoid name and IP address conflicts. You have several options available for achieving this.

• Reinstall Windows using unique server information. This may be the best option if your original source was a domain controller or running a name-specific application like Exchange.
• Run a utility like Microsoft SysPrep to modify SIDs (security identifiers), IP addresses, and the server name.
• Manually make the original source unique by modifying IP addresses and the server name. If your original source was a domain controller, you must also modify the SIDs.

2. Establish protection from your new source to your original source using the same process as when you protected your original source.
3. When the protection has been established from your new source to your original source, initiate failover.

Once failover has completed, you will be back to your original hardware.