move package from 1 cluster to another

[James Odak]

anyone out there have a good and easy? way of doing this?

thanks in advance
Jim

[John Poff]

Hi Jim,

I think the only way you can do it is to delete the package from the first cluster and then create it in the second cluster. It's pretty easy.

cmhaltpkg yourpkg # on 1 cluster
cmdeleteconf yourpkg

copy your package control and config files
from the first cluster to the second one and
edit as necessary

cmcheckconf -p yourpkg # on 2nd cluster
cmapplyconf -p yourpkg # if cmcheckonf is happy


JP

[John Poff]

Oops! I messed up the 'cmdeleteconf' command. It needs a '-p' in front of the package name:

cmdeleteconf -p yourpkg


JP

[monasingh_1]

just make sure all the compatibilities between package and the new cluster OS , patches, users etc is taken care of first.

[Juan Manuel López]

If all you want to do is to run your package other node:
cmhaltpkg pkg1
cmrunpkg -n othernode pkg1

If you prefer to run by default a package on another node of your cluster, you will need to change the parameters of your conf package file:
# Enter the names of the nodes configured for this package. Repeat
# this line as necessary for additional adoptive nodes.
#
# NOTE: The order is relevant.
# Put the second Adoptive Node after the first one.
#
# Example : NODE_NAME original_node
# NODE_NAME adoptive_node

then stop your package an run cmcheckconf -P pkg1 and cmapplyconf -P pkg1 and re-run your pkg1 .

I hope this help you.

Juanma.

[Edward Finneran]

The question you originally posed says to move a package from one 'cluster' to another -- if that indeed is what you want, not moving it from one node to another within a single cluster, there is one thing you'll need to watch out for. The cluster aware flag that's set on a volume group, I believe, is cluster-specific. If you actually make the volume group visible to a different host and try to move the definition for the package over they're you'll need to do a vgchange -c n vgx on the first cluster, and vgchange -c y vgx on the new cluster. Aside from that, it's largely like removing a package from the old cluster and adding it to the new one like any other package.

[James Odak]

thanks for all the input, i was just hoping there was an easier way then removing and re-adding the package from an existing cluster to a new cluster ..preferably one that consisted of less down time

guess i just need to buckle up and just do it remove and add


jim

[Emanuele Guarneri]

Hi, (sorry for my english)
i got a problem about switching a package
(and its relative VG) from one cluster to
another.
There's one thing I know for sure:

Suppose we have a volume actived from
cluster A running package A. So the volume
is clustered from cluster A.

If I try to CLUSTERIZING the same volume
from cluster B ... ta-da!!! I got no error!!!
If i try to activate it ... I got no error !!

This VG is part of a VA7410 disk-array.

These 2 clusters are attached to VA7410.

So I can clusterize and activate the same VG
from two different cluster.

Is it NORMAL ?!?!?!?!?

Thanks in advance
Emanuele

[Bernhard Mueller]

Emanuele,

in contrast to what Edward said, I believe this is normal, because I think the "cluster-aware flag" in the VG is just a bit set "on / off".

This requires vgchange -a e (instead of -a y)
but this has nothing to do with the vg or the owning CPU.

Regards,
Bernhard

[Kevin Wright]

The name of the cluster is also set inside the VG, as changing the name of a cluster requires making a VG 'uncluster aware', but apparently you just proved you can have multiple clusters see the same VG. Only 1 node in a cluster can have the VG activated exclusively, but being able to have 2 different clusters see a VG is not good if true. I would like to test that out, but I don't have the setup to try it.

[Kevin Wright]

After re-searching this, as I suspected, this is not normal. You can't have 2 cluster ID's in the VGDA of your VG disks.