Hello,
I've just released winbacula-vss-1.37.31.exe to the Win32-beta area on Source
Forge.
This version corrects the problem that you noted below. You need only specify
"File = c:" for the VSS snapshot to be taken. In addition, I've added "VSS"
on the status output in front of each Job output when the job is being backed
up by VSS. This is in addition to the VSS on the signon line, which
indicates that the FD is VSS enabled.
There are a good number of reasons why a particular backup cannot be made with
VSS, and generally they are reported in the Job output. However, as is
normal for new code, some of the fail conditions may not report correctly.
I've corrected at least one and as time goes on, we will correct them all.
Please be aware of one restriction on VSS backups: you may run only one job at
a time any given client. You may run multiple simultaneous jobs, but only
one that uses VSS in any given client. I suspect that few if any of you run
multiple simultaneous backups in a single client, so hopefully this will
create no problems.
Thanks for reporting this bug.
Best regards, Kern
On Thursday 21 July 2005 04:30, Thomas Simmons wrote:
> Seems I spoke too soon. After seeing the output:
>
> 21-Jul 21:59 nemo-fd: Generate VSS snapshots. Driver="VSS WinXP",
> Drive(s)="C"
> 21-Jul 21:59 nemo-fd: VSS Writer: "MSDEWriter", State: 1 (VSS_WS_STABLE)
> 21-Jul 21:59 nemo-fd: VSS Writer: "Microsoft Writer (Bootable State)",
> State: 1 (VSS_WS_STABLE)
> 21-Jul 21:59 nemo-fd: VSS Writer: "WMI Writer", State: 1 (VSS_WS_STABLE)
> 21-Jul 21:59 nemo-fd: VSS Writer: "Microsoft Writer (Service State)",
> State: 1 (VSS_WS_STABLE)
>
> I walked away but the backup failed because it couldn't find c:/*. In
> any event, I found that specifying two trailing slashes after c: does
> work. I don't yet know if this will cause any issues when doing the
> restore, I'll be testing that tomorrow.
>
> FileSet {
> Name = "default-winxp"
> Enable VSS = yes
> Include {
> Options {
> signature = MD5
> }
> File = "c://"
> }
> }
>
> Thanks,
> Thomas
>
> > Kern, List,
> > I figured out what the issue is! When backing up an entire drive, an
> > asterix must follow the trailing /. If the fileset is specified as
> > follows VSS will not be used:
> > FileSet {
> > Name = "default-winxp"
> > Enable VSS = yes
> > Include {
> > Options {
> > signature = MD5
> > }
> > File = "c:/"
> > }
> > }
> >
> > Adding a * to "c:/" solves the issue.
> >
> > FileSet {
> > Name = "default-winxp"
> > Enable VSS = yes
> > Include {
> > Options {
> > signature = MD5
> > }
> > File = "c:/*"
> > }
> > }
> >
> > Thanks,
> > Thomas
> >
> > Kern Sibbald wrote:
> >> On Thursday 21 July 2005 19:55, Nicolas Lopez wrote:
> >>> [EMAIL PROTECTED] wrote:
> >>>> Kern,
> >>>> Thanks for your reply. I am using the VSS enabled FD. Here is the
> >>>> output
> >>>> from status client.
> >>>>
> >>>> lightning:~# echo "status client=nemo-fd" | bconsole
> >>>> Connecting to Director lightning:9101
> >>>> 1000 OK: lightning-dir Version: 1.37.30 (14 July 2005)
> >>>> Enter a period to cancel a command.
> >>>> status client=nemo-fd
> >>>> Using default Catalog name=MyCatalog DB=bacula
> >>>> Connecting to Client nemo-fd at nemo:9102
> >>>>
> >>>> nemo-fd Version: 1.37.30 (14 July 2005) VSS Windows XP MVS NT 5.1.2600
> >>>
> >>> I think I see the problem, you're trying to backup an XP system. XP
> >>> is only a VSS client, it doesn't actually do Shadow Copies itself,
> >>> that's a Server 2003 thing. Microsoft bundled the VSS client with SP2
> >>> so that you wouldn't have to install it separately.
> >>> I haven't upgraded my director to 1.37 yet to double check that it
> >>> does work against out 2003 server, but as soon as it hits Debian I
> >>> will.
> >>
> >> I don't know what is going on here, but I'm backing up a Windows XP
> >> Home machine that has the same logon:
> >>
> >> Tibs Version: 1.37.30 (14 July 2005) VSS Windows XP MVS NT 5.1.2600
> >>
> >> with bconsole, and here is the top part of my Job report:
> >> 19-Jul 01:23 MainSD: Spooling data ...
> >> 19-Jul 01:23 Tibs: Generate VSS snapshots. Driver="VSS WinXP",
> >> Drive(s)="C"
> >> 19-Jul 01:23 Tibs: VSS Writer: "WMI Writer", State: 1 (VSS_WS_STABLE)
> >> 19-Jul 01:23 Tibs: VSS Writer: "MSDEWriter", State: 1 (VSS_WS_STABLE)
> >> 19-Jul 01:23 Tibs: VSS Writer: "Microsoft Writer (Bootable State)",
> >> State: 1 (VSS_W
> >> 19-Jul 01:23 Tibs: VSS Writer: "Microsoft Writer (Service State)",
> >> State: 1 (VSS_WS
> >> 19-Jul 01:25 MainSD: Committing spooled data to Volume. Despooling
> >> 534,420 bytes ..
> >> 19-Jul 01:25 MainSD: Sending spooled attrs to the Director. Despooling
> >> 2,539 bytes
> >> 19-Jul 01:25 HeadMan: Bacula 1.37.30 (14Jul05): 19-Jul-2005 01:25:57 ...
> >>
> >> As you can see, the VSS snapshot was clearly taken. I'll take a look
> >> at the code tomorrow. Perhaps I will see something.
> >>
> >>> - Nick Lopez
> >>> [EMAIL PROTECTED]
> >>>
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
