Download Print Usage Pro Implementation Best Practice Guide

Survey
yes no Was this document useful for you?
   Thank you for your participation!

* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project

Document related concepts

Oracle Database wikipedia , lookup

Microsoft Access wikipedia , lookup

Database wikipedia , lookup

Tandem Computers wikipedia , lookup

SQL wikipedia , lookup

Relational model wikipedia , lookup

Microsoft Jet Database Engine wikipedia , lookup

Database model wikipedia , lookup

Open Database Connectivity wikipedia , lookup

Btrieve wikipedia , lookup

Clusterpoint wikipedia , lookup

Team Foundation Server wikipedia , lookup

Microsoft SQL Server wikipedia , lookup

Transcript
Print Usage Pro Implementation Best Practice Guide
To achieve maximum availability, we recommend the following setup:
1) Use separate server for Web Management, Print Server and Database.
2) Install more than one print server to share the load of monitoring service. It is
recommended to attach up to 80 printers to each Print Server. This may vary
based on the printing traffic of the printers attached as well as the CPU/Memory
used for the server.
3) The recommended hardware for the Print Server is dual CPU, Intel P4 processor
with 2 Gig of memory. Based on the printing traffic of each printer, the user can
decide how big their hard drive should be. With 300 dpi capturing, more than 2
million pages of printing can be stored onto a 200 Gig hard disk drive.
4) Make a duplicate for each Print Server and use local DNS to dynamically direct
the Print job between the two based on the availability.
5) Setup more than one SQL database and put them into a cluster. Check SQL
server web site for details. Alternatively, you can set up a real time mirror copy
of the production SQL server and synchronized the data from the Production to
Mirror Server.
6) Setup weekly process to move historical print data from Production server to a
Reporting server. This will prevent the database and the image file size become
too large. Set up a Web Management server for the historical database. This
way, the review of historical data will not create any performance issue for the
production database.