Video Insight IP Server runs as a Windows Service on 32 or 64 bit OS. Requesting images from the cameras, the IP Server processes the images for motion alarm, stores the video in a folder structure, and saves all configuration, motion, and system logs in a SQL server database. The Clients connect to the IP Server - not directly to the cameras - and the Web Client uses Microsoft Internet Information Server (IIS). From an architecture perspective, Video Insight has four components: Server; Storage; SQL and IIS - each of which can be configured a number of ways to adapt to your organization's needs.
VI7 also supports integration with a number of industry leading access control manufacturers at no cost.
Integration instructions for 3RD Party Access Control solutions: Click Here
Gain Peace of mind knowing that each server and all cameras are running
The Video Insight Server can write to a single drive, multiple drives, or each camera can be pointed to a unique drive. The Server creates a folder structure that is organized by IP address and date and time. By default, the Server will use all available storage in the designated path and overwrite the oldest video when necessary.
The amount of storage is determined by the bitrate of each camera and how much of that will need to be saved. For example, a 1.3 Megapixel camera set at 10 FPS can be configured to stream video at 1.5 Mbits/sec and if the camera is recording motion at 50% of the time, then we can estimate we need 7 GB of storage per day. Click here for the VI storage calculator.
Video Insight supports all storage that Windows can address. In addition to the size of the storage, it's necessary to confirm the storage system can handle the amount of video — otherwise video can be lost when the storage is overloaded. To calculate the maximum storage throughput we must assume all cameras will write simultaneously and add up all camera bit-rates. Since most storage systems refer to their maximum simultaneous write speeds in Mbytes, divide the total camera traffic by 8 to convert it to MB. For example, let's assume you have 100 cameras that will stream at 3Mbits/sec or a total of 300Mbits and we expect them to record 50% of the time. The storage system must be able to write 37.5 MB/sec at its maximum. Video Insight has developed a storage speed test to confirm your systems capability. Click here for the VI Hard Drive Speed Test.
Hard drive manufacturers offer a wide variety of drives, offering different speeds and MTBF rates. When selecting drives, consider that video surveillance applications write data continuously but have far fewer read requests. This differs from typical file server operations where the hard drive is reading and writing simultaneously.
To provide the maximum protection to your data, we recommend using RAID5 with a designated Hot Spare. RAID5 allows for a single drive to fail without data loss and by designating a Hot Spare, the system will automatically rebuild the RAID on failure. Ensure your RAID card can handle the camera’s traffic as described above and for larger deployments, hardware based RAID with onboard cache is preferred.
Dell PowerEdge R720xd with (12) 4TB drives providing a usable storage of 36TB The Dell H710 PERC RAID card has a maximum storage throughput of 313.65MB/sec with continuous writing of 115 MB/sec.
Dell PowerEdge R520 with (8) 3TB drives providing a usable storage of 19TB The Dell H710 PERC RAID card has a maximum storage throughput of 313.65MB/sec with continuous writing of 205 MB/sec.
Our preconfigured NVR options can also address your requirements.
The Video Insight Server supports all Windows addressable storage. Current customers are using storage solutions from Dell, EMC, HP, Isilon, and others.
The Video Insight Server supports Automated Failover at no additional software cost. When utilizing the Video Insight Single Database configuration, a physical or virtual server can be designated as a Failover. This server will monitor the other servers and inherit the cameras of a failed device.
For example, if we have the five servers with one designated as a Failover, when one of the four stops writing information to the SQL database, the Failover Server will assume the role of the failed server and all camera traffic will now be associated with that server. Once the failed server is put back into service, restarting the primary server will move the cameras back to their original location.
Video Insight includes a standalone user management system or integration with Active Directory, LDAP, and Novell eDirectory. When using AD or LDAP, administrators create an active connection to the AD Server providing real time authentication.
Video Insight stores all camera-related settings in a Microsoft SQL Server database. In multi-server configurations, a single database can be used to store all settings. Using a centralized database has a number of benefits including automated failover, but it also allows administrators to easily move cameras between servers. For example, let’s assume you have 100 cameras spread across two equally-sized servers, but one of the servers is only keeping 20 days of recorded history instead of the desired 30 days. Using the Camera Setup tab, you can easily move cameras between servers with a few mouse clicks.
Video Insight supports all virtualization platforms, including VMware, Microsoft Hyper-V, and Citrix XenServer. Virtualizing your surveillance allows you to leverage existing infrastructure as well as create a perfect environment to test and deploy.
Deployed Virtual Environments:
The Video Insight Software Development Kit (SDK) is an application programming interface that provides the ability for third-party software developers or supported OEMs to develop their own client-side applications to access live and recorded video from Video Insight servers via an interface provided by Video Insight.
The Monitor Station client is used to configure and administer Server settings. In addition, the Monitor Station provides administrators a robust set of tools to optimize server performance including bit rates, last image received, FPS, and resolution.
Video Insight Server and Clients are upgraded with a single Setup.exe. Updates do not require existing applications to be removed, and includes automated update distribution
Video Insight uses a Microsoft SQL Server database to store system settings, user permissions, activity, alarm, and system logs. Video is not stored in the SQL Database so the database can be installed locally on the server and multiple servers can utilize one database. In addition, the SQL Database can be installed in a central location for multiple systems to share. When using the Monitor Station users do not see a difference when using a single or multi-database configuration. Microsoft SQL Server Express is installed during the standard installation of Video Insight. For installations that have existing SQL Servers already running, the Video Insight Servers can utilize a single database providing additional redundancy of the database.
Benefits of a Single Database Configuration When Using Multiple Servers
Tpyical Size of a Database
The database size will vary based on the amount of motion alarms. In environments with higher motion activity, the actual size of the database could be larger.
Video Insight utilizes Microsoft Internet Information Services (IIS) to power the Web Client. IIS is installed as a component of Windows and simply needs to be enabled for most OS versions. Each Video Insight Server will utilize IIS on the local server, and with the use of a shared database, can power the Web Client for use with any server load-balancing. Administrators can point users to a single URL address and the Video Insight Server with IIS will pull the live and recorded video from the appropriate server. For load balancing purposes, groups of users can be pointed to different Video Insight Servers. This decreases the amount of inter-server traffic.
Video Insight supports all of the IIS versions of the supported Operating Systems.
The Video Insight Web Client supports two transmission methods referred to as Low and High Speed mode. When using Low Speed mode, the Web Client receives MJPEG images and when in High Speed mode, the client receives the camera's native compression. IIS handles the transmission and its process is not CPU intensive.
When considering the number of Web Client users per server, the most important consideration is the cumulative bandwidth required.
Video Insight supports distributed and centralized deployments. As an example, let's use a school district that has 25 campuses. Traditionally, this required each campus to have servers, requiring space, power, security, and air conditioning. With increases in bandwidth, switching, and better compression, it's now possible to move the servers to a central data center.
Centralization can also mean centralizing existing DVRs and NVRs into a single solution. For example, a high school might have 10 DVRs spread across the campus. Using solid-state video encoders, all the video can be sent to a single NVR.
Centralization can be very beneficial, but the following areas need to be addressed prior to deployment:
Video Insight is licensed on a per-camera basis and does not require licenses for servers, clients, or accessories. During setup, a 5-digit key is activated online and is associated with the server specifying how many cameras can be connected to the server. Adding or removing cameras does not require changes to the key and adding additional cameras is done online or manually.
Video Insight Mobile, Web, and Monitor Station clients do not require activation keys and have no restrictions on installation.
Video Insight Server and Clients are upgraded with a single Setup.exe. Updates do not require existing applications to be removed, and includes automated update distribution.
The Video Insight Server can support multiple network interface cards (NIC) and traffic can be segmented by type. A common configuration is to isolate camera traffic on one NIC and connect a second NIC to the corporate network. This isolates all camera traffic, ensuring it does not affect normal traffic. In addition, the Server can support camera traffic from multiple NICs.
When using the Web Client, IIS handles all internal routing and can support inbound traffic on all NICs, but the server listens for the Monitor Station on a single NIC.
As processing power increases, camera manufacturers are adding more features to cameras. In addition to H.264 compression and enhanced onboard motion detection, analytics, like directional direction and enter and exit filters, are becoming common. These analytics allow rules to be configured to do object counting or alarms when a vehicle enters an unauthorized area. The Video Insight Server accepts these inputs and allows users to set up automations based on their trigger. For example, the following uses a counting analytic to notify the operator if the number of people in a room exceeds the specified threshold.
Video Insight supports camera-side analytics from the following manufacturers:
These companies have a variety of analytics including:
We can setup scheduled based Rules, that on alarm, can do any (or multiple) of the following:
Bandwidth is the primary challenge associated with hosted video, but the second challenge is the backend server. Most VMS platforms specify 120 or fewer cameras per server. In a hosted environment, this server requirement can dramatically increase the deployment costs. Video Insight v5.5 has been designed for Hosted Video with single OS support at over 2,000 cameras per host.
Call us for a more detailed overview of our hosting offering.
Minimum specifications depend highly on total camera load placed on each individual server, and total bandwidth availability of network which the cameras reside on. Please consult with a Panasonic sales professional for accurate system requirements based on your site's needs.
|Processor||2.0 GHz quad-core||Dual 2.4 GHz quad-core|
|Memory||4 GB||8 GB+|
|Network||1 Gb/s||Dual-Port 1 Gb/s+|
|Display Resolution||1600 x 900||1920 x 1080 or higher|
|OS||Win 7 Pro, Win 8 Pro, Win 10 Pro||Server 2008 R2 or Server 2012 R2|