An AI agent database cutover workflow adds checks, backups, and manual approval
tristanbob · x · 2026-07-25
The post describes using an AI agent to perform a database cutover with a heavy emphasis on safety.
What the agent checked before cutover
- Reachability, compatibility, versions, protocols, and authentication
- A live backup of the source database restored onto the new database
- Tests and checksums
- Human confirmation before proceeding
How the cutover was executed
- Stop the app using the database
- Verify all sessions had ended
- Take a cold backup and restore it to the new database
- Verify the restore in multiple ways
- Restart the app and confirm the database remained healthy
Why the author felt comfortable
- The full process was first run in a test environment
- The agent reused what it learned in production
- It saved logs, backups, and evidence for rollback
- Most importantly, it ran in manual approval mode so every command could be reviewed before execution
More from coding & agent
- Codex workflow tip: draw the flow first, then ask it to implement it — alex_frantic · 2026-07-25
- Microsoft’s OpenForgeRL trains agents inside the same harnesses they use in production — dair_ai · 2026-07-25
- Paper argues production agents fail from context overload, not reasoning — omarsar0 · 2026-07-25
- Gemini CLI fixes Windows diff views by normalizing CRLF to LF in a2a-server — luisfelipe-alt · 2026-07-25
- VaynerX says a $20,000 internal app was prototyped in hours with Claude — tomcrawshaw01 · 2026-07-25
- Researchers open-source a 1.6B-parameter Minecraft world model and code — heghbalz · 2026-07-25