I run a disaster test scenario at least once a quarter where I restore the database of mission critical components as though we were starting from scratch.
It's taught me three things:
1. Restoring a database is a lot more complicated than simply unzipping a file and importing it into a database program.
2. You inevitably forget things, so build a comprehensive checklist.
3. Database imports take longer than you think with full production data.
Practice makes perfect in disaster recovery.
Sarah Savage /
npub1jt…cap3r
2024-05-24 13:24:01
Author Public Key
npub1jtxf0l4nu4jsjz44ldwllej0ufc2e3rvmsxfq82yfay2f7ph2elsxcap3rPublished at
2024-05-24 13:24:01Event JSON
{
"id": "eca9f068810027fab4eb8a32f60e73862212b76c49a1a66120943a523b441e05",
"pubkey": "92cc97feb3e565090ab5fb5dffe64fe270acc46cdc0c901d444f48a4f837567f",
"created_at": 1716557041,
"kind": 1,
"tags": [
[
"proxy",
"https://phpc.social/users/sarah/statuses/112496282293983021",
"activitypub"
]
],
"content": "I run a disaster test scenario at least once a quarter where I restore the database of mission critical components as though we were starting from scratch.\n\nIt's taught me three things:\n\n1. Restoring a database is a lot more complicated than simply unzipping a file and importing it into a database program.\n2. You inevitably forget things, so build a comprehensive checklist.\n3. Database imports take longer than you think with full production data.\n\nPractice makes perfect in disaster recovery.",
"sig": "c1c4d99fc3f7e67582e47b4d032e0d660e18d17a137cd4a8e52e010b166c278318476475585f5e38bc2782ac9c02950c1bcd47576a19440ee1ed9179ccbb69dc"
}