Blog

Disaster Recovery is completely based on the particular data which is now available. Through which the users can easily recover an Exchange Server. This information is only available in any of this desired Domain Controller which is reached at the end of the recovery time. Exchange Configuration data is also available on a Domain Controller under the Configuration Partition. Microsoft Exchange 2013 Disaster Recovery cannot be possible when there is only one Exchange Server available which is also a Domain Controller. It is always the best way to have running Exchange Server within the member server. This is only applicable for Exchange Server 2003, 2007, 2010 and 2013 versions. Although the following steps to recover Exchange 2013 is the little bit different, however in this way the concept remains same. Therefore, in the below section, we are going to discuss the multiple prerequisites and the overall procedure to perform Microsoft Exchange 2013 Disaster Recovery.

In this article, we will discuss various methods to migrate EDB to PST. EDB is an Exchange Database file formatted using a B-tree structure that stores rich text data like MAPI, SMTP and HTTP messages in MS Exchange. On the other hand, PST is a personal folder file in Microsoft Outlook that stores data like emails messages, calender, reminders and everything in Outlook on user’s computer.

The Error 1022 JET errDiskIO usually occurs due to disk input/output failure. So, whenever the Exchange Server requests for the database page but due to some reason the operating system is unable to get the access to that particular page and the error occurs. In this case, Server will make a request for a page number which is greater than the number of pages in that database file. This error can also occur if some incomplete transaction log set is being replayed in the database. For instance, if a transaction is running on log 9 but the transaction could not be completed because it might have exceeded the database size but after that, the page reference size has now been added to log 10. Because of this, it leads to the error 1022.

Exchange Server saves a large amount of data in EDB (Exchange database) file. Many a time, EDB gets corrupt which in turn makes the database inaccessible. There are several reasons behind EDB file corruption i.e. unexpected shutdown, power outage, virus infection. In this post, we will discuss one of the frequently occurring issue – Exchange database Dirty Shutdown and Eseutil to fix it.

Every so often, Exchange Server produces an error message 501 jet_errlogfilecorrupt. The error mainly occurs when Exchange log files got corrupt or damaged. Transaction log files have their own importance in Exchange Server as they are widely used by administrators to recover inconsistent Exchange database.