Directory & Resource Administrator 8.x
The last successful synchronization date reported by my secondary server(s) does not match the date reported by the primary.
If you would like to test your Primary/Secondary Server synchronization ability, do the following:
- Edit an Active View by adding today's date to the comments field
- From the Primary Server, force a manual synchronization
- Wait a few minutes (depending on the size of your DRA environment) and check the "Last Successful Update" fields
When the Administration servers in an MMS environment synchronize, the primary Administration server sends the latest information to the secondary Administration servers. Synchronization is a three step process:
1. The primary Administration server sends security and policy information, as well as the domain configuration, to each secondary Administration server.
2. Each secondary server updates the stored security and policy configuration settings.
3. Each secondary server refreshes the domain configuration. If you added a domain since the last synchronization, the secondary server adds the accounts for the new domain to the accounts cache. If you removed a domain since the last synchronization, the secondary server deletes the accounts for that domain from the accounts cache. The secondary server does not refresh the accounts cache.
If no changes have been made to the security, policy, or domain configuration, then the last successful synchronization date/time stamp on the secondary servers will be different from the date/time stamp on the primary server. The primary server will have the most current date because it is able to successfully communicate with the secondary servers. If no changes are made, then no new information is sent, so their is no need to "sync" the data...this is why the last successfully synchronization date/time stamp on the secondary servers can be different than the date/time stamp on the primary.