Remove Architecture Remove Event Remove Failover
article thumbnail

The Storage Architecture Spectrum: Why “Shared-nothing” Means Nothing

Pure Storage

The Storage Architecture Spectrum: Why “Shared-nothing” Means Nothing by Pure Storage Blog This blog on the storage architecture spectrum is Part 2 of a five-part series diving into the claims of new data storage platforms. And just as important, why there is more to any product or platform than just architecture.

article thumbnail

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

AWS Disaster Recovery

This helps them prepare for disaster events, which is one of the biggest challenges they can face. Such events include natural disasters like earthquakes or floods, technical failures such as power or network loss, and human actions such as inadvertent or unauthorized modifications. Scope of impact for a disaster event.

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). The main traffic flows through the primary and the secondary Region acts as a recovery Region in case of a disaster event. This keeps RTO and RPO low.

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. Failover and cross-Region recovery with a multi-Region backup and restore strategy.

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. Decoupling integrations using event-driven design patterns. Predictive scaling for EC2. Centralized logging.

article thumbnail

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

AWS Disaster Recovery

Like other DR strategies, this enables your workload to remain available despite disaster events such as natural disasters, technical failures, or human actions. The architecture in Figure 2 shows you how to use AWS Regions as your active sites, creating a multi-Region active/active architecture. DR strategies.

article thumbnail

Time to Fight Back Against Ransomware: Zerto Will Show You How

Zerto

Through recovery operations such journal file-level restores (JFLR), move, failover test & live failover, Zerto can restore an application to a point in time prior to infection. Zerto pulls a “gold copy” of the infected VM initially backed up before the event to a repository. Get Your Files Back!

Failover 116