Veritas Volume Manager 5.1 SP1 Administrator"s Guide (5900-1506, April 2011)

Moving relocated subdisks
When hot-relocation occurs, subdisks are relocated to spare disks and/or available
free space within the disk group. The new subdisk locations may not provide the
same performance or data layout that existed before hot-relocation took place.
You can move the relocated subdisks (after hot-relocation is complete) to improve
performance.
You can also move the relocated subdisks of the spare disks to keep the spare disk
space free for future hot-relocation needs. Another reason for moving subdisks
is to recreate the configuration that existed before hot-relocation occurred.
During hot-relocation, one of the electronic mail messages sent to root is shown
in the following example:
To: root
Subject: Volume Manager failures on host teal
Attempting to relocate subdisk mydg02-03 from plex home-02.
Dev_offset 0 length 1164 dm_name mydg02 da_name c0t5d0.
The available plex home-01 will be used to recover the data.
This message has information about the subdisk before relocation and can be
used to decide where to move the subdisk after relocation.
Here is an example message that shows the new location for the relocated subdisk:
To: root
Subject: Attempting VxVM relocation on host teal
Volume home Subdisk mydg02-03 relocated to mydg05-01,
but not yet recovered.
Before you move any relocated subdisks, fix or replace the disk that failed.
See “Removing and replacing disks” on page 130.
Once this is done, you can move a relocated subdisk back to the original disk as
described in the following sections.
Warning: During subdisk move operations, RAID-5 volumes are not redundant.
Moving relocated subdisks using vxdiskadm
When a disk has replaced following a failure, you can use the vxdiskadm command
move the hot-relocated subdisks back to the disk where they originally resided.
417Administering hot-relocation
Moving relocated subdisks