Upgrading PaperCut NG in a Microsoft Cluster Environment

KB Home   |   Upgrading PaperCut NG in a Microsoft Cluster Environment

Main.UpgradeNGInACluster History

Hide minor edits - Show changes to output

July 05, 2018, at 07:23 PM by Aaron Pouliot - Added category Clusters
Changed line 41 from:
''Categories:'' [[Category.Administration|+]], [[Category.Upgrading|+]]
to:
''Categories:'' [[Category.Clusters|+]], [[Category.Upgrading|+]]
April 29, 2014, at 10:14 PM by don - Text of "Backup" was changed to "Export"
Changed lines 13-14 from:
-> '''Step 1:''' '''BACKUP NOW!''' - an upgrade is a system change and like all major system changes should be conducted with care.  We recommend taking time now to backup the PaperCut database using the system's point-in-time backup procedure ([@ Options -> Backups -> Backup Now @]), as well as a general backup of the current PaperCut install directory (e.g. a Zip archive).
to:
-> '''Step 1:''' '''BACKUP NOW!''' - an upgrade is a system change and like all major system changes should be conducted with care.  We recommend taking time now to backup the PaperCut database using the system's point-in-time backup procedure ([@ Options -> Backups -> Export Now @]), as well as a general backup of the current PaperCut install directory (e.g. a Zip archive).
June 03, 2013, at 08:01 AM by tom - obvious typos... whole article probably needs a scan
Changed lines 9-12 from:
This upgrade procedure is designed to compliment the [[UpgradingNG | standard upgrade procedure]].  The reader should familiarize themselves with the standard upgrade procedure before preceding.


to:
This upgrade procedure is designed to compliment the [[UpgradingNG | standard upgrade procedure]].  The reader should familiarize themselves with the standard upgrade procedure before proceeding.


