4 4 3 Beefalo:Schedules

From SEPsesam
Revision as of 21:31, 13 June 2019 by Sta (talk | contribs) (Beefalo-related update in progress.)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
Other languages:
Deutsch • ‎English
<<<Back
Scheduling
User Manual
Next>>>
Events


Draft.png WORK IN PROGRESS
This page is a draft. Treat the information on this page with caution as it may be incomplete.


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 Beefalo.jpg

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.

You can also use Without Schedule option, which 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 Beefalo.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 Beefalo.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.

You can create a new schedule from Main Selection -> Scheduling -> Schedules -> New Schedule. For details, see Creating a Schedule.

Schedule properties

Clicking Properties or double-clicking the schedule displays all details of the selected schedule. You can also edit the existing schedule settings.

Schedule Beefalo.jpg

  • Execution off: Execution is enabled by default. Use this option to disable the schedule. If you select it 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, monthly, yearly, or as defined (custom calendar).
    • 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. For details, see Creating Custom calendar.
  • 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. For details, see Creating a Backup Event.

The button New Backup Event opens the following window:

New backup event Beefalo.jpg

  • Name: You can change the displayed backup event name.

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.

Object

  • Task: Select the task to which you want to link this event.
  • Task group: Select the task group (instead of task) to which you want to link this event.

Parameter

  • Backup level: Select between the backup levels FULL, DIFF, INC, COPY.
  • Hot/Cold backup: You can set execution parameter, e.g., for database backups.
  • Media Pool: Select the target media pool to which the data will be backed up. If you want to enable source-side deduplication, you have to select the media pool which is combined with an Si3 deduplication store backend.
  • SEP Si3 Source Side Deduplication: 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 SEP Si3 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.): Optionally, specify the drive number of the drive that will be used to write the data.
  • 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.


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