Default Passwords

  • Username: dvr
  • Password*: 32dvr

*) Password in Windows Server OS –systems is: 32dvrDVMS

  • Username: Admin
  • Password: 0308

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.

Before You Start

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 analogue and digital surveillance cameras, supporting the creation of analogue (DVR), digital (NVR) or hybrid (consisting of both analogue and digital) surveillance systems.

This gives instructions for setting up the VMS Servers and installing audio devices, IP cameras, dome cameras, video matrices, digital inputs and outputs, and client programs (Spotter and System Manager).

Help Documentation

This help documentation, for example, is available:

  • Installation Guide: how to install VMS servers and client programs. It also shows how to add devices to the system.
  • Administrator Guide: how to use the System Manager program for configuring the system.
  • Spotter User Guide: Complete instruction on how to operate all features of the Mirasys Spotter program. (Not available in all languages.)
  • VCA Installation and Configuration Guide: Instructions on how to install and configure Mirasys Video Content Analytics.

The PDF help documentation is on the VMS installation medium and the full setup package 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.

Manuals For Party Devices

When installing party devices, follow the manufacturer's instructions.

Technical Support

For technical support and warranty issues, please contact the system supplier.

About the System

What is Mirasys Software?

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 analogue and/or digital surveillance cameras, supporting the creation of analogue, digital or hybrid (consisting of both analogue 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:

1-150 VMS Servers:

  • Master Server (dedicated server – recommended -, one of the video recording VMS Servers, or the only server in a single-server, non-networked environment)
  • VMS Server ("nodes," if the system consists of multiple servers)

Client programs:

  • Mirasys VMS System Manager
  • Mirasys VMS Spotter for Windows
  • Mirasys VMS Spotter Mobile
  • Mirasys VMS WebClient

VMS Servers

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:

  • PTZ (dome) cameras and keyboards
  • External devices, such as sensors, to the digital inputs
  • External devices, such as doors, lights, and gates, connected to digital outputs
  • Monitors
  • Printers
  • Backup unit (NAS, SAN, or RAID, for example)

Master 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:

  • It verifies the identity of all programs and users who try to log on to the system (authentication).
  • It stores all system configuration data.
  • It stores all user data.
  • It monitors the system.
  • It synchronizes the clocks on all servers.
  • It generates reports.
  • It stores watchdog event.
  • It stores alarms.
  • It stores an audit trail.

Client Programs

System administrators use the System Manager program for these tasks:

  • Configuring the servers.
  • Adding user accounts and user profiles.
  • Monitoring the system.

End-users use the Spotter program, for example, for these tasks:

  • Monitor real-time and recorded video and audio
  • Control digital I/O switches and PTZ cameras
  • Export video and audio clips to local media
  • Receive and handle alarm notifications
  • Create video matrixes via the optional, separately sold Agile Video Matrix (AVM) software
  • Control automatic license plate recognition systems via the optional, separately sold ANPR+ software

Mirasys 32-bit vs. 64-bit Versions

Starting from Version 8 onwards, the Mirasys VMS software is available only as a 64-bit ("x64") version.

Note that 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

In a networked, multi-server Mirasys VMS system, the server with the Master Server role can simultaneously connect to and manage both 32-bit and 64-bit VMS Servers (also known as "nodes") on the network:

  • The 64-bit Master Server supports simultaneously both 32-bit as well as 64-bit VMS Servers.
  • A Version 8.x based Master Server supports simultaneously Version 8.x, Version 7.x and Version 6.x VMS Servers, but does not support servers based on Version 5.x, or earlier.

Version 8 supports clients to connect to 32bit and 64-bit server versions. It is recommended to reinstall the clients with a 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 analogue video capture cards (also known as compression cards or grabber cards).

The system manager shows the 32 bit or 64-bit version information in the "Version" table.

All new IP camera, the 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.

System Requirements

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 fulfils 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 a 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 are 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.

Rating Minimum Server Requirements

The servers require this minimum (small) system configuration:

Hardware:

  • Intel Core i3, or better
  • 8 GB of RAM recommended
  • Min. 1 TB HDD
  • Min 100 GB C: drive space

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.

The 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).

Minimum Client Workstation Requirements

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 of the minimum requirements for a small-scale surveillance system.

  • Intel Core i3, or better (when using H.264 cameras in the system, quad-core processors are recommended).

  • The recommended processor allows simultaneous viewing of more than 10 cameras at a higher resolution than VGA (640×480).
  • Min. 8 GB RAM recommended
  • Min. 20 GB of free disk space
  • Display adapter with at least 512 MB of memory. Video adapter memory amount and performance will impact capacity to display simultaneous recorded or live camera streams. 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.

