Configuring Migration

From SEPsesam
Jump to: navigation, search
Other languages:
Deutsch • ‎English
Copyright © SEP AG 1999-2017. 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.2/4.4.3. For previous documentation version(s), check documentation archive.


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

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.

Configuring a migration job

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

SEP sesam schedules represent a framework for automating task execution. Different events, such as backup, migration, replication, restore, etc., can be linked to a schedule and configured to occur at a specified time.

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 once only. A schedule can be used for any number of events and the events of a particular task (backup, restore, migration, etc.) can can be configured in several schedules. All schedules and related jobs are configured and run in the SEP sesam Server's time zone.

Schedules always contain one predefined task: a NEWDAY schedule, which is linked to a NEWDAY event. SEP sesam uses the NEWDAY event to reorder its database, enable uninterrupted activity of the SEP sesam processes and 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.

The options for creating a SEP sesam schedule differ slightly depending on your SEP sesam version. Version 4.4.3 provides a few additional options such as user-defined dates (custom calendar). For details on its use, see Creating Custom Calendar.

> Creating a schedule with v. 4.4.3

> Creating a schedule with v. 4.4.2

SEP sesam v. 4.4.3

  1. From Main Selection -> Scheduling -> Schedules, click New schedule. The Schedule window appears.
  2. By default, the Execution is already enabled. Use this option to activate or disable the schedule. If you deselect the execution option, all events that are linked to this schedule will be deactivated. You can deactivate a schedule if you want to exclude scheduled jobs to run on specific days, such as holidays. For more details, see Creating Custom Calendar.
  3. In the Name field, enter the name for the schedule.
  4. Specify the time range and start time for the schedule in the Start field. Click the arrows in the date field to display a calendar. By default, the current date is already entered. In the next field, specify the start time, e.g., 18.30. All events related to this schedule will be started at the time defined by this parameter. Keep in mind that 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.
  5. If you want your schedule to be valid for a limited period of time only, e.g., until the end of the year, check the Expiration date option and enter the date of its suspension. 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.
  6. The table provides a selection of different time parameters to configure the time intervals for scheduled jobs. Jobs can occur once or recur daily or yearly. For example, you can schedule a full backup to take place every Friday at 18:00. From the tabs on the left, select one of the following:
    • 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. Available on SEP sesam v. 4.4.3 or higher. See Creating Custom Calendar for details.
  7. Under Advanced settings you can further refine your schedule.
    • Optionally, use the Start time frame if you want to define the maximum allowed startup time for your event. Specify the startup time in days and/or hours. If the event cannot be executed within this specified time frame, it will not be executed at all. If this option is not enabled, the allowed start time of the task is not limited and a job can be started at any time when the resource is available.
    • You can also specify a time frame for repeating the event. Check the Repeat task box and choose how often (in hours and minutes) the task should be repeated. Use the For a duration of parameter if you want to specify the duration of the repeated event (days and/or hours).
    • Optionally, you can specify the time frame after which the scheduled event will be cancelled by checking the box in front of the Stop task if runs longer than option and specifying the amount of time (in days and/or hours) following the event's scheduled start time after which the event will be cancelled.
    Schedule-user defined 10.png


  8. Click OK to save the schedule.

SEP sesam v. 4.4.2

  1. From Main Selection -> Scheduling -> Schedules, click New schedule. The Schedule window appears.
  2. By default, Execution is already enabled. Use this option to activate or disable the schedule. If you deselect the execution option (No), the schedule will still be displayed as shaded in the list of schedules but all events linked to this schedule will be deactivated.
  3. In the Name field, enter the name for the schedule.
  4. The Cycle table provides a selection of different time parameters to configure the time intervals for scheduled jobs. Jobs can occur once or recur daily or yearly. For example, you can schedule a full backup to take place every Friday at 18:00. From the tabs on the left, select one of the following:
    • 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
  5. Under the Period of validity, specify the time range for the schedule. Click the arrows in the date field to display a calendar.
    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 and there can be no execution prior to this date. If you want your schedule to be valid for a limited period of time only, 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 start time for your schedule – all events related to this schedule will be started at the time defined by this parameter. Keep in mind that 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. You can also limit the start time by specifying the Duration. This option specifies the amount of time in days and/or hours for which an event can be in the queue. If the event cannot be executed within the duration time frame, it will not be executed at all.
  7. New schedule bck weekly.png

  8. Click OK to save the schedule.

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 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. The settings under the 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 save set is purgeable immediately after the migration. The saveset EOL has no effect for save sets stored on tape media.
    Migration event.png


  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.

See also

Adding a Task to the Task GroupFollow-up Events