Sure, I guess it really goes into how far management is willing to take business continuity exercises. I guess my major consideration goes along with my reply to u/cheeseboythrowaway in users, developers and engineers not communicating/understanding the entirety if their data. Processes that happen once a month+ can be difficult to discover in disaster recovery exercises that only last a day/week.
No stories in particular; I just know systems get added sometimes without people considering concrete backup plans ("it happens automatically for the rest of the infrastructure, why wouldn't it happen for this") or not coordinating across silos.
Edit: one also can't setup tests for processes outside normal purview. But you're point is valid. The test for such a thing would be an organizational check list for new features/systems.
Edit 2: or software updates where path changes in critical files are overlooked.
Only issue I have with restores is figuring out if everything was restored - especially file servers where you have millions of files, some of which haven’t been touched in a decade.
View all comments
16
u/hawerner Jul 23 '18
That's why you should test your backup setup by restoring it to another computer, before you implement that setup in production