Scheduled offsite backup aborts a little time later, but local and offsite manual backup work fine

Support
#1

Hi there,

I have Duplicacy setup on my unraid system after following the ibracorp video and works well for backing up to an external drive and to google drive. Bizarrely the scheduled backup fails, yet if I backup to google drive or to my local drive manually, then the backup works fine. I have no idea why a scheduled backup fails but manual offsite and local backup works fine.

For local and manual backup, I see Warn_list skipped non-regular file for the docker folder. but backs up everything else fine and says completed like a normal backup.

However, for the scheduled offsite backup which backups the exact same stuff to exact the same location. it just says aborted in yellow text. I have no idea why. This is the latest log file to have been produced.

Any solutions, please? Should I just whitelist the docker folder or quite what as I want to back that so I don’t have to redownload all my docker containers to unraid? I could redownload, as AppData is more important.

thoughts?

#2

This can be caused by out-of-memory. Try to reduce the number of files to be backed up by excluding some files/directories. Or break the backup job into several smaller ones.

#3

ok, I will have a look. there’s no way I could suffer out of memory as have 128gb of ram. I have got the -threads 4 set in the command options as that was what the ibracorp video showed Duplicacy: Cloud Backups Done Right! Should You Dump Duplicati? - YouTube. I wonder if there’s a need to change that? Im running an offsite backup and it’s still going fine. Its not easy backing up when your internet is like 5mbps up.

If I change to smaller files to be backed then what happens to the folder structure when I browse to recover files? I don’t want duplicate folders in the root directory or anything like that?

#4

Check /logs/duplicacy_web.log in the docker console. It should have more information on why the CLI process was killed.

#5

Ok, I have had a look and this is the web log.