VERITAS Volume Manager 3.1 Administrator's Guide

Recovery

Detecting and Replacing Failed Disks

Chapter 8 351

the following example:

To: root

Subject: Volume Manager failures on host teal

Attempting to relocate subdisk disk02-03 from plex

home-02.

Dev_offset 0 length 1164 dm_name disk02 da_name c0t5d0.

The available plex home-01 will be used to recover the

data.

This message contains information about the subdisk before relocation

that can be used to decide where to move the subdisk after relocation.

For example, the following message indicates the new location for the

relocated subdisk:

To: root

Subject: Attempting VxVM relocation on host teal

Volume home Subdisk disk02-03 relocated to disk05-01,

but not yet recovered.

Before you move any relocated subdisks, ﬁx or replace the disk that

failed (as described in “Replacing Disks”). Once this is done, you can

move a relocated subdisk back to the original disk. For example, move

the relocated subdisk disk05-01 back to disk02 using the following

command:

# vxassist -g rootdg move home !disk05 disk02

NOTE During subdisk move operations, RAID-5 volumes are not redundant.

Moving Hot-Relocated Subdisks

NOTE You may need an additional license to use this feature.

After the disk that experienced the failure is ﬁxed or replaced,

vxunreloc can be used to move all the hot-relocated subdisks back to the

disk. When a subdisk is hot-relocated, its original disk media name and

the offset into the disk, are saved in the conﬁguration database. When a

subdisk is moved back to the original disk or to a new disk using