Skip to main content
Druva Documentation

Launch failback

This topic provides instructions on how to failback an EC2 instance recovered during failover in your AWS account. A failback is triggered on an EC2 instance on the Phoenix Management Console. When you trigger a failback, you must provide the details of the EC2 instance that you want to failback and the settings of the destination VMware. Unlike failover, you cannot pre-configure the settings for failback.

Note: You cannot trigger failback on multiple EC2 instances at a time. Also, you cannot trigger multiple failback operations for the same EC2 instance simultaneously.

Before you begin

Before you trigger failback, ensure the following:

  • The EC2 instance to be failed back must be in the running state. If the EC2 instance is in the stopped state, you must start the EC2 instance before triggering failback. The status of the failed over EC2 instance is fetched by the Phoenix AWS proxy from the AWS Cloud. 
  • Ensure that the failed over instance should have an additional space of 1.5 GB available for data copy.
  • The customer’s AWS account must be accessible from the vCenter data center where the backup proxy is installed.
  • You must stop all application services running on the EC2 instance that you want to failback so that no updates to the application are lost during the failback process.
  • You must assign a public IP address to the EC2 instance to be failed back. Ensure that the following ports are open.
    • Linux: Port 22 for SSH
    • Windows: Ports 400 and 50000

      Note: You must manually enable the SMP port for communication. 

  • When a failback job is running, ensure that an EC2 instance is not stopped or terminated.
  • Phoenix DRaaS does not allow you to resume the failback operation.

Procedure

  1. Log in to the Phoenix Management Console.
  2. On the menu bar, click All Organizations, and select the required organization from the drop-down list.
  3. On the menu bar, click Disaster Recovery.
  4. In the left pane, click the Failover Instances tab and select the check box of the instance for which you want to trigger a failback.
  5. Click Failback.
  6. On the Failback Settings page, provide the details in the EC2 Settings tab as shown in the following screenshot: 
    Failback_settings_EC2_settings.PNG
    • EC2 Username: The username required by the target worker virtual machine to connect to the EC2 instance.
    • Password: The password required by the target worker virtual machine to connect to the EC2 instance.
    • Source EC2 Network: The IP address of the source virtual machine. This network is used to transfer the data to the destination VMware environment. 
    • Stop EC2 instances after failback: Select this check box to stop the EC2 instance in the AWS account after the failback operation completes so that the application in your data center can run. AWS continues to charge for the EBS storage associated with the running EC2 instance and any unused Elastic IP addresses. 
  7. Click Next.
  8. On the Failback Settings page, provide the recovery site details in the Destination Settings tab as shown in the following screenshot:
    Destination_VM_Settings.png
    • vCenter: Select the vCenter setup where the instance should failback. This list only displays the vCenter servers registered with Phoenix DRaaS. 
    • Backup Proxy Pool: Select the name of the backup proxy pool that the backup proxy is part of. It is recommended that you select a backup proxy pool with backup proxies that support failback and are locally connected to the destination hypervisor.
    • Hypervisor: Select the IP address of the ESXi Hypervisor in the vCenter where you want to failback this EC2 instance.
    • Datastore: Select the data store where you want to failback this EC2 instance.
    • Compute Resource: Select host, cluster, or a resource pool where you want to failback the EC2 instance. You cannot select a datacenter or a folder.
    • VM Folder: Select a folder under the data center hierarchy where you want to failback the EC2 instance.
    • Network: Select the network setting available at the destination hypervisor.
    • VM Name: The name of the destination virtual machine.
    • Use static IP for the destination VM: Select this check box if you want to use pre-configured static IP for the virtual machine. When you select this check box, the following fields appear.
      • DNS: The IP address of the Domain Name System (DNS) server. 
      • Default Gateway: The IP address of the router used in your network.
      • Subnet: The subnet to be used during failback based on the source network present on the destination virtual machine.
      • IP Address: The IP address of the destination virtual machine where you want to failback data in your data center.
    • Keep VM(s) powered-off after failback: Select this check box to shut down the virtual machine in your data center after the failback operation completes to ensure that no updates to the application are lost during the failback process.
  9. Click Failback.

Failback is successfully triggered for the selected EC2 instance. Phoenix generates a failback job for this operation. You can view the details of the failback job and progress logs on the Job Details page. The backup proxy in your vCenter data center downloads a target virtual machine from the S3 bucket and launches a virtual machine in the data center using the target virtual machine. The virtual machine connects to the failed over EC2 instance and Phoenix DRaaS transfers the data to this virtual machine.

Note: If you have applied auto configuration rules to the target virtual machine, Phoenix automatically configures the virtual machine for backup. After a failback operation completes, the next backup of the configured virtual machine will be a full backup.

  • Was this article helpful?