>>>>> On Thu, 18 Feb 2010 10:58:54 -0500, empsis  said:
> 
> Martin Simmons wrote:
> > 
> > > 
> > > > 
> > > > > 
> > > > > > 
> > > > > > > On Thu, 18 Feb 2010 09:49:44 -0500, empsis  said:
> > > > > > > 
> > > > > > 
> > > > > 
> > > > 
> > > 
> > > Martin Simmons wrote:
> > > 
> > > > 
> > > > 
> > > > > 
> > > > > 
> > > > > > 
> > > > > > 
> > > > > > > 
> > > > > > > 
> > > > > > > > 
> > > > > > > > 
> > > > > > > > > On Thu, 18 Feb 2010 06:28:21 -0500, empsis  said:
> > > > > > > > > 
> > > > > > > > > 
> > > > > > > > 
> > > > > > > > 
> > > > > > > 
> > > > > > > 
> > > > > > 
> > > > > > 
> > > > > 
> > > > > 
> > > > > Thanks for the advice. 
> > > > > 
> > > > > I did this: 
> > > > > 
> > > > > #setdebug level=300 sd 
> > > > > Automatically selected Storage: File 
> > > > > Connecting to Storage daemon File at escrow:9103 
> > > > > 3000 OK setdebug=300 
> > > > > 
> > > > > And I get the same level of detail: 
> > > > > 
> > > > > 18-Feb 17:43 mercury-dir JobId 17749: Start Restore Job 
> > > > > RestoreFiles.2010-02-18_17.43.44_34 
> > > > > 18-Feb 17:43 mercury-dir JobId 17749: Using Device "FileDaily" 
> > > > > 18-Feb 17:43 mercury-sd JobId 17749: Fatal error: Bootstrap file 
> > > > > error: Keyword VolAddr not found 
> > > > > : Line 6, col 7 of file 
> > > > > /var/lib/bacula/mercury-sd.RestoreFiles.2010-02-18_17.43.44_34.18.bootstrap
> > > > >  
> > > > > VolAddr=214-999936174 
> > > > > 
> > > > > 18-Feb 17:43 mercury-sd JobId 17749: Fatal error: Error parsing 
> > > > > bootstrap file. 
> > > > > 18-Feb 17:43 mercury-dir JobId 17749: Fatal error: Bad response to 
> > > > > Bootstrap command: wanted 3000 OK bootstrap 
> > > > > , got 3904 Error bootstrap 
> > > > > 
> > > > > 18-Feb 17:43 mercury-dir JobId 17749: Error: Bacula mercury-dir 3.0.3 
> > > > > (18Oct09): 18-Feb-2010 17:43:46 
> > > > > Build OS: i686-pc-linux-gnu debian 5.0.1 
> > > > > JobId: 17749 
> > > > > Job: RestoreFiles.2010-02-18_17.43.44_34 
> > > > > Restore Client: mercury 
> > > > > Start time: 18-Feb-2010 17:43:46 
> > > > > End time: 18-Feb-2010 17:43:46 
> > > > > Files Expected: 1 
> > > > > Files Restored: 0 
> > > > > Bytes Restored: 0 
> > > > > Rate: 0.0 KB/s 
> > > > > FD Errors: 0 
> > > > > FD termination status: 
> > > > > SD termination status: 
> > > > > Termination: *** Restore Error *** 
> > > > > 
> > > > > 18-Feb 17:43 mercury-dir JobId 17749: Error: Bacula mercury-dir 3.0.3 
> > > > > (18Oct09): 18-Feb-2010 17:43:46 
> > > > > Build OS: i686-pc-linux-gnu debian 5.0.1 
> > > > > JobId: 17749 
> > > > > Job: RestoreFiles.2010-02-18_17.43.44_34 
> > > > > Restore Client: mercury 
> > > > > Start time: 18-Feb-2010 17:43:46 
> > > > > End time: 18-Feb-2010 17:43:46 
> > > > > Files Expected: 1 
> > > > > Files Restored: 0 
> > > > > Bytes Restored: 0 
> > > > > Rate: 0.0 KB/s 
> > > > > FD Errors: 1 
> > > > > FD termination status: 
> > > > > SD termination status: 
> > > > > Termination: *** Restore Error *** 
> > > > > 
> > > > > 
> > > > > Sorry, but I am quite new to bacula, is there some special location 
> > > > > where SD stores it's own log? 
> > > > > 
> > > > > BTW, any (contra/) arguments to try upgrading the version of bacula?
> > > > > empsis wrote:
> > > > > 
> > > > > 
> > > > > > Hi,
> > > > > > 
> > > > > > trying to restore a file from a backup, but it fails. 
> > > > > > 
> > > > > > FD - Windows x64 client on Windows Server 2008 x64, version 3.0.3
> > > > > > 
> > > > > > SD and Director on the same Debian machine, both version 3.0.3
> > > > > > 
> > > > > > Backups were performed without any problems, but restore - 
> > > > > > unsuccessful.  
> > > > > > No restores have been tried for this client until now, other 
> > > > > > clients - ok. 
> > > > > > 
> > > > > > Any help would be appreciated. Thanks.
> > > > > > 
> > > > > > Log:
> > > > > > 
> > > > > > Job queued. JobId=17622
> > > > > > *
> > > > > > 12-Feb 16:48 mercury-dir JobId 17622: Start Restore Job 
> > > > > > RestoreFiles.2010-02-12_16.48.44_48
> > > > > > 12-Feb 16:48 mercury-dir JobId 17622: Using Device "FileDaily"
> > > > > > 12-Feb 16:48 mercury-sd JobId 17622: Fatal error: Bootstrap file 
> > > > > > error: Keyword VolAddr not found
> > > > > > : Line 6, col 7 of file 
> > > > > > /var/lib/bacula/mercury-sd.RestoreFiles.2010-02-12_16.48.44_48.7.bootstrap
> > > > > > VolAddr=218-999936153
> > > > > > 
> > > > > > 12-Feb 16:48 mercury-sd JobId 17622: Fatal error: Error parsing 
> > > > > > bootstrap file.
> > > > > > 12-Feb 16:48 mercury-dir JobId 17622: Fatal error: Bad response to 
> > > > > > Bootstrap command: wanted 3000 OK bootstrap
> > > > > > , got 3904 Error bootstrap
> > > > > > 
> > > > > > ...
> > > > > > 
> > > > > > 
> > > > > > Bootstrap file contents:
> > > > > > 
> > > > > > Volume="2010-01-30_00-30-pvt-dc01-full"
> > > > > > MediaType="File"
> > > > > > Device="FileDaily"
> > > > > > VolSessionId=215
> > > > > > VolSessionTime=1263483189
> > > > > > VolAddr=218-999936153
> > > > > > FileIndex=1
> > > > > > Count=1
> > > > > > 
> > > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > It actualy looks I cannot restore on ANY client. Could be this is due 
> > > > > to
> > > > > upgrade from 2.x version to 3.0.3 which happened couple of months ago.
> > > > > I have even tried to perform restore on Debian, which is the backup 
> > > > > server
> > > > > and has SD, DIR and FD - the same error.
> > > > > 
> > > > > Any ideas what could be causing this?
> > > > > 
> > > > > 
> > > > 
> > > > Could be version mismatch, but AFAIK all versions support the VolAddr 
> > > > keyword.
> > > > 
> > > > Are these Debian packages or something you built yourself?
> > > > 
> > > 
> > > Thanks for quick reply!
> > > When I upgraded bacula, I downloaded source from bacula.org and compiled 
> > > it,
> > > because this version was not yet available via apt-get.
> > > 
> > > The strangest thing is - restore does not work on the bacula server, which
> > > has the same versions for FD, SD, DIR on the same machine...
> > > 
> > 
> > Yes, that is very strange.
> > 
> > Maybe it is a compiler bug?
> > 
> > The parsing is done by the function parse_bsr in src/stored/parse_bsr.c so 
> > you
> > could try running bacula-sd with debug level 300 to see what it prints.
> > 
> > __Martin
> > 
> > ------------------------------------------------------------------------------
> > Download Intel® Parallel Studio Eval
> > Try the new software tools for yourself. Speed compiling, find bugs 
> > proactively, and fine-tune applications for parallel performance. 
> > See why Intel Parallel Studio got high marks during beta.
> > http://p.sf.net/sfu/intel-sw-dev
> > _______________________________________________
> > Bacula-users mailing list
> > Bacula-users < at > lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/bacula-users
> 
> 
> Thanks for the advice. 
> 
> I did this: 
> 
> #setdebug level=300 sd 
> Automatically selected Storage: File 
> Connecting to Storage daemon File at escrow:9103 
> 3000 OK setdebug=300 
> 
> And I get the same level of detail: 
> 
> 18-Feb 17:43 mercury-dir JobId 17749: Start Restore Job 
> RestoreFiles.2010-02-18_17.43.44_34 
> 18-Feb 17:43 mercury-dir JobId 17749: Using Device "FileDaily" 
> 18-Feb 17:43 mercury-sd JobId 17749: Fatal error: Bootstrap file error: 
> Keyword VolAddr not found 
> : Line 6, col 7 of file 
> /var/lib/bacula/mercury-sd.RestoreFiles.2010-02-18_17.43.44_34.18.bootstrap 
> VolAddr=214-999936174 
> 
> 18-Feb 17:43 mercury-sd JobId 17749: Fatal error: Error parsing bootstrap 
> file. 
> 18-Feb 17:43 mercury-dir JobId 17749: Fatal error: Bad response to Bootstrap 
> command: wanted 3000 OK bootstrap 
> , got 3904 Error bootstrap 
> 
> 18-Feb 17:43 mercury-dir JobId 17749: Error: Bacula mercury-dir 3.0.3 
> (18Oct09): 18-Feb-2010 17:43:46 
> Build OS: i686-pc-linux-gnu debian 5.0.1 
> JobId: 17749 
> Job: RestoreFiles.2010-02-18_17.43.44_34 
> Restore Client: mercury 
> Start time: 18-Feb-2010 17:43:46 
> End time: 18-Feb-2010 17:43:46 
> Files Expected: 1 
> Files Restored: 0 
> Bytes Restored: 0 
> Rate: 0.0 KB/s 
> FD Errors: 0 
> FD termination status: 
> SD termination status: 
> Termination: *** Restore Error *** 
> 
> 18-Feb 17:43 mercury-dir JobId 17749: Error: Bacula mercury-dir 3.0.3 
> (18Oct09): 18-Feb-2010 17:43:46 
> Build OS: i686-pc-linux-gnu debian 5.0.1 
> JobId: 17749 
> Job: RestoreFiles.2010-02-18_17.43.44_34 
> Restore Client: mercury 
> Start time: 18-Feb-2010 17:43:46 
> End time: 18-Feb-2010 17:43:46 
> Files Expected: 1 
> Files Restored: 0 
> Bytes Restored: 0 
> Rate: 0.0 KB/s 
> FD Errors: 1 
> FD termination status: 
> SD termination status: 
> Termination: *** Restore Error *** 
> 
> 
> Sorry, but I am quite new to bacula, is there some special location where SD
> stores it's own log?  Tried googling, looks like there's only one for all..

Either add the -f -d 300 options when starting the bacula-sd from a terminal,
which will keep it in the foreground with debug 300 or use the trace=1 option
in setdebug to make it write to a trace file in the working directory.


> BTW, any (contra/) arguments to try upgrading the version of bacula?

None, as long as you can upgrade all of the clients as well.  You might want
to wait for 5.0.1, which was scheduled for release this week.

__Martin

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users