Etts Absent Member.
Absent Member.
1188 views

Centralizing Iprint

I have read that centralizing iprint is not a good idea. But how many printers can one Manager really handle well?
0 Likes
4 Replies
leekie Absent Member.
Absent Member.

Re: Centralizing Iprint

Hi,

We have two print managers, each running around 600 printer agents. These sit in our DataCenter and atm run on NW6.5SP8.
We/clients don't see any performance issues, but then most of our sites have 1Gb/100Mb links to our cores.

Hope that's of use,

Matt
0 Likes
RBrownCCB Absent Member.
Absent Member.

Re: Centralizing Iprint

That depends on a number of things, Server specification, other tasks the server is doing, how many print jobs you're dealing with, etc

We have found no issue with ~200 printers running from a single Manager on a Cluster, doing ~2 million print jobs a year.

Each cluster node is running a single 2.5Ghz Intel Quad Core with 12GB of RAM.
Manager is clustered (NSS iSCSI storage) and includes Accounting integrated with the Manager and Cluster resource (Papercut)

Cluster also includes a number of high traffic storage volumes, and a significant amount of LDAP/eDir traffic, and we have not had any issues even when the node holding Print is covering the storage work of other failedover cluster nodes.

We only spread our printers out to other servers when it makes geographic sense - we have a number of smaller sites after our main one with 200 printers. Those smaller sites have their own Manager.

Richard Brown // Systems Engineering Team Leader // City College Brighton and Hove
0 Likes
Etts Absent Member.
Absent Member.

Re: Centralizing Iprint

Thank you we should be able to handle things then... We were just debating the whole centralization project. But we are only at about 300 printers currectly so we should be good. Moving to a cluster shortly that will improve load balancing.
0 Likes
RBrownCCB Absent Member.
Absent Member.

Re: Centralizing Iprint

Great. Please be aware that currently, Clustered iPrint does not support two Managers/Driver Stores operating on the same Node at the same time.

Based on Dev feedback at Brainshare however, this is being looked at both from the iPrint point of view (eg. Support for binding iPrint to cluster IP addresses rather than 'all') and from the Cluster point of view (The ability to configure 'exclusivity' for resources. eg. Resources in this group are not allowed to run when resources from this group are present on a node)

In the meantime, you'll just need to be aware of the potential issue and avoid loading two Managers/Stores on the same node, either by implementing advanced scripts or using node assignments so never the twain can meet.

Good luck.

Richard Brown // Systems Engineering Team Leader // City College Brighton and Hove
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.