Upgrade from a previous version
This section describes the PaperCut NG/MF standard upgrade procedure. PaperCut NG/MF supports upgrades using a simple install-over-the-top procedure. Review all steps prior to commencing the upgrade procedure.
Before you start
A PaperCut NG/MF system might comprise many software components, such as secondary servers, locally installed User Clients and Release Stations. It is generally not required to upgrade these components along with an Application Server upgrade. However, we do recommend that you upgrade all components as best practice.
By contrast, all Site Servers must normally be upgraded at the same time as your Application Server.
Check the release notes to determine if a database schema upgrade is to be performed. If the release does require a database schema upgrade, allow extra time for the upgrade process.
The recommended upgrade procedure
Download the PaperCut NG/MF installer for your platform. In accordance with best practice, archive your install programs just in case you need to reinstall in the future or roll back to a previous version. Take some time to read the release notes for this version as they highlight considerations during upgrades.
Schedule approximately 10 minutes downtime. Select a time of day with minimal network activity. If there is a large volume of data in the system (for example, if the system has been running for more than a year, or there are more than 5,000 users) the upgrade takes longer. With very large installations, schedule an hour or more of downtime.
Take a point-in-time backup of the data by clicking Backup Now located under Options > Backups. This ensures you have a copy of the important data.
As a precaution on very large systems, back up the whole PaperCut NG/MF directory. Existing overnight backups might have taken care of this task, however, take a few moments to grab an up-to-date backup now. For example, create a zip archive of the directory:
C:\Program Files\PaperCut NG/MF\
or the equivalent path on Linux or Mac.
Run the installer downloaded in step 1 and install into the same location as the existing install.
When the install is complete, allow a few minutes before accessing the system. The system might perform a database upgrade and this is done in the background. If you try to access the application while a database upgrade is in progress a message displaying the upgrade status is displayed. IMPORTANT: Do not shutdown the application while an upgrade is in progress. Wait for the upgrade to complete.
After the install is complete, log in to the system and perform some tests to ensure all is working as expected and the system is monitoring user activity as expected. Sites running on Novell OES Linux are advised to restart their iPrint Print Manager.
Administrators might find the post upgrade test plan useful.