Schedules 4.4

From SEPsesam
Jump to: navigation, search
Other languages:
Deutsch • ‎English
<<<Back
Scheduling
User Manual
Next>>>
Events


Schedules overview

SEP sesam establishes schedules as a frame, to which you link different events, such as backup, migration, replication etc. Schedules always contain one predefined task: a NEWDAY schedule. Linked to it is a NEWDAY event which is used by SEP sesam to reorder its database, enable undisturbed activity of the SEP sesam processes as well as to define a new backup day.

Do not deactivate a NEWDAY event or delete a NEWDAY schedule, because this will cause SEP sesam to stop working properly! For details, see NEWDAY event.

A schedule defines the recurrence of an event and may be executed in minutes, hours, days, months or years. It can be set up to start periodically or to be executed just once. It can be used for any number of events, and a particular task (backup, restore, migration, etc.) can have events in several schedules. All schedules and related jobs are configured and run in the time zone of the SEP sesam Server.

Schedules overview 4.4.png

This window shows an overview of the configured schedules and related events. By using toolbar buttons you can configure the chronology of all processes in SEP sesam. You can create a new schedule or edit an existing one. Then you create a new event for the specific schedule and define its job. The job is run at specified time and, if defined as recurring, executed at specified time interval.

As of 4.4.3 Grolar, a new option Without Schedule is available under the Schedules.

Events without schedule.jpg


This option is available, if you set the value for enable_gui_events_without_schedule in the Defaults window (Configuration -> Defaults -> Settings tab) to 1 manually.

Defaults without schedules.jpg


It shows all backup events which are not assigned to a schedule due to the following possible reasons:

  • Events were deliberately created without a schedule for external backups, such as SAP HANA, where the external applications manage the backup scheduling.
  • Events were first linked to a schedule and then disconnected from it by opening the event and selecting the option Without Schedule, as shown in the screenshot below.
  • Changing events.jpg


Information sign.png Note
You should only delete events without a schedule if you are sure that they will not be used for an external backup.

Create new schedule (schedule properties)

The options for creating a SEP sesam schedule differ slightly depending on your SEP sesam version. Refer to the relevant version-specific information below. Version 4.4.3 provides a few additional options such as user-defined dates (custom calendar). For details on its usage, see Creating Custom Calendar.

Schedule v.4.4.2
Schedule 4 4 2.jpg


Name 
The name of the schedule.
Execution 
Enabled by default. Use this option to activate or disable the schedule. If set to No (disabled), the schedule will still be displayed as shaded in the list of schedules, but the related jobs will not run.
Cycle 
Configure the intervals for scheduled jobs. Jobs can occur once or recur from every day to every year.
once 
no repetition, single run
daily 
repetition in days, hours or minutes
weekly
repetition in weeks or weekdays
monthly 
repetition on absolute or relative dates: 1st, 2nd, ... or Mon, Tue, ...
yearly 
repetition on absolute or relative dates
Period of validity 
The time range of the schedule. Clicking the arrow displays a calendar.
Begin 
Start time of the repetition cycle. The schedule is only valid from the specified date. There can be no execution prior to this date.
End 
Set the validity of the schedule. If the schedule should only be valid for a limited period of time, e.g., until the end of the year, select the End checkbox and enter the date of its suspension. By default, this option is disabled and the schedule will be repeated in perpetuity.
Start time frame
The start time of the events linked to the schedule.
Start 
Designated start time of the event. The actual start time depends on the processor load of the system. See below option Duration.
Duration 
The time frame for the allowed actual start specified in days and/or hours (the amount of time an event can be in the queue). Actual start of event depends on the processor load and event priority. At schedule's designated start (see above option), every event is forwarded into the queue where it waits to be processed according to its priority. If execution is not possible within the specified duration time, the event will not be started.
Schedule v. 4.4.3
Schedule-4 4 3.jpg


