Virtual Machine Instance : Data Cleanup From CMDB
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-08-2019 01:07 PM
Hi There,
We are using VDI at big scale in our environment and a number of vCenter Servers as well to manage our virtual environment. Over the time, we have huge number of Virtual Machine Instance CI's (CI records in cmdb_ci_vmware_instance table) , which are duplicate and have become stale as well. We are not much interested to manage this class but on the other hand we are managing the VDI and VMs as computers / servers.
We are looking forward to perform a clean up of these CI records and have 2 questions around it,
1: What is the best practice to do this clean up?
2: What will be a good approach for future to get in to this situation of having so many duplicate and stale CIs? I see not creating these CIs in future can be one of the options.
Please advice.
Thanks
Amit
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-09-2019 02:37 AM
Hello Amit,
Can I ask how these records are being created in the first place? are you using ServiceNow Discovery or a different tool to populate the record?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2019 12:28 PM
Hi James,
Thanks for the response. I was away so responding late on this, sorry for that.
We are using discovery only and these records are coming from vCenter Discovery. We have a record for same device in Server/Computer class with proper information on it and records in VM Instance class with limited info like Host Name, vmdx file location. RAM & CPU.
Thanks
Amit
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-13-2019 02:00 AM
Hello Amit,
Decommissioning the CI's in the CMDB would be a good start, have you enabled the vCenter Event Collector if you are using ServiceNow Discovery?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-13-2019 03:23 PM
No James, we have not enabled vCenter Event Collector, though we have some coming from vCOP but those are more or less for DRS and Capacity related.
I looked in to the identification and it is a dependent identifier which looks for name in virtual machine table and to my surprise there is no record in that table. Do you think it may have something to do with cmdb reparenting issue? Our instance has that.
