Partitioning a NAS volume into shares for Australian users

When a household in Brisbane or a small business in Adelaide first sets up a network-attached storage device, it usually starts with a single oversized storage pool configured for capacity rather than segmentation. Over time, that one volume becomes a dumping ground for media files, business documents, backups, and surveillance footage, all sharing the same permissions and folder hierarchy. Splitting that monolithic pool into discrete shared folders is one of the most practical housekeeping tasks any NAS owner can perform.

Australian conditions make this task particularly relevant. With the National Broadband Network rolling out across Sydney, Melbourne, and Perth, more households run Plex or Jellyfin from a NAS in the garage. Local retailers stock QNAP and Synology units paired with 4 TB, 8 TB, and 12 TB drives, and a single volume assembled from such a mix can easily run into tens of terabytes — more than enough reason to slice it into logical shares.

The good news is that creating separate shares on an existing volume does not require reformatting the drives, rebuilding the RAID array, or losing data. Both Synology DSM and QNAP QTS allow administrators to carve an already-initialised storage pool into multiple shared folders, each with its own permissions, quota, and access protocols. The process is largely graphical, takes less than an hour, and is fully reversible.

Understanding volumes, pools, and shares on a NAS

A storage pool is the container the operating system sees; it reports a single usable capacity regardless of how the underlying drives are mirrored or striped in RAID. A shared folder is a logical directory that lives inside that pool and is exposed to the network via SMB, AFP, NFS, or WebDAV.

The separation matters because the pool defines how data is protected against drive failure, while the share defines how users and applications access that data. Creating separate shares isolates workloads, applies per-folder quotas, and prevents a buggy application that writes thousands of small files from fragmenting the entire pool.

Preparing your Synology or QNAP for share configuration

A short preparation phase prevents the most common mistakes. Confirm DSM or QTS firmware is up to date, since the share creation interface has changed between major versions. Log into the web interface from a computer on the same subnet — most Australian home networks use 192.168.0.x or 192.168.1.x ranges handed out by the NBN router or a mesh system.

Decide on a naming convention before opening the web interface. Many households and small businesses follow a simple pattern: a short prefix indicating purpose, followed by a year or version, such as media-2024, finance-audit, or family-photos. Record the chosen structure in a text file on a USB stick, and keep names lowercase, dash-separated, and free of spaces to avoid headaches when mapping drives on Windows, configuring Time Machine on macOS, or scripting rsync on Linux.

Creating new shared folders within an existing volume

In Synology DSM, open Control Panel, choose Shared Folder, and click Create. Pick the existing storage pool as the parent, give the folder the agreed name, and choose whether to enable encryption, recycle bin, and file compression. QNAP users follow a parallel path through Control Panel, then Shared Folders, then Create Shared Folder, selecting the volume from a dropdown.

A key decision is whether to encrypt the share. Synology and QNAP both support AES-256 encryption on a per-folder basis, valuable for a Hobart accountant storing client records or a Sydney healthcare practice bound by the Australian Privacy Principles. The trade-off is a small CPU overhead and the need to mount the share manually after each reboot unless the encryption key is stored in the system keychain. For purely media shares such as a Plex library, encryption is usually overkill.

Setting user permissions, quotas, and access controls

With the shares in place, attention turns to who can see them and how much space each user may consume. In Synology, open the Shared Folder panel, select the new folder, and click Permissions. Add individual users or groups such as staff, creative, or backups. For most household shares, ticking Read/Write for the family group and Read-only for guests strikes a sensible balance.

Quota management is where Australian users often save themselves from runaway logs. Synology Storage Manager caps each share at a specific terabyte value, while QNAP's Quota function does the same through Resource Monitor. A common approach is to assign 12 TB to media, 2 TB to documents, 500 GB to cctv-archive, and unlimited space to backups if an external rotation is in place.

Mapping network drives and verifying access

Once permissions are set, the new shares need to be reachable from client devices. On Windows 11, open File Explorer, right-click This PC, choose Map Network Drive, and enter the path in UNC form: \\nas-name\share-name. Tick Reconnect at sign-in if the share should be available after every restart, and supply credentials different from the local Windows account if the NAS is configured that way.

Mac users in Melbourne and Sydney typically see the shares appear automatically in Finder under Network, provided Bonjour is enabled on the NAS. For a more permanent mount, open System Settings, choose General, then Login Items, and add the share to the list.

Linux desktops handle the same task through fstab entries or GNOME Files' Connect to Server dialog, with smb://nas-name/share-name as the address. A short verification routine from each operating system catches misconfigurations that would otherwise surface months later.

Maintaining the structure over time

Partitioning a NAS into shares is not a one-off task. Snapshots, replication jobs, and backup schedules should be revisited whenever a new share is added. Synology's Snapshot Replication and QNAP's Hybrid Mount both work on the share level, so a freshly created cctv-4k folder can be snapshotted every six hours without touching the rest of the volume. The retention policy should reflect how important the data is: a few days for media, weeks for documents, and several months for compliance archives.

Drive failures, capacity upgrades, and migrations also demand attention. When the time comes to expand the array from four 8 TB drives to four 16 TB drives, the share structure remains intact, but the process is faster and safer if the layout is logical. Documenting the structure in a simple spreadsheet listing each share, its purpose, the groups with access, the quota, and the snapshot schedule is invaluable when handing the device to a colleague, a family member, or a managed service provider.

Practical recommendations for a clean share layout

• Plan the folder hierarchy on paper before touching the web interface, and stick to lowercase, dash-separated names.
• Reserve one share per workload: media, documents, backups, surveillance, and a public drop folder.
• Enable AES-256 encryption only on shares containing sensitive personal or financial data, and store the recovery key offline.
• Apply per-share quotas so a runaway log folder cannot fill the entire array.
• Disable AFP, NFS, FTP, and WebDAV on shares that genuinely do not need them.
• Schedule snapshots at the share level with retention that matches the value of the data inside.
• Keep an offline text file describing each share, its permissions, and its quota in case the device needs to be rebuilt from scratch.

The next time the household media library in Brisbane is being reorganised, or a small studio in Fremantle is onboarding a new collaborator, log into the NAS and split the volume into clearly named shares. A well-structured storage pool is easier to back up, easier to secure, and easier to hand over when the time comes. Open DSM or QTS today, sketch the layout, and start carving.