1836561 Members
1904 Online
110102 Solutions
New Discussion

chance package disk

 
SOLVED
Go to solution
mick001
Advisor

chance package disk

Can somebody provide me with a procedure how to chance a the scsi package disk to a optical disk?

L2000 HPUX 11

Many thanks,
2 REPLIES 2
Karthik S S
Honored Contributor

Re: chance package disk

What exactly do you mean by that?? I am Not getting heads and tail of the problem :-( .. are you referring to cluster package configuration??

-Karthik S S
For a list of all the ways technology has failed to improve the quality of life, please press three. - Alice Kahn
Sridhar Bhaskarla
Honored Contributor
Solution

Re: chance package disk

Hi,

To change the disks, you will need to migrate data. You can do it by establishing mirrors for each logical volume and then reducing the mirrors. For ex., if your old disk is c2t0d1 and if your new disk is c4t0d5, then you would need to do the following.

1. Add the new disk to the volume group

#pvcreate /dev/rdsk/c4t0d5
#vgextend vgxx /dev/dsk/c4t0d5

2. Create the mirror onto the new disk for each logical volume in the volume group

#lvextend -m 1 /dev/vgxx/lvol1 /dev/dsk/c4t0d5
(repeat the above for all the logical volumes in vgxx)

3. Reduce the mirror on the old disk for each logical volume

#lvreduce -m 0 /dev/vgxx/lvol1 /dev/dsk/c2t0d1
(repeat the above for all the logical volumes in vgxx that were previously mirrored)

Above steps can be done while your package is running. Shutdown the package at this time.

#cmhaltpkg -v

Remove the old disks out of the VG

#vgchange -a e vgxx
#vgreduce vgxx /dev/dsk/c2t0d1
#vgchange -a n vgxx

Generate map files to update on the secondary node.

#vgexport -p -v -s -m /tmp/vgxx.map vgxx
(copy /tmp/vgxx.map onto the secondary node)
#ll /dev/vgxx/group
(note the minor number, say 0x010000)

On the secondary node
#vgexport vgxx
#mkdir /dev/vgxx
#mknod /dev/vgxx/group c 64 0x010000
#vgimport -v -s -m /tmp/vgxx.map vgxx

Check for the cluster lock disk in the cluster ascii file.

vi /etc/cmcluster/cmclconfig.ascii and search for CLUSTER_LOCK. Replace it with the new one if it is affected and copy it to the failover node. Apply the configuration if you need to change the lock disk.

#cmhaltcl
#cmapplyconf -C /etc/cmcluster/cmclconfig.ascii
#cmruncl

Verify if everything comes up properly.

-Sri
You may be disappointed if you fail, but you are doomed if you don't try