Remove Architecture Remove Backup Remove Capacity Remove Whitepaper
article thumbnail

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

AWS Disaster Recovery

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.

article thumbnail

Pure Storage Veeam Plugin

Pure Storage

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
Insiders

Sign Up for our Newsletter

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

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 III: Pilot Light and Warm Standby

AWS Disaster Recovery

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.