vCloud Air OnDemand – Road Trip

vcloud-connector-us-18I have written a couple of posts on VMware’s vCloud Air DRaaS offering which covered ‘The Good, The Bad & Ugly‘ and ‘Improvements‘ to the service.  The reason for these original posts was based on customer enquiries and I wanted to get under the skin of VMware’s offering.

Since then customers have been asking more questions around using the cloud for application testing and development.

Application Testing

The issue with testing applications on-premises is you may not have the compute or storage resources available, an example is you want to upgrade your ERP solution to the latest version and test it before going into production.

ERP solutions are often complex three tier applications which require a decent amount of horse power to run.  Often businesses are nervous about upgrading the production software, as if someone goes wrong it could effect the entire company.

The solution to this could be to use vCloud Air OnDemand with vCloud Connector to link on-premises vCenter to vCloud Air.  A simple clone of your ERP virtual machines and then copy them to vCloud Air and test the application upgrade.


Many of the clients I deal with, don’t have access to dedicated vSphere Clusters and storage for development.  They are often nervous about giving developers a slice of their production vSphere clusters due to the effects a poorly designed application could have on their network and storage.

You could argue that placing limits on compute resources could mitigate the risk, but this then becomes a management overhead and politically it can cause all kinds of issues.

The solution to this could be again to use vCloud Air OnDemand.

vCloud Air OnDemand – Road Trip

With the above uses cases in mind, I wanted to give vCloud Air OnDemand a whirl.

The first step is to signup for vCloud Air OnDemand using the create a new MyVMware Account.

vCloud Air 1

Use this promotion code ‘Influencer2015’ and get a special offer of $500 in service credits.

After a few seconds you will receive an email to finalize your account settings, this essentially means create a password.  Then you are ready to login to your account.

Virtual Machine Provision

The ability to provision virtual machines quickly and easily is the acid test of an ‘cloud on demand service’.  The recording below shows my first interaction with the service.

Two issues cropped up:

  • Networking was not as straight forward as it could be.  You cannot assign a network to your first VM without it being powered on.  I wasn’t able to locate an add network in the vCloud Air area and used vCloud Director to assign the network.  Not sure how easy this would be for someone new accessing the service.  I believe it would cause some frustration to the user.
  • The password didn’t work that was assigned to my VMF-DC01 VM.  I even typed it in notepad to make sure I wasn’t going crazy.

Creating the second virtual machine I was able to assign a network on at the initial console screen and the password worked as well.

Final Thoughts

Overall the vCloud Air OnDemand experience was good.  However, first impressions count and not many of us spend time reading a manual for an ‘on demand’ service as we expect it to be straight forward.  If VMware can iron out the initial network and password issues, then my opinion would change from good to excellent. 

vCloud Air DRaaS – Improvements

Last October, I blogged about the vCloud Air DRaaS – The Good, Bad & Ugly in which I covered the following aspects:

  • Service Overview
  • vCloud Connector
  • Test Recovery
  • Failover and Failback

Logical Overview

The main area which was lacking with vCloud Air DRaaS was failback.  Failback could only occur offline whilst the virtual machine is shutdown.  If we do the basic maths on a 50GB virtual machine on 100Mbps dedicated connection it would take 76 minutes.

Multiple this by 100 virtual machines then the numbers start to get crazy.  It would take 127 hours or a little over 5 days to failback.  Could you image saying to your Directors, sorry we need everyone to take a week off work whilst we failback?

For the sake of brevity the calculation is shown below.  Overhead would be around 10% on 100Mbps link, giving 90Mbps throughput.


8Mb equal 1MB

50GB equals 51200MB

51200MB x 8Mb = 409,600 Mb

409,600 / 90Mbps = 4,551 seconds

4,551 seconds / 60 seconds = 76 minutes

100 VM’s x 76 minutes = 7,600 minutes

7,600 minutes / 60 = 127 hours

Good News

VMware understand that this kind of service was never going to be taken seriously by customers and could only be used for non production workloads and have announced some new service enhancements in a blog posted dated 20th January 2015.  The enhancements are:

  • Native failback support – provides seamless reverse replication from vCloud Air data centers to a customer’s environment, as well as support for offline data transfer via physical disk, to accommodate larger environments.
  • Multiple recovery points – enables multiple point-in-time copies of replicated VM(s), allowing you to roll back to earlier snapshots of your data center environment in the event of corruption or the need to recover to an earlier set of data.

Final Thought

This is an excellent move by VMware as now DRaaS could become reality.  What I would have hoped is that during failover VMware would have announced that they could offer virtual machine backups as part of the product offering.

Don’t forget DRaaS isn’t a panacea to fix application or service access for end users.  The same rules apply to an on-premises solution as they do a cloud based solution.

vCloud Air DRaaS – The Good, Bad & Ugly

I was recently given the task of looking into the vCloud Air DRaaS offering from VMware to understand how this could meet customers requirements to provide a disaster recovery platform for their production virtual machines.

This blog contains my understanding of the components, fit together, the good, the bad and the downright ugly parts of the vCloud Air DRaaS offering.

