The full backup completed last night (using c://), of my XP Pro laptop,
my and my girlfriend's XP Home laptop. I just ran a restore of
c:\bacula, and it restored successfully. I'll run a full restore when I
get home tonight and see how that goes.
Thanks,
Thomas
Kern Sibbald wrote:
Nice that you figured out what the issue is. As you noticed having a * will
not work. I suspect that // will not work either. In any case, Thorsten is
on vacation if I am not mistaken, but your discovery has pointed me to some
code that looks suspect to me. It assumed that the path must always be
present, which is not the case.
I tested only with paths (never c: alone due to the volume of data) and I
suspect the same was true for Thorsten.
I'm building the revised code, which should accept your // if you want, but it
is now going to eat it up (and hopefully nothing more). Some testing will
be necessary before I post a new version.
More later today.
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
-------------------------------------------------------
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
-------------------------------------------------------
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
