AWS Disaster Recovery

APRIL 5, 2021

Figure 2 shows the four strategies for DR that are highlighted in the DR whitepaper. 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.

Disaster Recovery 101

Disaster Recovery Architecture Failover Backup 101

Pure Storage

JANUARY 10, 2024

The Benefits of Pure Storage Integration with Veeam Agent-less application consistent array-based snapshot backups Veeam coordinates the execution of API calls to the hypervisor and guest OS, like VADP and VSS, eliminating the need for agents to be installed on a VM. This is the bar both looked to build upon with our integration efforts.

Backup 52

Backup Capacity Architecture Application 52

AWS Disaster Recovery

APRIL 27, 2021

To meet these goals, we developed a long-term business continuity plan per the Disaster Recovery of Workloads on AWS: Recovery in the Cloud whitepaper that consisted of the following: We accepted data loss for the data that’s not persistent in the database. Centralized cross-account management with Cross-Region copy using AWS Backup.

Architecture 74

Architecture Resilience Backup Application 74

AWS Disaster Recovery

MAY 14, 2021

Then we explored the backup and restore strategy. In addition to replication, both strategies require you to create a continuous backup in the recovery Region. Backups are necessary to enable you to get back to the last known good state. The warm standby strategy deploys a functional stack, but at reduced capacity.

Disaster Recovery 58

Disaster Recovery Architecture Failover Activation 58