Virtual Machine Instance : Data Cleanup From CMDB

[Amit Sharma4]

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

[Community Alums]

Hi Amit,

I would recommend you to not delete the records in cmdb_ci_vmware_instance table. Please go ahead and them as decommissioned.

Secondly, create a new Transform Map( I believe you will have a staging table and integration already) and you can mark the host name field as coalesce(Primary key) as this is the only field which is unique in VM's and after this you won't end up having duplicate records.

Let me know if you have more questions.

Please mark this comment as Helpful/ Correct Answer if it helped you.

Cheers,

Hardit Singh

[Amit Sharma4]

Thanks Hardit. Retiring them makes a good sense for me. Coming to stopping tham, how can i make a transform map , when they are directly discovered , not imported. 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.