December 10, 2012 at 8:28 pm
Comments posted to this topic are about the item Test Your Restores
December 11, 2012 at 2:49 am
I hit this problem yesterday with our first test of our disaster recovery solution: encryption no longer worked!
Once I'd figured out it was an issue to do with the Service Master Key on the new box I was ok, but still it was a bit of a "oh no!" moment.
And...back to the documentation 🙂
December 11, 2012 at 10:54 am
This is kind of like buying a car without test driving it first. Don't just assume everything works. Test drive those 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"
December 11, 2012 at 7:36 pm
I just keep repeating the mantra "no one has ever lost their job for failing to take a backup, only for failing to recover the application to the required state". I was caught recently where some backups from last year were needed to argue a legal case. The infrastructure team guaranteed that they had the data and went and ordered the relevant tapes from the off site storage. Low and behold all of the tapes were corrupt so there were no available back ups to restore. But that didn't frighten the infrastructure team into checking all other tapes, I had to force them via their manager and yes more and more of the tapes were found to be faulty, even though the back up software issued a "verified" status after the backup.
Always test your restores on a regular basis, and not just the local backups but also any business critical off site backups.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply