Difference between revisions of "Snapshot Schedules"
m (→Long Term Retention Rules) |
m (→Long Term Retention Rules) |
||
| Line 14: | Line 14: | ||
[[File:Create Snapshot Schedule - Select Vols & Shrs.jpg|512px]] | [[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. | 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 - Snap Set.jpg|512px]] | ||
Revision as of 15:52, 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.
Schedule Interval
Snapshot Settings
Snapshots schedules automatically expire the oldest snapshot once the specified maximum retained snapshots setting has been reached.
