3.4 Failback

This section assumes an original source server has failed, and a failover to a disaster recovery virtual machine has already taken place (see Planning for Failure). It also assumes that the target for the failback procedure does not already exist in Forge. The following instructions are a guide to deploying the virtual machine back onto physical hardware or to a virtual server (depending on whether the protected workload was a physical server or a virtual machine).

To failback a failed over workload you need to prepare the failback, configure the failback, run the failback and then optionally configure reprotection for the workload.

3.4.1 Preparing the Failback

  1. From the Forge dashboard, click Workloads.

  2. Select the checkbox next to the failed over (live) workload for which you would like to configure failback.

    Notice that some of the command buttons on the bottom of the screen become available in response to the type of workload selected. In this case, since the workload has been failed over, you can either configure failback or remove the workload.

  3. Click Configure Failback.

    The Failback Details page is displayed, prepopulated with the credentials for the workload you selected.

    NOTE:The IP and/or password for the workload may have changed while the workload was failed over. If so, make any required adjustments to the credentials.

  4. If you are failing back to brand new hardware or a new virtual machine, select Full Replication. If you are failing back to the same hardware or the same virtual machine that was previously protected, select Incremental Replication.

  5. Select either Virtual Targets or Physical Targets, as appropriate for your task.

  6. To failback to a physical target, see Step 7. To failback to a virtual target, skip to Step 8.

  7. To failback to a physical target for either a full (new hardware) or incremental (existing hardware) replication, you need to boot up and register the target physical server using the WinPE* ISO image. You can get the image by clicking Click to download at the bottom of the page. Once the target is booted up and registered, it will appear in the list of physical targets you can select for the failback task. Skip to Step 13.

  8. To failback to a virtual machine, click Add Target.

    For a full replication, see Step 9. For an incremental replication, skip to Step 11.

  9. For full replications, enter the Hostname/IP Address, the Username and the Password for the failback target server (hypervisor where Forge will create the virtual machine to which you will failback).

    NOTE:If both the failover and source workloads are online, use the IP address to identify them, since they will both have the same hostname.

  10. Click Add to return to the Prepare Failback page. Skip to Step 13.

  11. For incremental replications, click Add Target to display the Add Target(Virtual Server) page.

    Enter the Hostname/IP Address, the Username and the Password for the failback target server (hypervisor where the virtual machine to which you will failback resides) and click Add.

    The Add Target(Virtual Machine) page is displayed where you can select the virtual machine and network to which you want to failback.

    NOTE:Currently only ESX 3.x and 3i are supported as failback targets. When specifying a virtual failback target using incremental replication, you actually need to specify the hypervisor container as the target. In subsequent steps, you will specify the virtual machine in that container as the actual failback target.

  12. Click Add to return to the Prepare Failback page.

  13. Select the radio button next to the target you just added.

  14. Click Save and Prepare.

    Notice the green arrow in this button which indicates no confirmation message is displayed for this step. Proceed to Configuring and Running Failback.

3.4.2 Configuring and Running Failback

  1. Confirm the failback settings. Most of these setting typically are fine as is. For information on file transfer methods, see Supported Transfer Methods.

  2. (Optional) To stop any running services during the failback procedure, click Add Services, select services to stop and click Apply.

  3. Make any desired changes to the workload settings, including changing the state of any existing services.

  4. In the post-failback settings, specify whether you want to reprotect the workload after failback.

    If you choose not to reprotect the workload, you can choose whether to leave the failed-back workload powered on or not.

  5. Click Save and Failback.

    Optionally, proceed to Configuring Reprotect.

3.4.3 Configuring Reprotect

If you opted to reprotect the workload after failback, when the failback has completed running, you are presented with the Configure Reprotect page.

  1. Confirm the workload hostname/IP and credentials supplied by Forge.

  2. Specify whether you want the initial replication to be full or incremental. If you select incremental, confirm the Network and whether the IP assignment is DHCP or Static. If it is a static IP, fields are displayed for you to enter the configuration information.

  3. Click Save and Reprotect.

    To complete reprotect, see Configuring Protection and Preparing Replication.