Matthew Wallace, CTO of Faction, sees VMware Cloud on AWS growing in 2019. Here, he shares insights about trends in VMware, best use cases, advantages, and how to avoid delays and complications in disaster recovery.
Q. Do you see growth for VMware Cloud on AWS in 2019?
Yes. VMware has finally reached the tipping point where customers are no longer just kicking the tires. Instead, they are adopting the platform for disaster recovery (DR) and production use cases. At Faction, we’ve seen exponential growth in our pipeline and customer base for VMware Cloud on AWS; we expect this to accelerate throughout 2019 and beyond.
Q. What are the industry challenges facing VMware Cloud on AWS?
VMware has historically been a company that sold software. The company needs to pivot to selling cloud throughout their entire sales force. This could be a complex problem to solve at their global scale.
Q. What are the best use cases for using VMware Cloud on AWS?
There are four best use cases that we see:
1. First is disaster recovery. VMware Cloud on AWS allows for the use of existing on-premise DR technology, like VMware Site Recovery, to reduce the cost and complexity of replicating to cloud. On-demand scale-out provided by cloud DR also eliminates the need for the upfront costs of building an entire secondary site, which would only be used in the event of a failover.
2. Datacenter extension is a second important use for customers who need additional capacity for various reasons. Test/Dev capacity, added geographic locations or seasonal spikes can all expand a company’s on-premises footprint without adopting new and unfamiliar cloud technology or tools.
3. The next consideration is ease of cloud migrations. VMware platform consistency—on both source and target sites— allows customers to accelerate their migration to cloud. Familiar VMware tools require fewer expenses and less time, since you do not need to hire or retain expensive public cloud talent. You can also reduce time to value by integrating VMware tools being used on-premises.
4. The fourth and final use scenario is integrating applications with cloud services to boost business outcomes. Once you are deployed, you’ll be able to combine legacy apps that are migrated to VMware Cloud on AWS with native AWS IaaS or PaaS services. This provides your developers with tools to expand the business outcome that your application delivers.
Q. What are the advantages to cloud-based DR?
In short, there are four: geographic diversity, cloud services, scale and DR software.
– Geographic diversity: AWS has 60 availability zones across 19 regions and growing, not counting two GovCloud regions. VMware is rapidly expanding to all of them.
– Cloud services: One thing we’ve seen is that AWS offers a lot of services that help provide functionality that might otherwise need dedicated appliances or complex on-premises setup. For example, AWS Application Load Balancer and Network Load Balancer can replace costly on-premises hardware load balancers.
– AWS CloudFront Content Delivery Network can help ensure rapid scaling and high performance. AWS marketplace appliances can help replace other on-premises appliances.
– Scale: Need we say more? AWS spent over $25 billion on capex in 2018; a great deal of that went toward hardware for AWS. One of the largest appeals of DR to the cloud is the enormous capacity of AWS.
– DR software: As DR has increasingly moved to software-defined tools, those tools have become more complex. Now electronic versions of runbooks allow sophisticated ordering, checkpoint, custom scripting, network modifications, and more, all in an easy to use format.
Q. What are some customer challenges to cloud-based data protection solutions?
Fortunately, Faction’s offering of disaster recovery services on VMware Cloud on AWS delivers the advantages of Public Cloud based DR, without the following disadvantages of other solutions:
– Import, export and failback issues: If you have to go through a converter (which most recover to cloud tools require, because it is not VMware on the target side), you may not convert properly. Then you could have a “disaster” during your disaster recovery. Additionally, conversion can add a lot of time, worsening your recovery time objective (RTO). Finally, most cloud tools don’t support failback and require a manual process, prone to human errors.
– Tool incompatibility: VMware has a broad ecosystem of tools with solid integrations. You lose that if you go to public cloud directly.
– RTO time: Conversion adds a lot of time. Weak runbook software adds a lot of time. This is an infamously large problem.
– People, process and technology: You are going to have hair on fire during a live-fire full failover to a DR site. This is not the time to be using new tools. For example, say there’s an error in your AWS VPC security group. How many minutes will it take to diagnose and fix it when your team doesn’t have extensive experience in public cloud technology? Add to it the considerations of VMware Private Cloud providers. In order to provide on-demand capacity, they generally use vCloud Director, which means you’ll lose vCenter access and force your team to use an unfamiliar tool in the middle of a disaster recovery event
About the Author
As CTO, Matthew Wallace is responsible for product development, managed and professional services, and architecting Faction’s cloud infrastructure offerings. Prior to Faction, Matt has worked 20 years in technology in roles at both startups and Fortune 500 companies, including leadership roles at Level 3 Communications, ViaWest, Exodus Communications, and others. Matt is the co-author of Securing the Virtual Environment: How to Defend the Enterprise Against Attack, one of the first books to holistically address cloud security concerns. Matt is an Official Member of the Forbes Technology Council.