All Products
Search

This Product

    Object Storage Service:Feature differences between ossutil 1.0 and 2.0

    Document Center

    Object Storage Service:Feature differences between ossutil 1.0 and 2.0

    Last Updated:Oct 10, 2025

    This topic describes the feature differences between ossutil 1.0 and 2.0.

    Item

    Version 1.0

    Version 2.0

    Configuration file

    Uses the INI format.

    A configuration file supports only one set of configurations.

    The supported section types are Credentials, Bucket-Endpoint, and Bucket-Cname.

    Uses the INI format.

    A configuration file supports multiple sets of configurations. You can specify a section name using the --profile option.

    The profile and buckets section types are added.

    This version is compatible with the Credentials, Bucket-Endpoint, and Bucket-Cname sections of earlier versions, but using these sections is not recommended.

    Basic configurations (required)

    AccessKey ID, AccessKey secret, and Endpoint

    AccessKey ID, AccessKey secret, and region ID

    Command

    Commands vary based on the operating system. For example, on a Linux operating system, the command is ossutil+[Command].

    Commands are the same across different operating systems. The command is ossutil+[Command].

    Commands

    Bucket configurations

    Features such as logging and lifecycle are categorized under the root command.

    • Each API operation corresponds to a command under the ossutil api subcommand.

    • Configuration parameters support both XML and JSON formats.

    • Supports format conversion for output content, such as converting the output to the JSON format.

    rm command

    • Supports deleting buckets.

    • A single operation can delete multiple types of data, such as objects and shards.

    Example: rm oss://bucket/prefix -r -f -m

    • Does not support deleting buckets. To delete a bucket, you can use the new rb command.

    • A single operation can delete only one type of data. For example, to delete objects and shards, you must run separate commands.

    For example: rm oss://bucket/prefix -r -f

    rm oss://bucket/prefix -m -r -f

    Append command

    • The command is appendfromfile.

    • The data source can only be a local path.

    • The command is append.

    • The data source can be a local path, an OSS resource URL, or standard input.

    cat command

    Supports only outputting the entire content of a file.

    Supports outputting a part of a file, such as the first 10 bytes or the last 10 bytes.

    cp command

    When you copy an object, only the object data is copied. The metadata and tags are not copied.

    When you copy an object, you can use the --copy-props option to control how metadata and tags are copied. You can choose not to copy them, copy only the metadata, or copy both the metadata and tags.

    By default, metadata and tags are copied.

    Modify object attributes

    (permissions, storage class, metadata, and tags)

    • You can use the set-acl command to modify object permissions.

    • You can use the set-meta command to modify object metadata.

    • You can use the cp command to modify the object storage class and tags.

    • You can use the object-tagging command to modify object tags.

    • The commands for modifying object attributes are merged into a single command: set-props. You can select the appropriate API operation based on the attribute parameters that you need to modify. This makes attribute modification more efficient.

    • The set-acl and set-meta commands are supported as aliases, but their command-line parameters are different from the original commands.

    • Supports various instructions for modifying metadata and tags, such as replace, update, purge, and delete.

    Presigned URL

    • The command is sign.

    • Specifies the expiration time of the signature. Only time intervals are supported, such as 120 seconds.

    • The command is presign.

    • The sign command is supported as an alias, but its command-line parameters are different from the original command.

    • Specifies the expiration time of the signature. Both time intervals, such as 120 seconds, and absolute time are supported.

    • For v4 signatures, you cannot generate a presigned URL that is valid for more than 7 days.

    Version recovery

    Supports only restoring the latest version by deleting the delete marker.

    • Supports restoring the latest version by deleting the delete marker.

    • Supports restoring a specific version by copying it based on the version index.

    • Supports restoring a specific version by copying it based on the time index.

    hash

    Supports only calculating the hash value of a local file.

    • Supports local files.

    • Supports object paths.

    • Supports batch operations.

    sync

    • If you do not use the --delete parameter, the effect is the same as the cp command. It scans the source and copies files simultaneously, with no limit on the maximum number of files that can be copied.

    • If you use the --delete parameter, the data replication stage also scans the source and copies files simultaneously.

    • Regardless of whether the --delete parameter is set, a limit is imposed on the maximum number of files. The default value is 1,000,000, and the maximum value is 5,000,000.

    • It first scans the source and destination lists, synchronizes the data, and then deletes files at the destination based on the --delete option. This workflow provides better synchronization performance when used with the --update or --size-only option.

    Options

    --include

    --exclude

    • Supports only matching object or file names.

    • When multiple include and exclude conditions are specified, each rule is applied sequentially from left to right to determine the final match.

    • Supports matching object or file names.

    • Supports matching object or file paths.

    • When multiple include and exclude conditions are specified, the rules are applied sequentially from left to right. If a rule is matched (either include or exclude), subsequent checks are immediately stopped.

    --snapshot-path

    Supported

    Not supported

    --encoding-type

    Applies to both input and output parameters.

    • For high-level commands, this parameter applies only to input parameters, not to the output.

    • For API-level commands, this parameter has the same meaning as the corresponding parameter in the API operation.

    Exclusion options for the destination

    Supports only --update.

    Supports --update, --size-only, --checksum, and --ignore-existing.

    Speed limit

    Supports limiting only the upload speed. You can use the --max-speed option to set the limit.

    Supports limiting both upload and download speeds. You can use the --bandwidth-limit option to set the limit.

    Default configurations

    Signature version

    Signature Version 1.

    Signature Version 4. When you use a v4 presigned URL, the maximum validity period is one week.

    HTTPS protocol

    If not specified, the HTTP protocol is used by default.

    The HTTPS protocol is used by default.

    Object listing API

    Uses the ListObjects API operation.

    Uses the ListObjectsV2 API operation by default. You can switch to the ListObjects API operation using the --list-objects option.

    read-timeout

    Specifies the client read/write timeout. The default value is 1,200 seconds.

    The default value is 20 seconds.

    connect-timeout

    Specifies the client connection timeout in seconds. The default value is 120 seconds.

    The default value is 10 seconds.

    Resumable transfer

    Supported and enabled by default.

    Supported and disabled by default.