Microsoft DPM Upgrade & Operations Package

SECTION 1: Executive Summary

Environment:

• Current DPM Configuration:
• Windows Server 2016 Datacenter VM
• System Center Data Protection Manager (DPM) 2016 – v5.1.378.0
• SQL Server 2016 (local instance)
• Synology NAS storage (iSCSI LUNs + CIFS shares)
• Backing up ~35 enterprise servers

Goal:

• Upgrade DPM from 2016 to 2019
• Ensure compliance with current licensing requirements
• Maintain backup continuity and performance

Recommendation Summary:

• Proceed with a side-by-side upgrade for improved resiliency.
• Purchase System Center 2019 Datacenter core licenses (and Windows Server 2019 licenses if deploying a new OS).
• Reuse Synology storage or provision new LUNs for replica volumes.
• Retain the old DPM server in read-only mode until legacy recovery points expire.

 

SECTION 2: Licensing & Procurement Guidance (Non-EA Customers)

How to Obtain Licenses:

• Use CSP (Cloud Solution Provider) or Volume Licensing (Open Value) via certified Microsoft partners like Xerox.

Where to Obtain Licenses:

• Microsoft Channel Resellers like Xerox, or directly through Microsoft’s partner portal.

 

Licenses Required:

Service	License Type
Windows Server 2019/2016	Windows Server 2019 Datacenter Edition (16-core minimum)
System Center DPM 2019	System Center 2019 Datacenter Edition (16-core minimum)
SQL Server for DPM	Bundled SQL Server Standard (local use only)

 

SECTION 3: Technical Upgrade Options

• In-Place Upgrade:
• Advantages:
• Retains backup data and protection groups.
• Lower cost.
• Disadvantages:
• Higher risk, limited rollback options.
• Lower scalability path.
• Side-by-Side Upgrade:
• Advantages:
• New server (Windows Server 2019 preferred).
• Better testability and flexibility.
• No risk of data loss during rollback.
• Requires temporary dual licensing.
• Disadvantages:
• Higher initial cost, as two systems are running concurrently.

Factor	In-Place Upgrade	Side-by-Side Upgrade
Data Migration	No (retained)	Requires new replica data
Rollback Capability	Yes (must recreate backups)	No downtime or data loss in rollback scenario
Cost Efficiency	High	High (due to dual licensing)
Risk Profile	Moderate	Higher
Scalability Path	Limited	Better scalability options

 

 

SECTION 4: Network & Access Configuration

Ports Required for DPM Operations:

• TCP 135 – WMI / RPC
• TCP/UDP 5718, 5719 – DPM agent communication
• TCP 445 – File share access (SMB)
• TCP 1433 – SQL Server communication

Firewall Settings:

• Enable WMI-In, RPC-In, File and Printer Sharing (SMB-In).
• WMI Namespace: root\cimv2.

 

SECTION 5: Diagnostic Tools

Tool	Purpose
WMI Diagnosis Tool	Diagnose remote WMI connectivity
DPM Management Shell	PowerShell-based administration
Event Viewer (DPM Logs)	Monitor alerts and backup failures
Performance Monitor	Track disk throughput and bottlenecks
SQL Server Management Studio	Verify DPMDB health
Synology Resource Monitor	Validate NAS performance (DSM dashboard)

 

SECTION 6: Agent Deployment Account Setup

1. Create a domain service account (e.g., svc_dpmagent).
2. Grant local admin rights on all protected servers.
3. Add the account to the DPM Administrators group.
4. Ensure firewall allows remote RPC/WMI.
5. Use the account for pushing agents via DPM console.

 

 

SECTION 7: Backup Configuration

• Group servers by role (e.g., SQL, File, VM).
• Configure protection groups:
• Define replica and recovery point volume sizes.
• Set retention policy (e.g., 14 daily, 12 weekly, 6 monthly).
• Enable consistency check schedules.
• Verify disk capacity on Synology iSCSI LUNs.

 

SECTION 8: Backup Monitoring

• Use DPM Console Monitoring tab.
• Set up email notifications (SMTP required).
• Enable Event Viewer alerting or SCOM integration.
• Run Get-DPMBackupSummary for scripting reports.

 

SECTION 9: Basic Usage Guidance

• Add agents from Management > Agents.
• Protect workloads via Protection Groups wizard.
• Run manual backups or restores as needed.
• Test backup recovery monthly.
• Track space and recovery point usage.

 

SECTION 10: Client Management

• Maintain agent version compatibility post-upgrade.
• Push updates using DPM console or PowerShell.
• Monitor last successful backup per server.
• Schedule consistency checks.
• Use security groups for client access control.

 

Final Notes:

• Keep the legacy server in read-only mode if needed for legal hold.
• Document all upgrade activities in the change management system.
• Validate Synology iSCSI configuration and retention plans.
• Confirm that licensing aligns with total physical core counts.