Data transfers are coordinated according to Datamover policies and jobs. Policies specify what data is transferred, where the data is transferred to, and how often the data is transferred. You can also specify the policy expiration schedule.
There are four types of dataset policies that you can configure.
CREATION policy—the process of creating the dataset
One-time COPY policy—used for one-time data transfers
REPEAT_COPY policy—used for repeated transfers
EXPIRATION policy—how long the snapshot is stored
For detailed command syntax and descriptions, see the
OneFS CLI Command Reference, which you can find under the
Documentation tab on the
PowerScaleOneFSSupport site.
The common options across all policies that you can specify are as follows.
Table 1. Common OptionsThe following table displays the policy for each option.
Option
Policy
Priority
Relative priority of the dataset policy: LOW | NORMAL | HIGH
Schedule
Specific date/times at which this policy should run, date/time of the first run of the policy, and recurrence of jobs (repetitive schedule for the policy)
Parent execution policy ID
You can link a scheduled dataset CREATION policy to a REPEAT_COPY policy. Specify this option when creating the COPY policy.
The argument of the
--parent-exec-policy-id is the policy ID of the dataset CREATION policy.
The policy runs automatically when a job for its parent policy completes.
Run now
Create a job for a policy immediately instead of waiting for it to run as scheduled, regardless of the existing schedule
The key configuration parameters for the dataset policies are as follows.
Dataset CREATION policy
The dataset creation policy is used to create datasets once—or on a schedule—that can then be moved to other systems using the
isi dm policies create command. For example:
NOTE: Run the
isi dm policies modify --run-now=true command to manually run a policy.
The dataset
creates policy and dataset
copy policy can be "chained" together so that running the dataset
create policy runs the copy once the dataset creation is finished. For example:
For more information, see the
isi dm policies create command in the
PowerScaleOneFS CLI Command Reference Guide and in the
Datamover management tasks section of this guide.
The key configuration parameters are as follows for this policy:
Account ID
The
--creation-account-id is the storage system where you want to create the dataset. It can be a local or remote account.
Base Path or Object Store Key Prefix
The
--creation-base-path is the file system
Base Path or
Object Store Key Prefix used to create the dataset.
Expiration action
The
--creation-dataset-expiry-action (DELETE) is the action to be taken after the dataset expiration. Only the DELETE action is supported in
OneFS 9.4.0.0.
Retention Period
--creation-dataset-retention-period is the time in seconds after creation before the expiration action is performed by an expiration policy.
Reserve
The
--creation-dataset-reserve is the number of datasets in the current tree to protect from expiration regardless of the retention period.
Dataset COPY policy
The dataset copy policy is used to define a one-time copy of a dataset to or from a remote system. For example:
A repeat copy policy skips the initial baseline sync if the target base path contains a leaf dataset which is an ancestor of a source base path dataset.
The key configuration parameters for this policy:
Accounts
The
--copy-base-source-account-id is the source storage system containing the dataset that you want to copy from.
The
--copy-base-target-account-id is the target storage system where you want to copy the dataset to.
Source dataset
The
--reconnect parameter indicates that a first-time baseline copy is not necessary.
The
--repeat-copy-source-base-path is the base path (root) of the dataset on the source storage system to be used automatically.
Target dataset
These are the same options as the dataset create policy.
The
--copy-create-dataset-on-target is used to define a new dataset on the target storage system once the copy is complete.
The
--copy-base-target-dataset-type is the dataset type file on file dataset (FILE).
Dataset EXPIRATION policy
The dataset expiration policy creates jobs that look for expired datasets and runs their expiration actions. For example:
The key configuration parameter is the
--expiration-account-id <str> option, which is the storage system where you want to check for expired datasets, and the account where this expiration policy runs.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\