Re: [Duplicity-talk] Resume rsync to rsync.net

[Manuel Morales]

Hi Tyler

 

Actually I was testing and I read a little the man pages.

I changed the volume size with the command line, and increased the verbosity:

duplicity --volsize 50 --verbosity 8

 

It works pretty neat actually, I think duplicity tries to upload “per-volume”,,, so a 500MB backup folder will yield 10 volumes on the destination.

Duplicity will be able to resume, as long as at least 1 volume was already transferred to the destination.

 

I tested a few times, and it resumes nicely.

The reason I didn’t see it before, is because the default volsize is 200MB, (actually the volume on the destination will be a little more than whatever volsize is specified),,

So, everytime I tested, I cut the transfer as soon as 200MB were on the destination, so in reality, the first volume never got completely transferred.

That’s why it was starting from scratch every time, because everytime duplicity tried to resume, it found that volume1 was not completed.

 

It is easier to see if you force the volsize to a smaller size, and increasing the verbosity.

 

My thanks to everybody that writes and maintain duplicity.

 

Dotty

 

 

From: Tyler Ham <address@hidden>
Date: Saturday, April 22, 2017 at 1:18 AM
To: Discussion about duplicity backup <address@hidden>
Cc: Manuel Morales <address@hidden>
Subject: Re: [Duplicity-talk] Resume rsync to rsync.net

 

Hi,

 

I think what you are describing is some expected behavior with rsync by default. It waits to write to the destination file until it has assembled all of that file's content in a temporary file on the destination server. So if you Ctrl-C, the actual destination file hasn't been touched yet and rsync will have to start over on that file next time.

 

The rsync command line has an '--inplace' option that tells it to write directly to the destination file instead of using a temporary file, in which case it should resume the way you want it to after a Ctrl+C or a network outage.

 

You might try duplicity with --rsync-options="--inplace" and see if that works for your use case.

 

Tyler

 

 

On Fri, Apr 21, 2017 at 11:58 PM, Manuel Morales via Duplicity-talk <address@hidden> wrote:

Hi guys

Im using the following command to sync to rsync.net

 

duplicity /mnt/data/E4310-2/170403-2330/ rsync://address@hidden:

 

That folder is pretty big,, my uploads speed are about 10 Mbits (limited on my side).

I was testing what happen if the Internet goes down in the middle of the transfer, so I waited until there were 200 MB on the destination and I did Ctrl+C .

The file on the destination disappeared, and now when I try the same command again I get:

 

=======================

Local and Remote metadata are synchronized, no sync needed.

Last full backup left a partial set, restarting.

Last full backup date: Sat Apr 22 00:48:31 2017

GnuPG passphrase:

Retype passphrase to confirm:

RESTART: The first volume failed to upload before termination.

         Restart is impossible...starting backup from beginning.

=======================

 

 

 

Does duplicity have capabilities for resume a transfer that was cut in the middle?

Any advice? (My internet is not that reliable, and the backup set will be pretty big, specially the first time)

 

 

Thanks

Dotty

 

 

_______________________________________________
Duplicity-talk mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/duplicity-talk