Context:

Lots of customers, who do not intend the print information to leave the organizational network, ask for HCP private cloud solution within their own data centers or cloud to strengthen security.

The purpose of this article is to show the flexibilities of HCP solution to manage and handle higher load volumes with high available and resilient architecture.

Issue:

Customers demand scalability and high availability for HCP solution at the same time. They need to make sure that cloud print solution should run without any downtime in production.

Resolution:

HCP is a flexible cloud printing solution which can be configured via various ways to satisfy the customer requirements for seamless delivery. Infrastructure architecture can be changed for each case accordingly. 

Below is one of the examples of how HCP primary server can be installed and configured with high availability and better resilience.

Best Practice Recommendations:

Server: A good recommendation is to create minimum two servers (virtual/physical) as HCP primary servers. Each server needs to have own storage volume (Disk) and network interface attached. Otherwise if rebooted, virtual server can lose print or user information.

Load Balancer: Servers should be load balanced by an elastic load-balancer (you can add as many as servers behind the load-balancer if required). So, if one server is busy or down, client requests coming from internet, can be processed by the other virtual server(s).

Database: HCP comes with default database within. But for 'no adverse user experience', it is good to have an external database which would be easy to manage and audit. Create a PostgreSQL cluster within minimum 2 database instances. Also add Zookeeper for database orchestration (this is optional). The cluster should have a common DNS name to be connected from the HCP servers.

Security: Create a network security group all around HCP server group and create rules for inbound and outbound connections. This way get rid of micromanaging firewall rules for each server. Much easier process to overview the security rules from one place.

Resource Group: Put all the computing components under a single hood for easy maintenance and manageability.

For more complex customer cases, if you need any help, please contact support@everyoneproint.com.