Hi all,

Is it possible that, in version 5.2.5 (Ubuntu),


1)      An incremental job is started according to schedule, before a previous 
full run of the same job has finished?

2)      A nasty side effect when that happens is that the incremental job is 
bounced to full because "Prior failed job found in catalog. Upgrading to 
Full.", while there have been no errors?

I seem to be in that situation now.

The client has 'maximum concurrent jobs' set to 3, because the same client is 
used for backing up different NFS-mounted shares as separate jobs. Most of 
those are small, except for one, and that's that one that has the problem.

The normal schedule is either full or differential on Friday night, incremental 
on Monday through Thursday, and nothing on Saturday or Sunday.
Because many full jobs are scheduled for Friday and only a limited number run 
concurrently, it usually only really starts on Saturday morning.


The first overrun of Full into the next scheduled run was caused not by the job 
itself taking too long, but by a copy job that was copying that job from disk 
to tape, and that had to wait for a new blank tape for too long.
>From there on I think it took longer than 24 hours to complete because it ran 
>two schedules of the same job concurrently each time.
At least that's what the director and catalog report.

Fom Webacula:

Information from DB Catalog : List of Running Jobs

Id            Job Name           Status   Level     Errors    Client    Start 
Time
yy-mm-dd
28822    NAS-Elvis            Running               F             -             
 NAS       2015-04-29 11:29:48
28851    NAS-Elvis            Running               F             -             
 NAS       2015-04-29 20:06:00

Both are incremental jobs upgraded to Full because of a 'previous error' that 
never occurred.
I just canceled the later one to give the other time to finish before it's 
rescheduled again tonight at 20:06:00.


Besides that, there must be something else I have to find. I don't think it's 
normal that a backup of 600 GB from an NFS share to disk on another NFS share 
takes more than 20 hours, as the last 'normal' run last Saturday did (the 
physical machine the job is on is the SD itself, backing up an NFS share to 
another NFS share).

------------------------------------------------------------------------------
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@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to