CuraDevOps

tag: Disaster-Recovery · 8 items

2026-10-15 · Azure Updates · source ↗ #azure#disaster-recovery#arc
  • Platform/SRE — Plan: If you manage ARC-enabled VMware or physical Windows servers, evaluate adding ASR for disaster recovery coverage this quarter — this closes a gap for hybrid infrastructure protection.
  • CI/CD — Skip
  • Leader — Learn: ASR support for ARC-managed on-premise workloads expands Azure’s hybrid DR story; worth noting if the org is evaluating or expanding ARC adoption for governance of on-premise fleets.
  • Signals: GA announcement
2026-10-15 · AWS What's New · source ↗ #disaster-recovery#aws-arc#multi-region
  • Platform/SRE — Plan: The new service quota parity checks and wait-for-target-group-health blocks directly address common multi-region failover failure modes; platform teams using ARC Region switch should evaluate updating their recovery plans to incorporate these execution blocks this quarter.
  • CI/CD — Skip
  • Leader — Skip
2026-09-25 · Azure Updates · source ↗ #azure#vm-backup#disaster-recovery
  • Platform/SRE — Plan: New GA Azure capability enabling immediate disk restoration from application-consistent restore points on VMs with Premium v2 or Ultra data disks; evaluate adopting Instant Access in DR runbooks to reduce RTO for high-performance storage workloads.
  • CI/CD — Skip
  • Leader — Skip
  • Signals: GA announcement
  • Platform/SRE — Learn: Practical DR scenarios covering the gap between having backups and actually recovering — worth reviewing to pressure-test existing runbooks, but no deadline or current-production gap forces immediate action.
  • CI/CD — Skip
  • Leader — Skip
  • Platform/SRE — Learn: Relevant if you’re designing DR for workloads in Bangkok, Malaysia, New Zealand, Taipei, Calgary, or Mexico Central — DRS is now available in 36 regions, which may enable in-region DR targets previously requiring cross-region routing.
  • CI/CD — Skip
  • Leader — Learn: If the org has data-residency or latency requirements for any of these six new regions, this expands DR options worth noting in a future architecture review — no immediate decision required.
2026-07-16 · AWS What's New · source ↗ #disaster-recovery#aws#ec2
  • Platform/SRE — Plan: If you use AWS DRS for EC2 workloads, enabling this feature can meaningfully shrink your RTO with no added cost — evaluate enabling it account-wide or per server during your next DR review.
  • CI/CD — Skip
  • Leader — Learn: A no-cost RTO improvement of up to 65% on EC2 disaster recovery is worth noting when reviewing reliability targets and DR posture with engineering leadership.
  • Platform/SRE — Learn: Useful operational improvement for teams running Redshift Serverless with zero-ETL or S3 event integrations — snapshot restores within the same namespace no longer break integrations. No deadline or migration action required.
  • CI/CD — Skip
  • Leader — Skip
2026-07-15 · AWS What's New · source ↗ #aws#disaster-recovery#ebs
  • Platform/SRE — Plan: Teams running I/O-intensive workloads (databases, etc.) on AWS DRS should evaluate setting an EBS initialization rate on DRS launch templates to reduce time-to-full-performance during recovery drills — no deadline, but worth scheduling as a DR configuration review this quarter.
  • CI/CD — Skip
  • Leader — Skip