Cleaning up files transferred to the cloud storage tier

To do basic cleanup of objects that are transferred to the cloud object storage by using Transparent cloud tiering, issue a command according to this syntax:

mmcloudgateway files delete
 {-delete-local-file | -recall-cloud-file | 
--require-local-file} [--keep-last-cloud-file]
 [--] File [File ...]  

where,

• --recall-cloud-file: When this option is specified, the files are recalled from the cloud storage before deleting them on the cloud. The status of the local files becomes resident after the operation.
• --delete-local-file: This option deletes both local files and the corresponding cloud object. There is no recall here.
• --keep-last-cloud-file: This option deletes all the versions of the file except the last one from the cloud. For example, if a file has three versions on the cloud, then versions 1 and 2 are deleted and version 3 is retained.
• --require-local-file: This option removes the extended attribute from a co-resident file and makes it resident, without deleting the corresponding cloud objects. The option requires the file data to be present on the file system and will not work on a non-resident file.
• --File: This option can be used to process a file list similar to the one generated by the ILM policy.

The mmcloudgateway files delete command accepts files in GPFS file system as an input.