Difference between revisions of "Snapshot Schedules"
m |
m (→Select Volumes & Shares) |
||
| (10 intermediate revisions by the same user not shown) | |||
| Line 3: | Line 3: | ||
Snapshot schedules create a space efficient snapshots automatically on a schedule. Schedules may contain any number of Storage Volumes and Network Shares from any number of systems in a given storage grid. We recommend that a snapshot schedule be created for all mission critical storage volumes and network shares so that one has rollback ability in the event that a user deletes data or in the event that there's a security breach so that auditing and any necessary data recovery can be done using snapshots. | Snapshot schedules create a space efficient snapshots automatically on a schedule. Schedules may contain any number of Storage Volumes and Network Shares from any number of systems in a given storage grid. We recommend that a snapshot schedule be created for all mission critical storage volumes and network shares so that one has rollback ability in the event that a user deletes data or in the event that there's a security breach so that auditing and any necessary data recovery can be done using snapshots. | ||
| − | [[File: | + | [[File:Crt Snapshot Schdl - Web.jpg|512px]] |
| − | + | One may configure multiple snapshot schedules with any number of Storage Volumes and Network Shares from any number of systems in a storage grid. Volumes and Shares may also be associated with multiple Snapshot Schedules each maintaining independent snapshot rotations. For storage volumes and network shares containing critical data one should create a Snapshot Schedule that will create snapshots at least once a day. A second schedule that creates weekly snapshots is also recommended. | |
| + | ===General=== | ||
| + | Snapshots schedules maintain a rotating snapshot history for the specified Storage Volumes and Network Shares to facilitate easy data recovery. | ||
| + | |||
| + | [[File:Create Snapshot Schedule - General.jpg|412px]] | ||
===Schedule Interval=== | ===Schedule Interval=== | ||
| − | + | Choose the day/hour for snapshots. | |
| + | [[File:Create Snapshot Schedule - Intvl.jpg|512px]] | ||
===Select Volumes & Shares=== | ===Select Volumes & Shares=== | ||
| − | [[File:Create Snapshot Schedule - Select | + | Select the volumes and shares to be associated with the schedule. '''Note:''' at least one volume or share must be selected. |
| + | |||
| + | [[File:Create Snapshot Schedule - Select Vols & Shrs.jpg|512px]] | ||
| + | ===Snapshot Settings=== | ||
| + | Snapshots schedules automatically expire the oldest snapshot once the specified maximum retained snapshots setting has been reached. | ||
| − | + | [[File:Create Snapshot Schedule - Snap Set.jpg|512px]] | |
| − | [[File:Create Snapshot Schedule - | + | |
Latest revision as of 16:01, 19 December 2023
Snapshot schedules create a space efficient snapshots automatically on a schedule. Schedules may contain any number of Storage Volumes and Network Shares from any number of systems in a given storage grid. We recommend that a snapshot schedule be created for all mission critical storage volumes and network shares so that one has rollback ability in the event that a user deletes data or in the event that there's a security breach so that auditing and any necessary data recovery can be done using snapshots.
One may configure multiple snapshot schedules with any number of Storage Volumes and Network Shares from any number of systems in a storage grid. Volumes and Shares may also be associated with multiple Snapshot Schedules each maintaining independent snapshot rotations. For storage volumes and network shares containing critical data one should create a Snapshot Schedule that will create snapshots at least once a day. A second schedule that creates weekly snapshots is also recommended.
General
Snapshots schedules maintain a rotating snapshot history for the specified Storage Volumes and Network Shares to facilitate easy data recovery.
Schedule Interval
Choose the day/hour for snapshots.
Select the volumes and shares to be associated with the schedule. Note: at least one volume or share must be selected.
Snapshot Settings
Snapshots schedules automatically expire the oldest snapshot once the specified maximum retained snapshots setting has been reached.