Windows OS Compatibility

Mirasys VMS V9 supports the following operating systems:

Operating System

Server with analogue camera support via capture cards

Server with only IP cameras or connected video servers (encoders)

Gateway server

System Manager client application

Spotter for Windows client application

Windows 8 Pro & Pro Retail

32-bit Mirasys VMS V7 or earlier only

X

X

X

X

Windows 2008 Server R2 Enterprise

32-bit Mirasys VMS V7 or earlier only

X

X

X

-

Windows 2008 Server R2 Foundation

-

X

X

X

-

Windows 2012 Server Standard Edition

-

X

X

X

-

Windows 2012 Server R2

-

X

X

X

X

Windows 10

-

X

X

X

X

Windows Server 2016

-

X

X

X

X

Windows Server 2019

 

X

X

X

X


Notes:

Mirasys VMS has not supported Windows XP since Mirasys VMS version 6.4. If Windows XP support is required, do not install Mirasys VMS 6.4, or any later releases.

Make sure that the "Desktop Experience" feature is activated for Windows server operating systems.

No releases before Mirasys VMS V7.4 has support for Windows 10. Any older versions (V7.3 or older), if used with Windows 10, must be upgraded to the latest V7.4 release or later versions.

Network Requirements

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.

General

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 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:

  • Interrupt Moderation Rate --> Extreme
  • Receive Buffers/Receive Descriptors --> 2048
  • Transmit Buffers/Transmit Descriptors --> 2048

If the network card cannot be adjusted to these settings, replace the card.

IP Addresses

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 to the display servers is 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.

Ports

Port

Protocol

Service

Direction

5008

TCP

SMServer

OUT

5009

TCP

DVRServer

OUT

5010

TCP

WDServer

OUT

5011

TCP

DVRServer

OUT

8081

TCP

SMServer

OUT

8082

TCP

SMServer

OUT

8083

TCP

DVRServer

OUT

3556-4556

UDP

DVRServer

IN

554

RTSP

DVRServer

IN

Note: 

  • If you are using Windows Firewall, the VMS installer can automatically create exceptions for the required ports.
  • Automatic port forwarding can configure the ports to be different from these default ones.

Bandwidth Requirements

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:

  • Data transmission from the servers to the client computers (uplink) requires more bandwidth than data transmission from the client computers to the server (downlink). The connection does not have to be symmetric.
  • Real-time monitoring requires more bandwidth than transmitting recorded video or audio.
  • In addition, signalling and protocols increase the required bandwidth.

Data Security

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 (, intranet).

Server Installation

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:

  • Connect the display, mouse, and keyboard to the computer.
  • Connect the network cable to the computer (for network use).
  • Connect all power cords and turn on the power.
  • If your system has analogue cameras, connect the cameras to the encoder, and treat the encoder as an IP camera.
  • Install the server software. Please see the chapter Installing The Software for information on installing the required software.
  • Install IP cameras and other devices. Please see chapter Installing Devices for further information.
  • Install the client applications. Please see chapter Installing Client Programs for further information.
  • If your system WebClient or Spotter Mobile applications, you will need to install the Mirasys Gateway server. For further information, please see chapter Mirasys Gateway Server Installation.
  • For advanced users only: if your system contains VCA components, install and configure the required software.

To update recording software and client applications:

Please see the chapter Updating for information on updating server or client software.

Failover Servers - Optional

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 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 VMS Administrator Guide.

Installing The Software

During the 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 the system manager.

If the automatic storage configuration is grabbing disks that are not intended for material storage, the logic can be disabled from the installer.

The HDD's don't need to be the same size 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 for other HDDs. If 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 the 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.

Note

These instructions apply when installing software to a new server or reinstalling software to a server not provided by Mirasys. When reinstalling software to a server provided by Mirasys after e.g. a hard disk failure, please see Flash Memory Backup / Restore for further information.

IMPORTANT NOTE: Mirasys VMS will require SQL Express 2014 to be installed on the Master server. The "full" Microsoft SQL Server 2014 works, but then the configuration has to be customized. Mirasys l provides an installer that will install the SQL Express with correct settings as part of the VMS install. If you are planning to use Microsoft SQL Server Standard or Enterprise, contact Mirasys support on how to configure the SQL connection string to get the database connection working correctly.

IMPORTANT NOTE: Mirasys VMS is available as a Full installer and Limited installer.

