We are using the backup agent for SQL Server with Backup Exec which provides for SQL backup/recover, including transaction logs. However, it does not appear to support page level restore.

The DBCC CHECKDB showed the following:

DBCC results for '<table name>'.

Msg 8928, Level 16, State 1, Line 1

Object ID 482100758, index ID 0, partition ID 72057594045202432, alloc unit ID 72057594047168512 (type In-row data): Page (1:1600834) could not be processed. See other errors for details.

Msg 8939, Level 16, State 98, Line 1

Table error: Object ID 482100758, index ID 0, partition ID 72057594045202432, alloc unit ID 72057594047168512 (type In-row data), page (1:1600834). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.

There are 7464070 rows in 192799 pages for object "tblAuthServerLogsLive".

CHECKDB found 0 allocation errors and 2 consistency errors in table 'tblAuthServerLogsLive' (object ID 482100758).

DBCC TRACEON (3604, -1)

GO

DBCC PAGE('database', 1, <page>, 3)

GO

shows that it is the data pages that are corrupt: "Metadata: IndexId = 0"

PAGE HEADER:

Page @0x000000009E6A8000

m_pageId = (1:1600834) m_headerVersion = 1 m_type = 1

m_typeFlagBits = 0x4 m_level = 0 m_flagBits = 0x2208

m_objId (AllocUnitId.idObj) = 141 m_indexId (AllocUnitId.idInd) = 256

Metadata: AllocUnitId = 72057594047168512

Metadata: PartitionId = 72057594045202432 Metadata: IndexId = 0

Metadata: ObjectId = 482100758 m_prevPage = (0:0) m_nextPage = (0:0)

pminlen = 46 m_slotCnt = 73 m_freeCnt = 170

m_freeData = 7876 m_reservedCnt = 0 m_lsn = (10675:655871:253)

m_xactReserved = 0 m_xdesId = (0:0) m_ghostRecCnt = 0

m_tornBits = -1425631195