Let us take a closer look at Disaster Recovery Failback. We will learn more on how to setup the failback feature with the assistance of Bobcares’ Server management support services.

What is Disaster Recovery Failback?

We can migrate business operations back to the source VM once we have restored the primary site following a disaster and handled any difficulties.

Failback aids in the recovery of the original VM on the source host (or at a new location of your choosing) and the transfer of workloads from the VM replica to the original VM.

However, certain modifications to the VM replica may have happened since failover. As a result, before conducting failback, the original VM and the VM replica must be synced to ensure that no important information is lost.

Only the altered data is returned to the originating system during fallback. To test the disaster recovery solution in Test Mode, start the target computers. After that, carry out a Failback.

Performing and Preparing for a Failover

This is the first step to setting up Disaster Recovery Failback. To perform a failover follow the steps given below:

1. Start the machine in Recovery Mode.
2. Employ the tool or mechanism we employ to direct traffic to do the real failover (directing traffic to the target computers).
3. We may use CloudEndure to prepare for Failback after a successful Failover.

To prepare for a failback follow the steps given below:

Note: The steps may differ depending on the setup and failback strategy. We can find detailed instructions for each setup here.

1. Before we can resume regular operations, the data that was written to the Recovery computers must be replicated back to the machines in the original Source infrastructure.
2. Select the Prepare for Failback option from the PROJECT ACTIONS menu in the User Console.
3. The Project view will be reset, and what were previously Target computers will now show as Source machines, ready to copy their data back to the original Source infrastructure, which will now appear as the Target infrastructure (temporarily).
4. Start Data Replication according to the setup for Disaster Recovery Failback.

• Original Source Original Target Failback method
• AWS AWS Fully orchestrated
• vCenter AWS Fully orchestrated
• Other Infrastructure AWS Use Failback Client

Failback Network Requirements

If we’re failing back to vCenter or another infrastructure, make sure we meet these extra Failback network criteria.

vCenter

Additional network needs are necessary for vCenter integration to function during the Failback process. This is the next major step in setting up Disaster Recovery Failback:

• VLAN for Staging (Replication Server and Conversion Server) should:

  A: Provide DHCP addressing

  B: Allow outgoing port 1500 (when failing back)

  C: Provide access to S3 so that the replication software may be downloaded.

  D: Give access to console.cloudendure.com through TCP 443.

  E: Allow access to the vCenter/vSphere hosts so that it may send API requests to them.
• The Appliance VLAN should allow the following:

  A: Allow TCP 443 access to console.cloudendure.com.

  B: Allow access to S3 in order for the replication software to be downloaded.

  C: Allow the virtual Appliance access to the vCenter/vSphere hosts so that it may submit API requests to them.
• The AWS instance used as the source should:

  A: Allow inbound port 1500 on the Source AWS instance to be open so that the CloudEndure Failback Client may connect to it.

  B: Allow the Source AWS instance TCP 443 access to console.cloudendure.com.

  C: Administrative access to vCenter, as specified in the Appliance installation.

Additional Infrastructure

• AWS instance of origin

  A: Allow inbound port 1500 on the Source AWS instance to be open so that the CloudEndure Failback Client may connect to it.

  B: Allow the Source AWS instance TCP 443 access to console.cloudendure.com.
• Non-cloud or other on-premises cloud environment (using the Failback client)

  A: Allow access to S3 for the target non-cloud or other on-premises cloud environment so that the replication software may be downloaded.

  B: Allow non-cloud or other on-premises cloud environments to connect to console.cloudendure.com through port 443.

  C: Allow outbound port 1500 on the target environment to be open.

Testing and performing the Failback

After conducting the Prepare for Failback step, ensure that all computers have achieved Continuous Data Protection status.

Before redirecting traffic back to the original Source, we should ensure that all of the computers set for Failback are operational.

Check the box to the left of the machine’s name in the Machine List View and choose Test Mode from the Launch Target Machines menu.

Performing the Failback

Employ the tool or technique we employ to route traffic to redirect traffic back to the original source infrastructure.

Before performing a failback, stop all operating services on the Source computer. We have to plan a Failback timeframe within which the Failback will take place.

Please keep in mind that during failback, CloudEndre will only replicate the deltas (changes).

[Need assistance with similar queries? We are here to help]

Conclusion

To sum up we have learned more about Disaster Recovery Failback. With the support of our Server management support services at Bobcares we have now gone through the failback setup process and how to use it.