Working with external storage pools
With external storage pools you can migrate files to storage pools managed by an external application such as IBM Spectrum Scale™.
The following topics describe how to work with external storage pools:
- Defining external pools
When you define external pools, follow these rules. - User-provided program for managing external pools
After you define an external storage pool, subsequent migration or deletion rules might refer to that pool as a source or target storage pool. - File list format
Each call to the external pool script specifies the pathname for a temporary file that contains a list of files to be operated on. - Record format
The format of the records in each file list file can be expressed as shown in the following example. - Migrate and recall with external pools
After you define an external storage pool, subsequent migration or deletion rules might refer to that pool as a source or target storage pool. - Pre-migrating files with external storage pools
Pre-migration is a standard technique of Hierarchical Storage Management (HSM) systems such as Tivoli® Storage Manager. - Purging files from external storage pools
Files that have been migrated to an external storage pool continue to have their file name and attributes stored in GPFS; only the file data has been migrated. Files that have been migrated or pre-migrated to an external storage pool may be deleted from the GPFS internal storage pool and from the external storage pool with the policy language using a DELETE rule. - Using thresholds with external pools
Exhausting space in any one online storage pool generates a NO_SPACE event even though there might be space available in other online storage pools. To create free space, file data can be moved to other online storage pools, deleted, or moved to external storage pools.
Parent topic: Policies for automating file management
Related concepts:
Related tasks:
Related reference: