Migration Tasks

A migration is the process of copying already backed up data from one media pool (e.g. disk) to a different media pool (e.g. tape). The previously backed up files are organized in the form of savesets. These are copied identically from the source media pool to the target media pool. This way a duplication of savesets is possible. Typically these are realized in the sequence Disk-To-Disk-To-Tape (D2D2T).

As long as both media are available after the migration (in the source- or target- media pool) the saveset is duplicated. After the saveset is deleted from the source-media pool it is considered migrated. Optionally, both datasets can be accessed with the restore wizard. If only the migrated saveset exists it will be required in case of a restore.

From SEP sesam Version 3.6 the migration tasks are managed in a seperate menu item. In order to make Sesam more flexible regarding various requirements the tradition of the Sesam-Principle of only defining the source for tasks is broken with. Now source and target are to be defined in the new migration dialog. This makes enables you to immediately start a configured migration task from the GUI or attach it to a Migration Event over a schedule to start it automatically at a certein point in time.

Additionally a number of filter options were added(by task, task group or backup client, only to name a few). It is now also possible to migrate backups from a particular medium to a different pool.

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)
  • starting on medium
    Standard = "*" for all media. With this the savesets of a particular medium of the media pool can be migrated. Depending on media size a backup can range over several media. Here only backups that begin on this medium are migrated!
  • Drive
    Drive number of the drive that is used to read the data (Mandatory field)
  • Saveset
    Standard = "*" for all savesets. With this it is possible to only migrate a particular backup.The selection is made according to the saveset-ID.
• 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
  Here the timeframe of the backups that are to be migrated is defined.
  • Sesam day
    allows for the the definition of an absolute timeframe for the selection of the backups that are to be migrated. The entered date always referrs to the Sesam day.
  • relative Backup day
    from/to as a relative specification of the number of passed days. As an example, the relative timeframe 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 status
  This allows to choose to only migrate certain backups with certain statuses (successful, with warnings or partially restorable). Default is migrating all successful backups and backups with warnings.
• Backup type
  Choice according to CFDI-Type (Copy, Full, Diff Inc): C, F, D, I and G. The CFDI-Type '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 thing, this makes sure that all relevant backups for a possible disaster recovery are available on the created media set for removal scenarios.
• Object
  • Task
    Default = "*" for all tasks in the defined timeframe. Here, a particular task can be chosen for migration.
  • Task group
    Default = "*" for all taskt in the defined timeframe. If a task group is selected only the tasks within the defined timeframe of this task group are migrated.
  • Client
    Default = "*" for all backup clients in the defined timeframe.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.

Notes

text field with max. 255 characters for additional input.

Buttons

Start

After activating immediate start of the migration task

create 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