The nightmare scenario. We have an automated backup system for our accounting software. Up until now, this system would check once a day for any changes in the database. And if there were any, it would save that day's database over the previous day's database, as a "backup." Anyone see any problems with this approach. Well, we didn't really either, until aforementioned nightmare scenario. A weekend corruption!

Over the weekend, for reasons we can't put our finger on, the software dumped a WHOLE BUNCH of data-like all of our payroll history, all of our receivables, some of or long-term assets, and some of our long-term liabilities, and our checking accounts. Software just FORGOT that stuff existed. This happened on a weekend. And, when the system did its automatic check for changes in the database, it detected the change, and saved the corrupted database right over the accurate database from Friday afternoon. Imagine our surprise, when we came into the office yesterday (Monday).

We called technical support. They were pretty technical, but not very supportive. The net of their assistance was, "Well, dude, if the data's gone, it's gone. Nothin' I can do about it."

But, by the grace of God, Anne had done a backup back at the beginning of January. So, instead of having to cobble together more than a year's worth of data, we only had to cobble together about a month. We went to work tracking down job records, purchase orders, estimates, payables, receivables, client payments, checks, and deposit records. Props to Vivian for pitching in after hours yesterday. It's been about 35 hours since the crash was first discovered, and we're well on our way to recovery.

James says that we should "count it all joy." And this has certainly been a growth experience. And thanks to the Lord, it was a lot less awful than it could have been. Still, I would rather not go through it again.

By the way, we're changing our backup approach.