Snapshot Schedules: Difference between revisions

From OSNEXUS Online Documentation Site
Jump to navigation Jump to search
← Older edit
VisualWikitext
mNo edit summary
m Fix CLI arg names: --days, --hours (am/pm), --offset-minutes, --volume-list, --share-list; fix snapshot revert/clone args; fix volume-list --show-snaps
 
(11 intermediate revisions by the same user not shown)
Line 1: Line 1:
[[Category:admin_guide]]
Snapshot schedules automate the creation of space-efficient, point-in-time snapshots for storage volumes and network shares. Schedules can run on a calendar basis (specific days and hours) or at a fixed interval. When the maximum snapshot count is reached, the oldest snapshot is automatically expired, giving each volume or share a rolling history window.
 
Snapshots are strongly recommended for all mission-critical volumes and shares — they provide rapid rollback in the event of accidental deletion, data corruption, or ransomware.
 
__TOC__
 
== Schedule Types ==
 
{| class="wikitable"
! Type !! Description !! Best For
|-
| '''Calendar-based''' || Runs on selected days of the week at selected hours of the day, with an optional minute offset. || Daily or weekly backup windows; business-hour snapshots
|-
| '''Interval-based''' || Runs every N minutes (minimum 3). || High-frequency snapshots for critical workloads
|}
 
== Creating a Snapshot Schedule ==
 
'''Navigation:''' Storage Management → Snapshot Schedules → (toolbar) Create Snapshot Schedule
 
=== General Tab ===
 
{| class="wikitable"
! Field !! Description
|-
| '''Name''' || Unique name for the schedule
|-
| '''Description''' || Optional description
|-
| '''Enabled''' || Toggle to activate or pause the schedule without deleting it
|-
| '''Resource Group''' || Scope the schedule to a resource group (optional; for multi-tenant environments)
|}
 
=== Schedule Interval Tab ===
 
'''Calendar-based schedule:'''
 
Select one or more days of the week and one or more hours of the day. Snapshots will be taken at each selected hour on each selected day.
 
* '''Offset (minutes)''' — Optional minute offset past the hour (0–59). Use this to stagger multiple schedules and avoid simultaneous I/O.
 
'''Interval-based schedule:'''
 
* '''Interval (minutes)''' — How often to take a snapshot. Minimum enforced value: 3 minutes.
 
'''CLI — Calendar-based:'''
<pre>
# Every Monday and Friday at 2am and 6pm, 15 minutes past the hour
qs snap-schedule-create \
  --name=daily-snap \
  --days=mon,fri \
  --hours=2am,6pm \
  --offset-minutes=15
</pre>
 
'''CLI — Interval-based:'''
<pre>
# Every 30 minutes
qs snap-schedule-create \
  --name=frequent-snap \
  --schedule-type=interval \
  --interval=30
</pre>
 
=== Select Volumes & Shares Tab ===
 
At least one storage volume or network share must be associated with a schedule. Volumes and shares from any system in the storage grid can be selected.
 
'''CLI — Associate volumes and shares at creation time:'''
<pre>
qs snap-schedule-create \
  --name=daily-snap \
  --days=mon,tue,wed,thu,fri \
  --hours=2am \
  --volume-list=vol1,vol2 \
  --share-list=share1
</pre>
 
'''CLI — Add or remove associations after creation:'''
<pre>
# Add a volume to an existing schedule
qs snap-schedule-add --schedule=daily-snap --volume-list=vol3
 
# Add a share to an existing schedule
qs snap-schedule-add --schedule=daily-snap --share-list=share2
 
# Remove a volume from a schedule
qs snap-schedule-remove --schedule=daily-snap --volume-list=vol3
</pre>
 
A single volume or share can be associated with multiple schedules simultaneously — for example, an hourly schedule for short-term retention and a weekly schedule for long-term retention.
 
=== Snapshot Settings Tab ===
 
==== Rotating Snapshot Count (max-snaps) ====
 
The '''max-snaps''' setting controls how many rotating snapshots the schedule maintains. When the limit is reached, the oldest snapshot created by this schedule is automatically deleted before a new one is taken.
 
{| class="wikitable"
! Setting !! Default !! Range
|-
| Max Snapshots || 5 || 1–1000
|}
 
'''Recommendation:'''
* Daily schedule: 7–14 snapshots (one to two weeks of history)
* Weekly schedule: 4–8 snapshots (one to two months of history)
* Hourly schedule: 24–48 snapshots (one to two days of history)
 
