Resolution
How do I configure the Incremental Cache Refresh to not run if it takes x number of minutes to complete?
fact
Directory and Resource Administrator 6.60
fact
Directory and Resource Administrator 7.x
fix
Directory and Resource Administrator (DRA) 6.60 and later can be configured such that the Incremental Accounts Cache Refresh not run if it takes x number of minutes to complete. If there are a large number of changes made to objects within the managed domain since the last Incremental Accounts Cache Refresh (IACR), the next scheduled IACR can take a considerable amount of time to complete depending the on the number of changes made. During an IACR the domain is locked for write operations and thus if the IACR take a long time to complete, Assistant Admins will be unable to make any changes to objects in that domain during this time.
For each managed domain a constant can be defined to determine the maximum time the domain can be locked out during an ICR. The values will be domain specific, and will be stored under the domain's registry key in HKEY_LOCAL_MACHINE\SOFTWARE\Mission Critical Software\OnePoint\Administration\Modules\Accounts\Domains.Dns.
The following registry value is defined and used for each domain:
- IncDomRefr.MaxAllowedTime - (DWORD) maximum allowed time for ICR, in seconds. Defaults to 60 seconds.
Essentially, the IACR is a two phase process. The first phase consists of the data gathering process. It is at this point where DRA determines if the IACR is going to take longer than the maximum allowed time. If the IACR is going to take longer than the default time of 60 seconds, the IACR will not run. If this occurs, a Full Accounts Cache Refresh will be scheduled to run instead at 3:35AM.
The second phase of the ICR consists of the actual cache calls to update the cache status. It is is this phase where the domain is actually locked out to DRA clients.