Execution 
Enabled by default. Use this option to activate or disable the schedule. If you deselect the execution option, all events that are linked to this schedule will be deactivated. The schedule will still be displayed as shaded in the list of schedules, but the related jobs will not run.
Name 
The name of the schedule.
Start 
The start date and time for the schedule. By default, the current date is already entered in the first (date) field. In the next (hour) field, specify the start time <hh:mm> for a job to begin. The schedule will be activated on the specified date and time.
Expiration date
Set the validity of the schedule. If the schedule should only be valid for a limited period of time, e.g., until the end of the year, select the check box and enter the date of its suspension. Clicking the arrow displays a calendar. The schedule will be deleted after the Expiration date criterium is met.
By default, this option is disabled and the schedule will be repeated in perpetuity.
Selection of time intervals
Configure the time intervals for scheduled jobs. Jobs can occur once or recur daily or yearly.
once 
no repetition, single run
daily 
repetition in days, hours or minutes
weekly
repetition in weeks or weekdays
monthly 
repetition on absolute or relative dates: 1st/2nd... or Mon/Tue...
yearly 
repetition on absolute or relative dates
user defined 
option for setting up a custom calendar (available on SEP sesam v. 4.4.3 or higher, see creating custom calendar for details)
Advanced settings
Allows you to further refine your schedule.
Start time frame 
Select the check box if you want to specify maximum allowed actual startup time for your event (the amount of time an event can be in the queue). Specify the startup time in days and/or hours. The actual start time depends on the processor load of the system. At the starting time of the event, every event is forwarded to the queue, where it may have to wait until jobs with higher priorities are completed. For jobs with the same priority, the FIFO rule (first in first out) applies. If this option is set and the event cannot be executed within the specified time frame, it will not be executed at all.
Repeat task 
Select the check box if you want to repeat the event. Choose how often (in hours or minutes) the task should be repeated.
For a duration of 
Available if the Repeat task check box is selected. You can specify for how long should the event be repeated in days and/or hours.
Stop task if it runs longer than 
Select the check box if you want to set the amount of time (days and/or hours) following the event's scheduled start time after which the event will be cancelled.

New backup event

Backup event represents the last step in the process of configuring a backup job. First a backup task is created by selecting the task type and source. Next is a backup schedule, to which a backup event is linked.

The button New Backup Event opens the following window:

Backup task SSDD follow-up.jpg


Sequence Control 
Priority
The priority of your backup event. Default priority level is 1, which is the lowest priority (the highest is 99). The only exceptions are schedules with priority 0, which override all other priorities and are always executed. See Setting event priorities.
Blocking Date
The event only works within the prioritization concept as a block for other backups with the same name when schedules are overlapping. See Blocking events
Execution parameter 
Backup level
Select between the backup levels FULL, DIFF, INC, COPY
Hot/Cold backup
Execution parameter, e.g., for database backups
Media Pool
Target for the backup files. The exact label of the target medium is determined by the last prior media event or by the end of media (EOM)
Source Side Deduplication (≥4.4.3)
Introduced in SEP sesam version 4.4.3. Source-side deduplication (Si3S) requires a special license and a configured Si3 deduplication store. If the specified target media pool is combined with an Si3 deduplication store backend, the option Source Side Deduplication is shown and can be enabled
Drive Group 
(non-editable parameter) The drive group which is specified in the media pool. This field changes depending on the media pool selection
Drive (opt.)
Selection of a drive from the drive group mentioned above
Interface (opt.)
Selection of an alternate (configured) name of the TCP/IP-name of the client. This can be used to direct the data flow over a particular network connection in order to enable smooth execution of backups or restores without blocking another network activities.
Follow up (≥4.4.3)
Specification of events that are started on the SEP sesam Server once the initial event has completed. For details, see Follow-up Events.
Object 
Task 
Selection of the backup task related to this event
Task Group 
Selection of the backup task group related to this event

New restore event

The button New Restore Event opens the New restore event window with the Source tab selected. The first tab is Schedule. For more details, see Scheduling Restore.

New restore event – Source
Schedules 4.4 new restore event.png
Restore Task 
Selection of the restore task for which the event is going to be configured.
Fix Restore 
The restore will be executed exactly as defined by the restore task parameters using the same backup save set.
Selection
The restore task can be adjusted, for example to use the most recent backup save set. The following parameters can be set.
Parameters 
Saveset Limitation
indication of the time frame:
  • View: oldest selection: first, second, third, and so on
  • View: recent selection: last, penultimate, antepenultimate, and so on
