Fingerprint and skip
Scheduler and shutdown backup can skip backups when nothing changed.
Where it is used
- scheduler.jobs[].skipIfNoChanges (default: true)
- shutdownBackup.skipIfNoChanges (default: true)
How it works
-
ConfigGuard plans the backup:
- resolves the target into files
- applies mode and filters
-
A fingerprint is computed from the plan metadata
-
The previous state for the job id is loaded
-
If fingerprint is unchanged and skip is enabled:
- backup is skipped
- lastRun timestamp is updated
What counts as a change
The fingerprint depends on planned file metadata.
In practice this reflects: - changes in selected files - changes in file sizes or hashes
This prevents duplicate backups on frequent restarts or scheduler ticks.
Notes
- Scheduler does not catch up missed runs
-
Shutdown backup uses a reserved state id:
-
shutdown