Skip to main content
  • EN

case: 07735344

keyword:  Server 2025,  24h2,  upgrade ReFS

A few days after upgrading to Server 2025 (in-place upgrade ...yeah yeah...i know but options were limited), the CPU started to peg on the VM which would also max out the CPU of the host.  The VM would be unreachable/unusable until after a cold restart.
 

Ultimately, it looks like ReFS version was slowly being upgraded on our SAN due to the upgrade and it was incompatible with Veeam.  If I kept all veeam services off...no issues.  Once the services were on (even with all jobs disabled), the CPU would once again peg and the VM would hang.

After weeks of troubleshooting, I had to cut my losses and reformat/reinstall using server 2022....blowing away all backups.  Importing saved backup config did bring the Veeam server back with all settings and I was able to slowly bring all my backups online (I had to do it slowly because we have backup copy jobs going over a wan which took days.

 

CMadison

I would suggest keeping with the support case here as I have seen the post on the Forums too.  I have seen issues with Win2025 myself and in my lab stayed on Win2022 for everything until things are worked out with Win2025.

Agreed with Chris here. I haven’t even begun “playing” around in 2025 yet 🤷🏻‍♂️😂

It’s a known issue, it’s been almost 8 months with no fix: 

https://forums.veeam.com/veeam-backup-replication-f2/server-20225-high-cpu-and-ram-t96912-150.html

Hi ​@cmadison few words from my side this issue appears to be related to ReFS version changes that occur after upgrading to Server 2025. Veeam services trigger high CPU usage due to incompatibility with the updated ReFS.

 

I recommend staying on Server 2022 until full support is confirmed. Reinstalling with Server 2022 and importing the backup configuration helped restore stability in similar cases. 

Comment


Terms & Conditions