In this fast Hybrid Cloud world where a lot is changing, backing up your data is important for Enterprise organisations.
With System Center 2012 R2 Data Protection Manager you can do a lot. I made a High Level Design of our
System Center 2012 R2 DPM POD’s ( Dell PowerEdge R620 Server with MD1200 SAS Storage Enclosures ).
For the first time we skipped to buy a Tape Library for long time protection, we now backup to Microsoft Azure Backup Vault storage for long time protection. So we have no tape management any more.
When you have more System Center 2012 R2 Data Protection Manager Servers in your Datacenter, you can think of Scale-Out protection where you are more flexibel in your Datacenter to save your data.
Here you can read more about System Center 2012 R2 DPM Scale-Out protection
System Center Data Protection Manager (DPM) offers backup to Azure for long term protection by leveraging Azure Backup. The first step in configuring DPM-A (DPM backup to Azure) is to register the DPM server to the Azure Backup vault. This article explains how the registration process is greatly simplified and enhanced with Update rollup UR4 for DPM.
Till Update Rollup 3 (UR3), users were required to generate a self-signed certificate and upload this certificate to the backup vault through the portal. During the registration process, the certificate was used to register the server to the backup vault. While this process ensured security, it was a bit overwhelming.
With UR4, registration of the DPM server to the Azure Backup vault is simplified without compromising on the security by using a concept called “vault credential”. A vault credential is an authentication entity that can be downloaded from the backup vault on the portal. The vault credential is valid for 48 hours from the downloaded time and can only be used during the registration process to authenticate the server with the backup vault.
Here you can read more on Simplified workflow to configure backup to Azure from DPM