vCenter Migration Toolkit and Veeam

[DGrinev]

Hi Tom,

Veeam is using the MorefIDs provided by vCenter, thus the VMware migration utility preserves the same MorefIDs.
In case of failure, you can contact the support team and ask for assistance, however, according to the users and our own experience the VMware migration tool is stable in the most recent versions.

[Tomsyr]

Great - thanks for the feedback. How can I identify the MoreFID's in Veeam? I captured it all from the VCenter servers.

[DGrinev]

There is no way you can obtain MorefIDs in Veeam GUI.
All IDs are stored in the database. Thanks!

[paulfry6393]

I have read thru the forum posts and don’t see one that matches our strategy. We have old Windows vcenter and new VCSA together in Vsphere (both are 6.0). We will be using Enhanced Link Mode to do a compute migrate of VM’s from old to new. From what I read in the migration utility I can use the utility to locate VM’s that have moved (we are doing it in phases), check the txt file then run the migration utility for real to update to the new vcenter name on just the VM’s that have moved. Will this approach work and is doing a phased approach OK?

[foggy]

Hi Paul, please reveiw these considerations and feel free to contact technical support for assistance. Thanks!

[jim3cantos]

Hi, we are planning to migrate ours servers from ESX 5.1 (with VCSA in 5.5) to ESX 6.5U1. It's seems that we have to migrate first ESX hosts to 5.5. After that, we want to migrate VCSA 5.5 to VCSA 6.5 using the standard upgrade procedure. Can anyone confirm that this way existing VM MoRef IDs are going to be preserved or do we have to use Veeam vCenter Migration Utility instead?

thanks

[jim3cantos]

I can't quote myself... From what I read in this thread, can I presume that existing VM MoRef IDs are going to be preserved?

[foggy]

Hi José, during the standard upgrade procedure with native tools, IDs should be preserved.

[ddelly]

Old Production host
HP PROLIANT DL380 G7 / 64GB RAM / 8TB SAS Storage Array
VMWare ESXi 5.0 / VMWare vCenter 5.5 (VCSA)
Backup Server (off site location) is identical
A Local storage Array is used for daily local VEEAM Backup of our VMs...
Most VM replications are made from the local VEEAM backups

Just Purchased a new ESXi production host.
DELL PowerEdge R640 Server / DELL Dell EMC ME4012 Storage
ESXi 6.5 / VMWare vCenter 6.5 (VCSA)
Backup server will remain the same

Can you advise on the implications of transitioning to a new server with a later version of ESXi on the current VM backups and replications.
Would all current Replications have to be rebuilt? ( i.e. taking extra time to re-ingest from scratch) The concert is mainly about the off site location.
WIthin my VEEAM jobs, if the pathway to the host is via the VCSA is it recommended to retain the same IP Address as the old vCenter?

Hopefully someone has made a similar transition recently..
Much thanks for the help guys!

[DGrinev]

Hi Nassau,

In case you're going to migrate all the virtual infrastructure from VCSA 5.5 to 6.5 by native toolkit, all the morefIDs will be preserved, thus backups and replications should run without changes after the relocation.
Please review this discussion as it contains useful information regarding migration. Thanks!

[ddelly]

Hi, DGrinev --- I didn't see a link to the discussion you referred to... can you re-send please. Thanks for responding!

[Gostev]

He means this forum thread as a whole (the one that your post got merged with). Thanks!

[DonZoomik]

Due to various reasons I need to redeploy several VCSAs (6.7 -> 6.7) while also consolidating several Veeam instances. Currenty 3 environments are totally separated.
Does vCenter Migration Utility work with Veeam v10 and VCSA 6.7?

Plan:
At start there are three VCSAs (lets call them VCSA1-3, all 6.7) and 3 separate Veeam systems (Veeam1-3, all 9.5u4). Also there's a new Veeam instance (VeeamNew, v10) planned to service all 3 VCSAs.
Add VCSA1 to VeeamNew. Recreate all jobs, new chains on new hardware
Retire Veeam1
Redeploy VCSA1, use migration tool to migrate MoRef ID
Disable/remove Veeam2 (Veeam server and repo on same box), Add VCSA2 to VeeamNew, Recreate Veeam2's jobs, map to existing chains.
Redeploy VCSA2, use migration tool to migrate MoRef ID
Disable/remove Veeam2 (Veeam server and repo on same box), Add VCSA3 to VeeamNew, Recreate Veeam3's jobs, map to existing chains.
Redeploy VCSA3, use migration tool to migrate MoRef ID

[DonZoomik]

It seems that it's no longer supported and the only way is to edit the database directly?
vmware-vsphere-f24/migrating-esx-hosts- ... 61681.html

[foggy]

Or use the migration software from VMware.

[DonZoomik]

This VMware migration software is only for Windows to VCSA migrations or am I misunderstanding something?

[foggy]

Aren't there built-in configuration backup/restore capabilities in VCSA?

[DonZoomik]

That's good for reinstall, I was planning more of a full rebuild due to many changes related to some large restructuring.

[foggy]

Got it. But still, you need to somehow preserve the IDs from the older instance.