What are you doing to the CI relationships when you are retiring the CI?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-14-2022 11:20 AM
What are you doing to the CI relationships when you are retiring the CI? How are you handling the relationships?
Manually? Automated? or Archiving ?
Thanks in advance
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-14-2022 12:05 PM
Some articles for this
CI lifecycle management
For me i generally export the retired CIs,relationships once in every quarter and archive them into cloud which is shared with cmdb managers.
After that clean up those CIs to keep CMDB table clean.
Hope its helpful
Anshu
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-15-2022 03:34 AM
Hi @anshu
Can you share more details on how you are archiving? steps etc.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-15-2022 08:05 AM
Once in every quarter, I filter the Cis which are marked as retired.
I export these CIs into excel with related lists.(incidents, changes affected)
from cmdb_rel_ci, i get all its relationships exported.
filter on parent.ci is retired and child.ci is retired
Then Cleaned the orphan ,empty relationships via this script
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0780988
I have to do this because, our cmdb has 9 million records, and every now and then their are duplicates due manual creation in past and retired.
Also no one is interested in a server which was retired 5 years ago. why to keep it then...
If you have a small cmdb database, you can leave the retired ones as it.
just remove the serial numbers(also from serial_number table) and ip address for that Ci , so that they could not be discovered anymore(in case the same asset hardware components changed but asset is same)
Hope its helpful
Anshu