4 4 3 Beefalo:Migration Tasks

From SEPsesam
Revision as of 16:55, 29 October 2019 by FuzzyBot (talk | contribs) (Updating to match new version of source page)
Jump to: navigation, search
Other languages:
Backup Plans
User Manual
Replication Tasks

Migration tasks

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

This allows duplication of the savesets. To optimise migration performance, only successfully backed-up savesets or savesets with warnings (status successful or with warnings) can be selected for migration, while savesets with errors or partially restorable savesets (containing data from cancelled backups) are not migrated.

Provided that the media in the source and target media pools are available after migration, the saveset is duplicated; however, a saveset is considered to have been migrated if it is deleted from the source media pool. Both, source and target data sets can be accessed by using the restore wizard. If only the migrated saveset exists, it will be required in case of the restore.

Migration tasks Beefalo.jpg

Migration tasks are managed under Main selection -> Tasks -> Migration tasks. The source and target media pool must be defined in a new migration window. Additionally, a number of filter options are available (including by task, task group or backup client). You can also migrate backups from a specific medium to a different pool.

You can start a configured migration task from the GUI immediately or attach it to a scheduled migration event so it starts automatically at a predefined time. For details, see Configuring Migration.

New migration task Beefalo.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 you 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 is defined.
    • 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.
  • 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).
    • Copy migrated savesets 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.
  • Backup level: 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.
  • Number of copies: Select how many times may the backed up data be migrated. Default is 0, meaning that data migration is unlimited.
  • 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 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 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.
    • Paralell migration: Select (default) or deselect the check box Parallel migration. If selected, data can be migrated concurrently using multiple streams, thus improving the migration speed.
  • Note: Optionally, add additional information about the migration.

After you have configured your migration task, click Save or Cancel.

See also

Configuring Migration

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.