A protection policy is a reusable configuration that defines a schedule for taking snapshots and optionally replicating data to a specified S3 replication peer. It also defines how long to retain local snapshots. Once defined, it can be specified in the configuration of a protected path.
For example, you could set snapshots and S3 backup to be done on July 1st, 2020 at midnight and then once every day. Snapshots would be taken every day at midnight beginning July 1st and replicated to an S3 replication peer.
From the left navigation menu, select Data Protection and then Protection Policies.
Click + Create Protection Policy.
In the Add Protection Policy dialog, complete the fields:
Enter a name for the policy.
Optionally select an S3 replication peer from the dropdown. This defines an S3 bucket to which to back up the cluster's data.
To create a new S3 protection peer, see Managing S3 Replication Peers.
Enter a prefix for the snapshot names that will be saved to the Snapshots directory and/or the S3 replication peer.
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
Tdenotes time and doesn't represent a value,
zzzis 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 called:
Define a schedule:
The scheduling fields provided enable you to set one frequency period and start time. If you want to configure more than one frequency and start time, you can add additional lines by clicking the Add Schedule button.
To set the start time, click in the Start at field and a calendar appears. Clicking the start date you want in the calendar and adjust the time :
To set a frequency period, select seconds, minutes, hours or days from the Period dropdown and enter the number of units in the Every field. If an S3 replication peer is selected, the minimum interval between replications is 6 hours. Otherwise, shorter intervals are supported.
Set the keep local copy for period to determine how long after creation snapshots on the local cluster will be deleted.
Copies on an S3 replication peer do not expire. The Keep remote copy for field is disabled. It is reserved for future use.
The policy is created and listed in the Protection Policies page.
To modify the configuration of a protection policy, click to open the Actions menu for the policy and select Edit. Make your changes and then click Update.
To remove a protection policy, click to open the Actions menu for the policy and select Remove. Click Yes to confirm the removal.
To manage protection policies via the VAST CLI, use the following commands.