5 1 0:About Scheduling

From SEPsesam
Revision as of 10:07, 7 April 2023 by Jus (talk | contribs) (Created page with "<languages /> <br/> {{Release-Apollon}} ==<translate><!--T:1--> Overview</translate>== {{Additional_Resources_Box|seeAlsoLinks=<nowiki /> *<translate><!--T:2--> Standard Backup Procedure *Automating Backup Process *Schedules *SEPuler – an event calendar *Special:MyLanguage/Standard_Rest...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Other languages:


Docs latest icon.png Welcome to the latest SEP sesam documentation version 5.1.0 Apollon. For previous documentation version(s), check documentation archive.


Overview


SEP sesam scheduling works by creating schedules and events to automate the execution of data protection tasks, such as backups. This ensures timely and consistent task execution with customized recurrence patterns.

SEPuler is the SEP sesam event scheduling service that tracks and manages schedules and events in the system, assigns events to the calendar, and coordinates and initiates event execution based on specified schedules.

How it works

The initial step is to create a data protection task, such as a backup task, which defines the scope and methodology of the backup. Following that, a schedule must be established to determine the desired repetition pattern. Lastly, an event for the task should be created and assigned to the schedule.

SEP sesam events can be single, non-recurring instances, or they can occur at regular intervals or repetitions within a schedule.

To demonstrate how scheduling works, a weekly backup is presented as an example. Begin by creating a schedule with a weekly recurrence pattern, specifying the desired interval. Next, create an event for the backup task and add it to this schedule. This associates the event with the schedule.

Once the event is added, SEPuler, the scheduling component of SEP sesam, logs the event in the calendar, capturing the scheduled time for execution. When the specified time arrives, SEPuler triggers the execution of the backup event, and the backup task is performed at the scheduled time.

After the event is executed, SEPuler determines the next occurrence based on the recurrence pattern specified in the schedule. Using our example, if the backup starts on January 1st, SEPuler will schedule the next occurrence for January 8th. This automated process continues, scheduling subsequent occurrences according to the defined interval.

Key features

SEP sesam's scheduling functionality offers flexibility and advanced features to enhance task management. Some notable capabilities are:

  • Multiple events of the same type can be linked to a schedule, streamlining the scheduling of similar operations.
  • A single task, such as a backup, migration, replication, media action, restore, or command, can have multiple events that can be associated with different schedules. This allows occurrences of the same task to be distributed across various schedules, fulfilling different timing requirements and recurrence patterns specific to that task.
  • Task group scheduling enables efficient automation and management of complex workflows. Tasks can be created and added to a group, ensuring automatic scheduling for streamlined execution of backup tasks. This feature is particularly useful for optimizing the backup process of virtualized environments.
  • Custom calendars can be created that are tailored to specific country or company requirements. These custom calendars are in the form of a schedule, and can be utilized to exclude scheduled jobs from running on designated dates, such as holidays, or to schedule additional jobs on selected dates. The ability to customize calendars adds a layer of control and adaptability to scheduling workflows.
  • Execution of a schedule can be deactivated. The schedule remains displayed in the list but appears shaded (grayed out), and related jobs do not run during the deactivated period.

SEPuler – SEP sesam event scheduler

The SEPuler, SEP sesam's scheduling component, picks up the entries defined within the schedule to initiate event execution. SEPuler is a continuously active background routine (daemon) responsible for executing SEP sesam data protection events. It manages all SEP sesam events, such as backup, migration, replication, restore, commands, different media events, and NEWDAY event.

When SEPuler detects a scheduled or manually triggered event, it initiates the execution of the corresponding task.

Once the event is started, SEPuler determines the next occurrence for recurring tasks and adds it to the task calendar. Events that are triggered in UI or command line with the ‘’Immediate start’’ option are entered in the calendar as non-recurring events.

When modifying a schedule, SEPuler automatically detects the modifications and applies the changes to all events associated with that schedule. As a result, all affected events are rescheduled accordingly.

Calendars

The calendar feature in SEP sesam serves as a central tool for scheduling and managing data protection tasks. The calendar is empty and does not contain any public holidays or other significant dates.

To customize the calendar and accommodate country-specific or company-specific requirements, a custom schedule in a form of a calendar can be created. Such custom calendars can include public holiday dates for each year, ensuring that backup or other critical operations are adjusted accordingly to avoid conflicts with these designated days. Additionally, users can incorporate other important dates that are relevant to their organization's workflow or specific project timelines.

Schedules

A schedule functions as a timetable that establishes the periodic behavior of an event, determining its regular and repetitive occurrence at specific intervals or time periods. It defines when the event is scheduled to occur and how frequently it should repeat. A schedule sets the recurrence pattern, ranging from minutes to hours, days, months, or even years. It can be configured for periodic execution or as a one-time occurrence.

By combining schedules with custom calendars, specialized schedules can be created, that include events designed to block or override other events on specific dates. This ensures that critical operations or maintenance tasks take priority and avoid conflicts with other scheduled events.

SEP sesam offers integration with external backup applications, allowing seamless coordination of data protection processes. Events can be created without schedules, to facilitate the management of external backups, such as SAP HANA, where the backup scheduling is handled by external applications and processes.

By default, SEP sesam includes the NEWDAY schedule, which contains the NEWDAY event. This schedule is necessary for optimizing the SEP sesam database and ensuring uninterrupted system activity. The NEWDAY event starts a new backup day, triggers the reordering of the database and performs essential maintenance tasks, enhancing the performance and reliability of SEP sesam processes.

Time zones

To ensure seamless coordination of tasks across different locations and time zones, backups, restores, and other critical operations are performed at the specified times in the appropriate time zone. For this purpose, all schedules and related jobs within SEP sesam are configured and executed based on the time zone of the SEP sesam Server.


See also

Standard Backup ProcedureAutomating Backup ProcessSchedulesSEPuler – an event calendarStandard Restore ProcedureScheduling Restore

Copyright © SEP AG 1999-2024. 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.