Hi,
I'm currently testing 2.5.42 (svn as of Mar 24, I believe) and have
the following set in the defaults for all jobs:
Allow Duplicate Jobs = No
Allow Mixed Priority = Yes # doesn't apply as of now...
Max Run Sched Time = 3600 # 1 hour
Max Run Time = 1800 # 1/2 hour
Max Wait Time = 1200 # 20 min
All jobs are run every 15 minutes with different levels.
DIR config excerpts:
JobDefs {
Name = "DefaultJob"
Type = Backup
Level = Incremental
Client = gnom-fd
FileSet = "Full Set"
Schedule = "WeeklyCycle"
Storage = File
Messages = Standard
Pool = Default
Priority = 10
Allow Duplicate Jobs = No
Allow Mixed Priority = Yes
Max Run Sched Time = 3600
Max Run Time = 1800
Max Wait Time = 1200
}
With these settings, the scheduler queue display is incorrect. See here:
> *autom
> Turn on or off? off
> *time
> 29-Mär-2009 21:29:03
> *sta dir
> demo-dir Version: 2.5.42-b2 (16 March 2009) i686-pc-linux-gnu suse 11.1
> Daemon started 29-Mär009 21:28, 0 Jobs run since started.
DIR freshly started to make sure I didn't mess up anything earlier...
> Heap: heap=270,336 smbytes=64,080 max_bytes=64,633 bufs=356 max_bufs=358
>
> Scheduled Jobs:
> Level Type Pri Scheduled Name Volume
> ===================================================================================
No jobs scheduled before the BackupCatalog, i.e. at 21:30, 21:45,
22:00, etc.?!
> Full Backup 11 29-Mär009 23:10 BackupCatalog FIL0537
> Migrate 10 29-Mär009 23:25 MigratePhoenix
> Differential Backup 10 30-Mär009 00:00 Demo1 FIL0537
> Differential Backup 10 30-Mär009 00:00 DemoWin FIL0258
> Differential Backup 10 30-Mär009 00:00 Demo3 FIL0537
> Differential Backup 10 30-Mär009 00:00 Demo2 FIL0537
> Incremental Backup 10 30-Mär009 00:15 Demo1 FIL0537
> Incremental Backup 10 30-Mär009 00:15 Demo2 FIL0537
> Incremental Backup 10 30-Mär009 00:15 Demo3 FIL0537
> Incremental Backup 10 30-Mär009 00:15 DemoWin FIL0258
> Full Backup 10 30-Mär009 00:30 Demo1 FIL0537
> Full Backup 10 30-Mär009 00:30 Demo2 FIL0537
> Full Backup 10 30-Mär009 00:30 Demo3 FIL0537
> Full Backup 10 30-Mär009 00:30 DemoWin FIL0258
> Incremental Backup 10 30-Mär009 00:45 Demo1 FIL0537
> Incremental Backup 10 30-Mär009 00:45 Demo2 FIL0537
> Incremental Backup 10 30-Mär009 00:45 Demo3 FIL0537
> Incremental Backup 10 30-Mär009 00:45 DemoWin FIL0258
> Migrate 10 30-Mär009 05:23 MigratePhoenix
> Migrate 10 30-Mär009 11:23 MigratePhoenix
> Migrate 10 30-Mär009 17:23 MigratePhoenix
> ====
>
> Running Jobs:
> Console connected at 29-Mär009 21:28
> Console connected at 29-Mär009 21:28
> No Jobs running.
> ====
>
> Terminated Jobs:
> JobId Level Files Bytes Status Finished Name
> ====================================================================
> 2596 Incr 10 255.5 K OK 29-Mär009 21:20
> DemoWin.2009-03-29_17
> 2595 Full 10 255.5 K OK 29-Mär009 21:20
> MigratePhoenix.2009-03-29_17
> 2659 Incr 0 0 OK 29-Mär009 21:20
> Demo3.2009-03-29_21
> 2658 Incr 0 0 OK 29-Mär009 21:20
> Demo2.2009-03-29_21
> 2656 Diff 0 0 Error 29-Mär009 21:20
> DemoWin.2009-03-29_21
> 2657 Incr 64 2.447 K OK 29-Mär009 21:20
> Demo1.2009-03-29_21
> 2660 Incr 0 0 OK 29-Mär009 21:21
> DemoWin.2009-03-29_21
> 2600 Full 18 262.5 K OK 29-Mär009 21:21
> DemoWin.2009-03-29_17
> 2604 Incr 0 0 OK 29-Mär009 21:22
> DemoWin.2009-03-29_17
> 2608 Diff 0 0 OK 29-Mär009 21:22
> DemoWin.2009-03-29_18
>
> ====
Wait a bit...
> *time
> 29-Mär-2009 21:30:40
> You have messages.
> *sta dir
> demo-dir Version: 2.5.42-b2 (16 March 2009) i686-pc-linux-gnu suse 11.1
> Daemon started 29-Mär009 21:28, 1 Job run since started.
> Heap: heap=389,120 smbytes=113,893 max_bytes=124,942 bufs=514 max_bufs=549
>
> Scheduled Jobs:
> Level Type Pri Scheduled Name Volume
> ===================================================================================
Still nothing new scheduled.
> Full Backup 11 29-Mär009 23:10 BackupCatalog FIL0537
> Migrate 10 29-Mär009 23:25 MigratePhoenix
> Differential Backup 10 30-Mär009 00:00 Demo1 FIL0537
> Differential Backup 10 30-Mär009 00:00 DemoWin FIL0258
> Differential Backup 10 30-Mär009 00:00 Demo3 FIL0537
> Differential Backup 10 30-Mär009 00:00 Demo2 FIL0537
> Incremental Backup 10 30-Mär009 00:15 Demo1 FIL0537
> Incremental Backup 10 30-Mär009 00:15 Demo2 FIL0537
> Incremental Backup 10 30-Mär009 00:15 Demo3 FIL0537
> Incremental Backup 10 30-Mär009 00:15 DemoWin FIL0258
> Full Backup 10 30-Mär009 00:30 Demo1 FIL0537
> Full Backup 10 30-Mär009 00:30 Demo2 FIL0537
> Full Backup 10 30-Mär009 00:30 Demo3 FIL0537
> Full Backup 10 30-Mär009 00:30 DemoWin FIL0258
> Incremental Backup 10 30-Mär009 00:45 Demo1 FIL0537
> Incremental Backup 10 30-Mär009 00:45 Demo2 FIL0537
> Incremental Backup 10 30-Mär009 00:45 Demo3 FIL0537
> Incremental Backup 10 30-Mär009 00:45 DemoWin FIL0258
> Migrate 10 30-Mär009 05:23 MigratePhoenix
> Migrate 10 30-Mär009 11:23 MigratePhoenix
> Migrate 10 30-Mär009 17:23 MigratePhoenix
> ====
>
But:
> Running Jobs:
> Console connected at 29-Mär009 21:28
> Console connected at 29-Mär009 21:28
> JobId Level Name Status
> ======================================================================
> 2662 Full Demo2.2009-03-29_21.30.00.05 is running
> 2663 Full Demo3.2009-03-29_21.30.00.06 is running
> 2664 Full DemoWin.2009-03-29_21.30.00.07 is waiting on Storage File
> ====
>
> Terminated Jobs:
> JobId Level Files Bytes Status Finished Name
> ====================================================================
> 2595 Full 10 255.5 K OK 29-Mär009 21:20
> MigratePhoenix.2009-03-29_17
> 2659 Incr 0 0 OK 29-Mär009 21:20
> Demo3.2009-03-29_21
> 2658 Incr 0 0 OK 29-Mär009 21:20
> Demo2.2009-03-29_21
> 2656 Diff 0 0 Error 29-Mär009 21:20
> DemoWin.2009-03-29_21
> 2657 Incr 64 2.447 K OK 29-Mär009 21:20
> Demo1.2009-03-29_21
> 2660 Incr 0 0 OK 29-Mär009 21:21
> DemoWin.2009-03-29_21
> 2600 Full 18 262.5 K OK 29-Mär009 21:21
> DemoWin.2009-03-29_17
> 2604 Incr 0 0 OK 29-Mär009 21:22
> DemoWin.2009-03-29_17
> 2608 Diff 0 0 OK 29-Mär009 21:22
> DemoWin.2009-03-29_18
> 2661 Full 1,017 65.49 K OK 29-Mär009 21:30
> Demo1.2009-03-29_21
And this one is already finished...
And I did not start any jobs manually, by the way :-)
So, for some reason, something breaks the scheduler display, but the
scheduler itself works correctly.
This might be related to the above mentioned settings as I did not
observe this behaviour before I inserted that to the job defaults.
Can anybody confirm this?
Arno
>
> ====
> *quit
--
Arno Lehmann
IT-Service Lehmann
Sandstr. 6, 49080 Osnabrück
www.its-lehmann.de
------------------------------------------------------------------------------
_______________________________________________
Bacula-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-devel
