The manual indicates that encryption is set in the file daemon.
Is it possible to turn it off on a per job basis?

My catalog backups are encrypted; should disaster strike I'd rather not
have to deal with encryption before getting the catalog back.  That's
the job I'd like to do without encryption.

Of course, since everything else is encrypted, I'll have to deal with it
pretty soon anyway.

I also realize that I could create a special file daemon that didn't use
encryption, but that seems a bit heavyweight.

Related question: The example catalog backup in chapter 21 (Catalog
Maintenance) does not use compression.  Is there a reason for that?  I
imagine the file will compress well, and I'd rather save the space.

Thanks.
Ross Boylan

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users