The Limited installer can be used with

  • Client application installs
  • Networked VMS Server installs or upgrades when no Mirasys VCA is required
  • Upgrade installs when SQL is already installed

The Full installer should be used with

  • Master Server installs
  • VMS Server installs when Mirasys VCA is required

To install the server software:

  • Copy the installer package somewhere on the machine where you want to do the.
  • Start the VMS installer by clicking the installer file Release_XX_DVMS_x64_Full.exe or Release_8XX_DVMS_x64_Limited.exe
  • NOTE: The Mirasys VMS 8.x software is not compatible with earlier Mirasys VMS licenses. If you the software. If the software is upgraded before the license key is updated, all specific information (including profiles and stored material) will be lost. Please see Obtain a License Key for updating the license key.
  • In Welcome to the VMS Installation, click Install.
  • If you are installing a new system with the Full installer and the installer detects that the system needs an MS SQL server, installation of MS SQL Express 2014 will start. This takes approximately 7-8 minutes. If the installer detects already a SQL installation on the PC, this step is skipped automatically.
  • The installer next installs SlimDX to the system. takes approximately 30 seconds
  • After this, the "Welcome to VMS Setup Wizard" is displayed. Click Next.
  • In the next screen, you can select various installation options
  • If you install the Recording Server service, you will need a VMS license. If you only install client applications, you will not need a VMS license.
  • By default, the setup program installs the server and the applications System Manager, Spotter, and System Monitor:

If you do not want to install them, 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 a local hard drive. Do not select this option if you are not using Windows Firewall.

Click Next.

Select the destination folder and click Next.

Select the process startup setting. In the 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 that 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 dialogue 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 dialogue 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 dialogue box "Completed the VMS Setup Wizard" is shown.

Click Finish.

For information about setting up the server, see Server Installation.

For information about how to install the client programs, see Installing Client Programs.

Set The TCP/IP Addresses

To set the TCP/IP addresses in Windows 7:

  • Click Start, point to Settings and then click Control Panel.
  • Double-click Network and Internet.
  • Double-click Network and Sharing Center.
  • Click "Change adapter settings"
  • Right-click on the network adapter of your choice and choose Properties.
  • Click Internet Protocol v4 (TCP/IP) and then click Properties.
  • Select Use the following IP address and type a static IP address. Also specify the Subnet Mask, Default Gateway and DNS Server address.

Set The Master Server's IP Address to The System Files

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:

  • Start System Manager locally on the Master Server as instructed in the Administrator Guide.
  • In the System tab, click Change server addresses.
  • Click on Local Server.
  • Click the Change server address button .
  • Type the new IP address or DNS name of the server into the New server address field.
  • Click OK.

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.

Enable Time Synchronization

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:

  • Click Start, point to Settings, click Control Panel, and then double-click Date and Time.
  • On the Internet Time tab, sure that the checkbox Automatically synchronizes with an Internet time server is not selected.

Obtain a License Key


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 to address of the server.

To get a license key:

  • Start System Manager. The License Information dialogue box is automatically shown when no license key has been specified.
  • On the System tab, under Licenses, double-click the server that you want to update.
  • In the License Information dialogue box, copy the MAC address and send it to orders@mirasys.com In return, you will receive the license key as a text file.
  • Click Import license from the file.
  • Click OK. The system is updated immediately.

Note: 

  • The default unregistered state that allows the use of one IP camera has been time-limited. The unregistered state can be active for up to 60 days after which a valid license key is required. Unless a valid license key is not added to the system within 60 days after the installation, the system will cease to operate.
  • For information on acquiring VCA feed source licenses, please refer to Installing VCA Feed Source Licenses.

Setting Up The System

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:

  • Start System Manager locally or over a network (click the System Manager icon on the desktop).
  • Add servers to the system and configure their settings on the VMS Servers tab.
  • Add user profiles on the Profiles tab.
  • Add user accounts on the Users tab.
  • Install the client programs on the end users' computers. See Installing Client Programs.

For more information about how to configure the system, see the Administrator Guide.

Installing Devices

Installing IP Cameras

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 analogue cameras into IP cameras. Video servers are also connected directly to the local area network, and they have their 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.

Setting Up DirectX PTZ Joysticks

Any DirectX joystick can be used, but you can contact your supplier for a list of 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 the 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.

