Data management

Data in storage components must be managed to balance performance and capacity considerations with your business requirements for retention of data.

Blob data flows through the storage system in the following manner:

  1. A blob is created and moved to the storage system.
  2. The blob data can be saved (or divulged) as a file to a directory outside of AS4 Microservice at one of the following times:
    • When the blob is created.
    • When the blob is purged.
  3. The blob is purged.

After a blob is created in the storage system, the existence and availability of the blob and its contents are determined by its lifespan settings. System administrators can configure these lifespan settings with the storage provision and storage purge commands. For more information, see Data lifespan.

The reaper tool carries out the purge processing at specified time intervals. The reaper includes the following items:

  • The memento, which is a record file of time-stamped activity that is written by the reaper. This file is used by the reaper to detect clock errors and prevent erroneous reaping.
  • The optional function of divulging, which saves blobs as files outside of AS4 Microservice for your own records and analysis.
    Important: Divulging occurs either when a blob is created or before a blob is purged as determined by the parameters set with the storage provision or storage purge commands. The file that is created by divulging is not affected by the operations of AS4 Microservice.

System administrators configure the expiration, lifespan, and blob divulging according to their business requirements. Blobs are purged after their lifespan expires or earlier, if overridden by the expiration setting. The divulge settings determine whether blobs are saved before they are purged from storage.