Data Protection Manager 2025 – Remote Administration and DPM Database Backup

Hello Marcin,

thank you for your answer.

I did read through these Microsoft articles as well, but they didn't fully answer my questions.

Regarding the first point, if I understand it correctly, then you really have to use an older Windows Server version to remote administrate a DPM 2025 installed on Windows Server 2025? That's annoying when you already have a management system running on Windows Server 2025 and can't use the remote administration console to manage the DPM backup server. I wonder if there will ever be a new Remote Administration Console or did Microsoft just stopped the development of it? What's the alternative?

Referring to https://learn.microsoft.com/en-us/system-center/dpm/back-up-the-dpm-server?view=sc-dpm-2025#back-up-the-dpm-database it seems that the backup server has to back up its own database, because it's not mentioning doing the backup from another DPM server. But the same Microsoft article contains also this section: https://learn.microsoft.com/en-us/system-center/dpm/back-up-the-dpm-server?view=sc-dpm-2025#back-up-the-database-to-a-secondary-server where it describes the steps to backup the database to a secondary DPM server, but doing it that way did not removed the mentioned notification in DPM console. So is it necessary to let the DPM server backup it's own DB to get rid of the notification?

Best regards

AEde-7

The alternatives are to administer DPM directly on the DPM server or maintain a supported older Windows Server/Windows client management machine for the DPM console. AFAIK, Microsoft has not announced a replacement Remote Administration Console for Windows Server 2025, so there is no confirmed indication that one is forthcoming (although it would be reasonable to expect it at some point).

For the DPM database warning, the important distinction is between protecting the DPM database on a secondary DPM server and configuring the DPM server to protect its own database. The warning is specifically telling you that the DPM database must be protected separately from the DPM server's replica data so that the DPM server can be recovered during a disaster.

Microsoft does support backing up the DPM database to a secondary DPM server, so using another DPM server is a valid disaster-recovery option. However, that secondary-server protection does not necessarily satisfy the condition that causes the notification in the primary DPM console to disappear. If your objective is specifically to clear that notification, the DPM 2025 server should have its own DPM database protected in a separate protection group, as described in the "Back up the DPM server" procedure.

So, in your situation, I would not interpret the persistent notification as meaning that the secondary DPM server backup failed. It is indicating that the primary DPM server does not have the locally configured, separate protection of its DPM database that the notification is checking for. The secondary DPM server remains useful as an additional disaster-recovery copy, but it does not replace the local DPM database protection for purposes of that warning.

If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

hth

Marcin