Welcome! » Log In » Create A New Profile

Concurrent Jobs only for Backup Jobs

Posted by Anonymous 
Concurrent Jobs only for Backup Jobs
March 08, 2012 12:11AM
Hello

I did not understand how Maximum Concurrent Jobs works. In special the
sentence "Note, this directive limits only Jobs with the same name as the
resource in which it appears ".
I try to describe what I want. I have some jobs of type admin. They have to
be run before backup jobs in a defined sequence. After all admin jobs are
finihed, the backup jobs should start. The backup jobs (different clients)
should run concurrently. After the backup jobs are finished, verify jobs
should start. And after the verify, some other admin jobs should start in a
defined sequence. In other words: only the backup and verify jobs should
run concurrently, the admin jobs in a defined sequence before and after all
other jobs.

admin job 1
admin job 2
admin job 3

backup job client 1, backup job client 2 ...
verify job client 1, verify job client 2 ... (VolumeToCatalog)

admin job 4
admin job 5
admin job 6

My configuration now is Concurrent Jobs for sd and fd are set to 10. The "
Maximum Concurrent Jobs" for the director is set to 1, to ensure the admin
jobs runs in sequence before the backup jobs respectively after the verify
jobs. All Jobs run in sequence. But I want only the admin jobs running in
sequence.

Thank you!

Mit freundlichen Grüßen / Best regards

Markus Kress
System Technologies

GLS IT-Services GmbH
GLS Germany-Straße 1-7
36286 Neuenstein
Germany

T +49 (0) 66 77 17 426
M +49 (0) 172 1781 426
F +49 (0) 66 77 17 486

E markus.kress < at > gls-itservices.com

___________________________________________________________________________________________________________________

GLS IT Services GmbH
Sitz: Neuenstein, Amtsgericht Bad Hersfeld HRB 388, Geschäftsführer: Rüdiger Schmahl
___________________________________________________________________________________________________________________

------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
[www.accelacomm.com]
_______________________________________________
Bacula-users mailing list
Bacula-users < at > lists.sourceforge.net
[lists.sourceforge.net]
Concurrent Jobs only for Backup Jobs
March 08, 2012 01:09AM
Op 8/03/2012 9:09, Markus Kress schreef:
Quote

Quote

Hello

I did not understand how Maximum Concurrent Jobs works. In special the
sentence "Note, this directive limits only Jobs with the same name as the
resource in which it appears ".
I try to describe what I want. I have some jobs of type admin. They have to
be run before backup jobs in a defined sequence. After all admin jobs are
finihed, the backup jobs should start. The backup jobs (different clients)
should run concurrently. After the backup jobs are finished, verify jobs
should start. And after the verify, some other admin jobs should start in a
defined sequence. In other words: only the backup and verify jobs should
run concurrently, the admin jobs in a defined sequence before and after all
other jobs.
By default bacula will not run jobs with different priorities concurrently, so set different priorities for your different kinds of jobs. E.g.:
    [*]Admin job 1: 10 [*]Admin job 2: 11 [*]All backup jobs: 20 [*]All Verify jobs: 30 [*]Admin job 3: 40 [*]Admin job 4: 41 [*]...
Regards,
Jeremy

**** DISCLAIMER ****
http://www.schaubroeck.be/maildisclaimer.htm
Concurrent Jobs only for Backup Jobs
March 08, 2012 01:13AM
Hi Markus,

On Thu, Mar 08, 2012 at 09:09:22AM +0100, Markus Kress wrote:
Quote

defined sequence. In other words: only the backup and verify jobs should
run concurrently, the admin jobs in a defined sequence before and after all
other jobs.
admin job 1
admin job 2
admin job 3
backup job client 1, backup job client 2 ...
verify job client 1, verify job client 2 ... (VolumeToCatalog)
admin job 4
admin job 5
admin job 6
I solve similar things with priorities and a job to schedule the admin
jobs. The core statements are:
Allow Mixed Priority = no
Maximum Concurrent Jobs = 100

All backup jobs are run at e.g priority 50, then you can just run the
admin jobs beforhand with priorities between 1 and 40, those afterwards
with priorities between 60 and 100. The verify jobs you can run e.g. at
priority 55 all at once in a schedule or scheduled by the individual job
as a post-job, depending on how your load-szenario is.
The numbers are made up, I use priorities 5-20 myself and an admin job
ScheduleCopyMigrate (priority 15) priority that schedules 3 admin jobs,
CopyArch (prio 5), MigrateTape (prio 7), CopyTape (prio 8). The
ScheduleCopyArchive is timed after the backups (prio 10) start.
That way all backups are done, then CopyArch runs, which in turn
schedules a ton of copy jobs at priority 5, when they are done
MigrateTape schedules a few migration jobs at prio 7, after they are
done, CopyTape schedules more copy jobs at priority 8.
That way I make sure, all scheduled jobs are done before the next normal
backups start.

