Glossary
NAS consolidation
NAS consolidation moves file shares from many separate file servers onto fewer systems, often a single scale-out platform. Capacity is a poor guide to the effort. File counts, the permissions attached to each file and the paths people and scripts rely on decide the timeline and what breaks.
How estates end up with a dozen filers
A department buys its own filer, a full one gets a neighbour rather than an upgrade, an acquisition brings another vendor. Some years later there are twelve NAS systems, support ends on several in the same year, and backups stretch across all of them. This is storage sprawl in its file form.
What moves besides the files
| Item | Why it matters |
|---|---|
| Permissions and access control lists | Different filers store them differently, and translation errors surface as denied access after cutover |
| Directory identities | Old user and group identities have to map to the ones the new system recognises |
| Share names and paths | Users, scripts and applications address shares by name; aliases or a namespace layer keep old paths working |
| Timestamps and attributes | Retention, audit and search depend on them |
| Quotas, snapshots and antivirus hooks | Each is configured per filer and has to be recreated, or the share silently loses it |
File count sets the timeline
Copy time follows the number of items, not the terabytes. Every small file costs a metadata lookup, a permission copy and a verification. A share of a hundred million small files, copied at a thousand files a second, needs more than 27 hours for a single pass, while a few large video files of the same total size finish far sooner. Counting files per share before choosing dates is therefore the first planning step, and the small-file shares go early so they do not hold up the end of the project.
Keeping cutover quiet
Data is copied while the source stays live, then repeated delta passes pick up changes. The final pass runs in a short window, names are repointed, and users keep working on the same paths. After every pass, counts, sizes and permissions are compared with the source, so a mapping error is found per share instead of through help-desk tickets.
Typical landing platforms are scale-out NAS or a distributed file system, often with cold data moved on to object storage. Former departmental filers can remain separate tenants on the new system. The block-storage counterpart is SAN consolidation, and the estate-wide view is storage consolidation.
Frequently asked questions
Can NAS consolidation be done without downtime?
Mostly. Copying happens while shares stay live, and the interruption is limited to the final delta pass and repointing names, usually a short maintenance window.
Is NAS consolidation the same as data migration?
It is a migration whose goal is fewer systems, so it also covers retiring hardware, ending support contracts and recreating per-filer settings on the target.