Articles Tutorials Exchange Server 2010 High Availability Recovery Uncovering Exchange 2010 Database Availability Groups Dags Part4.HTML

Uncovering Exchange 2010 Database Availability Groups (DA...
Page 1 of 30
Articles Authors Blogs Exchange Hosting Free Tools Hardware Message Boards Newsletter Services Software Tips White Papers
Site Search Search Site Advanced Search
Submit Query
Home Articles & Tutorials Exchange 2010 Articles
http://www.msexchange.org/articles_tutorials/exchange-server-2... 3/16/2012
Uncovering Exchange 2010 Database Availability Groups (DA... Page 2 of 30

High Availability & Recovery
Uncovering Exchange 2010 Database Availability Groups (DAGs) (Part 4)

Advertisement
Over 99% Spam Capture Rate! Use the #1 Exchange Server anti-spam solution, which uses two anti-spam engines to capture over 99% of spam flooding your server on a daily basis
What Exchange 2010 Database Availability Groups is all about Download a free trial! and how they may fit into your enterprise. I will also provide you with step by step instructions on how you deploy DAG in a lab environment.
Published:Apr 08, 2010 Updated:Dec 15, 2010 Section:High Availability & Recovery Author:Henrik Walther Printable Version Adjust font size: Rating:4.9/5 - 47 Votes 1 2 3 4 5
Like
Figure 1: Suspending a Database copy To do the same via the EMS, you can use the following command: Suspend-MailboxDatabaseCopy Identity MDB02\E14EX02 In order to resume a database copy using the EMC, you just right-click on it again and choose Resume Database Copy.
Figure 2: Resuming a Database Copy If you rather want to resume it using the EMS, run the following command: Resume-MailboxDatabaseCopy Identity MDB02\E14EX02
Moving the Active Database Copy to another DAG Member (aka Switchover)
When you have a planned outage and need to take a DAG member that holds one or more active database copies down for maintenance, its considered best practice to manually move any active database copies (aka performing a switchover) to another DAG member in the DAG. To move an active database copy to another DAG member using the EMC is accomplished by right-clicking on the respective database(s) and selecting Move Active Mailbox Database in the context menu as shown in Figure 3.
Figure 3: Activating a Database Copy This brings up the Activate a Database Copy wizard (Figure 4).
Figure 4: Activate Database Copy wizard Here we can see the name of the database and on which DAG member it currently is mounted. To move the database copy to another DAG member, click Browse.
Figure 5: Selecting the server holding the database copy to be activated When you have selected the DAG member on which the databse copy should be activated, click OK. Then decide if you want to change the database mount dial settings on the target mailbox server. As you can see in Figure 6 its set to None (change nothing) by default. If you want to change the current setting (set to Best Availability by default) instead choose Lossless, Best Effort, or Best Availability.
Figure 6: Automatic database mount dial settings Heres a description of each of the available database mount dial settings: Lossless: (when selecting Lossless the database will not mount automatically until all logs generated on the active database copy has been copied to the passive database copy) Good Availability: (when selecting Good Availability, the database will mount automatically as long as you have a copy queue length less than or equal to 6. If the copy queue holds more than 6 log files, the database will not mount) Best Effort: (with Best Effort the database will mount no matter the copy queue length. Be careful with this setting as you could loose a lot of mailbox data!) Best Availability: (with Best Availbility the database will mount automatically as long as the copy queue length is less than or equal to 12. If the copy queue length is more than 12, the database will not be able to mount)
Unless theres a specific reason to chose another database mount dial override than the setting currently configured, leave this option at None. When you are ready to activate the database copy in the target mailbox server specified, click Move. To activiate a database copy using the EMS, we can use the following command: Move-ActiveMailboxDatabase MDB01 -ActivateOnServer E14EX02 MountDialOverride:None
Seeding Database Copies

There may be times where you need to seed a database copy for one reason or the other. This can both be done via the Exchange Management Console (EMC) and the Exchange Management Shell (EMS). Let us take a look at how to accomplish this via the EMC. If it is not already the case, the first thing we must do is to suspend replication for the passive database copy we want to seed.
Figure 7: Suspending the Database Copy You will now be presented with a dialog box where you can enter a comment on why replication for the database copy is being suspended.
Figure 8: Dialog box for optional comment When suspended, right-click on the database copy once again and select Update Database Copy.
Uncovering Exchange 2010 Database Availability Groups (D... Page 10 of 30
Figure 9: Selecting update Database copy in the context menu The Update Database Copy wizard will now appear (Figure 10).
Figure 10: Update database copy wizard As you can see we have several options in this wizard. We have the option of specifying the source server that should be used for seeding. This is a really cool feature since you are no longer limited to seeding from an active database copy as was the case in with Exchange 2007 LCR/CCR/SCR.
Figure 11: Selecting source seeding server We can also choose the behavior when files exist in the target path. In addition, we can specify whether replication to this database copy should be resumes or whether it should be leaved suspended. Lastly, we can select which DAG network should be used to seed the database copy. Again a great feature, which although it was an option in Exchange 2007 SP1, was very cumbersome.
Figure 12: Selecting DAG network used for seeding database copy When you have chosen your settings, click Update in order to seed the database copy. When the seeding has completed, click Finish.
Figure 13: Seeding process completed successfully If you rather want to use the EMS to seed a database copy, the above could be accomplished by first suspending replication with: Suspend-MailboxDatabaseCopy Identity MDB02\E14EX02
Figure 14: Suspending a database copy via the Exchange Management Shell Then run the following command to re-seed the database copy: Update-MailboxDatabaseCopy -Identity MDB02\E14EX02
Figure 15: Seeding a database copy via the Exchange Management Shell
Changing the Log file Replication Port

In Exchange 2007, the Microsoft Exchange Replication Service copies log files to the passive database copy (LCR), passive cluster node (CCR) or SCR target over Server Message Block (SMB). With DAGs in Exchange 2010, the asynchronous replication technology no longer relies on SMB. Instead, Exchange 2010 uses TCP/IP for log file copying and seeding and, even better; it provides the option of specifying which port you want to use for log file replication. By default, DAG uses TCP port 64327, but you are free to specify whatever port you want to use. To see the current port used, you must use the Get-AvailabilityGroup cmdlet with the Status parameter. To see the port used in our lab environment, use: Get-DatabaseAvailabilityGroup DAG1 Status | fl
Figure 16: Checking Replication port settings for a DAG To change the port used we must use Exchange Management Shell (EMS) as this option isnt included in the Exchange Management Console (EMC). Since this

setting is configured per DAG, we must use the Set-DatabaseAvailabilityGroup cmdlet. For instance to change the port for the DAG in our lab to TCP port 7580, we must use the following command: Set-DatabaseAvailabilityGroup DAG1 -ReplicationPort 7580 When the port have been changed, we can verify the new setting using: Get-DatabaseAvailabilityGroup DAG1 Status | fl ReplicationPort
Figure 17: Checking new Replication port settings for a DAG Now when updating a database copy, we can see that TCP/7580 is used (below I ran Netstat an while the database copy were updated.
Figure 18: Checking the new replication port is used (by running Netstat -an)
Log file Network Compression

With DAGs in Exchange 2010, we can enable or disable compression for seeding and replication activities over one or more networks in a DAG. This is a property of the DAG itself, not a DAG network. The default setting is InterSubnetOnly (which means compression is used when replication occur across subnets) as shown in Figure 19.
Figure 19: Checking Network Compression settings for a DAG The available values are: Disabled (disabled on all networks) Enabled (enabled on all networks) InterSubnetOnly (enabled for inter-subnet communication only) SeedOnly (enabled only for seeding)
If we for instance want to enable network compression for log file copying and seeding on all networks in a DAG in our lab environment, we would use the following command: Set-DatabaseAvailabilityGroup DAG1 -NetworkCompression Enabled
Figure 20: Checking new Network Compression settings for a DAG With compression enabled for log file seeding and replication, you can expect around 30% compression ratio. As you can see, theres really no reason why you should disable network compression unless you for instance use a 3rd party WAN/network optimizer that doesnt support DAG network compression.
Log file Network Encryption

With DAGs in Exchange 2010 theres now native support for encryption of log file seeding and replication activities. In Exchange 2007 log files are copied over an unencrypted channel unless IPsec has been configured. DAG leverages the encryption capabilities of Windows Server 2008/R2, that is DAG uses Kerberos authentication between each DAG member. Network encryption is a property of the DAG itself, not the DAG network. Available settings for the network encryption property are: Disabled (network encryption not in use), Enabled (network encryption enabled for seeding and replication on all networks associated with a DAG), InterSubnetOnly (the default setting meaning network encryption is used across subnets) SeedOnly (network encryption in use for seeding on all networks in a DAG). The default setting is InterSubnetOnly.
Figure 21: Checking Network Encryption settings for a DAG If you want to change the network encryption settings, you can use the SetDatabaseAvailabilityGroupcmdlet. For instance, if you wanted to enable encryption for log copying and seeding on all networks, you would use the following command: Set-DatabaseAvailabilityGroup -identity DAG1 -NetworkEncryption Enabled
Figure 22: Checking new Network Encryptions settings for a DAG
Configuring Replay & Truncation Lag Time

The Standby Continuous Replication (SCR) feature that was introduced with Exchange 2007 SP1 gave us the option of replicating one or more databases from a stand-alone mailbox server, cluster continuous replication (CCR) cluster, or single copy cluster (SCC) to a target stand-alone mailbox server or standby cluster (CCR or SCC failover cluster where only the passive clustered mailbox role has been installed). SCR could both be used for replicating storage groups locally in a datacenter or remotely to servers located in a secondary or backup datacenter.

In addition to being able to replicate data to multiple targets per storage group, SCR also introduced the concept of replay lag time and truncation lag time. With replay lag time you could configure the Microsoft Exchange Replication service to wait for a specified amount of time before log files that had been copied from the SCR source to the SCR target(s) were replayed. The default value for replay lag time was 24 hours and could be configured with a value of up to 7 days (if configured to 0 seconds there were a 50 log files lag time so that a reseed wasnt require when a lossy failover has occurred). The idea with replay lag time was to have a database from back in time, which could be used to recover if active database copy/copies on the SCR source server(s) were struck by logical corruption. This way to can stop replication before the logical corruption is replicated to the SCR target server(s) and thereby prevent loosing data. Truncation lag time could be used to specify how long the Microsoft Exchange Replication service should wait before truncating (deleting) the log files that had been copied to the SCR target server (s) and replayed into the copy of the database (s). The maximum allowable setting for truncation lag time is 7 days and the minimum is 0 seconds, which will remove the truncation delay completely. With truncation lag time you could recover from failures that affected the log files on the SCR source server(s). DAG also supports replay lag time and truncation lag time we know from SCR in Exchange 2007 SP1. They work pretty much the same way although controlled via a new cmdlet (Set-MailboxDatabaseCopy). These features have been improved a little with Exchange 2010. For instance, the replay lag time option now has a maximum setting of 14 days instead of 7 days as was the case with Exchange 2007 SP1. Also bear in mind that unlike SCR in Exchange 2007 SP1, replay lag time in Exchange 2010 does not have a hard-coded replay lag of 50 log files (even when set to 0 seconds). As you can see in Figure 23 both replay and truncation lag time are disabled by default.
Figure 23: Default Replay and Truncation Lag time setting for a Mailbox database The purpose with replay and truncation lag time in Exchange 2010 is pretty much the same as with SCR in Exchange 2007 SP1 that is to protect against database logical corruption and store logical corruption. Whats interesting and new with Exchange 2010 is you now can use lagged database copies in combination with legal hold etc. I wont dive further into lagged database copies in this multi-part article. Instead Ill cover this topic in a future articles here on MSExchange.org.
Blocking a Database Copy from being activated

a d v er ti s em e n t
There are situations where you might want to block a passive database copy (or even server) in a DAG from being changed activated (changed to the active database copy). Good thing is the Exchange Product group thought about this kind of scenario. You can do exactly that using a so called activation policy. Its not possible to use the EMC to set this, but using the EMS, you can use the SuspendMailboxDatabaseCopy cmdlet for this purpose. Yes correct, this cmdlet is typically used for suspending replication for a database copy, but when run with a special ActivationOnly parameter, you can block a database copy from being changed to the active database copy during a failover. For instance, if we want to block MDB01 on E14EX02 from ever being activated during a failover, we can use the following command: Suspend-MailboxDatabaseCopy Identity MDB01\E14EX02 -ActivationOnly
Figure 24: Blocking a database copy from being activated Notice this does not suspend replication for the database copy and thereby result in, an over time, huge copy queue. Only the database copy is being block from activation.
Figure 25: Replication not suspended when using Suspend-MailboxDatabaseCopy with the ActivationOnly parameter When this cmdlet is run with the ActivationOnly parameter, the database copy cannot be activated until the following command is run: Resume-MailboxDatabaseCopy Identity MDB01\E14EX02
Figure 26: Unblocking a database copy from being activated Ok so what if I wish to block all databases on a DAG member server? Will I then need to run the above command on all database copies on the particular server? Luckily not. We have a similar command that works on the server level. If oyu want to block a DAG member instead use the Set-MailboxServer with the DatabaseCopyAutoActivationPolicy Blocked parameter. For instance if I wanted to block DAG member E14EX02 from having database copies activated, I would use the following command: Set-MailboxServer Identity E14EX02 - DatabaseCopyAutoActivationPolicy Blocked
Figure 27: Blocking a DAG member from being activated To allow database copies to be activated again, I would replace Blocked with Unrestricted: Set-MailboxServer Identity E14EX02 - DatabaseCopyAutoActivationPolicy Unrestricted
Like
Add a comment...
Comment using...
Tariq Samsudeen Works at Fortune Promoseven Very clear. Amazing piece of info. Reply Like 4 March at 18:51
Facebook social plugin
Henrik Walther is a respected writer with special focus on Microsoft Exchange and Office 365/BPOS (Exchange Online) solutions within the unified communications area. Prior to joining Microsoft, he was an eight year Exchange MVP and back in 2006 he took the Microsoft Certified Master: Exchange certification. Click here for Henrik Walther's section.
Receive all the latest articles by email!

Get all articles delivered directly to your mailbox as and when they are released on MSExchange.org! Choose between receiving instant updates with the Real-Time Article Update, or a monthly summary with the Monthly Article Update. Sign up to the MSExchange.org Monthly Newsletter, written by Exchange Expert Henrik Walther, containing news, the hottest tips, Exchange links of the month and much more. Subscribe today and don't miss a thing! Real-Time Article Update (click for sample) Monthly Article Update (click for sample) Monthly Newsletter (click for sample)
Enter email address
Latest articles by Henrik Walther

Deep dive into rich coexistence between Exchange Forests (Part 1) Deep dive into rich coexistence between Exchange Forests (Part 2) Deep dive into rich coexistence between Exchange Forests (Part 3) Deep dive into rich coexistence between Exchange Forests (Part 4) Deep dive into rich coexistence between Exchange Forests (Part 5)
Related links
Continuous Backup for Exchange Server with DPM 2007 (Part 2) Moving from MDaemon to Exchange Server 2003/2007 (Part 1) Moving from MDaemon to Exchange Server 2003/2007 (Part 6) Recovering an Exchange 2007 Server using the RecoverServer switch Domain Rename Rename a Windows 2003 Forest with Exchange 2003 installed
Featured Links*
Simple Exchange and PST Archiving for SMEs MailStore Server solves 2 of the biggest problems facing those with email overload: How to reduce workload of email servers, and how to handle PST files. The New Archiving Debate: Is Exchange 2010 Enough? Debating Exchange 2010's new archiving features? Experts agree Exchange falls short for many organizations. Check out Archive Attender for a complete solution! Fed up of PST files? Archive all Exchange mail to SQL or simply NTFS Offload Exchange and improve performance, reduce Exchange storage requirements by up to 80% and allow users to retrieve archived (read-only) emails. Dld free trial. Dig into your Exchange message tracking files with PROMODAG StoreLog 3 - FREE This freeware transfers the content of your message tracking files into an Access database for easy querying. New version supports Exchange 2010 and it's FREE! Gain Visibility into Exchange with Over 200 Reports + Real-Time Monitoring Mailscape lets you manage your entire messaging environment in a sleek, one look dashboard. Prevent email outages & resolve problems quickly. Test Drive it Today!
Receive all the latest articles by email!

Receive Real-Time & Monthly MSExchange.org article updates in your mailbox. Enter your email below! Click for Real-Time sample & Monthly sample
Enter Email
Become an MSExchange.org member!

Community Area
Discuss your Exchange Server issues with thousands of other Exchange experts. Log in|Register Click here to join! My Account|Log out
Featured freeware!
Get a free copy of the new SolarWinds Permissions Analyzer! Anti Spam Section Articles & Tutorials Exchange 2010 Articles Exchange 2007 Articles

Exchange 2003 Articles Exchange 2000 Articles Exchange 5.5 Articles Office 365 Product Reviews Authors J. Peter Bruzzese Andy Grogan Nuno Mota Henrik Walther Neil Hobson Anderson Patricio Jaap Wesselius Markus Klein Rui Silva Ilse Van Criekinge Blogs Exchange Hosting Hardware Mail Archiving Message Boards Migration Section Services Anti Spam Filtering BlackBerry Hosting Exchange Hosting Hosted Email Archiving Software Administration Anti Spam Backup & Recovery Calendar Tools Content Checking CRM Software Disclaimers Document Management eDiscovery Email Anti Virus Email Archive & Storage Email Signatures

Fax Connectors Free Exchange Tools List Servers - Mgmt Log Monitoring Migration Misc. Exchange server software Mobility & Wireless Outlook Addons OWA Addons POP3 Downloaders PST Management Reporting Security & Encryption SMS & Paging Tips & Tricks White Papers
Featured Products
Featured Book
Order today Amazon.com Special Preview: Read Chapter 9 here
Readers' Choice
Which is your preferred Email Antivirus Solution?
Vote!
avast! Email Server Security BitDefender Security for Exchange Command Antivirus SDK GFI MailSecurity for Exchange/SMTP Hexamail Guard Antivirus Kaspersky Anti-Virus for MS Exchange Server Protector Plus for Exchange Sophos PureMessage for Microsoft Exchange Symantec Mail Security for Microsoft Exchange Trend Micro ScanMail XWall for Microsoft Exchange Other please specify
TechGenix Sites
ISAserver.org The No.1 Forefront TMG / UAG and ISA Server resource site. WindowSecurity.com Network Security & Information Security resource for IT administrators. WindowsNetworking.com Windows Server 2008 / 2003 & Windows 7 networking resource site. MSPAnswers.com Resource site for Managed Service Providers. WServerNews.com The largest Windows Server focused newsletter worldwide. VirtualizationAdmin.com The essential Virtualization resource site for administrators. Anti Spam Articles Authors Blogs Books

Free Tools Hardware Hosted Exchange Links Message Boards Newsletter Services Software Tips White Papers
About Us : Email us : Product Submission Form : Advertising Information MSExchange.org is in no way affiliated with Microsoft Corp. *Links are sponsored by advertisers. Copyright 2012 TechGenix Ltd. All rights reserved. Please read our Privacy Policy and Terms & Conditions.

Articles Tutorials Exchange Server 2010 High Availability Recovery Uncovering Exchange 2010 Database Availability Groups Dags Part4.HTML

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Articles Tutorials Exchange Server 2010 High Availability Recovery Uncovering Exchange 2010 Database Availability Groups Dags Part4.HTML

Transféré par

Droits d'auteur :

Formats disponibles

Uncovering Exchange 2010 Database Availability Groups (DA...

Site Search Search Site Advanced Search

Home Articles & Tutorials Exchange 2010 Articles

Uncovering Exchange 2010 Database Availability Groups (DA... Page 2 of 30

Uncovering Exchange 2010 Database Availability Groups (DAGs) (Part 4)

Uncovering Exchange 2010 Database Availability Groups (DA... Page 3 of 30

Uncovering Exchange 2010 Database Availability Groups (DA... Page 4 of 30

Uncovering Exchange 2010 Database Availability Groups (DA... Page 5 of 30

Uncovering Exchange 2010 Database Availability Groups (DA... Page 6 of 30

Uncovering Exchange 2010 Database Availability Groups (DA... Page 7 of 30

Uncovering Exchange 2010 Database Availability Groups (DA... Page 8 of 30

Seeding Database Copies

Uncovering Exchange 2010 Database Availability Groups (DA... Page 9 of 30

Uncovering Exchange 2010 Database Availability Groups (D... Page 10 of 30

Uncovering Exchange 2010 Database Availability Groups (D... Page 11 of 30

Uncovering Exchange 2010 Database Availability Groups (D... Page 12 of 30

Uncovering Exchange 2010 Database Availability Groups (D... Page 13 of 30

Changing the Log file Replication Port

Uncovering Exchange 2010 Database Availability Groups (D... Page 14 of 30

Uncovering Exchange 2010 Database Availability Groups (D... Page 15 of 30

Log file Network Compression

Uncovering Exchange 2010 Database Availability Groups (D... Page 16 of 30

Log file Network Encryption

Uncovering Exchange 2010 Database Availability Groups (D... Page 17 of 30

Figure 22: Checking new Network Encryptions settings for a DAG

Configuring Replay & Truncation Lag Time

Uncovering Exchange 2010 Database Availability Groups (D... Page 18 of 30

Uncovering Exchange 2010 Database Availability Groups (D... Page 19 of 30

Blocking a Database Copy from being activated

Uncovering Exchange 2010 Database Availability Groups (D... Page 20 of 30

Uncovering Exchange 2010 Database Availability Groups (D... Page 21 of 30

Uncovering Exchange 2010 Database Availability Groups (D... Page 22 of 30

Uncovering Exchange 2010 Database Availability Groups (D... Page 23 of 30

Receive all the latest articles by email!

Enter email address

Latest articles by Henrik Walther

Uncovering Exchange 2010 Database Availability Groups (D... Page 24 of 30

Uncovering Exchange 2010 Database Availability Groups (D... Page 25 of 30

Receive all the latest articles by email!

Become an MSExchange.org member!

Uncovering Exchange 2010 Database Availability Groups (D... Page 26 of 30

Uncovering Exchange 2010 Database Availability Groups (D... Page 27 of 30

Uncovering Exchange 2010 Database Availability Groups (D... Page 28 of 30

Order today Amazon.com Special Preview: Read Chapter 9 here

Uncovering Exchange 2010 Database Availability Groups (D... Page 29 of 30

Uncovering Exchange 2010 Database Availability Groups (D... Page 30 of 30

Vous aimerez peut-être aussi