5 1 0:Creating a Migration Event
Overview
A migration event represents the execution of migration tasks, which define the scope, details, source, and destination for the migration process. These tasks allow you to move data from one storage location to another, ensuring data availability and optimizing storage resources.
Migration tasks can be performed in the following ways:
- A task can be executed using the option Immediate start as a standalone, non-recurring instance.
- Migration process can be automated by scheduling migration events. These events can be set to repeat at regular intervals within a defined schedule. For a specific task, multiple events can be created across different schedules, each with its own set of customized parameters and configurations.
- Migration task can also be integrated with backup events. By configuring migration tasks as follow-up events for backup events, data migrations are initiated immediately after successful backups. This ensures that your data is consistently and promptly migrated to the desired storage location, maintaining data integrity and reducing the risk of data loss.
Create a migration event
To create a new migration event, go to Main Selection -> Scheduling -> Schedules, right-click on a schedule and then click on New Migration Event.
Define the settings and options as required. For detailed explanations of the available options, refer to section Migration event options.
Note | |
The settings for Media pool, Destination, Backup date, Backup state, Backup level, Object, and Special filter are initially defined in the selected migration task. For the migration event, you can modify these settings. Any changes are applied to the current migration event only and do not affect the values originally set in the migration task. When you reopen the event, the values that have been changed from their original settings in the migration task are displayed in blue. |
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
Migration event options
When creating or modifying a migration event, the following options are available to customize its settings and behavior.
General settings
Task name | Select the migration task this event is based on. |
Sequence control | |
---|---|
Priority | Select a priority that will determine the relative importance of this event and establish the execution order of events in a backup day. Event priorities in SEP sesam range from 1 (lowest) to 99 (highest). Events with priority 0 are always executed first, cannot be blocked or used for blocking events. |
Blocking date | Select this option to create a blocking event that prevents the execution of equal events scheduled on the same backup day as the blocking event, but with lower priority. By using this option, events associated with the same task and having lower priority will be blocked from starting. |
Source and destination storage settings
Media pool | |
---|---|
Pool | Displays the source media pool from which the data will be migrated. |
Drive | Displays 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 | Displays 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 | Optionally, you can change 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. |
Data mover | Optionally, you can select the data mover that will be used in the migration process. The data mover is responsible for handling the data transfer between the source and destination locations. This option is useful when access to a third-party software API is required or when you need to redirect the data stream. |
Scope settings
Backup date | ||||
---|---|---|---|---|
Date | If a fixed time range was defined in the migration task, it will be displayed in this field and cannot be changed for the current event. If you wish to modify the time range, 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 (INC), 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.
| |||
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 it was defined in the migration task and this cannot be changed for the current event. |
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 Migration Task – Configuring Migration – Managing Events – Managing Schedules