Lifecycle of a Cloud Storage Pool object

The figure shows the lifecycle stages of an object that is stored in a Cloud Storage Pool.
Life cycle of a Cloud Storage Pool object
  1. Object stored in StorageGRID

    To start the lifecycle, a client application stores an object in StorageGRID.

  2. Object moved to Cloud Storage Pool
    • When the object is matched by an ILM rule that uses a Cloud Storage Pool as its placement location, StorageGRID moves the object to the external S3 bucket specified by the Cloud Storage Pool.
    • When the object has been moved to the Cloud Storage Pool, the client application can retrieve it using an S3 GET Object request from StorageGRID, unless the object has been transitioned to Glacier storage.
  3. Object transitioned to Glacier storage
    • Optionally, the object can be transitioned to Glacier storage. For example, the external S3 bucket might use lifecycle configuration to transition an object to Glacier storage immediately or after some number of days.
      Note: If you want to transition objects, you must create a lifecycle configuration for the external S3 bucket, and you must use a storage solution that implements the Glacier storage class and supports the S3 POST Object restore API.
      Note: Objects ingested by Swift tenants do not support POST Object restore requests, and should not be transitioned to Glacier storage. The external S3 bucket should not have a lifecycle configured for Glacier storage.
    • During the transition, the client application can use an S3 HEAD Object request to monitor the object's status.
  4. Object restored from Glacier storage
    If an object has been transitioned to Glacier storage, the client application can issue an S3 POST Object restore request to restore a temporary copy to the Cloud Storage Pool. The request specifies how many days the copy should be available in the Cloud Storage Pool and the data-access tier to use for the restore operation (Expedited, Standard, or Bulk).
    Note: When the expiration date of the temporary copy is reached, the copy is automatically removed from the Cloud Storage Pool. The original object remains in Glacier.
  5. Object retrieved

    Once an object has been restored to the Cloud Storage Pool, the client application can issue a GET Object request to retrieve the restored object.

Moving objects back to StorageGRID

Cloud Storage Pool objects can be moved back to StorageGRID, as follows:
  • If the objects have not been transitioned to Glacier storage, use ILM to move the objects back to a storage pool within the StorageGRID system.
  • If the objects have been transitioned Glacier storage:
    1. Issue S3 POST Object restore requests to restore the objects back to the Cloud Storage Pool. Specify an extended length of time for Days to ensure that ILM has adequate time to process them—several weeks or more is recommended.
      Note: If you need to restore multiple objects, it is more efficient to issue the S3 POST Object restore requests directly to the external S3 bucket.
    2. Use ILM to move the restored objects back to a storage pool within the StorageGRID system.
  • Once an object is moved back to StorageGRID, the copy in the Cloud Storage Pool is deleted.

Deleting Cloud Storage Pool objects

You can delete Cloud Storage Pool objects, as follows:
  • Use ILM to delete the objects at the end of a specified time period.
  • Issue an S3 DELETE Object request.