Worldwide leaders in fund governance, risk and compliance, have deployed all of their Business Support IT Infrastructure in AWS. The workloads are primarily Microsoft based suites and the deployments are load balanced across the 3 Availability Zones in one of the AWS regions. A NetApp solution is used for Workspace Data Storage.
To improve IT Infra resilience, organisations wish to locate a Disaster Recovery centre in one of the AWS regions other than their primary region. Specifically the Disaster Recovery is to provide a warm standby resource for NetApp data storage.
The sketch below is a high level design diagram of a DR (Disaster Recovery) implementation in between different AWS regions:
In the primary region NetApps ONTAP solution was running in one of VPC, for implementing disaster recovery in another AWS region, new VPC was created and ONTAP solution was deployed. To provide connectivity between primary VPC and disaster recovery VPC, both of the VPCs are peered with each other through transit gateway peering and a route has been established in between both of them.
All five pillars of AWS well architected framework were followed during implementation, as per operational excellency pillar all the changes are made with infrastructure as code, as per security pillar only traffic from specific subnet was allowed in disaster recovery VPC from primary VPC and vice versa. As per reliability pillar all changes are tested before synchronization of actual data between both of the regions. As per performance layer and cost optimization we have used the inter region VPC peering through transit gateway peering for high network throughput and cost efficiency instead of using already deployed Cisco CSR.
A low level implementation of the design is shown in the below diagram:
