I was just wondering what the factors limiting the speed with which
Bacula writes to tape are? I performed some testing on my LTO-3 drive
and found that the theoretical limit is 276G/hr, while my backups are
writing at around 174G/hr. The client is the Bacula system itself. The
FD is reading files from a filesystem that resides on a SATAbeast FCA
attached storage array. The files are Oracle dumps, and the options I
have specified are:
signature = MD5
verify = pins5
sparse = yes
noatime = yes
The only compression I am using is the tape devices compression, which
at 2:1 compression should be over 500G/hr. I wrote a 3.4T job in
19h30m. At what seems to be a compression of 1.5:1. This should still
be faster than the 174G/hr its acheiving.
Would using MD5 signatures slow this up?
Are any of these settings tunable and do they affect Bacula performance?
mt-back4.director Version: 2.0.3 (06 March 2007) i386-pc-solaris2.8 solaris 5.8
Daemon started 05-Nov-07 07:07, 5 Jobs run since started.
Heap: bytes=72,064 max_bytes=74,700 bufs=376 max_bufs=397
Thanks,
Shon
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
