Start and Synchronize the Original Primary Instance

Document created by RSA Information Design and Development on Jun 13, 2017Last modified by RSA Information Design and Development on Jun 13, 2017
Version 2Show Document
  • View in full screen mode

If services did not start and synchronization did not complete on your original primary after promotion for maintenance, you must start the RSA Runtime Server (biztier) on the original primary instance and synchronize this instance with the new primary instance. If the biztier service cannot be started, reset and configure the appliance as a replica instance.

Procedure 

  1. Log on to the original primary instance using SSH with the User ID rsaadmin and the current operating system password.

    For instructions, see Log On to the Appliance Operating System with SSH.

  2. Verify that the RSA Runtime Server (biztier) service is running. Do the following.

    1. On the original primary instance, change the directory. Type:

      cd /opt/rsa/am/server

      and press ENTER.

    2. Type the following command and press enter.

      ./rsaserv status biztier

  3. If the biztier is not running, try to restart the service by typing the following command.

    ./rsaserv start biztier nodep

  4. If the RSA Runtime Server (biztier) service does not start, reset the original primary instance and configure it as a replica instance. For more information, see Manually Reset the Original Primary Instance as a Replica Instance.

  5. If you can start the RSA Runtime Server, synchronize the original primary instance using Operations Console of the new primary instance. In the Operations Console, select Deployment Configuration > Instances > Status Report and click Sync to synchronize the original primary instance with the new primary instance.

 

 


Attachments

    Outcomes