Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SQL Server Cluster failing over but not showing databases Expand / Collapse
Author
Message
Posted Monday, June 15, 2009 9:22 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, July 20, 2012 1:34 AM
Points: 3, Visits: 45
Hi,

I have an issue on my cluster at the moment. I wanted to replace my old passive node on the cluster with a new box which was exactly the same as the current box in production however fell into quite a hurdle. What happened was the new node was put into the cluster fine it could see all the drives from the san and failed over perfectly, however it just could not see any of hte databases. I confirmed sql and windows were the same and could fail from one node to the other very easily.

I have a feeling it had something to do with the quorum but can not be 100% sure. It was as if this new node on the cluster was working as a standalone server. I even tested it by creating a new database while the new box was the passive node and then failed over to the old box (which was working fine) and could not see the database. I also tried removing it from the cluster and adding it in again however all it could see was the same test database that i created?

Has anyone ever come across this issue?


Cheers
Post #735417
Posted Monday, June 15, 2009 9:59 PM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Wednesday, September 17, 2014 7:34 PM
Points: 93, Visits: 327
Hi,

So from your question what I understood is as below.

1) Initially we were having 2 node cluster Node A & Node B.
Node A was active and Node B was passive. We replaced Node B
with a new Physical machie alltogether.
2) We make it part of Windows Cluster (with same name everything
same as previous).
3) We evict Node B from the SQL Server Cluster and then add this
new Node. Everything (means setup) went well.
4) Right now we are not able move SQL Database to newly added
Node.

Please let me know if its correct. If yes then I would say lets have a look to below logs:

Cluster Log (Both Nodes)
Application Event Logs (Saved in Text Delimited Format) (Both Nodes)
System Event Logs (Saved in Text Delimited Format) (Both Nodes)
SQL Server/SQL Agent Logs

We can collect MPSReports for SQL As well for this thing (from both nodes).

Regards
GURSETHI
Post #735421
Posted Monday, June 15, 2009 10:08 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, July 20, 2012 1:34 AM
Points: 3, Visits: 45
Hi Gursethi,

1,2 and 3 were correct however 4 is incorrect. I could fail over and move sql server and the agent over to the new box however when i connected the box from sql management studio I could not see any of the databases,jobs, procs etc that I could see with the other node that was in production from the start.

In the application and event logs there are no problems or errors because the failover runs smoothly however I just can not see the databases.

Cheers

Rohit

ps. I hope taht makes sense. This is why I dont think it was a cluster issue but more of a quorum issue?

GURSETHI (6/15/2009)
Hi,

So from your question what I understood is as below.

1) Initially we were having 2 node cluster Node A & Node B.
Node A was active and Node B was passive. We replaced Node B
with a new Physical machie alltogether.
2) We make it part of Windows Cluster (with same name everything
same as previous).
3) We evict Node B from the SQL Server Cluster and then add this
new Node. Everything (means setup) went well.
4) Right now we are not able move SQL Database to newly added
Node.

Please let me know if its correct. If yes then I would say lets have a look to below logs:

Cluster Log (Both Nodes)
Application Event Logs (Saved in Text Delimited Format) (Both Nodes)
System Event Logs (Saved in Text Delimited Format) (Both Nodes)
SQL Server/SQL Agent Logs

We can collect MPSReports for SQL As well for this thing (from both nodes).

Regards
GURSETHI
Post #735424
Posted Monday, June 15, 2009 10:51 PM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Wednesday, September 17, 2014 7:34 PM
Points: 93, Visits: 327
Cool,

Thanks for this information. Now further to it are we able to connect to Master thru Query Window and run SELECT * FROM SYS.SYSPROCESSES?

In the output are we able to see databases names or not?


Regards
GURSETHI
Post #735444
Posted Monday, June 15, 2009 10:58 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, July 20, 2012 1:34 AM
Points: 3, Visits: 45
Hi mate,

Thanks for the quick response, no we cant see the databases through that query as well?

Cheers

GURSETHI (6/15/2009)
Cool,

Thanks for this information. Now further to it are we able to connect to Master thru Query Window and run SELECT * FROM SYS.SYSPROCESSES?

In the output are we able to see databases names or not?


Regards
GURSETHI
Post #735450
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse