How to migrate DRA settings to a new MMS

  • 7023774
  • 18-Mar-2019
  • 19-Mar-2019

Environment

Directory Resource Administrator 9.2.x

Situation

How to export DRA MMS data to another DRA MMS

How to migrate DRA MMS data between like versions

How to build a parallel DRA MMS

Resolution

To create a DRA Primary server in a new Multi Master Set (MMS) using the configuration from an existing DRA server running the same version of DRA, perform the following steps.

The default AD LDS port is 50000. If you are using a custom port replace all instances of 50000 below with your custom port.
1.    Export AD LDS configuration on the current DRA Primary server with LDIFDE (LDAP Data Interchange Format Directory Exchange):
I.    Click Start, right-click Command Prompt, and then click Run as administrator to open the command prompt.
II.    Execute the following commands:
a.    ldifde -f DRAVA.ldf -s localhost:50000 -d "CN=DRAVARoot,DC=DRA,DC=COM" -o "distinguishedName,instanceType,whenCreated,whenChanged,uSNCreated, uSNChanged,objectGUID,objectCategory,dSCorePropagationData" 
b.    ldifde -f DRADG.ldf -s localhost:50000 -d "CN=DRADynamicGroup,DC=DRA,DC=COM" -o "distinguishedName,instanceType,whenCreated,whenChanged,uSNCreated, uSNChanged,objectGUID,objectCategory,dSCorePropagationData"
c.    ldifde -f DRALQ.ldf -s localhost:50000 -d "CN=DRAQueriesRoot,DC=DRA,DC=COM" -o "distinguishedName,instanceType,whenCreated,whenChanged,uSNCreated, uSNChanged,objectGUID,objectCategory,dSCorePropagationData,showInAdvancedViewOnly"
III.    Execute the C:\Windows\ADAM\ADSchemaAnalyzer.exe command to open the AD DS/LDS Schema Analyzer.
IV.    From the “AD DS/LDS Schema Analyzer” client, connect to the AD LDS repository:
a.    Execute “Load target schema” from the File menu.
  •     Set Server[:port] = “localhost:50000” and click OK.
b.    Execute “Load base schema” from the File menu.
  •     Set Server[:port] = “localhost:50000” and click OK.
c.    Select the options from the Tools menu:
  •     In the Dependencies Graph tab, select all options.
  •     In the LDIF Generation tab, Set Present Elements = “Update with references to new elements and present elements” and clear “Allowed to write systemPossSuperiors…”
  •     In the Miscellaneous tab, clear all options.
  •     Click OK.
d.    In the tree view structure, expand the “Classes” node and for each of the following classes mark any associated virtual attributes as missing (specify an “X” next to the “mayContain: VA-???” element):
  •     DRA-User
  •     DRA-Contact
  •     DRA-Group
  •     DRA-Computer
  •     DRA-OrganizationalUnit
  •     DRA-DynamicDistributionGroup
e.    In the tree view structure, expand the “Attributes” node and for each of the following attributes that starts with “VA-“ mark attributes as to be added (specify a “+” next to the “VA-???” element).

f.    Execute the Create LDIF file from the file menu and Save as DRAVASchema.ldf
Important: At the end of this step the DRAVA.ldf, DRADG.ldf, DRALQ.ldf, DRAVASchema.ldf files will be exported.
2.    Export the Modules registry key from the current DRA Primary server:
I.    Click Start, right-click Command Prompt, and then click Run as an administrator to open the command prompt.

II.    Execute the RegEdit.exe command.

III.    Export the Modules registry key and save it as dra.reg by right-clicking and selecting Export:
  •  HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Mission Critical Software\OnePoint\Administration\Data\Modules
3.    Create a DRA Primary server
I.    Install a new DRA Primary server to create a new MMS.

II.    Manage the same set of domains or Office365 tenants to ensure the migrated registry files match the new MMS.

III.    Ensure that you wait until the Full Account Cache Refresh (FACR) completes for each managed domain.

IV.    Copy any trigger or policy scripts from the current DRA Primary server to the new Primary server ensuring they are copied to the same path.
4.    Import the AD LDS backup files onto the new DRA Primary server:
V.    Copy the DRAVA.ldf, DRADG.ldf, DRALQ.ldf, DRAVASchema.ldf backup files.

VI.    Open the DRADG.ldf file and remove the entry for “CN=DRADynamicGroup,DC=DRA,DC=COM” and “CN=MemberFilter,CN=DRADynamicGroup,DC=DRA,DC=COM” and save the ldf file. Do not add this node as this node is already existed in the new primary server. 

VII.    Open the DRALQ.ldf file and remove entry for “CN=DRAQueriesRoot,DC=DRA,DC=COM” and save the ldf file. Do not add this node as this node is already existed in the new primary server

VIII.    Open the DRAVA.ldf file and remove entry for “CN=DRAVARoot,DC=DRA,DC=COM” and save the ldf file. Do not add this node as this node is already existed in the new primary server.

IX.    Click Start, right-click Command Prompt, and then click Run as an administrator to open the command prompt.

X.    Navigate to the folder containing the .ldif files and execute the following commands:
  •     ldifde -i -u -f DRAVASchema.ldf -s localhost:50000 -j . -c "cn=Configuration,dc=X" #configurationNamingContext
  •     ldifde -i -f DRAVA.ldf -s localhost:50000
  •     ldifde -i -f DRADG.ldf -s localhost:50000
  •     ldifde -i -f DRALQ.ldf -s localhost:50000
5.    Import the registry backup files on the new DRA Primary:
I.    Copy the exported registry file from the current DRA Primary server to the new DRA Primary server and double-click it to merge the data into the registry.
6.    Restart the DRA Administration Service on the new DRA Primary server and run the DRA Health Check utility.

7.    Run the ADLDS or validate LDS Instance check on the Primary server. This check will apply required schema updates to AD LDS.

8.    Run the DRA Health Check Utility to ensure that services, accounts, and imported data is correct and do not cause any issues to the DRA system. 

Additional Information

The steps within this KB ONLY work between the same versions of DRA. These steps also require the same AD account be used to run the NetIQ Services, used by DRA.