This approach can help too: besides doing them in parallel (limited to 5 
concurrent jobs because ultimately it all winds up on the same disks), I also 
divided them into 4 groups.
From the 1st to 4th Friday night each month, a full backup is done of one group 
and differential of the other three. If there's a fifth Friday, it's 
differential for all.

I am using only one pool and device for all, just raised 'Maximum Concurrent 
Jobs' above 1.
That causes interleaving, but on disk that should be no problem.

Retention is the same for all clients and jobs in my case. If that is not so 
for you, you may better go for multiple pools/devices.


-----Original Message-----
From: Dan Langille [mailto:dan AT langille DOT org] 
Sent: 03 May 2015 15:43
To: bacula-users
Subject: [Bacula-users] Moving from serial jobs to parallel jobs.

I think I'm going to start doing my backups (to disk) in parallel. The monthly 
full backups take *hours*.  They still aren't done, 8 hours later.

  I've heard different approaches, but I think a different device for each 
client sounds best.  All the same pools, but on different devices.  Which also 
means different directories.  Should be fun.

—
Dan Langille
http://langille.org/





------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users