Recovery Database in Exchange Server 2013

In the previous two article we have learnt how to Backup and Restore Exchange Server 2013 database using Windows Server Backup. In this article we would be focusing on how to create Recovery Database (Aka RDB).

It is very important to understand in what scenario RDB can be useful. Lets first understand the scenario.

1. A user has deleted some important emails and that needs to be recovered. Without restoring the data to production we would be creating RDB.
2. Single Mailbox or the entire database needs to be restored. Etc.

Note :- In both the scenario the database has crossed the default retention limit.

To know how to backup Exchange Server 2013 using Windows Server Backup 2012. Please follow the below article.

How to Backup Exchange Server 2013 Database – Part 1

To know how to restore the Data from Backup. Please follow the below article.

How to Restore Exchange Server 2013 Database – Part 2

=====================================================

We will be using the same database which was restored. Before creating RDB we will first understand the database health.

Figure 1.1 : Restored Data.

Now since the database is restored we have to confirm if the data is clean shutdown. To do that we will be running ESEUTIL commands.

Figure 1.2 : State : Dirty Shutdown

In figure 1.2 since the database was restored. It will be always be in “Dirty Shutdown”. We sill be performing soft recovery by running the below command.

Figure 1.3 : Recovery Completed Successfully

Figure 1.4 : State : Clean Shutdown

Now that we have the database in clean shutdown. We have to create RDB to get the database mounted in RDB and restore the required mailbox.

Figure 1.5 : RDB Created

Figure 1.6 : RDB Status

Mount the database by running “Mount-Database RDB”

Figure 1.7 : RDB Mounted

Figure 1.8 : RDB Status

Now that we have the database mounted. Lets perform a restore.

Figure 1.9 : New-MailboxRestoreRequest

Figure 1.10 : Restore Request Removed.

There are many scenarios in which RDB can be used. In this scenario we have just restored one mailbox.

=====================================================

Happy Learning

Outlook Anywhere in Exchange Server 2013 – What’s New

In this blog we will explore something new which has been introduced in Exchange Server 2013. Yes, that’s New Outlook Anywhere configuration changes introduced for Microsoft Outlook.

Scenario

Client – Microsoft Outlook 2010

Exchange Server – Microsoft Exchange 2013

In Previous versions of exchange so far we have seen all local clients are considered as “MAPI” clients. In Exchange Server 2013 by default local clients are “RPC/HTTP”. So you don’t need any extra configuration for setting up RPC/HTTP. The SSL Certificate used for Outlook Web APP and Active Sync can be used for Outlook Anywhere.

=======================================

Lets Explore

For testing purpose we are configuring outlook profile for one user who is domain joined.

Figure 1.1 : Outlook Setup

Figure 1.2 : Option to configure Mailbox

Figure 1.3 : Setup Continued

Figure 1.4 : Final Configuration

Click finish. Post configuration open Outlook. Go to File > Account Settings > Select Change.

==============================================================

Figure 2.1 ; Server Name Highlighted

In figure 2.1 what we see in Server is not server name. Rather it is Exchange Mailbox Guid which is unique for every user Mailbox.

In this option a user can create multiple outlook profile the way it was in previous version of Exchange.

Figure 2.2 : Mailbox Guid Enlarged.

Figure 2.3 : Output from LDP dump.

In figure 2.3 we have output for a User Account which was taken using LDP tool. In this we see Object Guid and Mailbox Guid is different. This was the case with all versions of Exchange.

Figure 2.4 : Output from Powershell command for User

Figure 2.4 : Output from Powershell command for Mailbox.

Figure 2.5 : More settings options.

In figure 2.5 what we see is the email address for the user. Which was not the case with previous version of Exchange. We use to have only user Alias.

Figure 2.6 : Exchange Proxy Settings…

In figure 2.6 what we see is the option “Exchange Proxy Settings” which is by default enabled.

Figure 2.7 : HTTP settings by default enabled.

In this blog we have seen the changes which is by default enabled for all local clients.

Happy Learning

Automatic Reseed in Exchange Server 2013

In this blog we will be exploring some new feature introduced in Exchange Server 2013. Microsoft has introduced a new High Availability Feature “Automatic Reseed”. To simulate the scenario we have already created two member DAG.

Lets Explore

