> 2) For piddly stuff like this, gbak should be able to just warn me and carry on. There is no way a seemingly good back up should ever be un-restorable (barring corrupt media). At some point, you just have to accept that the data isn't as clean as it should be and get on with the job at hand, which is restoring the database. I've lost track of the number of times I have tried to recover from a back up only to find out that the back up is un-restorable for some silly reason and had to resort to writing a bunch of tools to piece the database back together. Not fun!
>

yeah that is not perfect, not fun. But AFAIK, is very *well* documented that you *have to* test your backup after created it. Right?