- Posts: 13
- Liked: 1 time
- Joined: Feb 22, 2011 12:32 pm
- Full Name: Robbert Erents
VM's are replicated to a remote site containing an ESXi host with vCenter foundation. Replication is done with reversed incremental settings. A meteor hits the main office during replication. It is of less importance which version of the VM is available, just as long as there is a working machine to begin with.
During what period is disruption of VM replication resulting in replica corruption? Is there some mechanism that first sends the delta file to the remote site, and then commits the delta to the last reversed incemental replica version? If so, is the "Commit" just an execution command from the Veeam server and is that the only moment of vulnerability? Or is data committed to the reversed incremental replica version as soon as it hits the other side, and is the whole period that the job runs vulnerable to termination or time outs and is termination resulting in a corrupt replica?
If someone knows, could he/she please explain how the process of commiting the delta data works? Many thanks!
- SVP, Product Management
- Posts: 28521
- Liked: 5134 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
Here is one of the older topics I was able to find quickly > Veeam Server DR