BMC Helix ITSM data archiving
Archiving data is an essential step in data management. It provides a way to remove obsolete records from your production database using a regular, controlled, and predictable process. Archiving data also helps you to maintain system performance and to comply with your record retention policies. When designing an archive process:
- BMC requires up to 24 months of inactive data in all environments (non-production and production) to be archived.
- BMC recommends retaining no more than 5 years of data in archive forms.
For steps to delete archive data, see Configuring and managing the archiving process in the BMC Helix Innovation Suite documentation.
Inactive Data: Closed or cancelled records. In the context of knowledge articles, it refers to historical versions of the article.
In-application archiving
You may use the in-application AR System Archive Manager console to configure a continuous archive job and extract and delete archive data as needed. Key tenets of the archive function include the following:
- The archiving process defaults to a 24 months or lower archiving cycle.
- You may perform an on-demand archive run against selected records at any time.
- Each record type has its own archiving policy (record status criteria, default record age, and so on).
- Archiving a parent record also archives all of its child records, regardless of their state.
- Related records, for example, a change request related to an incident, follow their individual record type's archiving policy.
- When you archive a record, it is removed from the production environment and sent to a set of corresponding archive forms (stored within your production database). Once archived, data cannot be copied back into the production forms.
- System administrators can access archived data by generating reports that can be run against the archive forms by using BMC Helix ITSM Archived Work Orders dashboard.
For archived data, BMC recommends looking at aggregated reports instead of looking at each ticket.
For archiving attachments, BMC recommends that you archive the attachments by using the AR System Archive Manager console. - Archived data may be exported to comma-separated files (.csv) and/or permanently deleted from the archive tables by executing the System Archive Export function. Exports create a separate .csv file for each form. Files will be available for download via the File-transfer-process.
What is archived
The table below provides a complete list of out-of-the-box forms and their archiving policy.
Main form | Archive policy age (Days) | Description | Archive form |
---|---|---|---|
AR System Email Error Logs | 183 | AR System Email Error Logs archive all logs messages which are generated at the time of sending and receiving email messages. | AR System Email Error Logs Archive |
AR System Email Error Messages | 183 | AR System Email Error Messages archive all Incoming error messages with specified qualification. | AR System Email Error Messages Archive |
AR System Email Messages | 183 | AR System Email Messages archive all Incoming messages as well as successfully sent messages with specified age qualification. | AR System Email Messages Archive |
AR System Historical License Usage | 730 | AR System Historical License Usage Policy | AR System Historical License Usage_Archive |
AST:CMDB Associations | 730 | Archive Legacy Unarchived CMDB Relationships to ITSM tickets | AST:CMDB Associations_Archive |
BMC.CORE:BMC_BaseElement | 730 | CMDB Archive Policy for class BMC.CORE:BMC_BaseElement | BMC.CORE:BMC_BaseElement_Archive |
BundleDeploy:PackageRegistry | 180 | Bundle Deployment Package Registry Archive Policy | BundleDeploy:PackageRegistry_Archive |
CHG:Infrastructure Change | 730 | Change Management Archive Policy | CHG:Infrastructure_Change_Archive |
CMDB:Activities | 30 | Archive policy for CMDB Alerts. | CMDB:Activities_Archive |
CMDB:Dashboard | 90 | CMDB archive policy for Dashboard data. | CMDB:Dashboard_Archive |
CMDB:Graph_Walk_State_History | 1 | Archive Graph Walk State History | CMDB:Graph_Walk_State_History_Archive |
ES_Chat:AgentStatusInfo | 2 | Archive records that have not been modified since 2 days | ES_Chat:AgentStatusInfo_Archive |
HPD:Help Desk | 730 | Incident Management Archive Policy | HPD:Help_Desk_Archive |
NE:JobRun | 90 | CMDB archive policy for Normalization Engine | NE:JobRun_Archive |
PBM:Known Error | 730 | Known Error Archive Policy | PBM:Known_Error_Archive |
PBM:Problem Investigation | 730 | Problem Investigation Archive | PBM:Problem_Investigation_Archive |
PBM:Solution Database | 730 | Solution Database Archive Policy | PBM:Solution_Database_Archive |
RDA:DeploymentPackageDetails | 183 | D2P Package Details Archive Policy | RDA:DeploymentPackageDetails_Archive |
RE:Job_Runs | 90 | CMDB archive policy for Reconciliation Engine. | RE:Job_Runs_Archive |
Reported Errors | 15 | Archive all fixed duplicate or rejected issues after 15 days | Reported Errors Archive |
RKM:KnowledgeArticleManager | 730 | Knowledge Management Archive Policy | RKM:KnowledgeArticleManager_Archive |
RKM:SearchHistory | 90 | Knowledge Management Archive Policy for Search History | RKM:SearchHistory_Archive |
RKM:SearchHistory_Company | 90 | Knowledge Management Archive Policy for Search History Company | RKM:SearchHistory_Company_Archive |
RKM:SearchHistory_OperationalCategorization | 90 | Knowledge Management Archive Policy for Search History Operational Categorization | RKM:SearchHistory_OperationalCategorization_Archive |
RKM:SearchHistory_OrganizationDepartment | 90 | Knowledge Management Archive Policy for Search History Organization Department | RKM:SearchHistory_OrganizationDepartment_Archive |
RKM:SearchHistory_ProductCategorization | 90 | Knowledge Management Archive Policy for Search History Product Categorization | RKM:SearchHistory_ProductCategorization_Archive |
RKM:SearchHistory_Service | 90 | Knowledge Management Archive Policy for Search History Service | RKM:SearchHistory_Service_Archive |
RKM:SearchHistory_SiteRegion | 90 | Knowledge Management Archive Policy for Search History Site Region | RKM:SearchHistory_SiteRegion_Archive |
RKM:SearchHistory_Source | 90 | Knowledge Management Archive Policy for Search History Source | RKM:SearchHistory_Source_Archive |
RKM:SearchHistory_VisibilityGroup | 90 | Knowledge Management Archive Policy for Search History Visibility Group | RKM:SearchHistory_VisibilityGroup_Archive |
SLM:SLACompliance | 730 | SLA Compliance Archive Policy | SLM:SLACompliance_Archive |
SLM:SLAComplianceHistory | 730 | SLA Compliance History Archive Policy | SLM:SLAComplianceHistory_Archive |
SMT:APILogs | 20 | SMT:APILogs Archive Policy | SMT:APILogs_Archive |
SRM:Request | 730 | Service Request Archive Policy | SRM:Request_Archive |
SRM:Variable | 180 | SRM Variable Archival policy | SRM:Variable_Archive |
UDM:JobLog | 90 | UDM Job Logs Archival policy | UDM:JobLog_Archive |
UDM:TransformationLog | 90 | UDM Transformation Logs Archival policy | UDM:TransformationLog_Archive |
WOI:WorkOrder | 730 | Work Order Archive Policy | WOI:WorkOrder_Archive |
CSM:WF:KPICalculations | 730 | Archive all the closed data from CS:WF:Kpicalculations form | CSM:WF:KPICalculations_Archive |
What is purged
The table below provides a complete list of out-of-the-box forms that is purged and their deletion policy. These forms contain transient data, which refers to short-lived, session-based, and non-persistent data that is temporarily stored for backend processing purposes and does not contain any transactional, sensitive, or critical customer data.
Main form | Deletion policy age (Days) |
---|---|
AIS:Simulation_Info | 1 |
AIS:SimulationCIs_Info | 1 |
AR System Email Monitor | 178 |
Atrium:DataAnalyzerReportStore | 2 |
CMDB:Dashboard_Failure_Details | 7 |
CMDB:Dashboard_Utility_Run_History | 7 |
com.bmc.arsys.myitsb.myitsb-approval:FailedSBApprovalRequests | 365 |
com.bmc.dsm.asset-automation:Automation Job | 30 |
com.bmc.dsm.itsm-applications:Application error log | 15 |
com.bmc.dsm.slm-lib:Notification Schedule | 30 |
com.bmc.dsom.hgm:ConversationStates | 7 |
com.bmc.dsom.hgm:DataConnectionJob | 30 |
Entry Delete Audit | 180 |
myit-sb:ServiceRequestTaskHistory | 365 |
Server Group Cache Peer Error Audit | 1 |
SMO:ARHealthStatusAudit | 7 |
SMO:Monitor Output_Audit | 7 |
SMO:Monitor Trigger Association_Audit | 7 |
SMT:Social_FollowConfig | 30 |