2 ms·
You missed on from the list: Always make sure a recent backup has been tested in a meaningful way. At least have an automated restore scheduled, and have it re
by dspillett 13y ago
You missed on from the list: Always make sure a recent backup has been tested in a meaningful way.
At least have an automated restore scheduled, and have it report to you any error. Have that process run what-ever verification tools your DB supports to as this will catch some corruption that won't be seen in a simple restore.
Better still (though this is very app dependent so difficult to create general rules for) do some actual data verification. If you app keeps an audit trail, keep a copy of the last backup around and compare anything that should not have changed between them (as there are no relevant audit entries) still identical.
All this serves to increase the confidence that your backup will save you if/when disaster strikes.