Option 1

In this setup the Controllers are installed physically on two separate servers. This provides software redundancy to protect against any software issues. Also, automatic failover is happens if the server fails or has to be taken out for maintenance. Major highlights for this setup are below.

  • Two separate instances of Controller software are installed on two different servers.
  • External database needs to be setup for metadata repository and should be accessible by both Controller installations. 
  • It is preferred to maintain a common mount point that is accessible to both Controllers for maintaining application logs and common application scripts.
  • The heartbeat daemon runs on both servers to manage the Active-Passive status.

  • Load balancer or virtual ip can be used to switch between the Purplecube URLs and keep the Controller URLs oblivious to the user.

  • The Agents can be either installed on separate servers or on the server where Controller is installed. Each Agent installation will have separate heartbeat daemon running to manage it's status.

Option 2

In this setup the Controller is installed on common mount point (SAN) accessible to two servers and the Controller service runs only through one of the servers. This provides automatic failover if there is server failures or if it has to be taken out for maintenance. Since the Controller installation cannot get corrupted this setup helps when using VMs for software installation and having SAN to mount to these VMs. Major highlights for this setup are below.

  • Requires a common SAN mounted to both the servers.
  • Single instances of Controller software is installed on a location in SAN. The controller is started from one of the servers designated as active.
  • External or embedded metadata can be used in this setup.
  • The heartbeat daemon runs on both servers to manage the failover from active to passive server in case of server failure.

  • Load balancer or virtual ip can be used to switch between the Purplecube URLs and keep the Controller URLs oblivious to the user.

  • The Agents can be either installed on separate servers or on the server where Controller is installed. Each Agent installation will have separate heartbeat daemon running to manage it's status.

Option 3

In this setup two physical instances of Controllers are installed on the same server on two different users. This provides software redundancy to protect against any software snag or corruption. In case of hardware failure both the Controllers will not be accessible. Major highlights for this setup are below.

  • Two separate instances of Controller software are installed on same server.
  • External database needs to be setup for metadata repository and should be accessible by both Controller installations. This could be postgreSQL installation in same server or pre-existing postgreSQL installation.
  • It is preferred to maintain a common location on the server that is accessible to both Controllers for maintaining application logs and common application scripts.
  • The heartbeat daemon runs on both Controller installations to manage their Active-Passive status.

  • Load balancer or virtual ip can be used to switch between the Purplecube URLs and keep the Controller URLs oblivious to the user.

  • The Agents can be either installed on separate servers or on the server where Controller is installed. Each Agent installation will have separate heartbeat daemon running to manage it's status.