Viewing Diagnostic Information about Both Units

Mirth® Appliance by NextGen Healthcare Deployment Guide, 4.1

Set Up Automatic Failover

Automatic failover enables you to move an application to a standby server during a failure. Before you begin You need an unused IP address to assign as the database virtual IP (VIP) address. This VIP must be in the same IP network as the appliances. You should ensure it's not already in use on your network, for example, by using the ping command and verifying you receive no responses. If you have any questions, contact your network administrator or NextGen Healthcare Support. After setting up replication, you can set up automatic failover for both the primary system and the standby system. Set up the first appliance (the primary). Go to Services > Postgres > Replication. Select Set up Auto Failover. Enter your database VIP. Select Enable. The window reloads automatically. Watch the window to ensure it eventually shows the “Actively managing the VIP” status. Auto Failover window Set up the second appliance (the standby). Go to Services > Postgres > Replication. Select Set up Auto Failov

Mirth® Connect by NextGen Healthcare Advanced Clustering User Guide

Set Up Automatic Failover

Automatic failover maximizes the availability of the Virtual IP address by switching to a standby server during a failure or service event. Use the following steps to set up automatic failover on the primary and secondary appliances. On the primary appliance, select Services > Postgres > Replication, and select Set up Auto Failover. Enter a virtual IP address for the database and a notification email address, then select Enable. On the secondary appliance, select Services > Postgres > Replication, and select Set up Auto Failover. Enter the same virtual IP address and email address you used for the primary appliance, and select Enable. Parent topic: Download the Advanced Clustering Plug-in

Mirth® Appliance by NextGen Healthcare Deployment Guide, 4.1

Postgres Replication Advanced Configuration

Use the Postgres Replication Advanced window to edit various replication-related configuration files. You can edit various configuration files. Select Services > Postgres > Replication > Advanced to go to the Postgres Replication Advanced window. CAUTION: It is recommended that you only edit the configuration files after contacting NextGen Healthcare Support. Postgres Replication Advanced window Parent topic: Replicate the Database

Mirth® Appliance by NextGen Healthcare Deployment Guide, 4.1

Using the Postgres Service

With the Postgres service, you can create additional databases for other uses, set up replication of the database, view logs, and view current database queries. Select Services > Postgres to open a sub-menu. If you select Postgres, it is the same as selecting the first entry in the sub-menu, Database Management. The other entries in the sub-menu are shortcuts to actions that are available using buttons on the Database Management window. Postgres menu An instance of PostgreSQL (or Postgres) runs on the appliance that is used by Mirth® Connect. With the Postgres service, you can create additional databases for other uses, set up replication of the database, view logs, and view current database queries. Note: The functionality associated with the Replication button, which enables you to create a duplicate of the database that can be used as a backup in case of a failure, is described in detail in the Replicate the Database section. After setting up replication, you can then begin Set Up A

Mirth® Appliance by NextGen Healthcare Deployment Guide, 4.1

Replicate the Database

You can use replication to designate a secondary appliance that contains a copy of the database that is on your primary appliance. After everything is set up, and the initial copy of the database is created on the secondary system, updates made to the database on the primary system ripple through to the replica database on the secondary system. Note: Even though "database" is referred to in the singular, all databases contained in the Postgres instance on the primary system would be replicated. You can view the list of these databases on the Database Management window. One of the principal reasons for setting up replication is so that the secondary database can be used as a failover system if the primary database becomes unusable. For this reason, the secondary database is frequently referred to as a standby database, because it is ready and waiting, standing by in case it is needed. It is also possible to set up multiple standby databases for the same primary database. For more inform

Mirth® Connect by NextGen Healthcare Advanced Clustering User Guide

Enable Postgres Replication

Before you begin Select a secondary appliance in your cluster to replicate from a primary appliance, and verify that the Postgres service is running on the primary appliance. Postgres replication is the process of copying data from one database server to another. The source database is also known as the “primary” database, and the database receiving the copied data is known as the “secondary” database. On your secondary appliance, select Services > Postgres > Replication, and select Replicate from a remote database. Enter the appliance's IP address, and select Next. Select Next again. You are redirected to the primary appliance to authorize replication Select Authorize <IP address of secondary> to replicate this database, then select Next to return to the secondary appliance. Select Begin Copy to perform the initial copy of the database from primary to secondary, then, if you are ready to copy and you have backed up the secondary's database (if needed), select OK. When the copy is comp

Viewing Diagnostic Information about Both Units

Recommendations

Set Up Automatic Failover

Set Up Automatic Failover

Postgres Replication Advanced Configuration

Using the Postgres Service

Replicate the Database

Enable Postgres Replication

Viewing Diagnostic Information about Both Units

Set Up Automatic Failover

Set Up Automatic Failover

Postgres Replication Advanced Configuration

Using the Postgres Service

Replicate the Database

Enable Postgres Replication