OCTom (8/22/2012)
Once the backup is in place, be sure to restore from it to test it out. There's nothing worse than having a backup plan and schedule to find out there's a problem when you need to restore. Having no backup is better than having one that you assume is working and it is not. Maybe the two are equally bad. :unsure:
Exactly, bad disk spots or database corruption can occur at any time and out of nowhere, so just testing your restore process once or twice is not good enough. Test it frequently and automate the restore process if you can. Particularly, if you are responsible for hundreds, if not thousands, of database backups..:-D
"Technology is a weird thing. It brings you great gifts with one hand, and it stabs you in the back with the other. ...:-D"