OpManager DE Failover For Central Server

It is very very essential, at the same time quite difficult to ensure 100% availability of the Central server. There are chances of DB getting crashed, Server going down etc., where your effective monitoring gets halted. If the Central DB crashes, it takes hours (depending on the data size) to restore and resume the service. Also, it is very complicated and time consuming to take backups of the Central, periodically. As the data grows more and more, the complication and the time in taking backups also grows more and more.

Failover is the best and the recommended technique to overcome these issues and to achieve 100% availability of the Central Server.

You can configure failover at the following cases

Configuring Failover at the Initial stage i.e., immediately after fresh installation.
Configuring Failover at the Later stage i.e., at the stage where the product has been running for quite some time.

Note: Failover configuration steps are same for the above two cases. So you may configure failover setup any point of time.

Steps to configure the failover:

In Primary Central server

1. Execute the script 'FailoverSetup.bat/sh' which is present under <OPM Home>/bin from the command prompt
2. Follow the steps in the prompt and configure the primary central server
3. Once primary configuration was over, copy the 'https.truststore' from <primary_central_home>\conf directory and save it in failover central server machine where you want to configure failover setup

In Failover Central Server

1. Execute the script 'FailoverSetup.bat/sh' which is present under <OPM Home>/bin from the command prompt

2. Give the absolute path of the 'https.truststore' file which was taken from primary central while configuring failover central server

3. Follow the steps in the prompt and configure the failover central server

4. Once failover configuration was over, copy the 'https.truststore' from <Failover_central_home>\conf directory and overwrite the same in <primary_central_home>\conf directory

5. To check whether the DB replication has started for both the Primary and Failover Central DB do the       following

        1. Open the file <machinename>.err [<central_home>\mysql\data] both in the Primary and                           Failover server.

        2. Check for the entry 'Replication started'. If the entry is available, then replication is successfully                 done.

6. Start the Primary Central server and then Failover Central Server. There after Failover Central             server will be ready to takeover as and when Primary Central fails

In Probe Server

1. Copy the 'https.truststore' from <Failover_central_home>\conf directory and overwrite the same in <Probe_Home>\conf as well as copy the <Failover_central_home>\conf\probe \defaultToNewProbes\conf folder(this will be helpful for future probe created) and forcefully run the script 'ssl_gen.bat' which is present under <Probe_Home>\bin as follows

ssl_gen.bat -f

2. Open the file NOCServerDetails.xml [<probe_home>\conf] and add the following after                             DMSID="<DMSID>".

    StandbyNOCServerName="<Failover Central Server Name>"

    StandbyNOCServerPort="<Port number of the Failover Central Server>"

    SwitchOverInterval="<Time period after which the probe will start communicating with the                 Failover Central server>"

    Retries="<Count after which the probe will start communicating with the Failover Central                 server>"

    ReEstablishInterval="<Count after which the probe will contact the Primary Central server,             once the connection is lost with Primary Central server >"

2. Now start the Probe server.

Attachments (2)

RSS of this page