Andreas Koch wrote:
> I am just running my first ``real'' backup job.  It consists of
> backing up roughly 300GB of data via a 75GB spool partition to a DLT
> VS80 drive.  While the process generally works as expected, I am
> somewhat disappointed by the performance:  According to the `status
> all' statistics, Bacula 1.36.3 achieves roughly 1.5MB/s, and is
> shoe-shining the tape during despooling quite a bit.  Note that the
> drive itself is rated for 3 MB/s, a speed it does indeed achieve,
> e.g., when using tar with some double buffering (to compensate for
> large numbers of small files).  I had hoped that Bacula's spooling
> mechanism would actually manage to keep the tape streaming.
> 
> My current setup has all daemons running on the same machine:  An Athlon XP
> 1700+ CPU, 512 MB RAM, Adaptec 2400 IDE RAID-5 with 4x300GB disks and
> 128MB of on-board cache, and a Benchmark DLT VS80 drive.  The spool
> disk is a dedicated 80GB IDE disk holding only the spool data.
> 
> I'd be grateful for any help diagnosing this slow-down. If you need
> further info, please let me know.

I think the magic word -- or acronym -- there, may be "IDE".  IDE
performance *sucks*, especially if you have more than one device on a
channel.  What are the spool disk and the VS80 connected to?  Can you
get them both onto their own IDE channels with no other device sharing
that channel?



-- 
 Phil Stracchino       [EMAIL PROTECTED]
    Renaissance Man, Unix generalist, Perl hacker
 Mobile: 603-216-7037         Landline: 603-886-3518


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to