How to create a migration job (e.g. to migrate data from DISK to TAPE)

From SEPsesam
Redirect page

Template:Copyright SEP AG en

Overview

SEP sesam migration is a process of copying selected save sets from one media pool (source pool, e.g., disk) to another media pool (target or destination pool, e.g., tape). You can select the save sets for migration from the selected backup task, task group, or client. To optimize migration performance, only the save sets with status successful or with warnings can be selected for migration, while the erroneous or only partially restorable save sets (containing data from cancelled backups) cannot be migrated.
With migration you can set up a disk-to-disk-to-tape (D2D2T) backup strategy to reduce your backup and recovery times, move older data offsite for long-term data retention and prepare for disaster recovery.

You can schedule a migration job so that it starts at a specific time and date or start it manually from the menu bar Activities -> Immediate start -> Migration.

Configuring a migration job involves the following steps:

  1. Creating a migration task by selecting the backed up data, source and target media pool
  2. Creating a migration schedule by specifying when you want to migrate your data
  3. Creating a migration event by reviewing migration task parameters and (optionally) setting event priority

The procedure for migrating save sets is version specific. From SEP sesam v. 4.4.1 onwards, the Migration tasks option is provided in GUI: Main selection -> Tasks -> Migration tasks. For versions lower than 4.4.1, the migration task is created as described below.

Prerequisites

  • You must have at least two media pools configured in your SEP sesam environment.
  • You must have admin user rights for performing a migration.

Choose one of the following procedures:

Configuring a migration job in SEP sesam v. 4.4.1 and higher

Step 1: Creating a migration task

  1. In the Main Selection -> Tasks -> Migration tasks, click New migration task. The New migration task window is displayed.
  2. Migration task 4.4.png


  3. In the Name field, enter a meaningful name for the migration task.
  4. Under the Parameter, specify the following:
    • Media pool
      • Pool: Select the name of the source media pool from which the data will be migrated, e.g., source_mediapool.
      • Drive: Optionally, select the drive number of the drive that will be used to read the data.
    • Destination
      • Pool: Select the name of the target media pool to which the data will be migrated, e.g., target_mediapool.
      • Drive: Optionally, select the drive number of the drive that will be used to write the data.
      • Interface: Optionally, specify the network interface of the server through which the data transfer will be executed, e.g., the name of the Remote Device Server (RDS).
    • Time frame
      • To define the time frame of the backups that will be migrated, you can specify it either according to dates – Date or select the option Relative backup date. With values entered in the from/to fields of the Relative backup date you define the number of days in the past that are considered for data migration, meaning all data in the source media pool that was backed up within a given period of time is going to be migrated to the target pool. For example, to migrate all data from the past week including the current Sesam day, the Relative backup date is set to -7 while to is set to 0. Or, to migrate all data from the last 10 days, specify the relative time frame from -10 to 0.
      • In the drop-down list based on, the Sesam days option is selected by default. Sesam day is a backup day you define according to your backup routines. For example, your backups can run after midnight but retain the backup date of the prior day. Sesam day/backup day is defined by time set in the NEWDAY event. For details, see SEPuler: SEP sesam backup day.
  5. Under the Filter, specify the following:
    • Backup state: Select the backup completion status of the save sets you want to migrate: successfully or with warnings (default) or only successful. You cannot migrate the erroneous or only partially restorable save sets (containing data from cancelled backups).
    • Object: Select one of the following objects as a migration source.
      • Task: If you select a particular backup task as a source, only this task within the defined time frame are migrated.
      • Task group: If you select a task group as a source, only the tasks of this task group within the defined time frame are migrated.
      • Client: If you select a particular client, only the backups for this client within the defined time frame are migrated.
    • Backup type: Select the backup type you want to migrate (COPY, FULL, DIFF, INC): C F D I G, where G means a special backup type generation. The G backup type enables you to migrate a complete backup cycle in one step thus providing everything you need for disaster recovery. For example, the combination of selected backup types I and G within the specified time frame -1 to 0 in the Relative backup date would migrate all incremental backups from yesterday up to today as well as all dependent incremental and differential backups of the respective backup chain including the last associated full backup. This ensures that in need of disaster recovery all required backups are available on the storage media.
    • Number of copies: Select how many times may the backed up data be migrated. Default is 0, meaning that data migration is unlimited.
    • Copy migrated save set again: If selected, a save set that has already been migrated can be migrated again.
    • Special filter
      • Start media: Optionally, you can select only one medium from the source media pool to be migrated. You should pay special attention in order not to break a backup chain that might span across more media. If you select to migrate solely one medium, then only the backups that are stored on this medium are migrated regardless whether they belong to a wider backup set or not.
      • Save set: Optionally, you can select only one save set to be migrated according to its ID.
  6. Select (default) or deselect the check box Parallel migration. If selected, data can be migrated concurrently using multiple streams, thus improving the migration speed.
  7. Click Save to save your migration task.

