How to create a migration job (e.g. to migrate data from DISK to TAPE)

From SEPsesam

Copyright © SEP AG 1999-2011. All rights reserved.

Any form of reproduction of the contents or parts of this manual is allowed only with the express written permission from SEP AG. When compiling and designing user documentation SEP AG uses great diligence and attempts to deliver accurate and correct information. However, SEP AG cannot issue a guarantee for the contents of this manual.

SEP sesam uses the Migration Function to copy already backed up data in SEP sesam from one media pool (e.g. DISK) to another media pool (e.g. TAPE). With this function you can implement a Disk-To-Disk-To-Tape (D2D2T) backup strategy.

Already backed up data are organized in Savesets. During a migration these Savesets will be completely copied, 1 for 1, from the source media pool to the destination media pool.

Follow the steps in the example to configure a migration job.

Create a migration task

From the GUI object window on left hand side choose Task/by Clients, select the device server that contains the source media pool and choose the button New Migration Task. The following dialogue appears:

• Name

Give the task a name. After storing the input the name gets the prefix "Migration Task"

• Source Pool

Here you have to select the source media pool, or where the data is currently located.

• Drive

What drive should work for the source pool (information is mandatory).

• Remote Device Server

You define which device server performs the migration operation. You should select the device server that sends the migration data.

• Count

This counter is currently just a switch.

Count = 0 --> migration once from the source media pool

Count > 0 --> migration will be repeated N times from the source media pool

Create a schedule

Create a new schedule and configure it to your requirements.

Create a new migration task event

Select the newly created schedule, then create a new migration task event by pressing the button Migration Task Event.

• Migration Task

Here you must select your already configured migration task.

• relevant backup day

From - To as values of a the reference to a range of the previous days to be migrated. (Example: a migration range 2 weeks ago from today: relevant backup day = -14, to = 0)

• FDI Type

Gives you the possibility to select (filter) what backup you want to process (Copy, Full, Diff, Inc): C F D I

The FDI Type G has a particular meaning. For example, if you've chosen I and G and a migration range -1 to 0, all incremental backups from yesterday up to today would be transferred to tape AND all incremental and differential backup backwards until including the last depending full backup. That makes it possible to migrate a complete FDI cycle for Disaster/Recovery in one step.

• State

You can filter it by a state of the backup results. The following values are working:

 * successfully or with warnings (default)
 * only successful
 * only with warnings
 * partially restorable

The next step is to define the destination page

• Priority

see admin manual

• Blocking date

see admin manual

• Media Pool

Here you have to select the destination media pool.

• Drive

Unlike other events on migration you have to define a drive in each case.

• Interface

Selection of another configured TCP/IP-Name of the backup server. Using this interface allows you to control which path the data stream flows through your network. (Note: This is optional, and only work if your hardware is properly configured and equipped).

• Medium or destination Tape

Currently you can only use the GET_OLDEST tape strategy.

The executed migration job can be checked under Job State/Migration.