Page History

...

• Server and Client: choose this type of installation if you have no more than 5 Servers in one location, which should must operate within the same Axxon-domain.
• Failover Server and Client: choose this type of installation if you have 5 to 30 Servers (minimum 3) in one location, which should must operate within the same Axxon-domain.

...

1. Use the port range 20111-20210 (see Network settings utility, Ports used by the Axxon One Software Package).
2. Metadata database:
   
   1. The path to the metadata storage folder can be specified only once during the installation process. If you decide to change it later, you will have to re-install Axxon One (without losing your configuration or video archive).
   2. It is highly recommended to install it on SSD specifically designed for storing metadata.
      Do not install metadata on system drive because Metadata size tends to grow over time, and if the system drive space is not sufficient it might cause system issues.
      Do not install metadata on the drive to which the archive is recorded because it will affect recording performance.
   3. Consider the disk space required for the database (see Disk storage subsystem requirements). For example, ≈1.5 TB is required to store metadata for 30 days for 50 cameras.

...

1. Connect the cameras to the Servers.
2. Synchronize the time of all Servers and cameras with a single NTP Server.
3. Add the cameras to the system (see Searching, adding, configuring and removing IP devices, Bulk creation of IP devices). Preferred protocol: ONVIF generic.

4. Multistreaming:

   1. Set different high and low quality streams for each video camera.

   2. Low quality stream settings should must be lower than the High the High quality stream.
   3. Enable GreenStream in the camera context menu on the layout (see Selecting video stream quality in a Surveillance window (GreenStream)) or in the layout settings (see Selecting the default video stream for all cameras on the layout).
5. Codec type*: H.265 or H.264 is recommended. If you plan to use the Web Client, then H.264 is recommended since using H.265 leads to the stream recompression on the Server side.
6. FPS: the Low quality stream frame rate should must be at least 6 to ensure the correct operation of the detection tools.
7. Resolution:
   1. Aspect ratio should must be the same for Low and High for Low and High quality streams*.
   2. The Low quality stream quality stream resolution should must be no less than 640x360 and no more than 1280x720 to ensure the correct operation of the detection tools.
8. Bitrate: 

   1. Recommended type*: VBR.

   2. Set maximum bitrate/bandwidth values.

   3. Recommended bitrate: 1 Mbps per 1 MP.

9. GOV (also known as GOP, I Frame, etc.): it is recommended to have at least one keyframe per 2 seconds. 
   
   *May differ for different camera models.

...

1. Link each camera to at least one archive.
2. Configure recording to the archive (permanent or triggered started by events from detection tools) for each camera.

3. Make sure pre-recording is enabled (> 1 sec).

4. Note that after you re-create the archive, it is necessary to re-create all recording rules in the detection tool settings or Programming settings.

...

1. The motion detection tool should must operate on a low quality stream (see Configuring the Motion detection).
2. Using masksTo mask, exclude the areas of the frame which constantly trigger that constantly have motion detection (for example, on-screen display (OSD) or TV).
3. Create automatic rules for recording to the archive (see Automatic rules).
4. Use a NVIDIA GPU for the detection tools operation if there is one.

...

1. Create and configure an email notification (see The Email notifier object).
2. Configure a cyclic macro command (once a day) to check if all cameras are recording (see Checking archive record, Cyclical Cycle macros).
3. Configure event macros based on statistical data (CPU load, free disk space, see Starting macros by statistical data).

...