CMDB Retirement Custom Definition

[sandeshsidn]

Hello All,

We wanted to archive one ci in our instance.

So we have created a CMDB Retirement Custom Definition and also we have published a policy in cmdb data manager. Attached are the screenshots.

Actually wanted to understand whether i have made the right configurations and also wanted to understand when the scheduled job runs to retire and archive the ci? 

[JobyV · Accepted solution]

Retirement: Marks a CI as no longer in use or needed within the active CMDB.

Say a server is no longer alive on the network, and the support team didn't change the operational status to retired. The discovery is no longer able to update the CI. The retire policy will look for the most recent discovery(60-90days) and if it does fall in the criteria, the policy will set the CI to retired status (instead of manually updating it).

Archival: Moves retired CIs to a separate storage location (archive tables) to reduce clutter in the active CMDB. 

This is all part of maintain the CMDB health (Correctness and reducing staleness). There is a nice on demand course for CMDB health dashboard if you are interested. Hope this explains it further.

[JobyV · Accepted solution]

Right. you will need two policies to separate out retirement and archival.

Make sure your filter criteria is specific to the class you want to retire, it shouldn't affect other classes. A good practice will be to test it out in the lower instance and promote it once it meets your requirements.

[JobyV · Accepted solution]

Right. you will need two policies to separate out retirement and archival.

Make sure your filter criteria is specific to the class you want to retire, it shouldn't affect other classes. A good practice will be to test it out in the lower instance and promote it once it meets your requirements.

[sandeshsidn]

Hello JobyV

Thank you your solution worked.

if a ci is already selected for a incident and later on we archive the ci , what happens to that ci which was already selected on the incident? will it clear out from the incident form?

Also what happens to the asset associated with that ci after we archive the ci?

[sandeshsidn]

Hello JobyV

Thank you your solution worked.

if a ci is already selected for a incident and later on we archive the ci , what happens to that ci which was already selected on the incident? will it clear out from the incident form?

Also what happens to the asset associated with that ci after we archive the ci?

[JobyV · Accepted solution]

Further Reading: Working with CMDB Data Manager

When the CI is archived, the incident will have the original sys_id, but it will no longer point to a CI in the CMDB_CI table.