Turning a friend's NAS into your offsite backup target

For Australians living in a country where the nearest major data centre can sit thousands of kilometres away and summer delivers both bushfire risk and tropical cyclones to different coasts, keeping a second copy of irreplaceable files outside the home is more than a nice-to-have. Photographs from a Nullarbor road trip, the books of a small Adelaide consultancy, or a videographer's raw footage shot in the Blue Mountains can vanish in a single flood or house fire. A friend's spare NAS sitting in another city offers a surprisingly practical alternative to paying for commercial remote storage, especially when both households already own gear from Synology or QNAP.

The concept is straightforward: replicate selected folders from your own NAS to a unit located at a friend's place, ideally in a different suburb, city, or on the other side of the country. Because the data travels over their home internet, the cost stays close to zero and the latency depends on whichever NBN plan each household subscribes to. What changes compared with plugging in a USB drive is the layer of network plumbing, security, and storage discipline needed to keep that replica current without accidentally exposing private files to the wider internet.

A second copy stored at someone else's address is also a quiet but effective hedge against ransomware, accidental deletion, and the kind of silent drive failure that takes both a primary and a mirror down at the same time. The rest of this guide walks through the practical steps Australians need to set the arrangement up properly, from picking the right replication method to understanding how the Privacy Act 1988 affects what you can legally send to a third party.

Why an offsite NAS beats cloud-only in Australia

Commercial cloud storage works well for many households in Sydney and Melbourne, but it falls short once the dataset grows beyond a few hundred gigabytes. Uploading a full family photo library or a videographer's working folder over a 50 Mbps NBN connection can take days, and monthly fees on Australian retail plans climb quickly once you cross the free tier. A friend's idle NAS gives you terabytes of capacity for the price of an extra power adaptor and a longer Ethernet cable.

There is also a sovereignty angle. Australian businesses handling personal information are bound by the Notifiable Data Breaches scheme, and many creators are rightly cautious about pushing client work to offshore servers. A replica stored on a unit sitting in a friend's Brisbane garage stays on Australian soil, governed by familiar privacy law rather than the terms of an overseas provider. Combined with the speed of a local gigabit LAN when you need to restore large folders, the offsite-NAS approach trades a small amount of convenience for a meaningful gain in control.

Preparing the friend's NAS for incoming replicas

Before any data leaves your home network, the remote unit needs a basic hardening pass. Create a dedicated user account rather than reusing the administrator login, and give that account permission to write only into a single shared folder. Disable any services you do not intend to use, such as FTP or older media modules that occasionally surface vulnerabilities, and make sure the firmware is current. Both Synology's DSM and QNAP's QTS release security patches regularly, and an unattended box in someone's spare room should be set to install them automatically after a sensible quiet period.

Capacity planning matters too. A good rule is to reserve at least 1.3 times the size of the dataset you intend to replicate, so that snapshots, versioning, and the friend household's own files do not compete for the same gigabytes. If your archive is 4 TB today and growing, the receiving NAS should have at least 5 TB of free space after RAID overhead. This is also a good moment to review the underlying redundancy scheme, and a clear-eyed look at SHR versus traditional RAID will help you settle on a layout that survives a single drive failure without doubling the storage bill.

Network setup: VPN, static IP, and NBN realities

Reaching a NAS in another suburb over the public internet requires either a static IP address or a dynamic DNS service, and ideally both. Most Australian NBN providers issue a dynamic address by default, so registering a hostname through Synology's DDNS, QNAP's myQNAPcloud, or a third-party service keeps the remote location reachable even after the IP rotates. If your friend's plan is on the HFC or FTTC footprint, the router may sit in bridge mode behind the NBN connection box, which adds a layer of port-forwarding complexity that is worth documenting before problems arise.

The single most important step is putting both NAS units on a virtual private network. WireGuard or OpenVPN, running on either the routers or the NAS operating systems themselves, encrypts every packet so that replication traffic cannot be read by an upstream provider or anyone snooping on a café Wi-Fi network. A site-to-site style setup, where each NAS treats the other as a remote subnet, lets scheduled jobs behave almost like a local copy once the tunnels are up. For households in regional Tasmania or the Top End with slower NBN satellite or fixed-wireless services, this is also where you throttle transfer windows to overnight so that neither household's Netflix stream suffers.

Choosing replication tools and schedules

Synology Hyper Backup and QNAP Hybrid Backup Sync are both capable of pushing encrypted snapshots to a remote server, and they understand NAS-to-NAS targets natively. Set the schedule so the initial full backup runs once, then incremental jobs fire nightly or weekly depending on how much data changes. Snapshot-based replication has the bonus of being able to roll back to a specific point in time, which is exactly what you want when a mistakenly deleted folder would otherwise propagate straight to the offsite copy.

For more technical households, a lightweight rsync-over-SSH job scripted in Task Scheduler on DSM or a cron job on QTS gives finer control over which subdirectories are excluded and how many old revisions are kept. Whatever tool you pick, configure email or push notifications so both households know when a job fails, since a backup that quietly stopped three months ago is worse than no backup at all. A small laminated card taped to the side of each NAS with the contact details of the other household speeds up troubleshooting on the rare occasions something needs attention.

RAID strategy and capacity planning

The receiving NAS still needs its own redundancy, because a friend store does little good if a single hard drive failure wipes it out the week before you actually need to restore. A mirrored layout such as RAID 1 or SHR-1 across two matching drives is usually enough for personal archives, while larger households in Sydney or Perth with multi-terabyte libraries often step up to a four-bay SHR-2 or RAID 6 configuration. The choice also affects usable capacity, which is why calculating effective space after parity before committing to a replication schedule is worth the ten minutes it takes.

Equally important is deciding what to encrypt. Most modern Synology and QNAP models include AES-NI acceleration, so enabling at-rest encryption on the receiving volume costs almost nothing in performance and ensures that pulling the drives out of the box yields unreadable data. Pair this with the VPN tunnel that already protects data in flight, and the friend backup covers the three states information can occupy: stored, travelling, and being copied.

Testing, monitoring, and the Australian legal context

A replica that has never been restored is just an expensive guess. Schedule a quarterly test where a sample of files is pulled back from the friend's NAS to a laptop or external drive, and confirm checksums or simply open a few key documents to make sure they are not corrupted. Keep a written log, since household memory fades faster than you might think, especially when the person responsible for the remote NAS moves house or swaps routers.

There is also a legal dimension worth mentioning. If either household is storing information that identifies other people, such as client records for a small Canberra accounting practice or patient files from a Perth allied-health clinic, the Privacy Act 1988 still applies even though the data sits on a friend's hardware. A simple written agreement between the two households, outlining who can access the drives, how long deleted files are retained, and what happens if the arrangement ends, protects both parties. For most Australians the offsite-NAS approach will sit comfortably within personal use, but treating the legal layer as seriously as the technical one keeps a useful tool from becoming an unexpected headache.

If this sounds like the kind of low-cost resilience your data has been missing, the next step is a quiet conversation over a coffee in your local Melbourne or Brisbane café, followed by an evening spent configuring both boxes. Pick a tool, set up the VPN, run that first full replication, and sleep better knowing your files exist in two genuinely separate places.