Changing HA Ports After Configuration

Changing the High Availability Port

It is possible to configure High Availability to use a custom port instead of the default port 1970. After any node pair has been added, it is possible to change the synchronization port.

Launch the Windows Client, and select the top-level Management Server from the Node Navigator.

In the Configurations section, find the HA Configuration, right click and select Properties to edit.

Locate the 'ADD PROGNOSIS_HA_PAIR' configuration line for the HA Pair to change.

Update the 'haport' token value to the new port number to use.

For example:

Change the haport to 60534 for the HA Pair Pair1 on servers \server1 and \server2

ADD PROGNOSIS_HA_PAIR (ID=Pair1, primary=\server1, secondary=\server2, primarystate=active, secondarystate=passive, haport=60534)

Save the HA Configuration using the Save As button while the Properties dialog box is open. Then Start this Configuration on the Management Server and then start the configuration on the HA Pair as well.

This is done by dragging the saved copy of the HA Configuration from the 'My Displays & Configurations' folders area onto the servers in the Node tree.

For example:

In the above example, the HA Configuration needs to be started on server1 and server2

Stop the HA processes on the HA pair by changing the PROGNOSIS Configuration on both the Active and Passive servers.

Find and disable these HA processes:

SET RUN ( IRHAMGR.EXE,  N )
SET RUN ( IRHASYNC.EXE, N )

Start the PROGNOSIS Configuration on both nodes.

Start the HA processes on the HA pair by changing the PROGNOSIS Configuration on both the Active and Passive servers.

Find and enable these HA processes:

SET RUN ( IRHAMGR.EXE,  Y )
SET RUN ( IRHASYNC.EXE, Y )

Start the PROGNOSIS Configuration on both nodes.

Changing the PostgreSQL Port

It is possible to configure PrognosisPostgres to use a custom port instead of the default port 5432.

A requirement for this operation is that both PostgreSQL instances in the HA Pair must be configured with the same port.

In the postgresql.conf file located in the 'PrognosisPostgres\PostgresData' directory on both the Active and Passive servers, modify the following line to the desired port:

port = 8888             # (change requires restart)

Navigate to the 'recovery.conf' file located in the directory <PROGNOSIS_HOME>\PrognosisData\PostgresData on the Passive server

Modify the 'primary_conninfo' line to update the port.

primary_conninfo = 'user=replication password=replication host=10.116.1.13 port=8888 sslmode=prefer sslcompression=1 krbsrvname=postgres target_session_attrs=any'

Restart the PrognosisPostgres service on both the Active and Passive servers in the HA Pair.

During this time, Prognosis Server will not be able to write any data into the PostgreSQL database and data loss might occur

Launch the Windows Client, and select the top-level Management Server from the Node Navigator.

In the HA Configuration on the top-level Management Server, add a DB_NODE_INFO command for each of the servers in the HA Pair.

For example:

ADD DB_NODE_INFO is configured for 2 servers named research1 and research2 where \research1 is the active server and \research2 is the passive server

ADD DB_NODE_INFO (nodename=\research1,  write-connection-id=ResearchPairPrimaryDatabase, read-connection-id=ResearchPairPrimaryDatabase)
ADD DB_NODE_INFO (nodename=\research2,  write-connection-id=ResearchPairPrimaryDatabase, read-connection-id=ResearchPairSecondaryDatabase)

In the HA Configuration on the top-level Management Server, add a DB_CONNECTION command for each of the servers in the HA Pair with the port information configured.

For Example:

ADD DB_CONNECTION is configured for 2 servers named research1 and resarch2 using the IPv4 address on port 8888:

ADD DB_CONNECTION (id=ResearchPairPrimaryDatabase,   'driver={PrognosisPostgreSQL Unicode}', server=10.0.0.1, port=8888, database=prognosis)
ADD DB_CONNECTION (id=ResearchPairSecondaryDatabase, 'driver={PrognosisPostgreSQL Unicode}', server=10.0.0.2, port=8888, database=prognosis)

Start the HA Configuration on the top-level Management Server and also on the HA Pair servers research1 and research2

Stop the HA processes on the HA pair by changing the PROGNOSIS Configuration on both the Active and Passive servers.

Find and disable these HA processes:

SET RUN ( IRHAMGR.EXE,  N )
SET RUN ( IRHASYNC.EXE, N )

Start the PROGNOSIS Configuration on both nodes.

Start the HA processes on the HA pair by changing the PROGNOSIS Configuration on both the Active and Passive servers.

Find and enable these HA processes:

SET RUN ( IRHAMGR.EXE,  Y )
SET RUN ( IRHASYNC.EXE, Y )

Start the PROGNOSIS Configuration on both nodes.

Provide feedback on this article