vCloud Air Key Benefits

The key benefits of the vCloud Air Disaster Recovery service are:

  • Restore point objective settings per virtual machine of 60 minutes or less
  • Subscription based ‘Recovery as a Service’ reducing capital outlay
  • Simple and secure asynchronous replication for virtual machines
  • Self-service disaster recovery testing of virtual machine
  • Guaranteed resource availability
  • On premise monitoring and management with the vSphere Web Client
  • Support for initial data seeding using vCloud Connector Offline Data Transfer
  • Supports the same guest operating systems and applications as vSphere
  • Application consistency for virtual machines running a Microsoft Guest Operating System
  • Integrates with your existing vSphere environment

vCloud Air Overview

vCloud Air Disaster Recovery is based on the following technologies:

  • Local VMware vSphere
  • Local and remote VMware vSphere Replication
  • Local and remote vCloud Connector
  • Remote VMware vCloud Air Disaster Recovery

A logical overview is shown below.

Logical Overview

vCloud Air Disaster Recovery is comprised of a number of components which enable the management, replication and access to virtual machines.

  • vSphere Replication – Provides asynchronous replication to copy virtual machines to an alternate location. Making the Makes the virtual machine copy available for recovery
  • vCloud Connector – Provides support for initial data seeding and failback of virtual machines to source site using Offline Data Transfer
  • vCloud Air – Infrastructure as a Service cloud owned and operated by VMware

vSphere Replication Appliance

A special version of vSphere Replication is used to copy virtual machines between location, and make that copy available for restoration using the vSphere Web Client.

  • vSphere Replication protects the virtual machine on an ongoing basis, replicating only changes that are made
  • Integrates with Microsoft Volume Shadow Copy Services (VSS) ensure that applications such as SQL Server databases are quiescent and consistent when replica data is being generated
  • Application consistency is achieved using Microsoft Windows Operation System with VMware Tools installed
  • vCloud Tunnelling Agent in the vSphere Replication appliance creates a tunnel to secure the transfer of replication data to vCloud Air Disaster Recovery service

vCloud Connector

vCloud Connector provides a single user interface for viewing private and public clouds and transferring content between them, as shown in the diagram below.

vCloud Connector

  • Connectivity between on premises and vCloud Air Disaster Recovery is achieved using SSL
  • Offline Data Transfer enables transfer of large volumes of data to the vCloud Air infrastructure
    • Data is securely encrypted onto a storage device supplied by VMware
  • vCloud Connector facilities failback of virtual machines

Test Recovery

vCloud Air Disaster Recovery service provides the ability to perform two test recoveries per twelve month period.

  • Testing a recovery does not affect production virtual machine workloads
  • Virtual machines in the test environment can be powered on for up to 7 days
  • While a test recovery runs, vSphere Replication continues to replicate data from the virtual machines at your source site
  • Test invoked at the source site have the ability to synchronise recent changes
  • Test recovery is per virtual machine

The diagram on the next page shows a logical overview of a test recovery.

Test Recovery


When you recover a virtual machine from your source site to vCloud Air, the production state of the virtual machine represents a point in time before the outage. Data accumulated after the last replication to vCloud Air and before the recovery is not available.

  • Recovering a virtual machine to vCloud Air stops replication from the source site
  • Virtual machines can be ran for up to 30 days in a failover scenario without additional cost.
    • If the source site is unavailable for a prolonged period, virtual machines can be transitioned to vCloud Air Private or Dedicated Cloud
  • Service Level Agreement of 4 hours or less of dedicated compute in a failover event, powered on and remotely accessible
  • Failover is per virtual machine


Failback of virtual machines that have been recovered in vCloud Air is performed using vCloud Connector.

  • Virtual machines are copied back to the source site using vCloud Connector using SSL
    • Default SSL Certificates are required to be replaced with an internal certificate authority
  • Failback should be within a planned outage windows as virtual machines are required to be powered off before being copied back to the source site

Consideration should be given to the amount of data to be transferred back in relation to the bandwidth available during failback

The Ugly

Having read this blog post you will have seen that a number of items would have jumped out at you.  The key considerations are shown below:

  • Failover to vCloud Air Disaster Recovery is per virtual machine.
    • Orchestration is possible, however this is currently at API level
  • DHCP is the default port group network setting. On failover each virtual machine receives an APIPA address.  Manual selection of the correct port group along with verification of network settings for each VM is required.
    • Note this is likely to change as vCloud Air Disaster Recovery Service is updated
  • vCloud Air Disaster Recovery does not include backup of virtual machines. Operational consideration should be given to the impact this may have to the recoverability of in guest data or failure of a VM
  • Failback from vCloud Air Disaster Recovery to on premises requires the virtual machines to be shutdown and copied back via vCloud Connector

Final Word

vCloud Air Disaster Recovery is a relatively new service introduced by VMware to UK datacentres in April 2014.  Even though vCloud Air Disaster Recovery is built on the proven technologies vCloud Director and vSphere Replication, a number of considerations exist,  Make sure that you make sure the service meets your requirements!