Post reply

Database Mirroring Suspended - Could not redo log record.

  • November 20, 2013 at 8:59 am

    #282658

    Hi

    Database Mirroring gets suspended with the following messages on primary and mirror.

    Primary

    Error: 1453, Severity: 16, State: 1.

    'TCP://MirrorServername.office.com:5022', the remote mirroring partner for database 'DBName', encountered error 3456, status 1, severity 21. Database mirroring has been suspended. Resolve the error on the remote server and resume mirroring, or remove mirroring and re-establish the mirror server instance.

    Mirror

    Error: 3456, Severity: 21, State: 1.

    Could not redo log record (6243:413245:13), for transaction ID (0:0), on page (146:6), allocation unit 6488064, database 'DBName' (database ID 14). Page: LSN = (5299:3282119:1), allocation unit = 6488064, type = 16. Log: OpCode = 7, context 24, PrevPageLSN: (5325:42999:7). Restore from a backup of the database, or repair the database.

    Error: 1454, Severity: 16, State: 1.

    Database mirroring will be suspended. Server instance 'MirrorServerName' encountered error 3456, state 1, severity 21 when it was acting as a mirroring partner for database 'DBName'. The database mirroring partners might try to recover automatically from the error and resume the mirroring session. For more information, view the error log for additional error messages.

    Database mirroring is inactive for database 'DB'. This is an informational message only. No user action is required.

    On doing some research I thought the fix was installing SQL 2012 SP1 CU3 as suggested by KB article http://support.microsoft.com/kb/2807974 but even after doing it we are experiencing the same issue with different databases. The one difference is our mirroring mode is synchronous.

    I did run DBCC CHECKDB on this database to make sure this issue is not related to corruption.

    Has anyone experienced this issue before ? Any ideas are appreciated.

    Thanks.

  • November 22, 2013 at 3:41 pm

    #1668555

    Not to scare you, but "Could not redo log record" sounds like Corrupted/Suspect Mirror database to me...(I could be wrong)

    Any traces of Storage Issues,Network issues on your Mirrored server or between these 2 servers? Is the status of End points healthy on both the sites? What's the current status of your Mirror database?

    Did you tried setting up(re-establish) mirroring again from scratch as per it's recommendation?

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply