User`s guide

1–Introduction
Feature Details
1-6 ISR654606-00 A
Protection
DMS provides data protection against some of the common user errors by
enforcing the following restrictions:
 An array must have an attribute of either Source, Destination, or
Source+Destination to participate in the migration. When you configure a
data migration job, Source LUNs can be assigned only from an array with
the attribute Source (or (Source+Destination), and Destination LUNs can be
assigned only from an array with the attribute Destination (or
Source+Destination). Use these attributes properly to avoid errors.
 A user acknowledgement is required for a data migration job after the job is
completed. This feature provides better accounting and record-keeping for
the job. The data migration log indicates when the job was completed and
when you acknowledge the completion status of the job.
 After a LUN is configured as a Destination LUN for a specific data migration
job, the LUN cannot be configured for a different job until the current job is
completed and you acknowledge or remove the job.
 DMS detects the normal configuration of partitions on the data LUN. Before
fully configuring a data migration job, DMS provides a warning if it detects
valid partition tables on the destination LUN.
Data Migration Jobs
DMS manages the data migration processes in terms of data migration jobs. A
maximum of 256 jobs can be scheduled to run at any time.
Data Migration Job Attributes
Configure a data migration job for the following attributes:
 Source and Destination LUN: You can configure a single source LUN to
migrate to one or multiple destination LUNs. Any specified destination LUN
can be part of a single data migration job.
 Job groups: For better manageability, you can configure data migration
jobs to belong to a specific, user-defined job group. By default, a job is
assigned to a default group, Group 0.
 Scheduling: You can configure data migration jobs to start immediately, to
start at a specified time, to have no start time (configure only), or to use a
priority-based serial scheduling. For details, see the “Scheduling...” sections
under “Using the Data Migration Wizard” on page 3-7.
 I/O size: You can configure each data migration job to migrate data using a
specified I/O size. Different types of arrays and LUNs may provide optimum
performance based on the I/O size. The default size is 64K.