Resposta de referência
My experience with disaster recovery planning has been pretty hands-on.
In my last role, I helped build and maintain the DR program for critical systems, not just the document itself, but the actual recovery process end to end. That included:
A big part of the job was working cross-functionally. I partnered with infrastructure, application owners, security, and business teams to figure out what truly needed to come back first, and what level of data loss was acceptable for each service.
I also put a lot of focus on testing, because a DR plan is only useful if it actually works under pressure. We ran regular tabletop exercises and recovery drills, then updated the plan based on gaps we found. That usually meant tightening procedures, clarifying ownership, or fixing dependencies that were missed the first time.
One example, we reviewed a recovery workflow for a key internal platform and found the documented process looked fine on paper, but in testing it depended on a manual step no one had clearly owned. We fixed the runbook, reassigned ownership, and adjusted the recovery sequence. That made the process much more reliable and cut expected recovery time significantly.
Overall, my DR experience is a mix of planning, coordination, testing, and continuous improvement, with a strong focus on making recovery practical, measurable, and repeatable.