Microsoft Exchange server 2013 introduced a new feature called AutoReseed which is used by Exchange 2013 DAG member servers. Its purpose is to quickly restore database redundancy after a disk failure with no manual intervention.

Before, I have written, how to setup a single database for auto seeding. This explained the process and concept for a single database per volume.

I would recommend first going through this blog before continuing. As I do not re-explain all steps.

The Steps we will follow:

1. Determine directory structure
2. Set AutoDagDatabasecopiespervolume
3. Create 1^st Directory structure
4. Mount volumes
5. Create 2^nd directory structure
6. Create Databases

So let’s get started

Scenario

Let’s say you have 3 database per volume and which you want to setup for auto-reseeding. DB1, DB2 and DB3 is their respective names. You can changes these, but remember to change the file directory names accordingly as well.

First of all the most important steps in the process is the naming and directory structures. If this is not 100% correct the Autoreseed workflow will fail.

1. 1.  Directory Structure

First we need to decide where our DAG’s root folder paths is going to be.

I will use the following paths

• AutoDagDatabasesRootFolderPath      C:\ExchDB
• AutoDagVolumesRootFolderPath       C:\ExchVol

You can create the directory on each DAG member server as follow.

md C:\ExchDB

md C:\ExchVol

Get-DatabaseAvailabilityGroup <DAG Name> | Format-List auto*Folder*

Results should show as follow:

1. 2.  AutoDagDatabasecopiesperVolume

Since we will have 3 Databases per volume, we need to set the AutoDagDatabasecopiesperVolume to 3

Set-DatabaseAvailabilityGroup <DAG Name> -AutoDagDatabaseCopiesPerVolume 3

1. 3.  1^st Directory Structures

Now that we have our Root folders created and properties set, we have 2 next tasks to complete.

1. Create Database Directories
2. Create Volume Directories

My Database names is DB1, DB2 & DB3 respectively. So I will create them as follow:

md C:\ExchDB\DB1

md C:\ExchDB\DB2

md C:\ExchDB\DB3

md C:\ExchDB\Volume1

md C:\ExchDB\Volume2

1. 4.  Mounting Volumes

The next steps is key. We need to mount our volumes to the newly created directory structures.

Let’s say we have Volume1 and Volume2. Volume1 will be used as my active database Volume and Volume2 as my spare volume.

Mount Volume1 to Paths

C:\ExchDB\DB1

C:\ExchDB\DB2

C:\ExchDB\DB3

C:\ExchVol\Volume1

You’re mount points on your volume should like this:

Mount Volume2 to paths

 C:\ExchVol\Volume2

 We have now mounted our volumes and database directories, the folder structure should like this now:

1. 5.  2^nd Set of Directories

We now need to create the last set of directories for our database logs and db files.

 For Volume1 “Active” we do:

 md C:\ExchVol\Volume1\DB1.db

md C:\ExchVol\Volume1\DB2.db

md C:\ExchVol\Volume1\DB3.db

md C:\ExchVol\Volume1\DB1.log

md C:\ExchVol\Volume1\DB2.log

md C:\ExchVol\Volume1\DB3.log

and for Volume2 we do:

md C:\ExchVol\Volume2\DB1.db

md C:\ExchVol\Volume2\DB2.db

md C:\ExchVol\Volume2\DB3.db

md C:\ExchVol\Volume2\DB1.log

md C:\ExchVol\Volume2\DB2.log

md C:\ExchVol\Volume2\DB3.log

Steps 3 to 5 should be done on all DAG member servers

1. 6.  Create Databases

We have now created all directory structures and last thing left is to create our databases.

DB1

New-MailboxDatabase -Name "DB1" -EdbFilePath “c:\ExchDb\db1\db1.db\MailboxDatabase01.edb” –LogFolderPath “c:\ExchDb\Db1\db1.log”

DB2

New-MailboxDatabase -Name "DB2" -EdbFilePath “c:\ExchDb\db2\db2.db\MailboxDatabase02.edb” –LogFolderPath “c:\ExchDb\Db2\db2.log”

DB3

New-MailboxDatabase -Name "DB3" -EdbFilePath “c:\ExchDb\db3\db3.db\MailboxDatabase03.edb” –LogFolderPath “c:\ExchDb\Db3\db3.log”

Now that our databases are created you can add your Database copies to your DAG members.

The process is now complete.

Any information on the workflow in case of failure can be found in the Seeding logs : Event Viewer\Applications and Services Logs\Microsoft\exchange\HighAvailability\seeding

Microsoft Exchange server 2013 introduced a new feature called AutoReseed which is used by Exchange 2013 DAG member servers. It's purpose is to quickly restore database redundancy after a disk failure with no manual intervention.

