Documentation for Axxon One 1.0.
Previous page
Next page
On page:
General requirements
For Axxon One VMS operation, the disk subsystem must match the following requirements:
The device must have no less IOPS the Axxon One VMS.
The Axxon One VMS records video footage to archive volumes in 4MB blocks with a 10 second interval. If the most recent block is not full after 10 seconds, it will be filled up later.
Similarly, footage is played back in blocks (except for re-indexation, see the utility for archive management Console utility for working with archives).
This is how you can estimate the IOPS value for the Axxon One VMS.If average bitrate per camera is less than 3.6 Mbps
If average bitrate per camera exceeds 3.6 Mbps
IOPS during archive recording
Archive recording includes both data input (writing) and output (reading) operationsIOPS (writing) = 0,29 * N
IOPS (reading) = 0,035 * MIOPS (writing) = 0,065 * M
IOPS (reading) = 0,035 * MIOPS during archive playback
Archive playback includes only output (reading) operationsIOPS (reading) = 0,035 * R * S
IOPS during simultaneous recording and playback
IOPS (writing) = 0,29 * N
IOPS (reading) = 0,035 * M + 0,035 * R * SIOPS (writing) = 0,065 * M
IOPS (reading) = 0,035 * M + 0,035 * R * Swhere
- N is the number of camera channels being recorded;
- M is the cumulative bitrate over all camera channels being recorded, in Mbps;
- R is the cumulative bitrate over all camera channels being played back at normal speed (1x), in Mbps;
- S is the playback speed.
- If you use RAID storage, please specify write-back policy for writing to cash memory.
Storage requirements
Size of disk subsystem will be calculated on the basis of frame resolution and compression, rate of video signal frames per second, number of cameras recording events to the hard drives and other recording parameters.
Minimum requirements
You need at least 10 GB of free disk space for Windows OS to install the Axxon One VMS package in a Server and Client configuration.
Please see the storage calculations below, taking into account space needed for video footage, databases and system logs.
Size of archives
Size of disk subsystem can be calculated by formula:
Size of Disk subsystem (MB) = Time of storing an archive (days) x Cameras number x Rate of recording (fps) x3,51 x Time of guaranteed recording from a camera (h / day) x Average frame size (KB),
where Time of storing an archive is the required time of storing an archive from one camera, days;
Cameras number is the number of cameras recording to the archive;
Rate of recording is the frame rate of recording to the archive, frames per second;
3,51 = (60 sec in min x 60 min in hour)/(1024 KB in MB) – is the coefficient used for KB/s-MB/h conversion,
Time of guaranteed recording from a camera is the number of hours of guaranteed recording from one camera to the archive per day,
Average frame size is the average size of the camera frame, kilobytes.
Note
Average frame size for 640х480 resolution is:
Video codec | Average frame size |
|---|---|
H.264 | from 8 KB to 17 KB |
MPEG4 | from 8 KB to 35 KB |
MJPEG | from 23 KB to 60 KB |
Average frame size may vary over a wide range depending on the vendor, model and settings of the camera and video image complexity.
Note
To calculate the frame size one can use the ratio, that while increasing vertical or horizontal resolution two times, the average frame size will be increased four times (this rule is a relative one and can be applied only to some cameras' models).
Examples of calculating a size of disk subsystem (without size of syslog database) are presented below.
Recording parameters | Calculating results |
|---|---|
4 cameras with 25 fps and 640х480 resolution, guaranteed recording of 24 hours per day during one week | H.264: from 500 GB to 1 TB |
16 cameras with 12 fps and 640х480 resolution, guaranteed recording of 12 hours per day during one week | H.264: from 500 GB to 1 TB |
4 cameras with 25 fps and 1280х960 resolution, guaranteed recording of 24 hours per day during one week | H.264: from 2 TB to 4 TB |
Database of the system log
The size of syslog database is to be taken into account when the size of disk subsystem is calculated. Estimated size of syslog database is calculated by formulas:
The capacity of the system log database (low detection activity) = D * T * (0.04 GB / day);
The capacity of the system log database (average detection activity) = D * T * (0.12 GB / day);
The capacity of the system log database (high detection activity) = D * T * (0.48 GB / day);
where D is the total number of detectors created in system,
T is the estimated duration of syslog storage, days.
Metadata database
The following formulas can help to determine the required disk size for the metadata database:
Size of metadata database = N×T×(0,5GB / day)– sufficient disk size;
Size of metadata database = N×T×(1GB / day)– sufficient disk size plus reserve space;
Size of metadata database = N×T×(5GB / day)– sufficient disk size plus a large reserve.
N equals the number of video cameras in the system actively recording metadata; T equals the period of time (number of days) that metadata will be stored. By default, T = 30 days.
If you have less than 15 GB of free disk space, the metadata DB is overwritten - new data records over the oldest data records.
Self-diagnostics service
When calculating disk subsystem capacity, please note that self-diagnostics service may generate up to 100 Mbytes of data per day.
The service's internal database retention time is limited to 7 days, and its size is limited to 512 Mbytes.
Overview
Content Tools