Perform a restore periodically
Data backup is critical to recover from large disasters. Test and evaluate your backup and restore strategy regularly.
Test your restores in order to verify:
This is one of the most common reasons that backups and restores fail, and one that has nothing to do with your software. This is particularly common when using tape, CD or DVD media. Make sure you follow the proper precautions for storing this media and remember that some media has a use-by date.
Running a test restore is the quickest way to make sure your media is totally functional and storing your data properly.
Human error is one of the primary cause for restore failures. Restore media can be incorrectly labelled, stored in the wrong place, some servers might have been excluded, and critical services fail due to incorrect configuration.
By running a test restore, not only do you double-check the job was completed properly, it’s a great exercise in disaster rehearsal. You want to be familiar with the process to cut down on downtime.
Restores require an enormous amount of disk sapce, as often, you need to be able to replicate the data of an entire machine, while keeping the original ifnormation. A restore test will make you aware of your storage limitations and impact of the restore.
Time needed to Restore
Network Performance, Connectivity, performance of the backup server and media all impact the time it takes to restore a Server / Service to it's backup up state.
Periodically performing restore tests can help you evaluate your Recovery Time Objective, and evaluate if needed.
Backup and Restore of Services do not always rely on the same permission sets. Backup Services can lack the permissions neccessary to make a copy of all the data, and the restore of e.g. a Database can fail, due to incorrect permissions.
Restoring a backup regularly can help you evaluate permission needed for both backup and restore.