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

How to find cause of failover Expand / Collapse
Author
Message
Posted Sunday, September 22, 2013 9:34 PM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Friday, July 25, 2014 7:21 AM
Points: 397, Visits: 2,415
Does eventvwr or cluster log clearly shows the reason for a failover?

What's the effective way to find the cause of a failover?


Regards,
SQLisAwe5oMe.
Post #1497259
Posted Monday, September 23, 2013 2:42 PM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Thursday, July 24, 2014 10:24 AM
Points: 373, Visits: 1,235
SQLisAwE5OmE (9/22/2013)
Does eventvwr or cluster log clearly shows the reason for a failover?

What's the effective way to find the cause of a failover?


I would start with the SQL error log, of course. Then you can check Event Viewer.

Both provide very good information about what went wrong and what caused the fail over. For instance, if a LUN went off or got disconnected, most likely you will see iSCSI errors on the Windows Error log followed by SQL errors.

Also, if you have a monitoring system, go back and check historical data there too. I use RedGate monitoring and I can go back in time and review the logs and SQL's health a min before.
Post #1497554
Posted Monday, September 23, 2013 3:26 PM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Friday, July 25, 2014 7:21 AM
Points: 397, Visits: 2,415
Ok, thank you.

Regards,
SQLisAwe5oMe.
Post #1497570
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse