Events stored in the local database of a gateway or client machine are eventually replicated up to the parent server and ultimately to the CMS. The main reason for database purging on gateways and client machines is therefore to prevent free disk space falling to dangerously low levels on these machines (with the attendant risk of the CA DataMinder infrastructure being suspended).
The simplest strategy is to implement purging after replication. This purges captured data from the local database as soon as it has been replicated to the parent server. Under this strategy, individual items of captured data are automatically excluded from purges until they have been replicated to the parent server. Only items that have already been replicated can become eligible for purging.
By default, database purging is turned off in the common client machine and common gateway policies.
|
Copyright © 2014 CA.
All rights reserved.
|
|