Sam,
Thanks for the input... However the point is that even if you force backups before posting you don't know you need to restore until you've done a verification and seen that it failed. At that point you have lost whatever work was done all the way back to the last backup that didn't contain the error.

So our current protocol is to run verifications before every posting so that we only have restore from the backup before. Otherwise if you did an end of day verification and found that something was damaged during that day, you'd have to incrementally restore each backup and test to see if you'd gone far enough back to be before the error occurred.

The problem with this is that it is time consuming to run a verification every time you post. And furthermore, regardless of how frequently you back up, doing a restore requires you to both identify and recreate your work since the last valid backup. The redoing of the work is just unfortunate, but the bigger issue is identifying what needs to be redone since you could be missing information.

*sigh*