Microsoft Exchange Server stores all the data related to e-mail communication that includes voice messages, contacts, e-mail messages, notes, tasks, etc. It supports web and mobile based access to information. All these information related to e-mail communication helps in smooth running of any business. At times, information contained within Exchange Server gets damaged or lost due to various reasons. Whatever may be the reasons? All the data contained within Exchange Server becomes inaccessible. In such critical moment, it becomes necessary to recover all the data contained within Exchange Server safely. So, in such case Exchange server recovery
becomes a primary need. Various tools are available that are enough competitive to deal with Exchange Server corruption related situation.
Suppose, when you make an attempt to mount a public store or a mailbox store in MS-Exchange Server 2000, you fail to do so. Additionally, you receive an error message that looks like:
“
The database files in this storage are inconsistent
Id no: c1041739”
Now, after receiving this error message all your data becomes inaccessible.
Cause:
Above error message is caused if the public store database or mailbox store database comes into an inconsistent state.
Solution:
For solving the above problem, you can use the MS-Exchange Server database utility to confirm the database state that is unmount. Then, try to perform repair or restore as per your need. After doing repair or restore, database can mount easily.
Below stated are the steps that will help you to confirm the database state:
- Open command prompt.
- Transfer to Drive:\Program Files\Exchsrvr\Bin folder.
Exchange 2000 Server stores the program files in this folder by default.
- Enter the below command:
eseutil /mh "drive:\program files\exchsrvr\mdbdata\dat
abase_name
.edb"
Database files are stored by default in Drive:\ProgramFiles\Exchsr
vr\MDBDATA
folder. In addition to this, the name of mailbox store database file is "Priv1.edb".
The public store database file is named "Public.edb".
- Review the output to check the database state. If the database is in non-consistent state, the below stated text appears in the output:
State: Dirty Shutdown
When you confirm that the database is in an inconsistent state, try to repair or
restore the database. If you have an updated backup, then try to restore the
database from it. In absence of backup, try to repair the database with the below
steps:
- Open a command prompt.
- Transfer to Drive:\Program Files\Exchsrvr\Bin folder.
- Enter the below command:
eseutil /p "drive:\program files\exchsrvr\mdbdata\dat
abase_file
_name.edb"
- Try to defragment and rebuild the database with the below command:
eseutil /d /t:x "drive:\program files\exchsrvr\mdbdata\dat
abase_file
_name.edb"
- Check the status of the database. Type the below command
eseutil /mh "drive:\program files\exchsrvr\mdbdata\dat
abase_file
_name.edb"
In case of consistent database, the below text appears in the output:
State: Clean Shutdown.
- Try to repair the logical corruption of database with the help of MS-Exchange
server information store integrity utility (Isinteg.exe). For doing the same, enter
the below command at the command prompt:
Isinteg –s exchange_server_name –fix –test alltests
- Perform the steps 3 to 6 for each database.
- Then, mount the databases.
- Once the databases get mount, try to execute an online backup of the storage group.
Comments (0)