Solaris

Not too familiar with VxVM. We have a Device c1t0d0, disk rootdg01, group rootdg that was paired with Device c1t1d0, disk mirror_1, group rootdg.

c1t0d0 has failed.

When we get a replacement for c1t0d0 can we just run vxdiskadm and choose choice #5 to "replace a failed or removed disk" ?

Will it be that simple?

Thanks!

Marty

Not quite. You run that AFTER replacing the failed disk to start using the new one. BEFORE you need to choose the "remove a failed disk for replacement" option (or something very similar to that). You need to run vxdiskadm before the physical hardware replacement and again after.

Replacing a mirrored root disk under VxVM is a little different from replacing any other mirrored disk under volume manager
First of all you have to confirm that your system cn boot from the mirrored disk, To ensure that run the following command out from my system is appended below (truncted for clarity)


root@baluqorcz1:/# eeprom
nvramrc=devalias vx-rootdg01 /pci@9,600000/SUNW,qlc@2/fp@0,0/disk@w2100000c50850e70,0:a
devalias vx-rootdg02 /pci@9,600000/SUNW,qlc@2/fp@0,0/disk@

You should create an alias to boot from alternate boot disk.
Once that is done, you have to remove the disk from volume manager control example
$vxdisk offline c1t0d0d0
then to physical pull the bad disk out you have remove it from OS control example
#luxadm removez-device c1t0d0s0
then you are safe to remove the disk
after that run#devfsadm -C -c disk
so that the system rereads all the drives present
then install the new drive.
After that make the OS presence of a new drive for that run this command
#luxadm insert_device c1t0d0s0
then again run this command #devfsadm -C -s disk
then bring the disk under volum manager conrol example
#vxdisk online c1t0d0s0
check that the volume manager can see it by running
#vxdisk list
now run #vxdiskadm command

You also might consider reading Veritas Volume Mnager Trouble shooting guide section Re-Adding and replacing Boot Disks

Thanks very much to both of you for taking the time to respond to my query. I'll try to post details of this activity after I get a new replacement disk. Wish I had a place to experiment . We're having a little trouble getting the replacement disk on-site so my feedback may take a few days.

I will try to locate and read The section in "Veritas Volume Mnager Trouble shooting guide" (section Re-Adding and replacing Boot Disks). Thanks again!

Volume Manager Support Operations
Menu: VolumeManager/Disk

1 Add or initialize one or more disks
2 Encapsulate one or more disks
3 Remove a disk
4 Remove a disk for replacement
5 Replace a failed or removed disk
6 Mirror volumes on a disk
7 Move volumes from a disk
8 Enable access to (import) a disk group
9 Remove access to (deport) a disk group
10 Enable (online) a disk device
11 Disable (offline) a disk device
12 Mark a disk as a spare for a disk group
13 Turn off the spare flag on a disk
14 Unrelocate subdisks back to a disk
15 Exclude a disk from hot-relocation use
16 Make a disk available for hot-relocation use
17 Prevent multipathing/Suppress devices from VxVM's view
18 Allow multipathing/Unsuppress devices from VxVM's view
19 List currently suppressed/non-multipathed devices
list List disk information


? Display help about menu
?? Display help about the menuing system
q Exit from menus

Select an operation to perform:

First do Option 4 (Remove a disk for replacement)

Then remove the bad disk/add new disk (luxadm remove_device /devfsadm etc ...)

Then do Option 5 (Replace a failed or removed disk)

Still waiting on the disk.

Isn't it necessary to run

vxdctl enable

once the operating system can "see" the new disk via the format command?

Also, does the fact that I already ran choice #11 (disable -offline- a disk device) change the instructions you provided?

Thanks!