Disable iSCSI Networks for DAGs
If you have Exchange 2010 DAGs and you use iSCSI to present those servers with storage for the databases, you must ensure the DAG does not use this network. (more…)
If you have Exchange 2010 DAGs and you use iSCSI to present those servers with storage for the databases, you must ensure the DAG does not use this network. (more…)
Recently, a reader of the website came to me with a question- “You explained in detail on how to perform various operations to recover data from an exchange database “which is great”. But, what exactly repair (eseutil /p) processes do? (more…)
Have you ever imagined the background processes involved in storing your email message in an exchange database? The process involved in the creation of transaction log files? How does “The famous Store.exe”- Microsoft Exchange Information Store service function and what is its significance? Keep reading…. (more…)
With Exchange 2007 and older versions, one of the key elements that an Exchange administrator needed to keep an eye on, and caused confusion for newcomers to Exchange was the amount of white space in the database. (more…)
This article outlines the process of putting your DAG members in maintenance mode prior to any activity. (more…)
This post address an issue where the index status shows status “failed” with Exchange 2010 DAG (more…)
Ratish post here has already detailed about Named Props Quota and the trouble it creates for the Admins in Exchange 2003 and 2007 and so, I am not going to dive into it now. But the good news is that Exchange 2007 SP1 RU7 and Exchange 2007 SP2 has got in some improvements, but at the same time, not with problems.
Exchange 2007 restore process fails with the following error -939586631 (more…)
This article outline’s the steps to restore an exchange database in Exchange 2010, christened Recovery Database for DAG. (more…)
In Exchange, it a known issue that we cannot mount or restore database of one server to another. The Database Portability feature in makes it possible in Exchange 2007 but for Exchange 2003 there is a procedure to tackle this situation.
