Cluster resource 'PBX-NODENAME' in Resource Group 'PBX-ClusterGroup-NODENAME' failed
Updated: 21 May 2010 | 3 comments
This issue has been solved. See solution.
Hello!
I have some clusters, each cluster have 2 node - active and passive (failover cluster) for MS SQL SERVER (x64 system)
Sometimes on cluster i see errors.
For example:
Event Type: Error
Event Source: ClusSvc
Event Category: Failover Mgr
Event ID: 1069
Date: 16.06.2009
Time: 16:48:16
User: N/A
Computer: SPDB-NODE-2
Description:
Cluster resource 'PBX-SPDB-NODE-2' in Resource Group 'PBX-ClusterGroup-SPDB-NODE-2' failed.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
At occurrence of such error the network for some seconds disconnected.
How to correct this problem?
Version NetBackup client - 6.5.3 x64, OS - Win 2003 x64
discussion Filed Under:
Comments
Remove PBX from cluster configuration
Symantec recommends not to configure PBX as a clustered resource.
http://support.veritas.com/docs/285594
That technote says 6.0MP4 will fix the problem, but well, why keep weeding when you can remove it's root.
PBX does not consume much resource, and there's no reason it needs to fail over - it can just stay running on both nodes, at all times, as a standalone instance.
So remove PBX from the cluster configuration, make it a standalone service running all times on both nodes.
In the services control panel it will show up as "VERITAS Private Branch Exchange" - make it startup as automatic, and keep it running.
PBX is not worth your headache/time.
Abe
Anger Management
Tnx!
Many thanks!
Can describe in more details how to remove PBX on cluster?
I understand - run cluster admin, select pbx-group-1 and take offline pbxmscs to offline. Next step - select pbx-group-2 and take offline pbxmscs.
What further?
Need remove on cluster admin pbx-clustergroup-node1 and pbx-clustergroup-node2??
Just delete them
It's in the technote - which is quoted again here.
1. It will be necessary to start the Cluster Manager. This can be done by going to Start > All Programs > Administrative Tools > Cluster administrator
2. In the console tree select the Resources folder
3. In the details pane, select the PBX resource
4. From the File menu select Delete
This will remove the PBX resource from the Cluster Manager. The PBX daemons will still be running on all nodes so this work around won't cause any connection issues.
Anger Management
Would you like to reply?
Login or Register to post your comment.