Redundancy

Setting up Redundancy

Currently, the only supported redundancy is a manual failover to warm standby configuration. With a failover to warm standby configuration you have two servers with Printer Installer installed: primary and secondary. The primary hosts an IP address for the Printer Installer application that is referenced with a DNS host record (example: print.domain.com). The Printer Installer client is setup to use the URL when contacting the Printer Installer server and users use the URL to access the Printer Installer Portal for self-service printer installation. The secondary server is updated regularly (warm standby) with the primary's database. Upon failure of the primary, you load the Printer Installer IP address on the secondary server, enabling the secondary to service all Printer Installer requests and administrator changes until the primary server can be brought back online.

Setup

To setup Printer Installer for manual failover to warm standy redundancy, do the following:

  1. Install and configure Printer Installer on the server that will be the primary Printer Installer server.
  2. Add an IP address to the server that will be used to access the Printer Installer resource.
  3. Create a DNS host record (example: print.domain.com) pointing to the Printer Installer IP address.
  4. Setup Printer Installer Clients to use the host record for the HOMEURL command-line option. Also, have any links that will open the Printer Installer Portal refer to the host record.
  5. Install Printer Installer on the server that will be the secondary Printer Installer server, do not configure the secondary server because all configurations will be overwritten in the next step.
  6. Export the Printer Installer database from the primary server and import it to the secondary server. Schedule this step to happen regularly or perform this step every time a change is made to the primary server’s Printer Installer configuration.


Failover to Secondary

To perform the manual failover to the secondary warm standby Printer Installer server, do the following:

  1. Disable importing the primary server’s database to the secondary server.
  2. Enable the Printer Installer resource IP address on the secondary server. The secondary server will now service all Printer Installer requests and allow changes to be made in the Administrator.


Restore to Primary

To bring the Printer Installer resource back to the primary server after manually failing the Printer Installer resource to the secondary server, do the following:

  1. Make sure the Printer Installer resource IP address will not be enabled when the primary server is brought up.
  2. Bring the primary server up. If changes were made while the primary server was down, export the secondary Printer Installer server’s database and import it to the primary server. This will update the primary servers database with any changes that were made while the secondary server was hosting PI.
  3. Disable the Printer Installer resource IP address on the secondary server and enable it on the primary server.
  4. Re-enable importing the primary server’s database to the secondary server.