Archiving unused Service Desk data

For Alloy Navigator Enterprise On-Prem

As the number of closed Service Desk tickets (Change Requests, Incidents, Problems, Service Requests, and Work Orders) grows, so does the size of your Alloy Navigator database. However, these closed Ticket records are rarely needed in daily activities. To reduce the size of your database you should use the Archiving functionality.

Archiving moves closed tickets into an archive database and deletes the originals from your database. If you do not want to archive your data, you can simply purge closed tickets, although that is not recommended.

FOR CLOUD CUSTOMERS: In our cloud (SaaS) instances, the ability to archive old Service Desk tickets is disabled. For details, see Installation Guide: Alloy Navigator Cloud (SaaS).

NOTE: Archived records do not store information about Tickets' History or their Related Objects (for details, see Viewing and restoring archived tickets). Archived records can be only viewed, so this feature is not a substitute for regular data backups. You can use the Database Backup/Restore Wizard to back up your database. For details, see Help: Database Backup/Restore Wizard.

In the Settings App, you can configure one or more archiving jobs to regularly clean up your closed Tickets. Archiving jobs regularly check your Alloy Navigator database, and archive and remove closed Ticket records matching the job’s policy.

When an archiving job runs, it creates a separate new archive database. Archive databases contain archived Tickets, where all references to other objects are replaced with text identifying these items.

INFO: Archiving jobs run on the Automation Server, which must be properly configured and started beforehand. For details, see Automation Server.