Hi,
You make a good point. I stuck with the 5Gb as keeping small volumes
aids restore times and reduces possibility of corruption affecting a
large part of the backups in the event of a disk fault, as indicated
in the documentation, which, as you say, may not be appropriate for my
setup any more, particularly as these disk volumes will only survive a
day, so be rarely used for restores.
I do see bacula switching and recycling volumes very often, and I also
intend to examine my tape write speeds, as the copy jobs take a long
time. I presume writing a few large files to tape is more efficient
than a large number of small files.
I think I'll reconsider this volume size and test some variations.
Incidently, do you use verification in your setup. Is this another
set of jobs that need to be scheduled somewhere between the backup
jobs and the copy jobs? I don't have much of a window for doing this.
I don't want to go off topic for this thread, but thought I'd ask
you while I'm typing. I'll start a new thread if I need to pursue
that any further.
Dermot.
On 11/18/10 05:56, Dermot Beirne wrote:
> Hi,
> There is a big difference in the size of individual jobs, they range
> from maybe 30Gb to 300Gb. No individual job would be multi terabyte.
> The number of clients combined would be over 1 TB for a given day,
> rather than an individual job. I used 5Gb as it was a suggested size
> in the bacula documentation.
5GB is a good starting size for fixed-size volumes for a small
installation, but one size need not fit all. It's undoubtedly not an
appropriate choice for a site with a backup volume measured in terabytes
per day. With that kind of volume of data to back up and that much
evident disk space available to do it with, if I wanted to limit volume
sizes I think I might set my volume size limit at 100GB, or even larger.
In actual fact, although my total full-backup set is under a terabyte, I
don't actually limit the size of my disk volumes at all; I instead use
Volume Write Duration to limit any given volume to hold only a single
day's jobs. Remember that none of the examples in the documentation is
set in stone. Use them as a starting point, sure, but apply logic and
decide what's reasonable in your case. Any volume size limit that
forces you to allocate several hundred volumes for a single day of
incremental backups is probably not appropriate for *your* installation,
and may be costing you significant time in sheer overhead. If you're
getting any kind of sane transfer rate at all for a dataset of that
size, Bacula must be having to create new volumes and switch volumes
every few seconds.
--
Phil Stracchino, CDK#2 DoD#299792458 ICBM: 43.5607, -71.355
ala...@caerllewys.net ala...@metrocast.net p...@co.ordinate.org
Renaissance Man, Unix ronin, Perl hacker, Free Stater
It's not the years, it's the mileage.
------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today
http://p.sf.net/sfu/msIE9-sfdev2dev
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
