Knowledge Base
Home » Main » Moving from one Edition of PaperCut to Another

Moving from one Edition of PaperCut to Another

To move from PaperCut Edition X to PaperCut Edition Y (also known as a cross-grade) follow the steps described below:

Use the following procedure to move PaperCut from one edition to another without setting/data loss. The procedure takes around 30 minutes. It is also possible to upgrade versions while changing editions (i.e. there is no need to match version numbers).

In summary, the process involves backing up the data, uninstalling the old edition, installing the new, then restoring the data. All database backups are compatible between editions.

1. Backup the data from the current installed PaperCut. Follow the instructions as described in the manual here.
2. Take a copy of the database backup which is saved in [appdir]\server\data\backups\. The filename will look like: “export-<timestamp>.zip” ( E.g. export-2008–01–18T14–22–03.zip ). Make sure you copy this file somewhere safe, and importantly outside of the PaperCut directory.
3. In line with best practice, we also recommend taking a backup copy of the entire PaperCut install directory. This will ensure you have a copy of other files that may need to be restored. e.g. customized web tools interface.
4. Double check that you have a copy of the database copies in a safe location! When you uninstall the current version of PaperCut all files will be deleted. So it is very important to copy files (or preferably all backup files) outside the PaperCut directory or even onto another disk for safe storage.
5. Uninstall the current PaperCut.
6. Install the new PaperCut edition following the standard setup procedure for your platform, architecture and environment.
7. Complete the setup wizard for the new PaperCut edition. (e.g. setting up the admin password, etc).
8. Once the setup is completed:
If using the internal database: restore the data from your backup file ( E.g. export-2008–01–18T14–22–03.zip ). The restore instructions can be found in the manual here.
If using an external database: Simply modify the server.properties file to point to your existing database as explained in the manual here.
9. If moving from PaperCut NG, to PaperCut MF, you should enable the external device integration by logging into PaperCut and enabling option “Enable external hardware integration” under the Options→Advanced tab.
10. If you had any custom SSL certificates installed: You will have to migrate them manually by copying your custom keystore my-ssl-keystore (or similarly named) from the old [app-dir]/server/custom directory to the new one. Also copy the following parameters from the old [app-dir]/server/server.properties to the new one: server.ssl.keystore, server.ssl.keystore-password, server.ssl.key-password.
11. Client software will usually automatically upgrade if you are using the zero-install (local cache) method for deployment. If the client is installed locally, a client from one edition will continue to work with the new installation however if you have upgraded versions during this process, it would be wise to keep the client and server software in sync.

If, during this process, you have also upgraded software versions (i.e. 9.2 to 11.4) please review the upgrade instructions. For larger sites it includes post-upgrade test plans which you may find useful.

To upgrade from PaperCut Quota to PaperCut NG follow the upgrading procedure listed in this KB article here:

http://www.papercut.com/kb/Main/UpgradingFromPaperCutQuotaToPaperCutNG.

If you have any questions about this process please email support.

keywords: move, migrating, transfer, migrate, change, changing, old, version, cross grade, ng, chargeback, mf, editions, ng to mf, changing to mf

Page last modified on October 20, 2011, at 01:39 AM

Comments

Share your findings and experience with other PaperCut users. Feel free to add comments and suggestions about this Knowledge Base article. Please don't use this for support requests.