Source:Creating a Migration Task

From SEPsesam
Revision as of 07:26, 25 May 2023 by Jus (talk | contribs) (Marked this version for translation)
Other languages:


Docs latest icon.png Welcome to the latest SEP sesam documentation version 5.1.0 Apollon. For previous documentation version(s), check documentation archive.


Overview

The migration task is the first step in the configuration of a migration job. A migration task is used to select a saveset and a target media pool for migration. It is created by selecting the backed up data and the source and target media pools.

Steps

  1. In the Main Selection -> Tasks -> Migration Tasks, click New Migration Task. The Migration Task window is displayed.
  2. New migration task Apollon.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, but you can also select another drive from the drop-down list. Typically, you use this option 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 is to take place, e.g., the name of the Remote Device Server (RDS).
  5. Under 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 option 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).
  6. Under Backup date, set the time frame for the backups to be migrated. You can either specify it by date – Date or select the option Relative backup date. With the values you enter in the from/to fields of the Relative backup date, you define the number of days in the past that are considered for the data migration, i.e. all data in the source media pool that was backed up within a given period of time is migrated to the target pool. For example, to migrate all data from the past week including the current Sesam day, set the Relative backup date 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 set according to your backup routines. For example, your backups can run after midnight but retain the previous day's backup date. The Sesam day/backup day is defined by the time set in the NEWDAY event. For details, see SEPuler: SEP sesam backup day.
  7. Under Backup state, select the backup completion status of the savesets you want to migrate: Successfully or with warnings (default), Only successful or Partially restorable (with data from cancelled backups). You can also select one of the following options:
    • Allow copying of existing migrations (previously Copy migrated saveset again): If this option is enabled, a previously migrated saveset can be migrated again.
    • Delete after successful migration: If this option is enabled, a saveset is deleted after successful migration.
  8. 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. With backup level G, you can migrate a complete backup cycle in one step and have everything you need for a disaster recovery. For example, the combination of 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 that all required backup copies are available on the storage media in case of disaster recovery.
  9. Under Number of copies, select how many times may the backed-up data be migrated. The default setting 0, which means that data migration is unlimited..
  10. Under Object, select one of the following objects as the migration source:
    • Task: If you select a specific backup task as the source, only this task will be migrated within the specified time frame.
    • Task group: If you select a task group as the source, only the tasks of this task group will be migrated within the defined time frame.
    • Client: If you select a specific client, only the backups for this client will be migrated within the defined time frame.
  11. Under 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 take special care not to break a backup chain that might span over several media. If you select only one medium, only the backups stored on that medium will be migrated, regardless of whether they belong to a larger 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 you select this check box, the 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.