Restoring from backup
How do I restore a PaperCut database file?
PaperCut NG & PaperCut ChargeBack (Internal Database):
The PaperCut NG data (stored in the internal database) can be restored either by restoring the contents of the directory:
[app-path]/Program Files/PaperCut NG/server/data
from your latest off-disk backup. Remember to stop the PaperCut Application Server service before restoring (so the files are not in use at the time of restoration).
Or, alternatively it is possible to restore a point-in-time backup file as created by PaperCut's own backup procedure. These are stored in the directory:
[app-path]/Program Files/PaperCut NG/server/backups
Again, you may need to restore your latest point-in-time backup file from your system's off-disk backup system. The files all end in a zip extension and are named with the data and time allowing you to select the most recent backup. Point-in-time backups can be imported into the system using the db-tools program as detailed in the user guide here:
and
PaperCut NG & PaperCut ChargeBack (External Database):
All data is stored in the external database with the exception of:
Instead, these settings are stored in the ~/server/server.properties file. If the Application Server fails, all data is still safe in the external database. Simply re-installing PaperCut, complete the configuration wizard, then pointing it to the existing external database will restore all settings and data.
If your database crashes, follow your database's recommended restore procedure. Again, PaperCut does maintain it's own point-in-time backups (see above) in the directory:
[app-path]/Program Files/PaperCut NG/server/backups
PaperCut Quota:
PaperCut stores data such as the user list, account balances, and activity logs in files labeled with an MDB file extension (*.mdb). PaperCut will automatically take backups of these important files during key operations such as a database “tune up”. Backups are placed in the directory:
C:\Program Files\PaperCut\Backups
*.mdb file intended to be overwritten to a safe place on the hard drive.
*.mdb file from the backup pool over the top of the existing file. Ensure the file name is consistent with the original file name.
Categories: Backups
keywords: crash, restoration, back-up