The current backup function adds a new dataset, every time it creates a backup.
That’s not really a problem because the zip file is below 2 MB in my case, I’d still prefer it if we’d have the option to limit the number of files it creates.
I thought about it, but ultimately it’s safer to only add files and not delete. I don’t want a situation where a new backup fails and we delete an old one. Hopefully the cloud services add some lifecycle management to handle this on their side.
Yeah, I can imagine that this could cause trouble. The potential issues could be limited by something slightly more sophisticated though.
Example:
Keep backups for the first day of the past three months, plus the last two Mondays and the past three days.
Would be a nice and rather safe compromise imho. And could be a simple opt-in, everyone else could keep their daily backups.
It’s a good idea, but I don’t have plans to do this currently. I agree we could make it opt in and put some good rules around it, but there is still a risk with deleting files that I’d rather not take on.
1 Like
I have asked about this and had the same “concern”, like all backups options to have keep the last 5 backups or something like that.
But i also think this over again ana 2MB of a file on a cloud is really nothing, make a reminder in your phone once a month to either archive them or delete the old ones.
It really is a moot point for such a small file size.
If you have for example google drive in your pc installed you can create a schedule task in windows with a batch files to delete backups older than 20 days for example.