Don't use SAM, use the command line. Simply use lvextend -m 1 to establish the new mirror. If your vg00 resides on one disk and you want to mirror it to a second internal disk then:
pvcreate -B /dev/rdsk/c?t?d? vgextend vg00 /dev/dsk/c?t?d? mkboot /dev/dsk/c?t?d? mkboot -a "hpux -lq" /dev/dsk/c?t?d? repeat above for original root disk for i in /dev/vg00/lvol* do echo lvextend -m 1 $i /dev/dsk/c?t?d? lvextend -m 1 $i /dev/dsk/c?t?d? done
Verify afterwards with vgdisplay -v vg00 I also recommend turning off mirror write cache and consistency for primary swap, but this can be done only in lvm maintenance mode and is not really necessary.
"Mirror disk operations require the installation of the optional HP MirrorDisk/UX software, which is not included in the standard HP-UX operating system."
First check to see if you have the ability to mirror with software.
Hi, Be careful, that Your swap/dump volume (lvol2) is in the first 2GB of Your disk. If you have a big lvol10 in vg00, You will have trouble with the for-loop. You can set the ALT-bootpath with "setboot -a hardwarepath_of_mirrordisk".
I question the use of mirroring. I'd rather have a good recovery tape. And use the drive space for something useful. A disk having problems will probably corrupt the mirror.
Larry, mirroring provides protection against hardware failure, pure and simple. It is essential to have a protection against drive failures in a system where availability is important. Where disk space is a concern, raid arrays provide availablity with lower overhead in terms of "wasted" disks. There is a performance degredation with raid arrays, though.
Also, while not integral to maintaining production, having data mirrors allows smooth and esay recovery options for a multitude of upgrade/testing situations.
