Source:Special Schedules
Special Schedules
In version 3.4.1.x or higher it's possible to define 'Blocking Date' schedules which will block execution of other schedules related to the same object where the blocking is done only during the 'starting time window' of the 'Blocking Date' schedule with higher priority.
To enable this the Sesam database table defaults must contain an entry "suppress_with_timerange" with value "yes". Without this entry the blocking is done for the whole sesam day. (since sm_sepul_event revision 1.188)
This value may be inserted with:
sm_db "INSERT INTO defaults (key,user_name,value) VALUES ('suppress_with_timerange','sesam','yes');"
Example:
An hourly scheduled backup for ORACLE with command event 'oracle_XE_full' and Priority '1' is already defined.
To disallow execution during 12:00 till 14:00 o'clock another schedule, e.g. block_ORACLE_1200-1400, must be defined with
- weekly execution, from Monday till Friday
- starting time 12:00 o'clock, duration 2 hours.
This schedule, e.g. 'block_ORACLE_1200-1400' must be connected to the same command event, e.g. 'oracle_XE_full',
his priority must be higher then the other one, e.g. '2'
and the execution parameter 'Blocking Date' ('Sperrtermin') must be enabled.
When you want to use this function with a regular backup job keep in mind that the blocking event has to reference the same taskname as the backup event does.