Special Schedules

From SEPsesam
Jump to: navigation, search
Other languages:
Deutsch • ‎English

Copyright © SEP AG 1999-2020. All rights reserved.

Any form of reproduction of the contents or parts of this manual is allowed only with the express written permission from SEP AG. When compiling and designing user documentation SEP AG uses great diligence and attempts to deliver accurate and correct information. However, SEP AG cannot issue a guarantee for the contents of this manual.

Docs latest icon.png Welcome to the latest SEP sesam documentation version 4.4.3/4.4.3 Beefalo V2. For previous documentation version(s), check documentation archive.


SEP sesam establishes schedules as a frame, to which you link different events, such as backup, migration, replication etc. A schedule defines the recurrence of an event and may be executed in minutes, hours, days, months or years. All schedules and related jobs are configured and run in the time zone of the SEP sesam Server. For more details on scheduling concepts, see SEPuler – an event calendar.

SEP sesam also provides options to prevent activation of individual events on specific days, such as holidays, and on certain hours:

  1. From v. 4.4.3 onwards, SEP sesam scheduling includes new User defined option which enables you to quickly and simply create a customized calendar, which enables you to set the dates on which you would like to run additional jobs or prevent specific jobs to be run. For details, see Creating Custom Calendar.
  2. When your custom calendar is set, create the desired event for it. Use the option Blocking date in the Event properties to prevent a job from being run. Such event is called a blocking event: any type of event with a higher priority that obstructs another event of the same type and prevents it from being activated. It can be specified to prevent activation of a specified event on specific days or hours. The latter example is given below. For general details on how to configure a schedule and link an event to it, see Standard Backup Procedure, step 2 and 3.

Configuring a blocking event only for the specified hours

A blocking event is created during configuration of an event or later in the event properties. It is used to prevent the activation of certain events on specific days (e.g., end of year, holidays). It may also be configured to prevent the execution of other jobs related to the same object only within the specified hours.

Information sign.png Note
  • By default, a blocking event suppresses any job with the same task name at respective (SEP sesam backup day) day, regardless of whether it is scheduled to be run before, during or after the blocking event.

If you want to set the blocking event to be applied only within the specified hours, you must perform some specific steps. If you are configuring a blocking event that is valid for a whole SEP sesam backup day (default), see Creating an Event.

To enable the blocking event within the specified hours, the SEP sesam database table defaults must contain an entry suppress_with_timerange with value yes. Without this entry the blocking event prevents related jobs to be activated for the whole sesam day!

  1. Set a SEP sesam profile as described in FAQ: What happens when I set a profile.
  2. Once you set the profile, use the command line to insert the following to SEP sesam database:
  3. sm_db "INSERT INTO defaults (key,user_name,value) VALUES ('suppress_with_timerange','sesam','yes');"
  4. The following scenario presumes that you have already defined an hourly-scheduled backup for ORACLE with command event Oracle all and event priority 1 (default). Now you want to disallow execution from noon till 2 p.m. Therefore you need to create another schedule, e.g., block_ORACLE_1200-1400. For details, see Creating a Schedule. In this schedule, you specify recurrence as:
    • weekly execution, from Monday till Friday
    • starting time 12:00 o'clock, duration 2 hours
  5. Blocking schedule execution Beefalo V2.jpg

  6. You must connect your newly created schedule, in our example block_ORACLE_1200-1400, to the same command event as mentioned above, e.g., Oracle_all (right-click the schedule and select New Command Event). Browse for the existing event (e.g., Oracle_all) and set the priority to a higher value. Note that this event's priority must be higher than the priority of the linked event. Then enable the Blocking date option.
  7. Blocking schedule execution params Beefalo V2.jpg

If you want to use this function with a regular backup job, keep in mind that the blocking event has to reference the same task name as the backup event does.