Currently setting the schedule to full-gc only cleans up the local storage, and ignores remotes and any retention policies set there. This is a problem because that means the only way to cleanup remote snapshots is either with an admin manually running the remote-prune command, or and external tool (be it a mod, or rcon + crontab).
Ideally, a new scheduling option (for example full-gc-remote) would exist that would make the schedule run a full backup, local prune and gc followed by remote prune.
Alternatively a schedule-remote-prune configuration option could be provided, which if enabled, would cause the standard full-gc action to perform the remote prune when triggered.
Currently setting the schedule to full-gc only cleans up the local storage, and ignores remotes and any retention policies set there. This is a problem because that means the only way to cleanup remote snapshots is either with an admin manually running the remote-prune command, or and external tool (be it a mod, or rcon + crontab).
Ideally, a new scheduling option (for example
full-gc-remote) would exist that would make the schedule run a full backup, local prune and gc followed by remote prune.Alternatively a
schedule-remote-pruneconfiguration option could be provided, which if enabled, would cause the standardfull-gcaction to perform the remote prune when triggered.