Blob offset and length details are stored in the Centera clip so that, when retrieving data during an event search, CA DataMinder only retrieves the relevant portion of the Centera blob needed to rebuild the CA DataMinder blob. During an event search, CA DataMinder retrieves the event data from the Centera blob to a regular CA DataMinder blob that can be accessed by the Data Management console or iConsole.
Retrieved blob files are retained in a temporary cache on the CMS. This is the same cache used to retain events retrieved from other third party remote storage locations, such as an email archive. The cache timeout is controlled by the Remote Data Cache Timeout setting in the CMS machine policy; when the timeout expires, the cache is deleted.
Note: When the timeout expires, data is not deleted immediately but is instead moved to a secondary folder within the cache and deleted after another elapsed timeout. This means data may persist in the cache for twice as long as specified.
|
Copyright © 2014 CA.
All rights reserved.
|
|