FTF Veeam v6 Replication – Optimizing Snapshots
Fact is, if you want cost effective replicas of your VMs for disaster recovery fail-over using hypervisor based technologies you are about to ask your V.I. to “turn your head and cough”. Reliable, fast and efficient replication in a minimal window starts with providing good health in your storage, hosts, and virtual machines. You will probably have to make some changes to your architecture and design. As I’ve pointed out before, few planned and then actually built their virtual datacenter with a specific tool for disaster recovery in mind. The good news is that by optiizing snapshots you will probably fix many those nagging performance issues you’ve struggled with for a long time.
I know. I know. I and others have said in the past that snapshots in in your virtual datacenter are a bad idea. Well, the context of the discussion before was not to leave running snapshots open. That is not the context here. In fact, hypervisor based replication should never leave behind snapshots in your environment. Veeam Backup and Replication does not, nor do all of the other alternatives that I know about, leave behind snapshots. Sure, things can go wrong, but that is usually because of abnormal events in the environment (connectivity loss, Veeam architecture server reboots during jobs, etc). Things go wrong with snapshots without Veeam in the mix all the time. More on this later in the post.
BTW, Veeam is also smart enough to clean up left behind snaphots from previous jobs, and smart enough to leave a snapshot alone that Veeam did not create. There is never a “delete all” command issued to the hypervisor. If a snapshot already exists then Veeam does it thing with a new snapshot without touching the existing one.
To learn more and to read the entire article at its source, please refer to the following page, FTF Veeam v6 Replication – Optimizing Snapshots- VM /ETC – vmetc.com