This is especially true of large DR resources it should be very easy to configure everything you need to do a full DR test in the cloud.

You just have to configure the appropriate resources in the cloud and then restore to those resources. The cloud has made all of this much easier, because you don’t have to fight for the resources to use for recovery.

A few times a year might be appropriate for a big DR test, but you should be restoring individual files and VMs at least once a week per person. The frequency of testing of each thing should be related to how often a restore of such a thing happens. This includes small things and very large things. You should regularly test the recovery of anything and everything you are responsible for. If they’ve done such a restore multitudinous times, they should just be able to follow their usual procedure. If the first time they’re executing a big restore is when they’re doing it in production, such a restore will be a much more stressful situation and more likely to be error prone. Regular recovery testing should be a fundamental part of your backup system.īesides testing the validity of the backup system and its documentation, regular testing also helps train your personnel. And the only way you’ll know whether you can restore the things you’re protecting is to test your ability to do so. There is no more basic concept of backup and recovery than to understand that the only reason we back up things is to be able to restore them.

Fbackup 4