Microsoft Azure Public Cloud Enterprise Exchange 2016 Deployment 5-Configure DC availability set

In this section we will configure another domain controller DC02 in the Azure Cloud Master Datacenter and create an azure availability set, as shown in the red box:

650) this.width=650; "title=" clip_image002 "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;margin:0px;padding-right:0px; "border=" 0 "alt = "clip_image002" src= "http://s3.51cto.com/wyfs02/M02/83/81/wKiom1d0uAOgKdK1AAEjiArwur8139.jpg" height= "702"/>

1. Storage space

Because in the third section we chose "Use automatically generated storage account", so the cloud automatically generated a storage account that can be viewed in the "storage" item.

650) this.width=650; "title=" clip_image004 "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;margin:0px;padding-right:0px; "border=" 0 "alt = "clip_image004" src= "http://s3.51cto.com/wyfs02/M00/83/80/wKioL1d0uASAdi05AAA0QepFIS4731.jpg" height= "/>"

The storage account provides access to azure blobs, tables, and queue services within a geographic region.

A storage account created after June 8, 2012 can contain 200TB of data. Only one storage account can be created automatically for each zone. All other virtual machines created with this setting are also located in the storage account. You can create a maximum of 20 storage accounts.

We can confirm how the storage data is replicated in the configuration item

650) this.width=650; "title=" clip_image006 "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;margin:0px;padding-right:0px; "border=" 0 "alt = "clip_image006" src= "http://s3.51cto.com/wyfs02/M00/83/81/wKiom1d0uASy-Y3OAABBVukmChI224.jpg" height= "222"/>

With locally redundant replication, the storage account data is replicated three times in the same datacenter.

With geo-redundant replication, storage account data is replicated to a secondary geographic location. If a major disaster occurs at the primary location, you can fail over to the secondary location.

Read-access geo-redundant replication, which copies data to a secondary geographic location while providing read access to the data in the secondary location.

Of course, three different ways of copying the charges are different, geo-redundant price is twice times the local redundancy.

2. Create a second DC

Now let's create a second secondary domain controller, this time using Azure PowerShell to create one.

First specify the storage account

650) this.width=650; "title=" clip_image009 "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;margin:0px;padding-right:0px; "border=" 0 "alt = "clip_image009" src= "http://s3.51cto.com/wyfs02/M02/83/80/wKioL1d0uAXSJvVwAAAjVLz67Mg509.jpg" height= "/>"

The following PS to query the name of the available virtual machine template image under Azure, where the image of Windows Server Datacenter is queried

Get-azurevmimage |? {$_. Imagefamily-eq "Windows Server Datacenter"} | FL os,imagename,label,imagefamily

650) this.width=650; "title=" clip_image010 "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;margin:0px;padding-right:0px; "border=" 0 "alt = "clip_image010" src= "Http://s3.51cto.com/wyfs02/M01/83/80/wKioL1d0uAbj5rI8AAIjtP4obew822.png" height= "402"/>

You can generate the DC02 virtual machine directly with the following command, and fix the IP address

New-azurevmconfig-name "Hhcloud-dc02"-instancesize "basic_a1"-availabilitysetname "HHCLOUD-DC"-ImageName " A699494373c04fc0bc8f2bb1389d6106__windows-server-2012-datacenter-20160430-en.us-127gb.vhd "| Add-azureprovisioningconfig-windows-adminusername hhcloud-password "xxxx" | Set-azuresubnet-subnetnames "Subnet-3" | Set-azurestaticvnetip-ipaddress 192.168.2.12 | New-azurevm-servicename "Hhcloud"

650) this.width=650; "title=" clip_image012 "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;margin:0px;padding-right:0px; "border=" 0 "alt = "clip_image012" src= "Http://s3.51cto.com/wyfs02/M00/83/80/wKioL1d0uAfD1P1NAACcg1D9cYg951.jpg" height= "139"/>

The availability set of the DC is also created here

3. Configure the availability set

