Onsite Manager Architecture - On Premise

Last updated on 2022-09-13 15:43:51

Onsite Manager uses Microsoft SQL Server 2019 Express or Microsoft SQL Server 2017 Express and Windows Services. It is capable of handling up to 1000 devices, in healthy environments with basic monitoring requirements. As such the database engine and the application reside on the same physical server. Dedicating a server to Onsite Manager is recommended for larger networks and when more thorough or frequent monitoring is required. For an average SMB client, you can typically install Onsite Manager onto a shared server.

When installing onto a shared server, you must ensure that the resources specified as the system requirements are available during the client’s production hours. (For information about the Onsite Manager system requirements, see Onsite Manager.) Otherwise you are introducing contention for the server’s resources, which can cause both Onsite Manager and its other roles to be performed less than optimally.

Best Practices

When deploying a single Onsite Manager to monitor more than 500 devices, start with a basic monitoring service policy set, and layer in other monitoring, automated tasks, and patch management activity one configuration at a time, keeping track of any changes to the performance of the server at each stage (CPU, RAM, and disk activity).
When there is another option available, you should avoid installing Onsite Manager on Domain Controllers or other mission-critical servers. Web or file servers are favorable when available.

Database Component

The Onsite Manager uses Microsoft SQL Server 2019 Express or Microsoft SQL Server 2017, included in the installation package, to house the Barracuda RMM database:

MWData Stores the monitoring rules that have been defined in Service Center, which direct the activities of the Onsite Manager application. It also contains the information about IP addresses and their associated devices.

During periods where Internet connectivity is interrupted, monitoring data is queued in the database to be sent to Service Center once the connection has been restored.

Best Practice

Install Microsoft SQL Management Studio when you install Onsite Manager so that you have a tool to back up your database, and are ready to receive technical support should it be required.

Application

The Onsite Manager application makes use of three Windows services:

MWExpertSystem Handles all the querying of managed devices for data, and also listens for data being sent to it, such as SNMP traps or Syslog messages. To function correctly, it must run with Administrator privileges to ensure it can gather all the information you are requesting from the devices.

MWExpertSystemHelper Uses Microsoft Background Intelligent Transfer Service (BITS) to download large automated task files from Service Center.

OMNetworkService Controls all the remote sessions users launch.