Do camera trigger an offline state accessible with SDK during failover ?

What is the process during failover ?

  1. Manual trigger of Camera1 recording for 15min on main recorder
  2. Loss of connection with main recorder
  3. Failover to failover recording server
  4. In which state is the recording of Camera1 ? Does SDK receive an event on Camera1 ONLINE → OFFLINE
  5. Connection restored with main recorder
  6. fall back on main recorder ?
  7. In which state is the recording of Camera1 ? Does SDK receive an event on Camera1 ONLINE → OFFLINE
  8. End of recording for Camera1 ?

I did not find a clear explanation on this process in documentation or forum, could you help in detailling this process ?

Best regards,

“Server.RecorderFQIDChangedIndication”

https://doc.developer.milestonesys.com/html/index.html?base=miphelp/class_video_o_s_1_1_platform_1_1_messaging_1_1_message_id_1_1_server.html&tree=tree_search.html?search=failover

I did see the other question regarding how to get the failover state from the recorder.

However my question was a bit different :

What is happening at the time of failover for the cameras ?

Do recording actions keep runing during failover ?

This is not really a development question then. The failover recording server will be started and then record the cameras. There will be a gap from the recording server is down until the failover recording server is up.

Please see - https://doc.milestonesys.com/2020r1/en-US/feature_flags/ff_recordingserverfailover/mc_failoverservers.htm?Highlight=failover

Please use the Support Community if you need further information on the failover recording server functionality.

https://supportcommunity.milestonesys.com

Well it is actually both functionning and development question since we have to know if the camera triggers an offline state during the failover process, as this info has to be treated by our software.

Do you have more hints on the subject ?

There will be a short interruption while the fail-over recording server is starting. We strongly recommend to test with failover recording servers and see for yourself.

We did the tests, and when a manual recording is ongoing during failover, the recording is stopped and is does not start again when the failover server is started.

The recording must be manually restarted but we lose the interest of failover.

Are there maybe specific rules to create to keep the manual recordings recording even through failover process ?

When fail-over happens recording on manual request will not be signaled to the fail-over recording server that takes over.

When the fail-over situation is ending recording on manual request will not be signaled to the original recording server that takes over.

The same goes for recording on event or on motion, the recording is only continued in the fail-over recording server if a new event or new motion detection is triggered.

Unfortunately there is no mechanism for handing over that a recording has been initiated.