Bacula-users

Re: [Bacula-users] Rif: Re: LTO3 performance

2009-01-08 08:15:56
Subject: Re: [Bacula-users] Rif: Re: LTO3 performance
From: Alan Brown <ajb2 AT mssl.ucl.ac DOT uk>
To: Chris Hoogendyk <hoogendyk AT bio.umass DOT edu>
Date: Thu, 8 Jan 2009 13:13:13 +0000 (GMT)
On Wed, 7 Jan 2009, Chris Hoogendyk wrote:

> Most backup software leaves the responsibility for planning more in the
> sysadmin's hands. If the software is just writing data to the tape until
> it hits the end of tape and then asking for another, hardware
> compression is a logical choice.

Part of the preference for no hardware compression in Amanda and other
packages is that a lot of them assume fixed tape sizes, so the only
thing that hardware compression gets you is less time to write to that
maximum.

ie: Program assumes tape is 33Gb. When 33Gb is reached the program
demands the tape be changed, even if the tape is only physically half
used thanks to hardware compression

Most of these types of programs have an all-or-nothing approach to
restores. This is not exactly the bacula model.

Even with hardware compression switched off, spooling is likely required
to prevent shoeshining of modern tape drives. Spooling hardware MUST be
fast enough to keep up. Switching on hardware compression increases those
requirements but the budgetary increase is minor.





------------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users