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/HarddiskVolumeShadowCopy1/ada" failed: No such file or directory (2) rsync error: some files could not be transferred (code 23) at /home/lapo/packaging/tmp/rsync-2.6.3/main.c(702) Is rsync not capale to access devices with this syntax? Or do I make an other error? Thanks for your help MIchael -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Dr. Michael T. Dirksen Brucknerstrasse 39 64347 Griesheim Tel: 0049 (0) 6155 - 848781 Fax: 0049 (0) 1212 - 5192 - 81276 mail: dirksen@wasserleben.com web: http://www.wasserleben.com -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -------------- next part -------------- HTML attachment scrubbed and removed
>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/HarddiskVolumeShadowCopy1/ada" failed:No >such file or directory (2)>rsync error: some files could not be transferred (code 23) at >/home/lapo/packaging/tmp/rsync-2.6.3/main.c(702)>Is rsync not capale to access devices with this syntax? >Or do I make an other error? >Thanks for your help >MichaelApparently not. I've done quite a bit of testing with this. It seems as though the windows xp copy command is the only command that can recognize the temporary volume shadow device. It seems as though xcopy doesn't even recognize the device. What I've done in the past is created a script that creates the volume shadow copy, copies the files to a temp directory, rsyncs them from there, then deletes the files. The rsync algorithm still seems to work fine with only the changes. It would be awesome if rsync could recognize the volume shadow copy device, but I have no idea what that would entail. Also, with Windows 2003 Server, you can create volume shadow copies that are linked to a drive letter that rsync does recognize. Max
On Tue, May 16, 2006 at 01:00:28AM +0200, dirksen@wasserleben.com wrote:> 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\HarddiskVolumeShadowCopy1I think you should map that location to a drive letter, such as X: (do this in your MS Windows setup), and then try accessing it via the normal /cygdrive/x/... prefix using rsync. ..wayne..
> On Tue, May 16, 2006 at 01:00:28AM +0200, dirksen@wasserleben.comwrote:> > 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 think you should map that location to a drive letter, such as X: (do > this in your MS Windows setup), and then try accessing it via thenormal> /cygdrive/x/... prefix using rsync. > > ..wayne..I tried the mapping approach. It did not work as I assumed. The error received was "The network path was not found". Then 'net use' command evidently does not recognize the volume shadow device. So far I've found that only the 'copy' command can recognize it. Max
> Is there any way to access the shadow device by the copy command andto> pipe the files to rsync? > that means to "filter" the files by rsync (to copy only the necessary > files)? > MichaelSorry for the late response. I don't know if you can pipe directly to rsync from the xp copy command, as I don't think rsync can receive its file list from stdin. What I've done is created a script with two file lists, standard rsync list and an open file list. My script runs vshadow.exe creating the volume shadow device, reads the files from 'open file list', then copies them to a temp location. Then rsync runs against its file list which includes the temp location. Then the script deletes everything in the temp directory. I add to the 'open file list', files that I know most likely will be open, like .pst files. I've tested restoring .pst files in which they were open, and only the changes calculated by rsync were transferred over the course of several backups. They restored fine. I had the thought of piping stderr from my rsync script to a separate file, and then copying all files that were 'in use' according to rsync via vshadow and then running rsync for a second time. If I recall though, on windows, rsync doesn't specify which files are 'in use' and rather uses a generic error for any file it cannot copy. I guess it still would not hurt to try getting them through vshadow. Max