Parameter/Option | Description |
file_url | The path of the local file. Examples: /localfolder/examplefile.txt in Linux and D:\localfolder\examplefile.txt in Windows. |
cloud_url | The path in which you want to store the uploaded local file. Specify the path in the oss://bucketname/objectname format. Example: oss://examplebucket/examplefile.txt . |
-r, --recursive | Specifies recursive operations. If you specify this option, ossutil performs the operation on all objects in the bucket that meet the specified condition. If you do not specify this option, ossutil performs the operation only on the specified object. |
-f --force | Forces the operation without requiring user confirmation. |
-u, --update | Specifies that ossutil uploads files only when the destination objects do not exist or when the last modified time of the files is later than that of the destination objects. |
--maxupspeed | The maximum upload speed. Unit: KB/s. The default value is 0, which indicates that the upload speed is not limited. |
--enable-symlink-dir | Specifies that ossutil uploads subdirectories in directories to which symbolic links point. By default, ossutil does not upload subdirectories in directories to which symbolic links point. |
--disable-all-symlink | Specifies that ossutil ignores subdirectories and objects in directories to which symbolic links point. |
--disable-ignore-error | Specifies that errors are not ignored during batch operations. |
--only-current-dir | Specifies that ossutil uploads only objects in the current directory. Subdirectories in this directory and objects in the subdirectories are ignored. |
--bigfile-threshold | The threshold for performing a resumable upload task. If the object size exceeds the threshold, resumable upload is used. Unit: bytes. Default value: 100 MB. Valid values: 0 to 9223372036854775807. |
--part-size | The part size. Unit: bytes. By default, ossutil determines the part size based on the object size. Valid values: 1 to 9223372036854775807. |
--checkpoint-dir | The directory in which information about the resumable upload task is stored. If the task fails, ossutil automatically creates a directory named .ossutil_checkpoint and saves the checkpoint information in the directory. After the task is successful, ossutil deletes the directory. If you specify a checkpoint directory, make sure that the directory can be deleted. |
--encoding-type | The encoding of the object names. Set the value to url. If you do not specify this option, the names of objects are not encoded. |
--include | Includes all objects that meet the specified conditions. For more information about the syntax and examples, see Batch upload objects that meet specified conditions. |
--exclude | Excludes all objects that meet the specified conditions. For more information about the syntax and examples, see Batch upload objects that meet specified conditions. |
--meta | The object metadata. Object metadata includes standard HTTP headers and user metadata. User metadata starts with x-oss-meta- . Format: header:value#header:value format. Example: Cache-Control:no-cache#Content-Encoding:gzip . For more information, see Manage object metadata. |
--acl | The access control list (ACL) of the objects. Valid values: default: The ACL of the objects is the same as the ACL of the bucket in which the objects are stored. This is the default ACL setting for objects. private: Only the bucket owner can perform read and write operations on the objects in the bucket. Other users cannot access the objects in the bucket. public-read: Only the bucket owner can perform write operations on the objects in the bucket. All users, including anonymous users, can perform read operations on the objects in the bucket. This may result in unrestricted access to the data in your bucket and unexpected high fees. If a user uploads prohibited data or information, your legitimate interests and rights may be infringed. We recommend that you do not set the object ACL to this value except in special cases. public-read-write: All users, including anonymous users, can perform read and write operations on objects in the bucket. This may result in unrestricted access to the data in your bucket and unexpectedly high fees. Exercise caution when you set the object ACL to public-read-write.
|
--snapshot-path | The directory in which the snapshots of uploaded objects are stored. In the subsequent upload task, ossutil reads the snapshot information from the specified directory and performs incremental upload. |
--disable-crc64 | Specifies that CRC-64 is disabled. By default, ossutil enables CRC-64 during data transmission. |
--disable-dir-object | Specifies that no OSS object is generated for the directory during object upload. |
--payer | The payer of the fees that are generated by the operation. If you want the requester who wants to access the resources in the specified path to pay the fees that are generated by the operation, set this option to requester. |
--tagging | The tags of objects. Format: TagkeyA=TagvalueA&TagkeyB=TagvalueB.... . |
-j, --jobs | The number of concurrent tasks performed across multiple objects. Valid values: 1 to 10000. Default value: 3. |
--parallel | The number of concurrent tasks that can be performed on a single object. Valid values: 1 to 10000. By default, if you do not specify this option, ossutil sets the value of this option based on the operation type and the object size. |
--start-time | The beginning of the time range to filter objects by the last modified time. The value is a UNIX timestamp. Objects whose last modified time is earlier than the UNIX timestamp are ignored. Note Only ossutil 1.7.18 and later support this parameter. For more information about how to update ossutil, see update. |
--end-time | The end of the time range to filter objects by the last modified time. The value is a UNIX timestamp. Objects whose last modified time is later than the UNIX timestamp are ignored. Note If both --start-time and --end-time are specified, the command applies only to objects whose last modified time is within the range specified by --start-time and --end-time. Only ossutil 1.7.18 and later support this parameter. For more information about how to update ossutil, see update.
|