Network Management
Orion server reboot - Best practices
This article explains how to reboot the Orion Environment, whether for troubleshooting or system updates such as Windows Updates, GPO updates or other software installations requiring a reboot.
First published date
Last published date
Overview
Product section
Cause
Resolution
Orion Server reboot sequence
- Start with disabling HA services; see the articles:
- SQL Database Server (if you’re planning to restart). Make sure that the SQL database server starts first so that the polling engines can connect to it when they reboot
- Note: Orion Platform 2022.3 will have the Orion Database for Log Analyzer and NTA's Netflow database regardless of licenses; these can be on separate SQL servers or the same SQL server running the Orion Database.
- Primary polling engine (make sure that this is restarted before any of the secondary servers because the secondary polling engines connect to it for license validation)
- Additional Polling Engines and Additional Web Servers
Open the Orion Web Console and go to Settings > My Deployment to view Deployment Health and Servers (High Availability Deployment Summary).
Procedure after the reboot
Nothing – all Orion services will be started automatically. However, some of the services depend on the Net.TCP Port Sharing Service, so if this service is not running, the dependent services will not start.
Can server restart be set as an overnight scheduled job?
Yes, but make sure that it does not overlap with the database maintenance (by default – 2:15 AM). The default time can be changed in the 'Archive Time' field, which is available in Orion Web console > Settings > Polling Settings > scroll down to the 'Database Settings' section (Sample screen is given below):