You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To stop the amount of backup storage growing indefinitely an auto-prune feature would be nice like the "remove-all-but-n-full" parameter for Duplicity.
The text was updated successfully, but these errors were encountered:
I wonder if auto-expiration of blocks on the back-end could meet this need? I'm thinking specifically of S3's bucket-configurable object expiration. Does zfsbackup-go store snapshots as single objects/keys on the backend, or is it split into multiple objects (which could each expire at different times)?
To stop the amount of backup storage growing indefinitely an auto-prune feature would be nice like the "remove-all-but-n-full" parameter for Duplicity.
The text was updated successfully, but these errors were encountered: