000025408 - AM- 5-6.x: How to Generate Replica Package.

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000025408
Applies ToRSA ACE/Server 5.2.1
Authentication Manager 6.1.2
IssueHow to Generate Replica Package.
How to Push Replica Package with PushDB recovery without generating a Replica_package.
How to Generate Replica Package And PushDB When There Are Ten Replicas Installed.
Cannot generate a Replica Package when there are ten replicas installed.
CauseYou cannot add another Replica Package if your license limit has been reached - remove one replica and re-add it
There is a bug in ACE/Server 5.0 where a replica package cannot be generated when there are ten replicas configured, Replica Packages can be generated  with up to 9 replicas configured. This will be fixed in the first patch release.
Resolution

1)        Log into sdadmin


      a.        You must be logged in as an ACE admin


      b.        cd /OPT/ace/prog


      c.        ./sdadmin


2)        Flag the Primary to NOT Push the database.


      a.        System Parameters > Edit System Parameters > Un-Check


Allow DB Push Assisted Recovery


3)        Remove any old replica_package directories from the


/opt/ace/data directory


4)        Stop the Primary ACE/Server


      a.        cd /opt/ace/prog


      b.        ./aceserver stop


      c.        ./sdconnect shutdown


5)        Generate a NEW Replica Package


      a.        ./sdrepmgmt delete       <remove the problem replica>


      b.        ./sdrepmgmt add           <add the problem replica back, so that it will be without a Push DB recovery>


      c.        ./sdsetup -package


      d.        Specify the Replica that you will generate this replica package for.


      e.        Optionally verify that your ?sdrepnodes.txt? was built correctly


              i.        cd /opt/ace/data/replica_package/license


              ii.       more sdrepnodes.txt


              iii.        You should see the name of all the Replica servers that you specified as well as some Seq Numbers and Port Names/Numbers


6) Restart Primary Services


      a.        cd /opt/ace/prog


      b.        ./sdconnect start


      c.        ./aceserver start


7)        Stop the Replica Server.


      a.        cd /opt/ace/prog


      b.        ./aceserver stop


      c.        ./sdconnect shutdown


8)        Copy the replica_package with sub folders ( license and database) to the Replica.  You can store the replica_package directory in any directory on the Replica Host


         a.    Apply the replica package


            i.        cd /opt/ace/prog


            ii.        ./sdsetup -apply_package pathname


            iii.        ./sdinfo | more


                      1.        You should see that the field PRIMARY ACE SERVER reflects the hostname of the Primary ACE/Server.


                      2.        You should see that the field THIS SERVER reflects the hostname of the Replica ACE/Server.


9)        Start the Replica Server


      a.        cd /opt/ace/prog


      b.        ./sdconnect start


      c.        Open a real-time activity log on the Primary


              i.        Open another session to the host


              ii.        cd /opt/ace/prog


              iii.        ./sdlogmon ?t


              iv.        Go back to your original session and continue with the Primary startup.


      d.        ./aceserver start


      e.        We should begin to see messages in both the Primary and that particular Replica logs that the two connect.  At this time, you should be sure that your Sequence numbers are the same


on both of those machines with an ./sdrepmgmt list on both hosts.


Regards,


Jay Guillette |   The Security Division of EMC2  |  Support Engineer III


 

stop Services - RSA 6.1 Control Panel in Windows, Windows Control Panel with ACE 6.0 or less, ../ace/prog/aceserver stop  and ../ace/prog/sdconnect shutdown in unix


If necessary, remove an old replica, or existing replica so you can re-add it. Start -> Programs -> RSA ...-> RSA configuration -> RSA Replica Management [Add] in Windows, or ..ace/prog/sdrepmgmt add in unix  


If [x] Allow PushDB assited recovery is checked in Host mode - system, you can wait for the Primary to push the database to all Replicas


If this is a new Replica, uncheck [ ] Allow PushDB assited recovery, and generate replica package; Start -> Programs -> RSA ...-> RSA configuration -> RSA Replica Management [Generate Replica package] in Windows, or ..ace/prog/sdsetup ?package  in unix.  Copy "ace"/data/replica_package (entire folder) to a temp folder on the New Replica, install ACE server as a replica and browse to this temp folder.  Allow time for Replica to synchronize with Primary.


If this is an existing Replica with software already installed, and you do not want to use [x] Allow PushDB assited recovery is checked in Host mode ? system, you can copy "ace"/data/replica_package (entire folder) to a temp folder on the New Replica and [Apply] the replica package with services stopped.  Start -> Programs -> RSA ...-> RSA Control Panel ? Apply Replica Package.  In unix, ../ace/prog/sdsetup ?apply_package 


When done, check [x] Allow PushDB assited recovery is checked in Host mode - system, if you want NOMINATE to work on Replicas in a emergency 


ONE REPLICA REQUIRES PUSHDB:
1. Remove the replica from the configuraton on the primary using Replica Management on Windows, and sdsetup -package on Unix.
2. Add the deleted replica back on the primary, using Replica Management on Windows, and sdsetup -package on Unix.
amTWO OR MORE REPLICAS REQUIRE PUSHDB:
1. Remove one replica from the configuraton on the primary using Replica Management on Windows, and sdsetup -package on Unix.
2. Add the deleted replica back on the primary, using Replica Management on Windows, and sdsetup -package on Unix, tag all other replicas requiring a pushdb for a push using the same replica package as the tenth replica.

 
Legacy Article IDa2750

Attachments

    Outcomes