Which SAN expansion methods keep recording uninterrupted?
The methods that keep recording uninterrupted are those performed online: adding disk shelves to a running array, creating new LUNs or volumes from the added capacity, and attaching them to recording servers as extra archive locations. Each avoids taking the existing volumes offline.
The right approach depends on the array and the VMS architecture. In practice, integrators usually choose between three options:
- Adding a new volume as an additional archive: Capacity is carved out as a new LUN and presented to the recording server, which then writes to it alongside or after existing storage. This is generally the lowest-risk option because existing volumes are untouched.
- Growing an existing volume or RAID group online: Some enterprise arrays can extend a volume or add drives to a pool while it remains mounted. This keeps a single contiguous archive, but rebuilds and restriping increase load on the array and can reduce sustained write headroom while they run.
- Adding a second storage node or recording server: Rather than enlarging one array, capacity is scaled out by adding another unit and distributing cameras across it. This isolates risk and adds write bandwidth as well as capacity.
Whether a specific array supports online volume growth varies by vendor and model, so confirm this in the manufacturer’s documentation before relying on it. Adding capacity is not the same as adding performance, so check that controllers, network links and the recording server can handle the new total load.
What causes recording gaps during SAN expansion?
Recording gaps during SAN expansion are usually caused by interrupted storage paths, saturated array controllers, volumes taken offline for resizing, or recording servers losing access to the archive while the VMS rescans or remounts storage. Most are avoidable with planning.
The most common causes include:
- Path disruption: Changing switch, HBA or iSCSI configuration can drop connections briefly. Without multipath configured and tested, even a short interruption can stall writes.
- Controller or disk contention: Initialising new drives, rebuilding RAID or restriping a pool competes with live video writes. Continuous sequential video from many cameras leaves little spare write headroom on an already busy array.
- Volume offline operations: Some file systems or older arrays need a volume to be unmounted to be resized, which stops recording to that location.
- VMS service restarts: If the VMS needs a recording service restart to recognise new storage, cameras without sufficient edge buffering will lose footage during the restart.
- Configuration errors: Incorrect LUN masking, wrong file system settings or mismatched block sizes can cause write failures once the new volume is added.
Because redundancy does not automatically guarantee uninterrupted recording, each of these should be treated as a specific risk to design out, not assumed away.
How does the VMS handle new storage while recording?
Most modern video management systems can accept new storage while recording, typically by letting administrators add an archive or storage location and assign cameras or retention tiers to it. Whether this needs a service restart varies by platform, so verify behaviour for your VMS and version.
Typically, the VMS sees the SAN volume as a drive or mount point on the recording server. Once the operating system presents the new volume, the administrator adds it as a storage location, and recording can be directed to it. Many platforms also support tiered or rolling archives, so older footage moves to the new capacity while live recording continues on faster storage.
Points to check with your VMS vendor include:
- Whether adding storage requires a recording service restart
- How retention settings apply across multiple archive locations
- How the system behaves if a storage location becomes unavailable
- Whether existing footage remains searchable and playable from the original volumes
Secure Logiq builds servers that are tested and certified for leading VMS platforms, which helps reduce surprises when storage configuration changes. For guidance on matching hardware to recording requirements, see the server selection knowledge base.
How much extra capacity should be planned before expanding?
Plan expansion capacity from required retention time, camera bitrate and expected growth, then add a margin so the array is never expanded while nearly full. Expanding at a comfortable utilisation level gives time to complete the work without pressure on recording.
A practical sizing approach starts with the bitrate of each camera, multiplied by the number of cameras and the retention period in days, then adjusted for compression, motion-based recording and any metadata from analytics. Because this is a calculation rather than a fixed rule, state your assumptions clearly, such as codec, frame rate, scene complexity and recording mode.
Beyond raw retention, allow for:
- Growth in camera count and resolution: Camera upgrades often raise bitrate significantly.
- Analytics metadata: AI-enabled deployments generate additional data that needs storage.
- RAID overhead and spares: Usable capacity is lower than raw capacity once parity and hot spares are accounted for.
- Operational headroom: Do not run volumes close to full, since performance and rebuild times can suffer.
Treat any figures as design estimates to validate. Secure Logiq’s system design service includes bandwidth and storage calculations, which help turn assumptions into a documented specification.
What steps reduce risk when expanding a live SAN?
Reduce risk by confirming the expansion method with the vendor, verifying backups of configuration, scheduling work during low-activity periods, and testing on a non-critical volume first. Keep a rollback path and monitor recording health throughout.
A sensible sequence for a live expansion is:
- Review documentation: Confirm that the array, firmware, file system and VMS all support the intended online operation.
- Back up configuration: Export array, switch and VMS settings so you can restore them if needed. Remember that RAID is not a backup, so protect critical footage separately where required.
- Check current health: Resolve degraded arrays, failed drives, path errors and capacity alerts before adding anything new.
- Assess performance headroom: Confirm controllers, links and the recording server can sustain live writes during the change.
- Schedule carefully: Choose a period of lower camera activity and avoid running other heavy tasks such as exports or rebuilds.
- Expand in stages: Add capacity incrementally, validating each step before moving on.
- Monitor continuously: Watch for dropped frames, write latency and gaps in the recording timeline during and after the change.
- Verify afterwards: Confirm footage is being written to the new capacity and that playback works across old and new volumes.
For complex multi-site or high-density environments, working through the plan with a specialist before touching live infrastructure is worthwhile. The Qatar University SAN storage case study illustrates how large-scale storage can be designed around real requirements.
If you are planning a SAN expansion and want to protect recording continuity, contact the Secure Logiq team to discuss your storage requirements and expansion approach.
Frequently Asked Questions
How do I get started if I've never expanded a live surveillance SAN before?
Start with an audit of your current setup: array model and firmware, file system, VMS version, current utilisation and any existing array health alerts. Then read the vendor documentation for the specific online expansion method you intend to use, and rehearse the process on a non-critical volume or a lab system if possible. Adding a new LUN as an additional archive location is usually the safest first step because existing volumes are left untouched.
What should I do if recording stops or gaps appear mid-expansion?
Pause the change immediately and check the recording timeline, VMS storage status and array alerts to identify whether the cause is a path drop, controller contention or an unavailable volume. If you have a rollback plan, revert the last step rather than pushing forward, and restore the configuration backups you exported beforehand if needed. Once recording is stable, review the logs to find the root cause before resuming in smaller stages.
Can edge storage on cameras protect me from gaps during a SAN change?
Yes, in many deployments. Cameras with onboard SD or edge storage can buffer footage locally during a short outage and, on platforms that support it, backfill the recorder once the connection returns. Check that your camera model and VMS both support automatic retrieval, confirm the buffer size covers your planned maintenance window, and test it beforehand rather than assuming it works.
Do I need multipath configured before I expand, and how do I test it?
It is strongly recommended, especially if the expansion involves any switch, HBA or iSCSI changes. Verify that both paths are active and healthy, then during a quiet period disable one path and confirm that recording continues without errors before re-enabling it and repeating for the other. Only proceed with the expansion once failover has been proven under live conditions.
Will adding more capacity also improve recording performance?
Not necessarily. More disks can add some throughput, but controllers, network links, HBAs and the recording server can still be bottlenecks. Compare your total camera bitrate, including future growth and analytics metadata, against the sustained write capability of the whole chain. If writes are already close to the limit, scaling out with an additional storage node or recording server is often a better choice than enlarging one array.
How can I check that old and new footage remain searchable after expansion?
Before and after the change, pick several cameras and test playback from dates stored on the original volumes as well as from recordings written to the new capacity. Also check that exports work from both locations and that retention settings behave as expected across the archive locations. Document the results so you have a baseline for future expansions.
What are the most common mistakes to avoid when expanding surveillance storage?
The most frequent mistakes are waiting until the array is nearly full, expanding while a rebuild or degraded drive is already in progress, and skipping configuration backups. Others include assuming the VMS will accept new storage without a restart, misconfiguring LUN masking or block sizes, and treating RAID as a substitute for a backup of critical footage. Planning headroom, validating each stage and monitoring throughout avoids most of these issues.