Hi, We have two storage directors: one locally and one located at an off-site data center. Our connection to the data center is a 10G link (but it's shared with other UC universities). Using programs like BBFTP, we've been able to achieve actual data throughput of something like 600Mbit/s to the remote storage daemon.
The storage daemon boxes are FreeBSD 8.2 with 16TB (local) and 12TB (remote) ZFS file systems, and the file daemon we're testing with is CentOS with an ext3 file system. When we back up to the local storage daemon, we're getting about 500Mbit/s. When we back up to the remote storage daemon, we're getting about 66Mbit/s. So, my question is: are there any compile-time options or configuration tricks for Bacula that would make it perform better on this sort of long-haul connection? I'm guessing that the answer is probably "you need to tweak your OS TCP/IP stack", but I thought I'd ask here if anyone else has this sort of setup and could maybe offer advice specific to Bacula that might help, at least to some degree. Thanks! -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Tim Gustafson t...@soe.ucsc.edu Baskin School of Engineering 831-459-5354 UC Santa Cruz Baskin Engineering 317B -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- ------------------------------------------------------------------------------ Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Discover what all the cheering's about. Get your free trial download today. http://p.sf.net/sfu/quest-dev2dev2 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
