PowerScaleOneFS CLI Command Reference

isi filepool policies create

Create a custom file pool policy to identify a specific storage target and perform other actions on matched files and directories.

Syntax

isi filepool policies create <name>  
 [--description <string>]
 [--begin-filter{<predicate> <operator> <link>}...--end-filter]
 [--apply-order <integer>]
 [--data-access-pattern  {random | concurrency | streaming}]
 [--set-requested-protection {default | +1 | +2:1 | +2 | +3:1 | +3 | +4 | 2x | 3x | 4x | 5x | 6x | 7x | 8x}]
 [--data-storage-target <string>]
 [--data-ssd-strategy  {metadata | metadata-write | data | avoid}]
 [--snapshot-storage-target <string>]
 [--snapshot-ssd-strategy {metadata | metadata-write | data | avoid}]
 [--enable-coalescer {Yes | No}]
 [--enable-packing {Yes | No}]
 [--cloud-pool <string>]
 [--cloud-accessibility {cached | no-cache}]
 [--cloud-cache-expiration <duration>]
 [--cloud-compression-enabled {yes | no}]
 [--cloud-data-retention <duration>]
 [--cloud-encryption-enabled {yes | no}]
 [--cloud-full-backup-retention <duration>]
 [--cloud-incremental-backup-retention <duration>]
 [--cloud-read-ahead <string>]
 [--cloud-writeback-frequency <duration>]
 [--verbose | -v]
 [--help | -h]

Options

<name>: Specifies the name of the file pool policy to create.

--begin-filter {<predicate> <operator> <link>}... --end-filter: Specifies the file-matching criteria that determine the files to be managed by the filepool policy. Each file matching criterion consists of three parts:

Predicate. Specifies what attribute(s) to filter on. You can filter by path, name, file type, timestamp, or custom attribute, or use a combination of these attributes.

Operator. Qualifies an attribute (for example, birth time) to describe a relationship to that attribute (for example, before).

Link - Combines attributes using AND and OR statements.; The following predicates are valid:

--size=<nn>[{B | KB | MB | GB | TB | PB}]

Selects files according to the specified size.

--path=<pathname>

Selects files relative to the specified pathname.

--file-type= <value>

Selects only the specified file-system object type.

The following values are valid:

file

Specifies regular files.

directory

Specifies directories.

other

Specifies links.

--name= <value> [--case-sensitive= {true | false}]

Selects only files whose names match the specified string. Use --case-sensitive=true to enable case-sensitivity.

When forming the name, you can include the following wildcards:

*

[ ]

?

--birth-time=<timestamp>

Selects files that were created relative to the specified date and time. Timestamp arguments are formed as YYYY-MM-DDTHH:MM:SS. For example, 2013-09-01T08:00:00 specifies a timestamp of September 1, 2013 at 8:00 A.M. You can use --operator= with an argument of gt to mean after the timestamp or lt to mean before the timestamp.

--changed-time=<timestamp>

Selects files that were modified relative to the specified date and time.

--metadata-changed-time=<timestamp>

Selects files whose metadata was modified relative to the specified date and time.

--accessed-time=<timestamp>

Selects files that were accessed at the specified time interval.

--custom-attribute=<value>

Selects files based on a custom attribute.; You can use the operator= option to specify a qualifier for the file-matching criterion. Specify operators in the following form:

--operator=<value>

The following operator values are valid:

Table 1. --operator=<value>--operator=<value>

Value

Description

eq

Equal. This is the default value.

ne

Not equal

lt

Less than

le

Less than or equal to

gt

Greater than

ge

Greater than or equal to

not

Not; Link arguments can be used to specify multiple file-matching criteria. The following links are valid:

--and

Connects two file-matching criteria where files must match both criteria.

--or

Connects two file-matching criteria where files must match one or the other criteria.
--description <string>: Specifies a description of the filepool policy
--apply-order <integer>: Specifies the order index for execution of this policy.
--data-access-pattern <string>: Data access pattern random, streaming or concurrent.
--set-requested-protection <string>: Specifies a protection level for files that match this filepool policy (e.g., +3, +2:3, 8x).
--data-storage-target <string>: The name of the node pool or tier to which the policy moves files on the local cluster. If you do not specify a data storage target, the default is anywhere.
--data-ssd-strategy <string>: Specifies how to use SSDs to store local data.

avoid

Writes all associated file data and metadata to HDDs only.

metadata

Writes both file data and metadata to HDDs. This is the default setting. An extra mirror of the file metadata is written to SSDs, if SSDs are available. The SSD mirror is in addition to the number required to satisfy the requested protection. Enabling GNA makes read acceleration available to files in node pools that do not contain SSDs.

