John Yassa's Blog

Home » Exchange 2016

Category Archives: Exchange 2016

HOW TO RESTORE THE EXCHANGE DATABASE FROM A BACKUP FILE IN STATE OF INCONSISTENCY?

How to Restore the Exchange Database from A Backup File in state of inconsistency?

For restoring the database on Exchange Server, the user needs to have an up-to-date and usable backup in hand, because an incomplete or even no backup can create a troublesome situation during the database the process of restoration. Additionally, Microsoft Information Store needs to be in a healthy state to mount the database successfully.

With an unmounted Exchange Store, the users face several issues such as restricted access to the data and the mail flow. In order to smoothly restore your database on Exchange Server, it is important to perform certain tests to verify the database consistency.

Pre-assessment Phase: Verify the State of the Database on Exchange

Use the following steps to verify the state of the database:

  1. Launch a command prompt.
  2. Move to the Drive:\Program Files\Exchsrvr\Bin

(The default location of the of Exchange 2000 Server program files are located in this folder)

 

Move to Drive:\Program Files\Microsoft\Exchange Server\V15\Bin

(When using Exchange 2013/2016, then use the above-mentioned default path)

 

  1. Enter the below-mentioned command:

eseutil /mh “drive:\program files\exchsrvr\mdbdata\database_name.edb”

Note: The default location of database files is on this Drive:\Program Files\Exchsrvr\MDBDATA folder. The public database file can be found with the name: “Public.edb”, whereas the mailbox store database file can be found with the name: “Priv1.edb”.

  1. Read the Output, in order to verify the state of the database. If the database appears in the state of inconsistency, then the output will appear, as:

State: Dirty Shutdown

Restoration Phase: How to Restore the database from a backup file

Upon using the pre-assessment phase, if the database appears in a consistent state, then simply restore the backup using the file.

Steps to Restore Database in A Consistent State:

Implement the following steps to restore the database from the backup file.

  1. Transfer the E00.log file to an another path or simply rename it.

The default location of E00.log file can be found on this Drive:\Program Files\Exchsrvr\MDBDATA folder.

  1. Restore the storage group and the log files from the backup file.

Note: Do not remove the existing log files, until you have performed the restore operation. Upon completing the restore operation, the log files are restored, and replay inside the restored database. This is how, the user can bring the database into a consistent state without involving the E00.log file.

  1. Once the storage group is restored, you can successfully mount the databases in the storage group.

Steps to Restore Database in an Inconsistent State:

  1. Launch the command prompt.
  2. Reach to the location – Drive:\Program Files\Exchsrvr\Bin folder.
  3. Enter the following command in the command prompt:

eseutil /p “drive:\program files\exchsrvr\mdbdata\database_file_name.edb”

  1. To use the database in a productive environment, try to defragment and then rebuild the database. Use the below mentioned command to proceed:

eseutil /d /t:x “drive:\program files\exchsrvr\mdbdata\database_file_name.edb”

Note: ‘x’ is a temporary drive location in the above-mentioned command.

  1. To determine the state of the database, enter the following command, and then read the output:

eseutil /mh “drive:\program files\exchsrvr\mdbdata\database_file_name.edb”

When database is consistent, the output will appear, as:

State: Clean Shutdown

  1. Use the Microsoft’s Store Integrity utility (Isinteg.exe) to fix the logical corruption issues in the database. Use the following commands to repair it:

Isinteg –s exchange_server_name –fix –test alltests

After executing the command, the user is prompted to choose the database in the utility. Repeat the aforementioned command until no errors or fixes are appeared in the output.

However, if zero errors are not displayed for a database that  you want to repair, then the other option is to rebuild the database. To do that create a new mailbox store on either the existing Exchange server or new server and then transfer all the mailboxes to that one. However, if you are still unable to create a new mailbox store, then try to rebuild the database from the following method. To do it, try to export all mailbox information to PST files, and delete the database, and finally import the data.

  1. Repeat the steps from 3 to 6 for each database in the storage group.
  2. Mount the databases.

Once the database is restored and you can also perform an online backup of the storage group. However, if the database is not restored or rebuilt in the state of inconsistency, then try using a third-party Exchange recovery software like Kernel for Exchange Server to perform accurate recovery of lost information from corrupt EDB and STM files, and without requiring log files. The Exchange mailbox items can be successfully restored to live Exchange Server, Office 365 mailbox or to Outlook PST files.

https://www.kerneldatarecovery.com/exchange-server-recovery.html

Article Summary:

When Exchange database creates mounting troubles, then try to investigate the issues hampering the restore operation. Verifying the shutdown state (whether consistent or inconsistent) of the database becomes important, and Eseutil can be helpful in this scenario, but with certain restrictions.

Exchange 2016 RTM is finally here

Microsoft has released Exchange Server 2016 RTM, available for download now. A public preview of Exchange Server 2016 has been available for customers to test and evaluate since July 2015.

You can download from here : Exchange server 2016 RTM

 

Microsoft Exchange Server 2016 – Preview

Microsoft Exchange Server 2016 brings a new set of technologies, features, and services to Exchange Server. Its goal is to support people and organizations as their work habits evolve from a communication focus to collaboration. Exchange Server 2016 helps lower the total cost of ownership whether you deploy on-premises or provision your mailboxes in the cloud. This release is not approved for production use and should be installed in a lab environment only.

