A single dealership generates a surprising amount of data for a business most people think of as selling cars. Between the DMS, the service department, the camera system, and a filing cabinet's worth of digitized F&I paperwork, one rooftop can produce several terabytes a year. Multiply that by twelve stores and you have a real infrastructure problem, usually landing on an IT team of four.
Dealership IT is not centralized by nature. Stores get acquired, each with its own equipment closet and habits, and the group inherits the mess.
What Each Rooftop Actually Generates
Start with an inventory, because the numbers surprise people. The DMS itself is comparatively small — customer records, repair orders, parts inventory, and accounting entries add up to tens of gigabytes of structured data.
Technician video walkarounds are the growth driver. Multi-point inspection videos, two to four minutes at 1080p, run 150 to 400 MB per repair order. A department turning 40 ROs a day with video on half adds roughly 4 GB daily, over a terabyte a year, per store.
Surveillance dwarfs everything else. Lot cameras, service-bay cameras for liability documentation, and cashier coverage add up to 40 to 80 streams per rooftop. At 4 Mbps with 30-day retention, sixty cameras produce roughly 78 TB. That single line item defines the design.
Retention Is Driven by Warranty and Audit
Dealers do not get to pick retention based on disk cost. Manufacturer warranty audits look back years, and the reimbursement claw-back on a failed audit is real money. Repair orders, parts documentation, and the video proving the work all need to survive that window.
F&I documents carry their own requirements. Credit applications, adverse action notices, and financing disclosures fall under federal lending and privacy rules driving multi-year retention. Surveillance has the shortest window — 30 to 90 days — except for clips pulled for a specific incident, which must be exported before the rolling overwrite consumes them.
Build the policy per data class, not per store. Otherwise every acquisition brings new rules and the group ends up with twelve answers to the same audit question.
Thin IT Staffing Changes the Constraints
Most rooftops have no dedicated IT person. There is a service manager who knows how to reboot the recorder and a sales manager with the server room key. Anything requiring regular local hands will fail eventually.
That pushes the architecture toward equipment that runs unattended: redundant power and drives, remote management over the store's existing circuit, and monitoring that alerts corporate before something becomes an outage. Well-chosen network storage solutions for distributed retail should be deployable by a technician following a checklist, then managed entirely from headquarters.
Standardize the build. Same model, same configuration, same share names at every rooftop means a problem diagnosed at store three is already solved at store nine.
Edge Storage at the Rooftop, Replication to the Hub
The practical pattern for multi-site network storage solutions is an edge appliance at each store handling local writes, with policy-driven replication back to a central hub. Cameras and workstations write at LAN speed, so a WAN outage does not stop the service department or drop surveillance recording.
What replicates back is a deliberate subset. Repair orders, F&I documents, technician video, and incident-flagged camera clips go to the hub. Routine surveillance footage stays local and ages out, because replicating 78 TB per store centrally is neither necessary nor affordable.
A properly sized NAS system at the edge also gives you a local backup target for the DMS database and store file shares, which shortens recovery when a server dies. Restoring over the LAN beats pulling from a cloud repository across a retail circuit.
Retail Circuits Are the Real Bottleneck
Dealership internet is usually business cable or a modest fiber circuit, and the upload side is where it hurts. A store on 100/20 Mbps has roughly 200 GB per day of theoretical upload, and you will not get all of it because the DMS, credit bureau lookups, and manufacturer portals compete during business hours.
Schedule replication overnight and rate-limit during the day. Use change-block or deduplicated transfer so unchanged data is not resent, and compress in flight. When a store is genuinely too constrained, seed the initial sync by shipping a drive rather than pushing the first full copy over the wire.
Monitor replication lag as a first-class metric. If store seven has been 11 days behind for a month, you have no backup for store seven.
Consolidating After an Acquisition
Every acquired store arrives with something unexpected: an unsupported appliance from a decade ago, a surveillance recorder nobody has the password to, or a share full of scanned deals with no naming convention.
Work in order. Inventory what exists and which data classes live where. Get the legally required data copied somewhere trustworthy before touching anything else. Then migrate the store to the standard build and decommission the old gear rather than leaving it running "just in case," which is how forgotten systems become breach entry points.
When sizing the group's central hub, it is worth reviewing the trade-offs of SAN vs NAS vs DAS — file-level sharing suits document and video workloads, while a block target may fit a consolidated DMS database better.
Customer PII Deserves More Attention Than It Gets
Dealerships hold an unusually rich set of personal data: driver's licenses, Social Security numbers on credit applications, bank details, and complete vehicle histories. Regulators have noticed. The FTC Safeguards Rule brought dealers under a written information security program requirement with access controls, encryption, and monitoring obligations.
Encrypt at rest on every appliance and in transit on every replication stream. Restrict share access by role so the parts department cannot browse F&I documents. Keep immutable copies of critical data so a ransomware event at one rooftop cannot reach the group's only backup, and actually review the access logs you collect.
The Bottom Line
Dealership groups do not fail at storage because the technology is hard. They fail because each rooftop was solved independently and nobody owns the whole picture. Inventory what every store produces, set retention by data class against warranty and lending requirements, put standardized network storage solutions at each location, and replicate only what genuinely needs to leave the building. Do that consistently and adding the thirteenth store becomes a checklist item instead of another custom project.
Top comments (0)