Mirasys VMS System Requirements up to version 8.3

Sök i kunskapsbas

Mirasys VMS System Requirements up to version 8.3

You are here:
< Back

The server and client software can be installed on any standard PC platform that fulfills the hardware and operating system (OS) requirements. Servers may also be virtualized using, e.g., Microsoft Hyper-V or VMWare ESX. (VMWare has compatibility limitations with VCA functionality, workaround existing).

In a basic configuration, one hard disk may be enough, but for secure multi-disk recording (modified RAID 0), at least two disk units are required (see the Mirasys VMS Network Storage Guide for further information). A separate partition or disk for the operating system (preferably with rapid data transfer rate – e.g. SSD) and application software is also recommended.

Use of 24/7 optimized HDDs is highly recommended.

NOTE: The VMS software reserves by default majority of available disk space on all other drives than the C-drive for storage use (as default 10GB left unused). It does not use the C-drive for storage, except when it is the only drive.

Display adapter with at least 2 GB memory (a dual-head display adapter is optional). Please note that display adapter performance can vary greatly depending on the adapter and the bus architecture used to connect the adapter to the motherboard.

Two 1 Gbps network adapters. (Separate network segments with dedicated NICs for camera and viewing networks are recommended. See the Mirasys VMS Networking White Paper for further information).

Server Profile Details


  • Intel core i3 or better
  • 8 GB RAM
  • Min 100 GB OS and VMS application (7200 rpm or SSD)
  • 2 TB HDD (7200 rpm)
  • Windows 10 (64 bit)
  • Integrated display adapter (full HD, min 2 GB, dual-head display optional)
  • 1 Gbps network adapter with receive and transfer buffers of min 2048 bytes (Intel recommended). Separate network connections for camera- and system network recommended.

Optional: Optional: GPU to increase the performance:

  • NVIDIA Quadro P1000
  • NVIDIA Quadro P4000

Software architecture built to be compatible with NVIDIA Maxwell (h.264) and Pascal/Tesla (with H.265 chip).

Mirasys VMS V8.x (until V8.3.x) supports the following operating systems (64bit only):


These network requirements apply to systems where users access the servers over a network.

Please see the Mirasys Networking White Paper and the Mirasys Network Storage White Paper for information on networking recommendations, limitations and rules.

1 Gbps network adapter with receive and transfer buffers of min 2048 bytes (Intel recommended).

Separate network connections for camera- and system network recommended.


A 1 Gbps Ethernet is required on both the client and the server side (see Bandwidth Requirements). Data can be transmitted over the Internet, intranet, LAN, WAN, WLAN or any other network using TCP/IP.

For best performance, the camera network should be closed from other network traffic and kept separate from the system network used for server-server or server-client communication. In case TruCast is used, connection between the camera and the Spotter is also additionally required.

It is heavily recommended to have at least two 1 Gbps network adapters for each server: in minimum one adapter for the camera feeds and one adapter for server-client and server-server communications.

In the case of large systems with multiple high resolution and high frame rate cameras, separating specific camera sets into their own networks (and adding network adapters to servers) can be recommended. However, this done case-by-case, and requires case specific calculations on network load.

PTZ (Pan-Tilt-Zoom) control requires a low latency in the network to make dome control as responsive as possible.


The servers must have static IP addresses, so that the client programs can connect to them. The Agile Virtual Matrix (AVM) Display Servers should also have either static addresses or names, as the connection from AVM operator console to the display servers is done either with IP address or computer name.

You can use some NAT solutions with the system but not all:

  • Static network address translation (NAT) can be used between the servers and the client programs.
  • Dynamic NAT cannot be used because the IP addresses can change.
  • Single-address NAT works if there is only one server in the NAT system. It does not work if there is more than one server in the same system.


In minimum the following ports must be open on the servers (please refer to the VMS networking white paper for further information):

  • 5008 (TCP), between SMServer (System Manager service) and client programs. Port rule: open inbound
  • 5009 (TCP), between DVR Server and client programs. Port rule: open inbound
  • 5010 (TCP), between Watchdog Service and client programs. Port rule: open inbound
  • 5011 (TCP), between Streaming Service and client programs. Port rule: open inbound

NOTE: If you are using Windows Firewall, the VMS installer can automatically create exceptions for the required ports.

NOTE: automatic port forwarding can configure the ports to be different than these default ones.


The bandwidth requirements for the network between the servers and client programs depend on a number of factors. Here are a few related aspects:

Data transmission from the servers to the client computers (uplink, video streaming (UDP)) requires more bandwidth than data transmission from the client computers to the server (downlink, signaling (TCP)). The connection does not have to be symmetric.

In addition, signaling and protocols increase the required bandwidth.


Using public networks generates always a security risk. Therefore, a dedicated network is recommended. Consider using a Virtual Private Network (VPN) to create a secure connection between computers over a public network.

Antivirus programs should also be used if the system units are on a public network (internet, intranet).