> On May 4, 2015, at 4:14 AM, Luc Van der Veken <lucvdv AT wimionline DOT com> 
> wrote:
> 
> 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 plan to create one device per client.

As pointed out offline, attribute spooling can be important for parallel (i.e. 
concurrent) jobs.  The theory being: database access while writing files slows 
down both processes.

In my case, the database server is on another machine.

> 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.

I'm not sure I want interleaving.

> 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.

Everything has the same retention period.

—
Dan Langille
http://langille.org/

signature.asc
Description: Message signed with OpenPGP using GPGMail

------------------------------------------------------------------------------
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