Step 2: Creating a migration schedule

Creating and modifying schedules in SEP sesam enables you to manage the chronology of data protection activities. A schedule establishes the timing, frequency, and recurrence pattern of events that can range from minutes to years. It can be configured for periodic execution or as a one-time occurrence.

Schedules can group related tasks based on their type or recurrence pattern. For example, you can configure schedules for daily incremental backups and weekly full backups, and a monthly schedule for various tasks involved in preparing the backup environment.

When schedules are configured, you can assign specific events to them, which define the tasks or jobs that need to be executed. Schedules can contain any number of events, allowing you to manage multiple tasks within a single schedule. You can configure events for a particular task across multiple schedules, giving a fine level of control over the execution of that task.

A schedule becomes active only when one or more events are assigned to it. Active schedules are marked with a green icon, and disabled or inactive schedules are marked with a grey icon.

Special schedules

SEP sesam scheduling offers the option User defined to create a special schedule, allowing you to customize a calendar and specify the dates on which you want to run additional jobs or prevent certain jobs from executing. With these special schedules, you can prevent the activation of individual events on specific days, such as holidays, or at specific hours. Additionally, you can block specific or all event types if needed.

Create a new schedule

To create a new schedule, go to Main Selection -> Scheduling -> Schedules and click on New Schedule.

Define the settings and options as required. For detailed explanations of the available options, refer to section Schedule options.

SEP Tip.png Tip
You can decide the purpose and time interval of the schedule and name the schedule accordingly. For example, BCK_INCR_DAILY_0600, BCK_VM_DIFF_SAT_2100, or NEWDAY_MO-FR_0800. This approach can help you plan and manage your backup strategy.

After you have created a schedule, you can create and assign an event to it. Right-click on the schedule or click New in the Schedules toolbar, and then choose the type of event you want to create, for example, a new backup event.

You can also assign an existing task to a schedule. In the task list find and double-click a task you want to schedule, then in the Schedules tab select the schedule and the target media pool. This creates a backup event that is assigned to the selected schedule.

Screenshots

Creating new schedule Apollon.jpg

Schedule options

When creating or modifying a schedule, the following options are available to customize its settings and behavior.

General settings

Name A name for the schedule.
Execution off This option allows you to deactivate the schedule, disabling all events linked to it. When the schedule is deactivated, the related jobs will not run. By default, execution is enabled.
Start Set the start date and time for the schedule. The schedule will be activated at the specified date and time. By default, the current date and time are pre-filled.
Expiration date Set a validity period for the schedule. If the schedule should only be active for a limited time, such as until the end of the year, select the checkbox and enter the expiration date. Once the expiration date is reached, the schedule will be automatically deleted. By default, this option is disabled and the schedule remains active indefinitely.
Notes Add any comments or information related to the schedule.

Time interval

Once This option indicates a single run without any repetition. After the execution of the event, the schedule is automatically deleted.
Daily This option allows you to set the repetition period in terms of days, hours, or minutes. You can specify how frequently the event should repeat within each day.
Weekly This option enables you to set the repetition period in weeks and select the specific day(s) of the week for the event to occur. You can choose multiple days if needed.
Monthly This option allows you to set the repetition period in months and select specific days of the month for the event to occur using absolute or relative dates. For example, you can set a specific day such as the 1st or 15th of the month, or you can use relative terms such as "Second" or "Last" "workday" or "Sunday".

Optional setting "Offset (in days)" enables you to specify a specific offset in days from the starting point of the repetition. For example, if you set the offset to 3, the event will occur up to three days after the specified start date.

Yearly This option allows you to set the repetition pattern in years and select specific days of the month for the event to occur using absolute or relative dates.

Optional setting "Offset (in days)" enables you to specify a specific offset in days from the starting point of the repetition. For example, if you set the offset to 3, the event will occur up to three days after the specified start date.

User Defined This option allows you to set up a custom calendar for defining the repetition pattern. For detailed instructions on creating a custom calendar, refer to Creating a custom calendar. See also Creating a Specialized Schedule.

Advanced settings

Start time frame Select this option to specify the maximum allowed actual startup time for your event. This refers to the amount of time an event can remain in the queue before it starts executing. You can define the startup time in days and/or hours. The actual start time of the event depends on the processor load of the system. When the event's start time arrives, it is placed in the queue, where it may need to wait for higher-priority jobs to complete. If this option is enabled and the event cannot be executed within the specified time frame, it will not be executed at all.
Repeat task Enable this option if you want the event to be repeated. Select the interval (in hours or minutes) at which the task should be repeated.
For a duration of This option is available when the Repeat task checkbox is selected. Specify the time frame in days and/or hours during which the event will occur repeatedly. For example, if you set the duration to 5 days, the event will repeat with the set interval for a period of 5 days.
Stop task if it runs longer than Select this option to define a time limit (in days and/or hours) for the maximum duration of the event after the scheduled start time. If the event exceeds this time limit, it will be automatically cancelled.

