5 2 0:Immediate Start in the GUI

Overview

Action Immediate Start enables you to start a SEP sesam task manually as a single, non-recurring event. In the GUI, it can be accessed from the menu bar -> Activities -> Immediate Start, where you can select the type of task you want to start immediately.

	Note
	In v. ≥ 5.0.0. Jaglion, the operations and options available after login may also differ depending on the user type. Other UI display restrictions may depend on the custom roles with specific permissions and the UI mode. For details, see About Authentication and Authorization and User Roles and Permissions.

Immediate Start: Backup

Screenshots

Settings tab

• Task: Selection of a previously configured task.
• Task group: Selection of a previously configured task group.
• Task type: Selection of a previously configured task type, e.g., Path, Hyper-V, SAP Hana, etc.
• Backup level: Displays the backup level (FULL, DIFF, INCR, COPY).
• Hot (online)/Cold (offline) backup: Special backup parameters, applicable for VMs and databases.
• Media pool: Selection of a media pool that will be used for this backup.
• Drive group: This inactive field displays the name of the drive group, which is defined for the specified media pool. The backup is executed automatically on a drive from the assigned drive group.
• Drive: You can define which drive handles the backup job for drive groups with several drives. If no drive is selected, SEP sesam selects the available drive based on criteria for load sharing.
• Interface: If multiple network connections are available, the hostname for the backup source (if necessary, the network interface) is defined.
• Migration task: From the drop-down list, you can select available migration task for the migration.

Execution Time tab (formerly Start Time)

• Start time: Instead of starting your backup immediately, you can specify the start time by entering the desired date and time.
• Start time frame: You can specify the maximum start time allowed (the time an event can be in the queue) in days and/or hours. The actual start time of an event depends on the processor load of the system. At the start time of an event, every event is forwarded into the queue, where it might wait until jobs with a higher priority have finished. For jobs with the same priority, the FIFO rule (first in first out) applies. If the event cannot be executed within this time frame, it is not executed at all.
• Cancel execution after (Stop task if it runs longer than): You can specify the amount of time (days and/or hours) after the event's scheduled start time at which the event should be canceled.
• Stop task at: Additionally, you can define the exact date and time when the task should be stopped.
• Follow up: You can specify the follow-up event to trigger the predefined event on the SEP sesam Server once the backup is complete. For details, see Follow-up Events.

Screenshots

By clicking the Start button, the backup process is picked up by SEPuler that initiates the execution of the event immediately or (if the time is specified) at the desired start time.

Immediate Start: Restore

From the list of the restored tasks select the relevant restore task.

Screenshots

Once you have selected the task, the web-based Restore Assistant opens with this task ready for restore. For details, see Standard Restore Procedure.

Immediate Start: Migration

The migration task window displays the tabs Settings and Start time.

Screenshots

Select the desired migration task from the Task name drop-down list. The selected migration task is displayed with its parameters. You can modify the migration destination and filter settings. By clicking the Start button, the changes of the migration task are saved and the migration is started. For details on migration options, see Creating a Migration Event.

Immediate Start: Replication

In the replication task window (v. ≥ 5.0.0 Jaglion), the tabs Settings and Execution Time are displayed.

Screenshots

Select the desired replication task from the Task name drop-down list. The task is displayed with its parameters. By clicking the Start button, the changes of the replication task are saved and replication starts. For details, see Creating a Replication Event.

Immediate Start: Media Action

Media events can be activated by SEPuler (timetable) as user-defined events, media EOM or backup itself. For details on configuring media events, see Creating a Media Event.

Screenshots

Settings tab

Sequence control:

• Priority: Event priority is used for resolving scheduling conflicts. Priorities can be assigned to schedules, from the lowest (1, default) to the highest (99). For details, see Event Priority.
• Blocking date: A blocking event is any type of event with a higher priority that obstructs another event. A blocking event affects other events with the same name only if the schedules overlap. For details, see Blocking Events.

You can choose from four different media actions:

