vCenter Migration Utility with Veeam v12.1

Did you read in this KB about the utility from VMware that can help preserve the ID? 

https://www.veeam.com/kb2136

Oh, sorry I got it now I did not notice the links below in that KB.

Thanks bro for your reply.

Unsure if it will work or not never used it.  Experimentation will be needed I think.

Some years ago, when we deployed for the very first time a VCSA instead of a windows based vCenter, we migrated data using a fling to do it, and we faced the same issue. We fixed it extracting the IDs of all the VMs from vcenter with powershell to a table and then modifying the Veeam database field for VM’s ID, matching VMs names….. probably it’s unsupported but it worked for us

Ok then my idea doesn’t work for that case. If you were on an older major release, you could have upgraded your VCSA which replaces the whole appliance instead of building a new one. As an alternative, have you tried to restore your existing vCenter configuration into a new appliance and then try to update it? 

I am not that sure if PowerShell Scripts can solve this case, but let me share the scripts that I will try it on Lab to figure it out and also if you have some comments or findings on these scripts as I am not that good with PowerShell yet it will be helpful.

1- Export the current list of VMs and their configurations from Veeam using PowerShell:

Get-VBRJob | ForEach-Object {
    $job = $_
    $vms = Get-VBRJobObject -Job $job
    $vms | Select-Object @{Name="JobName"; Expression={$job.Name}}, Name, Type, Path
} | Export-Csv -Path "C:\Backup\VeeamJobVMs.csv" -NoTypeInformation

2- automate the reconfiguration, use a PowerShell script to map old VMs to new VMs and update the Veeam jobs:

# Import the new vCenter
$newVC = Connect-VIServer -Server "new-vcenter.domain.com"

# Load the previously exported VM list
$oldVMList = Import-Csv -Path "C:\Backup\VeeamJobVMs.csv"

# Map old VMs to new VMs
$vmMapping = @{}
foreach ($oldVM in $oldVMList) {
    $newVM = Get-VM -Name $oldVM.Name -Server $newVC
    if ($newVM) {
        $vmMapping[$oldVM.Path] = $newVM
    }
}

Disconnect-VIServer -Server $newVC -Confirm:$false

# Connect to Veeam
Add-PSSnapin -Name VeeamPSSnapIn

# Iterate over each job and update VM references
foreach ($job in Get-VBRJob) {
    $jobObjects = Get-VBRJobObject -Job $job
    foreach ($jobObject in $jobObjects) {
        $oldPath = $jobObject.Path
        if ($vmMapping.ContainsKey($oldPath)) {
            $newVM = $vmMapping[$oldPath]
            Remove-VBRJobObject -Job $job -Object $jobObject -Confirm:$false
            Add-VBRViJobObject -Job $job -Entities $newVM
        }
    }
}

I will give it a try and let me know if you notice something too.

Thanks

For me it would be quite bad. With monster VM’s  and many 100’s of TB’s of data, takes a long time to backup. If I had to do a full backup on everything it takes an extremely long time.  The last time I did something like this I’d migrate 1 at a time and let the full run before moving on to the next. 

Sorry to hear the scripts did not work as it looked promising.  Hopefully someone will come out with a tool like the previous one that fixes this.

@Madi.Cristil @safiya - since it seems this thread does not have a true answer maybe we convert it to discussion instead of a question.