Permissions

The Permissions tab enables you to set the required permissions (ACLs) for the schedule. For details, see Using Access Control Lists.


Step 3: Creating a migration event

  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.
  2. Select new migration event 4.4.png


  3. 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.
  4. 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 Setting 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.
  5. Check the settings under the Parameter and Filter that you have defined when creating the selected migration task. For details, see Step 1: Creating a migration task.
  6. Click OK to save your migration event.

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

Configuring a migration job in SEP sesam versions lower than 4.4.1

Step 1: Creating a migration task

  1. In the Main Selection -> Tasks -> By clients, select the device server with the source media pool, then click New Migration Task. The New migration task window is displayed.
  2. Migration-task1a en.jpg


  3. In the Name field, enter a meaningful name for the migration task. After storing the input, the name gets the prefix "Migration Task".
  4. From the Source Pool drop-down list, select the source media pool from which the data will be migrated.
  5. From the Drive drop-down list, select the drive number of the drive that will be used to read the data.
  6. From the Remote Device Server drop-down list, select the device server that will perform the migration operation. You should select the device server that sends the migration data.
  7. Count represents a switch that specifies how many times may the backed up data be migrated.
  8. Count = 0 --> migrate only once from the source media pool Count > 0 --> migrate N times from the source media pool

Step 2: Creating a migration schedule

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.

To create a schedule, proceed as follows:

  1. In the Main Selection -> Scheduling -> Schedules, click New schedule. The Schedule window appears.
  2. By default, the Execution is already enabled. Note that if you deselect the execution option, all events that are linked to this schedule will be deactivated.
  3. In the Name field, enter the name for the schedule.
  4. In the Cycle box, select how you want to schedule your backup. For example, you could schedule a full backup to take place every Friday at 18:00.
    Among the tabs on the left, select 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, ...), or yearly (absolute or relative dates).
    For our example, select weekly, every 1 week, and Friday.
  5. Under the Period of validity, specify the time range for the schedule. By default, the current date is already entered in the Begin field. You can specify any date as a start time for your periodical event. The schedule will only be activated after the specified date. If you want your schedule to be valid only for a limited period of time, e.g., half a year, check the End field and enter the date of its suspension. By default, this option is disabled and the schedule will be repeated in perpetuity.
  6. Under the Start time frame, select the time for your schedule – all events related to this schedule will be started at the time defined by this parameter. For our example, select 18:00. Consider that the actual start time depends on the processor load of the system. At the starting time of the event, every event is forwarded into the queue, where it might wait until jobs with a higher priority are finished. For jobs with the same priority, the FIFO rule (first in first out) applies. Optionally, you can also limit the start time by specifying the Duration. If the event cannot be executed within the duration time frame, it will not be executed at all.
  7. New schedule bck weekly.png

Step 3: Creating a migration event

  1. In the Main Selection -> Scheduling -> Schedules, select the newly created schedule and click the button Migration Task Event. A new tab Source is displayed.
  2. Migration-event1a en.jpg


  3. From the Migration Task drop-down list, select the name of the already configured migration task for which you want to create a migration job.
  4. In the Relative backup date, enter the values in the from/to fields to define the number of days in the past that are considered for data migration, meaning all data in the source media pool that was backed up within a given period of time is going to be migrated to the target pool. For example, to migrate all data from the past week including the current Sesam day, the Relative backup date is set to -7 while to is set to 0. Or, to migrate all data from the last 10 days, specify the relative time frame from -10 to 0.
  5. In the FDI Type field, select the backup type you want to migrate (COPY, FULL, DIFF, INC): C F D I G, where G means a special backup type generation. The G backup type enables you to migrate a complete backup cycle in one step thus providing everything you need for disaster recovery. For example, the combination of selected backup types I and G within the specified time frame -1 to 0 in the Relative backup date would migrate all incremental backups from yesterday up to today as well as all dependent incremental and differential backups of the respective backup chain including the last associated full backup. This ensures that in need of disaster recovery all required backups are available on the storage media.
  6. From the State drop-down list, select the backup completion status of the save sets you want to migrate: * successfully or with warnings (default) * only successful * only with warnings * partially restorable
  7. Now open the tab Destination Parameter.
  8. Migration-event2a en.jpg


  9. In the Priority box, you can 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 Setting 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.
  10. From the Media pool drop-down list, select the name of the target media pool to which the data will be migrated.
  11. In the Drive, select the drive number of the drive that will be used to write the data.
  12. In the Interface, you can specify another configured TCP/IP name of the backup server. Using this interface allows you to control which path the data stream flows through your network. This is optional and only works if your hardware is properly configured and equipped. Medium or destination tape:
    Currently you can only use the GET_OLDEST tape strategy.

To check the status of your migration job, go to Main selection -> Job State -> Migration.