cancel
Showing results for 
Search instead for 
Did you mean: 

Cluster failover

Former Member
0 Kudos

I have a couple of clusters producing unexpected behaviour. The problem is the same for both.

Two nodes in the cluster, all resources are on Node A. SAP section of the cluster fails over to Node B for no apparent reason, SQL stays on A.

Node A and Node B can see each other no problem. However, users cannot connect to the B Node, only A.

Node B doesn't failback and if you try to make it by using Move Group it fails and switches back to Node B.

To make it move back you have to shut SAP on Node B and Node A. It will then let you move it back.

Any help or advice much appreciated.

David

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Thank you the quick response.

Following some greater investigation into the Event logs I think this may not be a SAP issue after all but rather a Windows/Cisco issue with the Shares timing out.

David

Former Member
0 Kudos

that are two problems:

1. unexpected failover

2. move back to A did not work

I need a little more information for getting the right answers.

- SAP release

- what did you find in the system log (event viewer, system)

- assuming you are running on 2003 output of tasklist.exe on A before you move the resource back to A.

peter

Rudi_Wiesmayr
Active Participant
0 Kudos

First response question: What do the windows logs say?