Duplication and Migration 3.6

From SEPsesam

Duplication and Migration

During migration, backed up data is moved from one media pool (disk) to another media pool (tape or disk). Typically data is backed up to disk (faster) and is then migrated to tape. The previously backed up data are stored in backup savesets. These savesets are transferred 1:1 from the source mediapool (disk) to the target mediapool (tape). This allows the completion of the D2D2T migration.

If you leave the media in both the source and target mediapools the saveset is duplicated. Deleting the savesets from the source mediapool (disk) defines the data as migrated. Data can be restored from either source using the SEP Restore Wizard. If only the migrated saveset still exists this will be used should a restore take place.

Since SEP sesam version 3.6 migration-events are managed in a seperate menu item. Making SEP sesam more flexible in order to different requirements, it was broken with the tardition that only the source is defined for a task. This means that a configured migration-task can be started as an immedate-event from the GUI. In the new migration dialog the source and the target has to be defined. Furthermore, a variety of new filtering options is added. By task, taskgroup or backed up client, to name only a few. It is now also possible to migrate backups of a particular medium to another pool.