I would like to share my experience here with Server 2025, maybe someone else can benefit.
I setup a physical HPE server with Server 2025;
4*370TB ReFS repos (2 repos per 800TB RAID 60)
512GB RAM
2*24Core (48 thread) CPUs, for a total of 96 Thread
Initially it was running OK for about 3 weeks... then it started locking up randomly, iLO showed the CPU at 100% and the only way to recovery was to hard reset the server from iLO.
The firmware is latest as of May 2025, with the BIOS on n-1 because the latest BIOS won't install...
At the time it was running Crowdstrike, with all the recommended AV exclusions.
When reviewing the many event logs before the unresponsive issue, I thought it could be related to defrag, so I disabled defrag on all disks, only to find that Server 2025 still defrags the disks even when they are set to not run defrag, so I just disabled the degfrag service.
Well this didn't resolve the issue, but, after uninstalling Crowdstrike, the problem was resolved.
After a couple weeks of stable operation, with no AV installed, I installed Microsoft Defender for Business on the server, and implemented all recommended AV exclusions, so far, its been 4 days, and the locking up issue has not returned.
We don't run any custom reg keys on the server other than S3GovernanceImmutabilityMode.
So maybe it is just AV is the problem?
Also, when I followed the AV exclusions list; https://www.veeam.com/kb1999
I used *:\repo location for the extension exclusions, because I have 4 repos.
For Veeam guys - the Postgres AV exclusion document linked from above, https://wiki.postgresql.org/wiki/Runnin ... s_software
It says to exclude the data dirs and postgresql.exe, however, Veeam's installation of Postgres doesn't have postgresql.exe, it runs from postgres.exe as far as I can tell, can anyone comment on what's going on with that, and what the recommended exclusions for Postgres are, in a default bundled Postgres installation?
I setup a physical HPE server with Server 2025;
4*370TB ReFS repos (2 repos per 800TB RAID 60)
512GB RAM
2*24Core (48 thread) CPUs, for a total of 96 Thread
Initially it was running OK for about 3 weeks... then it started locking up randomly, iLO showed the CPU at 100% and the only way to recovery was to hard reset the server from iLO.
The firmware is latest as of May 2025, with the BIOS on n-1 because the latest BIOS won't install...
At the time it was running Crowdstrike, with all the recommended AV exclusions.
When reviewing the many event logs before the unresponsive issue, I thought it could be related to defrag, so I disabled defrag on all disks, only to find that Server 2025 still defrags the disks even when they are set to not run defrag, so I just disabled the degfrag service.
Well this didn't resolve the issue, but, after uninstalling Crowdstrike, the problem was resolved.
After a couple weeks of stable operation, with no AV installed, I installed Microsoft Defender for Business on the server, and implemented all recommended AV exclusions, so far, its been 4 days, and the locking up issue has not returned.
We don't run any custom reg keys on the server other than S3GovernanceImmutabilityMode.
So maybe it is just AV is the problem?
Also, when I followed the AV exclusions list; https://www.veeam.com/kb1999
I used *:\repo location for the extension exclusions, because I have 4 repos.
For Veeam guys - the Postgres AV exclusion document linked from above, https://wiki.postgresql.org/wiki/Runnin ... s_software
It says to exclude the data dirs and postgresql.exe, however, Veeam's installation of Postgres doesn't have postgresql.exe, it runs from postgres.exe as far as I can tell, can anyone comment on what's going on with that, and what the recommended exclusions for Postgres are, in a default bundled Postgres installation?
Code:
Microsoft Windows [Version 10.0.26100.4061](c) Microsoft Corporation. All rights reserved.C:\Windows\System32>where /r C:\ postgresql.exeINFO: Could not find files for the given pattern(s).C:\Windows\System32>where /r C:\ postgres.exeC:\Program Files\PostgreSQL\15\bin\postgres.exeStatistics: Posted by william.scholes — Jun 09, 2025 4:08 am
