From the left navigation menu, select Data Protection and then Snapshots.
Click Create Snapshot.
Complete the fields:
Enter a name for the snapshot.
Enter the path to a directory. The snapshot will include all files and folders under the specified directory at the time of taking the snapshot.
If you want to make sure the snapshot expires some time in the future, specify that time here.
The snapshot is created and is listed on the Snapshots page.
Use snapshot policies to schedule snapshots. Set a retention limit to make sure older snapshots are deleted to allow the policy to keep taking new snapshots on schedule. Snapshots can be scheduled daily, weekly and monthly at multiple times. When setting up snapshot policies, be mindful of the following:
The maximum number of snapshots that can be retained for the cluster is 50. This limit includes all snapshots, including:
When the maximum is reached, a snapshot cannot be taken until another snapshot is deleted by manual deletion, expiration or retention limit.
However, deletion due to retention limit occurs after the latest snapshot that causes the retention limit to be exceeded is taken. Therefore, effectively, the maximum number of snapshots you can schedule to be taken successfully is equal to 50-n, where n is the number of snapshot policies.
A snapshot cannot be deleted while it is locked.
For example, one snapshot policy with a retention limit of 49 would continue taking snapshots indefinitely assuming no more than 48 snapshots are locked, no manual snapshots are taken and no additional snapshot policies are defined. In this example, if an additional snapshot is taken manually and does not expire before the policy takes the 49th snapshot, the snapshot policy will fail to take the 50th snapshot.
From the left navigation menu, select Data Protection and then Snapshot Policies.
Click Create Snapshot policy.
Complete the fields:
A name for the snapshot policy.
A directory path. A snapshot of this directory will be taken periodically.
A prefix to include in each snapshot name. If no prefix is specified, the policy's name is used.
The name of each snapshot will be <prefix>_<timestamp>, where <prefix> is the prefix specified here (or policy name if not specified) 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:
A maximum number of snapshots to retain. When needed, the oldest snapshot is deleted to maintain the limit. If not specified, an unlimited number is retained. The deletion actually occurs after the new snapshot is created.
ON by default. Switch OFF to disable the policy and ON to re-enable the policy. While the policy is disabled, snapshots scheduled in the policy are not taken.
Use this drop-down to schedule the snapshots. Start by selecting an interval from the dropdown:
After selecting the interval, more drop-downs let you specify more exact details of the periodic timing. Multiple times can be selected:
On - choose one or more days of the week
At - choose one or more hours of the day before the colon and one or more minutes of the hour following the colon.
For example, to schedule snapshots to be taken every week on Monday and Wednesday at 09:00 and at 18:00, you would make these selections:
The total number of snapshots that can be taken is limited to 49.
The snapshot policy is created.
Locking a snapshot protects the snapshot from deletion.
A locked snapshot is not deleted by any of the following:
Exceeding its expiration time
Due to its snapshot policy's retention limit
User attempted deletion without first unlocking it
Snapshots are created in an unlocked state.
Locked snapshots count towards the retention limit of their snapshot policy. If the number of locked snapshots that were created by a given snapshot policy is equal to the retention limit, the snapshot policy stops taking new snapshots.