VMware Failover

VMware Failover

If your primary server/VM has crashed due to a disaster, switch over to the replicated VM to continue with production. When your source machine is down, you can use the Failover process to switch the operations from the source VM to its replica in the target server. Once the Failover process is carried out, the replica machine will perform the role of the source machine. That is, the target VM will be powered ON with the same Network and IP configurations that were configured during the replication process.
  1. You can Failover the replica to any restore point available. If any data is added when the VM is in the Failover state, it will be maintained separately in a snapshot delta file.
  2. Select the VM Replication tab and choose the Failover and Failback option. Click the Restore icon beside the required replication job.
  3. The next step is to select the restore type from the list. Select Failover as the restore type and click Next to proceed with the restore process.
  4. Choose the restore version from the tree. The restore version depends on the retention settings you have configured. Click Next to continue with the restore process.
  5. The next step is to select the restore data for the restoration. Select the VM(s) to be restored. You can search the required machine from the Search VM option. Click Next to continue further with the restore process.
  6. The last step is to review your configurations before you perform the Failover process.
  7. Verify the following – VM(s) selected for the Failover, Restore Version configured. Once done verifying the selection, click the Failover option. You will get a pop-up window to confirm the Failover process, click OK to begin the Failover.
  8. You will now be redirected to the Restore Progress page. Check the Client Name, Backup Name, and Progress status.
Notes
Note: The VM should not be manually powered on or powered on after the Failover as it may lead to data loss.
Click the Failover and FailBack option and you will be taken to the list of replication jobs page. Click on respective jobs Restore progress icon to track the progress.

Finalize Failover

  1. Once you have performed the Failover process, you can finalize the Failover process. This option helps you finalize the failover process and let you decide whether to:
  2. Revert to Source VM immediately
  3. Completely switch from Source VM to replica VM
  4. Rollback to the Source VM after a considerable amount of work is done by the replica.
  5. Finalize Failover can be done based on the above scenarios as follows
Undo Failover

If you have performed the Failover process but then got your source VM running back up within the stipulated time and want to undo the Failover process, proceed with this type.

Procedure

Select Undo Failover from the Finalize Type and review the configurations by checking the selected VM(s) and the restoration type

Click Undo Failover to begin the restore process. Select OK from the pop-up window to confirm the Failover.
Notes
Note: The changes done in the target VM machine will be lost after undoing Failover. This ‘undo failover’ option is preferred when the source VM is restored and activated successfull
Permanent Failover

If you have failed over to the replica VM after a disaster and could not get your source VM running back up within the stipulated time, you can permanent the Failover process. The replica VM will be made the source VM permanently.

Procedure

Select Permanent Failover as the Finalize Failover type and review the configurations by checking the selected VM(s) and the restoration type.

Click Permanent Failover to make the Failover process permanent. Select OK from the pop-up window to confirm the Failover.
Notes
Note: The replica VM will be excluded from the replication job after completion of Permanent Failover. The same should be configured again for replication.
Failback

You have failed over to the replica VM after a disaster and begin working on the replica VM. You got the source VM running within a week. Then use the Failback option to Failback to the Source VM and begin working on it

Procedure

From the Finalize Failover type, select Failback and click Next to continue further.

You can restore to VMware Server or directly to the vCenter Server. If you want to add a VMware Server, click the +Add option, and provide the required details. Enter the Hostname/IP Address and select a credential if you have already from the Select Credentials drop-down list. Add a new credential by selecting the Add Credentials option. To read more on adding credentials, read this section – Credential.

Select the preferred option and specify the datastore and VM name of the source VM. Click Next to proceed to review your selection.

Review your selection by checking the following
  1. Selected VMs
  2. Failover Type
  3. Target Server Name
  4. Target Datastore
  5. Target VM Name
Click the Failback option to begin the Failback. Select OK from the pop-up window to confirm the Failback.
Notes
Note: Failing back only the modified data after performing Failover is not supported. If the Failback process fails intermittently, you have to delete the Failback VM in the target site and try again.
  1. The above-listed options get enabled only after performing the Failover process.

Follow the steps given to Finalize Failover

  1. Choose the VM Replication tab and select the Failover and Failback option.
  2. Click the Restore icon across the replication job which you had recently failed over.
  3. From the Restore type, select Finalize Failover as the restore type and click Next to proceed.
  4. The next step is to select the restore data for the restoration. Select the VM(s) to be restored. You can search the required machine from the Search VM option. Click Next to continue further with the restore process.
  5. The next step is to select the Finalize type. Three options will be displayed which are explained below:
  6. Undo Failover – This option will revert the replica machine to its original state (turned-off state) before the failover was performed. That is all the changes(work data) made in the target VM during the Failover period will be flushed and lost after undoing the Failover.
  7. Permanent Failover – You can select this option if the source VM is not recoverable after a disaster. Finalizing failover will enable you to make the replica VM as the production machine permanently. The VM will be excluded from the replication schedule and further increments for the source VM will cease.
  8. Failback – This option allows you to revert from the target VM to the source VM completely with all the changes made after failing over. You can recover the replica VM to the same or different host and continue the operations of the production VM.

    • Related Articles

    • VMware Replication

      Overview BDRSuite offers agentless replication solutions for VMware ESXi & vCenter. It provides near continuous data protection with flexible storage, instant failover & failback, and centralized management for efficient VM replication. Watch the ...

    • Replica Virtual Machine Stuck in Failover State in BDRSuite

      KB ID: 105068 Summary: This knowledge base article addresses the issue of a replica virtual machine being stuck in the failover state within the BDRSuite application. The error can arise due to VMWare replication when the configured virtual machine ...

    • Does BDRSuite support VMware replication?

      Yes, BDRSuite supports VMware replication, allowing you to replicate VMs efficiently between VMware environments. You can then perform Failover and Failback as well.

    • Configuring VMware VM Replication

      BDRSuite offers VMware Replication, a feature with which you can replicate your VMs and create an exact copy of the production VM on another vCenter Server/ESXi host. The VMs that are replicated to the target host will be synchronized with the VM ...

    • Hyper-V Failover

      Sometimes businesses may require a substitute of the Virtual Machine that is being used for their business-critical function in times of disaster. In such cases, they will want to avoid downtime and have the VM in a ready-to-use format so that their ...