我正在尝试使用 Duplicity 将大型文件系统(~800 GB)从 Ubuntu 16.04 备份到 Amazon S3。看起来它备份了大部分文件系统,但一直卡在最后。
我现在已经多次运行此命令,但它一直在同一个地方失败/中止(备份大约 8 小时):
$ duplicity --no-encryption --s3-use-ia --archive-dir /var/abc/tmp --tempdir /var/abc/tmp --exclude /var/abc/tmp /var/abc s3://s3-us-west-2.amazonaws.com/mybucket
Local and Remote metadata are synchronized, no sync needed.
Warning, found incomplete backup sets, probably left from aborted session
Last full backup left a partial set, restarting.
Last full backup date: Tue Jul 25 11:13:45 2017
RESTART: Volumes 32085 to 32085 failed to upload before termination.
Restarting backup at volume 32085.
Restarting after volume 32084, file backups/resourcespace.20170730.sql.gz, block 399
Attempt 1 failed. error: [Errno 104] Connection reset by peer
Attempt 2 failed. error: [Errno 104] Connection reset by peer
Attempt 3 failed. error: [Errno 104] Connection reset by peer
Attempt 4 failed. error: [Errno 104] Connection reset by peer
Giving up after 5 attempts. error: [Errno 104] Connection reset by peer
在我第一次尝试之后,我尝试将 duplicity 升级到最新的 PPA,现在正在运行 0.7.13.1。再试一次——同样的失败。
接下来,我将 boto 从 2.38.0 升级到 2.48.0(通过 PIP),但仍然看到同样的故障。
我发现一些较早的帖子表明这曾经是由于亚马逊方面的某种 5GB 限制而发生的,但是这些帖子还声称它应该在 Duplicity 的 0.7 系列(我正在运行)中修复。
任何有关如何进行进一步故障排除的建议将不胜感激,谢谢!