We're going to implement Veeam Backup in our environment really soon now. Probably next week... We're also getting new vSphere hosts and a new SAN but those have been delayed, so we need to have Veeam backup the existing servers and then migrate to the new servers. We're currently using a remote backup solution based on TSM -
- and that's going to stop workong on March 31st, so we're in a hurry.
I would really like to set up a new vCenter for the new hosts and then move the old hosts to the new vCenter one by one, and use Storage vMotion to move the VM's to the new servers and SAN. That will generate UUID for the VM's and if we don't do anything then Veeam will see them as new VM's. I don't want that to happen, because that would quickly fill up our backup storage.
Is there a good workaround for this? Can anyone suggest a good way of doing this migration?