Platform Deployment Guide › Technical Information › Replication Holding Cache › Reset the Holding Cache › Automatically Reset the Holding Cache

Automatically Reset the Holding Cache

In some situations, it is not practical to manually reset the holding cache on every machine that requires it. For this reason, CA DataMinder allows you to schedule operations to automatically reset the holding cache.

For example, a blob (Binary Large Object) file is quarantined by antivirus software on a client machine. Here, the maximum number of retries (fresh attempts to replicate the quarantined event) will be quickly used up. After diagnosing the problem by checking the log files on the parent server, the only intervention required from the CA DataMinder administrator is to remove the blob file from quarantine; the scheduled cache reset will then automatically return the blob file to the main replication queue.

To schedule automatic cache resets, you edit the following settings in the \Replication policy folder of the local machine policy:

• Replication Holding Cache Reset Frequency

  This setting specifies how often (in days) the replication holding cache is reset. Defaults to 3.

  Setting this value to zero enables the holding cache to be reset more than once per day with the Reset Time setting controlling the time (in minutes) between resets.

  Note: Setting both the Reset Time and Reset Frequency values to zero prevents holding cache entries from being reset.

• Replication Holding Cache Reset Time

  This setting is dependent on the value of the Reset Frequency. That is, if the Reset Frequency setting is:

  • zero, then this setting is the number of minutes between cache resets. Defaults to 180 (minutes).
  • non-zero, then this setting represents the number of minutes from midnight at which the replication holding cache is reset. For example, to schedule a reset for 9:00pm, enter 1260 (that is, 21 x 60). The reset will run at this time on each day that a reset is scheduled. Defaults to 180 (3:00am).

  Note: Setting both the Reset Time and Reset Frequency values to zero prevents holding cache entries from being reset.