© 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.AWS Reference ArchitectureRecovery flow

Backup flow

AWS Direct

Connect

Internet

Amazon

Route 53

AWS Region

NSX CGW ESXi

Amazon EC2

DATA

OS

APP

OS

APP

OS

APP

OS

VMware Cloud on AWS SDDCCustomer Managed AWS Account

S3 bucket

virtual tape

library

AWS

Storage

Gateway

backend

AWS Storage

Gateway

(or other

partner appliance)

Customer Data Center

vSphere Environment

ESXi

DATA

OS

APP

OS

APP

OS

APP

OS

The final recovery step is updating the Route 53 DNS records to route new requests to secondary domain controller in AWS.

8

After VMware Cloud on AWS SDDC is ready, deploy the software to restore the backed up application and VM data from Amazon S3.

7

The recovery process starts by launching and configuring a VMware SDDC cluster in AWS with the web portal or through automation scripts using AWS CloudFormation, VMware vRA, or vCLI.

6

Use the virtual tape library configuration in the Storage Gateway for long term data archiving to AWS Glacier or other archive service.

5

File gateway uses an AWS Identity and Access Management role to access the customer backup data and securely store it in Amazon S3.

4

The on-premises Storage Gateway securely transfers the backup data to the Storage Gateway backend using Direct Connect or through an SSL Internet connection.

3

VM and application backups are stored in Amazon S3 using an AWS Storage Gateway or other storage appliance using a partner-integrated solution or application-level backup software.

2

#

Amazon Route 53 routes DNS requests to the primary domain controller on-premises.

1

Description

user

Backup and Restore to VMware Cloud on AWSNative Services Integration: Storage Gateway, S3, Direct Connect, and Route53

1

2

34

5

6

7

8

Recovery Point Objective: ~24 hours

Recovery Time Objective: ~4 - 6 hours

Cost: $

© 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.AWS Reference Architecture

Pilot Light on VMware Cloud on AWSNative Services Integration: Storage Gateway, EC2, S3, DMS, Direct Connect, and Route53

The final recovery step is updating the DNS records to route new requests to the secondary domain controller in AWS.

10

Recovered applications in VMware SDDC directly connect to the secondary database through VMware endpoints.

9

After VMware Cloud on AWS SDDC is ready, retrieve backed up data using (A) public S3 endpoint or (B) VMware endpoint using S3 VPC endpoint.

8

The recovery process starts by launching and configuring a VMware SDDC cluster in AWS with the web portal or through automation scripts using AWS CloudFormation, VMware vRA, or vCLI.

7

Single point-in-time backups can be created on the secondary database using EBS snapshots stored in S3.

6

File gateway uses an AWS Identity and Access Management role to access the customer backup data and securely store it in Amazon S3.

5

Storage Gateway and DMS connect to the backend AWS services endpoints over Direct Connect or the Internet.

4

AWS Database Migration Service (DMS) replicates data from primary database to secondary database in AWS.

3

VM and application backups are stored in Amazon S3 using an AWS Storage Gateway or another storage appliance or software backup solution.

2

Amazon Route 53 routes DNS requests to the primary domain controller at the customer data center.

1

Description#

AWS Storage Gateway

Customer Data Center

vSphere Environment

ESXi

DATA

OS

APP

OS

APP

OS

APP

OS

AWS Direct Connect

Internet

AmazonRoute 53

AWS Region

NSX CGW ESXi

Amazon EC2VMware Cloud on AWS SDDC

Customer Managed AWS Account

S3 bucket

AWS Storage Gateway backend

APP

OS

APP

OS

APP

OS

VMware Managed AWS Account

Customer VPC Amazon EC2

DATA

OS

(or any DB replication technique)

Secondary Database

AWS DMS

110

2 34

5

6

7

9

8A

8B

user

Recovery flow Backup flow

Recovery Point Objective: MinutesRecovery Time Objective: ~4 – 6 hours

Cost: $$