Skip to main content

AWS Backup for VMware Cloud on AWS workloads - The Design

This blog post provides the high level design for implementing the Native AWS Backup to protect the VMware Workloads hosted on VMware Cloud on AWS. 

VMware Cloud on AWS

VMware Cloud on AWS enables customers to deploy the SDDC and consume vSphere workloads as a managed service on AWS global infrastructure. VMC is a jointly engineered solution by VMware and AWS that provides customers with a true hybrid cloud experience.

As customers continue to adopt VMware Cloud on AWS, data protection for the VMs and workloads hosted on the VMC SDDC is becoming increasingly important. Customers should also be able to comply with data regulations and manage backup costs effectively.

This post will go over the design considerations and best practices for enabling Native AWS Backup for VMs hosted on VMC SDDC. We'll go over different architecture design options and use cases that address customer needs.

AWS Backup for VMware

We can centrally protect our VMware workloads hosted on VMC SDDC thanks to AWS Backup support for VMware. AWS Backup enables us to demonstrate the status of compliance with our organizational data protection policies by monitoring backup, copy, and restore operations and generating unified auditor-ready reports to help us meet data governance and regulatory requirements. 

How does AWS Backup work with VMware SDDC

AWS Backup connects to VMware workloads via the AWS Backup gateway, which we will deploy in our VMC SDDC Compute Cluster. AWS Backup gateway discovers VMs via VMware vCenter Server, takes VM snapshots, and manages backup and restore data between AWS Backup and the VMC SDDC. We can assign VMs to your backup policies using tags, VM Resource IDs, or group assignment by VM folder or hypervisor, which centrally govern data protection of VMware VMs with supported AWS Backup services. Following these steps, AWS Backup begins securely backing up VMs into AWS Backup's storage vaults. You can view your VMware backups in AWS Backup and restore them on-premises, to VMware Cloud on AWS, VMware Cloud on AWS Outposts, Amazon EBS, or Amazon EC2 as needed. 

The detailed deployment steps to be followed in the next blog post. 

Deciding the Network path for the Backup traffic 

The great advantage of VMware Cloud on AWS is that it can integrate seamlessly with native AWS services like AWS backup. During the SDDC onboarding process, customers are able to establish high-bandwidth and low-latency connectivity to a designated VPC, which is often referred to as the connected VPC. This connectivity is established using cross-account Elastic Network Interface (ENI) between the NSX Edge appliance in the VMware-managed shadow account and a subnet within the AWS connected VPC in the customer-managed account. 

Advantage of ENI

Virtual machine workloads running on the VMC SDDCs and accessing native services hosted in the connected VPC (AWS Backup) will use the ENIs rather than the VMware Transit Connect, improving operations efficiency and lowering data transfer costs.

Because the VM backup size is large (daily, weekly, and monthly), it is recommended to use ENI to avoid cluttering the network bandwidth of VPN, Direct Connect, VMware Transit Connect, or the Internet path. 

The Architecture 

The detailed deployment steps to be followed in the next blog post. 

Popular posts from this blog


The BCD registry file controls which operating system installation starts and how long the boot manager waits before starting Windows. Basically, it’s like the Boot.ini file in earlier versions of Windows. If you need to edit it, the easiest way is to use the Startup And Recovery tool from within Vista. Just follow these steps: 1. Click Start. Right-click Computer, and then click Properties. 2. Click Advanced System Settings. 3. On the Advanced tab, under Startup and Recovery, click Settings. 4. Click the Default Operating System list, and edit other startup settings. Then, click OK. Same as Windows XP, right? But you’re probably not here because you couldn’t find that dialog box. You’re probably here because Windows Vista won’t start. In that case, you shouldn’t even worry about editing the BCD. Just run Startup Repair, and let the tool do what it’s supposed to. If you’re an advanced user, like an IT guy, you might want to edit the BCD file yourself. You can do this

DNS Scavenging.

                        DNS Scavenging is a great answer to a problem that has been nagging everyone since RFC 2136 came out way back in 1997.  Despite many clever methods of ensuring that clients and DHCP servers that perform dynamic updates clean up after themselves sometimes DNS can get messy.  Remember that old test server that you built two years ago that caught fire before it could be used?  Probably not.  DNS still remembers it though.  There are two big issues with DNS scavenging that seem to come up a lot: "I'm hitting this 'scavenge now' button like a snare drum and nothing is happening.  Why?" or "I woke up this morning, my DNS zones are nearly empty and Active Directory is sitting in a corner rocking back and forth crying.  What happened?" This post should help us figure out when the first issue will happen and completely avoid the second.  We'll go through how scavenging is setup then I'll give you my best practices.  Scavenging s

AD LDS – Syncronizing AD LDS with Active Directory

First, we will install the AD LDS Instance: 1. Create and AD LDS instance by clicking Start -> Administrative Tools -> Active Directory Lightweight Directory Services Setup Wizard. The Setup Wizard appears. 2. Click Next . The Setup Options dialog box appears. For the sake of this guide, a unique instance will be the primary focus. I will have a separate post regarding AD LDS replication at some point in the near future. 3. Select A unique instance . 4. Click Next and the Instance Name dialog box appears. The instance name will help you identify and differentiate it from other instances that you may have installed on the same end point. The instance name will be listed in the data directory for the instance as well as in the Add or Remove Programs snap-in. 5. Enter a unique instance name, for example IDG. 6. Click Next to display the Ports configuration dialog box. 7. Leave ports at their default values unless you have conflicts with the default values. 8. Click N