Creating a Migration Task

From SEPsesam
Jump to: navigation, search
Other languages:
Deutsch • ‎English

Copyright © SEP AG 1999-2021. 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 task represents the first step in a migration job configuration. A migration task is used to select a saveset and target media pool for migration. It is created by selecting the backed up data, source and target media pool.

Steps

  1. In the Main Selection -> Tasks -> Migration Tasks, click New Migration Task. The Migration Task window is displayed.
  2. New migration task Beefalo V2.jpg

  3. In the Name field, enter a meaningful name for the migration task.
  4. Under the Media pool, specify the following:
    • Pool: Select the source media pool from which the data will be migrated, e.g., source_media_pool.
    • Drive: By selecting the source media pool the drive number of the drive that will be used to read the data is set automatically, however, you can select another drive from the drop-down list. Typically, you use this if you have configured additional drives and you want to assign dedicated drives for migration jobs. For details, see the option Create second drive (introduced in SEP sesam 4.4.3 Tigon) 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).
  5. Under the Destination, specify the following:
    • Pool: Select the target media pool to which the data will be migrated, e.g., target_media_pool.
    • 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 you want to assign dedicated drives for migration jobs. For details, see the option Create second drive (introduced in SEP sesam 4.4.3 Tigon) 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).
  6. Under the Backup date, 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.
  7. Under the 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). You can also select one of the following options:
    • Copy migrated saveset again: If selected, a saveset that has already been migrated can be migrated again.
    • Delete after successful migration: If selected, a saveset will be deleted after successful migration.
  8. Select the Backup level you want to migrate (COPY, FULL, DIFF, INC): C F D I G, where G means a special backup level generation. The G backup level 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 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 that in need of disaster recovery all required backups are available on the storage media.
  9. Under the Number of copies, select how many times may the backed up data be migrated. Default is 0, meaning that data migration is unlimited.
  10. Under the 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.
  11. Under the Special filter, you can select the following options:
    • 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.
    • Saveset: Optionally, you can select only one saveset to be migrated according to its ID.
    • Select (default) or deselect the check box Parallel migration. If selected, data can be migrated concurrently using multiple streams, thus improving the migration speed.
  12. Click Save to save your migration task.

After you have created a migration task, you have to create a schedule and a new migration event for it.