Monitoring High Availability using Password Manager Pro |
Sl. No: | UI Element/Icon | Status | Definition |
---|---|---|---|
1 |
Active |
This blinking icon indicates that the HA is actively running in the server (Primary/Secondary) which you are viewing right now. |
|
2 |
Inactive |
This blinking icon indicates that the HA is down in the server (Primary/Secondary) which you are viewing right now. |
|
3 |
Success |
This icon indicates that HA is configured successfully in your server. In the case of HA configuration failure, this screen will be shown. |
|
4 |
|
This icon denotes the Primary server. |
|
5 |
|
This icon denotes the Secondary server. |
|
6 |
Configuration Details |
|
This is a table listing the following details of Primary and Secondary servers; Server Name, Server Port and Actions. You can modify the Secondary server details from here. (Please note that you cannot edit the Primary server details) |
7 |
Primary/Secondary Server |
This icon indicates that the Primary/Secondary server is up and running. |
|
This icon indicates that the Primary/Secondary server is down and stopped running. |
|||
8 |
Primary/Secondary Server PostgreSQL |
This icon indicates that the PostgreSQL database of Primary/Secondary server is up and running. |
|
This icon indicates that the PostgreSQL database of Primary/Secondary server is down and stopped running. |
|||
9 |
Replication Pending Count |
|
This indicates the total number of pending replications. If this value is zero, it means that there are no replications pending and the Primary and Secondary server are continuously in sync with each other. |
10 |
Connection Lost Time |
|
This indicates the time when the connectivity between the Primary and Secondary servers was lost. |
11 |
Connection Resumed Time |
|
This indicates the time when the connectivity between the Primary and Secondary servers was regained. |
The basic concept underlying HA is constant replication of data between the Primary and Secondary servers, where the Primary acts as the "Master" and the Secondary as the "Slave". The "Status" corresponds to the condition of the connection/communication between the Primary and Secondary servers/databases. There are two types of HA status:
1. Active - Indicates perfect data replication and data synchronization between the Primary and Secondary servers.
2. Inactive - Indicates a breakage in connectivity between the Primary and Secondary servers. The breakage might be due to a disruption such as network problem between the servers (in turn between the databases). Due to this, there will be no communication between the databases of Primary and Secondary servers and the data replication and data synchronization between the servers will get disturbed.
Once the connection gets re-established, the synchronization will start between the databases. Anyhow, during the network disconnectivity, those who have connected to the primary and Secondary will not face any disruption in service.
Since the above two conditions (Active/Inactive) assume importance in the HA setup, it is important to receive real-time alerts when the status turns from "Active" to "Inactive" and vice-versa. To configure alerts, navigate to "Audit >> Resource Audit >> Configure User Audit >> General Operations" and select the mode of alert (email/SNMP trap/Syslog message) for the events 'High Availability Alive' and 'High Availability Failed'.
Notes:
1. Post HA Configuration: If you change the port of the Primary Password Manager Pro server, the high availability setup will not work. You need to re-configure the setup with suitable changes.
2. If you have configured TFA: Whenever you enable TFA or when you change the TFA type (PhoneFactor or RSA SecurID or One-time password) AND if you have configured HA, you need to restart the Password Manager Pro secondary server once.
Click the icon under Actions beside the Secondary server, whose details you wish to edit. In the window that pops up modify the details as required and click Update.
Once the HA status becomes "Inactive", the Password Manager Pro HA setup also breaks down. In case of a HA failure, contact Password Manager Pro support (passwordmanagerpro-support@manageengine.com) with the below log file:
<PMP Installation Folder>/pgsql/data/pg_log/pgsql_Mon.log
©2025, ZOHO Corp. All Rights Reserved.