/
Munis Server Reboot Recommendation
Munis Server Reboot Recommendation
Description of Issue
How often should we reboot our Munis Servers and in what order should it be done?
Context
Munis
Server
Reboot
Cause
Client is looking for recommendations on the Munis Server reboot policy
Resolution
It is recommended that all Munis Servers for On Premise Clients are rebooted every 30 days. The order that they should be rebooted in is as follows:
Database Server(s)
If SQL Always On is configured, reboot the secondary server first followed by the primary.
Application Server(s)
Infrastructure Server(s)
Web Server(s)
TCM Server(s)
Other(s)
Additional Information
, multiple selections available,
Related content
Restart Munis Scheduler for SaaS
Restart Munis Scheduler for SaaS
More like this
Schedule Munis support to go through a year end close
Schedule Munis support to go through a year end close
More like this
Update The Refresh Scripts On New Servers So The MDF Files Are Placed On the Correct Drives
Update The Refresh Scripts On New Servers So The MDF Files Are Placed On the Correct Drives
More like this
How often should I update my Tyler software applications
How often should I update my Tyler software applications
More like this
Upgrade Checklist - Tyler Software Update Best Practices
Upgrade Checklist - Tyler Software Update Best Practices
More like this
Cloud Admin Refresh Backups Long Term Storage Location
Cloud Admin Refresh Backups Long Term Storage Location
More like this