Great, thank you so much for reporting the solution.
- Service Provider
- Posts: 147
- Liked: 20 times
- Joined: Oct 28, 2010 10:55 pm
- Full Name: Ashley Watson
In our case I had completely forgotten about the VM exclusions - presumably because the VMs being excluded did not exist any more.
I guess prior to update 4, VMs that were not present that had been previously excluded were simply ignored by the replication job?
Also strangely I saw the replica VM on the target existing in two places - one under the replica folder on the target and another in the Discovered virtual machine folder - which does not make sense.
As this specific Veeam instance is for our development workloads, I have completely removed the target replicas from both the storage and from within Veeam and am now rerunning the replication to see if I can get a clean run through (this will take several hours).
It definitely sounds like there is some sort of regression bug/change in behavior that has been introduced with update 4 specifically concerning replicas.
- Veeam Software
- Posts: 23333
- Liked: 3033 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
Users browsing this forum: Bing [Bot] and 18 guests