Microsoft System Center | Other
Additional System Center tools and components for managing infrastructure, applications, and services
WHAT FOR ist MS Q&A if you NEVER get an answer?
DPM 2025 often has hanging disk backups for Exchange and SQL Server
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(220.8, 66%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESF%3C/text%3E%3C/svg%3E)
Stefan Falk
171
Reputation points
Hello everybody,
first: Why is there still no "Select a child tag" option for Data Protection Manager when "Select a tag" is set to "Microsoft System Center"? This is the reason I post under "Operations Manager".
Since we use DPM 2025 (on Windows Server 2025), every few days we see transaction log backups for Exchange 2019 and SQL Server 2017 databases stuck for hours instead of being finished within seconds or one minute at most. This was never the case with DPM 2019 and DPM 2022.
Is there any knowledge or workaround for this issue? Time for a Update Rollup for DPM 2025?
Best Regards,
Stefan Falk
Microsoft System Center | Other
2 answers
Sort by: Most helpful
-
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(316.8, 21%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EM%3C/text%3E%3C/svg%3E)
Michael 86 Reputation points2025-11-27T02:29:58.1133333+00:00 I have same problem that and did not have it in earlier versions. It looks like problems in ReFS with Windows Server 2025 are part of the blame, but not completely. I went back to Server 2022 with DPM 2025. While not perfect, it is much better than running on Server 2025. It is still not as good as DPM 2022 on Server 2022 (which took less than a minute as well). With Windows Server 2025, CPU use would go to 100% a couple of days after rebooting rending the system useless. It required a reboot to return to normal CPU use.
I know that I lost everything when I went back to Server 2022, but I was missing so many recovery points anyway.