Export (0) Print
Expand All

Configure Azure storage

Updated: August 20, 2014

Applies To: System Center 2012 R2 Data Protection Manager, System Center 2012 SP1 - Data Protection Manager

You can store backed up data for short-term storage to tape, to disk, or to a combination of disk and Microsoft Azure. Backing up data to Azure as well as to disk provides a method for keeping short-term backups offsite in addition to on-premises. With backup to Azure enabled, your disk-based replicas are backed up to Azure storage.

Deploying WAOB for DPM

Note the following:

  • You can back up the following workloads to Azure:

    • File data

    • Hyper-V virtual machines

    • SQL Server databases

  • Supported file types include:

    • Encrypted (Full backups only)

    • Compressed (Incremental backups supported)

    • Sparse (Incremental backups supported)

    • Compressed and sparse (Treated as Sparse)

    Unsupported file types include:

    • Hard links (Skipped)

    • Reparse points (Skipped)

    • Encrypted and compressed (Skipped)

    • Encrypted and sparse (Skipped)

    • Compressed stream

    • Sparse stream

  • DPM servers on case-sensitive file systems are not supported.

  • DPM must be running on a server installed with Windows Server 2012 R2, Windows Server 2012, or Windows Server 2008 R2 with SP1. The DPM version must be DPM in System Center 2012 SP1 or System Center 2012 R2.

  • To use Azure Backup you’ll need an Azure account with the Azure Backup feature enabled. For information about a free trial, see Windows Azure Free Trial.

  • You’ll need to install the Azure Backup Agent on the DPM server. The server will need at least 2.5 GB of local free storage space for cache location. although 15 GB is recommended.

  • You’ll need a management certificate that you’ll upload to the backup vault in Azure for authentication purposes.

    • To upload to the certificate to the vault, you’ll need to export it as a .cer format file that contains the public key.

    • The certificate should be an x.509 v3 certificate.

    • The key length should be at least 2048 bits.

    • The certificate must have a valid ClientAuthentication EKU.

    • The certificate should be currently valid with a validity period that does not exceed 3 years.

    • The certificate should reside in the Personal certificate store of your Local Computer.

    • The private key should be included during installation of the certificate.

Prepare for backup to Azure as follows:

For additional resources, see Information and Support for System Center 2012.

Tip: Use this query to find online documentation in the TechNet Library for System Center 2012. For instructions and examples, see Search the System Center 2012 Documentation Library.
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
© 2014 Microsoft