NetIQ Directory and Resource Administrator 8.x
In a multi-DRA Sever Evniornment (also know as a Multi-Master Set); each DRA server can make changes to Acitve Directory Objects directly. If changes to AD objects are made on one DRA server, they may not imeddiatley be seen on the other DRA server.
- Active Directory replication must complete so that all the domain controllers are updated. This ensures that the local domain controller the secondary DRA server is connected to reflects the changes made on the other domain controllers.
- The secondary servers need to perform an Incremental Accounts Cache refresh (only in the case where a new object is created or if a cache property is changed).
Changes made to a non cached property -
If an Administrator updates a 'non cached property' field of a user account such as the Comments field on the primary DRA server, the change is written to a local domain controller. Once Active Directory replication has completed the Administrator will be able to view the updated description while connected to any secondary DRA server.
Changes made to a cached property -
If an Administrator updates a 'cached property' field of a user account such as the Name field on the primary DRA server, the change is written to a local domain controller as well as to the cache on the primary DRA server. The secondary DRA server will reflect any changes made to a cached property after Active Directory replicated has been completed and an Incremental Accounts Cache Refresh runs.
For more information on properties cached by DRA, please refer to the DRA Software Development Kit.