I posted a couple of days ago that restoring files from 1.39.27
(current CVS) with both encryption and compression turned on
resulted in 0 length files being restored.
I was able to test that further tonight by archiving and restoring a
file in the 4 combinations of encryption/compression off/on.
Running neither, compression alone or encryption alone I was able to
archive and restore a file correctly. Running the two together I
was able to reproduce the problem of 0 length restores, with no
apparent errors.
So... in my testing the combination of encryption and compression is
either not writing files correctly to tape (in which case there is a
lot of tape space taken up needlessly :) or the files are being
corrupted in the restore process; it appears to me to be the latter.
This is on a Linux Centos 4.4 system, dir/sd/fd running on the same
system. The relevant configurations are below.
-- Michael
FileSet {
Name = "Somehost-Archive"
Include {
Options {
signature = MD5
compression = GZIP6
}
File = ...
}
FileDaemon {
Name = somehost-fd
FDport = 9102
WorkingDirectory = /path/to/bacula/working
Pid Directory = /path/to/bacula/working
Maximum Concurrent Jobs = 20
PKI Signatures = Yes
PKI Encryption = Yes
PKI Keypair = "/path/to/bacula/keys/key.pem"
}
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
