Remove Architecture Remove Backup Remove High Availability
article thumbnail

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

AWS Disaster Recovery

By using the best practices provided in the AWS Well-Architected Reliability Pillar whitepaper to design your DR strategy, your workloads can remain available despite disaster events such as natural disasters, technical failures, or human actions. DR strategies: Choosing backup and restore. Implementing backup and restore.

article thumbnail

Four Key Backup and Recovery Questions IT Must Ask During Deployment

Solutions Review

In this submission, Skytap Technical Product Evangelist Matthew Romero offers four key backup and recovery questions that IT teams must ask during deployment. There are a number of ways a robust DR/backup system can mitigate the harm of a ransomware attack. Setting up backups for a core business application is a complicated task.

Backup 105
Insiders

Sign Up for our Newsletter

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

article thumbnail

Implementing Multi-Region Disaster Recovery Using Event-Driven Architecture

AWS Disaster Recovery

In this blog post, we share a reference architecture that uses a multi-Region active/passive strategy to implement a hot standby strategy for disaster recovery (DR). This makes your infrastructure more resilient and highly available and allows business continuity with minimal impact on production workloads. This keeps RTO and RPO low.

article thumbnail

Using Route 53 Private Hosted Zones for Cross-account Multi-region Architectures

AWS Disaster Recovery

Route 53 Private Hosted Zones (PHZs) and Resolver endpoints on AWS create an architecture best practice for centralized DNS in hybrid cloud environment. This blog presents an architecture that provides a unified view of the DNS while allowing different AWS accounts to manage subdomains. Architecture Overview.

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. Earlier, we were able to restore from the backup but wanted to improve availability further. Current Architecture with improved resiliency and standardized observability.

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.