Skip to content

Dear customers! Please send orders and inquiries to [email protected] or to Telegram @servix_uz instead of calling by phone: due to the high workload, the operator cannot answer all incoming calls.

Servix

Video surveillance server in Tashkent: archive calculation, drives and ready-made configurations

Updated

In brief. A video surveillance server is sized not by the number of cameras but by archive volume: sixteen 4 MP cameras streaming 4 Mbps for thirty days produce 19.8 TB of raw data, thirty-two produce 39.6 TB, sixty-four cameras at 6 Mbps produce 118.7 TB. Everything else follows from this: an LFF drive cage for 3.5-inch drives, RAID 6 instead of RAID 5, enterprise drives instead of desktop ones. A ready-made kit for sixteen cameras is 42,560,938 UZS, for thirty-two 86,180,174 UZS, for a hundred — price on request.

Request a video surveillance server calculation → — send us the number of cameras, resolution and required archive depth, and an engineer will calculate the volume and select the drive cage and drives.

Quick links: how to calculate archive volume · drive cage and drive form factor · which drives to install · RAID and headroom · servers from the catalog · ready-made kits · camera network and power

How to calculate archive volume

The formula is simple: camera bitrate × number of cameras × retention time. Everything else is details that refine this figure. Bitrate guidelines for H.265 encoding: 2 MP camera — 2–⁠3 Mbps, 4 MP — 4–⁠6 Mbps, 8 MP (4K) — 8–⁠12 Mbps. The lower bound is a static scene, the upper is a street with movement and night illumination.

Site

Stream

Archive depth

Raw capacity

With headroom and RAID 6

16 cameras, 4 MP

4 Mbps

30 days

19.8 TB

about 24.7 TB usable

32 cameras, 4 MP

4 Mbps

30 days

39.6 TB

about 49.4 TB usable

64 cameras, 4–⁠8 MP

6 Mbps

30 days

118.7 TB

about 148.3 TB usable

A 20–⁠25% headroom is planned not “just in case” but for three real things: bitrate growth in bad weather and night recording, cameras added during the year, and the fact that an array filled beyond 80% degrades in write speed. If motion-detection recording is enabled, the volume drops, but planning should still be based on continuous recording — detection turns off at the worst possible moment.

Drive cage: why LFF, not SFF

Video surveillance means terabytes with a modest load in operations per second. So the drive cage is chosen for 3.5-inch (LFF) drives: they take drives of 8–⁠22 TB, whereas 2.5-inch (SFF) bays take at most 2.4 TB on spinning disks. The difference in cost per terabyte is several-fold.

The number of bays sets the archive ceiling, and the drive cage cannot be changed after purchase: the backplane type is fixed when the chassis is ordered. A practical guideline: 4 LFF bays — up to 16–⁠20 cameras, 8 bays — up to 40–⁠50, 12 bays — up to 100 with a one-month archive depth.

Which drives to install

Video recording is continuous sequential writing 24 hours a day. This mode kills desktop drives within a year: their endurance is rated for 2,400 hours of operation per year, not 8,760.

  • Enterprise SAS and SATA 7.2k. The workable option: WD Ultrastar 8 TB SAS — 3,234,705 UZS, WD Ultrastar 16 TB SAS — 5,031,764 UZS, WD Ultrastar 22 TB SAS — 8,625,882 UZS and the 22 TB SATA version — 6,469,411 UZS. Designed for round-the-clock operation and an annual workload of hundreds of terabytes written.
  • NAS drives such as WD Red Plus 10 TB (price on request) are suitable for a small system with four to eight cameras in an office, but their annual write limit is about 180 TB, and on a busy system it is used up within a few months.
  • SSDs are not used for the archive. The price per terabyte is several times higher, and the latency advantage is not needed for video recording: the stream is sequential. An SSD is justified only for the operating system and the video server's metadata database.

A full review of drive classes with price per terabyte is in the selection drives and RAID controllers.

RAID, hot spare and why not RAID 5

RAID 5 is not used on drives of 8 TB and up: the rebuild takes more than a day, and a second drive failure in that window destroys the entire archive. The standard for video surveillance is RAID 6 with two parity drives plus a hot spare if the bays allow.

  • The controller must have a cache with battery protection: HPE Smart Array P408i-a — 7,188,235 UZS or Dell PERC H755 with battery — 8,625,882 UZS. Without cache, write performance in RAID 6 collapses.
  • For dense drive cages with 12 or more drives, a controller with 16 internal lanes is used — HPE Smart Array P816i-a (price on request).
  • The system is put on separate drives or a boot module so as not to waste cage bays: Dell BOSS (7,907,058 UZS) or HPE NS204i-p (10,063,529 UZS).

A detailed review of RAID levels is in the guide RAID 5, 6 or 10.

Servers from the catalog for video surveillance

Small site, up to 16–⁠20 cameras — a tower or 1U with four LFF bays:

Medium site, 30–⁠50 cameras — eight LFF bays:

Large site, 60–⁠120 cameras — twelve LFF bays:

When the archive outgrows one server, capacity is moved to a separate array — see the selections HPE MSA storage and Dell PowerVault ME5: they expand with shelves and survive a controller failure.

Ready-made kits with prices

The amounts do not include video management system licenses, a UPS or installation. Licenses are counted by the number of cameras, and each vendor has its own — they are budgeted as a separate line.

Camera network and power

The server is only half of the project. The other half is how the cameras reach it.

  • PoE switches. A dome camera draws 6–⁠12 W, a PTZ camera with a heater up to 25–⁠30 W. The PoE budget is calculated by total power, not by port count: twenty cameras at 9 W each is 180 W, and a model with a 195 W budget barely fits. Models and prices are in the selection Aruba Instant On.
  • Bandwidth. Thirty-two cameras at 4 Mbps is 128 Mbps of constant traffic toward the server. A gigabit uplink is enough, but the recording server is better connected through a separate port or an aggregated pair so that the stream does not share the link with the office.
  • Power. Both the server and the switches need a UPS: if a switch loses power, the cameras do not record even while the server is running. Sizing for the room is in the checklist server room in an office.

What to clarify before ordering

  • The number of cameras, actual resolution and bitrate (taken from the recorder settings or the camera datasheet), and the required archive depth in days.
  • Continuous or motion-triggered recording: the volume differs several-fold depending on this.
  • Which video management system is used and what its requirements are for the OS, drives and licenses.
  • How many bays are needed now and how many for growth: the drive cage cannot be changed after purchase.
  • Whether power redundancy is needed — two power supplies in the server and a UPS for the switches.

We will calculate the archive volume and build a configuration for your system — write to us. Platforms are in the section Servers, drives are here.

Sources

Other Servix collections

Installation and support — KP Solutions

Installation, setup and maintenance of equipment — from our integrator partner.

kpsolutions.uz