Creating DAG, Exchange 2010 PART#1
- Fallow MS best practices all the times
- Exchange 2010 System Requirements
Installing Exchange 2010 on Windows R2
This section is taken from Henrik Walter Blog, he has excellent article series also showing DAG in much Details, links to his blog is fallows, Henrik has been good mentor to many of us, not only with technical aspect but also his professionalism in my opinion is top quality.
After Installing Windows 2008 R2
Before we can install the Exchange 2010 Server roles on the two Windows 2008 R2 servers, we must first make sure the required features and components have been installed. The following components should be installed on all Exchange 2010 server roles:
Copy and paste fallowing into PS
|Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,RPC-Over-HTTP-Proxy –Restart|
Copy and paste fallowing into PS
|Set-Service NetTcpPortSharing –StartupType Automatic|
Replication NIC Card (Private network)
- NIC BINDINGS
- Go to Network Connections
- Advance Settings
- Make sure the replication NIC is listed on TOP
***Press ALT key to see the advance settings***
Now we are ready to move on with installing DAG. The configuration we are doing is very basic here. We will use ForeFront to achieve redundancy for OWA and Outlook anywhere later on, most likely on part 4, for now we will move on finishing the configuration of DAG. As reminder our goal is to bring two exchange 2010 servers in DAG configuration and make our messaging environment redundant, if one server goes down, the other server will pick up the production users. As you know DAG member can be added or taken out from DAG (Data Availability Group) any time. In very basic thinking the way DAG works is to assign active databases and passive databases to each DAG members. Renaming Databases to some sort of meaningful names seems to be the way to go. Remember Storage groups no longer exist in Exchange 2010 and logs are associating with each database.
***IF you go to ADUC you will see computer object called “DAG1” if you go to DNS you will see below A and PTR (if reverse zone exist), after creating the DAG group and assigning IP to it.***
*** We recommend that you use an Exchange 2010 Hub Transport server in the Active Directory site containing the DAG. This allows the witness server and directory to remain under the control of an Exchange administrator.***
*** If the witness server you specify isn’t an Exchange 2010 server, you must add the Exchange Trusted Subsystem universal security group to the local Administrators group on the witness server prior to creating the DAG. These security permissions are necessary to ensure that Exchange can create a directory and share on the witness server as needed. ***
*** Hub Transport server that doesn’t have the Mailbox server role installed, and it will automatically create the default directory***
- Go to EMC Under organization configuration select
- New Data Base Availability Group and fallow the simple wizard.
As you can see the Witness Server and Witness directory is not selected, DAG is configured with a witness server and witness directory, the DAG Wizard will search and locate the HTS server and create everything it needs automatically. (Witness Server = HTS server, Witness Directory will be on the HTS server also)
|New-DatabaseAvailabilityGroup -Name ‘DAG1′|
Now we will check the fail over clustering
- Click start on the search type
|Set-DatabaseAvailabilityGroup DAG1 –DatabaseAvailabilityGroupIpAddresses 10.10.10.150|
Categorised as: Exchange, Microsoft
Leave a Reply
You must be logged in to post a comment.