In MS Exchange Server Logical corruption is a common problem. It could occur due to corruption problems with the following components:
==> Information Store
==> Tables
==> Keys
==> Indexes
==> sometimes to whole database.
Logical corruption is more problematic as it is difficult to identify than the physical database corruption. The Server administrator and users are generally do not aware of logical corruption incidence. Unluckily Exchange Server also have not any in-built utility to diagnose it.
Causes of Logical Database Corruption:
A) Deletion of Edb.log File
B) Write Back Cache:
C) Repairing EDB using Eseutil /p
Logical corruption in Exchange Server might also take place when you apply Eseutil /p command to perform jet level repair. It may cause loss of data and incompetent space used in database as the repair fixes the EDB by removing the corrupted data.
For the Identification of logical corruption, you need to regularly perform integrity check (Isinteg –fix) or inconsistency check (Eseutil /mh).
Due to logical database corruption, the ultimate result would be the inaccessible Exchange Server database and the loss of your valuable data. To access your valuable data it is very important to perform EDB recovery by using a third party exchange recovery tool like Stellar Phoenix Mailbox Exchange Recovery software, specifically designed to repair and restore your damaged or corrupted exchange database file.
Stellar Phoenix Mailbox exchange recovery tool is the robust EDB repair software, supports Microsoft Exchange Server 5.5, 2000, 2003 and 2007. It can recover deleted user mailboxes and all of the database objects like mails, attachments, calenders, folders and Tasks etc.
==> Information Store
==> Tables
==> Keys
==> Indexes
==> sometimes to whole database.
Logical corruption is more problematic as it is difficult to identify than the physical database corruption. The Server administrator and users are generally do not aware of logical corruption incidence. Unluckily Exchange Server also have not any in-built utility to diagnose it.
Causes of Logical Database Corruption:
A) Deletion of Edb.log File
B) Write Back Cache:
C) Repairing EDB using Eseutil /p
Logical corruption in Exchange Server might also take place when you apply Eseutil /p command to perform jet level repair. It may cause loss of data and incompetent space used in database as the repair fixes the EDB by removing the corrupted data.
For the Identification of logical corruption, you need to regularly perform integrity check (Isinteg –fix) or inconsistency check (Eseutil /mh).
Due to logical database corruption, the ultimate result would be the inaccessible Exchange Server database and the loss of your valuable data. To access your valuable data it is very important to perform EDB recovery by using a third party exchange recovery tool like Stellar Phoenix Mailbox Exchange Recovery software, specifically designed to repair and restore your damaged or corrupted exchange database file.
Stellar Phoenix Mailbox exchange recovery tool is the robust EDB repair software, supports Microsoft Exchange Server 5.5, 2000, 2003 and 2007. It can recover deleted user mailboxes and all of the database objects like mails, attachments, calenders, folders and Tasks etc.
0 comments:
Post a Comment