Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

PowerScaleOneFS CLI Command Reference

isi cloud jobs create

Creates a CloudPool job to archive or recall files.

Syntax

isi cloud jobs create {archive | recall | restore-coi}  
[--files <string>]
[{--recursive | -r} {yes | no}]
[--accounts <string>]
[--expiration-date <timestamp>]
[--policy <string>]
[{--verbose | -v}]

Options

{archive | recall | restore-coi}
The type of job. Valid entries are archive, recall, and restore-coi.
--files <string>...
Specifies files or directory names to which the job applies. Use --files for each additional specification. Directory names are valid only for archive jobs.
{--recursive | -r} {yes | no}
Specifies whether the job should apply recursively to nested directories.
--accounts <string>
Specifies the cloud accounts to be used for restore-coi jobs. To specify additional cloud accounts, use the --accounts option.
--expiration-date <timestamp>
The expiration date for orphan objects. Use one of the following formats for <timestamp>:
  • A date string matching the pattern 'YYYY-MM-DD'
  • A date/time string matching the pattern 'YYYY-MM-DD[Thh:mm[:ss]]'
--policy <string>
The policy to use in an archive job.
{--verbose | -v}

Displays more detailed information.

Examples

For archive jobs, you can specify one or more directories to archive. The following command archives a single directory:

isi cloud jobs create archive --files /ifs/shares/dir1

The following example archives multiple directories:

isi cloud jobs create archive --files /ifs/shares/dir1 --files /ifs/shares/dir2

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  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: <>()\