Environment:
- Cluster: Veritas Cluster Server 6.1.0.000
- OS: Red Hat Enterprise Linux Server release 6.4 (Santiago)
- Volume Manager: Red Hat LVM
- Multipathing: Veritas Dynamic Multi Pathing
Introduction:
I have a two-node Veritas Cluster on Red Hat. My volumes are under LVM (customer standard).
Since Symantec does not support Device Mapper multipathing for the combination LVM+VCS on Red Hat,
I am using Veritas DMP for multipathing. Now I finally managed to get it working properly, I still have one issue.
The Cluster has 1 failover Service Group on the first node. And a second failover Service Group on the second node.
Description:
When I reboot both nodes, and the cluster starts, my Service Groups are in Partial state.
Even though the AutoStart attribute is set to false for both SG's. Every resource in my SG's is offline, execpt for my LVM Volumes.
VCS is not trying to start any resource, which is correct since AutoStart is disabled.
But the cluster sees all LVM Volumes as online, not the LVM Volume Groups.
The funny thing is that all LVM volumes (for both SG's) are online on the first node.
Even when the LastOnline was the second node. And even when priority for the second SG is set to the second node.
It appears that LVM activates all volumes at boot time, just before the Cluster kicks in.
This was proven by stopping the cluster on all nodes, deactivating all LVM volumes manual via the vgchange command,
starting the cluster again (so no host reboot). That results in expected behavior: no resource online and SG's offline.
This operational issue is know to Symantec and described in various recent release notes.
The workaround is rather vague and I tried already several options.
Resources:
Apperently this is know to Symantec.
See page 38 in "Veritas Cluster Server 6.0.1 Release Notes - Linux"
And see page 30 in "Veritas Cluster Server 6.0.4 Release Notes - Linux"
And see page 47 in "Veritas Cluster Server 6.1 Release Notes - Linux"
SG goes into Partial state if Native LVMVG is imported and activated outside VCS control
If you import and activate LVM volume group before starting VCS, the
LVMVolumeGroup remains offline though the LVMLogicalVolume resource comes
online. This causes the service group to be in a partial state.
Workaround: You must bring the VCS LVMVolumeGroup resource offline manually,
or deactivate it and export the volume group before starting VCS.
Question:
Does Symantec has more information, procedure, ... about this workaround?
Thanks in advance,
Sander Fiers