Most of us consultants probably can tell at least one story where database backup (or lack thereof) plays an important part in a sad story of an implementation that’s gone off-track.
The Types of Database Backup
With that in-mind, when I ran across this post that explains the different types of SQL Server database backup, thought it worth passing along as a number of readers of this blog are LIMS System Admins:
One comment someone made in one of the forum is to the effect of making sure that you can restore from your backup.
The Entire Procedure
This is critically important when you’re developing your backup procedure; don’t just create the procedure and take a backup – restore it, too. Restoration is part of your procedure. Run through EVERY STEP in your procedure. Don’t skip a step. Really! I mean it!!!
If you think I’m getting repetitive, it’s because people occasionally seem to assume you can restore what you backed-up. That’s not always true. And, if you have database admin rights, it’s not usually that difficult to create your own database to use as a place to restore your backup. Make sure it represents what you’ll actually restore to. If you’re going to be restoring to a live production database, don’t practice by making your test restoring only to a blank database.
Even if you’re buying off-site backup services, make sure you try them out to understand how they work. Also, keep in-mind that, if you switch services, there’s no guarantee that your backup copies from the current service can be used with other services as the tools might be different.