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. Depending on your country and business requirements, you can create a customized calendar.
The scheduling of all SEP sesam tasks is controlled and executed by SEPuler, which acts as an electronic event calendar and assistant performing all SEP sesam data protection events. SEPuler is a permanently active background routine (daemon) that is 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.
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.
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.
A schedule defines the recurrence of an event and can be executed in minutes, hours, days, months or years. It can be set up to start at regular intervals or to run only once. A schedule can be used for any number of events and the events of a particular task (backup, restore, migration, etc.) can be configured in multiple schedules.
Note that all schedules and related jobs are configured and run in the SEP sesam Server's time zone.
To configure an event, from Main Selection -> Scheduling -> Schedules right-click the schedule for which you want to create a new event and select the relevant event. You can create any of the following events:
- Creating a backup event
- Creating a restore event
- Creating a migration event
- Creating a media event
- Creating a command event
You can also create some special events:
- Creating a blocking event only for the specified hours
- Creating an event to execute additional jobs on specified dates
- Creating an event to prevent the execution of scheduled jobs on certain dates
- Creating a Newday blocking event to block events on certain dates
For details, see Creating a Custom Calendar.
SEP sesam provides flexible scheduling features to customize how and when your events are processed. By using the User defined option of a schedule, you can create a calendar that is customized according to your country- or company-specific requirements.
For example, you can define a calendar with specific days on which you want to perform special job executions, such as backup and migration. It also provides the ability to define specific dates on which the scheduled jobs are prevented from running, allowing you to set up a custom calendar of public holiday dates for each year and linking events with blocking date to it to stop scheduled jobs from running during holidays.
You can create as many custom calendars as you need. A custom calendar can be defined for a limited period of time, e.g., for one year if the holidays and other specific dates are entered only for the next year, for several years, or for an unlimited time.
Note that you can simply modify, import, export, and delete your custom calendar. For details, see Creating a Custom Calendar.
|In v. ≥ 5.0.0 Jaglion, you can automate the process of backing up multiple VMs by automatically generating tasks for VMs that are connected to the same host; you can also automatically create clients for VMs to which the created tasks and ACLs can be assigned. It is recommended to use these features when a new hypervisor is added and many new VMs need to be backed up. For details, see Automating Backup Process.