protectionpolicy create

--clone-type CLOUD_REPLICATION|NATIVE_REPLICATION|LOCAL

Specifies what type of protection to configure on the path:

--name POLICY_NAME

Specifies a name for the protection policy.

--schedule SCHEDULE

Defines the schedule for snapshots and replication.

The schedule includes a period defined as a number of time units, a start date and time, a retention time limit for local snapshots and, for async replication, a retention time for remote snapshots.

Specify SCHEDULE in the following format:

every <number><time units> start at YYYY-MM-DD HH:MM:SS keep-local <number><time units> keep-remote <number><time units>

Where:

Example: --schedule every 90m start-at 2025-07-27 20:10:35 keep-local 10h keep-remote 7d

--snapshot-prefix PREFIX

Specifies the prefix to use in the names of snapshots.

The name of each snapshot will be <prefix>_<timestamp>, where <prefix> is the prefix specified here and <timestamp> is the time the snapshot is created, in the format yyyy-mm-ddTHH:MM:SS.SSSSSSzzz (T denotes time and doesn't represent a value, zzz is the timezone, and the time is accurate to the microsecond). For example, if the prefix is dev, a snapshot taken at 8:15 pm UTC on 20th November 2024 would be named dev_2024-11-20T20:15:06.144783UTC.

--enable-lock

Makes the policy indestructible. Once this setting is enabled, deleting or modifying the protection policy requires unlocking the cluster's indestructibility mechanism.

--peer-id PEER_ID

Specifies the replication peer if --clone-type is either CLOUD_REPLICATION or NATIVE_REPLICATION.

If --clone-type is CLOUD_REPLICATION, specify the ID of an S3 replication peer.

If --clone-type is NATIVE_REPLICATION, specify the ID of an async replication peer.

Specify the ID as an integer.