Kace Ticket Archiving
Hello, we have been on Kace for about two years now. Complete total ticket count currently around 60,000. We do not have the Archive ticket feature turned on at this time, and I know if i try i am going to get push back from the rest of IT. Has anyone noticed a significant performance increase by turning on the archiving?
2 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
rrjustin
6 years ago
Set ours to archive closed tickets after 1 month, and delete archived tickets after 6 months so I can't comment on performance as we don't have nearly that many in an active queue. Prior to the archive feature being available, I think the highest volume of tickets in our queue was around 45,000 and we were running on a physical server. We've since migrated to a VM with better hardware support, and enabled archiving.
If you have a legitimate business case to keep the tickets longer than 1 year, I'd say just set archiving to archive tickets older than 3-6 months, but do not delete them. If storage is your concern, you could just archive and then export the tickets to a csv as a backup.
They can still search the archive by going to it but after a year it might be out of date.
My argument is that if it that important, convert the ticket to a KB article as well and use that for reference. - nshah 6 years ago
Once that is done, you can go into the queue and set the drop drowns for archive and delete. - nshah 6 years ago