CMDB Clean up ! Suggestions needed...

[Sohail Khilji]

Dear CMDB Experts !

We are going to do a large cmdb clean up and to keep things short and crisp... I'll explain the scenario below ( you can suggest your approaches too)

(Our source of truth is Discovery & SCCM only)

1. We have around 400,000 CIs currently in cmdb.

2. Around 160,000 are new CIs which the business needs it actively. (This is going to be the actual CI count after clean up - filter condition ( updated in last 6 months)).

3. Now we need to delete around 240,000 CIs from our cmdb ( reason for delete is - they are no more relevant to business ). 

Questions:  

1. Wats the best approch to delete these 240,000 CIs.

2. We only need 160000 CIs in cmdb for today ( what's the best way to purge / archive old 240,000 CIs.

3. Discovery does not run on our Dev/Uat , so we need to clean up the whole cmdb from dev/Uat and copy the new 160,000 CIs from Prod to Dev or UAT. ( What's recommend?)

@CMDB Whisperer @Community Alums @Amit Gujarathi @Ankur Bawiskar @Mark Roethof

@Mark Manders  @AndersBGS 

[AJ-TechTrek]

Hi @Sohail Khilji ,

When you are mentioning to delete the 240000 these CI, Whats is class of these CI, Also As i am sure somehow those CI are related to actual CI from related List , relationships etc.

As while we discovering any Windows Server, There are couple of record created in CMDB for an window server related CI like Disk, IP, Applications, Network Adapter, Software Installtions, Filesystems, Storage, Serial Number, running Process, memory Modules, TCP connections etc, somehow all these are related to One window server which we discovered as a Main CI.

Also ask customer to a baseline List of CI , so you can compare the both CMDB data and List.

Also deleting is not a good solution, Instead if that CI is not using, you can update the CI Operational Status and Install Status of CI.

Also Using background script you can delete if you want to delete.

Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.

Thanks

AJ

Linkedin Profile:- https://www.linkedin.com/in/ajay-kumar-66a91385/

ServiceNow Community Rising Star 2024

[Dr Atul G- LNG]

Hi @Sohail Khilji 

even we already discussed this, but still adding comments here

- Before delete take back up

- Try to divide in2.5 L CI in classes

- Retire is best option then delete

- Check is these 2.5L CI has any relationship with new CI's.

If no above point work, go and delete 🙂