Updated 09/02/2017: [Announcing backups of SQL Server 2016 and SharePoint 2016 with DPM 2016 Update Rollup 2. DPMDB can also be hosted on SQL Server 2016].
Happy New Year everyone!
We continue our series on deploying System Center Data Protection Manager 2016.
While working on several projects to upgrade System Center Data Protection Manager 2012 R2 to 2016. I thought why not automating the installation of DPM 2016.
If you are looking to automate the deployment, this post is right for you.
A little bit of Background
A while ago, I wrote an article on how to install DPM 2016 on Windows Server 2016 and SQL Server 2016. This was described the manual way.
Assuming you have already deployed a new Windows Server 2016 fully patched. There are two required updates to be installed immediately after you install Windows Server 2016:
1. Servicing Stack Update for Windows Server 2016 for x64-based Systems (KB3199986).
Automate SQL 2014 SP2 Installation
You can disregard this step if you already have SQL server deployed locally or on another server in your environment.
Mount SQL Server 2014 SP2 media and run the following command to automate SQL installation and add all the required features for DPM.
But before installing SQL Server, you need to install .NET Framework 3.5 SP1 which is a requirement for SQL Server 2014. However, with SQL Server 2016, this requirement is gone and replaced with .NET Framework 4.6.
Assuming your DPM server is connected to the internet, open Windows PowerShell and run the following command to install NetFx3 from Windows Update just as if we had checked the box in Windows Features:
Dism /Online /Enable-Feature /FeatureName:NetFx3 /All
Now we are ready to install SQL Server 2014. Open the command prompt and run the following as one command:
Note: Update the domain name, SQL service accounts and password according to your environment.
Setup.exe /Q /ACTION=install /IACCEPTSQLSERVERLICENSETERMS /FEATURES=SQLEngine,RS /INSTANCENAME=DPMINSTANCE /INSTANCEDIR="D:\Program Files\Microsoft SQL Server" /INSTALLSHAREDWOWDIR="D:\Program Files (x86)\Microsoft SQL Server" /INSTALLSHAREDDIR="D:\Program Files\Microsoft SQL Server" /SQLSVCACCOUNT=”VIRT\sqldpm” /SQLSYSADMINACCOUNTS=”VIRT\sqldpm” /SQLSVCPASSWORD="dpm2016+1" /RSSVCACCOUNT=”VIRT\sqldpm” /RSSVCPASSWORD="dpm2016+1" /AGTSVCACCOUNT=”VIRT\sqldpm” /AGTSVCPASSWORD="dpm2016+1" /SECURITYMODE=SQL /SAPWD=”dpm2016+1” /SQLTEMPDBDIR=”D:\Program Files\Microsoft SQL Server\TempDB\\” /SQLUSERDBDIR=”D:\Program Files\Microsoft SQL Server\SQLData\\” /SQLUSERDBLOGDIR=”D:\Program Files\Microsoft SQL Server\SQLLog\\”
Automate DPM 2016 Installation
DPM supports item-level recovery (ILR), which allows you to do granular recovery of files, folders, volumes, and virtual hard disks (VHDs) from a host-level backup of Hyper-V virtual machines. Therefore, the Microsoft Hyper-V Role and PowerShell Management Tools windows feature should be installed. This software is required for Data Protection Manager to run correctly.
Open a command-line in elevated mode on the DPM server, and type the following:
dism.exe /Online /Enable-feature /All /FeatureName:Microsoft-Hyper-V /FeatureName:Microsoft-Hyper-V-Management-PowerShell /quiet /norestart
Restart the DPM server before you move on to the next step.
Copy the following script into Notepad and save it on the DPM server as DPMSetup.ini.
You can use the same script below whether the SQL Server instance is installed on the DPM server or on a remote server.
When creating DPMSetup.ini, replace the text inside < > with values from your own environment.
SqlAccountPassword=<The password for the SQL sa account>
ProgramFiles = <Location path where you want to install DPM>
DatabaseFiles = <Location path where you want to install DPMDB>
IntegratedInstallSource = <Location path where the DPM media is extracted>
SQLMachineName=<Name of the SQL Server Computer> OR <SQL Cluster Name>
SQLInstanceName=<Name of the SQL Server instance>
SQLMachineUserName=<Domain-name\Username> SQLMachinePassword=<Password for the user name Setup must use>
SQLMachineDomainName=<Domain name to which the SQL Server computer is attached to>
ReportingMachineName=<Name of the SQL Server Computer> OR <SQL Cluster Name>
ReportingInstanceName=<Name of the SQL Server instance>
ReportingMachinePassword=<Password for the user name Setup must use>
ReportingMachineDomainName=<Domain name to which the SQL Server computer is attached to>
Here is a real example for DPMSetup.ini file:
After saving the file, at an elevated command prompt on the installation DPM server, type the following:
start /wait D:\SCDPM2016\setup.exe /i /f D:\DPMSetup.ini /l D:\dpmlog.txt
D:\SCDPM2016\ indicates the media location where you’ll run setup.exe from, and D:\DPMSetup.ini is the location path of the .ini file.
Sit back and relax… DPM will be installed automatically as shown in the following screenshot:
Last but not least, you need to run Windows Update and install Update Rollup 1 for System Center 2016 DPM KB3190600. This update is very important in order to start using Modern DPM Storage (MDS) and Resilient Change Tracking (RCT) based Hyper-V VM backups.
Thanks for reading!