Backup and Restore to VMware Cloud on AWS #

1
Description
Amazon Route 53 routes DNS
Native Services Integration: Storage Gateway, S3, Direct Connect, and Route53 requests to the primary domain
controller on-premises.
VM and application backups are stored
2 in Amazon S3 using an AWS Storage
Gateway or other storage appliance
using a partner-integrated solution or
application-level backup software.
user 8
The on-premises Storage Gateway
1 Amazon 3 securely transfers the backup data to
Route 53 the Storage Gateway backend using
6 Direct Connect or through an SSL
Internet connection.
Internet File gateway uses an AWS Identity
APP
APP
4 and Access Management role to
APP APP access the customer backup data and
OS
APP
APP 3 7 OS
OS securely store it in Amazon S3.
OS
OS 4
OS Use the virtual tape library
2 DATA
5 configuration in the Storage Gateway
DATA
for long term data archiving to AWS
OS Glacier or other archive service.
OS AWS Storage S3 bucket NSX
AWS Direct AWS ESXi The recovery process starts by
Gateway
Connect Storage 5 CGW
6 launching and configuring a VMware
ESXi (or other
Gateway
partner appliance) SDDC cluster in AWS with the web
backend portal or through automation
scripts using AWS CloudFormation,
virtual tape VMware vRA, or vCLI.
vSphere Environment library
Amazon EC2 After VMware Cloud on AWS SDDC is
Customer Managed AWS Account
7 ready, deploy the software to restore
VMware Cloud on AWS SDDC
Customer Data Center the backed up application and VM data
from Amazon S3.
Recovery Point Objective: ~24 hours AWS Region
The final recovery step is updating
Recovery Time Objective: ~4 - 6 hours
Cost: $
8 the Route 53 DNS records to route
Backup flow new requests to secondary domain
Recovery flow AWS Reference Architecture controller in AWS.
© 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
 # Description
Pilot Light on VMware Cloud on AWS Amazon Route 53 routes DNS requests to
1
Native Services Integration: Storage Gateway, EC2, S3, DMS, Direct Connect, the primary domain controller at the
customer data center.
and Route53 VM and application backups are stored in
2 Amazon S3 using an AWS Storage
Gateway or another storage appliance or
software backup solution.
10
user 1 AWS Database Migration Service (DMS)
Amazon
3 replicates data from primary database to
secondary database in AWS.
Route 53 AWS Storage 7
Gateway Storage Gateway and DMS connect to the
backend S3 bucket 4 backend AWS services endpoints over
Direct Connect or the Internet.
5
Internet File gateway uses an AWS Identity and
APP 5 Access Management role to access the
APP AWS DMS customer backup data and securely store
APP
OS
4 8A
APP
APP
OS APP it in Amazon S3.
OS 2 3 OS
OS
Single point-in-time backups can be
6 OS 6
AWS Storage created on the secondary database using
(or any DB replication
DATA
Gateway technique) 8B EBS snapshots stored in S3.
NSX
OS CGW ESXi The recovery process starts by launching
AWS Direct DATA
7 and configuring a VMware SDDC cluster
ESXi Connect in AWS with the web portal or through
Secondary
Database OS 9 automation scripts using AWS
CloudFormation, VMware vRA, or vCLI.
After VMware Cloud on AWS SDDC is
vSphere Environment Amazon EC2
8 ready, retrieve backed up data using (A)
public S3 endpoint or (B) VMware
VMware Cloud on AWS SDDC endpoint using S3 VPC endpoint.
Customer VPC Amazon EC2
Customer Data Center Recovered applications in VMware SDDC
Recovery Point Objective: Minutes
Customer Managed AWS Account VMware Managed AWS Account 9 directly connect to the secondary
Recovery Time Objective: ~4 – 6 hours database through VMware endpoints.
Cost: $$ AWS Region
Backup flow The final recovery step is updating the
Recovery flow AWS Reference Architecture 10 DNS records to route new requests to the
secondary domain controller in AWS.
© 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.