SALES: 1-800-867-1380

Prerequisites for DPM backup

Updated: July 11, 2014

DPM can back up some workloads to Microsoft Azure or short-term storage. This topic covers supported scenarios and prerequisites.

The following workloads can be backed up from DPM to Azure using Windows Azure Backup:

  • Protection for file system

  • Protection for virtual machines

  • Protection for 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)

These workloads aren’t supported:

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

  • Unsupported file types include:

    • Hard links (Skipped)

    • Reparse points (Skipped)

    • Encrypted and compressed (Skipped)

    • Encrypted and sparse (Skipped)

    • Compressed stream

    • Sparse stream

  • A server installed with Windows Server 2012 R2, Windows Server 2012, or Windows Server 2008 R2 with SP1, and running in System Center 2012 SP1 or System Center 2012 R2.

  • You must have a Windows Azure account that has the Windows Azure Backup feature enabled. If you don't have an account, you can create a free trial account in just a couple of minutes. For details, see Windows Azure Free Trial. Note that Windows Azure Backup uses the current pricing model at the time of writing (June 2013)

    • Charges are according to the amount of data stored in Windows Azure.

    • Up to 5 GB per month storage is free of charge.

    • Information about storage charges after 5 GB per month are available at Backup. While this feature is in preview there is a discount of 50% during the preview period.

  • Using Windows Azure Backup requires the Windows Azure Backup Agent to be installed on servers you want to back up. The server must have at least 2.5 GB of local free storage space for cache location, although 15 GB of free local storage space to be used for the cache location is recommended.

  • A management certificate that you will upload to the backup vault in Windows Azure Backup. Note the following:

    • To upload to the certificate to the vault, you must 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.

    • You can create a self-signed certificate using the makecert tool, or use any valid SSL certificate issued by a Certification Authority (CA) trusted by Microsoft, whose root certificates are distributed via the Microsoft Root Certificate Program. For more information about this program, see Microsoft article Windows Root Certificate Program members.

To use makecert.exe note that:

  • If you register the server you used to run makecert.exe, you can browse for the certificate using the Register Server Wizard (after installation of the agent).

  • If you want to register a server that was not used to run makecert.exe, you must export the .pfx file (containing the private key) from that server, and copy it to the server you want to register, and import it into the Personal certificate store on that server. After the import, you can browse for the certificate using the Register Server Wizard (which runs as part of the agent installation application).

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
© 2014 Microsoft