Infrastructure-based purges automatically delete any corresponding blob files. You can therefore link your partition-based purge to a scheduled infrastructure-based purge. This involves the following procedure:
You need to configure the machine policy to suspend the CMS during event purges. In the Data Management policy folder, set the Suspend Infrastructure During Purge? setting to True.
The infrastructure-based purge must be configured to invoke a custom SP. The recommended method depends on which database account owns the schema:
You need to implement a custom SP to execute the wgn_roll_partitions procedure.
We do not recommend using this method; instead, we recommend using a third-party scheduler—see the next section. But if you do not have a third party scheduler, you will need to use this more complex method. Specifically, you need a mechanism to automatically run a partition-based purge before the scheduled infrastructure purge, which itself must invoke a ‘no operation’ custom SP. This SP prevents the infrastructure-based purge from trying to delete event records in the CMS database that will have already been removed by the partition-based purge.
The infrastructure-based purge then automatically deletes any residual blob files marked for deletion.
|
Copyright © 2014 CA.
All rights reserved.
|
|