Exploring XProtect VMS: System Architecture – Part I
In this video tutorial, you will explore
the system architecture of an XProtect Video Management Software (VMS) installation. There are two types of XProtect VMS installations. Depending on the XProtect VMS product you’ve selected and your specific solution requirements, you can perform either a single-server installation or a distributed installation. Let’s look at each of these. In a single-server installation, you install all XProtect VMS system components on the same machine. Milestone recommends this for smaller systems with fewer than 50-100 cameras, depending on the hardware configuration. Single-server installations generally offer reduced hardware costs at the expense of overall performance or storage capacity. A distributed installation allows you to spread XProtect VMS system components across multiple servers. Milestone recommends this type of installation for larger systems with more than 50-100 cameras. With the distributed installation, you typically have a dedicated server for each system component. When each server performs only one function, it’s much easier to balance the overall system performance. You can, however, install several components on the same server. Now that you’re familiar with both types
of XProtect VMS installations, let’s look at a system architecture diagram and explore its system components in more detail. Management Server The Management Server is the principal component of the XProtect VMS. It stores the configuration of the surveillance system in a relational database, either on the management server computer itself or on a separate SQL server on the network. It also handles user authentication, user rights, the rule system, and more. To improve system performance, you can run several management servers in a Milestone Federated Architecture. The Management Server runs as a service and you typically install it on a dedicated
server. Users connect to the Management Server for initial authentication and then it grants access to other components, like recording servers, to retrieve live and recorded video. Event Server The Event Server handles various tasks related to events, alarms, maps, and third-party integrations via the Milestone Integration Platform Software Development Kit (MIP SDK). It houses all system events so there’s a single location for partners to install integrations that need access to system events. Furthermore, the Event Server allows third-party applications to send events to the system via the Generic events or Analytics events interface. The Event Server hosts alarm profiles, alarm logic, and alarm-states, in addition to handling the alarm database. The alarm database uses the same SQL server that the management server uses. The Event Server also hosts the map configurations used in the XProtect Smart Client. Log Server The Log Server records log entries for the entire system. It uses the same SQL server as the
management server and you typically install it on the same server as the management server. If you have specific needs for log performance, you can also install the Log Server on a separate server. An XProtect VMS can generate three types of logs. System Logs You can use the system log to see if a device goes offline unexpectedly. Audit Logs System administrators can use audit logs to document user activity in Milestone clients to complement their login and administration logs. If you need to see user activity for a specific time, you can look up this information in an audit log. Rule-triggered Logs This log records specific events and the rules triggered by those events. If you want to log an event, make sure you have a rule that creates a log entry when the event occurs. Service Channel The Service Channel communicates service and configuration messages to the Smart Client, the mobile server, and third-party components listening to the Service Channel. For example, the Service Channel would communicate updates to a Smart Wall monitor layout or communicate that a failover server is now active.