==== Long-Term Retention Counts ====
 
In addition to the rotating window, schedules support long-term retention tiers. Snapshots promoted to a retention tier are not subject to the max-snaps limit and are preserved until their tier count is exceeded.
 
{| class="wikitable"
! Parameter !! Tier !! Description
|-
| <code>rc-hourly</code> || Hourly || Number of hourly snapshots to retain long-term
|-
| <code>rc-dailies</code> || Daily || Number of daily snapshots to retain long-term
|-
| <code>rc-weeklies</code> || Weekly || Number of weekly snapshots to retain long-term
|-
| <code>rc-monthlies</code> || Monthly || Number of monthly snapshots to retain long-term
|-
| <code>rc-quarterlies</code> || Quarterly || Number of quarterly snapshots to retain long-term
|}
 
'''CLI — Create schedule with long-term retention:'''
<pre>
qs snap-schedule-create \
  --name=tiered-snap \
  --days=mon,tue,wed,thu,fri,sat,sun \
  --hours=12am \
  --max-snaps=7 \
  --rc-dailies=30 \
  --rc-weeklies=12 \
  --rc-monthlies=12 \
  --volume-list=vol1
</pre>
 
This example keeps 7 rolling daily snapshots plus 30 daily, 12 weekly, and 12 monthly long-term snapshots — approximately 13 months of history.
 
== Managing Schedules ==
 
=== List and Inspect ===
 
'''Navigation:''' Storage Management → Snapshot Schedules
 
'''CLI:'''
<pre>
# List all snapshot schedules
qs snap-schedule-list
 
# Get details for a specific schedule
qs snap-schedule-get --schedule=daily-snap
 
# List all volume/share associations for a schedule
qs snap-schedule-assoc-list --schedule=daily-snap
</pre>
 
=== Enable and Disable ===
 
Schedules can be paused without being deleted. A disabled schedule will not create new snapshots but its existing snapshots are preserved.
 
'''Navigation:''' Storage Management → Snapshot Schedules → (right-click) → Enable / Disable
 
'''CLI:'''
<pre>
qs snap-schedule-enable --schedule=daily-snap
qs snap-schedule-disable --schedule=daily-snap
</pre>
 
=== Modify a Schedule ===
 
'''Navigation:''' Storage Management → Snapshot Schedules → (right-click) → Modify
 
'''CLI:'''
<pre>
# Change to run at 3am instead of 2am, increase retention to 14
qs snap-schedule-modify \
  --schedule=daily-snap \
  --hours=3am \
  --max-snaps=14
</pre>
 
=== Trigger a Schedule Immediately ===
 
Run a schedule right now without waiting for the next scheduled time. This takes a snapshot of all associated volumes and shares immediately and counts toward the rotating window.
 
'''Navigation:''' Storage Management → Snapshot Schedules → (right-click) → Trigger Now
 
'''CLI:'''
<pre>
qs snap-schedule-trigger --schedule=daily-snap
</pre>
 
=== Delete a Schedule ===
 
Deleting a schedule does not automatically delete the snapshots it created. Existing snapshots remain until manually deleted or until another schedule's retention policy removes them.
 
'''Navigation:''' Storage Management → Snapshot Schedules → (right-click) → Delete
 
'''CLI:'''
<pre>
qs snap-schedule-delete --schedule=daily-snap
</pre>
 
== Creating One-off (Immediate) Snapshots ==
 
To take an unscheduled snapshot of a specific volume or share at any time:
 
'''Navigation:''' Storage Management → Storage Volumes → (right-click volume) → Create Snapshot
 
'''CLI:'''
<pre>
# Snapshot a single volume
qs volume-snapshot --volume=vol1 --name=pre-patch-snap
 
# Snapshot a network share
qs share-snapshot --share=share1 --name=pre-patch-snap
 
# Snapshot all volumes in a volume group simultaneously
qs volume-group-snapshot --volume-group=vg1
</pre>
 
== Snapshot Naming ==
 
All schedule-created snapshots use GMT-based names for compatibility with Windows Previous Versions (VSS):
 
<pre>
volname@GMT-2024.06.17-02.15.00
</pre>
 
The timestamp is always in UTC. Snapshots appear in the <code>_snaps/</code> folder over NFS/SMB and in the <code>.zfs/snapshot/</code> directory (if NFS snapshot browsing is enabled).
 
== Recovering Data from Snapshots ==
 
=== Browse and Copy Files (NFS/SMB) ===
 
