Hi.
I am new to Veeam and just been testing out Backup & replication 4.0
Quick question.
The documentation states: "Unlike competitive solutions, Veeam Backup & Replication does not require that replicated VMs run with open snapshots that prevent Live Migration and DRS."
I have found there is always an open snapshot while the replication job is taking place.
My replication job is a XP VM between 2 ESX 4.0 hosts connected over a VPN (using vStorage API Network mode)
Thanks
-
- Influencer
- Posts: 24
- Liked: never
- Joined: Nov 10, 2009 12:04 pm
- Full Name: Reilly
- Contact:
-
- Enthusiast
- Posts: 73
- Liked: 5 times
- Joined: Feb 18, 2009 10:05 pm
- Contact:
Re: Backup & Replication 4.0 Replication Snapshots
The snapshot is open during replication indeed, which should be quite fast considering usage of vstorage API. So most of the time, you are not bothered by a snapshot.
-
- Chief Product Officer
- Posts: 31780
- Liked: 7280 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: Backup & Replication 4.0 Replication Snapshots
Correct. DoubleTake or Vizioncore require that the source VM runs with open snapshots all the time (both periodically replicate the snapshot files to target, and merge them into the replica VMDK). With Veeam however, VM has snapshot for only few minutes (during each replication cycle), so most of the time, VM remains "clean".
Having snapshot open all the time obviously also requires a lot of disk space on source, and affects VM performance, especially during snapshot management procedures. Imagine periodic daily replication, every day there is a need to commit the snapshot to source the VM, and snapshot can grow very large for 24 hours.
To be fair, besides all the above-mentioned drawbacks this mode has certain benefits too on ESX 3.5 (faster incrementals comparing to Veeam v3 approach). But with vSphere and Veeam v4, our incrementals became are comparable and even faster due to the ESX4 changed block tracking.
Having snapshot open all the time obviously also requires a lot of disk space on source, and affects VM performance, especially during snapshot management procedures. Imagine periodic daily replication, every day there is a need to commit the snapshot to source the VM, and snapshot can grow very large for 24 hours.
To be fair, besides all the above-mentioned drawbacks this mode has certain benefits too on ESX 3.5 (faster incrementals comparing to Veeam v3 approach). But with vSphere and Veeam v4, our incrementals became are comparable and even faster due to the ESX4 changed block tracking.
Who is online
Users browsing this forum: AdsBot [Google], Google [Bot] and 108 guests