46,316 questions
Anyone having horrible performance in DPM 2025?
![](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
76
Reputation points
Anyone else experiencing horrible performance with DPM 2025? After upgrading from the latest update rollup of DPM 2022, we have been experiencing major issues that after about a week of operation make the system unusable and requiring reboot. After reboot, the system can catch up, but then in about a week the problem is back. This is causing many recovery points to be missed. CPU use is normally pegged near 100% at this time. Increasing the number of cores beyond the recommended number of 4 does not help. Many jobs are in the queue for things such as small SQL databases that in the past would complete in less than a minute but are now running for several days. I'm running on same hardware as with DPM 2022. Backup load is essentially the same as well. Only other difference is SQL 2022 is being used instead of SQL 2019 as well as running on Windows Server 2025 instead of 2022.
Community Center | Not monitored
{count} vote
-
Michael 76 Reputation points
2025-03-26T19:38:08.8966667+00:00 I'm also seeing many error id ID 52 and 65 for the data sources indicating some sort of communication error. I NEVER received those in DPM 2022, and there are no problems with the networking infrastructure (that has been checked many times). These errors for a specific data source are usually cleared the next synchronization time, but they are frequently logged for another data source at that time. These errors are not specific to any host as they change from host to host. I don't know if there is a relationship here or not.
Sign in to comment
Sign in to answer