> What happens with a migrate/copy from a storage that supports > compression (as per your new option above) to one that doesn't, or the > other way around? I assume nothing different as this is an option that > impacts the FD only right? > > Ideally, if you copied an uncompressed job from tape to disk, you might > like the option to compress the job if it wasn't compressed already (not > possible at the moment afaik as the compression is always done on the > fd?). > > If you copied a compressed job from disk to tape (a much more likely > scenario) the job should stay compressed (no point undoing the > compression 'effort'), but the hardware compression on the tape drive > itself should be disabled. AFAIK, bacula has no way of turning tape > drive compression on or off at this time though.
In this situation, at the end, the stream is compressed, which is the main goal. The tape compression isn't used? It doesn't matter, you won't gain anything. And, more important, i don't think that it's a good idea to mix hardware compressed/uncompressed files on tape. > If the items in the above two paragraphs are addressed at any time in > the future, the AllowCompression option would need to be in the > bacula-sd.conf file right? I don't think so. Bye > James ------------------------------------------------------------------------------ Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
