Microsoft Azure Backup provides backup for rich application workloads like Microsoft SQL Server, Hyper-V VMs, SharePoint Server, Microsoft Exchange and Windows clients with support for both Disk to Disk backup for local copies and Disk to Disk to Cloud backup for long term retention.
With Microsoft Azure Backup, you can protect application workloads such as Hyper-V VMs, Microsoft SQL Server, SharePoint Server, Microsoft Exchange and Windows clients to:
– Disk (D2D), giving high RTOs for tier 1 workloads
– Azure (D2D2C) for long term retention.
And, you can manage the protection of various protected entities (servers and clients) from a single on-premises user interface.
You can deploy Microsoft Azure Backup server as:
– A physical standalone server.
– A Hyper-V virtual machine – You can run DPM as a virtual machine hosted on an on-premises Hyper-V host server, to back up on-premises data.
– A Windows virtual machine in VMware – You can deploy DPM to provide protection for Microsoft workloads running on Windows virtual machines in VMware. In this scenario DPM can be deployed as a physical standalone server, as a Hyper-V virtual machine, or as a Windows virtual machine in VMware.
– An Azure virtual machine – You can run DPM as a virtual machine in Azure to back up cloud workloads running as Azure virtual machines.
Get the software here
Prepare Microsoft Azure Backup server to back up data by:
- Creating a Backup vault — Create a vault in the Azure Backup console.
- Downloading the vault credentials — In Azure Backup, upload the management certificate you created to the vault.
- Downloading Microsoft Azure Backup server — You can download Microsoft Azure Backup server for application workloads from the Quick Start Page of a backup vault.
Microsoft Azure Backup server inherits the functionality of Data Protection Manager (DPM) for workload backup. You will find pointers to DPM documentation for some of these capabilities. However Microsoft Azure Backup Server does not provide protection on tape or integrate with System Center.
Keep this in mind when you are using dynamic memory. this is just a warning.
No you can’t you need to run SQL on the local machine. And Currently you can’t use Windows Server 2016 TP3
In order to get passed the Recommendations you need to install .Net3.5 and SIS-Limited
start /wait dism.exe /Online /Enable-feature /FeatureName:SIS-Limited /quiet /norestart
and the .Net3.5 can be installed with Powershell or GUI
and incase of trouble installing .NET3.5
Remember a reboot is needed.!
When Choosing the Installation folders you need to be careful there is a bug
When using a root install sys just change the drive letter there is a \\ instead of the \ !
Better use a folder to install the bits.
Pick a password. and the next steps will install the Azure Recovery Agent.
Azure Recovery Services Agent setup is installed but you will need the Azure Credentials for the Backup Vault
If you don’t have a backup vault you will need to create one else just save the Credentials file to a location.
Incase you did nod create a Backup Vault.
In the dashboard there is a option to download the vault credentials.
Using the Credentials and saving the encryption key to a save location. that is not the C drive !! without the key you are unable to restore anything!!
After the SQL server is installed You are almost ready to backup some files.
Supported Operating System
Windows Server 2008 R2 SP1, Windows Server 2012, Windows Server 2012 R2
Minimum: 1 GHz, dual-core CPU
Recommended: 2.33 GHz quad-core CPU
Hard Drive Space:
Disks for backup storage pool: 1.5 times size of data to be protected
Open the Azure Backup in the start menu.
when checking About you will see that this is DPM – Data Protection manager.
Now we can add some Storage and adding some Agents to the Azure Backup Vault and create a protection group.
Installing and Operating is real easy, install an agent but remember if you already installed the Azure Recovery backup Agent you need to deinstall this agent and install the DPM agent.
Here you can choose it the Protection Group needs to upload the data to Azure or leave this on premise
Also Choose what to upload to Azure. maybe the Disk is ok but the system state is only available local.
The backup schedule is as the same as in the Azure Backup
Protecting my DC. As I did use the Azure ASR backup and I had to install manually ( PowerShell – manually ) an agent with DPM you can deploy this easily in your domain.
Many more options are there in DPM / Azure Backup but this blog post get you started with backup to the cloud.