[Bacula-bugs] [bacula 0000815]: After recover full or partial catalog in table Job field ClientId becomes zero

[<bac...@li...>]

The following issue requires your FEEDBACK. 
====================================================================== 
http://bugs.bacula.org/view.php?id=815 
====================================================================== 
Reported By:                umnov
Assigned To:                
====================================================================== 
Project:                    bacula
Issue ID:                   815
Category:                   other
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
====================================================================== 
Date Submitted:             03-30-2007 07:56 EDT
Last Modified:              03-31-2007 12:10 EDT
====================================================================== 
Summary:                    After recover full or partial catalog in table Job
field ClientId becomes zero
Description: 
After bscan bacula director through bconsole never see's restored jobs and
files.
Thanks field name in table Job, I can manually recover field Clientid.

====================================================================== 

---------------------------------------------------------------------- 
 kern - 03-31-07 12:10  
---------------------------------------------------------------------- 
I don't believe that this is a bug, but a misunderstanding on your part.
bscan is not meant to restore *every* field in the database. It cannot
restore Client ids since they do not exist on the Volume.  The client
records must pre-exist and are created by Bacula providing you have a
correct bacula-dir.conf file.  bscan is designed to provide the minimum
information to do a restore.

It is not clear from your text what error you are reporting. You didn't
even mention what SQL engine you are using. Please do so. Could you please
provide a list of exactly what commands you ran and why as well as an
"llist" of the appropriate table item that is incorrect, or a listing
produced using the SQL command which shows what field is missing.  Keep in
mind that the Client information is not on the volume.

 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
03-30-07 07:56  umnov          New Issue                                    
03-31-07 12:10  kern           Note Added: 0002340                          
03-31-07 12:10  kern           Status                   new => feedback     
======================================================================