Before we can begin, there are a couple of requirements that needs to be met for a successful Autoreseedable database.

• You need the appropriate rights to perform the actions on the DAG.
• A working and healthy Exchange 2013 DAG.
• Spare Hard Drives & Volumes.

The AutoReseed cleverly makes use of mount points to achieve the wanted goal. Let’s first take a look at the properties of your DAG.

Within the EMS type the following, change the DAG name to match your DAG name.

Get-DatabaseAvailabilityGroup <DAG Name> | Format-List *auto*

Results should show as follow:

The important properties we will be using are as follows:

• AutoDagVolumesRootFolderPath
• AutoDagDatabasesRootFolderPath
• AutoDagDatabaseCopiesPerVolume

AutoDagVolumesRootFolderPath is the root folder for the volumes and the default value is C:\ExchangeVolumes

AutoDagDatabasesRootFolderPath is the root path for the databases and default value is C:\ExchangeDatabases

AutoDagDatabaseCopiesPerVolume is the amount of databases per volume.

In this scenario we will have a single database per volume and is illustrated with the image below. Therefor the value of AutoDagDatabaseCopiesPerVolume will remain at 1.

Preparing your Volumes

We start the process by first preparing the directories, drives and volumes.

In disk manager create your volumes per disk. Since this is for hardware failure you will create one volume per disk. Note: “disk” here can also by JBOD or even a set of disks without parity. Assign “NO” paths or drive letters to these volumes yet.

It should look something like this, where Disk 1 and Disk 2 will be my Volumes hosting my Databases. Disk 2 will be my spare.

Preparing your directory structure

In the following example we will be using the C:\ drive to host the root paths.

Create the “root” directories.

md c:\ExchDb

md c:\ExchVol

You should set your DAG properties to match these.

Set-DatabaseAvailabilityGroup <DAG> -AutoDagVolumesRootFolderPath c:\ExchVol

Set-DatabaseAvailabilityGroup <DAG> -AutoDagDatabasesRootFolderPath c:\ExchDb

Or

Set-DatabaseAvailabilityGroup <DAG> -AutoDagVolumesRootFolderPath c:\ExchVol -AutoDagDatabasesRootFolderPath c:\ExchDb

Run Get-DatabaseAvailabilityGroup <DAG Name> | Format-List *auto*root* to verify the paths has changed to the directories you have created.

Mounting the volumes

We first need to create our mount point’s directories for our volumes and database

md c:\ExchVol\Volume1

md c:\ExchVol\Volume2

md c:\ExchDb\DB1

The next step is to mount the Volumes to the mount points.

You can do this by right clicking your volume and select “Change Drive letters and Paths”.

Mount Volume1 to the directory c:\ExchVol\Volume1

Follow the same steps and mount Volume2 to the directory c:\ExchVol\Volume2

We now also need to mount the DB path. Volume1 will be the primary volume for my database “DB1”. So “only” on Volume1 add the additional mount point C:\Exchdb\Db1.

Your mounts points for Volume1 and Volume2 should look like this respectively.

Volume1

Volume2

In windows explorer your directory structure should look something like this.

Now we have the AutoDagVolumesRootFolderPath and AutoDagDatabasesRootFolderPath set on the DAG

and all volumes mounted for the Database.

Remember to change the value of AutoDagDatabaseCopiesPerVolume to match your configuration. In this case it will remain on 1.

Creating the Database

We need to create our Directory structure for the database.

Volume1

md c:\ExchVol\Volume1\db1.db

md c:\ExchVol\Volume1\db1.log

Volume2

md c:\ExchVol\Volume2\db1.db

md c:\ExchVol\Volume2\db1.log

Note: You will now see that c:\ExchDb\DB1 & c:\ExchVol\Volume1 match in directory structure.

 Now let’s create our Database.

New-MailboxDatabase -Name "DB1" -EdbFilePath “c:\ExchDb\db1\db1.db\MailboxDatabase01.edb” –LogFolderPath “c:\ExchDb\Db1\db1.log”

Add your Mailboxdatabasecopy’s to your different DAG members. This can be done via the EMS or EMC

Your AutoReseed setup process is now complete for DB1.

Other things to know

Volume1 Contains the primary Volume1 and volume2 acts as a spare.

Seeding logs can be found in Event Viewer\Applications and Services Logs\Microsoft\exchange\HighAvailability\seeding

You can make use of one spare for several db1 or several active volumes.

The normal DAG rule still applies when creating Databases: ”The directory structure must remain the same across all DAG members.”

The health of the database copies are checked by the Microsoft Exchange Replication services periodically and is looking for a state of FailedSuspended before it start with the Auto reseed test’s and tasks.