Migration Tasks 4.4

From SEPsesam
Jump to: navigation, search
Other languages:
Deutsch • ‎English
<<<Back
Backup Plans
User Manual
Next>>>
Si3 Replications


Icon archived docs.png Note
This is not the latest version of the article and, as such, does not provide information on features and enhancements introduced in the latest release. For the latest documentation, check User Manual.

Migration Tasks

Migration tasks 4.4.png


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 save sets, which are copied from the source to the target media pool, typically in a disk-to-disk-to-tape (D2D2T) sequence.

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

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

Migration tasks are managed under Main selection -> Tasks -> Migration tasks menu. The source and target media pool must be defined in a new migration dialog. 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 that it starts automatically at a predefined time. For details, see Configuring Migration.

New migration task.jpg


Here is a description of all the fields and the functions assigned to them:

Name
A name for the migration task like for example 'EasyDisk1-to-Xtra_FDI' (max. 50 characters).
Parameters
  • Media pool
    Specification of the source media pool.
    • Pool
      Media pool name (e.g. 'EasyDisk1') from which the backups are to be copied (migrated). (mandatory field)
    • Drive
      Drive number of the drive that is used to read the data (mandatory field).
  • Destination
    Specification of the target.
    • Pool
      Media pool name (e.g. 'Xtra') to which the backups are to be copied (migrated). (mandatory field)
    • Drive
      Drive number of the drive that is used for writing the data (mandatory field).
    • Interface
      Optional specification of the network interface through which the data transfer is executed.
  • Date
    The time frame of the backups that are to be migrated is defined.
    • Sesam day
      Allows for the the definition of an absolute time frame for the selection of the backups that are to be migrated. The entered date always refers to the Sesam day.
    • Relative Backup Date
      From/to as a relative specification of the number of passed days. As an example, the relative time frame from -6 to 0 copies all datasets from the last 6 Sesam days including the current Sesam day.
Filter
Using the filter options the number of backups to migrate can be limited.
  • Backup State
    This allows to choose to only migrate certain backups with certain states (successful, with warnings or partially restorable). Default is migrating all successful backups and backups with warnings.
  • Backup Level
    Choice according to CFDI-level (Copy, Full, Diff Inc): C, F, D, I and G. The CFDI-level 'G' means generation-migration. This means that, in addition to the incremental backups of the past days, all connected backups from the past, up until and including the last associated full backup, are included in the migration. Among other things, this makes sure that all relevant backups for a possible disaster recovery are available on the created media set for removal scenarios.
  • Copy migrated savesets again
    Already migrated save sets will be used as source for migration in addition to original backup save sets. This allows the so called migration-of-migration.
  • Object
    • Task
      Default = "*" for all tasks in the defined time frame. Here, a particular task can be chosen for migration.
    • Task group
      Default = "*" for all tasks in the defined time frame. If a task group is selected only the tasks within the defined time frame of this task group are migrated.
    • Client
      Default = "*" for all backup clients in the defined time frame. If a backup client is chosen only the backups from this client are migrated.
  • Number of copies
    Default = 0 (zero) means that backups can be migrated as often as you want. Entering a number > 0 means that a backup can only be migrated that many times.
Special Filter
  • Start Media
    Standard = "*" for all media. With this the save sets of a particular medium of the media pool can be migrated. Depending on media size, a backup can range over several media. Only backups that begin on this medium are migrated!
  • Saveset
    Standard = "*" for all save sets. It is possible to only migrate a particular backup.The selection is made according to the save set ID.
Comment
Text field for additional input. To expand the comment field place the mouse pointer in the field and click F1.

Buttons

Make A Copy And Save
If the migration task was given a different name in the field Name all changed options can be saved under a new name.
Save
Saves the current changes.
Delete
Migration task is deleted.
Cancel
Editing of the migration task is closed, the changes are discarded.