Adding Microsoft Azure Backup to DPM 2012 R2

With the recent update to the Long Term Retention Periods for Azure backups and the features planned for the new year, I have recently begun talking to more clients about the integration of DPM with Azure Backup. The Backup Vault is a great feature of Azure that can take place of those boxes of tapes that require archiving offsite every week and speed up the recovery time of end user data.

The following article gives a quick overview of how easy it is to register and link a DPM 2012 R2 server with an Azure Backup Vault.

The first step to the process is to log into Azure, select Recovery Services then click the + NEW button to create a Backup Vault.


Once the Backup Vault has been created, clicking on the vault to open it to make available the options to download the two required files. The first file being the Azure Backup Agent which will need installing on the relevant DPM server and the second file which is the validation file, this will be required when registering the DPM server with the Azure Backup Vault.


Once the Backup Vault has been created and both the DPM agent and Validation file have been downloaded to your DMP server. The next step is to install the agent. During the installation process it is possible to change the installation path and the cache location. The cache location is used to keep track of the files that have been archived to Azure and require disk space equivalent to at least 5% of the planned backed up data.


Once the agent is installed, the next stage of the process starts from within DPM. Open the DPM console and browse to the Management view, then click on the Online option in the left hand window. clicking on the Online option will change the ribbons view exposing the options required for the next step.


From the ribbon select the Register option, this will open the Register Server Wizard.


The first page of the wizard is used to setup any proxy that is required for the server to make a connection to the internet. Either fill in the necessary proxy details in or leave blank if no proxy is required and click next.


The second page of the wizard is used to import the validation file that was downloaded during the creation of the Backup Vault within Azure. This is used to validate the DPM server against the Azure tenancy and the Backup Vault. Using the validation file negates the need for uploading expensive certificates.


The next page offers the ability to setup different bandwidth throttling for work and none work hours.


The following page makes it possible to configure the location of the staging location. The staging folder is a location that is used by the Agent when recovering data from Azure and as such should have enough disk space to house the volume of data expected to be restored in the largest restore envisaged.


For security the next step of the install asks for a passphrase to be configured. This can be one that is predefined or its possible to allow the agent to generate a phrase for you.


Clicking the Register button completes the process.

It is now possible to edit protection groups and add backup copies to Azure.


Add Azure AD and assign a Custom Domain Name

When creating an Azure directory, the default domain ends with the prefix. This is obviously not always the preferred naming convention, it is therefore possible to purchase the required domain and assign it to your Azure AD.

To begin, scroll down the left hand menu and select Active Directory.


Once Active Directory has been selected, the next step is to click on + NEW and select Directory then Custom Create.


Fill in the name of the directory you wish to create and the country or region you wish the directory to be located in, then click the tick to continue.


Once the directory has been created, click on the directory to open up the dashboard panel to configure the next options.


Click on the Domains menu at the top of the dashboard window.


Once on the Domains window, you will see the default domain name which has been created with the extension. To assign a custom domain, click Add a Custom Domain which will open the Add Domain wizard.


In the next window, add the name of the custom domain that has been purchased. If it is required, check the I plan to configure this domain for single sign-on with my local Active Directory and then click add.


Once the domain has ben successfully added, click on the arrow to continue to the next page.


The next windows requires the domain to be verified. This is achieved by adding a TXT record to the DNS of the purchased domain, Azure will verify the domain name against this TXT record.


When successfully verified, click the tick button to close the Add Domain wizard.


Now both domain names can be viewed, the original domain and the custom domain of Select the custom domain name and then click the Change Primary button on the bottom Azure menu.


On the Change primary domain wizard, check the current primary domain and the new primary domain are correctly selected. If the settings are correct, click on the tick button and the primary domain is switched to the custom domain.


Once the changes have been made, it is possible to view in the domains window, that the primary domain has been changed to the custom domain.


It’s as easy as that!


Transform The Datacentre Workshop, Supported by Microsoft


I have recently been invited to present at a number of events. The first event, Transforming the Datacentre Workshop, Supported by Microsoft, covered Microsoft’s Cloud OS approach to deliver a consistent and comprehensive set of capabilities via Windows Server, Hyper-V, System Center and Microsoft Azure, across on premise and cloud based platform.

Included in the event is a discussion around Windows Server 2003 reaching end-of-support on July 14th 2015, what options are available and how best to approach the problem.

It has been great to see the numbers of people turn up and very interesting to hear how they are adopting the Hybrid Cloud and plan to deal with the challenges around Windows Server 2003 reaching end-of-support.

cardiff-1st-october-2014-02If you fancy joining us at one of the multiple locations we are running the event at, you can book in by following the link below.


Failover Cluster Nodes with Mixed Upper & Lower Case Names

Over the years I have come across clusters in all sorts of states. Many with nodes that have a mixture of none standardised names or letter case. In my mind, a naming standard for nodes should be decided on in advance, one that will allow for additional nodes to be added to the cluster at a later date.

The issue that I come across the most, is that of cluster node names that are a mixture of upper and lower case. This in itself wont stop the cluster functioning but it is a personnel bugbear of mine.


Nodes can be add to a cluster in a mixture of case due to a number of reasons such as the case of the NETBIOS name and its not something you can ever be sure of when using the GUI.

One way you can be sure that the case will remain at what you specify, is to use the cluster.exe command to add the nodes to the cluster. The following shows one of the ways it can be used to import a new node into a cluster.

cluster.exe /cluster:clustername /add /node:NODENAMEINCASE

This command can be used on a 2008, 2008 R2, 2012 and 2012 R2 clusters, however if planning to use cluster.exe on a 2012 or 2012 R2 cluster, you will first need to enable the Failover Cluster Command Interface feature. To do this open the Add Roles and Features Wizard then browse to Features\Remote Server Administration Tools\ Failover Clustering Tools\ and select the Failover Cluster Command Interface feature.


Once the feature has been enabled, its possible to go ahead and use cluster.exe to add the node into the cluster in the necessary case.


Once the command has run successfully and the node has been added and validated against the cluster, things will look nice and standardised.



What is this temporary storage attached to my Microsoft Azure VM?

I follow the Microsoft Azure article How to Attach a Data Disk to a Windows Virtual Machine and I am told not to use D:\ as a drive label because it already exists. Why is this?

Virtual machines created in Windows Azure are created with temporary storage assigned automatically.

Depending on the OS this can appear as:

  • Windows Virtual Machine “D:\”
  • Linux Virtual Machine “/dev/sdb1/”


Essentially, the temporary storage is used for the paging file of the running VM. Using local storage on the physical host helps to increase IOPS and lower latency when compared to standard Azure storage.

It is obviously possible to store data on this drive BUT  do not use it to store data that you are not willing to lose! The reason for this is, the temporary storage is created on the physical machine that is hosting your virtual machine. Should your virtual machine move to a different host due to hardware hardware failure or local host updating, the OS disk will be recreated from your storage account. However the temporary storage will be reallocated on the new physical host and any data will not be migrated from the original host. Other causes for the temporary storage to be recreated include when you resize your VM or when your VM is shutdown and restarted.

The size of the temporary storage changes between virtual machines but an up to date size can be found on this Microsoft Azure article Virtual Machine and Cloud Service Sizes for Azure

This image is from the Microsoft Azure Support Team Blog, but shows this process.