I finally finished restoring the full backup, then turned to apply the
differential backup. Much to my surprise, I received an error saying that the differential
backup was not associated with the full backup. I ended up having to restore each individual
transaction log backup, which took me until almost 6 a.m. to complete. Since
processing and replication weren??™t occurring, a bottleneck occurred once users came into
the office. It took until at least 3 p.m. before the application started responding in the
usual fashion. I later found out that a developer had taken a full backup to refresh the test
system just after 7 p.m. the night before. From that point on, every differential backup
was associated with the developer??™s backup. Oh, and the developer deleted the full
backup once it was restored onto the test system to conserve disk space, so I wouldn??™t
have been able to use it even if I??™d known about it.
How SQL Server 2005 Would Have Helped
My client had been running SQL Server 2000. Had the company been running SQL Server
2005 or higher, the following features would have helped significantly:
??? Tail-log: If the tail-log had been available for backup, SQL Server 2005 would have
given the server staff a warning to back up the tail-log before proceeding.
Pages:
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518