I’ve been building my home OMV6-based NAS and have set up 4 different B2 buckets and using Duplicacy in Docker. 3 of the 4 have completed their initial uploads without any issues but the 4th and largest for my music media doesn’t.
The ~540GB backup should be taking about 35 hours, but after ~21 hours it stops making progress, seemingly with a crash of duplicacy. I’m using saspus/duplicacy-web:mini (1.6.3).
I’ve tried purging the container, cache, bucket and restarting the backup several times to no avail. Every time it reaches approx 325-326GB in size the web ui stops updating status. The Web log continues to show /get_backup_status entries but I’m not showing that anything is updating. The backup log ends with a usual entry and nothing unusual.
At the point it stops:
If I catch soon after it happens, I’m seeing in my dashboard that iowait consumes a whole core’s worth of time. At that point I can stop the docker container, but on a few occasions I’ve caught it a bit later, the docker container has crashed and I can’t stop or kill it. Worse, I’ve seen in my logs where the entire system locks up and reboots. I’ve set the duplicacy container to not restart automatically so when I come back I’ll see my system had rebooted. If I try restarting the backup, it will finish initial indexing and then crash again, seemingly when it would normally start uploading again.
I’ve tried adding the -debug switch to see if there’s anything amiss, but not seeing anything unusual.
Thanks in advance for any assistance, tips, or recommendations!