Supported Operating System

Windows Server 2012, Windows Server 2012 R2

.Net Framework: 4.5.2 Internet Explore 11, Microsoft Edge, Apple Safari (Latest), Google Chrome (Latest), Mozilla Firefox          (Latest)

Install Instruction

  1. Click the Download button on this page to start the download.
  2. Do one of the following:
    • To start the installation immediately, click Open or Run this program from its current location.
    • To copy the download to your computer for installation at a later time, click Save or Save this program to disk.

Download: Microsoft Exchange Server 2016 – Preview

More Info: Exchange 2016 (preview) now available for testing

 

Overview on Exchange 2016

The below is preliminary information and subject to change before the first release of Exchange server 2016

1- The Block Architecture:

In Exchange 2013 , there were 2 blocks (CAS – MBX) , these both blocks has been merged in Exchange 2016 , there is a single building block that provides the client access services and the high availability architecture necessary for any enterprise messaging environment.

1

The Mailbox server role now:

  1. Houses the logic to route protocol requests to the correct destination endpoint.
  2. Hosts all of the components and/or protocols that process, render and store the data.

No clients connect directly to the back-end endpoints on the Mailbox server; instead, clients connect client access services and are routed (via local or remote proxy) to the Mailbox server that hosts the active database that contains the user’s mailbox.

DAGs in Exchange Server 2016 do have a few specific enhancements:

  1. DatabaseAvailabilityGroupIpAddresses is no longer required when creating a DAG. By default, the failover cluster will be created without an administrative access point, as this is the recommended best practice.
  2. Replay Lag Manager is enabled by default.
  3. Lagged database copy play down can be delayed based on disk latency, thereby ensuring active users are not impacted.
  4. Database failovers times are reduced by 33% when compared to Exchange Server 2013.

Communication between servers still occurs at the protocol layer, effectively ensuring that every server is an island. For a given mailbox’s connectivity, the protocol being used is always served by the protocol instance that is local to the active database copy.

2

 

The load balancer configuration is also not affected by this architectural change. From a protocol perspective, the following will happen:

  1. A client resolves the namespace to a load balanced virtual IP address.
  2. The load balancer assigns the session to a Mailbox server in the load balanced pool.
  3. The Mailbox server authenticates the request and performs a service discovery by accessing Active Directory to retrieve the following information:
    1. Mailbox version (for this discussion, we will assume an Exchange 2016 mailbox)
    2. Mailbox location information (e.g., database information, ExternalURL values, etc.)
  4. The Mailbox server makes the decision to proxy the request or redirect the request to another Mailbox server in the infrastructure (within the same forest).
  5. The Mailbox server queries an Active Manager instance that is responsible for the database to determine which Mailbox server is hosting the active copy.
  6. The Mailbox server proxies the request to the Mailbox server hosting the active copy

3

 2- Search Improvements

One of the challenging areas for on-premises environment was the amount of data that was replicated with each database copy in previous releases. In Exchange Server 2016, we have reduced bandwidth requirements between the active copy and a passive copy by 40%. This was accomplished by enabling the local search instance to read data from its local database copy. As a result of this change, passive search instances no longer need to coordinate with their active counterparts in order to perform index updates.

Another area of investment in search has been around decreasing the length of time to return search results, especially in online mode clients like OWA. This is accomplished by performing multiple asynchronous disk reads prior to the user completing the search term, which populates the cache with the relevant information, providing sub-second search query latency for online mode clients.

 

3- Document Colloboration

In previous releases of Exchange, OWA included document preview for Office and PDF documents, reducing the need to have a full fidelity client. SharePoint had a similar feature, however it used the Office Web Apps Server to accomplish this capability. Within Office 365, we also leverage Office Web Apps Server to provide this capability, ensuring uniform document preview and editing capability across the suite.

In Exchange Server 2016, we leverage Office Web Apps Server to provide the rich document preview and editing capabilities for OWA. While this was a necessary change to ensure a homogenous experience across the Office Server suite, this does introduce additional complexity for environments that don’t have Office Web Apps Server.

 

4- Outlook Connectivity

Introduced in Exchange Server 2013 Service Pack 1, MAPI/HTTP is the new standard in connectivity for Outlook. In Exchange Server 2016, MAPI/HTTP is enabled by default. In addition, Exchange Server 2016 introduces per-user control over this connectivity model, as well as, the ability to control whether the protocol (and Outlook Anywhere) is advertised to external clients.

 

Topology Requirements

Exchange Server 2016 will only be supported on Windows Server 2012 R2 and Windows Server “10” operating systems.

From an Active Directory perspective, Exchange Server 2016 will require:

  • Windows Server 2008 R2 or later Active Directory servers.
  • Windows Server 2008 R2 or higher Forest Functional Mode and Domain Functional Mode.

Exchange Server 2016 will only support coexistence with Exchange Server 2010 SP3 RU11* and Exchange Server 2013 CU11* (*subject to change).

These are the main improvements and enhancements that exist in the new version of Exchange

Resources and more Information at : Exchange Team Blog & Exchange 2016 Ignite Video

%d bloggers like this: