After testing for timing, management deemed that the plan met all business
requirements.We documented the plan fully and meticulously with each step, with the
understanding that server support staff may be the ones executing the restore plan.
(If you happen to notice potential issues already, good for you!)
The Result
I was teaching a SQL Server 2005 class in a city far from my home base when around
8 p.m. I got a call on my cell from a member of the server staff. While replacing a server,
the primary application database ???wouldn??™t come up.??? Of course, the staff member didn??™t
remember seeing any specific error message or database state. He informed me that
they??™d begun the restore procedure and asked if I could check in later that night and
apply the additional backups.
???No problem,??? I responded.
I was wrong??”it turned out to be a problem.
What Went Wrong
The first thing I discovered was lost data. I forgot to include a crucial piece of information
in the documentation I put together: the tail-log backup. That was the first mistake. Since
the on-staff DBAs and I always backed up the tail of the log out of habit, I just missed that
step in the documentation.
Pages:
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516