SQL Clone
SQLServerCentral is supported by Redgate
Log in  ::  Register  ::  Not logged in

Backups after a DR Restore – MCM

If you have a disaster, and you need to restore to some point in time prior to the last log backup you have, what’s the first thing you should do at this point in time?

Make a full backup, of course.

Actually anytime you complete a restore sequence, you want to do a full backup immediately before you turn users loose to do work. Why is that?

Think about what happens if you complete the restore and then have another issue? You would have to go through the entire restore sequence again from before the first disaster. If that were a full backup, a differential, and a dozen log backups, would you want to explain that delay to your boss again?

Would you even want to go through it?

I wouldn’t, and it’s easy to prevent. Once you get done with your restore, start a full backup right away. You might never need it, but then again, you probably said that about the full backup you just restored.

Filed under: Blog Tagged: Backup/Recovery, mcm, sql server, syndicated

The Voice of the DBA

Steve Jones is the editor of SQLServerCentral.com and visits a wide variety of data related topics in his daily editorial. Steve has spent years working as a DBA and general purpose Windows administrator, primarily working with SQL Server since it was ported from Sybase in 1990. You can follow Steve on Twitter at twitter.com/way0utwest


Posted by Dukagjin Maloku on 22 February 2011

Hey Steve, thanks for sharing your experience "In the road to MCM"! - Wish you more success!

Leave a Comment

Please register or log in to leave a comment.