Retaining historical data when hosts are migrated to vCentre

[mshin]

Hi,

I have a client who's going through vSphere migration into new vCentre.
Their plan is to build new vCentre (5.5) and migrate their 4.1 hosts into new vCentre by simply disconnecting from old vCentre and connect to new vCentre, and ESXi hosts will eventually be upgrade to vsphere 5.5 later down the track.
However, my understanding is when host is moved to new vCentre, VeeamOne will lose all historical data regarding the hosts and also the VMs sitting on them.
Is there any way of retaining those data throughout the process of host migration / upgrade?
We don't really care whether those historical data is coming from VeeamOne database or from vCentre. Default 180days worth of data that's kept in vCentre is sufficient.

We will be migrating all of them at same time, VeeamOne does not need to monitor both vCentres at same time.

Any help would be greatly appreciated.

[Vitaliy S.]

Hello,

Is there any way of retaining those data throughout the process of host migration / upgrade?
We don't really care whether those historical data is coming from VeeamOne database or from vCentre. Default 180days worth of data that's kept in vCentre is sufficient

.
When you re-register hosts in the vCenter Server all objects will receive new unique IDs, and they will be treated as "new" objects in the inventory. Can you do an in-place upgrade of the vCenter Server in order to preserve all the IDs? Do you use a remote SQL Server for your vCenter Server machine?

Thanks!

[mshin]

in-place upgrade of vCenter is unfortunately not an option for this particular client, and currently, vCenter database is local sqlexpress db in windows vCenter server.
Is there anyway to make change to VeeamOne database, like a script to modify old UUID of the object to newly assigned UUID to 'link' previous performance data to new objects?

Thanks

Michael

[Vitaliy S.]

Hi Michael,

I believe that not only the UUID should be changed, but most likely some other object references. As an alternative to the script you can keep your previous Veeam ONE database till it ages out based on the retention policy you have defined. In this case you should be able to use old data for historical reporting.

Thanks!

[borismittelmann]

Hi Guys,
I'd like to open this topic once again. As we're seeing more and more customers migrating VMs between vCenters (live or cold), perhaps it would be good to provide them some choice to keep, or reset VM history after migration. I understand the MoRef ID / UUID is generated new with each vCenter creation/registration, but surely we are able to find the way to track VM somehow to provide users with historical data.

Thanks.

[Vitaliy S.]

Yes, of course there is a way to track that, but currently this request is still pending due to other tasks with higher priority. Anyway, we'll keep an eye on these requests when planning new features.