Okay, so you've got your database backup cycling every 24 hours right? Maybe even 12 hours- man, you don't want to lose ANY data in a restore, do you?
What happens if a backup goes by before you find out about the error?
That just happened to me. I started noticing strange errors and spent nearly a day figuring out what was happening. Then I discovered I had accidently deleted rows in a table I THOUGHT was a testbed table - but it was the live table. Oops!![[sadeyes]](/data/assets/smilies/sadeyes.gif "[sadeyes] [sadeyes]")
Restored the DB. The data was still missing! My debugging skills weren't fast enough. I needed to restore from the day prior, but it wasn't there anymore, because I only had one file available: the most recent backup.
Lesson learned: keep your most recent backup, and one from five days ago, and maybe 10 days ago, too. You never know what data you will need in a restore!
What happens if a backup goes by before you find out about the error?
That just happened to me. I started noticing strange errors and spent nearly a day figuring out what was happening. Then I discovered I had accidently deleted rows in a table I THOUGHT was a testbed table - but it was the live table. Oops!
Restored the DB. The data was still missing! My debugging skills weren't fast enough. I needed to restore from the day prior, but it wasn't there anymore, because I only had one file available: the most recent backup.
Lesson learned: keep your most recent backup, and one from five days ago, and maybe 10 days ago, too. You never know what data you will need in a restore!