Hi all,
We have a pretty significant issue with database mirroring (which we use for disaster recovery) that infrequently it will simply break and we will need to break the mirror, restore from a backup (which is significant because our database is very large) and resume the mirror.
The relevant log information is:
7:17:09 PM The mirroring connection to "TCP://principal:5022" has timed out for database "OurDB" after 10 seconds without a response. Check the service and network connections.
7:18:29 PM SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 2061:21; actual 0:0). It occurred during a read of page (2061:21) in database ID 5 at offset 0x0000000002a000 in file 'D:\SQLDatabases\OurDBP2061.mdf'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe 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.
7:18:35 PM SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 2061:12; actual 0:0). It occurred during a read of page (2061:12) in database ID 5 at offset 0x00000000018000 in file 'D:\SQLDatabases\OurDBP2061.mdf'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe 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.
(2-3 more of those style errors)
7:19:47 PM Could not redo log record (20047:189564:2), for transaction ID (0:175281756), on page (2061:1), allocation unit 72057598006525952, database 'OurDB' (database ID 5). Page: LSN = (20039:168473:1), allocation unit = 6488064, type = 11. Log: OpCode = 4, context 11, PrevPageLSN: (20045:169871:6). Restore from a backup of the database, or repair the database.
Now the mirror is in a suspended state and we are in the process of doing a full backup and restore. As you can see, a few of our database tables are partitioned. The vast majority of the time the mirror works fine; however, when it does break, it poses a large risk to the business in that we effectively have no disaster recovery for quite a few hours while the latest full backup and transaction logs are transferred to the mirror and restored.
Can anyone suggest why this is occurring and if not, if there is anything we can do to "repair" the mirror database without needing a full backup restored?
Appreciate the assistance.