Backup and recovery for hybrid architectures

The cloud-native and on-premises deployments discussed in this guide can be combined into hybrid scenarios where the workload environment has on-premises and AWS infrastructure components. Resources, including web servers, application servers, monitoring servers, databases, and Microsoft Active Directory, are hosted either in the customer data center or on AWS. Applications that are running in the AWS Cloud are connected to applications that are running on premises.

This is becoming a common scenario for enterprise workloads. Many enterprises have data centers of their own and use AWS to augment capacity. These customer data centers are often connected to the AWS network by high-capacity network links. For example, with AWS Direct Connect, you can establish private, dedicated connectivity from your on-premises data center to AWS. This provides the bandwidth and consistent latency to upload data to the cloud for the purposes of data protection. It also provides consistent performance and latency for hybrid workloads. The following diagram provides one example of a hybrid environment approach.

Well-designed data protection solutions typically use a combination of the options described in the cloud-native and on-premises solutions in this guide. Many ISVs provide market leading backup and restore solutions for on-premises infrastructure and have expanded their solutions to support hybrid approaches.