Audit messages and the object lifecycle

Each time an object is ingested, retrieved, or deleted, audit messages are generated. Audit messages are linked through identifiers specific to each protocol.

Protocol Code
Linking S3 operations S3BK (S3 Bucket) and/or S3KY (S3 Key)
Linking Swift operations WCON (Swift Container) and/or WOBJ (Swift Object)
Linking internal operations CBID (Object's Internal Identifier)

Timing of audit messages

Because of factors such as timing differences between grid nodes, object size, and network delays, the order of audit messages generated by the different services can vary from that shown in the examples in this section.

Dual commit

Dual commit forces two copies of the object to be stored on two LDR services at the time of initial ingest. These initial copies are made before the object is evaluated against the active information lifecycle management (ILM) policy. At the same time that these initial copies are made, objects are queued for ILM evaluation. Depending on the configuration of ILM rules, additional copies might be made in different locations and the initial dual "commit" copies deleted. If the ILM rule is configured with only one content placement instruction, when ILM rules are evaluated, the StorageGRID Webscale system deletes one instance of the object so that only one instance of object data is stored.

For more information about dual commit, see the Administering StorageGRID Webscale.

Information lifecycle management policy configuration

With the default ILM policy (Baseline 2 Copy Rule v1.0), object data is copied once for a total of two copies. If the ILM policy requires more than two copies, there will be an additional set of CBRE, CBSE, and SCMT messages for each extra copy. For more information about ILM policies, see the Administering StorageGRID Webscale.

Archive Nodes

The series of audit messages generated when an Archive Node sends object data to an external archival storage system is similar to that for Storage Nodes except that there is no SCMT (Store Object Commit) message, and the ATCE (Archive Object Store Begin) and ASCE (Archive Object Store End) messages are generated for each archived copy of object data.

The series of audit messages generated when an Archive Node retrieves object data from an external archival storage system is similar to that for Storage Nodes except that the ARCB (Archive Object Retrieve Begin) and ARCE (Archive Object Retrieve End) messages are generated for each retrieved copy of object data.

The series of audit messages generated when an Archive Node deletes object data from an external archival storage system is similar to that for Storage Nodes except that there is no SREM (Object Store Remove) message, and there is an AREM (Archive Object Remove) message for each delete request.