Remove Architecture Remove Backup Remove Capacity
article thumbnail

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

AWS Disaster Recovery

If data needs to be restored from backup, this can increase the recovery point (and data loss). If such a disaster results in deleted or corrupted data, it then requires use of point-in-time recovery from backup to a last known good state. Architecture of the DR strategies. Backup and restore. Pilot light DR architecture.

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.

Insiders

Sign Up for our Newsletter

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

article thumbnail

Backup and Disaster Recovery Strategy in the Era of Remote Work

Solutions Review

In this submission, Scality Co-Founder and CTO Giorgio Regni offers a commentary on backup and disaster recovery strategy in the new era of remote work. The shift to work-from-home and hybrid work models has put renewed focus on the importance of backup and disaster recovery plans. Backup and Recovery: The Impact of Remote Work.

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). With the multi-Region active/passive strategy, your workloads operate in primary and secondary Regions with full capacity. This keeps RTO and RPO low.

article thumbnail

Taming the Storage Sprawl: Simplify Your Life with Fan-in Replication for Snapshot Consolidation

Pure Storage

Before you know it, your fleet has become a many-headed monster of disparate storage arrays, with siloed data and a complex web of backup jobs. Fan-in unifies backup tasks, replication jobs, and access control under one roof, streamlining your workflow. Enter your knight in shining armor—snapshot consolidation via fan-in replication.

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