Load Balancing Among Servers
We cannot afford a server failure. Can we cluster the printing solution and balance the server load?
The basic feature of a SafeQ cluster is the absolute independent nature of its operation system. Since it works on the application level, neither the clustering of the operation system (Linux or Windows) nor a database is required. And what's more, the SafeQ cluster also provides fail-over among the nodes in the cluster.
Clustering and load-balancing with SafeQ
| higher efficiency thanks to internal logic |
Nodes can be added to the cluster continuously, enabling the creation of what could be called a "server farm". There are 2-5 nodes in one cluster anticipated. The cluster is fully redundant, i.e. none of the servers is a primary server. Therefore, in the case of a server failure, the system remains in full operation (unless all of the servers have failed).
In the event of a server failure, data can be lost only of those tasks that are being saved and/or processed on the server in the given moment (depending on configuration and infrastructure). However, this fact does not limit the print environment in any way. For the cluster function, a client - SafeQ port is to be installed on all client stations (mass deployment available). This client takes care of sending jobs to one of the print servers in the cluster.