foggy wrote:Magnus, as mentioned above, you need to make sure the jobs from different backup servers targeting the same VM don't overlap, as this can cause conflicts.
Just did a test.
First I started a backup job of vm1 from vbr1. While that job was running I started a replica job of vm1 from vbr2. When both jobs where running there was 2 veeam snapshots on vm1 in vmware.
Backup job finished first and removed only one of the 2 snapshots. I verified with timestamps on snapshots that the backup job removed the correct snapshot. Backup job finished successful. When the replica job finished the last snatshot on vm1 was removed. Replica job finished also with success.
Only error I saw was when backup job finished. Veeam then saw that there was multiple snapshots on vm1 and tried to consolidate. But the consolidate failed with:
2016-01-05 10:01:44 Error Performing disk consolidation: VM1 on vcenter
2016-01-05 10:01:43 Performing soft consolidation failed: Disks consolidation failed for VM vm-31300: Unable to access file since it is locked
2016-01-05 10:01:46 Error Job finished with error at 2016-01-05 10:01:45
From my testing it seems like it would work even if backup job and replica jo would collide. Atleast the backup job and replica job will end up successful.
I will go ahead and run backup job and replica job of the same vm from 2 different vbr servers. But I won't take any risk and still specify fixed backup windows for backup and replica job so they don't collide.