Snapshots are accessible directly from the client without administrator intervention. Navigate to the <code>_snaps</code> folder at the root of any mounted share or volume:
 
<pre>
# NFS
ls /mnt/data/_snaps/
cd /mnt/data/_snaps/@GMT-2024.06.17-02.15.00/
cp /mnt/data/_snaps/@GMT-2024.06.17-02.15.00/important-file.txt /mnt/data/
 
# SMB (Windows)
# Right-click the share in Explorer → Properties → Previous Versions
</pre>
 
For ZFS-backed pools with snapshot browsing enabled:
<pre>
ls /mnt/data/.zfs/snapshot/
</pre>
 
=== Revert a Volume to a Snapshot ===
 
Reverting replaces the current volume contents with the snapshot state. This is a destructive operation — all writes after the snapshot point are lost.
 
'''Navigation:''' Storage Management → Storage Volumes → (right-click volume) → Revert to Snapshot → select snapshot
 
Pass the snapshot name as the <code>--volume</code> argument — the snapshot is identified by its own name, not a <code>--snapshot</code> parameter:
 
'''CLI:'''
<pre>
qs volume-snapshot-revert --volume=vol1@GMT-2024.06.17-02.15.00
</pre>
 
=== Clone a Snapshot to a New Volume ===
 
To access snapshot data without reverting, clone the snapshot to a new read-write volume. As with revert, pass the snapshot name as <code>--volume</code>:
 
'''Navigation:''' Storage Management → Storage Volumes → (right-click snapshot) → Clone
 
'''CLI:'''
<pre>
qs volume-clone --volume=vol1@GMT-2024.06.17-02.15.00 --name=vol1-clone
</pre>
 
== Troubleshooting ==
 
=== Snapshots Not Being Created ===
 
# Verify the schedule is enabled: <code>qs snap-schedule-get --schedule=daily-snap</code>
# Confirm at least one volume or share is associated: <code>qs snap-schedule-assoc-list --schedule=daily-snap</code>
# Check the QuantaStor service log for scheduler errors: <code>journalctl -u quantastor --since "1 hour ago" | grep -i sched</code>
# Verify the storage pool has sufficient free space — snapshots cannot be created if the pool is full.
 
=== Snapshots Not Being Expired ===
 
# Confirm <code>max-snaps</code> is set to a value greater than 0 on the schedule.
# Check whether long-term retention counts (<code>rc-dailies</code>, etc.) are protecting snapshots from expiration — retained snapshots are not subject to the max-snaps limit.
# If a snapshot is pinned or has a dependent clone, it cannot be deleted until the clone is removed.
 
=== Storage Pool Filling Up Due to Snapshots ===
 
Snapshots consume space proportional to the amount of data changed since the snapshot was taken. If a volume sees heavy write activity, snapshots accumulate space quickly.
 
# Reduce <code>max-snaps</code> to keep fewer snapshots.
# Increase the snapshot interval to reduce frequency.
# Delete old manual snapshots that are no longer needed.
# Monitor per-snapshot space usage in the Storage Volumes panel.


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.
=== Schedule Ran But No Snapshot Visible ===


[[File:Create Snapshot Schedule Web.jpg|512px]]
Snapshots created by a schedule are listed under the associated volume or share, not under the schedule itself.


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. 
'''Navigation:''' Storage Management → Storage Volumes → (expand volume) → Snapshots


'''CLI (shares):'''
<pre>
qs share-list --include-snapshots=true
</pre>


===Schedule Interval===
For volumes, snapshots appear as child entries in the WUI under the parent volume. There is no CLI filter for volume snapshots — use <code>volume-list</code> and look for entries where <code>Is Snapshot</code> is true.
[[File:Create Snapshot Schedule - Schedule Interval.jpg|512px]]


== CLI Quick Reference ==


