4 4 3 Beefalo:Duplication and Migration: Difference between revisions
(Marked this version for translation) |
(Minor update (as proposed by EE).) |
||
Line 10: | Line 10: | ||
<!--T:4--> | <!--T:4--> | ||
To optimize migration performance, | To optimize migration performance, you cannot migrate savesets with errors. It is possible to migrate ''savesets with status successful'', ''savesets with warnings'' (status ''successful'' or ''with warnings'') or ''partially restorable savesets'' (containing data from cancelled backups). | ||
<!--T:5--> | <!--T:5--> |
Revision as of 17:25, 8 November 2019
Duplication and migration overview
SEP sesam migration is a process of copying selected savesets from one media pool (source pool, e.g., disk) to another media pool (target or destination pool, e.g., tape), typically in a disk-to-disk-to-tape (D2D2T) sequence. This enables duplication of the savesets.
To optimize migration performance, you cannot migrate savesets with errors. It is possible to migrate savesets with status successful, savesets with warnings (status successful or with warnings) or partially restorable savesets (containing data from cancelled backups).
If the media in the source and target media pools are available after migration, the saveset is duplicated. After the saveset has been deleted from the source media pool, it is considered migrated. The source and target data sets can be accessed by using the restore wizard. If only the migrated saveset exists, it will be required when performing the restore.
You can manage the migration tasks from GUI: Main selection -> Tasks -> Migration tasks. 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 media pool.
You can select the savesets for migration from the selected backup task, task group, or client. 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.