MoREF Migration Tool Question

[pmichelli]

Good afternoon,

I have a situation where I need to re-IP my vCenter and ESXi hosts and also change the vLAN they live on. It was suggested by Broadcom to build new vCenters and move the hosts over as there are often challenges and problems with re-IP of vCenter server.

This will cause all the MoREF ID to change causing a full backup to start on every VM. I am concerned about not having sufficient storage left on my Data Domain to keep all my existing chains plus having to start them over / wait for enough restore points to purge the old one. So here is my question :

My Veeam VBR manages both Prod and DR vCenters in one instance. If I am migrating one DC at a time, can this tool be run pointing say to the DR instance to fix the IDs, then allow the backups to continue running in the current chains? Once I am satisfied DR is working ok, can I repeat the process with Prod? I may have interpreted the documentation that this can only be run once. I'm concerned if I do this in DR, I won't be able to do this again in Prod (Prod has 4x the VMs and uses a lot more storage).

I am happy to open a SR to get the steps ironed out if this is supported. Just let me know, happy to do so and post the SR here.

As always, thank you for your assistance

[Origin 2000]

I have re-IP and entire Organization a long time ago.... It is posible to change the IP of the VCSA. From the beginning we always use the FQHN when adding ESXi to vCenter and when connecting the vCenter to Veeam. So when working with Hostname rather than IPs you dont have these problems.
So think about your vCenter and when ever it possible you should avoid of creating a new one.

We also have a DataDomain. You can start to lowering the number of Retensionpoints to free up some data. Otherwise from a DD perspective it doesn matter if you store VM with a new MoRefID or and existing one. The DD doenst see a MoRefID... it will see Blocks and these will be the same as from last Week. So DD+Compression will kicks in as with a "normal" backup also.

What might be a problem if that Veeam checks the space on the DD and Veeam may think that the DD runs out of capacity or it will stopps working because of the DD reports not enough storage left.

Regards,
Joerg

[Andreas Neufert]

In you case, best option is to use the following: https://community.veeam.com/blogs-and-p ... -12-2-8714

This will then not create additional data in DD.
Even without correcting moref, as Origin 2000 stated the DD deduplication engine should reduce the data during intake so that you do not have any space issue. Devil is in the details as always.