===Select Volumes & Shares===
{| class="wikitable"
[[File:Create Snapshot Schedule - Select Volumes & Shares.jpg|512px]]
! Command !! Short Form !! Description
|-
| <code>snap-schedule-create</code> || <code>sch-create</code> || Create a new snapshot schedule
|-
| <code>snap-schedule-modify</code> || <code>sch-modify</code> || Modify an existing schedule
|-
| <code>snap-schedule-delete</code> || <code>sch-delete</code> || Delete a schedule (snapshots are preserved)
|-
| <code>snap-schedule-enable</code> || <code>sch-enable</code> || Enable a paused schedule
|-
| <code>snap-schedule-disable</code> || <code>sch-disable</code> || Disable a schedule without deleting it
|-
| <code>snap-schedule-trigger</code> || <code>sch-trigger</code> || Run the schedule immediately
|-
| <code>snap-schedule-list</code> || <code>sch-list</code> || List all snapshot schedules
|-
| <code>snap-schedule-get</code> || <code>sch-get</code> || Get details for a schedule
|-
| <code>snap-schedule-add</code> || <code>sch-add</code> || Associate a volume or share with a schedule
|-
| <code>snap-schedule-remove</code> || <code>sch-remove</code> || Remove a volume or share association
|-
| <code>snap-schedule-assoc-list</code> || <code>scha-list</code> || List all associations for a schedule
|-
| <code>volume-snapshot</code> || <code>v-snap</code> || Create an immediate one-off snapshot of a volume
|-
| <code>share-snapshot</code> || <code>shr-snap</code> || Create an immediate one-off snapshot of a share
|-
| <code>volume-snapshot-revert</code> || <code>v-snap-revert</code> || Revert a volume to a snapshot point-in-time
|-
| <code>volume-group-snapshot</code> || <code>vg-snap</code> || Snapshot all volumes in a volume group simultaneously
|}


== See Also ==


===Long Term Retention Rules===
* [[Network_Shares|Network Shares]] — Enabling snapshot browsing over NFS/SMB (<code>_snaps</code> folder, <code>.zfs</code> directory)
Snapshots schedules automatically expire the oldest snapshot once the specified maximum retained snapshots setting has been reached. 
* [[Storage_Pools,_Volumes,_System|Storage Volumes]] — Managing volumes and viewing snapshots
* [[Remote-replication_(DR)|Remote Replication (DR)]] — Replicating snapshots off-site for disaster recovery
* [[Backup_Policies|Backup Policies]] — File-level backup as a complement to block-level snapshots
* [[Security_Configuration|Security Configuration]] — Resource groups for scoping schedule access


[[File:Create Snapshot Schedule - Long Term Retention Rules.jpg|512px]]
[[Category:admin_guide]]

Latest revision as of 15:06, 17 June 2026

Snapshot schedules automate the creation of space-efficient, point-in-time snapshots for storage volumes and network shares. Schedules can run on a calendar basis (specific days and hours) or at a fixed interval. When the maximum snapshot count is reached, the oldest snapshot is automatically expired, giving each volume or share a rolling history window.

Snapshots are strongly recommended for all mission-critical volumes and shares — they provide rapid rollback in the event of accidental deletion, data corruption, or ransomware.

Schedule Types

Type Description Best For
Calendar-based Runs on selected days of the week at selected hours of the day, with an optional minute offset. Daily or weekly backup windows; business-hour snapshots
Interval-based Runs every N minutes (minimum 3). High-frequency snapshots for critical workloads

Creating a Snapshot Schedule

Navigation: Storage Management → Snapshot Schedules → (toolbar) Create Snapshot Schedule

General Tab

Field Description
Name Unique name for the schedule
Description Optional description
Enabled Toggle to activate or pause the schedule without deleting it
Resource Group Scope the schedule to a resource group (optional; for multi-tenant environments)

Schedule Interval Tab

Calendar-based schedule:

Select one or more days of the week and one or more hours of the day. Snapshots will be taken at each selected hour on each selected day.

  • Offset (minutes) — Optional minute offset past the hour (0–59). Use this to stagger multiple schedules and avoid simultaneous I/O.

Interval-based schedule:

  • Interval (minutes) — How often to take a snapshot. Minimum enforced value: 3 minutes.

CLI — Calendar-based: 

# Every Monday and Friday at 2am and 6pm, 15 minutes past the hour
qs snap-schedule-create \
  --name=daily-snap \
  --days=mon,fri \
  --hours=2am,6pm \
  --offset-minutes=15

CLI — Interval-based: 

# Every 30 minutes
qs snap-schedule-create \
  --name=frequent-snap \
  --schedule-type=interval \
  --interval=30

Select Volumes & Shares Tab

At least one storage volume or network share must be associated with a schedule. Volumes and shares from any system in the storage grid can be selected.

CLI — Associate volumes and shares at creation time: 

qs snap-schedule-create \
  --name=daily-snap \
  --days=mon,tue,wed,thu,fri \
  --hours=2am \
  --volume-list=vol1,vol2 \
  --share-list=share1

CLI — Add or remove associations after creation: 

