After a full-server failover, the source is running on your original target hardware and your target no longer exists. You can reverse your full-server protection, which will apply the target identity to the original source hardware and establish protection from the source (running on the original target hardware) to the target (running on the original source hardware).
During the reverse process, you will see various states for the job Activity. During the Restoring process, the target identity is being established on the original source hardware. During the Synchronizing process , protection is being established from the source (on the original target hardware) to the target (on the original source hardware). The reverse protection is also established in the opposite direction. In the event you want to go back to your original hardware and roles (source on original source hardware and target on original target hardware), you can failover and reverse again.
Because the Windows product activation is dependent on hardware, you may need to reactivate your Windows registration after reverse. In most cases when you are using Windows 2003, you can follow the on-screen prompts to complete the reactivation. However, when you are using Windows 2008, the reactivation depends on your licensing type. If a Windows 2008 target comes online after reverse with an activation failure, use the steps appropriate for your license type.
Some applications and hardware devices create and use software devices within the operating system, but they have the characteristics of a hardware device. For example, software RAID solutions are typically implemented in the operating system, however they are still designed to emulate a single piece of storage hardware. In these cases, the device will not be reversed because it appears to be a hardware device.
You may experience issues following a reverse if an application or server uses hard-linked files. For example, Windows 2008 Server Roles added after failover will not function after reverse because the hard links related to the server role were not replicated. After updating server roles, a remirror should be performed.
If your NICs were configured for network load balancing (NLB), you will have to reconfigure that after reverse.