metadata-write

Writes file data to HDDs and metadata to SSDs, when available. This strategy accelerates metadata writes in addition to reads but requires about four to five times more SSD storage than the Metadata setting. Enabling GNA does not affect read/write acceleration.

data

Uses SSD node pools for both data and metadata, regardless of whether global namespace acceleration is enabled. This SSD strategy does not result in the creation of additional mirrors beyond the normal requested protection but requires significantly increases storage requirements compared with the other SSD strategy options.
--snapshot-storage-target <string>: The name of the node pool or tier chosen for storage of snapshots. If you do not specify a snapshot storage target, the default is anywhere.
--snapshot-ssd-strategy <string>: Specifies how to use SSDs to store snapshots. Valid options are metadata, metadata-write, data, avoid. The default is metadata.
--enable-coalescer {Yes | No}: Enables the coalescer.
--enable-packing {Yes | No}: Enables packing.
--cloud-pool <string>: Specifies the default CloudPool and, therefore, the cloud storage account where cloud data is to be archived.
--cloud-accessibility {cached | no-cache}: Specifies the default behavior for accessing a SmartLink (archived) file if there is no file pool policy for the archived file. If there is a file pool policy for the archived file, that policy and its settings take precedence over a --cloud-accessibility setting. Specify cache to ensure that only the data blocks requested are cached and flushed or invalidated based on the cache retention settings. Specify no-cache to ensure that the data blocks are not cached and do not consume file system blocks long term.
--cloud-cache-expiration <duration>: Specifies the minimum amount of time until the cache expires. A number followed by a unit of time is accepted. For example, a setting of 9H would specify a nine-hour duration. Similarly, a setting of 2D would specify a two-day duration.
--cloud-compression-enabled {yes | no}: Specifies whether data is to be compressed when archived to the cloud.
--cloud-data-retention <duration>: Specifies the minimum amount of time that archived data will be retained in the cloud after a SmartLink file is deleted from the cluster. A number followed by a unit of time is accepted. For example, a setting of 9H would specify a nine-hour duration. Similarly, a setting of 2D would specify a two-day duration.
--cloud-encryption-enabled {yes | no}: Specifies whether data is to be encrypted when archived to the cloud.
--cloud-full-backup-retention <duration>: Specifies the minimum amount of time that cloud files will be retained after the creation of a full backup. A number followed by a unit of time is accepted. For example, a setting of 9H would specify a nine-hour duration. Similarly, a setting of 2D would specify a two-day duration.
--cloud-incremental-backup-retention <duration>: Specifies the minimum amount of time that cloud files will be retained after the creation of an incremental backup. A number followed by a unit of time is accepted. For example, a setting of 9H would specify a nine-hour duration. Similarly, a setting of 2D would specify a two-day duration.
--cloud-read-ahead {partial | full}: Specifies the cache readahead strategy when SmartLink files are accessed. A partial strategy means that only the amount of data needed by the user is cached. A full strategy means that all file data will be cached when the user accesses a SmartLink file.
--cloud-writeback-frequency <duration>: Specifies the minimum amount of time to wait before OneFS updates cloud data with local changes. A number followed by a unit of time is accepted. For example, a setting of 9H would specify a nine-hour duration. Similarly, a setting of 2D would specify a two-day duration.
--verbose: Displays more detailed information.
--help | -h: Display help for this command.

Table 1. --operator=<value>--operator=<value>
Value	Description
eq	Equal. This is the default value.
ne	Not equal
lt	Less than
le	Less than or equal to
gt	Greater than
ge	Greater than or equal to
not	Not

Examples

The following example creates a file pool policy that moves all files in directory /ifs/data/chemical/arco/finance to the local storage target named Archive_2.

 isi filepool policies create Save_Fin_Data --begin-filter 
--path=/ifs/data/chemical/arco/finance --end-filter 
--data-storage-target Archive_2 --data-ssd-strategy=metadata

The following example matches older files that have not been accessed or modified later than specified dates, and moves the files to an archival tier of storage.

isi filepool policies create archive_old 
--data-storage-target ARCHIVE_1 --data-ssd-strategy avoid 
--begin-filter --file-type=file --and --birth-time=2013-09-01 
--operator=lt --and --accessed-time=2013-12-01 --operator=lt 
--and --changed-time=2013-12-01 --operator=lt --end-filter

Welcome

Welcome to Dell

PowerScaleOneFS CLI Command Reference

isi filepool policies create

Syntax

Options

Examples

Rate this content