to remove the volume group, you'll need to do N lvremoves (one for each lvol), N vgreduces (one for each disk minus one) and one vgremove (to remove the last physical volume).
when you go to make the replacement vg, you'll want to start with a "pvcreate -f" to write fresh/untainted lvm headers onto each disk.
------------
that's the lovely theoretical part!
since these disks are visible to both nodes of your cluster -- if you touch these disks, the application WILL BE impacted. so you'll need to arrange for application downtime!!
double and triple check that you've got backups (plural!!) of whatever is currently on this volume before you start anything!!
use this command to record the PVRA information of the disk that will be the cluster lock disk:
# echo "0x2008?4X" | adb /dev/dsk/cXtYdZ
following the vgimport of the map file on the 2nd node, issue this command (on the 2nd node) to make sure cXtYdZ is the same on both systems. (the values returned must match!).
cmapplyconf will distribute the SG information but also modify the LVM headers (the PVRA).
as a reminder -- mirroring does NOT replicate lvm headers. when you have to replace a disk -- especially one that is part of a SG cluster you need to do a vgcfgrestore as well.
