@jokoenen
Thanks, had nothing to delete yet and as I'm running on Reverse-Incremental right now, that's helpful to have in mind!
So I "just" finished the 69 TB-Job (Full, 40 hours) and one Reverse-Incremental step on Top (Server 24H2 Build 6584 as well) without any problems. System peaked at 24 GB of RAM, went back to 14 GB once done. Guess I can downsize it back again from its current 64 GB. Reporting CPU-Load during operation is pointless for me, as it is where it is supposed to be at Max-Compression (28 Threads Xeon Gold 6132) as I'm somewhat Storage-Performance-Limited anyway (300 MB/s Limit on the ReFS-Repo, but that's going constantly). System did not crash, that's a good start. As an Increment is done within three hours, I'm scheduling that thing for the upcoming week and monitor how it goes.
Seems like KB5065426 did something. Time will tell. Hopefully Microsoft will improve things before someone needs to delete something.![:)]( "Smile")
Thanks, had nothing to delete yet and as I'm running on Reverse-Incremental right now, that's helpful to have in mind!
So I "just" finished the 69 TB-Job (Full, 40 hours) and one Reverse-Incremental step on Top (Server 24H2 Build 6584 as well) without any problems. System peaked at 24 GB of RAM, went back to 14 GB once done. Guess I can downsize it back again from its current 64 GB. Reporting CPU-Load during operation is pointless for me, as it is where it is supposed to be at Max-Compression (28 Threads Xeon Gold 6132) as I'm somewhat Storage-Performance-Limited anyway (300 MB/s Limit on the ReFS-Repo, but that's going constantly). System did not crash, that's a good start. As an Increment is done within three hours, I'm scheduling that thing for the upcoming week and monitor how it goes.
Seems like KB5065426 did something. Time will tell. Hopefully Microsoft will improve things before someone needs to delete something.
Statistics: Posted by ChristophINV — Sep 20, 2025 9:18 pm
