pagefile size on Windows Server with dynamic RAM?
-
@DustinB3403 No - There are a couple reasons. The main reason is that the two servers don't get patched at the same time and the app they are running doesn't get updated at the same time. This is so that if an update breaks the server, I can just put the other one in service. I suppose I could set up a connection broker and have all the request go to one or the other, but then that's another server to troubleshoot if something isn't working.
-
The bottom line is that it's the software vendors patches and updates that are my biggest concern. Having a second server that is a version behind and ready to go is cheap protection against that.
-
@Mike-Davis said in pagefile size on Windows Server with dynamic RAM?:
The bottom line is that it's the software vendors patches and updates that are my biggest concern. Having a second server that is a version behind and ready to go is cheap protection against that.
As @scottalanmiller would say the cheaper approach might be to find a new vendor / solution..
-
So if these systems are on different patch cycles, and a patch breaks your primary RDS hosted application. I assume you use the backup as a fall in, and then perform a restore to the primary, or uninstall the patch to address the issue.
My question is there a way you can setup snap shotting at patch night, and if the patch breaks the system then you just restore the snap?
-
@DustinB3403 Yes we can (and do) snap and we can restore snaps. The last time the server got hosed, we did just that. I think it 20 minutes total and the owner was impressed, but then the vendor needed to figure out how to move forward. That's when we built a second server for him to test his new version on.
-
Seems like the fix should be on the Zabbix side.
-
@Mike-Davis said in pagefile size on Windows Server with dynamic RAM?:
Is there a best practice as it relates to the page file setting on a Windows Server with dynamic RAM? I have it set to system managed, and it's working ok, except the Zabbix reports "Lack of free swap space on <servername>" I could just turn that trigger off for the servers with dynamic RAM, but I wondered what others were doing.
I had to disable that trigger for me as well.
-
@dafyre Only on servers with dynamic RAM? Those are the only servers I'm having that issue with, and setting the page file size manually didn't fix it they way I thought it would.
-
@Mike-Davis said in pagefile size on Windows Server with dynamic RAM?:
@dafyre Only on servers with dynamic RAM? Those are the only servers I'm having that issue with, and setting the page file size manually didn't fix it they way I thought it would.
I would not do that. This is a Zabbix setting problem not a Windows one.
-
@Mike-Davis said in pagefile size on Windows Server with dynamic RAM?:
@dafyre Only on servers with dynamic RAM? Those are the only servers I'm having that issue with, and setting the page file size manually didn't fix it they way I thought it would.
If you didn't also change the PF size, I'm not surprised that it didn't fix the Zabbix issue.
-
@Dashrender said in pagefile size on Windows Server with dynamic RAM?:
@Mike-Davis said in pagefile size on Windows Server with dynamic RAM?:
@dafyre Only on servers with dynamic RAM? Those are the only servers I'm having that issue with, and setting the page file size manually didn't fix it they way I thought it would.
If you didn't also change the PF size, I'm not surprised that it didn't fix the Zabbix issue.
No, it have issues with all of my servers with that trigger. It's definitely a zabbix issue, as far as I'm concerned.
I haven't had time to research it.
