4 4 3 Beefalo:Migration Tasks

From SEPsesam
Jump to: navigation, search

Other languages:
Backup Plans
User Manual
Replication Tasks

Migration tasks

About migration

Migration is the process of copying backed-up data from one media pool to another, for example, from a disk to a tape. Backed-up files are organized as savesets that are copied from the source to the target media pool, typically in a disk-to-disk-to-tape (D2D2T) sequence.

This allows for duplication of the savesets. To optimize migration performance, you cannot migrate savesets with errors. It is possible to migrate:

  • savesets with status successful
  • savesets with warnings (status successful or with warnings) or
  • partially restorable savesets (with data from aborted backups).

Provided that the media in the source and target media pools are available after migration, the saveset is duplicated. However, a saveset is considered migrated when it is deleted from the source media pool. Both, the source and target savesets can be accessed using the restore wizard. If only the migrated saveset exists, it will be required in the case of a restore.

Migration tasks are managed under Main selection -> Tasks -> Migration tasks.

Migration tasks Jaglion.jpg

Configuring migration

Configuring a migration job consists of 3 steps: creating a migration task, creating a migration schedule, and creating a migration event.

You can start a configured migration task from the GUI immediately. For more details on configuration, see Configuring Migration.

Migration options

Migration task Jaglion.jpg

When configuring a migration task, you can set the following options:

  • Name: Enter a meaningful for the migration task, e.g., MIG_Si3_mly_to_mig_3mly (max. 50 characters).
  • Media pool: Specification of the source media pool.
    • Pool: Select the source media pool from which the data will be migrated, e.g., source_mediapool (mandatory field).
    • Drive: Drive number of the drive that will be used to read the data. By selecting the source media pool, the drive number is set automatically. However, you can select another drive from the drop-down list (mandatory field).
    • 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).
  • Destination: Specification of the target for the migration.
    • Pool: Select the target media pool to which the data will be migrated, e.g., target_mediapool (mandatory field).
    • Drive: Optionally, select the drive number of the drive that will be used to write the data. Typically, you use this if you have configured additional drives and want to assign dedicated drives for migration jobs. For details, see the option Create second drive in Configuring a Data Store.
    • 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).
  • Backup date: The time frame of the backups that will be migrated.
    • To define the time frame of the backups to be migrated, you can either specify it by Date or select the option Relative backup date. With the 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, i.e. 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 the time specified in the NEWDAY event. For details, see SEPuler: SEP sesam backup day.
  • Backup State: Select the backup completion status of the savesets you want to migrate: Successfully or with warnings (default), Only successful or Partially restorable (containing data from cancelled backups).
    • Allow copying of existing migrations (previously Copy migrated saveset again): If selected, a previously migrated saveset can be migrated again.
    • Delete after successful migration: If selected, a saveset is deleted after successful migration.
  • Backup level: Select the backup level you want to migrate (COPY, FULL, DIFF, INC): C F D I G, where G stands for a special backup level generation. Backup level G allows you to migrate a complete backup cycle in one step, giving you everything you need for a disaster recovery. For example, combining the selected backup levels 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 all required backups are available on the storage media in the case of a disaster recovery. .
  • Number of copies: Select how many times may the backed up data be migrated. The default value is 0, which means that data migration is unlimited.
  • Object: Select one of the following objects as the migration source.
    • Task: If you select a particular backup task as the source, only this task within the defined time frame is 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.
  • Special filter:
    • Start media: Optionally, you can select only one medium from the source media pool to be migrated. You should take special care not to break a backup chain that could span across multiple media. If you select only one medium for migration, only the backups stored on that medium will be migrated, whether or not they belong to a wider backup set.
    • Saveset: Optionally, you can select only one saveset to be migrated according to its ID.
    • Paralell migration: Select (default) or clear the check box Parallel migration. If selected, the data can be migrated concurrently using multiple streams, thus improving the migration speed.
  • Note: Optionally, add additional information about the migration.

After you configure your migration task, click Save or Cancel.


A migration task can be associated with a schedule that has a corresponding event attached to it. For more information on creating the entire setup for migration, see Configuring Migration.

If you already have a configured schedule, you can link your migration task to it by using the Schedules tab. Then select the check box next to the schedule you want to use. You can also change its priority.

See also

Configuring MigrationAbout Scheduling

Copyright © SEP AG 1999-2022. 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.