by foggy » Wed Feb 03, 2016 9:25 am people like this post
I suspect this process triggers VM ID's change in the database, so VM's will be treated as new ones. Probably you can ask support to map old ID's to the new ones, if the tool they periodically use for that is applicable to this scenario.
by mpatrick » Wed Mar 29, 2017 1:50 pm people like this post
We have two 5.5 vCenter appliances using the embedded database. One is used for our production virtual machines. They are being backed up by Veeam 9.5. The other vCenter is used for DR. Veeam is replicating about 30 VMs onto its two ESXi hosts. The issue is that the inventory service database on the DR vCenter has increased to 30 GB and we are getting close to running out of disk space. The inventory service database on the production vCenter appliance is only 500 MB. Could Veeam replication be causing the inventory service database to increase in size that much?
by mpatrick » Tue Apr 04, 2017 7:02 pm people like this post
No we are not replicating the vCenter Server appliance to the remote site. Our Veeam administrator has reviewed and adjusted the replica jobs. We are monitoring to see if this stops or slows the inventory service database growth.
by mpatrick » Mon May 01, 2017 4:54 pm people like this post
We turned off the initial seeding mapping to specific replicas. But the inventory service database continued to increase in size. We decided to double the size of the vCenter drive that the db is on instead of resetting the db.