A regional casino with 1,200 slot positions and 40 tables typically runs 1,500 to 2,500 cameras. A Las Vegas Strip property runs past 5,000. Every one of them records continuously, because the gaming regulator requires it and because the property's liability position depends on it. Surveillance is not a security amenity in this business. It is a license condition, and the storage behind it gets audited by people with the authority to close the floor. That makes NAS for casino surveillance an operational requirement rather than an IT preference.
Camera Counts on a Typical Gaming Floor
Coverage requirements are prescriptive. Every table game needs overhead views of the layout, the chip tray, and the dealer's hands. Each bank of slots needs coverage sufficient to identify a patron. Cage, count room, soft count, vault, and every perimeter door get dedicated cameras, and the count room usually gets multiple angles with audio. The camera count comes from regulation, not from preference or budget.
At 4 MP and 15 fps with H.265, a single camera writes roughly 6 to 8 Mbps. Two thousand cameras at 7 Mbps is 14 Gbps of sustained ingest, which works out to about 150 TB per day. Compression tuning moves that figure by a third in either direction, which is why sizing should start from measured bitrates on the existing recorders rather than a vendor calculator.
Gaming Commission Mandates Set the Retention Floor
Retention is jurisdictional. Nevada Regulation 5 and its surveillance standards, New Jersey DGE rules, and tribal compacts under IGRA all specify minimum hold times, commonly 7 to 30 days for general floor coverage and considerably longer for count room and cage activity. Anything under investigation is preserved indefinitely until the investigation releases it.
Thirty days of retention at 150 TB a day is 4.5 PB usable. That figure, not the camera count, is the number the storage design has to answer.
Continuous Recording Leaves No Room for Motion Triggers
Motion-based recording is standard in retail and useless here. A regulator reviewing a dispute expects unbroken coverage of the period in question, and a gap where nothing happened to move is still a gap in the record. Every camera records continuously at full frame rate, which makes the write load flat and predictable while removing the usual lever for reducing capacity.
That predictability is an advantage when specifying hardware. Reading how NAS appliances are deployed for constant-write video workloads shows why sustained throughput and rebuild behavior matter far more than burst benchmark figures.
Pulling an Incident Clip Under a Regulator's Deadline
When a patron dispute is filed, surveillance has hours rather than days to produce clips from several cameras across a defined window, watermarked, hashed, and exported in a format the regulator accepts. Export is a read-heavy operation running against an array simultaneously absorbing 14 Gbps of writes, and it cannot be permitted to drop frames on the recording side.
Sizing for concurrent export therefore deserves its own line item. A system that meets ingest exactly and nothing more will fall over on the first busy Saturday with three open investigations running at once.
Second Copies for Evidence You Cannot Recreate
Once footage is flagged for an investigation it stops being surveillance video and becomes evidence. Those clips belong on a separate, immutable store with its own retention lock, so that a recorder failure or a policy change on the main array cannot reach them.
Most properties already run a backup platform on the enterprise side, and setting up a Veeam repository against a NAS target for the flagged-evidence volume gives them immutability and a documented restore path without introducing a second toolset to learn.
Write Throughput, Not IOPS, Is the Real Constraint
Video recording is large sequential writes. A NAS for casino surveillance gets judged on sustained MB/s while a rebuild is running, not on random read latency. With 22 TB drives, a conventional RAID 6 rebuild across a 4.5 PB array can run for days, and write performance has to stay above the ingest rate the entire time or recorders begin dropping streams.
Erasure coding with distributed rebuild, or a scale-out design that spreads rebuild work across nodes, is the practical answer. Verify that number under load rather than trusting the datasheet.
Keeping the Surveillance Network Isolated
Surveillance VLANs are frequently the softest part of a casino network: cameras shipping with default credentials, recorders on unpatched Windows builds, and vendor remote access nobody tracks. Applying NAS security best practices to the storage tier, with no inbound internet access, separate administrative credentials, and immutable snapshots, limits how far a compromised camera can reach.
Regulators increasingly ask about segmentation directly, and a documented model is easier to present than a verbal assurance.
Giving Auditors and Investigators Controlled Access
Gaming agents, internal audit, and law enforcement all need access at different scopes. Role-based accounts limited to specific camera groups and time ranges, with every view logged, satisfy the requirement without handing out an administrator password. The access log itself becomes part of the compliance record the property presents at its next review.
Scoping matters as much as logging. A NAS for casino surveillance that exposes its entire namespace to any account holding a valid badge number defeats the purpose of role separation, so views and exports should be brokered through the video management system while the underlying shares stay reachable only by the recorders and a small administrative group.
The numbers in this business are unforgiving: thousands of cameras, continuous recording, petabyte-scale retention, and a regulator who can close the floor. Storage earns its place by absorbing a flat multi-gigabit write stream for years, surviving rebuilds without dropping frames, and producing a clean, hashed clip within hours of a request. StoneFly and other vendors build to those numbers, but the specification has to start with the jurisdiction's retention rule and the measured bitrate on the floor.
Top comments (0)