![veeam orchestrator veeam orchestrator](https://vzilla.co.uk/wp-content/uploads/2018/08/082718_1520_Intelligent3.png)
This is so we can transfer the minimum data across the network to bring the source VM up-to-date with current state. However for your questions let's consider just the main 2 above)ĭuring failback we will compare the disk contents of the replica with the disk contents of original source VM. (there are other options, such as Undo failover, Permanent failover, Commit failback etc which add more flexibility.
![veeam orchestrator veeam orchestrator](https://nolabnoparty.com/wp-content/uploads/2018/04/veeam-orchestrator-setup-19.jpg)
What I would like to find out is how Veeam fares in that situation. The problem arises when the VM in question is 4 TB - this checksum activity takes around 6 or so hours no data is being copied across the WAN link, its purely ensuring the VMDK is valid. However, as part of it's reprotection steps, the reverse replication requires a delta checksum is performed on the underlying VMDK as the "new" protected VM now exists in DR with its failover counterpart in PROD. I failed over from PROD to DR without any problem. SRM works a treat for my client, generally speaking.
![veeam orchestrator veeam orchestrator](https://image.slidesharecdn.com/sis2018veeam-180314065810/95/rethink-veeam-availability-platform-2-638.jpg)
Probably best to give a slight overview of the issue. In regards to Veeam Backup, this is required as the current solution is not suited to the Enterprise.īeing a complete newcomer to this, I can only compare it to SRM, so apologies in advance. I understand that they would like to replace VMware SRM with the Veeam solution, which looks to be using Availability Orchestrator. So I am working for a client that is interested in using Veeam for Backup and Replication, which will be used in order to recover in a DR situation. New to the Forum, and to Veeam AO, so please excuse the newbie questions.