This tutorial shows you how to fail back a virtual machine from vCloud Air Disaster Recovery to vSphere on-premises. It assumes you have already installed and configured vCloud Connector between your on-premises environment and vCloud Air – Disaster Recovery.
Watch the video
Some failback operations are performed in vCloud Air, which requires the vCloud Connector Server to be connected to the vCloud Air Node. As shown in the following image, this tutorial assumes that this connection has already been established:
Stop the Virtual Machine in vCloud Air
To shut down the virtual machine:
4. Still in the Inventory pane, select the virtual machine that was failed over and then click the Power Off icon.
Rename the Original Virtual Machine
Remember that you already have a virtual machine in the vCenter inventory with same name as the replicated virtual machine in vCloud Air – Disaster Recovery. To keep the inventory current and easy to navigate, you need to rename the original virtual machine so that you can bring the replacement virtual machine back with the same name. You do this series of steps in the vSphere Web Client.
5. Moving to the vSphere Web Client, on the Inventory tab in the left pane, click the original virtual machine, and then select Rename.
6. In the Rename dialog box, enter a new name for the original virtual machine, and then click OK.
Once the original virtual machine is renamed, the next task is to stop replication. Note that there actually is no replication happening at this point, but you need to take this virtual machine out of the replication service inventory so that it can be restarted later. This series of steps simply reconfigures the virtual machine and brings it back to a state where you can use it later.
7. Select the recovered virtual machine, and then click the Stop Replication icon.
8. In the Stop Replication dialog box, click OK.
At this point, you can initiate a standard vCloud Connector copy from vCloud Air back to vCenter on-premises. You do this series of steps in the vCloud Connector client.
4. In the Copy Wizard – Select a target window, enter information as follows, and then click Next.
5. In the Copy Wizard – Select Resources window, select a resource cluster where the virtual machine will be sent once it is back on-premises. Then, click Next.
6. In the Copy Wizard – Select storage window, enter information as follows, and then click Next.
7. In the Copy Wizard – Deployment options window, choose whether or not to power on the virtual machine after deployment, and then click Next.
8. In the Copy Wizard – Ready to complete window, review the settings, and then click Finish.
Note: At this point, the virtual machine is being exported from vCloud Air. After export, copying through vCloud Connector will start, followed by importing to vCenter on-premises. You can see the progress in both the vCloud Connector client and the vSphere Web Client:
After the virtual machine has been transferred from vCloud Air to vCenter on-premises, you need to modify its settings so that it can be powered on in its original state. When the virtual machine was copied over, it adopted some default settings; you will change these settings in the vSphere Web Client. Then, you’ll run a set of command prompt tests to verify the settings.
Reconnect to the Correct On-Premises Network
To configure the connection to the on-premises network:
2. Click the virtual machine, and then select Edit Settings.
3. In the Edit Settings window, change the settings as needed, and then click OK.
4. Power on the virtual machine: Click the virtual machine, and then select Power On.
5. Review the virtual machine’s status and settings: On the Inventory tab in the left pane, click the virtual machine. Then, in the right pane, click the Summary tab.
Verify IP Address Assignment
At this point, you can examine the settings inside the virtual machine to ensure that everything transferred correctly and that it can communicate with not only the Internet but also other on-premises machines, such as the domain controller. (Note that this tutorial uses a Windows Server virtual machine and DHCP.)
4. Again at the command prompt, ping an outside IP location to verify that you receive a response.
5. Once more at the command prompt, enter the IP address for the local domain controller.
6. Review the virtual machine’s status and settings: On the Inventory tab in the left pane, click the virtual machine. Then, in the right pane, click the Summary tab.
The final task for failing back is to restart replication. This tutorial demonstrates the seed option, which can save time during the replication process. To set up replication, you'll use the vSphere Web Client. Then, you can monitor replication progress in both the vSphere Web Client and vCloud Air.
To define replication settings:
3. In the Configure Replication – Target site window, select the target site where the virtual machine will be replicated, and then click Next.
4. In the Configure Replication – Target location window, select the location for the target vApp, and then click Next.
5. In the Configure Replication – Replication seed window, select the correct virtual machine container, and then click Next.
6. In the Configure Replication – Replication options window, select a guest quiescing method, if desired, and then click Next.
7. In the Configure Replication – Recovery settings window, set an RPO value, and then click Next.
8. In the Configure Replication – Ready to complete window, review the configuration settings, and then click Finish.
Monitor Replication Progress
Behind the scenes, the replication process is now using the virtual machine in vCloud Air Disaster Recovery as a base to compare against the virtual machine you want to replicate. A full replication of this virtual machine took approximately 51 minutes. Using a seed, this process will be faster (approximately 27 minutes). Importantly, it also will save storage space. For this reason, you should use replication seeds if you want to reuse storage instead of reserving new space. However, if you want to maintain a virtual machine for testing or demonstration purposes, use the standard storage policy option instead.
Regardless of the replication option you choose, you can view the replication progress in the vSphere Web Client as well as vCloud Air.
9. In the vSphere Web Client, on the virtual machine's Monitor tab, note that configuration is taking place.
10. To move to vCloud Air, go to https://vchs.vmware.com/login and log in (if you haven't already).
11. From the Dashboard, click the desired virtual data center.
12. On the virtual data center's Dashboard, click the Virtual Machines tab. Note in the Recovery Status column that the virtual machine displays as a Placeholder.
13. Move to the Replication tab. Note in the Replication Status column that the virtual machine is registering an RPO violation.