If a restore scenario requires you
to retrieve a backup file from a tape library, you should test that also.
Yes, test is a four-letter word. No one likes to do it. I sure don??™t.
The point of testing is not simply to see if things work. A well-thought-out testing
plan should provide much more information than just success or failure. Performing a
test provides a mountain of information, in particular when the test fails. The best way to
learn is by making mistakes. Isn??™t it better to make those mistakes during a test run than
during a real disaster scenario? Consider these questions while performing a test:
CHAPTER 5 n CREATING A BACKUP/RECOVERY PLAN 137
??? Why did it work?
??? Why did it fail?
??? How long did the process take?
??? Were there any delays, and if so, why?
Another item that no one wants to hear: testing is a continual process. How often
should you review and test? Definitely not more frequently than quarterly, unless you??™re
actively experiencing problems with the plan. You should test at least once a year, and
preferably every six months, assuming things are running smoothly.
Pages:
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279