Well that was embarrassing... From: Richard Stovall (RDI) Sent: Monday, June 17, 2013 3:38 PM To: [email protected] Subject: RE: [Exchange] JET_errAttachedDatabaseMismatch
\\sql2008r2prod\To_Process<file:///\\sql2008r2prod\To_Process> From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Michael B. Smith Sent: Wednesday, May 15, 2013 7:56 PM To: [email protected]<mailto:[email protected]> Subject: RE: [Exchange] JET_errAttachedDatabaseMismatch CORRECTION: Move the "2nd to last logfile" up to the last log file to SOMEWHERE else. Do the same thing for E00.log. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Michael B. Smith Sent: Wednesday, May 15, 2013 7:50 PM To: [email protected]<mailto:[email protected]> Subject: RE: [Exchange] JET_errAttachedDatabaseMismatch Ok. Copy the "2nd to last logfile" up to the last log file to SOMEWHERE else. Do the same thing for E00.log. Rename the new highest numbered log file to E00.log. Restore ONLY the EDB file and STM file. Re-run eseutil. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Barrie Russell Sent: Wednesday, May 15, 2013 3:34 PM To: [email protected]<mailto:[email protected]> Subject: Re: [Exchange] JET_errAttachedDatabaseMismatch Hi, Yes to all of the above. In event viewer I watched it replay all of the log files when DPM kicked off the eseutil. Everything looked ok up until the 2nd to last log file when I hit the below error. Even though I am trying to avoid it, I think I may be in for a hard repair on this one. Event Type: Error Event Source: ESE Event Category: Logging/Recovery Event ID: 516 Date: 16/05/2013 Time: 2:28:28 AM User: N/A Computer: QQTEX0601 Description: eseutil (2980) Database F:\ExchangeDatabases\DPM_E2k3_Restore\IT & Managers.edb: Page 901949 (0x000dc33d) failed verification due to a timestamp mismatch. The expected timestamp was 0x4b6fd3bfc but the actual timestamp on the page was 0x4b7029411. Recovery/restore will fail with error -567. If this condition persists then please restore the database from a previous backup. This problem is likely due to faulty hardware "losing" one or more flushes on this page sometime in the past. Please contact your hardware vendor for further assistance diagnosing the problem. For more information, click http://www.microsoft.com/contentredirect.asp. On 16 May 2013 05:12, Michael B. Smith <[email protected]<mailto:[email protected]>> wrote: Does the server name match? Do the file paths match? Do the volume names match? From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Barrie Russell Sent: Wednesday, May 15, 2013 11:53 AM To: [email protected]<mailto:[email protected]> Subject: [Exchange] JET_errAttachedDatabaseMismatch Hi, Had a nasty hardware failure with our ex 2003 sp2 server. Had to do a full DR to new hardware. When I went to restore the databases using DPM 2010 it copies the log files and database files back then tries to start eseutil and fails When I run eseutil /r e00 from the directory I get the above error. Been on this for a while so my google skills are not working as good as they could. Any help on this would be great. Some extra info, eseutil /ml shows no errors The full error text is :- Operation terminated with error -1216 (JET_errAttachedDatabaseMismatch, An outst anding database attachment has been detected at the start or end of recovery, bu t database is missing or does not match attachment info) after 21.203 seconds. eseutil /mh shows a dirty shutdown and the below Initiating FILE DUMP mode... Database: .\IT & Managers.edb File Type: Database Format ulMagic: 0x89abcdef Engine ulMagic: 0x89abcdef Format ulVersion: 0x620,11 Engine ulVersion: 0x620,11 Created ulVersion: 0x620,11 DB Signature: Create time:09/10/2007 09:57:18 Rand:1118040 Compute cbDbPage: 4096 dbtime: 8098820987<tel:8098820987> (0x1e2ba337b) State: Dirty Shutdown Log Required: 568513-568514 (0x8acc1-0x8acc2) Streaming File: Yes Shadowed: Yes Last Objid: 2263652 Scrub Dbtime: 0 (0x0) Scrub Date: 00/00/1900 00:00:00 Repair Count: 0 Repair Date: 00/00/1900 00:00:00 Old Repair Count: 0 Last Consistent: (0x7C3D6,1EF0,10E) 04/14/2013 19:51:59 Last Attach: (0x7C3D6,1F06,16) 04/14/2013 19:57:38 Last Detach: (0x0,0,0) 00/00/1900 00:00:00 Dbid: 3 Log Signature: Create time:07/18/2012 14:56:57 Rand:1323991 Compute OS Version: (5.2.3790 SP 2) Previous Full Backup: Log Gen: 566049-566053 (0x8a321-0x8a325) - OSSnapshot Mark: (0x8A326,8,16) Mark: 05/14/2013 06:13:39 Previous Incremental Backup: Log Gen: 568249-568252 (0x8abb9-0x8abbc) - OSSnapshot Mark: (0x8ABBD,8,16) Mark: 05/14/2013 19:45:12 Current Full Backup: Log Gen: 0-0 (0x0-0x0) Mark: (0x0,0,0) Mark: 00/00/1900 00:00:00 Current Shadow copy backup: Log Gen: 0-0 (0x0-0x0) Mark: (0x0,0,0) Mark: 00/00/1900 00:00:00 cpgUpgrade55Format: 0 cpgUpgradeFreePages: 0 cpgUpgradeSpaceMapPages: 0 ECC Fix Success Count: none Old ECC Fix Success Count: none ECC Fix Error Count: none Old ECC Fix Error Count: none Bad Checksum Error Count: none Old bad Checksum Error Count: none Operation completed successfully in 3.63 seconds. Thanks
