Addindg disk to a package .

[Chapaya]

Hello ,
I have MC/SG with 2 packges and 2 nodes ,
i want to add a disk to my db package .

how do i do it ?

Eran .

[Rita C Workman]

I do the following:

PKG control:
cmhaltpkg -v
vgchange -c n
vgchange -a y

Set up Disks:
pvcreate the disks your going to add
vgextend /dev/vg /dev/dsk/c-t-d- (your new disks)

Set up lvols:
lvextend -l xxx /dev/vg/lvol /dev/dsk/c-t-d-
(unless your creating a new lvol then do your lvcreate first)
* * if on EMC disks remember to turn off bad-block re-allocation
using lvchange -r N command * *

Filesystem:
either extend it or create new
fsadm -F vxfs -b xxxx(size in kbytes) /filesystemname
or
newfs -F vxfs -o /dev/vg/rlvol

Check work:
vgdisplay to check your work
lvdisplay to check your work

Export vg to other node !
vgexport -pvs -m /etc/lvmconf/vgname.map /dev/vg

Copy mapfile to other node
rcp /etc/lvmconf/vgname.map :/etc/lvmconf

Now if you created a new lvol (or maybe vg) then go in and edit
your package control script to include these addtions.
rcp the package control script to the other also.

On other node:
Take note of the /dev/vg/group minor number.........
vgexport /dev/vg (get rid of the old info from lvmtab file)
mkdir /dev/vg
mknod /dev/vg/group c 64 0x_ _ 0000 recreate it

Import your vg mapfile:
vgimport -vs -m /etc/lvmconf/vgname.map /dev/vg

Back on the original node:
vgchange -a n /dev/vg
vgchange -c y /dev/vg
cmrunpkg -v

Hope I didn't leave anything out...remember if your creating a new vg you have editing to do in your control script....if your just increasing an existing lvol, then you can omit copying the control script to the other node.

Rgrds,
Rita


Hope I didn't leave anything out....

[Chapaya]

Hello Rita ,

do i have to use cmapplyconf ?

Eran.

[Marco Santerre]

Eran, I can answer that question for Rita. No you don't have to do a cmapplyconf.

[Rita C Workman]

Thanks Marco...

Now I remember what I left out...dah....(where's my coffee)
If you create a new vg, remember to add this new vg entry to your Cluster Configuration File...and generally when I do that, I like to run my check and apply then.

Rgrds,
Rita

[Stuart Abramson_2]

If you are adding a disk to an existing VG, you don't have to shut down the cluster.

If you are adding a new VG, then you USED to have to shut down the cluster, but you don't anymore (since MC/SG 10.10).

If you add a new LV to an existing VG, you must modify the package control script, which has lines like this:


LV[56]="/dev/vgdb/sapdata46"; FS[56]="/oracle/PA1/sapdata46"

[Marco Santerre]

Yes Rita,

I, too, like to run the cmapplyconf when I add a new VG in my cluster. The reason why I made my answer so simple was that, after looking at the question and answer, I assumed that the VG was already existing. But I agree with you.

[Sanjay_6]

Hi Eran,

You do not have to do a cmapplyconf again. Like Rita has suggested, shutdown the package, activate the vg in exclusive mode, add the disk, export the vg info to a map file on the node , rcp this map file to another node. Export the vg info from that node to delate the old info for that vg and then use the map file to reimport the vg info. Once done, you can deavivate the vg on all nodes and start the package. You do not have to do a "cmapplyconf" at this point.

Hope this helps.

Regds

[Kent Ostby]

There is a certified document , UXSGLVKBAN00000002 , in the ITRC that has been written to help with this issue.

Best regards,

Kent M. Ostby

[Stephen Doud]

Eran,

Yours is a common question and Kent recommended an article I authored and made available in the ITRC technical knowledge database.

For your (and forum readers) benefit, most of the ServiceGuard engineering notes I have written (over a hundred) begin with the prefix UXSG or UMCSG. These self-help articles give a walk-thru of most common tasks.

-Stephen Doud