[Box Backup-dev] Hello all - win32 client

[Stuart Sanders]

> -----Original Message-----
> The problem without shadow copy and trying to backup exchange (or
> similar - point 3 shadow copy) is you have to back an=20
> intermediary file
> using ntbackup - or just pulling out the database with exchange
> shutdown, but the problem with this is the id of the file changes so I
> believe box treats it as a new file so doesn't even try to diff??

Hi, I'm newish to the list, and getting BB to work with VSS was one of the =
things that interested me.  I didn't plan on attempting it immediately sinc=
e the first plan was to familiarise myself with the project and some core c=
ode areas, and perhaps to a more important extent, refamiliarisation to C++=
 which I haven't looked at for far too many years.

In anycase, the reason for this email is that I've been exploring backup so=
lutions for a while, and one of the things I ran across a while ago was a c=
omment on how to get rsync working with VSS.  This isn't an ideal solution,=
 nor would I consider it a long term solution, but it might meet some peopl=
es needs *right now*.

http://www.itefix.no/phpws/index.php?module=3Dfaq&FAQ_op=3Dview&FAQ_id=3D81

Stuart

----------------------------------------------------
Extract:
----------------------------------------------------

Can cwrsync copy files in use ?

A: =09NB! The recipe below applies to Windows 2003 Server only.

I recently had the issue of running rsync to backup up files that are "in u=
se". A good example was backing up documents and settings and the ntuser.da=
t file would always fail.along with several other system locked files.

Resolution was to download the VSS SDK from Microsoft's web site. The SDK h=
as an executable vshadow.exe which will allow you to create volume shadow c=
opies that are mapped to a drive, allowing rsync to use the VSS drive where=
 no files are locked.

An example command set would be:

rem create a permanent shadow copy
vshadow.exe -p -nw -script=3Dvars.bat
call vars.bat
rem drive H: is assigned to the permanent shadow copy created
vshadow.exe -el=3D%SHADOW_ID_1%,H:
rem perform your rsync operation, use drive H: (shadow drive) as source
rsync.exe -ruztiv '/cygdrive/h/xxxxxxx' myrsyncserver::myrsyncuser
rem remove the permanent shadow copy
vshadow.exe -ds=3D%SHADOW_ID_1%

-- Contributed by Rob Bosch

You may also visit this link for more detailed information.