Figure 1 : Two Node Dag

To understand the concept lets first explore the new DAG properties.

Figure 2 : Data properties

In figure 2 we can see some attributes as “AutoDag” with various options. The option available is the default option and there are some customization required to ensure that Automatic reseed works the way you expect.

Old Story – In Exchange Server 2010 if a disk fails then the entire database fails over from active node to passive node. And if the same happens in passive node then you might end up replacing the disk and start with either full reseed or manual reseed based on the database size.

New Story -  In Exchange Server 2013 we have Automatic Reseed. So lets have a look at it how to configure the Automatic Reseed feature.

DAG Settings

In figure 2 we have to set below properties as per our requirement.

1. AutoDagDatabasesRootFolderPath : Default mount point for database.
2. AutoDagDatabaseCopiesPerVolume : Allows us to set number of database copies per volume.
3. AutoDagVolumesRootFolderPath : Default mount point for all volumes (Best practices is to have it in the root).

For more information on Best Practices on volume mount points please refer 280297.

Figure 3 : Folder Names Created in the root of C Drive.

In figure 3 Two folders are created for Volumes and Database.

Now first we have to create mount volume folders as shown below.

Figure 4 : Two directories for volumes

Now open disk management and we will create mount points using these two folders.

Figure 5 : Change Drive Letter and Paths

Figure 6 : Select Add

Figure 7 : Path

Figure 8 : Volume Mount Points Created

Figure 9 : Database Directory

Repeat steps 5,6 and 7 for database directory.

Figure 10 : Mount Volume for MDB1

Figure 11 : Comparing and Confirming Mount Volume.

Now lets create Data folder and Log File folder.

Figure 12 : Data folder and Log folder

In figure 12 when we create data folder and log folder. It must create the exact folders in E drive.

Figure 13 : Folders listed in E Drive.

Now Lets create database with the help of EMS.

Figure 14 : Create Database

Figure 15 : Created Successfully

After Creating the database mount the database. Post which add the database copy.

Figure 16 : Database Status

Lets test auto reseed.

Figure 17 : E Drive is offline.

In figure 17 E drive was taken offline forcefully to simulate the auto reseed functionality. In practical scenario it may be different.

Figure 18 : Status

Figure 19 : Auto reseed completed.

Note : To track the behavior in the background. You can refer the crimson log. Check “Seeding” on the source server where the drive has crashed. If the database is large it will take considerable amount of time to reseed.

===================================================

Happy Learning

Certificate Restore in Exchange Server 2013 SP1

Disclaimer Note: The test performed is on Certificate which was issued by an Internal CA. Third party vendors may offer a different solution. Please check and understand their terms and conditions before performing any steps.

Figure 1: After Disaster Recovery

Figure 2: Import Exchange Certificate

In figure 2 we have to ensure that our cursor is pointing somewhere in the middle pane. Do not select any options. And then click Import Exchange Certificate as shown above.

Figure 3: File to Import

In figure 3 Import the Certificate from the Shared Location.

Figure 4: Certificate Restored

Post restoring the Certificate assign the services as required and the server should be back in production.

Hope it was helpful

=========================================================================

How to Restore Exchange Server 2013 Database – Part 2

In first part we have successfully backed up Exchange Server 2013 Database. In this blog we will be performing restore.

Lets see what options we have to select, so that the restore is successful with zero errors.

Figure 1.1 : Windows Server Backup (Apps)

In figure 1.1 we will be selecting Recover.

Figure 1.2 : Getting Started

Figure 1.3 : Select Backup Date

In figure 1.3 Dates shown in BOLD is the backup available dates. And also Status should show “Available Online”.

Figure 1.4 : Select Recovery Type

Figure 1.5 : Select Items to Recover

In figure 1.5 you can either select the entire data to restore as per your choice or you can select “Mailbox” itself. that will restore the entire mailbox database.

Note : Ensure that the restore destination has enough room to restore the backup.

Figure 1.6 : Specify Recovery Options

In figure 1.6 I have selected alternate location. Since the original location is online database.

Figure 1.7 : Confirmation

Figure 1.8 : Recovery Progress

Figure 1.9 : Completed

Figure 1.10 : Restored Data files and log files

Now that we have data restored successfully. We can get the health of the data files and restore them either to production or recovery database.

===================================================