- 1 Overview
- 2 Activating follow-up events
- 3 Configuring follow-up events
- 4 Testing events on the command line
- 5 Follow-up examples
- 5.1 Verify save set after the backup
- 5.2 Migrate or replicate save set after the backup
- 5.3 Migrate save set after the backup and delete it after successful migration
- 5.4 Start single backup task after the backup
- 5.5 Start backup group after the backup
- 5.6 Start event on special drive
- 5.7 Send notification after the backup, migration or restore
- 6 See also
As of SEP sesam version ≥ 4.4.3, you can configure follow-up events that are triggered on the SEP sesam Server once the initial event is completed. You can set up migration, save set verify and other actions to be triggered immediately after backup or other event is completed.
Follow-up events allow you to start actions based on events happening on the backup server.
The following event chains can be combined:
- Start migration after the backup or task group is successfully completed.
- Start single backup task or backup group after the backup, task group or migration is successfully completed.
- Start save set verify after the backup or task group is successfully completed.
Activating follow-up events
To activate the follow-up events, enter the following commands in the shell/cmd.
c:\program files\sepsesam\var\ini\sm_prof.bat sm_glbv w gv_use_follow_up 1 sm_db "update defaults set value='1' where key ='enable_gui_follow_up'"
source /var/opt/sesam/var/ini/sesam2000.profile sm_glbv w gv_use_follow_up 1 sm_db "update defaults set value='1' where key ='enable_gui_follow_up'"
Event-based actions are logged within:
|If you need troubleshooting assistance, send this log file with a description of your issue to SEP sesam support.|
Configuring follow-up events
A follow-up event can be configured in the backup event properties: Main Selection -> Scheduling -> Schedules -> New backup event. See Creating a backup event for details.
In the Follow up field you can configure events that are started on the SEP sesam Server once the initial event is completed.
|A follow-up event is always configured for the schedule that should trigger the event.|
Testing events on the command line
Backup events can be tested on the command line before configuration. As initial start of a backup the command line tool sm_cmd is used.
The notation of the command has a special syntax:
sm_cmd <cmd_command> @- "<event_definition>"
The following example shows an sm_cmd command which then automatically starts a follow-up event to backup a task group:
sm_cmd backup -m MEDIAPOOL -j TEST_BACKUP -@ "sm_event backup task SESAM_BACKUP - -m MEDIAPOOL -"
See SEP sesam Command Line Interface for details.
In the following examples the elements within the angle brackets < > indicate that the enclosed element is mandatory and must be appropriately replaced by parameter or actual name. Do not type the angle brackets in the command line. Every follow-up command also requires the ending hyphen -. All specified tasks and migration tasks have to be configured in the GUI before the follow-up event is started. For example, first you configure a migration task and then you set up the event migrate save set after the backup.
Verify save set after the backup
|Verifying save sets is currently only available for Path backup type.|
To verify the backup, use the following command:
sm_event verify saveset -
After the backup is finished, a restore is started and data is being verified. No data is written to the target system. To view the status of your verification job, go to the Main selection -> Job state -> Restore and check the verification status.
Migrate or replicate save set after the backup
To start an already configured migration or replication task as a backup follow-up, specify the following:
sm_event migrate saveset <migration_task> -
Replace <migration_task> with the actual name of the migration (or replication) task, as it is displayed in Tasks -> Migration Tasks (or alternatively in Tasks -> Si3 replication).
Migrate save set after the backup and delete it after successful migration
First, create a migration task. Once the required task is created, you can set it up as a follow-up event after the backup is completed by entering the following command:
sm_event migrate saveset <migration_task> - -r 1 -
The additional option "-r 1" will be passed to the migration task and the save set will be deleted after successful migration.
Replace <migration_task> with the actual name of the migration task, as it is displayed in Tasks -> Migration Tasks.
|This follow-up event can only be used for migration, not for replication.|
Start single backup task after the backup
To start another backup task after the scheduled backup is finished, specify the following:
sm_event backup task <task_name> - -m <target_pool> -
Replace <task_name> with the name of the backup task and <target_pool> with the target media pool the data should be saved to.
Start backup group after the backup
Sometimes you need to start a backup group after the backup is finished:
sm_event backup group <task_group> - -m <target_pool> -l BACKUP-LEVEL -
Replace <task_group> with the name of the backup group and <target_pool> with the target media pool the data should be saved to. With backup-level you can define F/C/D/I.
Start event on special drive
To start the target event on a different drive, specify the option -d:
sm_event backup task <task_name> - -m <target_pool> -d <drive_num> -
Send notification after the backup, migration or restore
You can trigger a notification after the backup, migration or restore event is finished.
sm_event notify result <username> -
In the example below, the notification will be send to the username configured as backup within Configuration -> E-Mail Settings.
sm_event notify result backup -