Posted on Saturday, October 30, 2010 at 12:03 AM
Microsoft Exchange Server may sometimes report errors when an Exchange-aware backup is running. Not always, but database corruption is the most common reason for a backup failure. You can analyze the exact cause of the problem by the event ID and related error description logging in the application log of Exchange Server. If this comes out to be database corruption, you then need to implement
Exchange Server Recovery methods.
For example, consider the below event ID and backup failure error, which might occur post failure of a backup attempt.
Event ID: 217
Source: ESE
Type: Error
Category: Logging/Recovery
Description:
Error err_num During backup of a database location. The database will be unable to restore.
The symbolic name of the above error is 'BACKUP_ERROR_FOR_ONE_DATABASE'.
Cause
To know the root cause of the given problem, you should check the err_num in description section of the above event. Common reasons for backup failure are described underneath:...
Posted on Wednesday, June 30, 2010 at 1:41 AM
Microsoft Exchange Server is an exchange server that is server-side of the client-server product. It stores all the information of emails, contacts, calendar entries in an EDB (Exchange Information Store Database) file. In addition, you can access Exchange Server using Windows-based mobile devices as well. Sometimes, you are unable to mount the Exchange Server because of EDB file corruption. The reasons that lead to EDB corruption are human errors, database header corruption, virus infections, oversized EDB file. In such cases, you should try to find the cause of corruption and perform appropriate operations to repair corrupt EDB file. If you are unable to do this, then you should use a third-party
EDB recovery software to recover EDB file.
Consider a scenario wherein you are unable to mount the Exchange Store in Exchange Server 2007. An error message is displayed, that is:...
Posted on Tuesday, May 18, 2010 at 4:41 AM
When you install Microsoft Exchange Server 2007, a set of tasks is run to install few services. One of these services is Microsoft Exchange Transport Service, which is a network service responsible for SMTP and transport stack. At times, you observe that the service fails to start. Among other reasons, one root cause of this problem is corruption of ESE ( Extensible Storage Engine) database. This occurs when the corrupted database exists on Edge Transport Server or Hub Transport Server and has been serving as Content Filtering database or message queue database. This clearly means corruption and calls for actions to apply
EDB Recovery solutions.
For more clarification of the issue, let's consider a problem when you attempt to start Microsoft Exchange Transport Service, but fail to do so. Further, on viewing the application log, you encounter the below event ID logging:
Event ID: 17003
Source: MSExchangeTransport
Category: Storage...
Posted on Saturday, April 17, 2010 at 4:43 AM
A storage group in Microsoft Exchange Server Information Store contains one or more mailbox stores, depending on the version of Exchange Server you use and requirements of the organization. Mailbox stores are the most critical components from data preservation perspectives as they comprise of system and user mailboxes. If corrupted, mailbox store causes serious problems in the working of an organization. A mailbox store is further comprised of two files, namely Priv1.edb and Priv1.stm. Corruption usually affects Priv1.edb file and occurs because of typical reasons like, database dirty shutdown, anti-virus software scan, virus infection, and network issues. When corrupted, EDB file on being accessed, prompts errors under a few event IDs, which can be read from application event log. Following is one such event IDs that generally occurs because of database corruption and requires
EDB Recovery solutions...
Posted on Thursday, April 01, 2010 at 2:58 AM
Is your Exchange Server database inaccessible due to corruption of the Information Store? Are you getting Jet Database Engine errors while restoring database from backup? Information Store is the most commonly affected Exchange Server component, when database corruption occurs. Corruption generally occurs in Priv.edb or Pub.edb, that are located in ExchSrvr\Mdbdata directory on server. EDB (Exchange Server Database) is an extension of Exchange Server database file. In case of corruption, the database becomes inconsistent and Exchange Server can not read data from it. It leads to significant data loss situations and needs
EDB Recovery, if you do not have an updated backup in place.
Microsoft Exchange Server indicates Information Store corruption with a number of symptoms, which include:
1. You can not start Microsoft Exchange Server Information Store Service.
2. The Information Store Service can not be stopped...
Posted on Wednesday, February 24, 2010 at 5:15 AM
Are you facing fatal errors while accessing your Microsoft Exchange Server 2007 database? Is your EDB (Exchange Server Database) file is inaccessible? The fatal error in Exchange server aborts the application and thus makes it unusable. This behavior of MS Exchange Server renders all your valuable data inaccessible and cause critical data loss situations. In order to get your precious data recovered in such situations, you need to repair and restore the damaged EDB file, using an
EDB Recovery solutions.
As an example, MS Exchange Server 2007 Management Pack for Operations Manager supervises the MS Windows Application Event log on systems, which are running MS Exchange Server 2007 and returns the below event:
“Product Name: Exchange
Product Version: 8.0 (Exchange Server 2007)
Event ID: 17003
Event Source: MSExchangeTransport
Alert Type: Critical Error...
Posted on Tuesday, February 02, 2010 at 4:38 AM
Unified Messaging (UM) is the integration of various communications media and electronic messaging technologies into a single store, while giving full access from different devices. The unified messaging products for Exchange Server have the capability to store all types of messages (like voicemails, faxes, e-mails etc.) in one system. The UM solutions for Exchange Server require Exchange database to be intact in order to get started. There can be situations when a unified messaging utility may stop. Apart from other reasons, you can deduce this behavior for database corruption. In such situations, if you don't have any valid data backup, an
EDB Recovery solution is required.
The following scenario will help you understand such problems better. Consider you deploy a Unified Messaging system in your Exchange Server environment. You observe that the UM utility cannot start. Later, you observe that Microsoft Exchange database is also unable to mount and reports an error, such as below:...
Posted on Monday, January 18, 2010 at 10:30 PM
Microsoft Exchange Server databases suffer from two type of inconsistencies: Logical and Physical. Logical database corruption is caused due to reasons like deletion of Edb.log file and write-back caching, which generally introduce errors in B-trees and other logical structures. On the other hand, physical database corruption root from hardware failure like reasons that usually affect the database pages. Logical database corruption is hard to be detected by database administrator when compared to physical database corruption. However, at times when Exchange Server tries to read data from a corrupted database, it reports an error (as mentioned further). The corruption can be logical or physical and you need to apply
EDB Recovery techniques to solve these problems.
As an instance, you might receive the below error message with your Exchange Server database:
“msgidJetDatabaseCorrupted.”...
Posted on Wednesday, January 13, 2010 at 5:06 AM
Microsoft Exchange Server Calendaring agent is the tool that allows performing several scheduling tasks, which include creating and saving appointments etc. For the tool to function properly, it is required that Exchange directory structure remains excluded from antivirus scanning. Another disadvantage of scanning your Exchange Server directory structure is that it may also lead to corruption of the most important files in your Information Store, such as .edb, .stm, .chk, and .log files. Since most of your important data resides in your .edb files,
EDB Recovery becomes essential while such instances.
To illustrate such scenarios with Calendaring agent, suppose you try to save few appointments in MS Exchange Server. Your observe that Calendaring agent fails to function properly. Some or all of the calendar information are lost. Additionally, you receive the similar entries logging in application event log of Exchange Server:
Event ID: 8206...
Posted on Tuesday, December 08, 2009 at 11:08 PM
Transaction log files contain the uncommitted data of an Exchange database. When an EDB (Exchange database) file crashes, the transaction log files act as disaster recovery means as they bring the database to a consistent state. For these reasons, it is recommended to store transaction logs on a different drive to avoid disk failure consequences that can affect the database. At times, Exchange Server observes issues when writing data to the drive where log files are stored. This can occur out of several reasons, such as file system issues, antivirus software problems, disk concerns etc. You need to troubleshoot the root cause. However, if the database is still inconsistent, you should restore the damaged database from backup or apply Exchange eseutil tool. Alternatively, you can opt for using an
EDB Recovery Software to repair the damaged database.
For example, you might receive the below error with your Exchange Server:...
