Re: Updating VGs that are part of a cluster

The important gotcha for any clustering is to have complete disk
definitions on both boxes that match before you do the addition.

John T Mills

Something similar to what you have could be:

Initial work
----------------------
Node 01:
cfgmgr
lspv | grep None # determine new disk
chdev -l newdisk0 -a pv=yes

Node 02:
cfgmgr
lspv | grep None # determine new disk
chdev -l newdisk0 -a pv=yes

Final work
----------------------
Node01:
Use CSPOC type LVM process to extendvg. Cluster remains up for all the
work.

-or-

Stop clustering software 01/02 (will varyovff the VG)
Node01:
varyonvg VG
extendvg VG newdisk0
varyoffvg VG
Choose method A or B:
Node02: (Method A)
varyonvg VG (Method A)
importvg -L VG (Method A)
varyoffvg VG (Method A)
Node02: (Method B)
exportvg VG hdisk (Method B)
importvg -V MajorNum VG (Method B)
varyoffvg VG (Method B)

Run a cluster synchronization.
Start the cluster on 01.
Start the cluster on 02.


________________________________

From: IBM AIX Discussion List [mailto:aix-l@xxxxxxxxxxxxx] On Behalf Of
Sunder Iyengar
Sent: Tuesday, March 18, 2008 12:47 AM
To: aix-l@xxxxxxxxxxxxx
Subject: Updating VGs that are part of a cluster



Dear All,



I am talking of cases where maybe HACMP is not involved - but other
clustering software like VERITAS Cluster Server is (for sake of
simplicity, assume two cluster nodes).



If you have an AIX VG that needs to be accessible from both cluster
nodes - not concurrently but varyed on on any one cluster node at any
time. In this scenario, how do you handle addition of disks to the VG?



So the VG is imported in to both cluster nodes but only varyed on one
one node. On that node, you run a series of commands to expand the VG
and add one or more new PVs.



What actions would you take on other cluster node to ensure that when
the VG is varyed on on that node at some point, it will see and
recognize the newly added disks?



I know the synclvodm command can be used to ensure newly added volumes
are updated in the node's ODM, but what about PVs?



Perhaps this applies to HACMP environment also - not sure how this is
handled by it.



Any pointers/steps will be greatly appreciated.



P.S. This is what I had to do to get it to work properly.

Say new disks have been added to node where VG is currently active.



On active node - varyoff the VG

On second node - ensure PVid for new PVs is set (if not already set,
will set same PVid as set on other cluster node (chdev -l hdiskxx -a
pv=yes)

Export VG and importvg again. Now the VG is complete on this node too.



Any alternative to the above steps?



Thanks in advance,



Sunder.





Relevant Pages

  • SUMMARY: changed WWID on cluster member boot disk
    ... disk and quorum disk of a single-member cluster, ... I could no longer boot from the cluster disks, ... the pre-cluster stand-alone system disk; ... the root1_domain on LUN containing the member boot disk was found ...
    (Tru64-UNIX-Managers)
  • Join an existing cluster
    ... I had a cluster setup with 2 computers running windows ... shared disk array. ... Creating a dummy Local Quorum resource. ... on the same storage bus as the boot disk... ...
    (microsoft.public.windows.server.clustering)
  • Re: Creating a wide area VMS Cluster
    ... > My goal is to provide a disaster tolerant cluster for both OS and data. ... disrupting the balance of the effect of votes between sites A and B. ... You have the option of a single shadowed system disk between the ...
    (comp.os.vms)
  • RE: Cluster IP Address Does not fail over
    ... The cluster IP has no dependicies at all. ... Node1 disk manager sees LUN5. ... [DiskArb] ...
    (microsoft.public.windows.server.clustering)
  • Re: Windows 2003/SQL 2000 Cluster SAN Migration
    ... Isin't the W2K3 Cluster Server Recovery tool designed to ... > 4) assume the Old disk drive is O: and the New disk Drive is N: ... > 4) Create a new Disk Resource for the new disk and have that in the SQL ... >>just fine but not the data drives, basically on step 14 my old drives ...
    (microsoft.public.windows.server.clustering)