Get best of the week

Disaster Recovery and migration using VMware vCloud Availability. Part 2

Hello! In a previous post, I talked about the capabilities of VMware vCloud Availability (vCAV) and showed how to organize Disaster Recovery (DR) and migration within several cloud provider sites. Today we’ll see how to recover using vCAV or simply migrate to the cloud of a service provider from an on-premise platform. In our example, we will configure DR from the customer’s local site to the cloud in St. Petersburg. 



At the preparation stage, you need to decide how to provide access to the servers after they are restored in the cloud. To do this, you need to organize network connectivity between the local site and the cloud. About the main ways to connect to the cloud, I wrote here .

For convenience, I made quick navigation according to the instructions:



Configure vCloud Availability Appliance for Tenants on-premises


To prepare your on-premise site for relocation or restoration, you must deploy and configure a virtual machine with the vCloud Availability Appliance for Tenants.

  1. Download the virtual machine template from the VMware website .


  2. vCenter . -, , -. Deploy OVF Template .

    : 

    • ,  
    • , 
    • ,  
    • , 
    • , 
    • .


  3. Finish.


  4. . vCAV https://*IP--*/ui/admin. 



    . 


  5. — Initial Setup Wizard.


  6. .


  7. vCenter: 
    • lookup-, 
    • vCenter.  

    Platform Service Controller (PSC), lookup- PSC.


  8. vCenter.


  9. - vCloud Director. . 

    Allow access from cloud, vCloud Director .


  10. vCloud Director. 


  11. . , : . Configure local placement now. Finish.


  12. Configure local placement .

    : .




  13. , . 


  14. .


  15. Finish.


  16. vCAV System Monitoring -.


  17. vCenter vCloud Availability. . 


  18. vCAV -.


  19. vCloud Director, vCAV ( ).



DR on-premise


  1. vCAV. Incoming replications , DR: .


  2. New Protection.


  3. . 


  4. .


  5. .


  6. . , :
    • RPO. RPO — 5 .
    • Storage Policy. , . 
    • Retention policy. . 24 .
    • Enable quiesce. .
    • Advanced. - . , .


  7. , Finish.


  8. .



    .




  1. . Test Failover.


  2. : 
    • vApps — Power on recovered vApps;
    • — Apply preconfigured network settings on failover.


  3. .


  4. Finish.


  5. .



    , .


  6. .


  7. ( ) Test Clenup.



    Cleanup.


  8. , .



on-premise


  1. , , Failover.


  2. :
    • — Consolidate VM disks;
    • vApps — Power on recovered vApps;
    • — Connect all VMs to network.


  3. Select a recovery point.


  4. Click Finish .


  5. We are waiting for the switch to complete.


  6. We look for VM to appear in the cloud.


  7. To switch the direction of replication in the opposite direction, after the Failover operation, click Reverse . 


  8. As a result, the replication task from the cloud to the local site will be recreated. The original VM will be deleted.


  9. Now the cloud platform has become the source, and the backup one is local.



If necessary, you can do the reverse switch from the cloud to the local site.



In these articles, we looked at the main scenarios for using vCAV and showed how easy it is to protect your infrastructure or perform migration.

The tool is simple to configure, and most importantly - you can independently control the replication process.

More articles:


All Articles