Восстановление базы Exchange 2013 из состояния Dirty Shutdown
Восстановление базы Exchange 2013 из состояния Dirty Shutdown. Исправление грязного отключения — Dirty Shutdown. Виртуальная машина на котором работает Exchange2013 была выключена по питанию. После включения, обнаружил что Outlook не цепляется к базе.. Заходим на сервер смотрим состояния базы:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 |
PS] C:\Windows\system32>Get-MailboxDatabase -status |Select-Object name,Mounted Name Mounted ---- ------- Mailbox Database 0543696474 False my-db False База отключена. Воспользуемся утилитой eseutil [PS] C:\Windows\system32>eseutil /mh "d:\bd\sys01\my-db.edb" Extensible Storage Engine Utilities for Microsoft(R) Exchange Server Version 15.00 Copyright (C) Microsoft Corporation. All Rights Reserved. Initiating FILE DUMP mode... Database: d:\bd\sys01\my-db.edb DATABASE HEADER: Checksum Information: Expected Checksum: 0x44d2a046 Actual Checksum: 0x44d2a046 Fields: File Type: Database Checksum: 0x44d2a046 Format ulMagic: 0x89abcdef Engine ulMagic: 0x89abcdef Format ulVersion: 0x620,20 Engine ulVersion: 0x620,20 Created ulVersion: 0x620,20 DB Signature: Create time:02/02/2015 00:10:51.931 Rand:24188368 cbDbPage: 32768 dbtime: 83297 (0x14561) State: Dirty Shutdown Log Required: 764-764 (0x2fc-0x2fc) Log Committed: 0-764 (0x0-0x2fc) Log Recovering: 0 (0x0) GenMax Creation: 02/12/2015 23:30:06.571 Shadowed: Yes Last Objid: 482 Scrub Dbtime: 0 (0x0) Scrub Date: 00/00/1900 00:00:00 Repair Count: 0 Repair Date: 00/00/1900 00:00:00.000 Old Repair Count: 0 Last Consistent: (0x3E,12,6B8) 02/03/2015 11:53:05.964 Last Attach: (0x3F,2,268) 02/03/2015 11:53:32.511 Last Detach: (0x0,0,0) 00/00/1900 00:00:00.000 Last ReAttach: (0x2FC,2,0) 02/12/2015 23:30:06.884 Dbid: 1 Log Signature: Create time:02/02/2015 00:10:51.696 Rand:37111707 OS Version: (6.1.7601 SP 1 NLS ffffffff.ffffffff) Previous Full Backup: Log Gen: 0-0 (0x0-0x0) Mark: (0x0,0,0) Mark: 00/00/1900 00:00:00.000 Previous Incremental Backup: Log Gen: 0-0 (0x0-0x0) Mark: (0x0,0,0) Mark: 00/00/1900 00:00:00.000 Previous Copy Backup: Log Gen: 0-0 (0x0-0x0) Mark: (0x0,0,0) Mark: 00/00/1900 00:00:00.000 Previous Differential Backup: Log Gen: 0-0 (0x0-0x0) Mark: (0x0,0,0) Mark: 00/00/1900 00:00:00.000 Current Full Backup: Log Gen: 0-0 (0x0-0x0) Mark: (0x0,0,0) Mark: 00/00/1900 00:00:00.000 Current Shadow copy backup: Log Gen: 0-0 (0x0-0x0) Mark: (0x0,0,0) Mark: 00/00/1900 00:00:00.000 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.000 Current checksum start Date: 00/00/1900 00:00:00.000 Current checksum page: 0 Operation completed successfully in 0.47 seconds. |
Видим статус грязного завершения — State: Dirty Shutdown Запускаем восстановление:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 |
[PS] D:\BD\SYS01>eseutil /r E01 /l "D:\BD\SYS01\log" /d "d:\bd\sys01\my-db.edb" Extensible Storage Engine Utilities for Microsoft(R) Exchange Server Version 15.00 Copyright (C) Microsoft Corporation. All Rights Reserved. Initiating RECOVERY mode... Logfile base name: E01 Log files: D:\BD\SYS01\log System files: <current directory> Database Directory: d:\bd\sys01\my-db.edb Performing soft recovery... Restore Status (% complete) 0 10 20 30 40 50 60 70 80 90 100 |----|----|----|----|----|----|----|----|----|----| .................................................X Operation terminated with error -1216 (JET_errAttachedDatabaseMismatch, An outstanding database attachment has been dete cted at the start or end of recovery, but database is missing or does not match attachment info) after 21.844 seconds. |
И тут же получаю… (read more)