How to limit disk space for Seedvault on WebDAV?

Using /e/OS Applications
,
1

I successfully set up Seedvault backups with the Murena cloud, then migrated to my own Nextcloud.

It seems that the app creates snapshots, which means that the size might grow until the server is full (not sure if the app does incremental backups or starts from zero for each snapshot).

Is there any default limit or any setting where I can prevent this from happening? Or do I have to use another script to delete old snapshots on the server?

2

I had a similar problem once. Your link does include

at the end, delete old snapshots based on retention rules,

So I guess those rules might be set up on initial creation, maybe they can be adjusted in service ?? I had the problem once and started a fresh run. No noticed problem since but I forget the point of setting the rules.

Edit. I do not use the backup of files, marked experimental.

3

I haven’t noticed anything. An option like that would be very helpful.

4

It seems that the app creates snapshots, which means that the size might grow until the server is full (not sure if the app does incremental backups or starts from zero for each snapshot).

  • it’s incremental, similar to borgbackup / restic, the storage design.md has the explanation.
  • snapshots are limited to 3 daily, 2 weekly. As you said, this is fixed in code and not a user config
  • beware with nextcloud nginx+php-fpm setups (vs apache), see 0 byte files and chunked transfers, a long workaround is imo scheduling a sync of the Seedvault backupdir with RoundSync instead
1 Like
5

Thanks, that makes it clearer.

Line 102 in the code suggests that 3 snapshots is a lower limit. With incremental snapshots that shouldn’t be an issue though.

Thanks also for the warning. I will check my server setup. Possible that nginx is running in proxy mode, but I think that apache is involved somehow.

1 Like
6

assembled some issues to track for activity. Size can balloon pretty quickly depending on what is backed up

I myself do include a Signals backup target directory. It’s one multi-gigabyte blob that isn’t friendly to incremental backup. Though there was a chunked PR in 2022 that was then acknowledged (but not merged) and I see “local archive export” from 2024 that feels to be still behind a feature flag not yet enabled.

1 Like