I have several computers backing up to a Samba installation on a NAS. This setup with the standard Ubuntu backup tool (Dejadupe?) has worked fine for several years. Recently the backups fail with this message: Giving up after 5 attempts. Error: Connection timed out.
The destination location for the backup is accessible and has plenty of room.
Looking at the duplicity files, it appears that some files have an unexpected end to the file. The files still have a .tmp extension which I assume indicate that the file was not completely written.
At least two computers writing to the NAS have the same error.
One thing I would like to try is to somehow change the timeout option in duplicity but I have no idea how to do this.
Any help would be appreciated.
Hello! Sorry that Deja Dup is giving you a hassle.
- “Connection timed out” out of nowhere is odd indeed. No obvious connection to a system update or anything?
- I don’t know how to modify the timeout length.
- Are there any issues when copying files to the NAS from the Files app (
nautilus)? - It’s a long shot, but the later versions of Deja Dup tweak how we connect to servers (using a FUSE mount rather than talking directly to GVfs) - you could try the latest release from Flathub and see if things are any better?
Yes, I can save a file from one of the computers that failed with the backup to the backup drive. Also, the backup process copies a considerable amount of data to the destination directory.
Duplicity is the latest version (flatpac) and has a command line switch for a longer timeout. I don’t know if the quick launch icon on my desktop calls duplicity directly. If it does, then modifying the details of the quick launch icon might work … but I do not know how to modify the icon.
I will try and see if Deja dup is the latest version.
Updating all flatpak packages did not help. I also upgraded my Ubuntu installation but no joy.
I think I am looking at this the wrong way. I did a backup while watching the files fly by. As it turns out, several times during the backup, everything stopped. I now suspect that there is something going on with either the system that is the backup destination drive or the network itself. This last backup was actually successful.
I will try and figure out how to increase the standard time-out on duplicity. I will also see about what can be done with the network and the destination computer (a raspberry pi 4)
This topic was automatically closed 45 days after the last reply. New replies are no longer allowed.