SearchFAQMemberlist Log in
Reply to topic Page 1 of 1
ClientRunBeforeJob Performance Query
Author Message
Post ClientRunBeforeJob Performance Query 
Hi all,

I am performing 2 Jobs that use the ClientRunBefore feature at a
specific client.

The first Job is a State Backup (Win32) of about 8GB.
The Second is a Exchange Backup of about 32GB.
The State and Exchange Backups are performed using
NTBackup on local an Bacula then grabs the completed BKF file.

Both of these Jobs execute without a problem, but
takes an incredibly log time to complete. (Reports Below)

What I have noticed is that on a Backup Job where
ClientRunBefore is not used the job would start and run
at about 6MB/sec and keep the same performance all the
way through.

But with the jobs that use the ClientRunBefore feature
the job starts at a few Kb/s and then gradually
(an increase in speed of about 30KB/sec) builds
speed until about 6MB/sec.

I am just curious to know if anyone else have experienced a
simmilar isssue or and if so, if there is a way around it?

Yours sincerely

Stephan Heine
Support Engineer
Genetic Interactive
Tel: +27 861 99 88 99
Fax: +27 861 99 77 99
Cell: +27 82 467 1164
EMail: s < at > genetic.co.za

12-Jun 20:22 xxxx-dir: Bacula 1.38.11 (28Jun06): 12-Jun-2007 20:22:36
JobId: 1240
Job: xxxxStateTuesday.2007-06-12_19.00.00
Backup Level: Full
Client: "xxxx-fd" Windows Server 2003,MVS,NT 5.2.3790
FileSet: "xxxxStateSet" 2006-09-13 19:00:02
Pool: "xxxxTuesdayState"
Storage: "FilexxxxStateTuesdayStorage"
Scheduled time: 12-Jun-2007 19:00:00
Start time: 12-Jun-2007 19:51:09
End time: 12-Jun-2007 20:22:36
Elapsed time: 31 mins 27 secs
Priority: 10
FD Files Written: 2
SD Files Written: 2
FD Bytes Written: 7,730,344,766 (7.730 GB)
SD Bytes Written: 7,730,345,032 (7.730 GB)
Rate: 4096.6 KB/s
Software Compression: 42.5 %
Volume name(s): xxxxStateTuesday
Volume Session Id: 8
Volume Session Time: 1181551527
Last Volume Bytes: 7,739,588,003 (7.739 GB)
Non-fatal FD errors: 0
SD Errors: 0
FD termination status: OK
SD termination status: OK
Termination: Backup OK

13-Jun 01:01 xxxx02-dir: Bacula 1.38.11 (28Jun06): 13-Jun-2007 01:01:16
JobId: 1245
Job: xxxxMailTuesday.2007-06-12_19.00.05
Backup Level: Full
Client: "xxxx-fd" Windows Server 2003,MVS,NT 5.2.3790
FileSet: "xxxxMailSet" 2006-09-13 19:00:49
Pool: "xxxxTuesdayMail"
Storage: "FilexxxxMailTuesdayStorage"
Scheduled time: 12-Jun-2007 19:00:04
Start time: 12-Jun-2007 23:12:09
End time: 13-Jun-2007 01:01:16
Elapsed time: 1 hour 49 mins 7 secs
Priority: 10
FD Files Written: 2
SD Files Written: 2
FD Bytes Written: 32,960,720,384 (32.96 GB)
SD Bytes Written: 32,960,720,661 (32.96 GB)
Rate: 5034.5 KB/s
Software Compression: 26.2 %
Volume name(s): xxxxMailTuesday
Volume Session Id: 13
Volume Session Time: 1181551527
Last Volume Bytes: 32,995,490,984 (32.99 GB)
Non-fatal FD errors: 0
SD Errors: 0
FD termination status: OK
SD termination status: OK
Termination: Backup OK

Post ClientRunBeforeJob Performance Query 
Hello,

It has nothing to do with Bacula having a problem, but is just math.

Having a PhD in math would help, but it really doesn't require that much
schooling. It is simple math of averages. If you are driving 1000 miles and
after 1 minute you stop for 10 minutes, your average speed drops to almost
nothing, then gently climbs up to almost the average speed that you would
have if you did not stop.

