Source:Creating a Migration Event-Jaglion

From SEPsesam
Revision as of 15:52, 13 March 2020 by Sta (talk | contribs) (Minor correction.)
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.

Docs latest icon.png Welcome to the latest SEP sesam documentation version 4.4.3/4.4.3 Beefalo V2. For previous documentation version(s), check documentation archive.


Overview

Migration event represents the last step in a migration job configuration. Creating a migration event consists of reviewing migration task parameters and (optionally) setting event priority.

Steps

  1. In the Main Selection -> Scheduling -> Schedules, select the schedule for which you want to create a new migration event, click New (or right-click the selected schedule) and click New Migration Event.
    Select new migration event Beefalo V2.jpg
  2. From the Task name drop-down list, select the name of the already configured migration task for which you want to create a migration job.
  3. In the Priority box, set up the Priority of your migration event. SEPuler always executes the schedules with higher priority first. Default priority level is 1, which is the lowest priority (the highest is 99). The only exception are the schedules with priority 0, which override all other priorities and are always executed. For details, see event priorities. You can also enable the Blocking date. This option should be used together with high priority for special events. If checked, the blocking event will block events of the same type of a lower priority, ensuring the backup to be processed in case other backups are scheduled at the same time. For details, see Blocking Events.
  4. The settings under the Media pool, Destination, Backup date, Backup state, Backup level, Object, and Special filter (previously Parameter and Filter) were defined when you have created the selected migration task. If required, you can modify these settings. The changes will only be applied to the current migration event and will not affect the original values set in the migration task. All changed values (in opposition to the settings in the migration task) are displayed in blue color when the event is re-opened. The check box Delete after successful migration sets the saveset EOL to the actual date and time of the successful migration. The source saveset is purgeable immediately after the migration. The saveset EOL has no effect for savesets stored on tape media.
    New migration event Beefalo.jpg
  5. Click OK to save your migration event.

To check the status of your migration job, go to the Main Selection -> Job State -> Migrations and Replications. Migration tasks are listed by name together with details on completion status, start and end time, and media pools used for the task.

As of 4.4.3 Beefalo V2, you can check the status and details of your migration jobs online by using new Web UI. For details, see SEP sesam Web UI.

SEP Tip.png Tip
As of version 4.4.3 Grolar, you can use Migration task option in the backup task and event properties to chose a follow up migration task.