Remove Architecture Remove Backup Remove Failover Remove Meeting
article thumbnail

Disaster Recovery (DR) Architecture on AWS, Part I: Strategies for Recovery in the Cloud

AWS Disaster Recovery

AWS offers resources and services to build a DR strategy that meets your business needs. All requests are now switched to be routed there in a process called “failover.” For tighter RTO/RPO objectives, the data is maintained live, and the infrastructure is fully or partially deployed in the recovery site before failover.

article thumbnail

Disaster Recovery (DR) Architecture on AWS, Part II: Backup and Restore with Rapid Recovery

AWS Disaster Recovery

DR strategies: Choosing backup and restore. As shown in Figure 1, backup and restore is associated with higher RTO (recovery time objective) and RPO (recovery point objective). However, backup and restore can still be the right strategy for your workload because it is the easiest and least expensive strategy to implement.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Trending Sources

article thumbnail

Disaster recovery with AWS managed services, Part 2: Multi-Region/backup and restore

AWS Disaster Recovery

In part two, we introduce a multi-Region backup and restore approach. Using a backup and restore strategy will safeguard applications and data against large-scale events as a cost-effective solution, but will result in longer downtimes and greater loss of data in the event of a disaster as compared to other strategies as shown in Figure 1.

article thumbnail

What’s New in Data Protection at HPE and Zerto: Updates and Releases for Q4 2023

Zerto

New capabilities include powerful tools to protect data and applications against ransomware and provide enhanced security with new Zerto for Azure architecture. I am excited to tell you about some of the latest updates to Zerto, HPE GreenLake for Disaster Recovery, and HPE GreenLake for Backup and Recovery.

article thumbnail

Disaster Recovery (DR) Architecture on AWS, Part IV: Multi-site Active/Active

AWS Disaster Recovery

My subsequent posts shared details on the backup and restore , pilot light, and warm standby active/passive strategies. The architecture in Figure 2 shows you how to use AWS Regions as your active sites, creating a multi-Region active/active architecture. I use Amazon DynamoDB for the example architecture in Figure 2.

article thumbnail

IT Resilience Within AWS Cloud, Part II: Architecture and Patterns

AWS Disaster Recovery

In Part II, we’ll provide technical considerations related to architecture and patterns for resilience in AWS Cloud. Considerations on architecture and patterns. Resilience is an overarching concern that is highly tied to other architecture attributes. Let’s evaluate architectural patterns that enable this capability.

article thumbnail

Journey to Adopt Cloud-Native Architecture Series: #3 – Improved Resilience and Standardized Observability

AWS Disaster Recovery

In this blog, we talk about architecture patterns to improve system resiliency, why observability matters, and how to build a holistic observability solution. Minimum business continuity for failover. Earlier, we were able to restore from the backup but wanted to improve availability further. Predictive scaling for EC2.