• Initialize: Initializing the media prepares it for use with SEP sesam. Initialization process rewrites the tape label. All existing information on the tape is deleted. A media event prepares the media of the selected pool for use for data backup.
• Readability check: The readability check tests the backup data readability. During the check, the data on media is read block by block, and the structure of the tape is checked and recorded. For details, see Configuring a Readability Check.
• Archive adjustment: An archive adjustment scans the media in the selected loader to update the SEP sesam information about the media in the loader. It is required when the media in the loader have changed, for example, when new media are added. For details, see Setting up Archive Adjustment.
• Close tape: Closing the tape means that EOM (End of Media) is created on the tape regardless whether it is full or not. Such a tape can no longer be used to store data.

Parameter:

• Media pool: Defines the media pool that will be used for the media event.
• Drive: Optionally, you can define a specific drive for the event execution. If no drive is selected, SEP sesam Server automatically selects one of the available drives.
• Media: Optionally, you can select the medium you want to use. If no medium is selected, SEP sesam Server automatically assigns the medium with the oldest EOL. For details on the GET_OLDEST strategy, see Media Strategy.
• Drive group: Displays the name of the drive group that belongs to the media pool.
• Loader: Optionally, you can select the loader (tape library) whose content you want to synchronize with the SEP sesam database.
• Options: If required, set additional execution options.

Execution Time (Start time) tab

• Execution Time: Instead of starting your media event immediately, you can specify the start time by entering the desired date and time.
• Start time frame: You can specify the maximum start time allowed (the amount of time an event can be in the queue) in days and/or hours. The actual start time of an event depends on the processor load of the system. At the starting time of the event, every event is forwarded to the queue, where it might wait until jobs with higher priority finish. For jobs with the same priority, the FIFO rule (first in first out) applies. If the event cannot be executed within this specified time frame, it will not be executed at all.
• Cancel execution after (Stop task if it runs longer than): You can set the amount of time (days and/or hours) after the event's scheduled start time at which the event will be canceled.
• Cancel execution at (Stop task at): Additionally, you can define the exact date and time when the task should be stopped.
• Follow up: You can specify the follow-up event to trigger the predefined event on the SEP sesam Server once the media event is complete. For details, see Follow-up Events.

Immediate Start: Command

Starts a preconfigured command event by inserting it into the calendar with the actual time. Events initiated with the Immediate start command from the GUI or command line are listed in the calendar as non-recurring events. For details on command event configuration, see Creating a Command Event.

Screenshots

Settings tab

• Name: Use the Select button to select a relevant command from the drop-down list of already configured commands. Select the command and click OK.
• Client: Select the hostname of the computer on which the command is going to be executed.
• User: Specify a user with privileges to run the command on the client. This applies only to Unix systems, on Windows the command is executed with the rights required to run the SEP sesam service. For information on access restrictions for command events, see section Access limitation of command events.
• Retention time: Optionally, specify for how long (in days) the command event results and logs will be kept. The default is 30 days.
• Preview: The selected command is displayed.

Execution Time (Start time) tab

• Start time: Instead of starting your command event immediately, you can specify the start time by entering the desired date and time.
• Start time frame: You can specify the maximum start time allowed (the amount of time an event can be in the queue) in days and/or hours. The actual event startup depends on the processor load of the system. At the starting time of the event, every event is forwarded to the queue, where it might wait until jobs with a higher priority are finish. For jobs with the same priority, the FIFO rule (first in first out) applies. If the event cannot be executed within this specified time frame, it will not be executed at all.
• Follow up: You can specify the follow-up event to trigger the predefined event on the SEP sesam Server once the command event is completed. For details, see Follow-up Events.

Access limitation of command events

• UNIX: External commands are executed only if the user and the command are inserted into the file /etc/sesam_cmdusers.allow on the client computer. Therefore, the template from path <SESAM-BIN>/skel/templates may need to be copied to /etc and adapted accordingly. Format: user command|* (* = all commands can be started)

• Windows: External commands are only executed if the user and the command are inserted into the registry on the client computer under the key //HKLM/SOFTWARE/SEP Elektronik GmbH/sesam/CommandEvents/<user>/<command>.

Command	Execution
*	all instructions
cmd /c	all DOS instructions (dir, etc.)
ping	only command ping

See also

Immediate Start of SEP sesam Tasks — Monitoring in Web UI — Managing SEP sesam Events

Copyright © SEP GmbH (formerly SEP AG) 1999-2025. 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 GmbH. When compiling and designing user documentation SEP GmbH uses great diligence and attempts to deliver accurate and correct information. However, SEP GmbH cannot issue a guarantee for the contents of this manual.