Bug #59582
closedsnap-schedule: allow retention spec to specify max number of snaps to retain
0%
Description
Along with daily, weekly, monthly and yearly snaps, users also need a way to mention the max number of snaps they need to retain if they feel that MAX_SNAPS_PER_PATH (50) is insufficient for their purpose.
eg. the new snap-schedule with the retention spec could be: /PATH 1d1m 75n
where a max of 75 snaps from the 1d1m snap-schedule will be retained. If number of snaps ('n') are not specified as the retention spec then the default of MAX_SNAPS_PER_PATH (50) should be applicable.
NOTE: the max number of snaps possible are also a function of the system-wide config named mds_max_snaps_per_dir, which currently defaults to 100
So, if the number of snaps for a path/dir that need to be created exceeds 100, then a user would first need to tweak the value for mds_max_snaps_per_dir before updating the snap-schedule retention spec beyond 100.
NOTE: Since mds_max_snaps_per_dir is a run-time system-wide spec, any change to that config will immediately affect existing snap-schedule retention specs.
Updated by Venky Shankar about 1 year ago
- Category set to Administration/Usability
- Assignee set to Milind Changire
- Target version set to v19.0.0
- Backport set to reef,quincy,pacific
- Component(FS) mgr/snap_schedule added
Updated by Venky Shankar 10 months ago
- Status changed from New to Pending Backport
Updated by Backport Bot 10 months ago
- Copied to Backport #61989: pacific: snap-schedule: allow retention spec to specify max number of snaps to retain added
Updated by Backport Bot 10 months ago
- Copied to Backport #61990: reef: snap-schedule: allow retention spec to specify max number of snaps to retain added
Updated by Backport Bot 10 months ago
- Copied to Backport #61991: quincy: snap-schedule: allow retention spec to specify max number of snaps to retain added
Updated by Milind Changire about 2 months ago
- Status changed from Pending Backport to Resolved