Michael Stowe wrote at about 14:48:16 -0500 on Thursday, August 20, 2009:
 > Sort of -- VSS/cygwin has a weird catch-22 where the shadow copy has to
 > exist before cygwin is launched or cygwin can't see the volume at all.  In
 > other words, ssh can start a shadow copy, but then any launched rsync
 > can't see it, which makes it pointless.
 > 
 > The first thing I tried was using remote ssh to manage the shadow volume
 > process, and within that context, rsync couldn't see the shadow volumes.
 > 
 > Now that you mention it, though, I can't think of a good reason why my
 > scripts couldn't be triggered by remote ssh, since the whole point of them
 > is to launch rsync within the context of a shadow volume.
 > 
 > That being said, I can currently set up a machine for backup by just
 > dragging a directory over, remote ssh would require slightly more setup.
 > 

As documented on an earlier thread, I use ssh to launch scripts to
setup/stop VSS and start/stop rsyncd. I do have to do a bunch of
kludges (including recursively calling the script via 'at') to get the
right process permissions and to make sure that the VSS stays around
for the length of the backup and then unwinds appropriately. The
script I wrote is rock-solid and is quite configurable. Check it out
in the archives or email me if you are interested in it.

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/