Re: [Bacula-users] Config error: Keyword EnableVSS not permitted in this re

2005-07-22 Thread Kern Sibbald
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 out

Re: [Bacula-users] Config error: Keyword EnableVSS not permitted in this re

2005-07-22 Thread Dana Bolden
Thanks Thomas!! I can confirm the same responses to the * and the second slash that you received. The backup does appear to be OK. I too am curious about the impact to restores. I'll test a restore to an alternate directory over the weekend if I have a bit of time. Dana At 10:30 PM 7/20

Re: [Bacula-users] Config error: Keyword EnableVSS not permitted in this re

2005-07-22 Thread Thomas Simmons
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 y

Re: [Bacula-users] Config error: Keyword EnableVSS not permitted in this re

2005-07-22 Thread Kern Sibbald
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 alway

Re: [Bacula-users] Config error: Keyword EnableVSS not permitted in this re

2005-07-21 Thread Thomas Simmons
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_STABL

Re: [Bacula-users] Config error: Keyword EnableVSS not permitted in this re

2005-07-21 Thread Thomas Simmons
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

Re: [Bacula-users] Config error: Keyword EnableVSS not permitted in this re

2005-07-21 Thread Kern Sibbald
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 O

Re: [Bacula-users] Config error: Keyword EnableVSS not permitted in this re

2005-07-21 Thread twsnnva
;s using volume shadow copy. Thanks, Thomas > > From: Nicolas Lopez <[EMAIL PROTECTED]> > Date: 2005/07/21 Thu PM 01:55:03 EDT > To: bacula-users@lists.sourceforge.net > Subject: Re: [Bacula-users] Config error: Keyword EnableVSS not permitted > in this re > > [EMAI

Re: [Bacula-users] Config error: Keyword EnableVSS not permitted in this re

2005-07-21 Thread Nicolas Lopez
[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 cance

Re: [Bacula-users] Config error: Keyword EnableVSS not permitted in this re

2005-07-21 Thread twsnnva
/job.c:205 Executing JobId= command. nemo-fd: ../../filed/job.c:189 > From: <[EMAIL PROTECTED]> > Date: 2005/07/21 Thu AM 09:08:08 EDT > To: > CC: <[EMAIL PROTECTED]> > Subject: Re: [Bacula-users] Config error: Keyword EnableVSS not permitted in > this re > > F

Re: [Bacula-users] Config error: Keyword EnableVSS not permitted in this re

2005-07-21 Thread twsnnva
t;> > >>> > From: Kern Sibbald <[EMAIL PROTECTED]> >>> > Date: 2005/07/20 Wed PM 04:25:28 EDT >>> > To: [EMAIL PROTECTED] >>> > CC: bacula-users@lists.sourceforge.net, >>> > Frederic PIERROT <[EMAIL PROTECTED]> >>&

Re: Re: [Bacula-users] Config error: Keyword EnableVSS not permitted in this re

2005-07-21 Thread Frederic PIERROT
rver there and see if I have the same issue. Thanks, Thomas > > From: Kern Sibbald <[EMAIL PROTECTED]> > Date: 2005/07/20 Wed PM 04:25:28 EDT > To: [EMAIL PROTECTED] > CC: bacula-users@lists.sourceforge.net, > Frederic PIERROT <[EMAIL PROTECTED]> > Subject:

Re: Re: [Bacula-users] Config error: Keyword EnableVSS not permitted in this re

2005-07-20 Thread Frederic PIERROT
urceforge.net, > Frederic PIERROT <[EMAIL PROTECTED]> > Subject: Re: [Bacula-users] Config error: Keyword EnableVSS not permitted in this re > > On Wednesday 20 July 2005 21:59, [EMAIL PROTECTED] wrote: > > Kern, > > Thanks for your reply. I am using the VSS ena

Re: Re: [Bacula-users] Config error: Keyword EnableVSS not permitted in this re

2005-07-20 Thread twsnnva
Date: 2005/07/20 Wed PM 04:25:28 EDT > To: [EMAIL PROTECTED] > CC: bacula-users@lists.sourceforge.net, > Frederic PIERROT <[EMAIL PROTECTED]> > Subject: Re: [Bacula-users] Config error: Keyword EnableVSS not permitted in > this re > > On Wednesday 20 Jul

Re: [Bacula-users] Config error: Keyword EnableVSS not permitted in this re

2005-07-20 Thread Kern Sibbald
On Wednesday 20 July 2005 21:59, [EMAIL PROTECTED] wrote: > Kern, > Thanks for your reply. I am using the VSS enabled FD. Here is the output > from status client. Well, something is obviously wrong because the FD reports that 0 jobs have run since it was started. I recommend you run again, then

Re: Re: [Bacula-users] Config error: Keyword EnableVSS not permitted in this re

2005-07-20 Thread twsnnva
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=n