These two failures are a 1-2 punch to the jaw of your career. Check every server’s job logs – I’ve seen so many cases where backups stopped working on a SQL Server, and alerting had also long ago stopped alerting.Ideally, check the ones that hit tape, because those are the most risky. Test your backups manually – if you don’t have the time to script the tests, just go run a restore of your largest backup.Restore a different server every day onto the same target testbed box. Automate your backup testing – build a set of T-SQL scripts to automatically restore your production databases onto another server.For the love of your own job, never mind your company’s revenue stream, take some time this week to: Who knew they were referring to their own services?ĭon’t point and laugh and say it could never happen to you because you do your own backups in-house, because I’ve seen too many backup strategies fail for too many reasons. Bogus equipment? You mean, like hard drives that fail? That’s horrible! Who could expect something like that? Who could know about the dangers that lurk around every corner? The Statistics are Staggering AlrightĬarbonite’s web site warns, “You need to be aware that losing your most valuable files is a very real possibility. They’re suing Promise Technology, makers of popular storage gear, for selling them bogus equipment.
TechCrunch reports that Carbonite, an online backup company, lost customer data.īut wait, this is different: it’s not their fault.