your experience on full DR testing
hi
i have never been involved in a FULL disaster recovery test which involves a lot of parties so if you are involved in a FULL disaster recovery test before, can share your experiences...?
Some qns in my mind,
1) how long does it take on average to plan such BIG tests... in terms of years?
2) For 24x7 cases, like banks, how does one carry out such tests.. i believe the switch over mechanism must be very transparent and fast to the users involved..
3) what other experiences? thanks
Re: your experience on full DR testing
Quote:
Originally posted here by ghostmachine
hi
i have never been involved in a FULL disaster recovery test which involves a lot of parties ...
I like parties!
Oh, not that kind.
OK, FULL DRs are almost never completely tested. However, if your org has a warm or hot site, you can come pretty close by running tests to bringing up the warm or hot sites with live data --- then taking them back down. You can test DRs in increments using dry runs and scripts, as well.
If your DR plan is well defined and complete, you can plan and execute tests every six or 12 months. If you are starting from scratch with DR, you may be a couple years out before you are ready for any testing.
Of course, start with backup and restore testing. Validate your backups first. Make sure you can successfully restore. Yeah, your backup system does a nice job, and even verifies at the end of each job. Have you actually taken a volume backup and run a restore just to see if it restores?
Wanna know how good most of the backup system "verifies" are?
The stats ain't pretty.