Documentation for Axxon Next 4.3.5. Documentation for other versions of Axxon Next is available too.

Previous page Recommended hardware platforms for Server and Client  Supported operating systems Next page

Skip to end of metadata
Go to start of metadata

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. 

Take into account the size of the system log and metadata databases.

Attention!

You need at least 10 GB of free disk space to install the Axxon Next VMS package in a Server and Client configuration.

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
MPEG4: from 500 GB to 2 TB
MJPEG: from 1.3 TB to 3.5 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
MPEG4: from 500 GB to 2 TB
MJPEG: from 1.3 TB to 3.5 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
MPEG4: from 2 TB to 8 TB
MJPEG: from 5.3 TB to 14 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.01 GB / day);

The capacity of the system log database (average detection activity) = D * T * (0.03 GB / day);

The capacity of the system log database (high detection activity) = D * T * (0.12 GB / day);

where D is the total nuMBer of detectors created in system,

T is the estimated duration of syslog storage, days.

Object trajectory database 

The following formulas can help to determine the required disk size for the trajectory database:

Size of object trajectory database = N×T×(0,5GB / day)– sufficient disk size;

Size of object trajectory database = N×T×(1GB / day)– sufficient disk size plus reserve space;

Size of object trajectory 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 5 GB of free disk space, the Object Tracking DB is overwritten - new data records over the oldest data records.