Yes, I am aware this has nothing to do with admin connections.

Regards,
Adrian
--
LiHAS - Adrian Reyer - Hessenwiesenstraße 10 - D-70565 Stuttgart
Fon: +49 (7 11) 78 28 50 90 - Fax: +49 (7 11) 78 28 50 91
Mail: lihas < at > lihas.de - Web: [lihas.de]
Linux, Netzwerke, Consulting & Support - USt-ID: DE 227 816 626 Stuttgart

------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
[www.accelacomm.com]
_______________________________________________
Bacula-users mailing list
Bacula-users < at > lists.sourceforge.net
[lists.sourceforge.net]
Concurrent Jobs only for Backup Jobs
March 13, 2012 03:52AM
Hello Adrian,

thank you, it works. I've tested this two years ago and it doesn't work as
it should work. So I never had a look again about the priorities. Actually
I don't know if there was a bug in bacula or in my two years old config.
But I still use many parts of my old configuration where the prios are
still set like your described. So I had only to set the max conurrent to a
higher value.

Mit freundlichen Grüßen / Best regards

Markus Kress
System Technologies

GLS IT-Services GmbH
GLS Germany-Straße 1-7
36286 Neuenstein
Germany

T +49 (0) 66 77 17 426
M +49 (0) 172 1781 426
F +49 (0) 66 77 17 486

E markus.kress < at > gls-itservices.com

Adrian Reyer <bacula-lists < at > lihas.de> schrieb am 08.03.2012 10:12:20:

Quote

Hi Markus,

On Thu, Mar 08, 2012 at 09:09:22AM +0100, Markus Kress wrote:
Quote

defined sequence. In other words: only the backup and verify jobs
should
Quote

Quote

run concurrently, the admin jobs in a defined sequence before and after
all
Quote

Quote

other jobs.
admin job 1
admin job 2
admin job 3
backup job client 1, backup job client 2 ...
verify job client 1, verify job client 2 ... (VolumeToCatalog)
admin job 4
admin job 5
admin job 6
I solve similar things with priorities and a job to schedule the admin
jobs. The core statements are:
Allow Mixed Priority = no
Maximum Concurrent Jobs = 100

All backup jobs are run at e.g priority 50, then you can just run the
admin jobs beforhand with priorities between 1 and 40, those afterwards
with priorities between 60 and 100. The verify jobs you can run e.g. at
priority 55 all at once in a schedule or scheduled by the individual job
as a post-job, depending on how your load-szenario is.
The numbers are made up, I use priorities 5-20 myself and an admin job
ScheduleCopyMigrate (priority 15) priority that schedules 3 admin jobs,
CopyArch (prio 5), MigrateTape (prio 7), CopyTape (prio 8). The
ScheduleCopyArchive is timed after the backups (prio 10) start.
That way all backups are done, then CopyArch runs, which in turn
schedules a ton of copy jobs at priority 5, when they are done
MigrateTape schedules a few migration jobs at prio 7, after they are
done, CopyTape schedules more copy jobs at priority 8.
That way I make sure, all scheduled jobs are done before the next normal
backups start.

Yes, I am aware this has nothing to do with admin connections.

Regards,
Adrian
--
LiHAS - Adrian Reyer - Hessenwiesenstraße 10 - D-70565 Stuttgart
Fon: +49 (7 11) 78 28 50 90 - Fax: +49 (7 11) 78 28 50 91
Mail: lihas < at > lihas.de - Web: [lihas.de]
Linux, Netzwerke, Consulting & Support - USt-ID: DE 227 816 626 Stuttgart

___________________________________________________________________________________________________________________

GLS IT Services GmbH
Sitz: Neuenstein, Amtsgericht Bad Hersfeld HRB 388, Geschäftsführer: Rüdiger Schmahl
___________________________________________________________________________________________________________________

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
[p.sf.net]
_______________________________________________
Bacula-users mailing list
Bacula-users < at > lists.sourceforge.net
[lists.sourceforge.net]
Sorry, only registered users may post in this forum.

Click here to login