Versions Compared

Old Version 1

changes.mady.by.user Vadim Belyakov

Saved on

compared with

New Version 2

changes.mady.by.user Alena Kniazeva

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Section


Column
width35%


Panel
borderColor#CCCCCC
bgColor#FFFFFF
titleBGColor#F0F0F0
borderStylesolid
titleOn the page:
Table of Contents



Column




General requirements

For Axxon Next VMS operation, the disk subsystem must should match the following requirements:

  1. The device must have no less IOPS the Axxon Next number of input/output operations (IOPS) of the device should not be less than the IOPS of Axxon Next VMS.
    The Axxon Next VMS  records video footage to the 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 managementblocks of 4 MB (megabytes) every 10 seconds. However, if the block is not filled in 10 seconds, a smaller fragment of the block will be recorded, which will be added to later.
    Archive playback is also performed in blocks (except when reindexing, see Console utility for working with archives).
    This is Below you can see how you can estimate the IOPS value for the  Axxon Next VMS.


    If the average bitrate per camera is less than 3 ~3.6 Mbps

    If the average bitrate per camera exceeds 3 ~3.6 Mbps

    IOPS during archive recording
    Archive recording includes both data input (writingrecording) and output (reading) operations

    IOPS (writingrecording) = 0,.29 * N

    IOPS (reading) = 0,.035 * M

    IOPS (writingrecording) = 0,.065 * M

    IOPS (reading) = 0,.035 * M

    IOPS during archive playback
     Archive playback includes only output (reading) operations

    IOPS (reading) = 0

    ,

    .035 * R * S

    IOPS during simultaneous recording and playback

    IOPS (writingrecording) = 0,.29 * N

    IOPS (reading) = 0,.035 * M + 0,.035 * R * S

    IOPS (writingrecording) = 0,.065 * M

    IOPS (reading) = 0,.035 * M + 0,.035 * R * S

    where

    • N is the number of camera channels cameras being recorded;
    • M is the cumulative bitrate over of all camera channels cameras being recorded, in Mbps;
    • R is the cumulative bitrate over of all camera channels cameras being played back from the archive at normal speed (1x), in Mbps;
    • S is the playback speed.


  2. If you use RAID storage, please specify the write-back policy for writing recording to cash memory.

Storage requirements

Size of The 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. capacity of Axxon Next Server should be estimated taking into account the resolution, the compression algorithm, the frame rate of the recorded video signal, the number of video cameras from which the recording to disk(s) takes place and other recording parameters. In addition, the size of the system log and metadata databases should be considered.

Minimum requirements

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

Please see See the storage calculations below, taking into account space needed for video footage, databases and the size of the archive, the size of the database and the size of the archive of the system logs.

Size of

...

the archive

Size The capacity of the disk subsystem can be calculated by the formula:

Size Capacity of Disk disk subsystem (MB) = Time of storing an archive (days) x * Cameras nuMBer x number * Rate of recording (fps) x3,51 x FPS) * 3.51 * 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 for storing an archive from one camera, days;

Cameras nuMBernumber is the nuMBer number of cameras from which recording to the archive takes place;

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 factor used for KB/s -in MB/h conversion,;

Time of guaranteed recording from a camera is the nuMBer 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.

Info
titleNote

Average frame size for of 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, the model and the settings of the camera and video image complexity.


Info
titleNote

To calculate the frame size one you can use the ratio, that while when increasing the 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' camera models).


Examples of calculating a size the capacity of the disk subsystem (without size of syslog databasethe capacity of the system log and metadata databases) are presented below.

Recording parameters

Calculating results

4 cameras with 25 fps 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 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 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

...

System log database

The capacity of the system log

...

The size of syslog database is to database should be taken into account when the size capacity of the disk subsystem is calculated. Estimated size of syslog The estimated capacity of the system log database is calculated by the formulas:

The capacity Capacity of the system log database database (low detection tools activity) = D * T * (0.04 GB / day);

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

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

where 

D is is the total nuMBer number of detectors detection tools created in the system,

T is is the estimated duration of syslog system log storage, days.

Metadata database 

The following formulas can help be used to determine the required disk size for the metadata database:

Size of metadata database = N×T× 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.,

where

N equals  is the nuMBer number of video cameras detection tools in the system actively recording metadata. One video camera can have several detection tools with metadata (see General information on metadata),

T is ; T equals the period of time (nuMBer 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  database is overwritten - the new data records is written over the oldest data records.

The system logs

When calculating the disk subsustem capacity, it is necessary to include at least 1 GB for the system logs archive.

Self-diagnostics service

When calculating disk subsystem capacity, please note that self-diagnostics service diagnostics service may generate up to 100 Mbytes of data per day.

The depth of the service 's internal database retention time is limited to 7 days , and its size is limited to 512 MbytesMB.