Microsoft Failover Cluster Manager (MSFCM) on Windows 2008 R2
Microsoft Windows 2008 R2 offers clusteringClustering allows your organisation to ensure your services are not affected if anything should happen to your main server. PaperCut is a cluster compatible application and is supported under Windows (Microsoft Cluster Server / MSCS, Microsoft Failover Cluster Manager / MSFCM, Vetitas Cluster Server / VCS) and Linux (Novell Cluster Services / NCS, Linux-HA) at all levels of the application, including: clustering at the print spooler service layer by integrating with clustering services, failover based clustering at the Application Server layer using clustering services, and at the database layer by utilising cluster aware databases such as Microsoft SQL Server, PostgreSQL, or Oracle. capabilities through its Microsoft Failover Cluster Manager (MSFCM)The Microsoft Failover Cluster Manager (MSFCM) snap-in validates failover cluster configurations, creates and manages failover clusters, and migrates some resource settings to a cluster running Windows Server 2008 R2..
This section documents the setup for Microsoft Failover Cluster Manager. Sites using Veritas Cluster Server (VCS) on Windows or Novell Cluster Services (NCS) on Novell OES Linux should jump to their respective sections.
This section assumes that you have an already installed and working clustered server environment.
Mode 1 is the simplest configuration and is suitable for most organizations. It implements clustering in the
front line, that is, the printer and print monitoring layer. The cluster print serverA print server is a system responsible for hosting print queues and sharing printer resources to desktops. Users submit print jobs to a print server rather then directly to the printer itself. A print server can be a dedicated server but on many networks this server also performs other tasks, such as file serving is configured as a secondary print server reporting back to a primary PaperCut server hosted on another system outside the cluster.
Mode 2 implements clustering on all levels of the application for maximum fault tolerance - In addition to the print queues, the PaperCut Application ServerAn Application Server is the primary server program responsible for providing the PaperCut user interface, storing data, and providing services to users. PaperCut uses the Application Server to manage user and account information, manage printers, calculate print costs, provide a web browser interface to administrators and end users, and much more. is also hosted in the cluster. Mode 2 is somewhat more demanding to configure and should only be attempted by organizations with staff experienced with advanced cluster and database management.
Refer to the subsequent sections for an explanation on how to set up Mode 1 or Mode 2 in your environment.
Windows Server 2008 R2 installations might experience a Windows bug where print jobs are not removed from the print queueA print queue displays information about documents that are waiting to be printed, such as the printing status, document owner, and number of pages to print. You can use the print queue to view, pause, resume, restart, and cancel print jobs. when completed. For more information, see Windows Server 2008 R2 only. Perform this work around on the clustered print server, not the nodes.
Mode 1 - Clustering at the print layer
Windows 2012 no longer support high-availability of printing servers using Failover Cluster Manager. Microsoft now only supports printing high availability through the use of highly available VM clusters. This is described in detail in the Microsoft document High Availablity Printing Overview. You should also review Virtual Machine clustering for more information on VM clustering. To set up Mode 1 clustering on Windows 2012 the printer server must be installed on a highly available VM cluster. The remainder of this section described setting up Mode 1 on Windows 2008.
Step 1 - Application Server (primary server) setup
Install the Application Server component (Standard Install option) on your nominated system. This system is responsible for providing PaperCut NG's web based interface and storing data. In most cases this system will not host any printers and is dedicated to the roll of hosting the PaperCut Application Server. It might be one of the nodes in the cluster; however, a separate system outside the cluster is generally recommended. An existing domain controller, member server or file server will suffice.
Step 2 - Installing the Print Provider components on each node
The Print ProviderA Print Provider is a monitoring service installed on a secondary print server to allow PaperCut to control and track printers. This monitoring component intercepts the local printing and reports the use back to the primary Application Server. component needs to be separately installed on each node involved in the print spooler cluster. This is done by selecting the Secondary Print Server option in the installer. Follow the secondary serverA PaperCut secondary server is a system that directly hosts a printer, that is, a print server with a Print Provider installed. A secondary server can be a server style system hosting many printers, a desktop style system hosting printer(s) also shared to other network users, or a desktop style system with the printer used only for local users (not shared). set up notes as detailed in Configuring secondary print servers and locally attached printers . Take care to define the correct name or IP address of the nominated Application Server set up in step 1.
Step 3 - Decouple service management from nodes
By default the Print Provider component is installed under the management of the node. To hand over management to the cluster, the service start-up type needs to be set to manual. On each node navigate to Control Panel > Administrative Tools > Services, locate the PaperCut Print Provider service. Stop the service and set the start-up type to Manual. Repeat for each node in the cluster.
Step 4 - Adding the Print Provider service as a resource under the print spooler's cluster group
Open the Failover Cluster Manager.
Right-click the cluster group hosting the spooler service; then select Add a resource > 4 - Generic Service.
In the new resource wizard, select the name PaperCut Print Provider; then click Next.
Click Next at Confirmation.
Click Finish at Summary.
Right-click the PaperCut Print Provider; then click Properties. On the PaperCut Print Provider Properties page ensure the Use Network Name for computer name option is selected.
Next, click the Dependencies tab and ensure the Print Spooler is added as a resource.
Right-click the PaperCut Print Provider; then click Bring this resource online.
Step 5 - Shared active job spool
To ensure the state of jobs currently active (e.g. held in a hold/release queue) are not lost during a failover event, PaperCut NG is able to save job state in a shared drive/directory. If a shared disk resource is available and can be added to the cluster resource, PaperCut can use this to host a shared spool directory to ensure no active job state is lost.
Add a shared drive to the cluster resource. e.g. (Q: drive). It is advisable to use the same drive as used for the shared print spool directory.
Create a directory in this drive called PaperCut\Spool
On each node, edit the file: [app-path]/providers/print/win/print-provider.conf and add a line pointing to the shared active job spool directory:
Change the drive letter as appropriate.Important:
If running an "Active-Active" print cluster you must use a separate active job spool directory for each node. To configure this use the %service-name% value in the SpoolDir setting. The %service-name% value is replaced by the service name of the running PaperCut Print Provider instance. e.g.
See below for details on "Active-Active".
Restart the cluster resource to ensure the change is picked up.
Step 6 - Test
Perform operations to verify that:
Print jobs are logged as expected.
There is no error message in the Print Providers text log located at: C:\Program Files\PaperCut NG\providers\print\win\print-provider.log on each node.
Active/Active clustering - multiple virtual servers
On large networks it is common to distribute load by hosting print spooler services under two or more virtual servers. For example, two virtual servers might each host half of the organization's printers and share the load. This is sometimes referred to as Active/Active clustering - albeit not an entirely correct term, as the print spooler is still running in Active/Passive.
Virtual servers cannot share the same service on any given node. For this reason if the virtual servers share nodes, you need to manually install the PaperCut Print Provider service a second time under a different name. You can do this with the following command line:
cd \Program Files\PaperCut NG\providers\print\win pc-print.exe PCPrintProvider2 /installThe argument preceding /install is the unique name to assign to the service. The recommended procedure is to suffix the standard service name with a sequential number. Repeat this on each physical node. Use a unique service name for each "active" virtual server hosted in the cluster group.
Make sure that you have unique SpoolDir settings for each node of your cluster. Ensure that the SpoolDir setting in the print-provider.conf file has a %service-name% expansion variable as explained above. This ensures that each service has it's own spool directory.
Mode 2 - Clustering at all application layers
Mode 2 implements failover clustering at all of PaperCut NG's Service Oriented Architecture software layers, including:
Clustering at the Print monitoring layer
Clustering at the Application Server layer
Optional clustering at the database layer
Mode 2 builds upon Mode 1 by introducing failover (Active/Passive) clustering in the Application Server layer. This involves having an instance of the Application Server on each of the cluster nodes. When one node fails, the other automatically takes over the operation. Both instances use a share data source in the form of an external database (see Deployment on an external database (RDBMS)). Large sites should consider using a clustered database such as Microsoft SQLStructured Query Language (SQL) is a special-purpose programming language designed for managing data held in a relational database management system (RDBMS), or for stream processing in a relational data stream management system (RDSMS). Server.
This section assumes that you have an already installed and working Service and Application group hosting a clustered printing environment.
Step 1 - Application Server installation
On one of the cluster's nodes, install the PaperCut Application Server component by selecting the Standard Install option in the installer. Follow the setup wizard and complete the process of importing all users into the system.
Step 2 - Convert the system over to an external database
The system needs to be configured to use an external database as this database is shared between both instances of the Application Server. Convert the system over to the required external database by following the procedure detailed in Deployment on an external database (RDBMS). The database can be hosted on another system, or inside a cluster. As per the external database set up notes, reference the database server by IP address by entering the appropriate connection string in the server.properties file.
Step 3 - Setup of 2nd node
Repeat steps 1 and 2 on the second and any subsequent cluster nodes.
Step 4 - Distributing application license
Install your license on your 2nd node and any subsequent cluster nodes. To do this:
- Log in to the Admin web interface by browsing to http://[IP-Address-Of-Your-Node]:9191/admin.
- Click the About tab.
- In the Register area, click Browse.
- Locate the license file.
- Click Install license.
- Verify that the license information is correctly listed on the About page.
Step 5 - Decouple service management from the nodes
By default the PaperCut Application Server component is installed under the management of the node. It needs to be managed inside the cluster, so set the service's start-up type to manual. On each node navigate to Control Panel > Administrative Tools > Services locate the PaperCut Application Server. Stop the service and set its start-up type to Manual. Repeat this on all nodes.
Step 6 - Create a new Services and Applications group
Create a new Services and Applications group containing the two nodes. Make note of the IP Address that you assign as you will use it later. Add the Generic Service PaperCut Application Server. Give the Client Access Point an appropriate title such as PaperCutAppCluster.
This Services and Applications group is separate to the existing clustered printing environment. It is recommended to set up two Services and Application groups where you can later set the node affinity to better distribute the application load across nodes.
Step 7 - Configure PaperCut Application Server
- Right-click the PaperCut Application Server; then click Properties.
On the PaperCut Application Server Properties page, select the Use Network Name for computer name.
On the Dependencies tab make sure the Service and Application group is added as a Resource.
Step 8 - Confirm PaperCut Application Server active
Right-click the Service and Applications group; then select Bring online. Wait until the Application Server has started, then verify that you can access the system by pointing a web browser to:
http://[Virtual Server Name]:9191/adminLog in, and perform some tasks such as basic user management and User/Group Synchronization to verify the system works as expected.
Step 9 - Set up the Print Provider layer
Set up the Print Provider as described in Mode 1 - Clustering at the print layer. The exception being that the IP address of the Application Server is the IP address assigned to the Virtual Server.
Step 10 - Client configuration
The client and Release StationPrint Release Stations place a print job on hold and allow users to release it when required. Often a Release Station is a dedicated PC terminal located next to the printers, however, Release Stations can take other forms such as a web browser based interface. Some common examples where Release Stations can be used include secure printing, approved printing, and authentication. In a secure printing environment jobs are only printed when the user arrives at the print area and confirms his or her identity. This ensures the user is there to collect the job and other users can't "accidentally" collect the document. In some organizations it may be appropriate to hold jobs until they are approved by selected individuals. A good example would be a teacher approving printing on an expensive color printer. Hold/Release queues can be used as a form of authentication in an unauthenticated environment. Users must authenticate prior to releasing their jobs allowing PaperCut NG to confirm their identity. programs are located in the directories:
Step 11 - Test
Mode 2 setup is about as complex as it gets! Take some time to verify all is working and that PaperCut NG is tracking printing on all printers and all virtual servers.
Advanced: Load distribution and independent groups
Separating these resources into to groups, running on different IP addresses allows you to set up different node affinities so the two groups usually run on separate physical nodes during normal operation. This ensures the load is spread across multiple nodes.
To make this change after setting up the single group Mode 2 configuration:
Set the Preferred owners of each Services and Applications group to different physical nodes.
Restart or bring on line each group, and independently test operation and operation after fail-over.
Take some time to simulate node failure. Monitoring can stop for a few seconds while the passive server takes over the role. Simulating node failure is the best way to ensure both sides of the Active/Passive setup is configured correctly.
It is important that the version of PaperCut running on each node is identical. Ensure that any version updates are applied to all nodes so versions are kept in sync.
The PaperCut installation sets up a read-only share exposing client software to network users. If your organization is using the zero-install deployment method, the files in this share are accessed each time a user logs onto the network. Your network might benefit from exposing the contents of this share via a clustered file share resource.
PaperCut regularly saves transient state information (such as print job account selections) to disk so that this state can be recovered on server restart. If failing over to a new cluster server, you should ensure this state information is saved to a location available to the new server.
By default the state information is located in [app-path]/server/data/internal/state/systemstate. You can change this location if required by setting the property server.internal-state-path in your server.properties file.
Additional configuration to support Web Print
By default the Application Server looks in [app-path]\server\data\web-print-hot-folder for Web PrintWeb Print enables printing from user-owned devices without the need to install printer drivers and manage server authentication. files. This location is generally available only on one node in the cluster. To support Web Print in a cluster, add a Shared Folder on the Shared Storage in your cluster. This can be done on the same disk that the spool files reside and the Print Provider point to.
To change this location, use the Config editor and modify the web-print.hot-folder key.
Add a Shared Folder on the Shared Storage, an example would be E:\web-print-hot-folder and share it as \\clustername\web-print-hot-folder\.
In the Admin web interface, click the Options tab.
- In the Actions menu, select Config editor.
Modify web-print.hot-folder to E:\web-print-hot-folder
Map your selected network drive on the Web Print Sandbox machine to \\clustername\web-print-hot-folder\
Add all relevant printer queues from \\clustername\web-print-hot-folder\ to the Web Print Sandbox server.
Additional configuration to support Print Archiving
If you have enabled Print Archiving (viewing and content capture), the Applications Server stores archived print jobs in [app-path]\server\data\archive. This location is generally only available on one node in the cluster. To support Print Archiving in a cluster, add a Shared Folder on the Shared Storage in your cluster. This location must be accessible to all cluster nodes and also any print servers that are collecting print archives.
For instructions for moving the archive location see Phase 1: Moving the central archive:. This describes how to configure both the Application Server and your print servers to use the same shared storage location.