Quote:
Originally Posted by
dnicky
[...]what will happen if the two new disks are not configured i.e. PVIDs are not created using chdev command on the secondary node before starting the cluster services on the primary node?
I guess, obviously the fail over to the secondary node will fail as the cluster services won't be able to access the new disks. In this scenario, will it be ok to create the PVIDs for the new disks on the secondary node and then subsequently fail over to the secondary node?
You are right both with your assumption about what whould happen and that you need to make the PVIDs known to secondary before you could proceed. I don't know which HACMP version you use. Regardless of the version the following procedure should work: make the PVID visible, then update the VG information on secondary while HACMP is stopped (by a Learning Import), then verify and sychcronise the Cluster.
If you are curious you could try to verify/sync the cluster with the autocorrection flag activated after assigning the PVID but before the manual import to find out if there was a chance that the cluster would resolve the problem on its own. I did not try this with current HACMP version but saw some enhancements in 5.4.1 compared to earlier versions that make me think that it might be possible now. When you are below version 5.3 forget it.