John Drescher wrote:
>> | i thought attributes were spooled, then commited to the database, of
>> course
>> | i may be completely wrong :-\
>>
>> Actually, you may be right. I ran into a situation over the weekend
>> where something that was locking the database caused attribute spooling
>> to hang. Anyone have a definitive answer?
>>
>>     
> Attributes are spooled to the database at the end of the job. If you
> have thousands of files bacula may indicate that the job is finished
> before this spooling is done but if you check the status of the
> storage you will see that spooling is still happening. I am not sure
> if you can remove media while this is happening as I have never
> attempted that.
>
>   
Hm. Not sure about that. The manual says that setting Spool Attributes = yes
causes the storage daemon to buffer the attributes to a temp file in the 
working
directory, and then send them to the director (presumably for insertion 
into the catalog)
when 'writing the Job data to the tape is complete' whatever that means.

I also think that the storage daemon will have written those attributes 
to tape along
with the per-file data (not at the job completion), so that bscan can 
unback files
without a catalog,  or rebuild the catalog .

Cheers,
Terry

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users