Your Browser is Out of Date

Nytro.ai uses technology that works best in other browsers.
For a full experience use one of the browsers below
Cloud Disaster Recovery Best Practices
Executive summary Architecture Pre-deployment planning Deployment and post-deployment Protection to the cloud Recovery Failback
Failback
Uninstall REST API Limitations Maintenance and troubleshooting Technical support and resources

Failback

Home > Data Protection > PowerProtect Data Manager > White Papers > Cloud Disaster Recovery Best Practices > Failback

Failback

  • The Cloud DR Server orchestrates the recovery of protected virtual machines from segmented files stored on cloud targets to running VMs in the cloud.

    Failback is the opposite process of protection and recovery and consists of exporting failed over VMs that were recovered using Cloud DR back to virtual machines that run on the original on-premises VMware vSphere environment.

    What to do after a Failback ends successfully

    When the failed back virtual machine is ready, it will be powered off. Since we configured and deployed it in a staging area, it is recommended to review the location of the virtual machine, and if needed, vMotion it to another datastore, host, or network, as some organizations may not want to have their production virtual machines directly accessible from the Internet.

    After the failed back virtual machine is located on its final production location in the vCenter, VMware tools should be installed on it as AWS and Azure removes it during the Recovery process.

    An IP address should be assigned to the failed back virtual machine since the IP addresses from the IP range pool are used for the Restore VMs. Assigning an IP address can be done by opening a console to the virtual machine from the vSphere client, logging in to the operating system and changing the network settings. It is also possible by running scripts.

    The default hardware level of restored virtual machines is 10 and matches the minimal supported vSphere version. Upgrading the hardware level is possible from the vSphere client, in case it is needed specifically in the vSphere environment.

    After a successful Failback, the user should decide what to do with the powered off failover instance: terminate it, which is supported from the Cloud DR Server user interface, continue working with it (not recommended as a Failback should be permanent if it was successful), or keep it powered off.

    Make sure the failed back virtual machine is protected by PowerProtect Data Manager, Avamar, or RecoverPoint for VMs and that it is also protected to the cloud, by default it is not associated to any backup policy or consistency group.