- Edit CloudPools Settings
- Enables you to change default CloudPools settings, as follows. After you are done specifying CloudPools settings, click
Save Changes to save the new settings or
Cancel to leave the previous default settings in place.
- Archive files with snapshots
- Specifies that files with snapshot versions should be archived. The default is enabled. Because snapshots maintain full point-in-time file data, archiving files with snapshot versions does not save storage space on your cluster for those files.
- Encrypt data before transfer
- Specifies whether CloudPools encrypts data prior to archiving it. The default is disabled. CloudPools uses AES-256 block-based encryption. If enabled, cloud data is encrypted when archived and decrypted when recalled.
- Compress data before transfer
- Specifies whether CloudPools compresses data prior to archiving it. The default is disabled. CloudPools uses ZLIB block-based compression. If enabled, cloud data is compressed when archived and decompressed when recalled.
- Cloud Data Retention Period
- Specifies the length of time that cloud files are retained after the local SmartLink files have been deleted. The default is
1 week. When a SmartLink file is deleted from the local cluster, CloudPools cleans up local resources allocated for the SmartLink file, and also removes the associated cloud objects.
CloudPools removes (garbage-collects) cloud objects when their SmartLink files and all local references to them have been removed. If a SmartLink file has been backed up and the original SmartLink file is subsequently deleted, cloud objects are only deleted after the retention period associated with the backed-up SmartLink file has expired.
- Incremental Backup Retention Period for NDMP Incremental Backup and SyncIQ
- Specifies the amount of time that cloud files will be retained after either an incremental NDMP backup or a SyncIQ replication job. The default is 5 years. If a SmartLink file has been backed up and the original SmartLink file is subsequently deleted, cloud objects are deleted only after this retention period has expired.
- Full Backup Retention Period for NDMP Only
- Specifies the amount of time that cloud files will be retained after the creation of a full NDMP backup. The default value is 5 years. If a SmartLink file has been backed up and the original SmartLink file is subsequently deleted, cloud objects are only deleted after the longer of the two retention periods has expired.
- Writeback Frequency
- Specifies the interval after which the system writes back data stored in a SmartLink file cache to the cloud. The default value is 9 hours. When a user opens and modifies a SmartLink file through an NFS export or SMB share, a cache is created for the SmartLink file. Modified data is stored in the cache and periodically written back to the cloud so that the cloud has the latest file data.
- Specifies whether, when a SmartLink file is accessed through NFS or SMB, cloud data is incrementally downloaded (cached) as needed, or fully downloaded (not cached). The default value is Allow archive files to be cached locally. By allowing archive files to be cached locally, only the portion of data that the user needs is recalled from the cloud. If, instead, you specify Do not cache archived files, when a user accesses a SmartLink file, the file is fully recalled and replaces the SmartLink file. Depending on file size, this can be more time-consuming and use more system resources.
- Cache Read Ahead
- Specifies whether the associated cloud data is partially or fully cached when an SMB or NFS user accesses a SmartLink file on the cluster. The default value is Cache accessed data only. If files are always fully cached, this can take up more system resources than partially caching files.
- Cache Expiration
- Specifies the interval before the system purges cached data from SmartLink files. The default value is 1 day. This value should be greater than the WriteBack Frequency value. This will enable CloudPools to write back any modified data to the cloud before the cache is purged. Regular expiration of cache data ensures that storage space on your cluster is not used up by cache data that is no longer needed.