Archiving and Deleting Log Data from the Neurons for ITSM Databases

about archiving and deleting log data from the neurons for itsm databases docid\ tmpvz7tsfxzvjpswjr53cabout the types of log data to archive and delete docid\ tmpvz7tsfxzvjpswjr53carchiving and deleting log data from the neurons for itsm databases docid\ tmpvz7tsfxzvjpswjr53cmodifying the database archive and delete feature docid\ tmpvz7tsfxzvjpswjr53c about archiving and deleting log data from the neurons for itsm databases in , if you do not delete the data in your databases, the data continues to grow this can cause problems with storage for the databases, reduced performance as the application grows, database schema changes taking longer to apply, and the quality of the search results can diminish when old, and irrelevant, data is included additionally, larger databases required more database servers which can increase costs logs contain valuable information about and are invaluable aids to technical support for diagnosing customer issues recommends that you keep all logs from the current release and the most recent past major release prior to release 2015 1, we only supported backing up the databases for disaster recovery purposes you can configure the data to delete at the business object level for each database delete, you can specify the following the business objects to include in the archive the schedule for the archive, per business object if the archive is enabled or disabled, per business object the part of the business object to archive if you can preview the archive when to back up or purge the archive about the types of log data to archive and delete the database archive and delete feature works with two types of data transactional data, which is a customer's data records, including incidents, changes, service requests, and so on non transactional data, which is made up of logs currently, these are the database tables for logs frs application update notes frs application update notes frs baselinelog baseline log frs data integration history integration history frs data integration log integration log frs data run program log run program log frs data workflow instance workflow instance frs globalauditlog global audit log frs itfm rolluplog itfm rollup log frs ops change log development package change log frs ops gbu pipeline history gbu pipeline history frs ops integration queue integration queue frs ops metadata history metadata history frs ops validation results validation results ldapimportlog ldap import log logs logs scheduledjobhistory scheduled job history audit ci auditci archiving and deleting log data from the neurons for itsm databases you can either use this feature as is to clean out non transactional data or you can modify the feature to tailor it to your organization's needs to modify the feature, see modifying the database archive and delete feature docid\ tmpvz7tsfxzvjpswjr53c to use the feature as is, follow this process from the configuration console, click build > workflow > workflows to open the workflows workspace the application displays the list of available workflows under the scheduled entry header, click archive logs the application displays the workflows archive logs page at the end of the line for the most recent workflow version, click the publish icon to enable the workflow the workflow line turns green at the confirmation message, click yes the application publishes the archive logs workflow and data either archives or deletes the data based on its parameters easily deleting your data see about workflows docid\ yknnkmov2vtiowta7xn5w and archive for search workflow block docid\ uof25jljo49l8g9f2keot for information about workflows modifying the database archive and delete feature you can modify the database archive and delete feature to suit the specific needs of your organization modifying the age of the data to archive and delete docid\ tmpvz7tsfxzvjpswjr53cmodifying the time and frequency of the database archive and delete feature docid\ tmpvz7tsfxzvjpswjr53cmodifying the data to archive and delete docid\ tmpvz7tsfxzvjpswjr53c modifying the age of the data to archive and delete the application archives and deletes data of a certain age, as defined by the archiveage global constant you can edit the value of the archiveage global constant so that the data to archive and delete is older or newer than the default value of 180 days follow these steps to modify the age of the data to archive and delete from the configuration console, click build > global constants to open the global constants workspace the application displays the list of global constants scroll to the global constant called archiveage double click the value to edit it change the value click save see modifying a global constant docid\ mirdh rhcg0jei2i56fmm for more information about using global constants modifying the time and frequency of the database archive and delete feature the database archive and delete feature runs on a schedule that is defined by a scheduled job called archive schedule you can edit the archive schedule scheduled job so that the database archive and delete feature runs more or less frequently, or at a different time run the database archive and delete feature outside standard office hours for the landscape location to maintain optimal performance, as archiving and deleting data could impact the performance of the application, especially the very first time the amount of time to archive and delete the data depends on the size of the data to archive and delete, which depends on how frequently you run the feature and how big your application is for example, if you run the database archive and delete feature weekly, then you archive and delete a week's worth of data but the first time that you archive and delete data, you will be archiving and deleting all of the application data so that will be significantly more data and take much longer the default scheduled job for the data archive and delete feature is to run on saturday and sunday starting at 12 00am and ending any time before 11 45pm both times are local times follow these steps to modify the frequency of the database archive and delete feature from the configuration console, click monitor > scheduled jobs to open the scheduled jobs workspace the application displays the list of scheduled jobs double click the archive schedule scheduled job to open the record change the values as needed click save see about the schedule entry and scheduled jobs workspaces docid\ oly9b8ak4f7dbrbymcikf for more information about using scheduled jobs modifying the data to archive and delete the data to archive and delete is based on a saved search called archive you can create your own saved search or you can use the archive saved search for example, if you do not want to archive or delete all of the logs, but just a specific log, you can modify the saved search follow these steps to modify the data to archive and delete by modifying the archive saved search from the application, open the logs workspace the application displays the list of logs click all to show the list of saved searches associated with logs at the bottom of the list, click all saved searches the application displays the list of saved searches with additional information highlight a saved search and click the edit icon to view the search criteria to run the saved search, click run search the application displays the list of logs that are part of this saved search