Installing Client Programs

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:

  • Unzip the installer package somewhere on the machine where you want to do the Install.
    NOTES:
  • - Clients can be installed either with the VMS installer file Release_8XX_DVMS_x64.exe OR with an available "Spotter -only" installer file.
    - SQL Server is not needed for a client installation, so use the "Limited" DVMS installer file for installing only the clients.
  • Start the VMS installer by clicking the installer file Release_8XX_DVMS_x64.exe
  • In Welcome to the VMS Installation, click Install.
  • next, install SlimDX to the system. takes approximately 30 seconds
  • After this, the "Welcome to VMS Setup Wizard" is displayed. Click Next.
  • In the next screen, you can select various installation options
  • When installing clients, uncheck the "Recorder" option and sure that the "Applications" option is checked.
    If you want firewall exceptions set automatically for Windows Firewall, open the menu next to Set firewall exceptions and select Will be installed on a local hard drive. Do not select this option if you are not using Windows Firewall.
  • Click Next.
  • Select the destination folder and click Next.
    In the Installation Configuration dialogue 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 dialogue 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.
  • Click Install to start the installation.
  • When the server has been installed, the dialogue box "Completed the VMS Setup Wizard" is shown.
  • Click Finish.

Compatibility

Mirasys. servers are compatible with Mirasys 7.x and 6.x networked VMS Servers. The Master Server always needs to be the same or higher version than the network VMS Servers

Updating

Version 7 (or older) file system support

DVMS installer

Filesystem support selection is made during DVMS install in this dialogue:

 

1. Use File System V7 or older

  • Old storage will be used in V7 format without any changes to its current disks or structure. 
  • All previously-recorded data (video, audio, text, alarms etc.) will be accessible after the software has been updated.
  • If you need to add more storage disks then these disks must have the same size as the already installed disks.

2. Use File System V8/V9 and remove old data

  • Old storage will be erased and formatted to a new File System format. 
  • All previously-recorded data are lost.

3. Use File System​ V8/V9 and leave old data

  • Old storage disks will be left as is, but DVMS will be configured to use a new File System format on new disks. 
  • This is useful if there is some additional disk that can be used for new data, and there is some need to keep old storage for some time to access previously recorded data.
  • Previous data can be opened as an archive in Spotter.
  • The installer will create archive information if this option is selected in the installer.

Notes for installer's option 3 (Use File System​ V8/V9 and leave old data)

If there were several disks used in DVMS V7, then each disk will be opened as a separate archive in V8 or later after the DVMS update. DVMS V7 has a recording mechanism similar to RAID 0 (stripe recording). Still, in this case, it writes 1st second to one disk, 2nd - to another, so as a result, if each disk is opened separately, it will have gaps in places where those data is written to another disk.

If text channels are used in V7, then to generate archive information correctly, DVMS V8 or later should be installed on top of V7 (without V7 uninstall). If V7 is uninstalled first - text channel event names and search tags information will not be written to the archive information file. Also, if V7 will be removed with the "Remove settings" checkbox set, then also channel names, manufacturer, and other information will be lost so that archive information will be generic (like Camera 1, Audio 1 etc.)

Notes for alarms database

If V7 is updated to V8, then the alarm database should be removed, so the option "Yes" should be set to this installer dialogue:

In another case, the alarm database will not be updated, and previously recorded alarms will not be fetched from file storage.

Limitations

DVMS with V7 file system support has those limitations:

1. Can't launch several archiving processes at the same time, so if the timed archive was launched - the manual archive would fail until the first process is finished.

2. If disk connection will be lost or disk will be unplugged and plugged again - it will not be recovered back until DVRServer restart.

3. Future file system features will not be supported

Updating a Server

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:

Click Start, point to Settings, click Control Panel, and then double-click Uninstall programs.

Click DVMS and then click Uninstall and then review the installation instructions earlier in this.

Updating Client Programs

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, emove the current version and install the new version by running the VMS installer.

To remove the current version:

Click Start, point to Settings, click Control Panel, and then double-click Uninstall programs.

Click DVMS and then click uninstall and then review the installation instructions earlier in this.

Updating VMS Servers From Master Server

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, 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 using the 'Update servers' tool in System Manager.

NOTE: This feature is available only if the VMS Servers have Mirasys VMS 6.2.5 or later. In case the VMS Servers have an earlier version, you need to install Mirasys VMS 6.2.5 or newer on them manually to enable remote server updates.

NOTE: In some cases, the VMS Servers might need a restart of PC after remote software update. Monitor the servers after a remote update, and if they do not return online in 10 – 15 minutes, restart the PC they are running on.

NOTE: Please remember the different 32-bit and 64-bit versions when doing remote updates. If a system is partially 64-bit, do not push a 64-bit update to all servers.

