Mark Berry November 14, 2016
This is a very instructive nightmare:
- Environment with fancy new VSS-aware hybrid local and cloud backup gets hit by crypto malware.
- Turns out backups are based on timestamps, which Pervasive/PSQL often doesn’t change. Only possibility is to go back to last server backup, five weeks prior.
- Backup was too big to save that long locally.
- Cloud backup was only retained for three weeks.
- Old server and its backups were recently scrapped.
- Customer had to re-install database and re-create data from scratch.
Note that it was no problem to get to the boot screen locally or in the cloud. They just couldn’t get a usable database.
- Seeing a boot screen does not mean the full machine is restorable.
- Restoring a couple random flat files is not an adequate disaster recovery test of a machine with a database.
- Database backups require separate planning and testing.VSS is not always enough.
The author has specific steps for testing and backing up PSQL, but the same principles apply to any database system.
Are your databases adequately protected?