Changed lines 27-28 from:
-> '''Step 4:''' The installer will start the application server.  On first startup after an upgrade, the server may need to perform some data upgrade tasks.  The browser window may inform you of this upgrade status - Keep pressing the browser's refresh button to update the status.  If/when you can see the standard login box, the upgrade has completed.  Do '''not''' precede to the next step until the data upgrade has completed.  This may take a few minutes on large databases.
to:
-> '''Step 4:''' The installer will start the application server.  On first startup after an upgrade, the server may need to perform some data upgrade tasks.  The browser window may inform you of this upgrade status - Keep pressing the browser's refresh button to update the status.  If/when you can see the standard login box, the upgrade has completed.  Do '''not''' proceed to the next step until the data upgrade has completed.  This may take a few minutes on large databases.
Changed lines 21-22 from:
-> Match the install options as per the origional install. i.e. If the cluster is [[https://www.papercut.com/products/ng/manual/ch-clustering-microsoft.html#cluster-mode1|Mode 1]] installed the "Secondary Server" option, or if [[https://www.papercut.com/products/ng/manual/ch-clustering-microsoft.html#cluster-mode2|Mode 2]], the "Standard Installation".
to:
-> Match the install options as per the origional install. i.e. If the cluster is [[https://www.papercut.com/products/ng/manual/ch-clustering-microsoft.html#cluster-mode1|Mode 1]] installed the "Secondary Server" option, or if [[https://www.papercut.com/products/ng/manual/ch-clustering-microsoft.html#cluster-mode2|Mode 2]], the "Standard Installation" option.
Changed lines 15-16 from:
-> '''Step 2:''' Using the cluster manager, take down the cluster group managing the PaperCut NG services (e.g PaperCut Application Server and PaperCut Print Provider).
to:
-> '''Step 2:''' Using the cluster manager, take down the cluster group managing the PaperCut NG services (e.g PaperCut Application Server and/or PaperCut Print Provider).
Changed lines 19-22 from:
-->[@C:\Program Files\PaperCut NG\@]

->This will upgrade the current install with an install-over-the-top procedure.  At the end of the install process, ''select''  the option to ''Open application and complete configuration''.  The browser should open to:
to:
--->[@C:\Program Files\PaperCut NG\@]

-> Match the install options as per the origional install. i.e. If the cluster is [[https://www.papercut.com/products/ng/manual/ch-clustering-microsoft.html#cluster-mode1|Mode 1]] installed the "Secondary Server" option, or if [[https://www.papercut.com/products/ng/manual/ch-clustering-microsoft.html#cluster-mode2|Mode 2]], the "Standard Installation".

->This will upgrade the current install with an install-over-the-top procedure.  If prompted at
the end of the install process, ''select''  the option to ''Open application and complete configuration''.  The browser should open to:
Changed lines 1-2 from:
(:title Upgrading PaperCut NG in a Microsoft Cluster Environment :)
to:
(:title Upgrading PaperCut NG in a Microsoft Cluster Environment:)
Changed lines 38-40 from:

''Categories:'' [[!PaperCutNG]], [[!Administration]], [[!Upgrading]]
to:
----
''Categories:'' [[Category.Administration|+]], [[Category.Upgrading|+]]
Changed lines 25-26 from:
-> '''Step 4:''' The installer will start the application server.  On first startup after an upgrade, the server may need to perform some data upgrade tasks.  The browser window may inform you of this upgrade status - Keep pressing the browser's refresh button to update the status.  If/when you can see the standard login box, the upgrade as completed.  Do '''not''' precede to the next step until the data upgrade has completed.  This may take a few minutes on large databases.
to:
-> '''Step 4:''' The installer will start the application server.  On first startup after an upgrade, the server may need to perform some data upgrade tasks.  The browser window may inform you of this upgrade status - Keep pressing the browser's refresh button to update the status.  If/when you can see the standard login box, the upgrade has completed.  Do '''not''' precede to the next step until the data upgrade has completed.  This may take a few minutes on large databases.
Changed lines 21-22 from:
->This will upgrade the current install with an install-over-the-top procedure.  At the end of the install process, ''select''  the option to ''Open application and complete configuration''.  The browser should open to [=http://localhost:9191/=] .
to:
->This will upgrade the current install with an install-over-the-top procedure.  At the end of the install process, ''select''  the option to ''Open application and complete configuration''.  The browser should open to:

-->[@http:
//localhost:9191/@]
Changed lines 21-24 from:
->This will upgrade the current install with an install-over-the-top procedure.  At the end of the install process, ''unselect'' (turn off) the option to ''Open application and complete configuration''

-> '''Step 4:''' Repeat the install-over-the-top procedure outlined in the previous step on each relevant node on the cluster
.
to:
->This will upgrade the current install with an install-over-the-top procedure.  At the end of the install process, ''select''  the option to ''Open application and complete configuration''.  The browser should open to [=http://localhost:9191/=] .

-> '''Step 4:''' The installer will start the application server.  On first startup after an upgrade, the server may need to perform some data upgrade tasks.  The browser window may inform you of this upgrade status - Keep pressing the browser's refresh button to update the status.  If/when you can see the standard login box, the upgrade as completed.  Do '''not''' precede to the next step until the data upgrade has completed.  This may take a few minutes on large databases
.
Changed lines 30-36 from:
->Repeat this for each node in the cluster and ensure the services are stopped on all nodes.

-> '''Step 6:''' Open
the cluster manager and bring online the cluster group hosting the PaperCut services.

-> '''Step 7:
''' Log into PaperCut and ensure the system is working as expected.  Testing should include performing simple administration tasks, testing printing and simulating node failure.  Administrators may also find the [[PostUpgradeTestPlan | post upgrade test plan]] useful.

to:
-> '''Step 6:''' Repeat steps '''3''' through '''5''' undertaking the install-over-the-top procedure on each relevant node on the cluster.

-> '''Step 7:''' Open
the cluster manager and bring online the cluster group hosting the PaperCut services.

-> '''Step 5
:''' Log into PaperCut and ensure the system is working as expected.  Testing should include performing simple administration tasks, testing printing and simulating node failure.  Administrators may also find the [[PostUpgradeTestPlan | post upgrade test plan]] useful.

Changed lines 34-36 from:
-> '''Step 7:''' Log into PaperCut and ensure the system is working as expected.  Testing should include performing simple administration tasks, testing printing and simulating node failure.  Administrators may also find the [[PostUpgradeTestPlan | post install test plan]] useful.

to:
-> '''Step 7:''' Log into PaperCut and ensure the system is working as expected.  Testing should include performing simple administration tasks, testing printing and simulating node failure.  Administrators may also find the [[PostUpgradeTestPlan | post upgrade test plan]] useful.

Changed lines 34-36 from:
-> '''Step 7:''' Log into PaperCut and ensure the system is working as expected.  Testing should include performing simple administration tasks, testing printing and simulating node failure.

to:
-> '''Step 7:''' Log into PaperCut and ensure the system is working as expected.  Testing should include performing simple administration tasks, testing printing and simulating node failure.  Administrators may also find the [[PostUpgradeTestPlan | post install test plan]] useful.

Changed lines 19-20 from:
-->[@c:\Program Files\PaperCut NG\@]
to:
-->[@C:\Program Files\PaperCut NG\@]
Changed lines 23-24 from:
-> '''Step 4:''' Repeat the install-over-the-top procedure outlined in the previous step on each relevent node on the cluster.
to:
-> '''Step 4:''' Repeat the install-over-the-top procedure outlined in the previous step on each relevant node on the cluster.
Changed lines 7-8 from:
#A cluster is composed of 2 or more nodes.  '''All''' nodes need to be upgraded at the same time.
to:
#A cluster is composed of 2 or more nodes.  ''All'' nodes need to be upgraded at the same time.
Changed lines 5-8 from:
# The installer needs to stop the PaperCut services before performing the install-over-the-top. In a cluster environment, these services are controlled by cluster management software rather than by the local system.  The services need to be manually stopped prior to the installed.

#A cluster is composed of 2 or more nodes.  All
nodes need to be upgraded at the same time.
to:
# The installer needs to stop the PaperCut services before performing the install-over-the-top. In a cluster environment, these services are controlled by cluster management software rather than by the local system.  The install will not have access to the cluster resources so for this reason, the services need to be manually stopped prior to the procedure.

#A cluster is composed of 2 or more nodes.  '''All'''
nodes need to be upgraded at the same time.
Changed lines 13-14 from:
-> '''Step 1:''' '''BACKUP NOW!''' - an upgrade is a system change and like all major system changes should be conducted with care.  We recommend taking time now to backup the PaperCut database using the system's point-in-time backup procedure ([@ Options -> Backups -> Backup Now @], as well as a general backup of the current PaperCut install directory (e.g. a Zip archive).
to:
-> '''Step 1:''' '''BACKUP NOW!''' - an upgrade is a system change and like all major system changes should be conducted with care.  We recommend taking time now to backup the PaperCut database using the system's point-in-time backup procedure ([@ Options -> Backups -> Backup Now @]), as well as a general backup of the current PaperCut install directory (e.g. a Zip archive).
Changed lines 3-4 from:
The upgrade procedure in a Microsoft Cluster environment is a little different from the standard upgrade procedure.  The reasons for this are:
to:
If PaperCut NG is running in a Microsoft Cluster environment, the upgrade procedure is a little different from the standard upgrade procedure.  The reasons for this include:
Changed lines 1-2 from:
(:title Upgrading PaperCut NG in a Microsoft Cluster :)
to:
(:title Upgrading PaperCut NG in a Microsoft Cluster Environment :)
Changed lines 37-38 from:

to:
''Categories:'' [[!PaperCutNG]], [[!Administration]], [[!Upgrading]]
Added lines 1-38:
(:title Upgrading PaperCut NG in a Microsoft Cluster :)

The upgrade procedure in a Microsoft Cluster environment is a little different from the standard upgrade procedure.  The reasons for this are:

# The installer needs to stop the PaperCut services before performing the install-over-the-top. In a cluster environment, these services are controlled by cluster management software rather than by the local system.  The services need to be manually stopped prior to the installed.

#A cluster is composed of 2 or more nodes.  All nodes need to be upgraded at the same time.

This upgrade procedure is designed to compliment the [[UpgradingNG | standard upgrade procedure]].  The reader should familiarize themselves with the standard upgrade procedure before preceding.



-> '''Step 1:''' '''BACKUP NOW!''' - an upgrade is a system change and like all major system changes should be conducted with care.  We recommend taking time now to backup the PaperCut database using the system's point-in-time backup procedure ([@ Options -> Backups -> Backup Now @], as well as a general backup of the current PaperCut install directory (e.g. a Zip archive).

-> '''Step 2:''' Using the cluster manager, take down the cluster group managing the PaperCut NG services (e.g PaperCut Application Server and PaperCut Print Provider).

-> '''Step 3:''' On one cluster node, run the latest version of the PaperCut NG setup program and install into the same location as the current install on this node.  Normally:

-->[@c:\Program Files\PaperCut NG\@]

->This will upgrade the current install with an install-over-the-top procedure.  At the end of the install process, ''unselect'' (turn off) the option to ''Open application and complete configuration''

-> '''Step 4:''' Repeat the install-over-the-top procedure outlined in the previous step on each relevent node on the cluster.

-> '''Step 5:''' Open the local system's ''Service Manager'' via [@ Control Panel -> Administrative Tools -> Services @] and  ensure that the following services are ''Stopped'':

-->[@PaperCut Application Server@]
-->[@PaperCut Print Provider@]

->Repeat this for each node in the cluster and ensure the services are stopped on all nodes.

-> '''Step 6:''' Open the cluster manager and bring online the cluster group hosting the PaperCut services.

-> '''Step 7:''' Log into PaperCut and ensure the system is working as expected.  Testing should include performing simple administration tasks, testing printing and simulating node failure.



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 July 05, 2018, at 07:23 PM
Printable View   |   Article History   |   Edit Article