Password: 32dvr *
*) Password in Windows Server OS –systems is: 32dvrDVMS
System Manager, Spotter, and System Monitor
The default username and password should not be used even in closed networks. Please ensure that the default username and password are not in use after the system has been installed.
Mirasys VMS software is a distributed Video Management System for video and audio surveillance applications.
The software can be used for monitoring real-time and recorded video, audio and text data, and to control dome cameras, I/O devices and IP cameras.
The software supports systems consisting of both analog and/or digital surveillance cameras, supporting the creation of analog (DVR), digital (NVR) or hybrid (consisting of both analog and digital) surveillance systems.
This guide gives instructions for setting up the VMS Servers and for installing audio devices, IP cameras, dome cameras, video matrices, digital inputs and outputs, and client programs (Spotter and System Manager).
This help documentation, for example, is available:
The PDF help documentation is on the VMS installation medium and the full setup package that can be downloaded from the Mirasys Extranet.
You can also access the Administrator’s Guide and the Spotter User’s Guide by clicking Help in the System Manager or Spotter programs.
When installing third party devices, follow the manufacturer’s instructions.
For technical support and warranty issues, please contact the system supplier.
The lists below include only select information. For a full list of new features and changes, please refer to the Release Notes included in the installation packages.
Note: Microsoft SQL Server Express 2014 or the full Microsoft SQL Server 2014 is required to be installed on the Master Server (in single server installations the only server is the Master Server) and on networked recording VMS servers (nodes or slaves) when Mirasys VCA (Video Content Analytics) is to be utilized.
New features in version 8:
Mirasys software is a distributed, digital video management system (VMS or DVMS) for video and audio surveillance applications.
The software can be used for monitoring real-time and recorded video, audio and text data, and to control PTZ cameras, I/O devices and IP cameras.
The software supports systems consisting of both analog and/or digital surveillance cameras, supporting the creation of analog, digital or hybrid (consisting of both analog and digital) surveillance systems.
A centralized surveillance system domain can consist of a network of up to 150 local or remote VMS Servers.
Mirasys software is sold both separately and as part of Mirasys video management systems consisting of both the software and the VMS Server hardware. Please contact your Mirasys supplier for information on Mirasys software or hardware.
What Does a System Contain?
The Mirasys system consists of these components:
The VMS servers record video and audio from multiple cameras and audio channels and write the data on hard disks. You can access a VMS Server locally or over a network by using the System Manager and Spotter programs, and monitor server functionality through the Spotter Diagnostics plugin.
A server contains the computer with storage, the Windows operating system, and the VMS software with required drivers.
In addition, you can connect these devices to a VMS Server:
In a networked system, one of the servers must be set as the Master Server. A Master Server is the central server of a surveillance system. All other VMS Servers connect to it, and all client applications communicate through the Master Server.
If the system contains only one server, then that server is the Master Server. If there is more than one server, the Master Server can be set freely. In a larger system it is recommended that the Master Server is a dedicated server for this purpose alone.
Note: Master Servers must have SQL Server Express 2014 or another Microsoft SQL Server 2014 installed.
The Master Server does these things:
System administrators use the System Manager program for these tasks:
End users use the Spotter program, for example, for these tasks:
The Workstation client is the legacy client that is no longer supported. If you must use Workstation you need to use Mirasys VMS V7.5.10, or earlier.
Starting from Version 8 onwards, the Mirasys VMS software is available only as a 64-bit (“x64”) version.
Note: Mixed 32-bit and 64-bit systems need more care and expertise for the installation, upgrading and management of the system.
Analog video compression (capture) cards are not supported on the 64-bit Mirasys VMS.
Managing an Environment With 64-bit Versions of Mirasys VMS
Version 8 supports clients to connect to 32bit and 64 bit server versions. It is recommended to reinstall the clients with version 8 installer to get the latest application updater (VAU).
Server upgrading considerations
When using the System Manager application's “Update servers” -feature to update the VMS Servers in the system, all or the selected VMS Servers you choose to update will update to the version you choose (which installation file you provide).
In a mixed environment with both 32-bit and 64-bit servers, be careful that you know which servers are to be upgraded to which version, 32-bit or 64-bit!
The 64-bit versions will not work at all on, so called, hybrid servers with internal analog video capture cards (also known as compression cards or grabber cards).
System manager shows the 32 bit or 64 bit version information in the “Version” table.
All new IP camera, encoder (video server) or other drivers are also available as separate 32-bit and 64-bit versions. When installing a new driver or updating an existing driver, you must use a 32-bit driver package on a 32-bit server, and a 64-bit driver package on a 64-bit server.
Note: Also that all servers with the Master Server role, as well as all VMS Servers with Mirasys VCA (Video Content Analytics) require Microsoft SQL Server Express 2014 to be installed on the server before installing Mirasys VMS.
The Mirasys VMS (Video Management System) software is flexible and scalable network video recording software that consists of Mirasys server software and client application software. 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.
Mirasys VMS is delivered either in pre-assembled servers, or as software-only, in which case the distributor/reseller, an integrator/installer or the end-customer installs the software on a PC.
The performance of a Mirasys VMS solution depends on several factors such as processor type and speed, available memory, and network bandwidth. The requirements below define minimum requirements for running Mirasys VMS software with IP surveillance cameras.
The examples presented in this document should only be used as a base guideline when planning to set up a system. For detailed calculation of system performance and storage capacity requirements, please refer to your Mirasys sales contact or an authorized distributor/reseller.
Please note also that the performance and functionality of a VMS system’s server or client software is guaranteed only when it runs as the sole application on the PC platform. No other software applications – with the exception of dedicated server software such as Mirasys ANPR+ (Automatic Number Plate Recognition), Mirasys Reporting+, Mirasys VCA (Video Content Analytics), or Microsoft SQL Server when required – should be installed on the computer on which the Mirasys VMS server or client applications are executed. It is also recommended that server and client software should be used on separate computers.
The servers require this minimum (small) system configuration:
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 disk for the operating system and application software is also recommended.
Use of 24/7 optimized HDDs is highly recommended.
Note: The VMS software reserves by default 90% of available disk space on other drives than the C-drive for storage use. It does not use the C-drive for storage, except when it is the only drive.
Display adapter with at least 128 MB 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 (separate network connections for the camera network and the system network, see the Mirasys VMS Networking White Paper for further information).
These are the minimum requirements for Mirasys VMS client applications (such as Spotter for Windows or the System Manager).
The following hardware specification should be viewed only as the minimum requirements for a smallscale surveillance system.
Mirasys VMS V8 supports the following operating systems:
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.
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, ISDN, ADSL, or any other network using TCP/IP.
For best performance, the camera network should be closed to other network traffic and kept separate from the system network used for server-server or server-client communication.
It is heavily recommended to have at least two 1 Gbps network adapters for each server: at least 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.
Network Card Settings
Network card setting requirements:
If the network card cannot be adjusted to these settings, replace the card.
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:
These ports must be open on the servers:
The bandwidth requirements for the network between the servers and client programs depend on a number of factors. Here are a few aspects to think about:
The system uses a data protection mechanism and user authentication. However, using public networks always includes a security risk because there are no completely secure systems available on the Internet.
For this reason, dedicated networks should be used whenever possible to prevent unauthorized access to the system. Consider using a Virtual Private Network (VPN) to create a secure connection between computers on a public network.
Antivirus programs should also be used if the system units are on a public network (internet, intranet).
This chapter shows how to install the Mirasys VMS software on a computer that has not already a previous version installed.
To set up the server:
To update recording software and client applications:
Please see the chapter Updating for information on updating server or client software.
Mirasys VMS supports failover video recording servers. Failover servers are VMS Servers that are on a passive standby until the system recognizes that one of the active video recording VMS Servers has broken down; at this point a failover server takes the place of the broken server. The broken server can be repaired and replaced as a new failover server, while the failover server that took its place can continue operating as an active server.
For details, see the Mirasys MS Administrator Guide.
During server software installation, the installer designates the material disks used to store the recorded data. Effectually, the server installer scans the locally available HDDs and grabs any sufficiently large drive automatically for material storage purposes. The operating system disk is omitted.
If the automatic storage configuration does not detect a disk, the storage drives can be added later using system manager.
If the automatic storage configuration is grabbing disks that are not intended for material storage, the automatic logic can be disabled from installer.
The HDD’s don’t need to be same size like in earlier Mirasys VMS releases.
After designating the material disks, the installer appropriates all except 10 GB of it for data storage.
It is highly recommended not to use USB HDDs in the server, as they will be used as data storage disks in addition to other HDDs. If, however, you need to have USB HDDs connected to the server, it is highly suggested that you disconnect them before installing Mirasys VMS server software. You can attach them after installing the software, and they will not be used as material disks unless specifically designated through System Manager. (The same applies to other HDDs added after server installation.)
If you do not disconnect the USB HDDs before software installation, the server software will automatically use them to store server media files.
To install the server software:
If you do not want to install the applications on the server, open the menu next to Applications and select Entire feature will be unavailable.
You can also define if Spotter or System Monitor should start automatically.
If you want firewall exceptions set automatically for Windows Firewall, open the menu next to Set firewall exceptions and select Will be installed on local hard drive. Do not select this option if you are not using Windows Firewall.
Select the destination folder and click Next.
Select the process startup setting. In master server where the SQL Server is installed, it is recommended to select the middle setting. In normal servers it is recommended to select the top setting.
If automatic port forwarding is needed, you can activate this in the next installer screen. For systems which don’t have external network access, the automatic port forwarding option can be disabled. This setting can be controlled later in system manager application.
In the Installation Configuration dialog box, specify the IP address or DNS name of the Master Server. The Master Server is the server where all system configuration data is stored when more than one server is used in the same system. (This dialog box is not shown if only the server is installed). If the Master Server is the local computer, use the default value 127.0.0.1. Then click Next.
Then click Install to start the installation.
When the server has been installed, the dialog box “Completed the VMS Setup Wizard” is shown.
For information about setting up the server, see Server Installation.
For information about how to install the client programs, see Installing Client Programs.
To set the TCP/IP addresses in Windows:
If the server will function as the Master Server of a system, and if it will be accessed over a network, you have to set the server’s IP address through the System Manager application.
To set the IP address through System Manager:
Note: You only need to set the local IP address for the Master Server of a system if the server can be accessed over a network. If the server is accessed locally, there is no need to set the address.
When more than one server is used in the same system, the Master Server keeps the clocks of all networked VMS Servers synchronized. Master will synchronize the clocks using the computer clock as the source.
For this reason, one server should not belong to more than one system. The Master Server synchronizes the clocks once a day. However, if the time difference between the clock on the Master Server and the clock on the other server is more than 29 minutes, the clocks are not synchronized.
For the time synchronization to work correctly, the Windows time synchronization must be disabled on the other servers. However, it can be enabled on the Master Server.
To disable Windows time synchronization:
By default, without a VMS license, the server supports only one IP camera. To get the full functionality, get a license key from Mirasys. For the license key, you need the MAC address of the server.
To get a license key:
After connecting the cameras and other devices to the servers, configure the system settings and add user accounts and user profiles.
To configure the system:
For more information about how to configure the system, see the Administrator Guide.
You can connect supported IP cameras and video servers to a server over a TCP/IP network. An IP camera has a built-in component for capturing video images. The camera is connected directly to a local area network, and it has its own IP address.
You can also use video servers (encoders) to change analog cameras into IP cameras. Video servers are also connected directly to the local area network, and they have their own IP addresses.
For a list of supported cameras, see the document Supported IP Cameras on that can be accessed from Mirasys Extranet.
Please see the Administrator Guide for instructions on installing IP cameras to the system.
Any DirectX joystick can be used, but you can contact your supplier for a list of devices that are proven to work best.
Connect the DirectX device to your computer and wait for the driver to be installed.
Calibrate the joystick in windows. Press “Start” and write “USB game” and then select the “Set up USB game controllers” option
Select the device from the list and click “properties”
Select “settings” and then “Calibrate” and follow instructions.
After this, start Spotter application and then configure the input device settings in spotter to get the joystick working. Please see the Spotter User Guide for further details.
You can use the client programs locally on the server or on a computer that has a network connection to the server system.
To install the client software:
Mirasys 8.x servers are compatible with Mirasys 8.x, 7.x and 6.x networked VMS Servers. The Master Server always needs to be same or higher version than the network node VMS Servers.
To update a server, first remove the current software version and then install the new software version.
Important: Backup system settings and server settings in System Manager before removing the current version and then restore the settings after the update is completed.
To remove the current server version:
The client programs are updated automatically to the same program version as the Master Server when they are started.
To manually update the client programs, first remove the current version and then install the new version by running the VMS installer.
To remove the current version:
Updating VMS Servers remotely through the Master Server has been possible since Mirasys VMS 6.2.5.
To update VMS Servers remotely, first update the Master Server to the latest version. In the System Manager, update the licenses for the individual VMS Servers through the 'Licenses' list in the 'System' tree. After updating the licenses, you can update the VMS Servers remotely by using the 'Update servers' tool in System Manager.
In addition to camera drivers and Spotter Plugins, it is possible to also update metadata drivers from System Manager.
Spotter Plugins are updated by removing the old version and adding a new version *.spi file to the system.
Metadata drivers offer the possibility to update the drivers to whole system or only selected servers.
Contact Mirasys for more information on available metadata drivers and updating them.
Mirasys VMS includes an automatic flash memory based backup and restore functionality (“ABUR”). This feature is only available on servers delivered by Mirasys Ltd.
The flash memory backup and restore functionality is intended for situations in which the operating system and hard disk have failed and the server hard disk needs to be re-formatted or replaced.
The automatic flash memory functionality can backup and restore the following:
The automatic flash memory functionality does not include the following:
The flash memory functionality automatically backs up the server configuration and license files at installation and after that each time there are changes in them. The server automatically handles all steps of the process, and there is no need for the users to do anything to enable the functionality.
In case of operating system being corrupted or hard disk failure, the system administrator may need to restore the system from the automatic backup files. The process is mostly automatized, but the user needs to perform some steps.
To use the flash memory, restore functionality:
Set the computer BIOS to boot from USB devices. Ensure that there are no other USB memory devices or other boot media connected.
Once the Windows loader starts, select either:
Format the hard disk – Use this option to format a hard disk that has already been in use. This option should be used when the operating system has been corrupted and the hard disk needs to be reformatted.
Blank installation – Use this option to restore the system to a blank hard disk. This option should be used when the hard disk has been changed and a blank one has been installed on the computer.
Once the Windows installer starts, select the appropriate country, time zone, and language options.
Once the VMS software loader starts, choose either:
Don’t install VMS – Choose this option if you do not want to install Mirasys VMS software.
Drivers are installed properly. Continue to install VMS – Choose this option if want to install Mirasys VMS software.
After the server software has been installed, the configuration files and license information is automatically restored.
When rebooting the computer, remember to go to the BIOS to disable booting from USB devices.
Mirasys WebClient is a browser-based application that is used for viewing video from Mirasys servers over a network. Mirasys WebClient uses the same user profiles, user names, and passwords as Mirasys System Manager and Spotter client programs.
To be able to use Mirasys WebClient, the Mirasys Gateway server must be first installed on a computer running a HTTP (web) server. Mirasys VMS recording software is not required on the server. The Gateway server needs to be able to connect to the Mirasys VMS Master Server.
Note: Please note also that the minimum system requirements are recommended for mostly live viewing. If multiple users access the same WebClient server simultaneously mainly for search and play back functions, a more powerful processor is required.
The Mirasys VMS Gateway server can be installed on any Microsoft Windows server that meets the system requirements. Mirasys VMS software is not required on the server.
The Gateway server has a default license controlled limitation of 32 simultaneous streams for all WebClient connections. The limit is universal and user independent; if, for example, User A has 30 open video streams and User B has 2 open video streams, neither can open any more streams unless one or more of the currently open streams are closed.
To install the Mirasys Gateway server:
To verify that the server has been correctly installed:
Open a compatible web browser and type the following address:
http://[WEBCLIENT SERVER URL]:[PORT]/
For example, if the WebClient server is on the same computer:
If the server is correctly installed, the logon screen is displayed. Type a user name and password in the corresponding boxes and click Log On. The user name and password are set in the Mirasys System Manager program.
The users can view the WebClient streams in JPEG format (default) or in the native format in which they are received by the servers. This does not require any action on the server side: the users can decide to view the streams in native format by adding ?video=native to the end of the WebClient URL.
For example, if the WebClient server is on the same computer:
Spotter plugins can be added to system from System Manager.
Spotter plugins are added to System Manager as *.spi files from the system manager first tab – Add-ins – install client plugin.
Each plugin needs to be enabled in the master license. If the plugin is not in the license, it can be installed, but will not be deployed to the Spotter clients of the system.
After plugin is installed to System Manager, each Spotter client that logs in to this Master Server (SMServer), gets the updated plugin next time the client is started.
Development of custom plugins is possible. Contact Mirasys for further information.
Mirasys provides configuration services for the VCA functionality; for further information, please contact Mirasys.
This section of the manual only covers installing basic VCA functionality. Please refer to the Mirasys VMS VCA Installation and Configuration Guide for more information on using VCA with Mirasys products.
Mirasys VMS supports both analog and IP based VCA services. The VCA functionality allows using VCA metadata for creating alarms based on metadata information. This functionality requires separate licensing (see below).
Installing VCA components to a Mirasys VMS system requires the following steps:
These steps are further discussed below.
Important: It is important to note that the licenses and the database are server specific and need to be installed on the server(s) on which the VCA feeds are situated. If a system contains multiple servers, the licenses and database must be installed separately on each server with VCA feeds.
Note: VMS comes pre-installed with drivers for VCA metadata analysis and metadata enrichment. The drivers can be updated later from system manager application.
Install MS SQL Server 2014 with a separate ExpressInstaller.exe or with the built in SQL installer of the VMS installer (Full installer).
The database must be installed separately on each server with Mirasys VCA.
The VCA functionality requires VCA channel licenses for each VCA camera feed.
The VCA license keys can be acquired at the same time as the server license key (see Obtain a License Key for further information).
Installing VCA Channel Licenses
The server license must include a VCA channel licenses for each VCA camera feed. VCA channel licenses can be added during default VMS license addition or separately (see Obtain a License Key for further information).
Installing VCA Software Licenses
The system requires a VCA license for each VCA source; i.e. for IP camera based VCA feeds. These licenses can be acquired by contacting firstname.lastname@example.org and sending a server specific hwguid.txt file for each server for which you want to add VCA channels.
To acquire VCA licenses:
Start the VCA Configurator (in the DVMS folder)
Note: Starting VCA Configurator automatically pauses Mirasys VMS server functions. Exiting VCA Configurator automatically restarts the server functions.
On the upper side of the VCA Configurator window, select the devices for which you want to create hwguid.txt files. Each device will have its own HWGUID file.
Contact Mirasys to get the VCA licenses. Attach the device specific hwguid.txt files to the mail.
After getting the licenses, use VCA Configurator to import each license.
After importing the licenses, you can configure the cameras with VCA functionality in the Camera tab in the VCA Configurator application.
To configure VCA zones and calibration:
As the configuration rules and parameters are extremely flexible and it is easy to do user errors, Mirasys can take no responsibility for the functionality of any user specified configurations. However, Mirasys provides configuration services for the VCA functionality.
The VCA based alarms are configured through System Manager through the default alarm management functionality. The VCA events are used as alarm start and end triggers.
Please see the Mirasys VMS Administrator Guide for information on creating alarms.