Remove Account Manager Remove Backup Remove Failover
article thumbnail

Disaster Recovery Solutions with AWS-Managed Services, Part 3: Multi-Site Active/Passive

AWS Disaster Recovery

Welcome to the third post of a multi-part series that addresses disaster recovery (DR) strategies with the use of AWS-managed services to align with customer requirements of performance, cost, and compliance. You would just need to create the records and specify failover for the routing policy.

article thumbnail

Using Route 53 Private Hosted Zones for Cross-account Multi-region Architectures

AWS Disaster Recovery

This post was co-written by Anandprasanna Gaitonde, AWS Solutions Architect and John Bickle, Senior Technical Account Manager, AWS Enterprise Support. Many AWS customers have internal business applications spread over multiple AWS accounts and on-premises to support different business units. Introduction. Considerations.

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

Minimum business continuity for failover. Earlier, we were able to restore from the backup but wanted to improve availability further. We built a pilot light using point-in-time backups for data stores, cross-Region Amazon RDS read replicas , cross-Region Amazon S3 replication , and AWS CloudFormation templates.

article thumbnail

VMware vs. OpenStack: Choosing the Right Cloud Management Solution

Pure Storage

It allows for dynamic provisioning, snapshotting, and the management of different storage backends. It’s ideal for managing large volumes of unstructured data (e.g., media files, backups) with high durability and availability. Object storage: Swift is OpenStack’s distributed object storage system.