Updating Components

In addition to camera drivers and Spotter Plugins, it is possible to also update metadata drivers from the 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 the whole system or only selected servers.

Contact Mirasys for more information on available metadata drivers and updating them.

Flash Memory Backup / Restore

Mirasys VMS includes an automatic flash-based backup and restores 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 server hard disk needs to be reformatted or replaced.

The automatic flash memory functionality can backup and restore the following:

  • Windows OS
  • Mirasys VMS software
  • Mirasys VMS license
  • Server configuration files

The automatic flash memory functionality does not include the following:

  • Windows OS updates made after server delivery
  • Any VMS software updates made after server delivery
  • Any driver updates made after server delivery

Notes:

  • It is important to note that the automatic restore function restores the VMS software version delivered with the server. The same applies to IP camera drivers. If the server has been updated or new drivers installed, the software needs to be after restore, and the IP camera drivers will need to be reinstalled.
  • It should be noted that the first backup is done at midnight of each day (unless changes are made to the configuration during the hour before midnight, in which case backup is delayed until the next day).

Flash Memory Backup

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.

Flash Memory Restore

Hard disk failure, the system administrator may need to restore them 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 . 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 Gateway Server Installation

Mirasys WebClient is a browser-based application that is used for viewing video from Mirasys servers over a network. Mirasys WebClient uses user profiles, user names, and passwords as Mirasys System Manager and Spotter client programs.

To use Mirasys WebClient, the Mirasys Gateway server must be first installed on a computer running an 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.

Minimum System Requirements

Client:

  • Internet Explorer 6 or Mozilla Firefox 2.0 or newer
  • Java Runtime Environment (latest version recommended for security reasons)

Server:

  • Windows 7 Enterprise, or Windows 2008/2012 Server
  • HTTP server software (IIS)
  • Intel i3 processor, or better
  • 4 GB of RAM

Note: Please that the minimum system requirements are recommended for mostly live viewing. If multiple users access the same WebClient server simultaneously mainly for search and playback functions, a A more powerful processor is required.

System Restrictions

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 independent; if, for example, User A has 30 open video streams and User B has video streams neither can open any more streams unless one or more of the current streams are closed.

Installing The Mirasys Gateway Server

To install the Mirasys Gateway server:

  • Double-click the Release_8XX_Gateway_x64.exe installation package to start the installation.
  • After the VMS Gateway Setup screen has loaded, select the destination folder and click Next.
  • Type the SMServer IP address (the IP address of the Master Server) into the SMServer IP field.
  • Click Next
  • When the software has been installed, click Finish.

Verifying The Installation

To verify that the server has been correctly installed:

Open a compatible web browser and type the following address:

://[WEBCLIENT SERVER URL]:[PORT]/

For example, if the WebClient server is on the same computer:
http://localhost:9999/

If the server is correctly installed, the 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.

Streaming Options

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:

http://localhost:9999?video=native

Installing Spotter Plugins

Spotter plugins can be added to the 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.

After the plugin is installed to System Manager, each Spotter client to this Master Server (SMServer) gets the updated plugin next time the client is started.

The development of custom plugins is possible. Contact Mirasys for further information.

Installing VCA Components

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 analogue 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:
  • Installing a database to each Mirasys VMS server with VCA streams
  • Adding VCA channel license keys to each server with VCA streams
  • Configuring the VCA cameras
  • Configuring alarm events based on VCA messages in System Manager

These steps are further discussed below.

Important: It is important to note that the licenses and the database are 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 the system manager application.

Database Installation

Install MS SQL Server 2014 with a separate ExpressInstaller.exe or with the installer (Full installer).

The database must be installed separately on each server with Mirasys VCA.

Adding License Keys

The VCA functionality requires VCA channel licenses for each VCA camera feed.

The VCA license keys can be acquired 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 license 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 sources for IP based VCA feeds. These licenses can be acquired by contacting your Mirasys sales representative and sending a 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)

Nore: 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 you want to create hwguid.txt files. Each device will have its HWGUID file.

Contact Mirasys to get the VCA licenses. Attach the specific hwguid.txt files to the mail.

After getting the licenses, use VCA Configurator to import each license.

Camera Configuration

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:

  • Calibrate the VCA functionality.
  • Create zones and rules.
  • Test the functionality of your rules.

As the configuration rules and parameters are flexible easy to user errors, Mirasys can take no responsibility for the functionality of any specified configurations. However, Mirasys provides configuration services for the VCA functionality.

VCA Installation

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.