Veeam V11 and Moref id migration tool

[FrenchBlue]

Hi,

Not at the moment, but colleagues have this kind of requirements, and I know I will need it sooner or later

[FrenchBlue]

Hello,

Not at the moment but it will happen sooner or later, and I've seen colleagues needing this too.

[GianlucaCroci]

Hello,

good news about the migration utility "coming back to life".

I've never used this utility in the past and I thought this utility was only for changing the BIOS_UUID of a VM inside Veeam, and not for migrating a VM from one Vcenter to another.

I've some questions (after reading the PDF guide):

• in the step 2 it's written to rename the old VCenter in Veeam Backup Database

  Code: Select all

  To perform the migration, do the following:
    1. Update Existing VMs BIOS_UUID.
    2. Rename Old vCenter in Veeam Backup Database.
    3. Prepare a Migration Task File.
    4. Review and Customize the Migration Task File.
    5. Perform the Migration.
    6. Finish the Migration.

  and in the "Considerations and Limitations" it's written that after migration the old Vcenter can't be use anymore

  Code: Select all

  Old vCenter must not be used by Veeam Backup & Replication after migration.

  this only to avoid saving one or more VMs with the same BIOS_UUID from two different VCenters?
  Because if so, FOR US once a VM is migrated, we will put the NO_BACKUP TAG on the VM on the old VCenter. So the VM will be backuped only from one VCenter, even if it’s present on two.
  Can we skip this point?

• Also, since we've more than 800 VMs, we would like to migrate only 30-40 machines per day.
  Can the migration list be customized to migrate only the desired VMs?

thanks in advance for the reply.

[FrenchBlue]

Hi, the answer to the last question is a few updates before in the thread: no.

[Seve CH]

Hi

I didn't use the new version yet, but the old one allowed staged migration. We had both vCenters running and configured in VBR for almost a year until we managed to migrate everything and decommission the old vCenter.

The key step is the number 4: Review and Customize the Migration Task file.

With the old version, it was possible to remove the VMs you didn't want to migrate. I assume the new one should be similar (mapping list of old VMs to new VMs).
This is how we did it

FOR US once a VM is migrated, we will put the NO_BACKUP TAG on the VM on the old VCenter

But note: As already said in this thread, backup chain mapping is tricky and can lead to bad backups and a world of pain. If you copy or clone the VM in your migration, it is no longer the same VM -> Full backup. Before reenabling the jobs, the VM should be registered in one vCenter only. I doubt excluding the VM from a job would be enough.