Eberhard,
I looked in to the -b switch and it's a good idea but I have been unable to
find a way to use it such that a resume can continue where it left off,
without re-checking what has already been completed, *and* continue to use
the same ultimate destination file as a source of diffing.
On 15.07.2011 13:10, Donald Pearson wrote:
Matthias,
A vpn tunnel is an interesting idea. Do you know how long you're able to
keep rsync in limbo before it will give up?
I haven't really tried. But it was about 15 Minutes the one time it
didn't reconnect in time.
The issue I think is
Hi,
On Fri, 15 Jul 2011, Donald Pearson wrote:
I looked in to the -b switch and it's a good idea but I have been unable to
find a way to use it such that a resume can continue where it left off,
without re-checking what has already been completed, *and* continue to use
the same ultimate
On 7/15/2011 2:42 PM, Matthias Schniedermeyer wrote:
On 15.07.2011 13:10, Donald Pearson wrote:
Matthias,
A vpn tunnel is an interesting idea. Do you know how long you're able to
keep rsync in limbo before it will give up?
I haven't really tried. But it was about 15 Minutes the one time it
Wow can't tell you how many times I've read over the man page but Batch Mode
never jumped out at me before.
Batch Mode could very well provide a solution, I'm going to give it a run.
Also, I think I found the knob in Ubuntu that's creating the error in rsync.
It's
On 11.07.2011 16:01, Donald Pearson wrote:
I am looking to do state-full resume of rsync transfers.
My network environment is is an unreliable and slow satellite
infrastructure, and the files I need to send are approaching 10 gigs in
size. In this network environment often times links
@Eberhard: I understand what you're trying to say, but in this environment
the reality is rsync reaches and impasse where it is unable to get beyond
work that has already been completed before link failure cuts it off again.
@Leen: A combination of --append with --partial is what I tried,
Hi,
On Tue, 12 Jul 2011, Donald Pearson wrote:
[very selective cited, just to lighten one aspect]
@Eberhard: I understand what you're trying to say, but in this environment
the reality is rsync reaches and impasse where it is unable to get beyond
work that has already been completed before
On 7/12/2011 11:10 AM, Donald Pearson wrote:
@Eberhard: I understand what you're trying to say, but in this
environment the reality is rsync reaches and impasse where it is unable
to get beyond work that has already been completed before link failure
cuts it off again.
@Leen: A combination of
On 12.07.2011 11:10, Donald Pearson wrote:
...
A 'trick' i personally use for an unreliable connection is an
OpenSSH-Tunnel.
Altough any VPN-solution should to the trick.
That way the connection between the two rsync-halvs isn't directly tied
to the internet-connection.
In my case that
I am looking to do state-full resume of rsync transfers.
My network environment is is an unreliable and slow satellite
infrastructure, and the files I need to send are approaching 10 gigs in
size. In this network environment often times links cannot be maintained
for more than a few minutes at a
Hi,
On Mon, 11 Jul 2011, Donald Pearson wrote:
I am looking to do state-full resume of rsync transfers.
My network environment is is an unreliable and slow satellite
infrastructure, and the files I need to send are approaching 10 gigs in
size. In this network environment often times links
Hi once more,
On Mon, 11 Jul 2011, Eberhard Moenkeberg wrote:
On Mon, 11 Jul 2011, Donald Pearson wrote:
I am looking to do state-full resume of rsync transfers.
My network environment is is an unreliable and slow satellite
infrastructure, and the files I need to send are approaching 10
On 07/11/2011 10:57 PM, Eberhard Moenkeberg wrote:
Hi once more,
On Mon, 11 Jul 2011, Eberhard Moenkeberg wrote:
On Mon, 11 Jul 2011, Donald Pearson wrote:
I am looking to do state-full resume of rsync transfers.
My network environment is is an unreliable and slow satellite
14 matches
Mail list logo
