Migrating PaperCut to a New Server
Last modified on 25 August 2016 05:49 PM
Migrating primary servers is considered a large administration task. Network administrators should block out at a minimum three hours, or more if you have a very large database, and should select a time where downtime will be of minimum disruption to end-users.
This article describes how to migrate the PaperCut primary server to a new system so that all data is moved to the new system. To ensure a smooth migration it is strongly recommended (actually required for versions prior to 7.2) to ensure that the versions of PaperCut on both the old and new servers is the same. The easiest way to achieve this is to upgrade the old server to the latest version, and then install the latest version on the new server.
Please read this article in full before conducting your migration.
NOTE: If you are running PaperCut on and external database (like SQL Server, PostgreSQL, Oracle) on a different machine to PaperCut follow our external database migration process.
Upgrading the old server to the latest version.
Migrating the data to new server
The simplest way to migrate data to the new server is to use the backup and restore process.
Updating user client, release station, site server, and secondary server connection details
If the primary server’s name and/or IP address is changing then it will be necessary to update these connection details for any user clients, site servers, secondary servers, and release stations that connect directly to it.
User Clients (Client Software)
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/updated. The simplest option is to re-install the client using the version available from the newly installed server. The other option is to manually edit the connection details in “config.properties” file in the user client install directory. On Mac clients, the “config.properties” file is embedded in the “.app” package and installing the client again by copying it off the new server is often the easiest solution.
If you have any site servers, then the
On each site server, start by opening a text editor such as Notepad.
Then open the file:
Locate the line starting with
Restart each site server so their new configuration is detected. Alternately, an administrator may choose to manually restart the Site Server service following the same process used to restart an application server.
If you have secondary print servers, then the
To do this, open a text editor such as Notepad.
Open the file:
Locate the line starting with
Restart the server so the new configuration is detected. To avoid a restart, an administrator may also choose to manually restart the PaperCut Print Provider service.
Secondary Servers (Internet)
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.
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.
Web Print (Simple)
If running a simple Web Print installation on Windows, Web Print will need to be reconfigured on the new server. If the server is not a domain member, you will have to recreate the “webprint” user and reconfigure its access to Adobe Reader, the hotfolder and the PaperCut Web Print service. Review the Web Print Simple Mode setup instructions for further details.
Web Print (Sandbox)
If running a sandbox Web Print installation, check the “webprint” user’s printer and hot folder shares from the sandbox, as the relevant paths may have changed. Review the Web Print Sandbox Mode setup instructions for further details.
If running PaperCut MF, you may need to reconfigure your MFDs to connect to the new machine’s network address.
Migrating a PaperCut Site Server
Migrating a site server is a lot simpler than migrating a PaperCut primary server. You don’t need to backup and restore a database, nor do you need to copy across any configuration or license files. It’s best to just install a new site server and associate it with the primary server, before switching off your pre-existing site server. Once setup, the new site server will simply copy down all the information it needs from the primary server.
However, it’s very important to note that if the site server’s name and/or IP address is changing, then any devices at your site that were configured to directly connect to it will need to be reconfigured with these new connection details.
This will typically be any of the site’s release stations and secondary servers, which can be reconfigured using the same methods as described above in this article for connecting those components to a new primary server. Similarly, if you’re running PaperCut MF, you may need to reconfigure the site’s MFDs to point to the new site server’s network address.
If the server’s hostname has changed (or if the installed printer names have changed) then you may like to rename the existing printer entries in PaperCut so that the printing history and settings are maintained. See the article How to Rename a Printer for more details.