Home / server / Questions / 499606
Accepted
Eric C. Singer
Asked: 2013-04-16 11:21:03 +0800 CST

SQL AlwaysOn auto fail over due to disk

  • 772

All,

I'm in the process of evaluating SQL AlwaysOn, and everything is failing over as expected, except in one circumstance, when the disk goes belly up. In this case, SQL does nothing, other than present the following two errors.

Dash board error as well as when i go to the properties of the DB

The error makes sense, as I've dropped the drive that also contains TempDB, but what concerns me, is dropping the drive doesn't seem to be catastrophic enough to cause a fail over.

Am I missing something here? I tried adding the drive to wsfc, but because its not a clustered drive, it doesn't seem that it will work, as each individuals servers drive shows up as a separate resource.

Edit 1: The only event log entry is as follows. Once again, pretty much an expected error.

The operating system returned error 21(The device is not ready.) to SQL Server during a read at offset 0x00000000382000 in file 'E:\Data\vcdb.mdf'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.

sql

1 Answers

  1. Best Answer

    Losing a database file, even one as critical as the tempdb file, is still a database-level event.

    According to this Microsoft Technet article:

    (Failover and Failover Modes (AlwaysOn Availability Groups) )

    Issues at the database level, such as a database becoming suspect due to the loss of a data file, deletion of a database, or corruption of a transaction log, do not cause an availability group to failover.

    • 2