Still using smsql but are running into an ongoing problem where the largest database comes up in suspect mode on the disaster recovery side. No evidence of any corruption on the source/production database.

Our method is 1) break the mirror ( or it breaks itself if a real DR )

2) bring up DR netapp luns

3) fire up the DR sql failover cluster and the databases come online since they were attached when the cluster was last shut down. In other words most of the time sql is not running in DR.

3456,Server,"Could not redo log record (1741525:1017743:2), for transaction ID (0:0), on page (1:30607705), allocation unit 281474979397632, database 'COLLATERALMANAGER' (database ID 5). Page: LSN = (1741525:942479:31), allocation unit = 281474979397632, type = 1. Log: OpCode = 4, context 18, PrevPageLSN: (1741525:995618:2). Restore from a backup of the database, or repair the database."