Skip to main content
Storage & files

Volume Shadow Copy Age

Detect when a Windows device stops creating new shadow copies.

The Volume Shadow Copy Age check watches the shadow copies (VSS snapshots) on a Windows device. For every volume that has shadow copies it takes the newest one, works out how old it is and alerts once that age reaches or exceeds your thresholds — so you notice when snapshot creation has quietly stopped, for example because a backup job or a scheduled task no longer runs. The check runs on the device through the octoja agent and reads the snapshot list locally — nothing is installed and no credentials are needed. It runs every 60 minutes; the interval belongs to the check itself and cannot be changed per device. The Check Library shows this as Every 60 min in the Interval column.

Steps

  1. Go to Devices and open the Windows device.
  2. Click the Checks tab → Add Check → Volume Shadow Copy Age.
  3. Adjust the thresholds if needed.
  4. Click Add Check.

Settings

Both thresholds compare against the age of the newest shadow copy per volume.

FieldTypeRequiredDefaultDescription
Warning age (hours)NumberNo26Warn when the newest shadow copy reaches or exceeds this age.
Error age (hours)NumberNo50Critical when the newest shadow copy reaches or exceeds this age.
Warn when no shadow copies are foundBooleanNoOnDisable to report OK when a device has no shadow copies. Age thresholds and query errors are unaffected.
  • The defaults — warning at 26 hours, critical at 50 hours — fit a daily snapshot schedule: one missed run raises the warning, a second missed run makes it critical.
  • If Warning age (hours) is set higher than Error age (hours), the check swaps the two values so the smaller age always warns first.

Results

Each volume with at least one shadow copy gets its own result; the check result is the worst of those volumes. Age is rounded to one decimal hour before comparison.

Volumes without shadow copies do not appear in the results. The check can therefore report OK even when an expected volume has no shadow copy. Warn when no shadow copies are found applies only when none are found anywhere on the device. After setup and storage changes, check that every expected volume is listed and verify the job responsible for creating its shadow copies.

ResultWhen it happens
OKOn every listed volume the newest shadow copy is younger than Warning age (hours).
WarningOn at least one listed volume the newest shadow copy reaches or exceeds Warning age (hours) but is still below Error age (hours).
CriticalOn at least one listed volume the newest shadow copy reaches or exceeds Error age (hours).
ErrorThe check itself stopped unexpectedly, so the result lists no volumes. Run it again with the play button beside the check on the device's Checks tab; if it keeps ending this way, look at the agent logs on the device.

The result shows one card per volume:

  • The volume name with an OK, Warning or Critical badge.
  • Newest — the age of the newest shadow copy, shown in hours (4.2h) and, from 48 hours, in days (2.1d).
  • The number of snapshots on the volume. It is informational: only the newest shadow copy per volume is compared against the thresholds.

When the check can't run

These outcomes raise a warning by default instead of a volume status. For No shadow copies found, you can turn off the warning with the Warn when no shadow copies are found option.

MessageWhat to do
No shadow copies foundThere are no shadow copies on any volume of the device. If you expect snapshots here, check the job that should create them. Otherwise, disable Warn when no shadow copies are found so the check reports OK.
Only runs on WindowsThe check is assigned to a device that is not running Windows. Assign it to Windows devices only.
Shadow-copy query failedWindows could not list the shadow copies; the message shows the error the system reported. If it repeats, check the Volume Shadow Copy service on the device.

Platform support

Shadow copies are a Windows feature, so octoja publishes this check for Windows only. The Check Library lists it with a Windows badge in the Platforms column, and when you add a check on a device the picker opens filtered to that device's operating system — so the check is not offered on a Linux or macOS device. If it reaches one anyway, through a config package whose rule matches non-Windows devices for example, the check reports the warning Only runs on Windows.

PlatformSupported
Windows (x64 and ARM64)Yes, client and server editions
LinuxNo
macOSNo