Your shared VG is not same in another node's ODM after you add a PV to shared VG.
So another node of yours can not varyon it.
In this condition, I assume you just add a disk, no add FS on shared VG .
I suggest you do steps below on node that VG missed
0.shutdown your HACMP gracefull ,(it means your production will be down)
1.exportvg shared VG .
2.importvg shared VG
3.change shared VG to not auto varyon when boot.
hi,
it seems as if you only added the disk on one box ?
what version of OS and HACMP are you running ?
if 4.3.3 and 4.4 HACMP or higher you can import volume group
on the second server without taking any services down ,
i.e.
on primary node ( node you have added the disk )
varyonvg -b -u vgname
on secondary node
importvg -L vgname hdisk? ( ? a disk in the volume group you want to import)
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.