Configuring Network Attached Storage (NAS) for Simultaneous Multi-Animator Access

Start With the Workflow, Not the NAS Model

A common mistake is choosing storage based almost entirely on capacity: “We need 40 TB, so we need a 40 TB NAS.” Capacity is only one part of the problem.

For simultaneous access, three questions matter just as much:

• How many people may actively read or write files at the same time?
• What type of data are they moving?
• Do those artists need shared storage for source assets, active project files, caches, renders, or all four?

Opening a collection of small rig files is a different workload from streaming multiple high-resolution image sequences. Copying a finished render is different from thousands of small reads generated while an application resolves dependencies.

A Practical Studio Network Layout

For an in-office team, the simplest reliable design is usually a dedicated wired path between production workstations and the storage system.

This layout is deliberately boring. That is a good thing. Shared production storage should be predictable.

Wi-Fi can be convenient for review laptops and lightweight access, but an artist’s active workstation is easier to diagnose when its main production path is wired. Wireless performance can change with distance, interference and competing clients, making a storage issue look like an application issue.

Do Not Size the Network From a Single Speed Test

Ethernet ratings describe raw link capacity. They do not guarantee that a NAS will deliver that throughput. Protocol overhead, disk performance, CPU load, file size and concurrent activity all reduce what an application ultimately sees.

*These values are mathematical link-rate ceilings: bit rate divided by eight. They are not promised NAS transfer speeds.

Use This Planner Before Buying Network Hardware

The calculator below is intentionally simple. It creates a planning baseline from three assumptions: how many users are active at once, the throughput you want to budget for each active user, and how much extra capacity you want to leave for bursts.

The NAS Is Only as Fast as Its Slowest Important Layer

A 10 GbE port does not turn a slow storage pool into a 10 GbE storage system.

Think of the path as a chain:

If any stage cannot keep up, upgrading a different stage may produce little improvement.

That is why a useful pre-deployment test includes both large sequential transfers and the actual project workload. Animation projects often mix large video or image sequences with many smaller scene, texture, proxy and metadata files.

Separate Shared Production Data From Local Scratch Data

Not every file generated by an artist belongs on shared storage.

Temporary caches can generate enormous amounts of short-lived I/O. If every workstation writes all application cache data to the NAS, useful production traffic may have to compete with disposable files.

Build a Folder Structure People Can Understand at 2 A.M.

A technically perfect NAS still fails as a production tool if nobody knows which file is authoritative.

For a small studio, a predictable structure is often more useful than dozens of clever folders.

The exact names are not important. Consistency is.

Do not allow every artist to invent a different location for textures, approved rigs or final scenes. Paths become dependencies in many creative applications, and moving assets casually can break projects long after the original artist has forgotten why the folder existed.

A NAS Does Not Automatically Make a File Multi-User Safe

A NAS can let twenty users see the same file. That does not mean the application supports twenty people editing that file at once.

Some applications implement project locking, databases, collaboration layers or their own asset-management systems. Others expect a project file to have a single active editor.

If the software does not explicitly support concurrent editing, create a studio rule that assigns ownership of an active shot or scene.

For example:

• AVAILABLE — nobody is actively editing the shot;
• IN PROGRESS — MAYA — Maya owns the active working scene;
• REVIEW — the current version is ready for review;
• APPROVED — changes require a new revision.

This can be managed through production software, a tracker, or even a disciplined naming system in a very small team.

The goal is simple: prevent two people from saving different versions over the same authoritative file.

Use Accounts and Groups Instead of One Shared Password

Every artist should have an identifiable account. Permissions should then be assigned through roles or groups wherever possible.

This is only an example. The correct permissions depend on the pipeline, but the principle remains useful: a render node does not need administrative rights simply because it needs to write frames.

Limiting access also reduces the damage caused by an accidental deletion or compromised workstation.

When SMB Multichannel Is Worth Investigating

SMB is widely used for file sharing between NAS systems and Windows or macOS workstations.

SMB Multichannel can use multiple network connections between a compatible client and server. Microsoft documents it as a feature for increasing throughput and providing network fault tolerance when multiple suitable paths are available.

Microsoft also notes that SMB Multichannel is enabled by default in supported Windows configurations rather than being something that should automatically be forced on every network.

On macOS, Apple states that SMB Multichannel has been enabled with default settings since macOS Big Sur 11.3. Apple also notes an important detail: for macOS to use multiple interfaces simultaneously for higher throughput, those interfaces need matching enabled speeds.

Snapshots Solve a Different Problem From Backups

In animation production, accidental changes may be more common than complete NAS failure.

An artist may overwrite a scene, remove an asset directory or discover that yesterday’s approved rig was better than today’s revision. Frequent snapshots can make that kind of recovery much faster.

Current TrueNAS documentation, for example, supports exposing eligible ZFS snapshots to SMB users as previous versions. Synology also provides file recovery from snapshots for supported storage configurations.

But a snapshot stored on the same system should not be treated as the studio’s only backup.

CISA’s ransomware guidance recommends maintaining offline, encrypted backups of critical data and regularly testing their integrity and restoration process. That is a stronger protection strategy than assuming the production NAS can protect itself from every possible failure or compromise.

A Sensible Production Protection Cycle

Test the NAS Like a Studio, Not Like a Hardware Reviewer

A giant sequential file copy can tell you something about maximum transfer performance, but it does not reproduce a production morning.

Before relying on the NAS for a deadline, create a short workload test involving several machines at the same time.

Watch more than the transfer-speed number. Look for pauses when saving, delayed directory listings, dropped mounts, applications waiting on assets, unexpectedly high NAS CPU use and latency spikes when several people become active together.

Do Not Upgrade Everything at Once When Performance Is Poor

If artists complain that the NAS is slow, isolate the bottleneck before purchasing hardware.

What a Good Small-Studio NAS Setup Actually Feels Like

The best shared-storage system is not the one with the most impressive specification sheet. It is the one artists stop thinking about.

A scene opens from the expected location. Textures resolve. A render arrives where compositing expects it. An animator cannot accidentally rewrite the delivery folder. A deleted file can be recovered. A machine failure does not reveal that the only copy of a project lived on someone’s desktop.

That reliability comes from treating the NAS as part of the production pipeline rather than as a large external hard drive with an Ethernet port.