We only reboot the OS for hardware/software maintenance as required by the action being performed (many of our hardware maintenance items are hot-swap).
Our Linux server which hosts our Cloverleaf hasn’t been rebooted for 322 days, on only then because we added enough interfaces that we finally need to adjust the shared memory parameters!
We schedule quarterly reboots to exercise our Business Continuity procedure: we maintain two side by side production servers in our data center and perform a manual failover (takes about 30 minutes). Also: at one time in Cloverleaf history, then Quovadx support recommended at least a quarterly reboot to clean up memory – sorta like taking a bath at least every 3 months. If messages drain we do a complete scrub of all of our sites too (we are multi-site). The justification back then (from support) was that the engine starts to do “weird” things
if they are not cycled and memory cleared.
This has served us well as our engines continue running fine.
We reboot Cloverleaf once a month. It coincides with a regularily scheduled downtime for a software load on our HIS, so users don’t know any different.
Running AIX 5.2 Platform V 5.3P_Rev2. We only reboot for hardware maintenace. Our production server’s uptime is 185 days. I cycle the production hostserver and monitor daemons monthly.
Same here. AIX 5.3 up for 209 days. Let’s here it for Unix!!! If you windows server is up past 6 weeks, then you are not loading your security patches. We call it Microsoft Tuesday..
Author
Replies
Viewing 18 reply threads
The forum ‘Cloverleaf’ is closed to new topics and replies.