Final Words and Exercises
- 23 Downloads
Every organization is different. For each one, the workload is varied based on how old it is, what industry is belongs to, its level of technical adoption, the type of customer data it handles, and length and breadth of its application portfolio. Depending on what DR means for each such type of organization, its unique application portfolio decides the solution it wants to adopt. Remember a disaster recovery solution is more than a technology product; it is a solution that is heavily process dependent. There should be adequate documentation and definition of what, how, who, and when to be able to recover a workload. In addition to coordination among various groups, the end-to-end process should be outlined and baked in as part of the DR solution. Most important, measure your confidence level on the solution. Will it work when you need it the most? Have you tested it enough end to end? Did all the parts come together well? Did everyone do what they needed to do? Are you detecting all the failures and exceptions? When do you trigger a DR? When do you take the call to do that seriously? Did your target environment recover during the planned RTO? Was application consistency achieved with the desired RPO? Challenges will be varied because this is a process and not the execution of technology.