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.

> Michael Stowe wrote:
>> It's faster, though I didn't do formal benchmarks.  My own reason for
using it is to handle open files, documented below:
>> http://www.goodjobsucking.com/?p=62
>
> Is there some reason that wouldn't work as well using ssh for remote
execution instead of winexe?  Since it runs rsync in daemon mode it
shouldn't affect xfer speed anyway.
>
> --
>    Les Mikesell
>     lesmikesell AT gmail DOT com




------------------------------------------------------------------------------
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/