>Hello
>Im trying to access shadow copies under windows XP by rsync.
>Shadow copies may be accessed as a device with the following syntax:
>\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1
>I try it with rsync but the log always states:
>rsync: link_stat
>"/cygdrive/\//GLOBALROOT/Device/HarddiskVo
Hello
Im trying to access shadow copies under windows XP by rsync.
Shadow copies may be accessed as a device with the following syntax:
\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1
I try it with rsync but the log always states:
rsync: link_stat
"/cygdrive/\//GLOBALROOT/Device/HarddiskVolum
On Mon, May 15, 2006 at 01:30:30PM -0500, helices wrote:
> That appears to be the most appropriate first step -- right? Only if
> this faults, then the other options?
Rsync 2.6.4 has some limited support for keep-alive, it it could help
to set a compatible timeout value via the client's --timeout
https://bugzilla.samba.org/show_bug.cgi?id=3778
Summary: rsync triggers ( pre/post xter scripts )
Product: rsync
Version: 2.6.8
Platform: Sparc
OS/Version: Windows XP
Status: NEW
Severity: major
Priority: P3
Wayne =>
* Wayne Davison <[EMAIL PROTECTED]> [2006:05:15:09:50:17-0700] scribed:
> On Mon, May 15, 2006 at 08:02:20AM -0500, helices wrote:
> > rsync error: timeout in data send/receive (code 30) at io.c(181)
>
> This means that either the client invocation or the server config file
> has set
On Mon, May 15, 2006 at 08:02:20AM -0500, helices wrote:
> rsync error: timeout in data send/receive (code 30) at io.c(181)
This means that either the client invocation or the server config file
has set a timeout option. If the server sets a timeout option, it does
not communicate this fact t
We have two (2) servers on a LAN, backup [A] and tjg1 [B]. We want to
PUSH file synchronization from [B] to [A]. We are repeatedly this
error:
rsync error: timeout in data send/receive (code 30) at io.c(181)
Google has not been kind; nor have the archives to this list.
Perhaps, I am ignoran
We have two (2) servers on a LAN, backup [A] and tjg1 [B]. We want to
PUSH file synchronization from [B] to [A]. We are repeatedly this
error:
rsync error: timeout in data send/receive (code 30) at io.c(181)
Google has not been kind; nor have the archives to this list.
Perhaps, I am ignoran
Mike Daws wrote:
> > ssh isn't always an option. E.g. to reach HP's testdrive machines,
> > telnet is the only available option.
> >
> > I've done rsync over telnet, in binary mode and with the terminal set
> > to raw, using Perl and the Perl Net::Telnet module, and it mostly
> > worked but there
