Project Server backups: an untested backup does not count
Everyone backs up. Few check that they could restore. For a Project Server environment, that is the only test that matters.
Next restore test: January 15
A Project Server environment holds years of schedules, timesheets and history. Losing it means losing the projects' memory. Backups almost always exist. The question is whether they work.
What to back up
Project Server's databases, but also its configuration: custom fields, views, templates, permissions. A database restored without its configuration gives an environment that starts but that nobody recognizes.
Three moments to back up
- every night, automatically, with an alert if it fails;
- before every intervention: in our slow timesheets example, the indexes were only rebuilt after a verified backup;
- before every update or migration.
Test the restore
A backup is only worth something if you know how to restore it. Once a quarter, restore to a test environment and check that projects open, timesheets are there and permissions are right. It is the only way to be sure, before you need it.
Backup monitoring and restore tests are part of the maintenance we provide for Project Server environments.