Exchange 2010 数据库异常关闭

Exchange 2010 数据库异常关闭

我们遇到了一次电源故障,在我启动服务器后,邮箱数据库处于异常关闭状态。

我已经跑了

eseutil /r E00

并得到

PS E:\BACKUPS_MDB_EXCHANGE\Mailbox Database 1773415643> eseutil /r E00

Extensible Storage Engine Utilities for Microsoft(R) Exchange Server
Version 14.00
Copyright (C) Microsoft Corporation. All Rights Reserved.

Initiating RECOVERY mode...
    Logfile base name: E00
            Log files: <current directory>
         System files: <current directory>

Performing soft recovery...
                      Restore Status (% complete)

          0    10   20   30   40   50   60   70   80   90  100
          |----|----|----|----|----|----|----|----|----|----|
          .........................



Operation terminated with error -567 (JET_errDbTimeTooNew, dbtime on page in advance of the dbtimeBefore in record) afte
r 0.936 seconds.

然后我就跑eseutil /ml E00

PS E:\BACKUPS_MDB_EXCHANGE\Mailbox Database 1773415643> eseutil /ml E00

Extensible Storage Engine Utilities for Microsoft(R) Exchange Server
Version 14.00
Copyright (C) Microsoft Corporation. All Rights Reserved.

Initiating FILE DUMP mode...

Verifying log files...
     Base name: E00

      Log file: E:\BACKUPS_MDB_EXCHANGE\Mailbox Database 1773415643\E000004C9FE.log - OK
      Log file: E:\BACKUPS_MDB_EXCHANGE\Mailbox Database 1773415643\E00.log - OK

No damaged log files were found.

Operation completed successfully in 0.436 seconds.

于是我尝试运行eseutil /p 'Mailbox Database',运行完成后它仍然处于某种Dirty Shutdown状态。

以下是输出eseutil /mh 'Mailbox Database'

PS E:\BACKUPS_MDB_EXCHANGE\Mailbox Database 1773415643> eseutil /mh '.\Mailbox Database 1773415643.edb'

Extensible Storage Engine Utilities for Microsoft(R) Exchange Server
Version 14.00
Copyright (C) Microsoft Corporation. All Rights Reserved.

Initiating FILE DUMP mode...
         Database: .\Mailbox Database 1773415643.edb


DATABASE HEADER:
Checksum Information:
Expected Checksum: 0x1683ef3b
  Actual Checksum: 0x1683ef3b

Fields:
        File Type: Database
         Checksum: 0x1683ef3b
   Format ulMagic: 0x89abcdef
   Engine ulMagic: 0x89abcdef
 Format ulVersion: 0x620,17
 Engine ulVersion: 0x620,17
Created ulVersion: 0x620,17
     DB Signature: Create time:11/10/2012 16:34:35 Rand:62691655 Computer:
         cbDbPage: 32768
           dbtime: 511641873 (0x1e7f0911)
            State: Dirty 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: 113713
     Scrub Dbtime: 0 (0x0)
       Scrub Date: 00/00/1900 00:00:00
     Repair Count: 4
      Repair Date: 11/10/2012 16:34:35
 Old Repair Count: 0
  Last Consistent: (0x0,0,0)  00/00/1900 00:00:00
      Last Attach: (0x0,0,0)  11/10/2012 16:34:35
      Last Detach: (0x0,0,0)  00/00/1900 00:00:00
             Dbid: 1
    Log Signature: Create time:00/00/1900 00:00:00 Rand:0 Computer:
       OS Version: (6.0.6002 SP 2 NLS 500100.50100)

Previous Full Backup:
        Log Gen: 0-0 (0x0-0x0)
           Mark: (0x0,0,0)
           Mark: 00/00/1900 00:00:00

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: found (16)
   Last ECC Fix Success Date: 11/10/2012 14:49:50
   Old ECC Fix Success Count: found (16)
         ECC Fix Error Count: none
     Old ECC Fix Error Count: none
    Bad Checksum Error Count: found (678)
Last Bad Checksum Error Date: 11/10/2012 11:55:55
Old bad Checksum Error Count: found (678)

  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 1.107 seconds.

这是我第一次遇到这种情况,我该如何解决这个问题并能够再次安装数据库?

答案1

解决方案 1

1.:复制 EDB 文件

2.:然后针对数据库的工作副本运行 eseutil /P,完成后如果没有任何错误消息,则运行 eseutil /D

C:一旦您能够安装数据库,请创建新数据库并将所有邮箱从修复的 EDB 移动到新创建的数据库

解决方案 2:
如果上述步骤对你不起作用,创建拨号音恢复让您的电子邮件再次畅通,然后您可以使用第三方工具打开损坏的数据库并将邮箱恢复到拨号音数据库中。

相关内容