Snapshots can be scheduled using protection policies. This procedure creates a single snapshot.
-
From the left navigation menu, select Data Protection and then Snapshots.
-
Click Create Snapshot.
-
Complete the fields:
Field
Description
Name (required)
Enter a name for the snapshot.
Path (required)
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.
Expiration time
If you want to make sure the snapshot expires some time in the future, specify that time here.
Indestructible
Enable this setting if you want the snapshot to be indestructible. This setting protects the snapshot from accidental or malicious deletion. For more information about indestructibility, see Keeping Indestructible Backups.
Caution
After saving the snapshot, you won't be able to delete the snapshot or disable its indestructibility without performing an authorized unlocking of the cluster's indestructibility mechanism.
-
Click Create.
The snapshot is created and is listed on the Snapshots page.
In the left navigation menu, select Data Protection and then Snapshots.
The following information is displayed for each snapshot:
Field |
Description |
---|---|
Created |
The time the snapshot was created. |
Name |
The name of the snapshot. |
Indestructible |
Reflects if the snapshot is indestructible (Yes) or not (No). |
Type |
Possible values:
|
Path |
The path that is captured by the snapshot. |
Policy |
The protection policy that created the snapshot. |
Expiration Time |
The time the snapshot is scheduled to expire. |
To manage snapshots via the CLI, use the following commands.
Tip
For full CLI command syntax, including arguments, enter the command at the CLI prompt in the <command> <subcommand> format provided in the table, followed by ?.
To do this task... |
Use this command... |
---|---|
Display snapshots. |
|
Display details of a specific snapshot. |
|
Take a snapshot. |
|
Modify a snapshot (includes locking and unlocking). |
|
Delete a snapshot. |
Comments
0 comments
Article is closed for comments.