On 20/03/16 23:44, Les Mikesell wrote:
>>> If the data is split into subdirectories, you might try adding one at
>>> >> a time and repeating the runs as they complete.
>> >
>> > Would you do this by adding to $Conf{BackupFilesOnly} after each
>> > successful run or by gradually extending $Conf{Rsyn
On Sun, Mar 20, 2016 at 4:08 PM, David Raison wrote:
> >
>> Some more guesses: anti-virus software slowing down access, something
>> wrong with the network connection like a full/half duplex mismatch at
>> a switch port, or not enough RAM to hold the directory tree loaded by
>> rsync forcing disk
Hi,
Thanks for the additional guidance.
On 20/03/16 17:56, Les Mikesell wrote:
>> Unfortunately we have still not managed to solve this issue or to even
>> > fully understand it. We have determined that indeed the Windows client
>> > in this example is sending a RST after a random duration, but w
On 03/20/2016 12:56 PM, Les Mikesell wrote:
> On Sun, Mar 20, 2016 at 8:50 AM, David Raison wrote:
>
>> Unfortunately we have still not managed to solve this issue or to even
>> fully understand it. We have determined that indeed the Windows client
>> in this example is sending a RST after a rando
On Sun, Mar 20, 2016 at 8:50 AM, David Raison wrote:
> Unfortunately we have still not managed to solve this issue or to even
> fully understand it. We have determined that indeed the Windows client
> in this example is sending a RST after a random duration, but we we're
> not quite certain how t
HI
I apologize for re-opening an old thread.
Unfortunately we have still not managed to solve this issue or to even
fully understand it. We have determined that indeed the Windows client
in this example is sending a RST after a random duration, but we we're
not quite certain how to get to the sou
Timothy J Massey/OBSCorp wrote on 12/08/2015 01:46:31 PM:
> 2) I looked for a github site for this software and couldn't find
> one, including searching for various permutations of "backuppc
> github". I probably don't need it with the updated items linked
> above, but would you mind sharing i
Michael Stowe wrote on 12/04/2015 06:17:01
PM:
> I'm *pretty* sure both these things are fixed -- I took a quick look at
> the code on github and it looks like it'll handle 7 drives in the
> scripts and at least it thinks it detects 2012 (I'm pretty sure I tested
> this, but I could be easil
On 07/12/15 14:17, David Raison wrote:
>> A 'parallel' ssh
>> would not necessarily do the same thing where session timeouts are
>> involved. Might be worth snooping with tcpdump/wireshark at both ends
>> to see if they both end up waiting or if something has sent a reset.
>
> I'll see what I can
Good day,
On 05/12/15 21:11, Les Mikesell wrote:
>> Well I did have ServerAliveInterval set. And as I mentioned, a parallel
>> > ssh session was still up, even when backuppc/rsync reported a timeout/EOF:
> Yes, that is the problem you really need to solve. Why is your
> connection breaking befor
On Sat, Dec 5, 2015 at 10:37 AM, David Raison wrote:
>
> Well I did have ServerAliveInterval set. And as I mentioned, a parallel
> ssh session was still up, even when backuppc/rsync reported a timeout/EOF:
Yes, that is the problem you really need to solve. Why is your
connection breaking before
On 05/12/15 16:59, Les Mikesell wrote:
>> Well, as I mentioned, rsyncd didn't work either. That's the reason I
>> switched to ssh+rsync in the first place.
>>
>> I can re-run it using rsync and give you that info too.
> Your situation sounds like what can happen if your vpn or a NAT
> gateway or
On Sat, Dec 5, 2015 at 9:28 AM, David Raison wrote:
>
>
> On 04/12/15 14:51, Carl Wilhelm Soderstrom wrote:
>> Don't try to do rsync+ssh on Windows, just use rsyncd. Maybe someone else
>> has gotten rsync+ssh to work on Windows but AFAIK the conventional wisdom is
>> that it doesn't work. (Someone
On 04/12/15 14:51, Carl Wilhelm Soderstrom wrote:
> Don't try to do rsync+ssh on Windows, just use rsyncd. Maybe someone else
> has gotten rsync+ssh to work on Windows but AFAIK the conventional wisdom is
> that it doesn't work. (Someone probably knows why, but that someone is not
> me).
Well, a
On 2015-12-04 15:39, Timothy J Massey wrote:
> Michael Stowe wrote on 12/04/2015
> 04:07:34 PM:
>
>> I do use rsync, and winexe to handle shadow copies so I don't have
> to
>> worry about open files and such. And I put together an installer
>> package with all the pieces.
>
> Funny you should m
On 2015-12-04 15:39, Timothy J Massey wrote:
> Michael Stowe wrote on 12/04/2015
> 04:07:34 PM:
>
>> I do use rsync, and winexe to handle shadow copies so I don't have
> to
>> worry about open files and such. And I put together an installer
>> package with all the pieces.
>
> Funny you should m
Here's mine:
If I recall, just add additional lines to
backuppc.cmd/vrsync.cmd/rsyncd.conf for additional drives. I'm not 100%
sure about this, but I'd imagine it's something like what I have below.
Mine is edited for in-place rsync restores (at your own risk!), but you get
the point.
Also, I'm
Michael Stowe wrote on 12/04/2015 04:07:34
PM:
> I do use rsync, and winexe to handle shadow copies so I don't have to
> worry about open files and such. And I put together an installer
> package with all the pieces.
Funny you should mention that...
I really like Michael's installer package
On 2015-12-04 07:51, Carl Wilhelm Soderstrom wrote:
> On 12/04 11:37 , David Raison wrote:
>> The set-up is a Linux server that is supposed to back up the contents
>> of
>> a Windows 7 client via rsync over ssh.
>
> Don't try to do rsync+ssh on Windows, just use rsyncd. Maybe someone
> else
> ha
On 12/04 11:37 , David Raison wrote:
> The set-up is a Linux server that is supposed to back up the contents of
> a Windows 7 client via rsync over ssh.
Don't try to do rsync+ssh on Windows, just use rsyncd. Maybe someone else
has gotten rsync+ssh to work on Windows but AFAIK the conventional wisd
Good day,
I would like to request you assistance, since I'm trying to understand
the behavior of one of our backuppc instances and, if ever possible,
find a way to solve it.
The set-up is a Linux server that is supposed to back up the contents of
a Windows 7 client via rsync over ssh. Now, we use
21 matches
Mail list logo