Home > Storage > PowerScale (Isilon) > Product Documentation > Cloud > PowerScale: CloudPools and ECS > CloudPools operations
This section describes the workflow of CloudPools operations:
The archive operation is the CloudPools process of moving file data from the local PowerScale cluster to cloud storage. Files are archived either using the SmartPools Job or from the command line. The CloudPools archive process can be paused or resumed. See Commands for details.
The following figure shows the workflow of the CloudPools archive.
More workflow details include:
The recall operation is the CloudPools process of reversing the archive process. It replaces the SmartLink file by restoring the original file data on the PowerScale cluster and removing the cloud objects in ECS. The recall process can only be performed using the command line. The CloudPools recall process can be paused or resumed. See Commands for detailed instructions on commands.
The following figure shows the workflow of CloudPools recall.
The read operation is the CloudPools process of client data access, known as inline access. When a client opens a file for read, the blocks will be added to the cache in the associated SmartLink file by default. The cache can be disabled by setting the accessibility. For more information, see File pool policies.
The following figure shows the workflow of CloudPools read by default.
Starting from OneFS 9.1.0.0, cloud object cache is introduced to enhance CloudPools functions for communicating with cloud. In step 1, OneFS looks for data in the object cache first and OneFS retrieves data from the object cache if the data is already in the object cache. Cloud object cache reduces the number of requests to the ECS when reading a file.
In versions earlier than OneFS 9.1.0.0, OneFS looks for data in the local data cache first in step 1. It moves to step 3 if the data is already in the local data cache.
Note: Cloud object cache is per node. Each node maintains its own object cache on the cluster.
The update operation is the CloudPools process that occurs when clients update data. When clients change to a SmartLink file, CloudPools first writes the changes in the data local cache and then periodically sends the updated file data to ECS. The space used by the cache is temporary and configurable. For more information, see File pool policies.
The following figure shows the workflow of the CloudPools update.