You can migrate a virtual disk
(VDisk) from one MDisk group to another from the Migrating VDisks panel.
Context
The SAN Volume Controller provides various data migration features. These can be used to
move the placement of data both within MDisk groups and between MDisk groups.
These features can be used concurrent with I/O operations. There are two ways
in which you can migrate data:
- Migrating data (extents) from one MDisk to another (within the same MDisk
group). This can be used to remove hot or overutilized MDisks. This can only
be performed using the CLI.
- Migrating VDisks from one MDisk group to another. This can be used to
remove hot MDisk groups, for example, you can reduce the utilization of a
group of MDisks.
You can determine the usage of particular MDisks by gathering I/O statistics
about MDisks and VDisks. Once you have gathered this data, you can analyze
it to determine which VDisks or MDisks are hot. This procedure then takes
you through migrating VDisks from one MDisk group to another.
When a migrate command is issued, a check is made to ensure that the destination
of the migrate has enough free extents to satisfy the command. If it does,
the command proceeds, but will take some time to complete. During this time,
it is possible for the free destination extents to be consumed by another
process, for example, by creating a new VDisk in the destination MDisk group
or by starting more migrate commands. In this scenario, when all the destination
extents have been allocated the migration commands suspend and an error is
logged (error id 020005). There are two methods for recovering from this situation:
- Add additional MDisks to the target MDisk group. This will provide additional
extents in the group and will allow the migrations to be restarted (by marking
the error as fixed).
- Migrate one or more VDisks that are already created from the MDisk group
to another group. This will free up extents in the group and allow the original
migrations to be restarted (again by marking the error as fixed).
Steps
Perform the following steps to migrate VDisks between MDisk
groups:
- Isolate any VDisks that are overutilized. You can determine this by requesting
an I/O statistics dump and analyzing the output. To start I/O statistics gathering,
select Manage Cluster from the portfolio, then select
the Start statistics collection task. Enter 15 minutes for the interval and click OK. This will
generate a new I/O statistics dump file approximately every 15 minutes.
Wait for at least 15 minutes before proceeding to the next step.
- Select Service and Maintenance from the portfolio
and then select the List dumps task.
- Click on the I/O Statistics logs link in the panel
displayed. This will list the I/O statistics files that have been generated.
These are prefixed with m and Nm for
MDisk statistics and v for VDisk statistics. Click on
one of the filenames to view the contents.
- Analyze the dumps to determine which VDisks are hot. It may be helpful
to also determine which MDisks are being heavily utilized as you can spread
the data they contain more evenly across all the MDisks in the group.
- Stop the statistics collection again by selecting Manage
Cluster from the portfolio and then select Stop statistics
collection task.
Once you have analyzed the I/O statistics data, you can determine which
VDisks are hot. You also need to determine which MDisk group you wish to move
this VDisk to. Either create a new MDisk group or determine an existing group
that is not yet over utilized. You can do this by checking the I/O statistics
files generated above and ensuring that the MDisks or VDisks in the target
MDisk group are less utilized than the source group.
- Click Work with Virtual Disks from the portfolio.
- Click Virtual Disks from the portfolio. The Filtering
Virtual Disks panel is displayed.
- Specify the filter criteria that you want to use. Click OK. The Virtual Disks panel is displayed.
- Select the VDisk you want to migrate and select Migrate
a VDisk from the list. Click Go. The Migrating VDisks panel is displayed.