Endura Continious and Alarm recording.

[Kly]

Hi.

We faced such a problem. Our customer wants to use Continious recording in Endura system for first 7 days, but Alarm Records should be kept for 30 days for the same cameras.

The question is how to realize this. We cannot delete just continious records avter 7 days. And we cannot record Continious schedule and Alarm Schedule in different pools.

What is you suggestion?

[sesa137169]

Hi Sergij,

They should use two storage pools with different recording schedules:

• the first pool woll recoed continuously for 7 days
• the second pool should record by alarms for 30 days

In addition - multicast recording should be used.

[Kly]

Hi, Plamen. We haven`t used Multicast recording yet. I thought about that solution.

If we use unicast recording and asign cameras to one pool, we cannot asign cameras to another pool.

I hope in case of multicast recording we will be able to asign cameras to two different pools.

[sesa137169]

Hi Sergij,

The latest firmware of the NSM allows you to do redundant recording (recording the same cameras on different pools). It has to be checked if unicast or unicast - but we support now redundant recording. I will try to find some info on this.

[Kly]

Does redundant recording allow to use different schedules for different pools? i doubt about that.

[sesa137169]

I will check.

[sesa137169 · Accepted solution]

Hi Sergij,

Please, see the release notes of NSM5200 version 2.2.0.0856:

Features and Enhancements 

1. Added SNMP health monitoring messages and trap support for input air temperature, hard disk drive status, system fan status, CPU fan status, CPU load, memory load, etc. Users who had received pre-release MIBS are required to repeat the integration with updated MIBS available from www.pelco.com.
2. Added support for mulcaticast recording, allowing the system to record the same multicast stream used for live view to conserve network bandwidth between the camera and the recorder. Unicast recording is still the default configuration.
3. Added support for redundant recording, allowing the same camera(s) to be recorded on two different storage pools. Each pool can have its own independent schedule. The Endura viewing devices will query the primary pool for Quicksearch and both pools for enhanced search results.
4. Added support for NSM failover on demand. In situations where storage pooling may not be an option, failover on demand allows one NSM5200 pool to monitor any number of NSM5200s setup as individual recorders. Should one of them fail, the monitoring pool assumes the responsibility of recording the impacted cameras. NSM failover on demand can work across network subnets.
5. Added support for Unicode naming of schedules.
6. RTSP server is now part of the unit’s image to aid in integrating Endura into a 3rd party access control or other system.
7. Improved the algorithm that is used to refresh cameras on the web configuration application to speed up how quickly cameras are displayed.

See point 2 and 3. For position 3 is said that the redundant recording allows you to record cameras on two different pools, which means that you can use different schedules on each pool (this is a native Endura functionality). It is using multicast streams. Find attached the release notes for version 2.3.1.0259. It is written there that the redundant recording allows you to use different schedules on each pool. Use the latest NSM firmware version!

Best regards,

[sesa210359]

Please note, the NSM5200 software referenced is Version 2.3.1.0259.  This is the latest release as of May, 2013.

[Kly]

I have a great idea to solve our problem, but it needs some improvements in Endura System.

Endura Settings have such parameters. Delete Scheduled Video in _____days and Delete blocked video in ____ days.

So if Endura system obtains a setting which can allow automatically block alarm video, we will be able to solve the problem.

We will be able to create two schedules for one pool, one for Continious recording and one for Alarms Recording. Continious records will be deleted in 7 days but automatically blocked alarms will be deleted in 30 days.

So we do not need Redundant pools.

Endura already has the possibility to block video manually but it cannot block video automatically. So the question is whether it`s possible to add such feature.

[sesa137169]

Hi Sergij,

The automatic video lock (blocking) could be achieved also using the Pelco SDK.

Best regards,