Exchange 2010 beta has been released for several days and of course I have installed it myself. The coming weeks I will publish several articles about the changes in Exchange 2010 Beta. Ofcourse it is a beta so it could be that some features will not be available in the final version.
In this article I will zoom in at the mailbox part and then specificly to the Exchange Management Console.
When you open the Exchange Management Console and go to mailbox via organizational configuration you will see the following tabs:
You can see 2 news tabs here:
- database management
- database availability group
First database management, on this tab your can create a mailbox and enable a database copy. The greatest difference is that there are no storage groups anymore but only databases.
When getting the properties of the database you will see 4 tabs instead of 3. I think this is done because on specific tabs more information is displayed.
On the general tab you will see a few new fields:
- mounted on server: here you can see on which mailbox server the database is mounted
- master: this is the server which is master of the specific database
- master type: this is the type of the server which is the master of the database
- servers that have a copy of this database: this field will contain all servers that have a copy of the database
The tab maintenance is a new tab compared with Exchange 2007. The fields displayed on this tab where previously displayed on the general tab. The only new field is circular logging, this was displayed on Storage Group level in Exchange 2007.
On the two other tabs: Limits en Clients there has nothing been changed.
When you are searching for the option local continious replication you can spent a lot of time before finding it. LCR is not available anymore in Exchange 2010 just as almost every high availability options, these options have been replaced by a new option called: Database Availability Group, this will be discussed later in this article.
Configuring the database copy is really easy and can be done fully via the EMC.
Only a few fields need to be filled in:
- the server which you would like to copy the database to, this can be only a server which is in the same DAG group as the master server.
- replay lag time, the delay before the logs will be replayed on the other mailbox server
- truncation lag time, the delay before logs will be truncated on the other mailbox server
- preferred list sequence number, the priority of the copy, this copy is used when the database needs to be activated on another mailbox server, for example when an other server needs to be activated because the master server went down.
When the datbase copy is configured you can view the status by getting the properties of the database in the lower part of the screen.
On the first tab you can easily see how many logs need to be copied/replayed, how many logs have been copied/replayed and what the curren priority is.When having a look at the status tab you can see several status messages of several items:
In Exchange 2007 this can only be done via Powershell, but now you can do it via the EMC. The button view is only active when failures happen during the copy of the database.
The second tab is called database availability group. This option makes it possible to copy a database to a maximum of 16 Exchange 2010 servers. The DAG monitor will keep an eye on database and if needed will perform an automatic database-level recovery of a database, server, or network issue.
Before you can use the DAG functionality you will need to create a DAG group. This group contains all servers which will have a copy of the specific database
Configuring the DAG group goes really easy, a few fields need to be filled in:
- database availability group name::name of the database availability group
- file share witness share: name of the share that willbe created on the HUB server
- file share witness directory: the name of the directory where the files need to be placed in
- network encryption: when does traffic need to be encrypted
- network compression: when does traffic need to be compressed
This is the end of the first article about Exchange 2010 beta.