Date: Wed, 13 Jun 2007 09:23:18 +0200
From: "Stephan Heine - [Genetic Interactive]" <s < at > genetic.co.za>
Subject: [Bacula-users] ClientRunBeforeJob Performance Query
To: <Bacula-users < at > li...>
Message-ID: <007e01c7ad8b$b6d4d790$8319a8c0 < at > stephanheine>
Content-Type: text/plain; charset="us-ascii"

Hi all,

I am performing 2 Jobs that use the ClientRunBefore feature at a
specific client.

The first Job is a State Backup (Win32) of about 8GB.
The Second is a Exchange Backup of about 32GB.
The State and Exchange Backups are performed using
NTBackup on local an Bacula then grabs the completed BKF file.

Both of these Jobs execute without a problem, but
takes an incredibly log time to complete. (Reports Below)

What I have noticed is that on a Backup Job where
ClientRunBefore is not used the job would start and run
at about 6MB/sec and keep the same performance all the
way through.

But with the jobs that use the ClientRunBefore feature
the job starts at a few Kb/s and then gradually
(an increase in speed of about 30KB/sec) builds
speed until about 6MB/sec.

I am just curious to know if anyone else have experienced a
simmilar isssue or and if so, if there is a way around it?

Yours sincerely

Stephan Heine
Support Engineer
Genetic Interactive
Tel: +27 861 99 88 99
Fax: +27 861 99 77 99
Cell: +27 82 467 1164
EMail: s < at > genetic.co.za

12-Jun 20:22 xxxx-dir: Bacula 1.38.11 (28Jun06): 12-Jun-2007 20:22:36
JobId: 1240
Job: xxxxStateTuesday.2007-06-12_19.00.00
Backup Level: Full
Client: "xxxx-fd" Windows Server 2003,MVS,NT 5.2.3790
FileSet: "xxxxStateSet" 2006-09-13 19:00:02
Pool: "xxxxTuesdayState"
Storage: "FilexxxxStateTuesdayStorage"
Scheduled time: 12-Jun-2007 19:00:00
Start time: 12-Jun-2007 19:51:09
End time: 12-Jun-2007 20:22:36
Elapsed time: 31 mins 27 secs
Priority: 10
FD Files Written: 2
SD Files Written: 2
FD Bytes Written: 7,730,344,766 (7.730 GB)
SD Bytes Written: 7,730,345,032 (7.730 GB)
Rate: 4096.6 KB/s
Software Compression: 42.5 %
Volume name(s): xxxxStateTuesday
Volume Session Id: 8
Volume Session Time: 1181551527
Last Volume Bytes: 7,739,588,003 (7.739 GB)
Non-fatal FD errors: 0
SD Errors: 0
FD termination status: OK
SD termination status: OK
Termination: Backup OK

13-Jun 01:01 xxxx02-dir: Bacula 1.38.11 (28Jun06): 13-Jun-2007 01:01:16
JobId: 1245
Job: xxxxMailTuesday.2007-06-12_19.00.05
Backup Level: Full
Client: "xxxx-fd" Windows Server 2003,MVS,NT 5.2.3790
FileSet: "xxxxMailSet" 2006-09-13 19:00:49
Pool: "xxxxTuesdayMail"
Storage: "FilexxxxMailTuesdayStorage"
Scheduled time: 12-Jun-2007 19:00:04
Start time: 12-Jun-2007 23:12:09
End time: 13-Jun-2007 01:01:16
Elapsed time: 1 hour 49 mins 7 secs
Priority: 10
FD Files Written: 2
SD Files Written: 2
FD Bytes Written: 32,960,720,384 (32.96 GB)
SD Bytes Written: 32,960,720,661 (32.96 GB)
Rate: 5034.5 KB/s
Software Compression: 26.2 %
Volume name(s): xxxxMailTuesday
Volume Session Id: 13
Volume Session Time: 1181551527
Last Volume Bytes: 32,995,490,984 (32.99 GB)
Non-fatal FD errors: 0
SD Errors: 0
FD termination status: OK
SD termination status: OK
Termination: Backup OK

Display posts from previous:
Reply to topic Page 1 of 1
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
  


Magic SEO URL for phpBB