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]

You are on the right track, but you shouldn't have the "serial number" in the retirement definition. It should be generic enough to be applied to the whole class. Also, since you are defining the Retirement policy, you should just set the Operational status/Install status to Retired. Once it's retired for a sometime, say 90 days, you can have another policy to archive it.

The schedules can be found in System Definition > Scheduled Jobs > 

CMDB Data Manager Retire Policy Processor

CMDB Data Manager Archive/Delete Policy Processor

You can run it on demand, but not a good idea to change the schedule.

[sandeshsidn]

Hello JobyV thanks for your reply,

I have added serial number just for testing one record.

Can you please let me know how this Retirement policy works? and how's its related to cmdb data manager.

My requirement is to archive the cmdb ci's for solaris server class.

[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.

[sandeshsidn]

Thanks for your inputs ,

For my requirement where i need to archive all ci's with class as solaris server , first i need to retire them and then i need to archive right?

so i need to create two data management policies one for retiring and other for archiving ?

attached are the below updated screenshots , please let me know if am missing anything and for the retirement definition i have just made the OOB definition as true.

So first the retire job runs and marks the ci's to retired and then the archive job archives them?

And also enabling the OOB retirement definition will affect any other ci's of different class?