vCenter Migration Utility for Veeam One

[Jamesdld23]

Hello,

we plan to migrate our vCenter to a new server, is there something similar than the vCenter Migration Utility for Veeam B&R in order to conserve my archived log data?

Thanks for helping

[Shestakov]

Hello James,
Your historical data will be preserved in Veeam ONE DB in accordance with the data retention rule.
No tool is needed.
Thanks!

[Jamesdld23]

Hello,

do you mean that I should conserve two vCenter servers in Veeam One console (the old and the new vCenter hostname)?
No way to fusion the data?

Thanks.

[Shestakov]

New vCenter is a different object and it will be incorrect to show other`s VC`s the historical data.
By the way, what kind of data are you interested in, events, VMs performance etc?
Thanks!

[Jamesdld23]

I am not sure to understand : we could not have two vCenters on Veeam One?
For your question : we have decided to have our Hypervisor performances retention only on Veeam One, we use it for auditing states during production operation & get capacity planning.

[Shestakov]

You can have several vCenters connected to Veeam ONE.
As I understood your request, you wanted to migrate performance data of one vCenter to another vCenter.
When you delete the object from Veeam ONE(VC, host, VM) all data is removed as well. If you migrate all VMs to the new vCenter Server, it will change their unique identifier (moref ID) and make Veeam ONE treat these VMs as new ones. In other words, it will not be possible to match historical performance data to the new VM instances anymore. I would recommend just keeping this database as a stand-by database for historical performance analyses.

[Jamesdld23]

Ok I understand.
Thank you for those precision.

[Shestakov]

You are welcome, James.
Once you have a question, don`t hesitate asking!

[Jamesdld23]

I did my migration from one vCenter to another and honestly I am really disappointed for the Veeam One part ...
Veeam One does monitor the new vCenter but all data of the old ones are not available from the Veeam One console.

[Shestakov]

That`s an expected behavior as we discussed above.
Have you preserved the old database?

[Jamesdld23]

I have preserved the database, as you mentioned I didn't remove the old vcenter from Veeam console.
I now have 3 issues :
- I exceed my socket number authorized by my licence
- I got an error each time Veeam One perform it's collection, normal because I didn't remove my "old vcenter from Veeam console"
- I can not parse any data of my old vcenter from the Veeam One console, seems we can not monitor something that is not reachable (sad when you loose your Infra, you can not use Veeam One to monitor what went bad)

[Vitaliy S.]

If you want historical data to be available in Veeam ONE, then I would suggest to deploy a new server and point it to existing (old database), keeping 2 databases (two vCenter Servers) will cause the behavior you see currently.

For future readers: if you want to preserve all data, you need to do an in-place upgrade of the vCenter Server or at least point new vCenter Server installation to the old database.

[tloveland]

This is a pretty big inconvenience for those of us who rely on Veeam One historical data for VM right sizing efforts. Veeam created a tool (though they don't officially support it) that does an excellent job of matching old moref ID's to new moref ID's when doing a vCenter migration so that CBT data is retained for Veeam B&R. It would be nice if there were something similar for Veeam One. The process would be the same. It would just be for a different database. As an engineer, I can say that I prefer to do an in place upgrade, but it's not always a feasible solution for various reasons, not the least of which it sometimes just doesn't work.

[wishr]

Hi Tom,

Thank you for the honest feedback.