The script mentioned wouldn't help. Anytime a host is registered to a new vCenter, all associated VMs get new IDs in inventory. These are the references Veeam uses to identify the VM in a job.
spgsit5upport wrote:So I edited the jobs, removing VMs & adding the same VMs from new vCenter
But strangely each job now runs as "new" taking no notice of what is already in repository
v.Eremin wrote:According to the case, your problem seems to be slightly different to the one discussed above. You don't want to move VMs to a new VC, but rather to change VC FQDN. Support team has PS solutions for both problems.
Anyway, I've asked the support engineer who is aware of the said solutions to take over your case.
Hope this helps.
Users browsing this forum: No registered users and 19 guests