Help

Table Of Contents
How data mobility works
When a mobility job begins, a temporary device is created. For extents and devices, a temporary RAID-1 is created for each
source device or extent. The target extent or device is attached as a mirror leg of the temporary device, and synchronization
between the source and the target begins. Once synchronization completes, both source and target are fully synchronized and
you can commit (or cancel) the mobility job. Committing the job permanently transfers the data from the source to the target
and completes the mobility operation. Cancelling the job detaches the target device and keeps the data on the source device.
Once committed or cancelled, the temporary mobility device is deleted.
CAUTION: If there is I/O to the devices being moved, and latency to the target cluster is equal to or greater
than 5ms, significant performance degradation may occur.
Depending on the metro node environment, some devices cannot be moved across clusters. The Create Device Mobility Jobs
wizard automatically filters out those devices that cannot be moved. If your device is not shown in the Available Devices list it
could be for one of these reasons:
The device has exported virtual volumes. Un-export the virtual volume to move this device.
The device has virtual volumes that belong to a consistency group. Remove the virtual volume from its consistency group to
move this device.
See the Administration Guide for metro node for more information.
Move Data Within Cluster
The Move Data Within Cluster option under Mobility provides a central location for you to create, view, and manage the
status of your mobility jobs. The Status column is automatically sorted by job status, allowing you to see all jobs in a particular
state. The arrow in the default sort column indicates the direction of the sort; ascending (
) or descending ( ). You can sort
additional columns of data, select one or more jobs, and show/hide on the screen.
This screen shows the following information about your mobility jobs:
Column
Description
Mobility Job The name assigned to the mobility job.
Type Type of mobility job. This could be a device mobility job, or an extent mobility
job.
Status The status of the job. Mobility job status lists and describes the job states and
the possible actions you can take on the job in that state.
Percentage Done Displays the percentage of the mobility job that is complete.
Source The name of the device from which the data is being moved.
Target The name of the device to which the data is being moved.
Source Cluster The cluster that the data comes from.
Target Cluster The cluster to which the mobility job is moving data.
Transfer size The speed of the mobility job. When creating a mobility job, you can specify
the speed at which the data transfer will take place to balance your required
completion time with the load restrictions on your system.
Start Time The time at which the mobility job started. N/A may sometimes appear in this
column if you are connected to one cluster while viewing a mobility job that was
started on another cluster.
Filtering data
Use the Filter icon to filter the jobs displayed on the screen.
Moving data
127