Prerequisites:

We need the following prerequisites first:

VM:

• 2 vCPU
• 4096MB Memory dynamic min. 512MB – max. 8192MB
• Systemdrive – 128GB Dynamic
• Backupdrive – <whatever you need>GB

User Accounts:

SQL:

Install SQL Server local on DPM Server or use a remote SQL Server (DPM 2016 does not support AlwaysOn Groups – so i will install a local SQL Server instance on DPM VM itself)

<sql.ini>

SQL components you need:

• DataBase engine
• Reporting Services Native

..in addition you need SQL Server Management Studio (DPM setup check this prerequisite) – if you do not install management studio you will receive this error while installation of DPM:

..so start install of SQL Management Studio:

Install:

The ISO of DPM you can download, have only a single MSI file that extract the source files for installation – you can mount this from a remote source, extract remote, or as same i will do – copy the MSI to C:\Temp – double-click on the MSI package and enter C:\Temp\DPM2016Setup as destination directory.

After extracting – double-click on setup.exe – install will start:

…enter the localhost-name and the name of the sql instance you installed before with the SQLxxx.ini…

…setup will check and install all prereq´s – while installing Hyper-V PowerShell Modules you have to restart the DPM server and run setup again:

..after reboot – start DPM setup again:

…after finishing of setup – install all updates – at time of creation of this blog it is “Update Rollup 2 – Data Protection Manager 2016”

Remote Administration:

If you want to remotely manage your DPM server and have a “Administration Workstation” you can install “DPM Remote Administration” there. (HINT: other tutorials and howto´s tell you that you need SCOM, Management-Packs,… to install Remote Tools – thats not correct – for “Remote Administration” you need nothing of these – you need SCOM,.. only if you want to install “DPM Central Console”…

…after finish setup of Remote Administration you have to check for Updates – because DPM Console checks the version between Console and Server and need the same on both. (you receive an error starting a console with an old version…)

Post-Task´s after finishing setup:

Add Disks/Volumes to DPM:

DPM uses a new concept called MBS (Modern Backup Storage) – based on ReFS Volumes with Storage Spaces – so adding disks is completely different than in DPM 2012R2 – in my case i will add two virtual disks (dynamic and 64GB) to my DPM Server VM (you can add additional disks later) and start with Server Manager in dem DPM Server VM:

…right click on the first disk and click on new storage pool (choose ONE disk has a reason: this will create a Storage Pool with column size 1 – so you can later simple add single disks to the pool)

..give the new pool a name:

…if you have a physical DPM Server with JBODs – best practice here is to add several disks and configure one of them as Hot-Spare – because we have a DPM virtually – we need no hot-spare:

…now we create a virtual disk:

…best practice is to use a simple layout:

…we use Fixed provisioning type:

…specify a size a little smaller than the disk (we expand this volume later):

…deselect create volume and click on close:

…add the second disk to storage pool:

…and extend the virtual disk:

..i will not use all (in this example) 128GB:

…now we can create a volume on the new vdisk:

..add a drive letter:

…now you can add this volume to DPM:

HINT: you have to click on rescan if you don´t see your new volume here…

…give it a friendly name and click ok:

Add Agents:

Now it´s time to add agents to DPM – click on Agents in console and click Install:

HINT: if you want to install an agent in a untrusted source (not domain joined source or in a domain that do not trust – see my post: Install DPM agent in unstrusted workgroup…

..in my environment in want to install it first on my hyper-v cluster – so i choose my both hyper-v nodes (not necessary to include clustername – ie “hvfc”):

..enter a account that has local admin rights on this servers (you can use your own account, it is only for the installation of agent NOT for service or other purposes..)

..a reboot of ALL (because it is a cluster) is necessary to add hyper-v nodes/cluster to DPM – i will not start automatically (you must restart ALL clusternodes)

..if you receive a error – check your firewall settings on the target computers (for all port exclusions see: https://technet.microsoft.com/en-us/library/hh757794(v=sc.12).aspx – for a list of exclusions only for dpm agents see: https://technet.microsoft.com/en-us/library/hh758204(v=sc.12).aspx):

HINT: easy way – use the following powershell cmdlets on the potentially protected computers:

..or use a GPO – after setting the correct port exclusion – agent installation will work: