Hi
We're moving a number of 10TB SQL Server (large delta's) to a new environment using VEEAM Replication. Also converting the disk from thin to thick. So we do one replication, remove the replica job, convert the disk, create a new replica job WITH seeding and do a mapping to the previously created replica.
We've had some failures in this process when there turned out to be not enough space left on the CSV volumes and the replication would fail. Assign some more space to the CSV and then to find out that in the retry, VEEAM decided to create a new copy of the VM on that same CSV, but not always. I can't fully understand when and why the seed is used as target and sometimes a new VM is created.
Anyone know the internal decision process that the replication job goes through?
-
- Expert
- Posts: 244
- Liked: 37 times
- Joined: Jun 15, 2009 10:49 am
- Full Name: Gabrie van Zanten
- Contact:
-
- Veteran
- Posts: 3077
- Liked: 453 times
- Joined: Aug 07, 2018 3:11 pm
- Full Name: Fedor Maslov
- Contact:
Re: Mapping / seeding creates a new VM
Hi Gabrie,
This is definitely not the expected behavior. What B&R version is it? I'm asking because in U4 we introduced several improvements for this scenario - the job should fail if it was unable to find the mapped VM. It might be a good idea to look at the details with our support team.
Thanks,
Fedor
This is definitely not the expected behavior. What B&R version is it? I'm asking because in U4 we introduced several improvements for this scenario - the job should fail if it was unable to find the mapped VM. It might be a good idea to look at the details with our support team.
Thanks,
Fedor
Who is online
Users browsing this forum: No registered users and 22 guests