backup day 
set a time frame for the exact backup day: from date ... to date
relative backup day 
from - to as a relative indication of the number of days that have passed since the backup. Negative numbers specify days in the past, while positive numbers specify days in the future.
Example : 2 weeks ago until now: from date = -14 to date = 0
FDI-Type 
Only save sets with the specified backup level will be used for restore: C (copy backup), F (full backup), D (differential backup), I (incremental backup).
Selection 
Provides the criteria according to which the backup save set to be restored is defined:
  • youngest: The most recent backup in the range of the relative backup day will be used for restore.
  • oldest: The eldest backup in the range of the relative backup day will be used for restore.
Media Preference 
Option to limit the media that are used as the restore source.
  • No limitation >> ' '
  • Regular medium before clone >> 'media'
  • Clone before regular medium >> 'clone'. If no clone is available this selection is ignored.
Tolerance 
Option to limit the media that are used for the restore.
  • Error if medium is not available (Default) >>
  • Only select available media >> 'available'
  • Only select available media that are eol-protected >> 'eol-protected'
Pool Restriction
Option to define that a save set must come from the specified media pool.
State 
Option to select the condition of the backup that will be used for restore:
  • successful or with warnings (default)
  • only successful
  • only with warnings
  • partially restorable (cancelled backups)
New restore event – Destination parameters
Schedule dest param tab.jpg


Sequence control 
Priority
The priority of your restore event. Default priority level is 1, which is the lowest priority (the highest is 99). The only exceptions are schedules with priority 0, which override all other priorities and are always executed. See Setting event priorities.
Blocking date
Used together with high priority for special events. See Blocking events.
Execution parameter 
Backup Type 
Backup-related parameter, not selectable for restore.
Hot/Cold Backup
Backup-related parameter, not selectable for restore.
Media Pool 
Backup-related parameter, not selectable for restore.
Drive Group 
Backup-related parameter, not selectable for restore.
Drive (opt.)
Selection of a drive from the drive group mentioned above.
Interface (opt.)
Backup-related parameter, not selectable for restore.
Follow up (≥4.4.3)
Specification of events that are started on the SEP sesam Server once the initial event has completed. For details, see Follow-up Events.

New migration event

As of SEP sesam v. 4.4.1, the procedure for configuring migration is changed (including GUI options). If you are using SEP sesam version < 4.4.1, see Configuring a migration job in SEP sesam versions lower than 4.4.1.

Migration event represents the last step in a migration job configuration. First a migration task is created by selecting the backed up data, source and target media pool. Next is a migration schedule, to which a migration event is linked.

Creating a migration event consists of reviewing migration task parameters and (optionally) setting event priority.

Migration event.jpg
Name
The name of the already configured migration task for which you want to create a migration job.
Priority
The priority of your migration event. Default priority level is 1, which is the lowest priority (the highest is 99). The only exceptions are schedules with priority 0, which override all other priorities and are always executed. See Setting event priorities.
Blocking date
Used together with high priority for special events. See Blocking events.
Parameter 
Media pool 
Pool
The name of the source media pool from which the data will be migrated, e.g., source_mediapool.
Drive
The drive number of the drive that will be used to read the data.
Destination 
Pool
The name of the target media pool to which the data will be migrated, e.g., target_mediapool.
Drive
The drive number of the drive that will be used to write the data.
Interface (opt.)
The network interface of the server through which the data transfer will be executed.
Time frame
The time frame of the backups that will be migrated specified by exact date or by relative backup date.
Filter 
Backup state
The backup completion status of the save sets you want to migrate: successfully or with warnings (default) or only successful. You cannot migrate the erroneous or only partially restorable save sets (containing data from cancelled backups).
Object
Select one of the following objects as a migration source.
Task
Only this task within the defined time frame is migrated.
Task group
Only the tasks of this task group within the defined time frame are migrated.
Client
Only the backups for this client within the defined time frame are migrated.
Backup level
The backup level relevant for migration (COPY, FULL, DIFF, INC).
Number of copies
How many times may the backed up data be migrated. Default is 0, meaning that data migration is unlimited.
Copy migrated save set again
A save set that has already been migrated can be migrated again.
Special filter
Start media
Select only one medium from the source media pool to be migrated.
Save set
Select only one save set to be migrated according to its ID.
Parallel migration 
The data can be migrated concurrently using multiple streams, thus improving the migration speed.

