You are here: Failback and restore > Failing back and restoring a full-server workload

Failing back and restoring a full-server workload

After your target has failed over and becomes your source, you can continue running from the failed over server indefinitely. However, in some instances, it may be necessary or desired to go back to using the original hardware after you have failed over. Because the source identity now exists on the network (step 1 of the diagram), failback and restoration requires manual preparation of the original or a new server (step 2 of the diagram). Once the original or new server is prepared, you can mirror and replicate data from the source to the new server (step 3 of the diagram), and when you are ready, failover will convert the original or new server to the source (step 4 of the diagram).

Full-server workload diagram

Preparation of your original source or a new server source is key to this process. The type of preparation required will depend on the role of the original source server, the applications that were used on the original server, whether the original source was a physical or virtual server, and the failure or event that occurred.

Server role—If your original source was a domain controller, a Cluster Service server, or a Certificate Service server, you will have to reinstall Windows. The utility required to reuse a server cannot be used on these types of servers. Start with 1A Preparing a new source by reinstalling Windows and then continue with the remaining instructions.
Applications—If your original source was running a name-specific application, like Exchange, you should reinstall Windows. Start with 1A Preparing a new source by reinstalling Windows and then continue with the remaining instructions.
Physical servers—If your original source was a physical server, your preparation method will depend on if you experienced a catastrophic or non-catastrophic failure.

Catastrophic failure—If your original hardware is unusable or the failure will require you to reinstall Windows, start with 1A Preparing a new source by reinstalling Windows and then continue with the remaining instructions.
Non-catastrophic failure—If the failure did not damage the server or the operating system and you want to reuse the server, start with 1B Reusing your source and then continue with the remaining instructions.

Virtual servers—If your original source was a virtual server, you preparation method will depend on if you want to create a new virtual guest or reuse the existing one.

New virtual guest—If your original guest is unusable, start with 1A Preparing a new source by reinstalling Windows and then continue with the remaining instructions.

Note: If possible, you can attach any virtual hard disks that survived the failure event to a new virtual guest. Reusing any undamaged disks will decrease the time required to restore data because you can use a difference mirror.

As an alternative to manually creating a new virtual guest, you can let Double-Take Availability automatically provision (create) the new virtual guest for you. If you choose this option, you will need to use the instructions for Double-Take Availability virtual protection and virtual failover instead of the instructions in this section.
Reusing virtual guest—If the failure did not damage the virtual guest and you want to reuse it, start with 1B Reusing your source and then continue with the remaining instructions.

1A. Preparing a new source by reinstalling Windows

1B. Reusing your source

2. Mirroring and replicating from the source to the original or new source and failing over