DPM 2019 is a new version of the Microsoft Hyper-V backup software. This article will walk you through the steps to install and configure it on your computer.
The install dpm 2019 step by step is a tutorial on how to install DPM 2019 (Hyper-V backup) from the command line.
We talked through the Nakivo backup solution, and I’ll also be doing a DPM 2019 series. We’ll start with installation, which has a lot of requirements and may be difficult.
Before we get started, let’s have a look at
This method can be automated, but if this is your first time, it isn’t a terrible idea to perform it manually to familiarize yourself with the process and components required.
Here are some sites if you need additional information.
https://docs.microsoft.com/en-us/system-center/dpm/prepare-environment-for-dpm?view=sc-dpm-2019
https://docs.microsoft.com/en-us/system-center/dpm/install-dpm?view=sc-dpm-2019
Prerequisites
DPM 2019 will be installed on a Hyper-V inside VM, and this DPM tutorial will focus on backing up Hyper-V VMs.
On Windows Server 2019 DTCNTR, DPM will be deployed under a domain (informatiker.local).
Backup2 will be the name of the VM on which DPM will be deployed.
DPM 2019
Download System Center 2019 here: https://www.microsoft.com/en-us/evalcenter/evaluate-system-center-2019
If you’re unfamiliar with System Center, it’s a collection of products, and we’ll be using Data Protection Manager in this tutorial.
SQL
Aside from that, Installation of SQL is required. DPM will be the one to install SQL. I intended to utilize my current SQL installation in the lab, which is set to Always ON, however this isn’t possible.
For SGL, I’ll use the dpm admin account as the administrator account.
SQL
I have a SQL 2017 license, so I’ll be utilizing that — you can get SQL here: https://www.microsoft.com/en-us/evalcenter/evaluate-sql-server-2017-rtm
Using SQL 2019 should be OK as well.
SSMS
We will also need SQL SSMS in addition to SQL (18.9.1 is actual version at the time of writing this)
https://aka.ms/ssmsfullsetup
SQL Reporting Services is a set of tools that allows you to create
Finally, SQL Server 2017 Reporting Services must be downloaded.
https://www.microsoft.com/en-us/download/details.aspx?id=55252
Set SQL Server Agent service to Automatic start in Control Panel | Administrative Tools | Services after installing SQL (if you don’t, DPM installer can do it for you).
Only for a distinct SQL VM:
Make sure that inbound ports TCP 1433, 80, 443, and UDP 1434 are open if you have a different SQL installation on another VM.
Accounts for Users
For Windows login, sql logon, and DPM logon, I’ll use the same user – dpmadmin. Although it is not the greatest security practice, that account is the sole user on the domain and is only used on the one computer that hosts DPM.
In the domain, I established a distinct OU called DPM, which has three accounts.
dpm admin – DPM VM and DPM itself administrator
DPMSQL Agent – SQL Agent installation account
DPMsql DBEngine – SQL Database Engine account
Inside Windows Server 2019, dpm admin is also a local admin, which we will be installing.
System
The amount of RAM and CPU you need depends on what you intend to do with DPM and how much you plan to do with it. The disk configuration is the same.
In this configuration, I have a 250GB local drive that is not started or formatted.
Again, you must have a backup and disaster recovery strategy, as well as an understanding of how high your workloads are, how often you want to backup, and how long you must maintain backups. Then you can figure out how much bandwidth, storage space, and VM specifications you’ll need.
Roles and Features in Windows
We need to install Hyper-V Powershell from the Roles and Features area, which is found under Remote Server Administration Tools | Role Administration Tools | Hyper-V Management Tools | Select both Hyper-V Management Tools and Module for Windows Powershell.
If for some reason this does not work, you can instead execute the command in – Powershell to install the Hyper-V Powershell module (as Admin)
Enable-WindowsOptionalFeature -Online -FeatureName Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-Management-PowerShell
It’s also a good idea to have both.NET 3.5 and.NET 4 installed.
SQL installation
Because SQL is a requirement for this one, we’ll go through the whole installation procedure. Because my Always ON SQL installation isn’t supported, I couldn’t utilize it. On the DPM VM, I’ll start a fresh SQL installation.
This SQL installation tutorial will vary from my usual SQL setups. (I’m going to skip a few displays that aren’t important.)
Click Run as Administrator to begin SQL setup.
Standalone SQL Server installation
I’ll choose Evaluation version | Next for this LAB.
I consent | Next
So far, everything has gone well | Next
I’ll just pick Database Engine Services and leave the rest alone. Next
I’m going to call my instance DPM (you may leave it at default or give it a another name…) | Next
I’m going to use the domain accounts we created previously for SQL Server Agent and Database Engine. Default Collation (SQL Latin1 General CP1 CI AS) will be used | Next
I’ll disable Windows authentication and create a SQL user for dpm admin. I’ll leave everything else to default. Next
Install
Success
SSMS should be installed.
I’m not going to go through the installation of SQL Server Management Studio in detail. I’ll simply leave it here on this screen. After the installation is complete, restart the server.
Management Studio has been set up.
SQL 2017 Reporting Services should be installed.
Last but not least, DPM will not install without this component.
Set up the Reporting Services
Next | Evaluation
I consent | Next
Only Reporting Services should be installed | Next
Install
…
Restart. In my instance, it didn’t work, thus I had to manually reset the VM.
Setup the Report Server
Start Report Server Configuration Manager once the reboot is complete.
Connect
Change Network Service | Apply under Service Account.
URL of a Web Service I’ll simply rename the virtual directory ReportServerDPM and leave everything else alone. |
Next, go to Database and choose Change Database.
Next, create a new report server database.
You’ll need to input your SQL path, which in my case is BACKUP2DPM. I kept the rest of the settings alone and clicked on Test Connection. After that, everything should be OK – go on to the next step.
Next, I named the database ReportServerDPM.
Next | Service Credentials
Next
Everything has been completed – now it’s time to wrap things up.
Okay, the database is complete.
ReportDPM | Apply | ReportDPM | ReportDPM | ReportDPM | ReportDPM | ReportDPM | Report
Finally, click Delete under Encryption Keys.
Yes
Reporting Services may now be closed.
We can see that the ReportServerDPM DB has been established in Management Studio.
There’s one more thing we need to accomplish before we leave the SQL world.
Check TCP/IP settings in SQL Configuration Manager.
TCP/IP must be turned on.
Let’s go to the DPM installation now.
Installation of Data Protection Manager
Finally, after pages and pages of material, we’ve arrived at the stage where we’ll install DPM.
DPM is typically extracted to a temporary folder on my C disk.
Right-click setup and choose “Run as Administrator.”
Select Data Protection Manager from the Install menu.
Read the License Agreement | Accept if you want to continue reading. If you decline, the installation is complete 🙂
Welcome to the DPM wizard from Microsoft | Next
Use stand-alone SQL (Always-ON, which I have set, does not function with DPM), and the username and pass fields were greyed out shortly after I provided my server name (Backup2) and sql instance name (DPM). Select Install and then Check.
If you receive the message “DPM needs TCPIP protocol to be enabled on the chosen SQL Server instance…”, you’re on the right track. Whether you’ve already enabled TCP/IP, check to see if TCP/IP under IP addresses has status enabled and Dynamic port is either 1433 or empty in SQL Server Configuration Manager. Also, make sure you’re not using SQL Express – it won’t work and will give you this message (at least in my experience).
…
…
I received one warning since I’m using the Evaluation version of SQL, which I’m aware of. If you use this scenario in production (which you shouldn’t; you should only use it for testing), be aware that when the evaluation period ends, everything comes to a halt.
Next
On the following page, enter your login, business name, and Product Key | then click Next.
On the next page, you’ll choose an installation location and see which disks are required | Next
Despite the fact that Windows Updates may be troublesome, I recommend opting-in | Next.
So, let’s get started.
Before you begin the installation, make sure you have an active network connection. The installer requires certain network shares, and if you haven’t setup your network up to this point, the installation will fail.
The installation is complete! We may now close this window.
These are the firewall exceptions generated by DPM.
There are two new DPM icons on the desktop. To test whether it works, we’ll launch Microsoft System Center Data Protection Manager.
Okay, it’s functional.
I’m not going to make this any longer since it’s already a big wall of text.
We’ll save the setup and backup testing for later.
Conclusion
It’s a lengthy setup with a lot of little tasks to do in order for DPM installation to function. There are ways to make this more automatic, but I believe this is a decent approach for someone who is doing this for the first time and has minimal expertise with DPM and System Center.
Disclaimer
The system center data protection manager 2019 download is a tool that allows you to backup your computer. This article will show how to install DPM 2019 on Hyper-V.
Related Tags
- hyper-v backup and restore
- hyper-v backup best practices
- how to backup hyper-v virtual machines windows 10
- dpm installation step by step
- dpm 2019 sql requirements
