Migrating PaperCut to a New Server - when using external database

KB Home   |   Migrating PaperCut to a New Server - when using external database

Main.MigratingNGToNewServerExtDB History

Hide minor edits - Show changes to output

May 15, 2017, at 04:56 AM by peterf - Removing default recommendation to run Adobe Reader, as the xpdf renderer is now preferable
Changed lines 72-73 from:
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 [[https://www.papercut.com/products/ng/manual/ch-web-print-setup.html#ch-web-print-setup-simple|setup instructions]] for further details.
to:
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 the Web Print Hot Folder, as well as the PaperCut Web Print service. Review the Web Print Simple Mode [[https://www.papercut.com/products/ng/manual/ch-web-print-setup.html#ch-web-print-setup-simple|setup instructions]] for further details.
Changed line 76 from:
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 [[https://www.papercut.com/products/ng/manual/ch-web-print-setup.html#ch-web-print-setup-sandbox|setup instructions]] for further details.
to:
If running Web Print in sandbox mode, check the "webprint" user's printer and Web Print Hot Folder shares as added on each of the Web Print Servers, as the relevant network paths may have changed. Review the Web Print Sandbox Mode [[https://www.papercut.com/products/ng/manual/ch-web-print-setup.html#ch-web-print-setup-sandbox|setup instructions]] for further details.
June 26, 2015, at 06:58 AM by peterf - Expanded/fixed up the Site Server information further
Added lines 86-93:
!! Migrating a PaperCut Site Server

Migrating a Site Server is a lot simpler than migrating a PaperCut primary Application 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 Application 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 Application Server.

However, if your Site Server has been configured to use an external database of its own, then the original Site Server should be shutdown before the new one is configured to connect to both the external database and the Application Server; this will prevent two separate Site Servers attempting to access the same external database simultaneously. Additionally, 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 Application Server. Similarly, if youíre running PaperCut MF, you may need to [[https://www.papercut.com/kb/Main/UpdatingEmbeddedServerIP | reconfigure the siteís MFDs]] to point to the new Site Server's network address.

Added line 111:
* [[UpdatingEmbeddedServerIP|+]]
June 26, 2015, at 06:39 AM by peterf - Included information for Site Servers.
Changed lines 38-41 from:
!! Updating user client, release station and secondary server connection details

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.
to:
!! Updating user client, release station, site server, and secondary server connection details

If the server's name and/or IP address is changing then it will be necessary to update these connection details for user clients, site servers, secondary servers, and release
stations that connect directly to it.
Added lines 47-60:

!!! Site Servers

If you have any site servers, then the [@server.master.address=@] setting in the ďsite-server.propertiesĒ file on each of those site servers needs to be updated to point to the new primary serverís network address.

On each site server, start by opening a text editor such as Notepad.

Then open the file:

->[@[app-path]/server/site-server.properties@]

Locate the line starting with [@server.master.address=@] and change the name or IP address to that of the new primary server.

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 [[https://www.papercut.com/products/ng/manual/apdx-tools-start-stop-app.html | restart an application server]].
Changed lines 82-84 from:
to:
* Consider informing your users that jobs currently in a secure hold/release queue will not be transitioned across to the new installation and they should release their jobs prior to the planned outage.

April 03, 2013, at 05:22 AM by Jason - We don't use app-dir
Changed lines 26-29 from:
# Copy the @@[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.

# Copy the @@[app-dir]/server/application.license@@ file from the old server to the new server.  This file contains your license information. NOTE: On Mac/Linux ensure proper permissions on the new server: @@chown papercut:admin server.properties@@
to:
# Copy the @@[app-path]/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.

# Copy the @@[app-path]/server/application.license@@ file from the old server to the new server.  This file contains your license information. NOTE: On Mac/Linux ensure proper permissions on the new server: @@chown papercut:admin server.properties@@
Changed lines 34-35 from:
# '''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.
to:
# '''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-path]/server/custom@] directory to the new one. Also copy the following parameters from the old [@[app-path]/server/server.properties@] to the new one: server.ssl.keystore, server.ssl.keystore-password, server.ssl.key-password.
December 31, 2012, at 04:41 AM by ian - Added webprint notes as per Daniel Schwartz's comment.
Added lines 56-63:
!!! 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 [[https://www.papercut.com/products/ng/manual/ch-web-print-setup.html#ch-web-print-setup-simple|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 [[https://www.papercut.com/products/ng/manual/ch-web-print-setup.html#ch-web-print-setup-sandbox|setup instructions]] for further details.

Changed line 91 from:
[-Keywords: migrate, upgrade, move, moving to a new server, changing servers, transfer-]
to:
[-Keywords: migrate, upgrade, move, moving to a new server, changing servers, transfer-]
Changed lines 16-17 from:
# Download the latest available version available from the [[https://www.papercut.com/download/ng/ | PaperCut NG download page]].  For information on what has changed in recent releases, see the [[https://www.papercut.com/products/ng/release_history/ | release history page]].  '''NOTE: Make sure you are eligible to upgrade to this release by checking our [[UpgradePolicy | upgrade policy]].  Past releases can be downloaded [[PastVersions | here]]'''
to:
# Download the latest available version available from the [[https://www.papercut.com/download/ng/ | PaperCut NG download page]].  For information on what has changed in recent releases, see the [[https://www.papercut.com/release-history/|release history page]].  '''NOTE: Make sure you are eligible to upgrade to this release by checking our [[UpgradePolicy | upgrade policy]].  Past releases can be downloaded [[PastVersions | here]]'''
Changed line 83 from:
[-Keywords: migrate, upgrade, move, moving to a new server, changing servers, transfer-]
to:
[-Keywords: migrate, upgrade, move, moving to a new server, changing servers, transfer-]
Added lines 36-37:
# Consider turning off the old server or if running Windows, making the PaperCut services a manual start-up.
Changed line 83 from:
[-Keywords: migrate, upgrade, move, moving to a new server, changing servers, transfer-]
to:
[-Keywords: migrate, upgrade, move, moving to a new server, changing servers, transfer-]
Changed lines 3-4 from:
This article describes how to migrate the PaperCut NG primary server to a new system, when using an external database (like Microsoft SQL Server or `PostgreSQL) hosted on a different machine to PaperCut.
to:
This article describes how to migrate the PaperCut primary server to a new system, when using an external database (like Microsoft SQL Server or `PostgreSQL) hosted on a different machine to PaperCut.
Changed lines 8-9 from:
!! Install PaperCut NG on the new machine
to:
!! Install PaperCut on the new machine
Changed lines 16-17 from:
# Download the latest available version available from the [[https://www.papercut.com/products/ng/download/ | PaperCut NG download page]].  For information on what has changed in recent releases, see the [[https://www.papercut.com/products/ng/release_history/ | release history page]].  '''NOTE: Make sure you are eligible to upgrade to this release by checking our [[UpgradePolicy | upgrade policy]].  Past releases can be downloaded [[PastVersions | here]]'''
to:
# Download the latest available version available from the [[https://www.papercut.com/download/ng/ | PaperCut NG download page]].  For information on what has changed in recent releases, see the [[https://www.papercut.com/products/ng/release_history/ | release history page]].  '''NOTE: Make sure you are eligible to upgrade to this release by checking our [[UpgradePolicy | upgrade policy]].  Past releases can be downloaded [[PastVersions | here]]'''
June 23, 2011, at 11:46 PM by 202.129.124.120 -
Changed lines 3-4 from:
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.
to:
This article describes how to migrate the PaperCut NG primary server to a new system, when using an external database (like Microsoft SQL Server or `PostgreSQL) hosted on a different machine to PaperCut.
June 09, 2011, at 01:19 AM by 202.129.124.120 -
Added lines 28-29:
# Copy the @@[app-dir]/server/application.license@@ file from the old server to the new server.  This file contains your license information. NOTE: On Mac/Linux ensure proper permissions on the new server: @@chown papercut:admin server.properties@@
October 10, 2010, at 11:08 PM by 202.129.124.120 -
Changed lines 32-33 from:
to:
# '''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.
Changed lines 57-58 from:
If running PaperCut MF, you may need to reconfigure your MFDs to connect to point to the new machine's network address.
to:
If running PaperCut MF, you may need to reconfigure your [=MFDs=] to connect to point to the new machine's network address.
April 20, 2010, at 02:14 AM by 202.129.124.120 -
Added lines 14-15:
# Take down PaperCut services on the old server.  e.g. Disable the ''PaperCut Application Server'' service or manually uninstall PaperCut from the old server.  This is important as only one PaperCut primary server must exist on a network and only one instance of PaperCut should connect to the database at any one time.
Changed lines 53-56 from:
to:
!!! Other devices

If running PaperCut MF, you may need to reconfigure your MFDs to connect to point to the new machine's network address.

Changed lines 26-27 from:
# Start the application server again.  PaperCut should connect to the database and start correctly.  '''NOTE: If a database upgrade is required, this may take a while, but you can view the status of the upgrade at @@[=http://server:9191/admin=]@@.  DO NOT STOP/RESTART THE APPLICATION WHEN AN UPGRADE IS IN PROGRESS.'''.
to:
# Start the application server again.  PaperCut should connect to the database and start correctly.  '''NOTE: If a database upgrade is required, this may take a while, but you can view the status of the upgrade at @@[=http://server:9191/admin=]@@.  DO NOT STOP/RESTART THE APPLICATION WHEN AN UPGRADE IS IN PROGRESS'''.
Deleted line 44:
Added lines 54-69:
!! Renaming Printers

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 [[HowToRenameAPrinter|+]] for more details.


!!Advanced Tips:
* Set up your printers on the new server and test before installing PaperCut.

* Consider turning your old server into a ''PaperCut Secondary Server'' reporting usage across to your new primary server.  This may give you more time to map over workstations that may not be managed via a logon script, etc.  You can then decommission the server at a later date.


!!See also:
* [[MigratingNGToNewServer|+]]
* [[HowToRenameAPrinter|+]]
* [[ChangingServerNameIP|+]]

Changed line 71 from:
''Categories:'' [[!PaperCutNG]]
to:
''Categories:'' [[Category.Administration|+]]
Changed line 73 from:
[-Keywords: migrate, upgrade, move, moving to a new server, changing servers, transfer -]
to:
[-Keywords: migrate, upgrade, move, moving to a new server, changing servers, transfer-]
December 11, 2008, at 01:48 AM by 218.214.136.161 -
Changed lines 1-2 from:
(:title Migrating PaperCut NG to a New Server - when using external database:)
to:
(:title Migrating PaperCut to a New Server - when using external database:)
Changed line 58 from:
[-Keywords: migrate, upgrade, move, moving to a new server, transfer -]
to:
[-Keywords: migrate, upgrade, move, moving to a new server, changing servers, transfer -]
Changed lines 22-25 from:
# Stop the application server service as described in the [[https://www.papercut.com/products/ng/manual/apdx-tools-start-stop-app.html | manual here]].

# Copy the
@@[appdir]/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.
to:
# Stop the ''PaperCut Application Server'' by running the script [@[app-path]/server/bin/<platform>/stop-server@]

# Copy the
@@[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.
Changed line 58 from:
[-Keywords: migrate, upgrade, move -]
to:
[-Keywords: migrate, upgrade, move, moving to a new server, transfer -]
Changed lines 18-19 from:
# Once the setup is complete, you will be requested to run the config wizard.  You do not need to perform this step, because your configuration is stored in your database on a different server.
to:
# Once the setup is complete, you will be requested to run the config wizard.  After the installation has ran, ''complete'' the configuration wizard and import your users.  Although importing the users again is not strictly required - as this data will be overridden later - it does confirm that your new server has the correct network connectivity and also saves your admin password as entered in the wizard.

-->[-'''TIP:''' If you have a very large list of users, try importing a small group of users, hence cutting down the import time. -]

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.

Article last modified on May 15, 2017, at 04:56 AM
Printable View   |   Article History   |   Edit Article