I have a Data Protection job that has a “Snapshot lifetime” defined:
When it ran on schedule it created a snapshot with:
Retention: Will not be destroyed automatically
My other periodic snapshot jobs are working fine:
Did you change anything about the task after you created it?
There’s a discrepancy between the task’s scheduled time of 01:00 and the snapshot’s creation of 16:00.
Zettarepl is likely parsing the name and skipping it because “16-00” does not match the task’s configuration of the expected “01-00”.
I did change the time… Does this mean that after a snapshot task is scheduled it can’t be changed?
It can be changed, but any existing snapshots will be decoupled from the task.
Zettarepl is name-based. It parses snapshot names and compares them against the schema in the task. It does not use a separate database or list to track snapshots and expirations.
So how does it work? If I change the schedule time the last snapshot is no longer auto deleted. Does the next snapshot that runs become the base snapshot for subsequent incremental snapshots? Can I then delete the first one that is not going to be deleted automatically, ie. the one that becomes: Retention: Will not be destroyed automatically
The Replication Task is likely to complain that the destination is missing a base snapshot for an incremental replication.
This is the simplest approach.
According to zettarepl, your Periodic Snapshot Task is creating auto-YYYY-MM-DD_01-00 snapshots.
The parts in bold are not variables. They must perfectly match.
This is why any value for year (2026, 2027, 2028) or month (07, 08, 09) or day (24, 25, 26) is fine. The value for hour and minute must be “01-00” and the value at the start of the name must be “auto”.
This gets skipped: auto-2027-02-15_12-00
This gets skipped: manual-2028-06-01_01-00
This gets skipped: auto-2029-12-31_18-00
This is coupled to the existing task: auto-2040-03-01_01-00
1 Like
Great - thanks!