A Cloud Storage Pool lets you use ILM to move object data outside of your StorageGRID system. For example, you might want to move infrequently accessed objects to lower-cost cloud storage, such as Amazon S3 Glacier, S3 Glacier Deep Archive, or the Archive access tier in Microsoft Azure Blob storage. Or, you might want to maintain a cloud backup of StorageGRID objects to enable disaster recovery.
The following table compares storage pools to Cloud Storage Pools and shows the high-level similarities and differences.
Storage pool | Cloud Storage Pool | |
---|---|---|
How is it created? |
Using the Grid Manager. option inYou must set up storage grades before you can create the storage pool. |
Using the Grid Manager. option inYou must set up the external bucket or container before you can create the Cloud Storage Pool. |
How many pools can you create? |
Unlimited. |
Up to 10. |
Where are objects stored? |
On one or more Storage Nodes or Archive Nodes within StorageGRID. |
In an Amazon S3 bucket or Azure Blob storage container that is external to the StorageGRID system. If the Cloud Storage Pool is an Amazon S3 bucket:
If the Cloud Storage Pool is an Azure Blob storage container, StorageGRID transitions the object to the Archive tier. Note: In general, do not configure Azure Blob Storage lifecycle management for the container used for a Cloud Storage Pool. POST Object restore operations on objects in the Cloud Storage Pool can be affected by the configured lifecycle.
|
What controls object placement? |
An ILM rule in the active ILM policy. |
An ILM rule in the active ILM policy. |
What data protection method is used? |
Replication or erasure coding. |
Replication. |
How many copies of each object are allowed? |
Multiple. |
One copy in the Cloud Storage Pool and, optionally, one or more copies in StorageGRID. Note: You cannot store an object in more than one Cloud Storage Pool at any given time.
|
What are the advantages? |
Objects are quickly accessible at any time. |
Low-cost storage. |