A dataset must be available before a copy, or repeat-copy data replication policy runs, as displayed in Figure 6. If a dataset is unavailable, the copy or repeat-copy replication policy fails. For more information about the copy and repeat-copy policies, see Replication policies.
The steps provided in this section assume a traditional push dataset creation, defined and initiated on the source cluster. After reviewing this section, see the Pull dataset creation policy section to define a pull dataset creation.
To create a dataset, use the isi dm policies create command with the CREATION policy option. As an example, use the following command:
isi dm policies create [Policy Name] NORMAL true CREATION --creation-account-id=[DM local account] --creation-base-path= --creation-dataset-retention-period= --creation-dataset-reserve= --creation-dataset-expiry-action=DELETE ––recurrence=”cron expression” --start-time="YYYY-MM-DD HH:MM:SS"
In the example above, the options specified include the following:
Check the dataset creation policy's status by running the isi dm jobs list and isi dm historical-jobs list. For more information about options for a running policy, refer to the Troubleshooting section. Once the dataset is created, it is listed under isi dm datasets list. The dataset creation uses a SnapshotIQ snapshot, and also displays under isi snapshot list, with an isi_dm preceding the snapshot name.
A pull dataset creation policy is defined and initiated on the target cluster. To perform a pull dataset creation on the source cluster, the command above is issued on the target cluster. However, the --creation-account-id is updated to the source cluster’s account, found under isi dm accounts list on the target cluster. All other fields in the command remain the same, as explained above.