Migrating PaperCut NG to a New Server - when using external database
This article describes how to migrate the PaperCut NG primary server to a new system, when using and external database (like Microsoft SQL Server or PostgreSQL) hosted on a different machine to PaperCut.
Important: If you are using the internal database, or are also moving the external database to a new machine then you should follow the standard migration process.
[app-path]/server/bin/<platform>/stop-server
[app-dir]/server/server.properties file from the old server to the new server. This file contains your database connection settings, and admin password, etc. If your database connection settings have changed, update the file appropriately.
http://server:9191/admin. DO NOT STOP/RESTART THE APPLICATION WHEN AN UPGRADE IS IN PROGRESS..
If the server's name and/or IP address is changing then it will be necessary to update these connection details for user clients, secondary servers, and release stations.
If user clients are being run from the share on the PaperCut server, you just need to ensure that the clients are run from the share on the new server.
If clients have been installed locally on workstations, then the connection details need to be edited in the "config.properties" file in the user client install directory.
If you have secondary print servers, then the "print-provider.conf" file on these servers need to be updated to point to the new machine's network address.
For all release stations, the "connection.properties" file located in the release station installation directory must be updated to reflect the machine's new network address.
If you have secondary Internet servers, then the "connection.properties" file on these servers need to be updated to point to the new machine's network address.
Categories: PaperCutNG
Keywords: migrate, upgrade, move, moving to a new server, changing servers, transfer