DPM Backup via VLT to AWS Glacier/S3 reliable RRS feed

  • Question

  • Hi,

    we are using DPM for a couple of years and honestly are not very happy with it, because is not very stable and reliable. We had in the past quite frequently issues after updates and have besides from that often Sync issues. Though with the few recovery cases we need it for recovery it did not let us down. :-)

    Another pain point is that DPM wastes storage space. For each source it allocates a partition and reserves spaces. So even with more than a third of free space we cannot protected more sources. Since Azure is expensive we consider using Glacier instead. Has any experience using it via virtual tape library?




    Saturday, January 2, 2016 5:44 PM

All replies

  • Hi,

    Backup data out of the Azure will incur additional cost. Please refer to how pricing is charged:-

    Lai (My blog:-

    Monday, January 4, 2016 2:11 PM
  • Hi John,

    I can relate to the pains of DPM, but found that, with our new setup, all pain have disappeared.

    We firstly upgraded to the latest version (2012 R2 with UR8), but then also virtualised our DPM server so it runs off dynamically expanding VHDX's, which removes the space problem as the VHDX only expands when backup data is copied. In addition, we also enabled Deduplication on the underlying storage, which saved us an additional 60%.
    All in all, we now found that DPM is much more reliable, but also consumes a fraction of the space.

    If you found the above cannot be implemented, I would still not recommend Glacier because it comes with one BIG hidden cost compare to Azure:

    Because DPM and Azure are integrated, every time to do a backup from DPM to Azure, you are only copying the changes (delta) up to Azure. Even if you use the system (like we do) as tape replacement for long term storage, only the delta are copied.
    If on the other hand you are using Glacier in conjunction with a VLT software, the entire backup to tape will be send over to Glacier instead of the delta only. This translate in a much larger use of storage which makes the pricing of Glacier less attractive.
    In addition, when pulling the data back from Glacier to on-premises, you are not only going to have to wait for a few days (which can be acceptable), but will also get hit with a large bill for downloading your data. 
    In azure, the data is accessible immediately, and the downloads are free.

    For example: 
    Say your total amount of live, backed up data is around 30TB with a weekly churn of +/- 3% and you are doing weekly "tape" backups ("Tape" means you replaced it to a cloud based solution).
    Each week, DPM will upload around 1TB up to Azure (the 3% delta only), which translate in a cost of +/-1024GB * $0.031 = +/- $31.
    On the other hand if DPM use Glacier, you will upload 30TB (like it would backing up to tape) each week at a cost of 30720GB * $0.007 = $215.

    Hope this helps.


    Tuesday, January 5, 2016 2:09 AM