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.

Inactive Data: Closed or cancelled records. In the context of knowledge articles, it refers to historical versions of the article.  

Important

If you have questions about this update, please open a case with BMC Helix Support with “Archival Questions” as the subject.
BMC Helix service management base data capacity is in effect for the production environment, including archive tables, regardless of the archive solution.

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.

Important

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 Logs183AR 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 Messages183AR System Email Error Messages archive all Incoming error messages with specified qualification.AR System Email Error Messages Archive
AR System Email Messages183AR 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 Usage730AR System Historical License Usage PolicyAR System Historical License Usage_Archive
AST:CMDB Associations730Archive Legacy Unarchived CMDB Relationships to ITSM ticketsAST:CMDB Associations_Archive
BMC.CORE:BMC_BaseElement730CMDB Archive Policy for class BMC.CORE:BMC_BaseElementBMC.CORE:BMC_BaseElement_Archive
BundleDeploy:PackageRegistry180Bundle Deployment Package Registry Archive PolicyBundleDeploy:PackageRegistry_Archive
CHG:Infrastructure Change730Change Management Archive PolicyCHG:Infrastructure_Change_Archive
CMDB:Activities30Archive policy for CMDB Alerts.CMDB:Activities_Archive
CMDB:Dashboard90CMDB archive policy for Dashboard data.CMDB:Dashboard_Archive
CMDB:Graph_Walk_State_History1Archive Graph Walk State HistoryCMDB:Graph_Walk_State_History_Archive
ES_Chat:AgentStatusInfo2Archive records that have not been modified since 2 daysES_Chat:AgentStatusInfo_Archive
HPD:Help Desk730Incident Management Archive PolicyHPD:Help_Desk_Archive
NE:JobRun90CMDB archive policy for Normalization EngineNE:JobRun_Archive
PBM:Known Error730Known Error Archive PolicyPBM:Known_Error_Archive
PBM:Problem Investigation730Problem Investigation ArchivePBM:Problem_Investigation_Archive
PBM:Solution Database730Solution Database Archive PolicyPBM:Solution_Database_Archive
RDA:DeploymentPackageDetails183D2P Package Details Archive PolicyRDA:DeploymentPackageDetails_Archive
RE:Job_Runs90CMDB archive policy for Reconciliation Engine.RE:Job_Runs_Archive
Reported Errors15Archive all fixed duplicate or rejected issues after 15 daysReported Errors Archive
RKM:KnowledgeArticleManager730Knowledge Management Archive PolicyRKM:KnowledgeArticleManager_Archive
RKM:SearchHistory90Knowledge Management Archive Policy for Search HistoryRKM:SearchHistory_Archive
RKM:SearchHistory_Company90Knowledge Management Archive Policy for Search History CompanyRKM:SearchHistory_Company_Archive
RKM:SearchHistory_OperationalCategorization90Knowledge Management Archive Policy for Search History Operational CategorizationRKM:SearchHistory_OperationalCategorization_Archive
RKM:SearchHistory_OrganizationDepartment90Knowledge Management Archive Policy for Search History Organization DepartmentRKM:SearchHistory_OrganizationDepartment_Archive
RKM:SearchHistory_ProductCategorization90Knowledge Management Archive Policy for Search History Product CategorizationRKM:SearchHistory_ProductCategorization_Archive
RKM:SearchHistory_Service90Knowledge Management Archive Policy for Search History ServiceRKM:SearchHistory_Service_Archive
RKM:SearchHistory_SiteRegion90Knowledge Management Archive Policy for Search History Site RegionRKM:SearchHistory_SiteRegion_Archive
RKM:SearchHistory_Source90Knowledge Management Archive Policy for Search History SourceRKM:SearchHistory_Source_Archive
RKM:SearchHistory_VisibilityGroup90Knowledge Management Archive Policy for Search History Visibility GroupRKM:SearchHistory_VisibilityGroup_Archive
SLM:SLACompliance730SLA Compliance Archive PolicySLM:SLACompliance_Archive
SLM:SLAComplianceHistory730SLA Compliance History Archive PolicySLM:SLAComplianceHistory_Archive
SMT:APILogs20SMT:APILogs Archive PolicySMT:APILogs_Archive
SRM:Request730Service Request Archive PolicySRM:Request_Archive
SRM:Variable180SRM Variable Archival policySRM:Variable_Archive
UDM:JobLog90UDM Job Logs Archival policyUDM:JobLog_Archive
UDM:TransformationLog90UDM Transformation Logs Archival policyUDM:TransformationLog_Archive
WOI:WorkOrder730Work Order Archive PolicyWOI:WorkOrder_Archive
CSM:WF:KPICalculations730Archive all the closed data from CS:WF:Kpicalculations formCSM:WF:KPICalculations_Archive

Important

Archiving a record also archives its attachments.

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_Info1
AIS:SimulationCIs_Info1
AR System Email Monitor178
Atrium:DataAnalyzerReportStore2
CMDB:Dashboard_Failure_Details7
CMDB:Dashboard_Utility_Run_History7
com.bmc.arsys.myitsb.myitsb-approval:FailedSBApprovalRequests365
com.bmc.dsm.asset-automation:Automation Job30
com.bmc.dsm.itsm-applications:Application error log15
com.bmc.dsm.slm-lib:Notification Schedule30
com.bmc.dsom.hgm:ConversationStates7
com.bmc.dsom.hgm:DataConnectionJob30
Entry Delete Audit180
myit-sb:ServiceRequestTaskHistory365
Server Group Cache Peer Error Audit1
SMO:ARHealthStatusAudit7
SMO:Monitor Output_Audit7
SMO:Monitor Trigger Association_Audit7
SMT:Social_FollowConfig30

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*