23
Jun
2016

TUTORIAL: Disaster Recovery using VMWare VCloud Air

Marcelo Soares explaines 'How to use Disaster Recovery with VMWare VCloud Air Thursday, 23 June 2016 Data Center and Cloud Computing

Enabled since version 5.8 on vSphere Replication (if you are using vSphere 5.5), the public cloud DR option is very useful for quick and low cost solutions for disaster recovery.

The vSphere Replication tool available on all vSphere editions (excluding Essentials) and, if you have already used the most recent versions of it, every time you start a new replication, you have the following options:

 

 

 

Natively, vSphere Replication only accepted another vCenter as target, but actually we can include vCloud (Air or other vCloud Director enabled provider) as a target site. This means you already have the feature, and you only need to purchase resources from a provider. You can check pricing for vCloud air here: http://vcloud.vmware.com/service-offering/pricing-guide

 

But let’s check the hands-on operation. After you have registered for a DR solution on your provider, you will have the chance to get the information needed to connect and start the replications. Assuming you already have a vSphere Replication appliance in place (you can check how to deploy it here:

https://www.vmware.com/support/pubs/vsphere-replication-pubs.html , you can go, on the vSphere Web Client, to vSphere Replication > Manage > Target sites.

 

 

 

 

You will need to provide your vCloud Air VDC information, and you can check that on your Account Management section.

 

 

 

 

After this configuration, the vCloud Air VDC will show up as a possible target site for replication. It is necessary also to create test and production networks, but we can cover this on other blog post. After this initial configuration, it is possible to configure replication for any VM on vCenter:

 

 

 

After the replication starts, you can monitor the process on the vCloud Air interface. Note that there is a “Recovery” button on the top of the VM list – is kind of like if you have a VMware SRM available for failover, per VM:

 

 

 

 

 

And also on the vSphere Web Client:

 

 

 

In a case of a disaster, you can log into vCloud Air and recover your VMs there, manually, VM by VM. You may need to perform some configuration steps, but the power of the solution is that you have your VMs secure and available promptly as needed. Important detail: there is no Failback, you need to perform this manually copying your data from the DR site to production site in a maintenance window, but at least you were not down due to a problem. VMware allows you to have your VMs up a running on a DR event up to 30 days with no additional charge.

 

You can check by yourself how this works and test it running the HOL from VMware:

https://labs.hol.vmware.com

 

 

 

Ida Grondahl

PegasusSays

Pegasus Community
#Avaya may be considering forming a joint venture with #communications and #collaboration brand #RingCentral and is… https://t.co/fio1JV5Pwb
Pegasus Community
#Cisco, #Lenovo, #HP, #HPE and #Dell are taking on more risk for the #channel as partners shift to a more #cloud-lihttps://t.co/GnDoQ3JKTB
Pegasus Community
@Cisco has redesigned its #Cloud and #ManagedServiceProviders program to increase profitability for #MSP's working… https://t.co/rhRn9HOCzo
Pegasus Community
#APM - #ProductionMonitoring with @newrelic. Basic key metrics you should monitor in #NewRelic to find out the… https://t.co/O5steLBbuT
Pegasus Community
Meeting our partner @TufinTech and their customers today at customer panel here in #Lisbon #Tufinnovate #emea and l… https://t.co/n5cW7MKxre
Pegasus Community
Latest update on #Autonomy's trial earlier this week. #Deloitte auditor kept quiet at company's internal committees… https://t.co/113RkM7jzM
FOLLOW Pegasus Community ON_TWITTER

Magnolias House

Cryers Hill Road, Buckinghamshire

United Kingdom, HP15 6JR

Email:

Out and About

Sorry something went wrong. Here is the possible list of errors:

  • Error loading user data. Disconnect and connect instagram from module setting may fix this issue. Instagram connect expires in each 60 days.