Upgrading DPM 2012 R2 to DPM 2016 on same hardware RRS feed

  • Question

  • Hi 

    I've read the following post re upgrading DPM 2012 R2 to DPM 2016 and have a query on the styep by step process:

    I am planning to also upgrade the OS from Windows 2012 R2 to Windows 2016 but wanted clarification on this statement:

    Some DPM 2016 features, such as Modern Backup Storage, require the Windows Server 2016 RTM build. It is possible to upgrade DPM 2016 from DPM 2012 R2, running on Windows Server 2012 R2. However, customers receiving DPM 2016 will want the latest features, so Microsoft recommends installing DPM 2016 on a new installation of Windows Server 2016 RTM

    I read this to mean that if you want to use the new features of DPM 2016, the Windows 2016 installation needs to be a fresh build, not an upgrade from Windows 2012 R2 - is this correct?  If so I guess the upgrade process is effectively going to be a migration to a new server rather than an in place upgrade?



    Monday, December 2, 2019 3:57 PM


All replies

  • Hello Chris,

    It does not have to be a fresh installation, from DPM 2016 and onward, DPM uses "volumes", in earlier versions of DPM it uses "disks".

    When you add new storage in DPM 2016/2019 running on Windows Server 2016 or newer, it will use "volumes", in pre Windows Server 2016 "disks" were used.

    The "volumes" will benefit of the new Modern Backup Storage (MBS) feature, while the old "disks" won't benefit from it.

    DPM 2016 & 2019 accepts both volumes or disks for storage, once you add a volume, DPM formats the volume to ReFS (with 4K allocation unit size) to use the new features of Modern Backup Storage.

    Note: Volumes cannot reside on a dynamic disk, use only a basic disk.

    Here's an example for you:

    If you have upgraded from an earlier version of DPM to version 2016/2019, and you have kept the old storage, DPM will see the old storage as "disks", and they will not benefit from the Modern Backup Storage feature, meaning they will be NTFS formatted disks. 

    Hope this makes it more clear :-)

    Best regards,

    Blog: LinkedIn:

    • Edited by Leon Laude Monday, December 2, 2019 9:56 PM Clarification
    Monday, December 2, 2019 4:26 PM
  • Thanks Leon.  I may have to go down the upgrade route I think.  We have plenty of space on the disk storage at present and it means minimal disruption and downtime whilst running an upgrade and not needing to remove, add and then migrate old disk storage to new.

    Once I have upgraded everything, would it be possible at a later stage to remove the DPM repository and add it as modern backup storage or is it a permanent restriction once the upgrade option has been done?

    Friday, December 6, 2019 10:59 AM
  • Yes you can remove the old "disks" later on, and then basically recreate/reformat the disks and re-add it to DPM and it will make use of the modern backup storage feature.

    Blog: LinkedIn:

    • Marked as answer by chris624 Friday, December 6, 2019 3:46 PM
    Friday, December 6, 2019 11:06 AM
  • Thank Leon,

    One more query I wonder if you can clarify for me - Windows 2008 I know is not able to be protected on DPM 2016 as a physical server, and it looks as though it can't be protected as a Hyper-V guest, however do you know if this is definitely the case as it is protected as a VM with VMWare and also Windows Storage Server 2008 SP2?



    Friday, December 6, 2019 12:15 PM
  • DPM 2016 can protect Windows Server 2008 SP2 / Windows Server 2008 R2 both on Hyper-V and VMware.

    Blog: LinkedIn:

    Friday, December 6, 2019 12:38 PM
  • Thanks Leon - I looked at that earlier which is why I was querying it.  It states for Windows 2008 SP2 the following:

    Servers (32-bit and 64-bit) Windows Server 2008 SP2 Physical server

    On-premises Hyper-V virtual machine
    N N Volume, share, folder, file, system state/bare metal

    Friday, December 6, 2019 2:00 PM
  • I suppose your screenshot was meant to be Windows Storage Server 2008 SP2?

    If it isn't listed for VMware as a virtual machine, it is not supported, that means it's only supported when running either as a physical server or virtual machine running on Hyper-V.

    Blog: LinkedIn:

    Friday, December 6, 2019 2:22 PM
  • No, the Windows Storage Server 2008 is this one which it says is supported:

    Servers (32-bit and 64-bit) Windows Storage Server 2008 SP2 Physical server

    On-premises Hyper-V virtual machine
    Y Y Volume, share, folder, file, system state/bare metal

    Its slightly confusing I think as I would have thought 2008 SP2 would be ok as a Hyprer-V guest if it is able to back it up as a VMWare guest.

    Friday, December 6, 2019 3:16 PM
  • Ah I see what you mean now, yes it's a bit weird, but usually host-level backups don't require the agent to run on the server itself and it only backs up the .VHD/.VHDX which makes it easy compatibility wise.

    Blog: LinkedIn:

    Friday, December 6, 2019 3:27 PM
  • That's what I was thinking too - it doesn't have an agent on it and you would like to think that if it can backup a VM on VMWare, it should be able to backup a VM on Microsoft's own virtual platform!!  I may have to test it first to be sure though.

    Thanks again for your help Leon,



    Friday, December 6, 2019 3:46 PM
  • You're welcome Chris, if you have any other concerns feel free to ask!

    Please also don't forget to mark helpful replies as answer, it helps the community to identify helpful posts, thanks!

    Blog: LinkedIn:

    Friday, December 6, 2019 4:01 PM