New media event

New media event.jpg
Succession Parameters  
Priority
The priority of your media event. Default priority level is 1, which is the lowest priority (the highest is 99). The only exceptions are schedules with priority 0, which override all other priorities and are always executed. See Setting event priorities.
Blocking date
The event is only in effect to block other media events for the pool when schedules overlap. See Blocking events.
Execution Parameters
Media Pool
Grouping of media by certain criteria (e.g., by types of media etc.)
Media Strategy
Indication of strategy OLD defined in the media pool
Drive Group
Selection of a drive group. Advantage: Sesam uses the drives belonging to a specific group independently
Drive
Selection of a certain drive
Tape Label
Selection of a pre-set tape label (tape identification) from the media pool
Spare Label
Selection of a pre-set spare label from the media pool

A media event from the point of its activation defines a specific media of a pool onto which the backups write their data. The contents of the media are deleted by the event.

If the expected media is unavailable at the start of a backup or end of media is reached during data-transfer then SEP sesam creates an internal media event which provides the next media for the backup. If no media event is configured in the calendar only the internal one is in effect at the EOM.

New command event

As of SEP sesam version 4.4.2, a new command event can be scheduled to run automatically. In the Main Selection -> Scheduling -> Schedules, select the schedule to which you would like to add a command event. Right-click it and select New command event.

New command event.png


Under the Sequence Control, the following options are available:

  • Priority: Define a priority of your command event. SEPuler always executes the schedules with higher priority first. Default priority level is 1, which is the lowest priority (the highest is 99). The only exception are the schedules with priority 0, which override all other priorities and are always executed. For details, see SEPuler.
  • Blocking date: This should be used together with high priority for special events. If checked, the blocking event will block events of the same type of a lower priority, ensuring the command event to be processed in case other command events are scheduled at the same time. See Blocking events.

Under the Parameter, define the following:

  • Name: Enter a name for the new event or search for and select an already existing command event. Searching for command opens a new window, where you can add a new command event, copy an already existing command event, select which existing command event you want to use again by clicking the Choose button, and delete an existing command event.
Select command.png


  • Client: Select a client, on which the command will be executed.
  • User: Enter the username of a user with sufficient access to execute the command on the client.
  • Command: Enter the complete command and parameters if necessary, e.g., eventlog.ps.
SEP Tip.png Tip

You can also access the configured commands from the menu bar -> Configuration -> Command.

Access restriction of command events

Command event starts any executable command on the chosen client. Since there are certain security issues to consider, not every command can be implemented by each user on specific clients. Without additional entries only commands entered in the system directory at <SESAM_ROOT>/bin/sesam are allowed. Within these commands, e.g., a shell script, any desired commands can be released to selected users.

If a command should be started from another directory before the regular backup starts, this must be entered/permitted at the target client.

UNIX

External commands are only executed when the username and the command are entered into the file /etc/sesam_cmdusers.allow on the client computer.

Format: 'user command|*  ( * = all commands is started with su - user)
Windows

External commands are only executed when the user and the command are entered in the registry on the client computer, in key text HKEY_LOCAL_MACHINE/SOFTWARE/SEP Elektronik GmbH/sesam/CommandEvents/user/command.

command           execution
*                 all commands
specific command  this command only
cmd /c            all DOS commands ( dir, etc. )
DOS-Command       this command only

Additionally on the client computer the entry CTRLD_Path=ID/bin/sesam;ID/bin/sms in the file ID/var/ini/sm.ini in section [CTRLD_Server] must be extended with the directories where the desired programs reside.

Registryentry.JPG

Information sign.png Note

Many errors are made when setting up the desired user permissions and allowed commands:

  • The necessary entries are not entered in the target client directories, not entered in the server or are entered incorrectly.
  • Instead of entering the command as a key it is entered as a character string.