Partially Clearing Out The Log Data

Q We are a school who have been running PaperCut for approximately one year. We would like to clear out the database of print jobs prior to this school year. How do I perform a partial clear? PaperCut has unlimited log sizes and has a smart log rotation procedure for text based system and print logs. Rotation is not usually required as disks are so large these days. You can, however, configure the system to delete older data either: Automatically via the options under Options → Backup → Delete old log data (Enable automatic weekly reports box must be checked) Manually using the command-line option db-tools delete-old-logs as explained in detail in the manual . A value of 0 will delete all logs from today onwards. In line with print management best practice, PaperCut recommends that all sites keep print log data as long as possible. Historical print usage data allows organizations to look at printing trends and conduct audits over long periods of time. PaperCut is designed in a way where large databases with historical log data will not slow down day-to-day use of the system. For reference if print data is deleted and “Delete data in tables linked to deleted print logs” is selected - the below will be deleted: tbl_printer_usage_log - logs detailed usage data for printers, such as jobs printed, user activity, or hardware interactions. tbl_print_hardware_check –Stores hardware status checks, which could include printer diagnostics or maintenance logs. tbl_refund_request – Contains refund request records for print jobs, including who requested a refund and whether it was approved or denied. Q I am seeing the error shown below when trying to delete old logs. What can I do about it? Error occurred running db-tools, command: delete-old-logs. GC overhead limit exceeded We have seen this error at a few busy sites. (Sites printing a large volume of pages every day). By default, db-tools application uses 256MB of memory which can be increased by making the following changes. Open the db-tools file using a text editor. Find the line Xmx256M Try adding a higher amount by doubling it. E.g. Xmx512M Save the file. Test it, and repeat as necessary. Hopefully, this should resolve the issue. If you still see issues, please contact support . Including Application server debug logs would be super helpful.