1) Überprüfen mit ESEUTIL /MH – Datenbank integrität
F:\ExchangeData\Priv2012>eseutil /MH "Mailbox Database 2.edb"
Extensible Storage Engine Utilities for Microsoft(R) Exchange Server
Version 14.02
Copyright (C) Microsoft Corporation. All Rights Reserved.
Initiating FILE DUMP mode...
Database: Mailbox Database 2.edb
DATABASE HEADER:
Checksum Information:
Expected Checksum: 0x0b8404d4
Actual Checksum: 0x0b8404d4
Fields:
File Type: Database
Checksum: 0xb8404d4
Format ulMagic: 0x89abcdef
Engine ulMagic: 0x89abcdef
Format ulVersion: 0x620,17
Engine ulVersion: 0x620,17
Created ulVersion: 0x620,17
DB Signature: Create time:01/27/2012 04:00:51 Rand:2319548 Computer:
cbDbPage: 32768
dbtime: 43394155 (0x296246b)
State: Clean Shutdown
Log Required: 0-0 (0x0-0x0)
Log Committed: 0-0 (0x0-0x0)
Log Recovering: 0 (0x0)
GenMax Creation: 00/00/1900 00:00:00
Shadowed: Yes
Last Objid: 8712
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: (0x7B81,285,35) 10/18/2012 22:18:35
Last Attach: (0x52F3,9,86) 07/26/2012 23:41:40
Last Detach: (0x7B81,285,35) 10/18/2012 22:18:35
Dbid: 1
Log Signature: Create time:01/27/2012 04:00:51 Rand:2343915 Computer:
OS Version: (6.1.7601 SP 1 NLS ffffffff.ffffffff)
Previous Full Backup:
Log Gen: 27194-27197 (0x6a3a-0x6a3d) - OSSnapshot
Mark: (0x6A3E,8,16)
Mark: 10/18/2012 08:41:43
Previous Incremental Backup:
Log Gen: 0-0 (0x0-0x0)
Mark: (0x0,0,0)
Mark: 00/00/1900 00:00:00
Previous Copy Backup:
Log Gen: 0-0 (0x0-0x0)
Mark: (0x0,0,0)
Mark: 00/00/1900 00:00:00
Previous Differential Backup:
Log Gen: 0-0 (0x0-0x0)
Mark: (0x0,0,0)
Mark: 00/00/1900 00:00:00
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
Last checksum finish Date: 00/00/1900 00:00:00
Current checksum start Date: 00/00/1900 00:00:00
Current checksum page: 0
Operation completed successfully in 0.78 seconds.
2) Überprüfen mit ESEUTIL /K – Checksummen prüfen
F:\ExchangeData\Mailbox\V14>eseutil /k "Mailbox Database 0201847403.edb"
Extensible Storage Engine Utilities for Microsoft(R) Exchange Server
Version 14.02 Copyright (C) Microsoft Corporation. All Rights Reserved.
Initiating CHECKSUM mode...
Database: Mailbox Database 0201847403.edb
Temp. Database: TEMPCHKSUM13292.EDB
File: Mailbox Database 0201847403.edb
Checksum Status (% complete)
0 10 20 30 40 50 60 70 80 90 100
|----|----|----|----|----|----|----|----|----|----|
.............................................ERROR: page 13403094 checksum failed......
14656162 pages seen 1 bad checksums 0 correctable checksums 34414 uninitialized pages 0 wrong page numbers
0x9419d99e highest dbtime (pgno 0x159) 7328081 reads performed 458005 MB read 1457 seconds taken 314 MB/second
1492032627 milliseconds used 203 milliseconds per read 3391 milliseconds for the slowest read 0 milliseconds
for the fastest read Operation terminated with error -1206
(JET_errDatabaseCorrupted, Non database fi le or corrupted db) after 1457.406 seconds.
3) Defragmentieren mit ESEUTIL /d
So wird die DB kleiner und falls der Fehler im „free space“ liegt, wird der Fehler automatisch behoben.
D:\ExchangeData\Mailbox\V14>eseutil /d "Mailbox Database 0201847403.edb"
Extensible Storage Engine Utilities for Microsoft(R) Exchange Server
Version 14.02 Copyright (C) Microsoft Corporation. All Rights Reserved.
Initiating DEFRAGMENTATION mode...
Database: Mailbox Database 0201847403.edb
Defragmentation Status (% complete)
0 10 20 30 40 50 60 70 80 90 100
|----|----|----|----|----|----|----|----|----|----| .
Bei dem VMware 4.1 Update Manager kann es vorkommen, dass nach einem Reboot des ESXi Hosts jegliche Abfrage betreffend Updates mit dem Fehler 99 beantwortet werden.
