Replica DCs on Microsoft Azure – Create the Cloud Service and Storage Accounts

September 28, 2015 at 7:49 pm in Azure, Cloud, DC, IaaS, PowerShell by Wim Matthyssen

This blog post is part of the step by step to deploy replica DCs on Azure which can be found here: http://scug.be/wim/2015/09/28/deploying-replica-dcs-in-windows-azure/

In this part I will setup the Cloud Service that acts as a container to store my replica DC VMs. This Cloud Service which is part of my Azure virtual network (VNET), provides a unique public DNS name, a public IP address (VIP), and a set of endpoints to access the DC VMs over the Internet (those endpoints will be deleted at the end of the blog series for security reasons).

So, first of all let us create the Cloud Service in the virtual network via Custom Create:

1) In the Azure Management Portal, click New -> Compute -> Cloud Service -> Custom Create

clip_image002

2) In the field URL, enter a unique name to use in the public URL for accessing your cloud service. In my example I use “contoso-azure-dc”. Secondly, in the field Region or Affinity Group, select the geographic region or affinity group to deploy the cloud service to. In my example I use “West Europe”

clip_image004

3) Click Create Cloud Service and as you can see the Cloud Service is successfully created

clip_image006

You can also use Azure PowerShell (run as Administrator) to create the Cloud Service:

clip_image008

Before we create the necessary Storage Accounts, first some remarks:

  • The Active Directory database and logs will be placed on a separate data disk (with NO caching)
  • Data disks should always be the maximum allowable size (1 TB), keep in mind that you only pay for what you use (16 TB total per VM)
  • In my example I use Locally Redundant Storage (stores 3 replicas of your data within the primary location)
  • In the Standard Tier maximum IOPs is 500 IOPs per disk, if higher IOPs are needed you can use Storage Spaces
  • Keep in mind that the D: drive named “Tempory Storage” is a tempory drive (local storage), never place critical unreplicated data on it (modify persistent drive letters to avoid D:)
  • I always use separate Storage Accounts to store OS disks and data disks. This reduces the number of custom images to be copied to the Storage Accounts and you have a better overview of all your different disks
  • Azure support suggests to don’t have more than 40 disks (total of 20,000 IOPs) per Storage Account
  • You can have 100 Storage Accounts and 4,000 Active Disks per Subscription as recommended limits

So now it is time to create the necessary Storage Accounts:

1) In the Azure Management Portal, click New -> Data Services -> Storage -> Quick Create

In URL, enter a name for your storage account. In my example I use “azuos1”. In Location/Affinity Group, select a location for your storage account. In my example I use “West Europe”. As Replication Mode I select “Locally Redundant”. At the end click Create Storage Account

clip_image010

2) Repeat the same steps to create the second Storage Account. In my example I use “azudata1”“West Europe”“Locally Redundant”

clip_image012

clip_image014

You can also use Azure PowerShell (run as Administrator) to create the Storage Accounts:

clip_image016

That ends the first part of this series. Please continue through the rest of the series to complete the setup (if all are available).

Till next time!

Wim Matthyssen (@wmatthyssen)

Share on LinkedInTweet about this on TwitterShare on Google+Share on Facebook