You DO backup your databases, don't you? And you do test your backups occasionally to make sure they're good, don't you?
One of my clients didn't, and they got bit hard recently. Thankfully it was “just” the test instance. But it set the QA department back several weeks, which then affects everyone's deadlines. Oh sure, they were doing regular nightly backups, but apparently nobody verified that the backups were usable. Then disaster struck, and the entire test environment was gone! The nightly backups weren't any good. The monthly backups weren't any good. And so on, all the way back to the Autumn of 2002. You might have noticed that I'm posting this in early 2004. That's a year and a half back they would have to go to recover, and then re-apply all updates made since that time. This would be a good place to argue that they'd be better off making a fresh QA instance from the production one, and that might be true, but in this case that's no easy chore either.
Regardless, all this pain and suffering could have been averted if they had had good backups. You can bet they do now.
posted @ Thursday, February 26, 2004 12:30 AM