What are typical ages to retire and archive records in the cmdb_ci_computer table
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-29-2024 04:34 PM
I want to create policies for cmdb_ci_computer table and its subclasses. Does anybody have experience with policies for this table? What are typical ages to retire or archive a computer? I know it all depends on each organization, but is there a typical age, or what are the considerations to arrive to a number? 2 years to retire, 3 years to archive for example?
- Labels:
-
Data Foundations
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-30-2024 11:13 PM
In the case of a computer, the retirement is typically managed as part of hardware asset management process and usually it will be based on the end of life for that model. Sometimes organizations have policies like retiring computers which are older than 3 years (for example). But ideally they are retired as part of the HAM process based on the end of life date for the asset model. When the asset state is updated, the corresponding CI status will also automatically update to retired.
For archiving, it can be something like 2 or 3 years after retirement. It can be more than that also sometimes based on organization's requirements and volume of data. Similarly for deleting, it can be something like 2 or 3 years after archival. But you need to consider both the configuration management and the asset management considerations in your organization while defining the archival and retention periods. Also there are scenarios like 'legal hold' in HAM where you may need to exclude certain assets from your usual archival or deleting time periods.