>>just wait at least 1 year. after that you can evaluate a upgrade. no rocket science
Look sonny, I have probably had more breakfasts than you by a long way![:twisted:]( "Twisted Evil")
don't talk to me about waiting a year, I may not have that long! ![:D]( "Very Happy")
as for rocket science - yeh, but that sort of falls into the shoulda woulda coulda bucket and we are, as they say, where we are.
Anyhow
Server was restarted using the windows GUI at 1520 yesterday with memory use at around 45Gb and climbing gently. It had not restarted by end of shift (15:30) and nor had it restarted by the scheduled backup start times. It had restarted by 2200 when a Surebackup job was scheduled start; that job promptly got upset becasue things weren't as it expected.
I checked the machine this morning and memory use is constant at around 90Gb "used" and 5 Gb "free" - quoted because those concepts are a bit vague when it comes to memory management in Windows. The machine is, at least, usable and will happily retry backup jobs. Yes there are issues (not being able to publish malware/indexes to the catalog - known feature) but it works after a fashion.
Memory demand doesn't appear to change significantly during backup operations so, for my use case, there is a finite amount of memory required to run Veeam with Server 2025 and ReFS file systems presented, to the server, using iSCSI.
I will leave it be until it runs the scheduled tasks over the weekend.
Look sonny, I have probably had more breakfasts than you by a long way
don't talk to me about waiting a year, I may not have that long! 
as for rocket science - yeh, but that sort of falls into the shoulda woulda coulda bucket and we are, as they say, where we are.
Anyhow
Server was restarted using the windows GUI at 1520 yesterday with memory use at around 45Gb and climbing gently. It had not restarted by end of shift (15:30) and nor had it restarted by the scheduled backup start times. It had restarted by 2200 when a Surebackup job was scheduled start; that job promptly got upset becasue things weren't as it expected.
I checked the machine this morning and memory use is constant at around 90Gb "used" and 5 Gb "free" - quoted because those concepts are a bit vague when it comes to memory management in Windows. The machine is, at least, usable and will happily retry backup jobs. Yes there are issues (not being able to publish malware/indexes to the catalog - known feature) but it works after a fashion.
Memory demand doesn't appear to change significantly during backup operations so, for my use case, there is a finite amount of memory required to run Veeam with Server 2025 and ReFS file systems presented, to the server, using iSCSI.
I will leave it be until it runs the scheduled tasks over the weekend.
Statistics: Posted by BenM2024 — May 09, 2025 7:53 am