# Add a volume to an existing schedule
qs snap-schedule-add --schedule=daily-snap --volume-list=vol3

# Add a share to an existing schedule
qs snap-schedule-add --schedule=daily-snap --share-list=share2

# Remove a volume from a schedule
qs snap-schedule-remove --schedule=daily-snap --volume-list=vol3

A single volume or share can be associated with multiple schedules simultaneously — for example, an hourly schedule for short-term retention and a weekly schedule for long-term retention.

Snapshot Settings Tab

Rotating Snapshot Count (max-snaps)

The max-snaps setting controls how many rotating snapshots the schedule maintains. When the limit is reached, the oldest snapshot created by this schedule is automatically deleted before a new one is taken.

Setting Default Range
Max Snapshots 5 1–1000

Recommendation:

  • Daily schedule: 7–14 snapshots (one to two weeks of history)
  • Weekly schedule: 4–8 snapshots (one to two months of history)
  • Hourly schedule: 24–48 snapshots (one to two days of history)

Long-Term Retention Counts

In addition to the rotating window, schedules support long-term retention tiers. Snapshots promoted to a retention tier are not subject to the max-snaps limit and are preserved until their tier count is exceeded.

Parameter Tier Description
rc-hourly Hourly Number of hourly snapshots to retain long-term
rc-dailies Daily Number of daily snapshots to retain long-term
rc-weeklies Weekly Number of weekly snapshots to retain long-term
rc-monthlies Monthly Number of monthly snapshots to retain long-term
rc-quarterlies Quarterly Number of quarterly snapshots to retain long-term

CLI — Create schedule with long-term retention: 

qs snap-schedule-create \
  --name=tiered-snap \
  --days=mon,tue,wed,thu,fri,sat,sun \
  --hours=12am \
  --max-snaps=7 \
  --rc-dailies=30 \
  --rc-weeklies=12 \
  --rc-monthlies=12 \
  --volume-list=vol1

This example keeps 7 rolling daily snapshots plus 30 daily, 12 weekly, and 12 monthly long-term snapshots — approximately 13 months of history.

Managing Schedules

List and Inspect

Navigation: Storage Management → Snapshot Schedules

CLI: 

# List all snapshot schedules
qs snap-schedule-list

# Get details for a specific schedule
qs snap-schedule-get --schedule=daily-snap

# List all volume/share associations for a schedule
qs snap-schedule-assoc-list --schedule=daily-snap

Enable and Disable

Schedules can be paused without being deleted. A disabled schedule will not create new snapshots but its existing snapshots are preserved.

Navigation: Storage Management → Snapshot Schedules → (right-click) → Enable / Disable

CLI: 

qs snap-schedule-enable --schedule=daily-snap
qs snap-schedule-disable --schedule=daily-snap

Modify a Schedule

Navigation: Storage Management → Snapshot Schedules → (right-click) → Modify

CLI: 

# Change to run at 3am instead of 2am, increase retention to 14
qs snap-schedule-modify \
  --schedule=daily-snap \
  --hours=3am \
  --max-snaps=14

Trigger a Schedule Immediately

Run a schedule right now without waiting for the next scheduled time. This takes a snapshot of all associated volumes and shares immediately and counts toward the rotating window.

Navigation: Storage Management → Snapshot Schedules → (right-click) → Trigger Now

CLI: 

qs snap-schedule-trigger --schedule=daily-snap

Delete a Schedule

Deleting a schedule does not automatically delete the snapshots it created. Existing snapshots remain until manually deleted or until another schedule's retention policy removes them.

Navigation: Storage Management → Snapshot Schedules → (right-click) → Delete

CLI: 

qs snap-schedule-delete --schedule=daily-snap

Creating One-off (Immediate) Snapshots

To take an unscheduled snapshot of a specific volume or share at any time:

Navigation: Storage Management → Storage Volumes → (right-click volume) → Create Snapshot

CLI: 

# Snapshot a single volume
qs volume-snapshot --volume=vol1 --name=pre-patch-snap

# Snapshot a network share
qs share-snapshot --share=share1 --name=pre-patch-snap

# Snapshot all volumes in a volume group simultaneously
qs volume-group-snapshot --volume-group=vg1

Snapshot Naming

All schedule-created snapshots use GMT-based names for compatibility with Windows Previous Versions (VSS): 

volname@GMT-2024.06.17-02.15.00

