VCS Concurrency Violation brief note.

Concurrency Violation brief note mentioned based on the real scenario.

engineA.log are,



2014/12/03 06:46:54 VCS INFO V-16-1-10299 Resource App_saposcol (Owner: Unspecified, Group: sapgtsprd) is online on mapibm625 (Not initiated by VCS)
2014/12/03 06:46:54 VCS ERROR V-16-1-10214 Concurrency Violation:CurrentCount increased above 1 for failover group sapgtsprd
2014/12/03 06:46:54 VCS NOTICE V-16-1-10233 Clearing Restart attribute for group sapgtsprd on all nodes
2014/12/03 06:46:55 VCS WARNING V-16-6-15034 (mapibm625) violation:-Offlining group sapgtsprd on system mapibm625
2014/12/03 06:46:55 VCS INFO V-16-1-50135 User root fired command: hagrp -offline sapgtsprd  mapibm625  from localhost
2014/12/03 06:46:55 VCS NOTICE V-16-1-10167 Initiating manual offline of group sapgtsprd on system mapibm625

Explanation
=============

Most service groups are of type failover (the default) meaning it should only run on one system at any one time and it can fail over to another system, so if VCS detects a failover group is running on more than one node then it reports a Concurrency Violation and then tries to offline on the node that VCS did not online it on.

So in your situation resource App_saposcol in group sapgtsprd was onlined on mapibm625 outside of VCS control when it was already online on another system in the cluster so VCS offlined it:

2014/12/03 06:46:55 VCS NOTICE V-16-1-10167 Initiating manual offline of group sapgtsprd on system mapibm625

If group should run on 2 systems at the same time then you should configure group as Parallel (set group attribute Parallel = 1) and then group will run on all systems in the cluster at the same time.

Credit to https://www.veritas.com