We’ve all been there. We’ve had to restore something and our backup solution didn’t meet our needs as we had expected. At Veeam, we are all about virtualization and we’ve seen a few traps along the way. Here are five things you should NOT do with VM backups:
- Do not forget to protect new VMs. Virtual environments grow, sometimes quicker than we would like. Make sure your backups run at the container level (host, datastore, vApp, SCVMM cluster).
- Do not forget the 3-2-1 rule. Keep three different copies of your data on two different media, one of which is off-site. This is a timeless rule that can address about any protection and failure scenario. By the way, this is made easy with Veeam Backup & Replication v7.
- Do not forget what your restore options are. Sometimes you need a little, sometimes you need a lot. Why restore an entire VM if you only need a file? With Veeam, we can deliver 26 restore scenarios from one agentless backup.
- Do not omit critical metadata from backups. With a Hyper-V VM, there are critical pieces of information (including XML data and a UID) associated with the VM. Is that restored? Using vCloud Director? Are you protecting the vApp metadata? Here’s a tip: Veeam can help you with this.
- Do not skimp on backup storage. We live in a world where the expectations are high, including restore time. Let’s put some real storage in place for backups and restores.