An availability set is a set of virtual machines deployed across fault domains and update domains to ensure that your application is not affected by a single point of failure, such as a network switch or a power unit on a server rack.

Microsoft is guaranteed to use an external connection for at least 99.95% of the time for all Internet-facing virtual machines with two or more instances deployed within the same availability set.

So by adding multiple virtual machines to an availability set, we can manage the availability of applications that use these virtual machines and improve SLA service assurance.

The availability set is directly related to fault domains and update domains. You can define fault domains in Windows Azure by avoiding the failure of a single point, such as a network switch or power device on a server rack. In fact, fault domains are approximately equivalent to physical server racks. When multiple virtual machines are connected together in a cloud service, the availability set ensures that these VMs are in different fault domains.

The following shows two availability sets, where each availability set contains two virtual machines, each on a different rack.

650) this.width=650; "title=" clip_image013 "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;margin:0px;padding-right:0px; "border=" 0 "alt = "clip_image013" src= "Http://s3.51cto.com/wyfs02/M02/83/80/wKioL1d0uAjiWzIVAAC3aT1Nm6U056.png" height= "342"/>

Because Windows Azure regularly updates the operating system that hosts the application instance. Sometimes when an update is applied, the virtual machine shuts down, and the update domain is used to ensure that not all virtual machine instances are updated at the same time. When we assign more than one virtual machine to an availability set, Windows Azure ensures that these virtual machines will be assigned to different update domains.

Two virtual machines running ad are displayed in different update domains, and two VMs running Exchange are in different update domains. In this way, there is a virtual machine available at any point in time.

Now that we are in the Azure Web VM configuration, we can see that the DC02 you just created has been added to the DC's availability set

650) this.width=650; "title=" clip_image015 "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;margin:0px;padding-right:0px; "border=" 0 "alt = "clip_image015" src= "http://s3.51cto.com/wyfs02/M01/83/81/wKiom1d0uAijDSDaAACQQWzdPgQ068.jpg" height= "539"/>

Let's add the DC01 page to this availability set

650) this.width=650; "title=" clip_image016 "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;margin:0px;padding-right:0px; "border=" 0 "alt = "clip_image016" src= "http://s3.51cto.com/wyfs02/M00/83/80/wKioL1d0uAmAJbUtAAAraN4Pkas981.png" height= "/>"

Finally we can see that the DC01, DC02 are all in the availability set DC

650) this.width=650; "title=" clip_image017 "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px, "border=" 0 "alt=" clip_ image017 "src=" http://s3.51cto.com/wyfs02/M00/83/81/wKiom1d0uAnwfJe9AAATfGas8fw292.png "height="/>

With availability sets, we can use multiple Windows Azure virtual machines to ensure the availability of your applications. Using more than one virtual machine in your application ensures that the application is still available when there are local network failures, local disk hardware failures, and any planned outages that the platform may require.

4. Configure Virtual Network DNS

Manually specifying DNS may not only cause the virtual machine to "fail", and the configuration will be reset if the resource is released after the shutdown.

So we can specify the DNS of the network in the configuration of the virtual network. This specifies the DNS provided by DC01 and Azure.

650) this.width=650; "title=" clip_image007 "border=" 0 "alt=" clip_image007 "src=" http://s3.51cto.com/wyfs02/M00/83/ 81/wkiom1d0uasrgnvkaaamv9swhdu218.png "height=" 332 "style=" border:0px;padding-top:0px;padding-left:0px;margin:0 Px;padding-right:0px;background-image:none; "/>

5. Enable AD Service

Finally enable the ad service, DC02 as the second secondary domain controller in the cloud.

This is the same as the previous operation method, no longer repeat it.

This article is from the "Iron Fist of the Invincible Speaker" blog, please be sure to keep this source http://yaojiwei.blog.51cto.com/762134/1794538

Microsoft Azure Public Cloud Enterprise Exchange 2016 Deployment 5-Configure DC availability set