5 1 0:Creating a Migration Task

From SEPsesam
Revision as of 12:25, 15 September 2023 by Jus (talk | contribs) (Marked this version for translation)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Other languages:


Docs latest icon.png Welcome to the latest SEP sesam documentation version 5.1.0 Apollon. For previous documentation version(s), check documentation archive.


Overview


The migration task is the first step in the configuration of a migration job. It defines the scope of migration and is used to select savesets and a target media pool for migration.

A migration task can be used in different ways:

  • You can schedule migration events to execute migration tasks at specific times or intervals. This allows you to automate the migration process and maintain up-to-date copies in the target location.
  • You can configure migration tasks as follow-up events for backup events. With this approach, data migration is triggered immediately after successful backup, either in combination with individual backup tasks or entire backup task groups.

Create a migration task

To create a new migration task, go to Main Selection -> Tasks -> Migration Tasks, and then click on New Migration Task.

Define the settings and options as required. For detailed explanations of the available options, refer to section Migration task options.

Information sign.png Note
If you want to run pre or post actions for migration tasks, configure the appropriate scripts in files sm_copy_pre and sm_copy_post (on Windows add the .bat extension, for example, sm_copy_pre.bat), and place these files in <SESAM_ROOT>/bin/sesam directory. When a migration task is started (and finished), the directory is checked. If these files exist, they will be executed before and/or after migration.

You can view the status of your migration jobs. In Web UI navigate to Monitoring -> Migrations/Replications and review the job results. The status overview lists migration tasks by name, along with details of completion status, start and end times, and media pools used for the job.

Screenshots

New migration task Apollon.jpg

Migration task options

When creating or modifying a migration task, the following options are available to customize its settings and behavior.

General settings

Name Enter the name for the migration task.

Source and destination storage settings

Media pool
Pool Select the source media pool from which the data will be migrated.
Drive Optionally, you can select the drive number of the drive that will be used to access and retrieve the data from the source location. This option is useful when you have multiple drives configured and wish to allocate a specific drive exclusively for the migration process, optimizing performance and resource utilization.
Interface Optionally, you can select the specific network interface that will be used to access the source media pool. This enables you to control which network connection is used to access the data, ensuring efficient data transfer and minimizing potential network congestion.
Destination
Pool Select the destination media pool to which the data will be migrated.
Drive Optionally, you can select the drive number of the drive that will be used to write the data to the target location. This option is useful when you have multiple drives configured and wish to allocate a specific drive exclusively for the migration process, optimizing performance and resource utilization.
Interface Optionally, you can select the specific network interface that will be used to access the target media pool. This enables you to control which network connection is used to transfer the data, ensuring efficient data transfer and minimizing potential network congestion.

Scope settings

Backup date
Date You can select this option to specify a fixed time range for the migration process. If you want that the time range is adjusted automatically, you can use the option Relative backup date.
Relative backup date Optionally, you can specify the number of days in the past to define the time frame for the migration process.

For example, if you specify a relative time frame from -7 to -2, it will migrate the data for the past five days, starting from seven days ago and ending the day before yesterday (two days ago). Similarly, a relative time frame from -10 to 0 will migrate data from the last 10 days.

Note that positive values cannot be set, as they would indicate a time range in the future. The value 0 represents the current day.

Based on Optionally, you can select whether the time frame for the migration process is based on calendar days or Sesam days. By default, Sesam days is selected. For more information, see SEP sesam backup day.
Backup state
Backup state Displays the backup completion status of the savesets that you want to migrate. The possible values are Successfully or with warnings (includes savesets that were completed successfully or with warnings in migration process), Only successful (includes only savesets that were completed successfully, any savesets with warnings or errors will be excluded), and Partially restorable (includes savesets from canceled backups that still contain data).
Allow copying of existing migrations Select this option to enable the system to copy a saveset that has already been migrated and perform the migration process again. By default, data is typically migrated only once and is not considered eligible for migration again. However, enabling this option overrides the default behavior, allowing to reprocess or duplicate savesets as needed during the migration process.
Delete after successful migration Select this option to enable the automatic deletion of the source savesets after a successful migration. Once the migration process is completed without any errors or warnings, the source savesets are deleted, freeing up storage space and reducing the need for manual cleanup of migrated savesets.
Backup level Select the specific backup levels you want to migrate. The available options include C (COPY), F (FULL), D (DIFF), I (INCR), and G (special backup level generation).

By selecting the backup level G, you can migrate an entire backup cycle in a single step, ensuring you have all the necessary data for disaster recovery. For example, if you select backup levels I and G within the time frame of -1 to 0 in the "Relative backup date" option, it will migrate all incremental backups from yesterday up to today, along with all associated incremental and differential backups within the backup chain. This includes the last corresponding full backup.

Migrating the complete backup cycle in this manner ensures that all essential backup copies are available on the storage media, enabling efficient disaster recovery process.

Copies Specify the maximum number of migrations allowed for backed-up data. This setting defines the total number of copies of a saveset across all media pools. When a migration task is run, savesets that match the task criteria are copied to the destination media pool. For example, to have two copies of backed-up data in two different media pools, you would configure the first migration task with a copy count of 1 (for the initial copy). Then, you would configure the second migration task with a copy count of 2 (for the second copy). This approach helps conserve space in destination media pools.

The default setting for this option is 0, indicating unlimited data migration without any restrictions on saveset copies. You can limit the number of migrations, ensuring that the same data is migrated only a specified number of times.

Information sign.png Note
In Apollon V2, this option functions differently. It now applies to the number of copies in a single destination pool, rather than the overall number of copies across all media pools. If you set the "Number of copies" to 1, the same savesets are migrated only once, regardless of how many times the migration task is run. This setting now specifies the number of copies of the migrated data within the same destination pool. For example, setting this number to 2 creates two copies of the same data in the destination pool.

To have multiple copies of backed-up data across different media pools, configure separate migration tasks and set the "Number of copies" to 1 for each task. This ensures a single copy is created in each destination pool.

Object
Task You can select a specific backup task as the source for the migration process. By choosing a particular backup task, only the data associated with that task is migrated within the specified time frame and configured settings. Note that the options Task, Task group and Client are mutually exclusive.
Task group You can select a specific backup task group as the source for the migration process. By choosing a task group, only the data associated with the backup tasks in that group is migrated within the specified time frame and configured settings. Note that the options Task, Task group and Client are mutually exclusive.
Client You can select a specific client as the source for the migration process. By choosing a particular client, only the backups associated with that client are migrated within the specified time frame and configured settings. Note that the options Task, Task group and Client are mutually exclusive.

Other options

Special filter
Start media Optionally, you can select a specific medium from the source media pool to be migrated. Use this option with caution to avoid breaking a backup chain that may span across multiple media. By selecting a single medium, only the backups stored on that medium will be migrated, even if they are a part of a larger backup set.
Saveset Displays the specific saveset ID if you want to migrate a single backup result and start the migration from the context menu of the backup result.
Parallel migration Select this option to enable concurrent data migration using multiple streams. This allows for faster data transfer and optimizes the overall migration process.
Options
Options Optionally, you can configure additional options to be performed with this event.
Note Add any comments or information related to the migration event.


See also

Creating a ScheduleCreating a Migration Event

Copyright © SEP AG 1999-2024. 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.