Platform Deployment Guide › Object Storage › Integrating with EMC Centera › About Centera Integration › How the Centera Integration Works

How the Centera Integration Works

Centera integration with CA DataMinder is controlled by the CMS. If Centera integration is enabled, when an event is replicated to the CMS from a client machine or gateway, the blob file is first saved to the object store \Data folder. It is then copied to Centera and the source blob file deleted from the CMS.

Note: The blob file is not deleted immediately; it is cached in case it is needed again soon.

The database entry on the CMS is subsequently updated to reflect the new location for the blob, replacing the blob file system location with the Centera content address code.

• If the Centera is temporarily unavailable: CA DataMinder maintains a database table containing a list of blobs that need to be stored to Centera. This list can build up if the Centera is offline or if the configuration settings are incorrectly optimized for the installation. We recommend that you monitor the size of this database table as a health check.
• Migrating existing blob files to a Centera: There is no inbuilt mechanism for migrating to Centera those blobs that were stored on the CMS before Centera integration was implemented. It is possible to do this, however. You will need to write a custom SQL procedure to add a blob queue record for each blob migrated to Centera.

Note: Any custom SQL procedure to migrate existing blobs must be carefully designed to ensure that the migration queue is properly managed. We strongly recommend that you contact Technical Support for guidance if you need to write a migration procedure; see CA Technical Support.

More information:

Managing the Temporary Object Store