Automating Disaster Recovery with Aura API
summary
Altrata automates Neo4j disaster recovery on Aura by wrapping the Aura API into one-click workflows: a GitHub Actions flow lists hourly snapshots, runs an authenticated snapshot restore for production, and enforces approval gates and audit logs. For DR they resume a paused replica to save cost, then use the resume endpoint plus polling and an instance overwrite endpoint to copy a snapshot across. The graph is large—about 9 million nodes and 700 million relationships—while Datadog metrics and LaunchDarkly feature flags trigger a kill‑switch and automated failover.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 0:25Disaster recovery scenarios
- 3:38Automating snapshot restores
- 6:51Failover to DR instance
- 9:46Orchestrating DR workflow
- 11:54Kill switch for user experience
- 13:20Monitoring and automation
- 14:25Q&A and closing
related talks
30mNeo4j Product Vision and Roadmap
30mNeo4j Product Vision and Roadmap
46mAzure SQL Database Business Continuity During Disaster
31mAura Agents in Action
30mNeo4j Product Vision and Roadmap
25mAutomating Disaster Recovery: The Ultimate Reliability Challenge
54mSoaring to New Heights with Accelerated Database Recovery
27mAutomating for Failure: Disaster Recovery Testing with Terraform & Gremlin