In the past for setting up disk based backups I've used multiple physical disks 
each with a  single sd device on them and limited each device to a single job 
at a time, and each fd backing up to its own pool, with one device per job. 
This minimises seeks and fragmentation etc but does mean I'm making guesses 
about what client to back up to which disk to balance occupancy and workload.

I'm setting up a new server for backups now with 4 x 3TB disks and am thinking 
about the best parameters for filesystems. I'd like for multiple jobs to be 
able to run at once (still one volume per job) and with all the SD data sitting 
on one giant partition on RAID5 to maximise storage use.

I think I should be able to tweak the sd media filesystem to best suit this and 
minimise fragmentation. The parameters I'm looking at are:
. large allocation unit - maybe up to 1MB
. high commit time to maximise the case of streaming writes. Up to 30 seconds 
should be acceptable, provided a sync is done at the conclusion of each job
. data in writeback mode (eg no ordering of data writes, only metadata is 
journaled, on the basis that on a power failure the current backup is 
considered dead anyway).

Anything else I should be considering? Does any of the above sound like a 
recipe for disaster?

Thanks

James


------------------------------------------------------------------------------
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users