ONSSI Storage And Fail Over Questions

Can someone describe how ONSSI handles fail over? Details in terms of licensing etc.. Does the fail-over server need to have X quantities of camera licenses sitting there on idle?

For example, if I have a system that has 24 cameras all streaming back to a central virtual server – how does ONSSI handle a WAN outage with fail-over functionality? The fail-over server would be on the camera side of the WAN (obviously).

In terms of storage – can ONSSI use a NAS solution as a primary for 1500+ cameras? Or does it need block level read/write capabilities? Would ONSSI use a SAN as a primary and then archive off to a NAS?

Thanks.

Login to read this IPVM discussion.
Why do I need to log in?
IPVM conducts unique testing and research funded by member's payments enabling us to offer the most independent, accurate and in-depth information.

* ******* *** ** ***** ** ******* ** ******.

** ****,

* ** * ********* ******* **** *****.

* *** ****** **** ** **** ******* *********, *** *** specific ******** ****** ****, ***'* **** ** *** **** *** sales *********** **** **** (**** ******* *** ** **** *******) - **** *** *** ****** ******** **** * ** ******* answers ** ******-******* ********* ********* **** ********* *** ******* *** archiving.

** **** ***** *********, ****'* *** * *** ***** *** - ********* ** *** ******. *** ******** ****** '*******' *** original (****) ********* ****** - ** *** ** *** ****** 'sees' **. *.*. ** ***** ****** ********* ** ******** ******* there *** ** '**********' *******. *** ******* **** ***** **** the ******** ********* ****** ******* *** *** **** **** ***** to *** *** **. (** ************ ******* ***** *****)

*'* *** ******* **** **** *** *** ****** ** **** 2nd *********, *** ** ** ***** ******** **** **** ****** lies ********* ******* ***** *** *** *** (******** *******) ** this ******** -->******** **/** ******. :)

*** **** **** *********, ************ ***/** ******* ** * ***, *** ********* *** ********* **** ********(*** *** ******* **** *** ******** ****** *****).

*** *** (** ***** ***) ** ******* **** ******* ** NAS, ***** *** ********** ** *************! (*** ******* *****) :) ...actually, *'* **** ***** *** **** *************. ***'* *** **** my **** ****... **** *****.

* **** ********* * ******* ** *** **** ******* ******* for ***** (*** **** **** *** ******* ** *** *******/********* schemes), *** ** ** *** *****. :(

****** *** *** *********. **** ** ****** *******.

***** *** ***** *** **** ********* ********.

**** *** ** ******** ** ****'* ******** ******** *** *****'* response:

  • *** ******** ******** ***** * ***** ***** ** *** ********* it *** **** ****** ** *******, ** * ******** ***** responding, *** ******** **** ******* ** **** **** **** ********'* responsibilities, ** **** **** ** ** **** ** ****** * network ********** ** *** ******** *******.
  • ******* **** ***** ******** ** * *** ** ********* ********** (as **** ** *** ********** ** *** *** ** ***** and ********), *** ** ************ ***** **** ** **** ***** Installations. *** *** ****** ** **** *** ********* ****.
  • ** ***** *** ******** **/** *********, ** ** *********** *** to ******* ** *** **** ***** ** *** *** **** for **** *********.
    • ***** ** ** **** ** ******* **** (********* ** **** commonly **** **** ***** ** ***** ****** ** ******** *, and **** ***** ** ***** ** ******** * (*** **** term ******* ********).
    • *** ********* ******* *** ** ******** ********* (** * *** database ** ***** **** *** ** *** ******** **** ********); it ** *** **** ****** ********* ** *** *********** ** the ***** ** *** ***** ***** ** * ********* ********.

****** *** ** **** ** *** **** *** ******* *********.

*** ********

****** ***** *** *** ********.

** ** ******** ** *** ******* *********, *** ***** *** enterprise *** ********* **** *** *** *** ** *** ******* storage? ******* ********** ********* ********** ** ****+ *******.

* ***** ***** **** *** *** ********* ***** **** ***** level ****/***** **********.

****,

* ***** **** *** *************** *** ** ******* *******.... *** **** ****** ********** * big *** ******* ***** (****) **** ******** ***% ******* **-**** to *****. *** ********* ** *** ******** *** *** ****** be *********** ************ ******. **** ******** **** **** ** ******** **** **** altogether....

** ****** ***** ** ******** *** ********* **** ******** *** as ******* *******, ****** *****.

****, *** **** ** ***** ******** ********** ******* (** ****** else) ***** ** **** ***** ******** ** *** ** ******* storage? ****** ** **? (*** ** **, *** ** *** do **?)

** ****** ***** ** ******** *** ********* **** ******** *** as ******* *******, ****** *****.

** **** ** ********* **** **** *. ********************** *** *** ***** **, *** *** ***** ******* ****** contentious, **********.

****, *** **** ** ***** ******** ********** *******...

***** ***** ******** **** ** ** ****-******** **********?

****-******** ** ********* ****.... :)

****, ** * ** ******* ****** ******** *** **********, * am ******* *** ******* ******* *** ********* ********** *** ***** used - *** **** ***********, ******* - *** ** *** field.

*'* ******* **** ******** **** *** ** *******, *** *** some ****** **** ******* *** **** ** ****... **** ** only *** ****-******** *********.

*** ***** *** ********** *** *****?

* *** * ******** *** ******* *** ******* * *** for ******* ** * ********** ***** (***** *******) ******* ******. Honestly ** ****** "**", *** ***** **** ********** ***** ****** heavy ****** ******* **** *** ******** *** ******** ***** ***** seem ** ** ********* *** ****. * ***** *** ******** originally *** ** ** *** *** **** ** *** *** cost *** *** * ******; *** ** ********** *** ******** converted **** **** * ****** ******** ******* ***********.