Remove Architecture Remove Backup Remove Whitepaper
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

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.

Insiders

Sign Up for our Newsletter

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

article thumbnail

Types of Backup: Select Wisely to Avoid Costly Data Loss

Zerto

Backup technology has existed as long as data has needed to be recovered. We’ve seen countless iterations of backup solutions, media types, and ways of storing backup data. This last decade, many new backup tools have come out. Backup Appliances. Software-based Backup.

Backup 98
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

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

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