What are the steps to promote ADAM instances during recovery/promotion scenarios? (NETIQKB71020)

  • 7771020
  • 04-Apr-2008
  • 14-Feb-2011

Environment

Directory and Resource Administrator 8.x

Situation

What are the steps to promote ADAM instances during recovery/promotion scenarios?
How do I manually recover ADAM when the primary Administration server goes offline temporarily or permanently?

How do I manually make a DRA secondary Administration server the ADAM Master when the primary Administration server goes down?

How do I manually transfer the ADAM roles back to the DRA primary server when the DRA server comes back online? How will I retrieve the old Multi-Master Set (MMS)?

Resolution

To recover the ADAM partition when the Primary DRA server goes offline permanently, perform the following steps:

  1. Promote one of the existing secondary Administration servers to primary Administration server.
  2. Logon to the new Primary Administration server as a user who has Administrator privileges on the ADAM partition.
  3. Go to Start > Programs > ADAM > ADAM tools Command prompt.
    1. Execute the command ?DSmgmt.exe?.
    2. Execute the command ?roles? at the ?dsmgmt? command prompt.
    3. Execute the command ?Connections? at the ?FSMO maintenance? prompt.
    4. Type ?Connect to server <New DRA primary server name>:<ADAM port number>? at the Server connections prompt.  (for example,  GMCSRV02:50000).
    5. Return to the ?fsmo maintenance? prompt from ?Server connections? by entering the command ?quit?.
    6. Execute the ?seize schema master? and ?seize naming master? commands.
    7. Click Yes  in the Role seizure Confirmation dialog box.

      • Note: The summary of the new primary Administration server has been delegated as ADAM schema master and naming master role.

    8. Restart the DRA ADAM instance service and then restart the NetIQ Administration service on all the DRA servers.

To manually transfer the ADAM roles back to the DRA primary Administration server when the Primary Administration server comes back online:

  1. Demote the existing primary Administration server to secondary Administration server by using Demote Server option.
  2. Log on to any DRA server as a user who has Administrator privileges on the ADAM partition.
  3. Go to Start > Programs > ADAM > ADAM tools Command prompt.
    1. Enter and execute the command ?DSmgmt.exe?.
    2. Execute the command ?roles? at the ?dsmgmt? command prompt.
    3. Execute the command ?Connections? in ?FSMO maintenance? prompt.
    4. Type ?Connect to server<Old DRA primary server name>:< ADAM port number>? at the Server connections prompt. (for example,  GMCSRV01:50000).
    5. Return to the ?fsmo maintenance? prompt from ?Server connections? by entering the command ?quit?.
    6. Execute the ?transfer schema master? and ?transfer naming master? commands.
    7. Click Yes in the Role Transfer Confirmation dialog box.

      • Note: The summary of the old primary Administration server has been delegated as ADAM schema master and naming master role.

    8. Restart DRA ADAM instance service and then NetIQ Administration service on all the DRA servers.

Cause

The Primary DRA server goes offline temporarily or permanently.

Additional Information

Formerly known as NETIQKB71020

<New DRA primary server> is the Administration server which was promoted as primary Administration server as in Step1.
<Old DRA primary server name> is the Administration server which was offline.

 

 

For information on manually installing ADAM on a DRA server, see NETIQKB71020.