NAS

How it works

The NAS holds the bytes. The protocol is the share. A transfer off the NAS to a client in another city is a separate copy. RAID inside the NAS is not a backup and not a transfer.

A studio keeps projects on a NAS. A client delivery still uploads 15 GB to a bucket because the client cannot mount the NAS. The NAS copy is the working set. The bucket copy is the delivery.

How it differs

NAS is not object storage. You edit in place. You do not presign a NAS path for a stranger without a VPN.

A full NAS fails writes that cloud quotas would also fail. Watch free space.

A share is not an offsite copy.

On the ticket

• The practical close is a log line: time, actor, byte count, result.
• Without that line the transfer is a story.
• With it, the next person can see whether this door did what the ticket claimed.
• If the path is shared, say so in the partner profile so a later change does not silently pick a different limit, key, or region.
• On a real ticket, write down the door, the byte count, and the clock.
• For nas, that means naming the host or bucket, the expected size, and the time the other side must have a complete file.
• A progress bar is not that record.
• A 200 response that arrives before the complete call is not that record.
• If a retry is allowed, say how many and whether it resumes.
• If a person must approve the send, name the person.
• Partners who receive nas files should match on hash or size before they import.
• A same-length corrupt file passes a size check and fails a hash.
• Keep the published hash off the only channel an attacker can edit, or treat it as a corruption check rather than a substitution check.
• When the path changes, new key, new region, new cap, update the profile the same day so the next run does not use a stale limit.