Archive:4 4 3:About Scheduling

From SEPsesam
Revision as of 10:35, 17 August 2017 by Sta (talk | contribs) (Marked this version for translation)
Other languages:

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.

Draft.png WORK IN PROGRESS
This article is in the initial stage and may be updated, replaced or deleted at any time. It is inappropriate to use this document as reference material as it is a work in progress and should be treated as such.
Docs latest icon.png Welcome to the latest SEP sesam documentation version 4.4.3. For previous documentation version(s), check Documentation archive.


Overview

SEP sesam schedules represent a framework for automating task execution. Different events, such as backup, migration, replication, restore, etc., can be linked to a schedule and configured to occur at a specified time. As of SEP sesam version 4.4.3, you can create a customized calendar.

SEPuler

The scheduling of all SEP sesam tasks is controlled and executed by the SEPuler, which acts as an electronic event calendar and assistant performing all SEP sesam data protection events. The SEPuler is a permanently active background routine (daemon), constantly searching for events to be executed. Backup, migration, replication, media event, command event, restore and NEWDAY event are all types of SEPuler events.

When SEPuler finds a scheduled task or manually triggered event, the execution of the corresponding program is initiated. All events in SEP sesam start from the SEPuler schedule, even if they are unique, non-recurring tasks.

Once the event has started, SEPuler will determine the next execution event for a cyclical task and rewrite the event to the task calendar. For example, if SEPuler starts a weekly backup on January 1, it will schedule a new weekly backup to occur on January 8. Events initiated with the Immediate start command from the GUI or command line are posted in the calendar as non-recurring events. For more details on SEPuler, see SEPuler - an event calendar.

NEWDAY schedule

Schedules always contain one predefined task: a NEWDAY schedule, which is linked to a NEWDAY event. SEP sesam uses the NEWDAY event to reorder its database, enable uninterrupted activity of the SEP sesam processes and 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 SEP sesam backup day – NEWDAY.

Events

SEP sesam Events/en

Calendar

Calendar/en

See also

Standard Backup ProcedureSchedulesSEPuler – an event calendarStandard Restore ProcedureScheduling Restore