The timestamp is always in UTC. Snapshots appear in the _snaps/ folder over NFS/SMB and in the .zfs/snapshot/ directory (if NFS snapshot browsing is enabled).

Recovering Data from Snapshots

Browse and Copy Files (NFS/SMB)

Snapshots are accessible directly from the client without administrator intervention. Navigate to the _snaps folder at the root of any mounted share or volume: 

# NFS
ls /mnt/data/_snaps/
cd /mnt/data/_snaps/@GMT-2024.06.17-02.15.00/
cp /mnt/data/_snaps/@GMT-2024.06.17-02.15.00/important-file.txt /mnt/data/

# SMB (Windows)
# Right-click the share in Explorer → Properties → Previous Versions

For ZFS-backed pools with snapshot browsing enabled: 

ls /mnt/data/.zfs/snapshot/

Revert a Volume to a Snapshot

Reverting replaces the current volume contents with the snapshot state. This is a destructive operation — all writes after the snapshot point are lost.

Navigation: Storage Management → Storage Volumes → (right-click volume) → Revert to Snapshot → select snapshot

Pass the snapshot name as the --volume argument — the snapshot is identified by its own name, not a --snapshot parameter:

CLI: 

qs volume-snapshot-revert --volume=vol1@GMT-2024.06.17-02.15.00

Clone a Snapshot to a New Volume

To access snapshot data without reverting, clone the snapshot to a new read-write volume. As with revert, pass the snapshot name as --volume:

Navigation: Storage Management → Storage Volumes → (right-click snapshot) → Clone

CLI: 

qs volume-clone --volume=vol1@GMT-2024.06.17-02.15.00 --name=vol1-clone

Troubleshooting

Snapshots Not Being Created

  1. Verify the schedule is enabled: qs snap-schedule-get --schedule=daily-snap
  2. Confirm at least one volume or share is associated: qs snap-schedule-assoc-list --schedule=daily-snap
  3. Check the QuantaStor service log for scheduler errors: journalctl -u quantastor --since "1 hour ago" | grep -i sched
  4. Verify the storage pool has sufficient free space — snapshots cannot be created if the pool is full.

Snapshots Not Being Expired

  1. Confirm max-snaps is set to a value greater than 0 on the schedule.
  2. Check whether long-term retention counts (rc-dailies, etc.) are protecting snapshots from expiration — retained snapshots are not subject to the max-snaps limit.
  3. If a snapshot is pinned or has a dependent clone, it cannot be deleted until the clone is removed.

Storage Pool Filling Up Due to Snapshots

Snapshots consume space proportional to the amount of data changed since the snapshot was taken. If a volume sees heavy write activity, snapshots accumulate space quickly.

  1. Reduce max-snaps to keep fewer snapshots.
  2. Increase the snapshot interval to reduce frequency.
  3. Delete old manual snapshots that are no longer needed.
  4. Monitor per-snapshot space usage in the Storage Volumes panel.

Schedule Ran But No Snapshot Visible

Snapshots created by a schedule are listed under the associated volume or share, not under the schedule itself.

Navigation: Storage Management → Storage Volumes → (expand volume) → Snapshots

CLI (shares): 

qs share-list --include-snapshots=true

For volumes, snapshots appear as child entries in the WUI under the parent volume. There is no CLI filter for volume snapshots — use volume-list and look for entries where Is Snapshot is true.

CLI Quick Reference

Command Short Form Description
snap-schedule-create sch-create Create a new snapshot schedule
snap-schedule-modify sch-modify Modify an existing schedule
snap-schedule-delete sch-delete Delete a schedule (snapshots are preserved)
snap-schedule-enable sch-enable Enable a paused schedule
snap-schedule-disable sch-disable Disable a schedule without deleting it
snap-schedule-trigger sch-trigger Run the schedule immediately
snap-schedule-list sch-list List all snapshot schedules
snap-schedule-get sch-get Get details for a schedule
snap-schedule-add sch-add Associate a volume or share with a schedule
snap-schedule-remove sch-remove Remove a volume or share association
snap-schedule-assoc-list scha-list List all associations for a schedule
volume-snapshot v-snap Create an immediate one-off snapshot of a volume
share-snapshot shr-snap Create an immediate one-off snapshot of a share
volume-snapshot-revert v-snap-revert Revert a volume to a snapshot point-in-time
volume-group-snapshot vg-snap Snapshot all volumes in a volume group simultaneously

See Also

Retrieved from "https://wiki.osnexus.com/index.php?title=Snapshot_Schedules&oldid=27167"