Archive:Migration Tasks 4.0

From SEPsesam
Icon archived docs.png THE CONTENT OF THIS PAGE IS OUTDATED
SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.
<<<Back
Backup Plans
User Manual
Next>>>
Scheduling

Migration Tasks

Migrationsauftraege 4.0 en.jpg


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 cancelled 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 How to create a migration job.

MigrationTask en 3.8.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
    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.
Special
  • 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!
  • 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.
User Comment
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