A 4 TB NAS backup takes roughly 10 hours over a 1GbE home network. And over 10 days if you're uploading to the cloud over an NBN 50 connection. Most people are shocked by this gap. The hardware benchmarks are fine, the backup software is set up correctly, and yet the first backup takes forever. The reason is almost always the same: the connection speed, not the NAS or the software, is the limiting factor. This guide breaks down realistic backup times for the setups most Australian NAS owners actually have, and explains what you can do when the numbers don't fit your maintenance window.
In short: Over a 1GbE home network, expect roughly 2.5 hours per TB for a full backup at real-world speeds (~110 MB/s). Over NBN 50 upload, expect roughly 60+ hours per TB. The initial full backup is always the slow part. Incremental backups after that typically finish in minutes. Use the Backup Time & Window Calculator to model your specific setup.
Why Backup Time Surprises People
Backup software benchmarks and vendor marketing typically quote the NAS's disk read speed or network interface throughput. Numbers like "1 Gbps" or "200 MB/s read." What they don't tell you is that these are theoretical maximums under ideal conditions, and that your backup job will almost certainly be bottlenecked by something slower: the destination write speed, the network link, or (for cloud and offsite backups) your internet upload connection.
There are three links in the backup chain: the source that reads data, the network that moves it, and the destination that writes it. The slowest of the three determines your actual backup speed. On a home LAN where both source and destination are connected over 1GbE, the practical ceiling is around 100-115 MB/s sustained. Faster than most single-drive HDDs can write, but not as fast as the spec sheet implies. Over NBN, the ceiling drops dramatically: a typical NBN 50 plan delivers around 37 Mbps real-world upload, which is roughly 4.6 MB/s. About 24 times slower than a 1GbE LAN transfer.
Full Backup Times: What to Expect on Australian Connections
The table below shows estimated full backup times for common dataset sizes across the connection types most Australian NAS owners have. These use real-world sustained throughput, not burst or theoretical maximums. NBN upload figures reflect approximately 75-80% of the advertised tier speed, consistent with typical FTTC and FTTN performance.
Full Backup Time by Dataset Size and Connection Type
| 1GbE LAN (~110 MB/s) | NBN 50 Upload (~37 Mbps real) | NBN 100 Upload (~75 Mbps real) | 10GbE LAN (~500 MB/s) | |
|---|---|---|---|---|
| 500 GB | ~1h 16m | ~30h (1.3 days) | ~15h | ~17m |
| 1 TB | ~2h 35m | ~62h (2.6 days) | ~30h (1.3 days) | ~34m |
| 2 TB | ~5h 10m | ~124h (5.2 days) | ~60h (2.5 days) | ~1h 8m |
| 4 TB | ~10h 20m | ~248h (10.3 days) | ~121h (5 days) | ~2h 17m |
| 8 TB | ~20h 40m | ~496h (20.7 days) | ~242h (10 days) | ~4h 34m |
| 16 TB | ~41h 20m | ~993h (41 days) | ~484h (20 days) | ~9h 8m |
A few things stand out from this table. First, a 1GbE LAN backup of 4 TB takes just over 10 hours. This fits comfortably in an overnight window. Second, that same backup over NBN 50 upload takes over 10 days. Completely incompatible with any reasonable maintenance window. Third, 10GbE makes a significant difference for large datasets: 4 TB in just over 2 hours versus all night on 1GbE. If you're backing up 8 TB or more to a local destination and time matters, 10GbE is worth considering.
The Initial Seed Problem. Why Your First Backup Is Always Slow
The initial full backup is the hardest part of any NAS backup strategy. There's no shortcut: you have to move all the data at least once. This is true whether you're backing up to another NAS on your LAN, to an external USB drive, or to the cloud. After the initial seed, everything changes. Incremental backups only move changed data, which is typically a small fraction of the total.
The mistake most NAS owners make is starting the initial backup at an arbitrary time, then discovering mid-week that it's still running and impacting network performance. The right approach is to treat the initial seed as a one-time project: schedule it for a Friday evening, accept that it will run over the weekend, and don't expect anything from your network while it's happening.
For cloud backups, the situation is more extreme. If you have a 4 TB dataset and an NBN 50 connection, the initial seed will take over 10 days at real-world upload speeds. During this time, your upload bandwidth will be saturated unless you configure bandwidth throttling in your backup software. Most NAS backup tools. Including Synology Hyper Backup and QNAP Hybrid Backup Sync. Support upload speed limits that let you cap the backup to, say, 50% of available upload bandwidth during business hours.
Local seed strategy for cloud backups: Back up your initial dataset to a portable USB drive, physically transport it to the offsite location or post it to the cloud provider's seed ingestion service, then switch to incremental-only over NBN. This can reduce the initial cloud backup from weeks to hours. Many Australian cloud providers support this workflow. Ask about "offline data transfer" or "seed import" options.
Full vs Incremental vs Differential: How Much Data Actually Moves Each Night
Once the initial seed is done, the ongoing backup strategy determines how long each nightly job takes. Understanding the three backup types is essential for fitting backups into a real maintenance window.
Full backups copy everything every time. A weekly full backup of 4 TB over 1GbE takes over 10 hours. Fine for a weekend, but it chews up your entire overnight window. Running full backups nightly on large datasets is almost never practical.
Incremental backups only copy data that has changed since the last backup (whether that was a full or another incremental). For a typical home NAS with a 5% daily change rate on a 4 TB dataset, that's roughly 200 GB changed per day. Over 1GbE, that incremental takes about 31 minutes. Over NBN 50, about 12 hours. Which is still a stretch for a standard overnight window, but far more manageable than a full backup.
Differential backups copy everything that has changed since the last full backup. They start small (Day 1 is similar to an incremental) and grow each day until the next full run. By Day 7, they're approaching the size of a full backup. Differential backups are faster to restore (you only need the last full plus one differential file), but they create more transfer volume than incrementals on a day-to-day basis.
Nightly Backup Time: 4 TB Dataset, 5% Daily Change Rate (~200 GB changed/day)
| 1GbE LAN (~110 MB/s) | NBN 50 Upload (~37 Mbps) | NBN 100 Upload (~75 Mbps) | |
|---|---|---|---|
| Full (4 TB) | ~10h 20m | ~248h (10+ days) | ~121h (5 days) |
| Incremental (~200 GB) | ~31m | ~12h 24m | ~6h 6m |
| Differential Day 3 (~600 GB) | ~1h 32m | ~37h | ~18h 12m |
| Differential Day 7 (~1.4 TB) | ~3h 35m | ~86h (3.6 days) | ~42h (1.75 days) |
The practical conclusion: for most home NAS owners, a weekly full backup (over the weekend) combined with nightly incrementals is the right strategy. The weekend full backup fits comfortably on 1GbE, and nightly incrementals typically complete in 30-60 minutes for datasets up to 4 TB with a normal change rate. This is exactly the strategy that Synology Hyper Backup and QNAP Hybrid Backup Sync are designed for. Both support scheduled full + incremental rotation out of the box.
NBN Upload Reality: Why Cloud Backup Is Hard in Australia
Australia's NBN upload speeds are one of the most under-discussed constraints in the NAS space. The upload tiers look reasonable on paper, but the real-world experience is consistently lower than advertised, and even the top residential tiers leave a lot to be desired for large backup workloads.
Typical real-world upload throughput for common NBN plans:
- NBN 25: ~15 Mbps real (~1.9 MB/s). Barely usable for anything beyond small incremental backups
- NBN 50: ~37 Mbps real (~4.6 MB/s). The most common plan; practical for incrementals under ~200 GB, painful for anything larger
- NBN 100: ~75 Mbps real (~9.4 MB/s). Workable for 500 GB incrementals, still slow for initial full backup of large datasets
- NBN 250: ~190 Mbps real (~23.8 MB/s). Genuinely useful; 4 TB initial backup takes about 5 days instead of 10
NBN upload speeds are also asymmetric by design. You get more download than upload. For backup purposes, only upload speed matters, which is why NBN plans that look fast for streaming video can feel slow when you're trying to push data offsite.
There's also the CGNAT complication: NBN fixed wireless, satellite, and some FTTP plans use Carrier-Grade NAT, which means you can't receive incoming connections. Most self-hosted offsite backup setups rely on the backup software connecting out to the destination, which still works under CGNAT. But peer-to-peer setups or remote access via port forwarding will fail. Synology QuickConnect and QNAP myQNAPcloud work around this by routing through vendor relay servers. Tailscale is the most reliable general-purpose solution for Australian users on CGNAT connections.
How to Estimate Your Backup Window
A backup window is the time available between when the last user finishes working and when the first user starts again. Typically overnight. For home users, this is roughly 10 PM to 7 AM (9 hours). For small businesses, it might be 8 PM to 7 AM (11 hours). The backup must complete before the window closes, and ideally with at least 30-60 minutes of margin in case of slowdowns.
To estimate whether your backup fits in your window, you need three things: how much data moves per run (full vs incremental, plus compression), your effective throughput (the slowest link in the chain), and your available window hours. The Backup Time & Window Calculator does this calculation automatically and flags whether your current setup fits, runs tight, or overruns. With practical recommendations if it doesn't fit.
The most common mistakes in backup window planning:
- Using vendor speed specs instead of real-world throughput. A "1 Gbps" NAS doesn't actually write at 125 MB/s sustained. Plan for 90-115 MB/s depending on RAID level, drive age, and protocol overhead.
- Not accounting for compression overhead on weak CPUs. Enabling compression on a NAS with a low-power ARM CPU can actually slow backups down if the CPU can't compress data as fast as it can be transferred. Measure both ways before committing.
- Scheduling full backups nightly on large datasets. A 6 TB dataset doesn't fit in an overnight window on 1GbE. It takes 15+ hours. Switch to weekly full + nightly incremental.
- Forgetting that backup windows change. A backup that fits comfortably in a window today won't fit in two years when your dataset has doubled. Build headroom into your planning.
When Cloud Backup Makes Sense for Australian NAS Owners
Despite the upload speed constraints, cloud backup remains worthwhile for many Australian NAS owners. The key is understanding which part of the 3-2-1 backup strategy it serves. Cloud backup is best used as the offsite copy, not as the primary backup destination.
Cloud backup works well when: Your dataset is under 1 TB, your daily change rate is small, you're on NBN 100 or NBN 250, or you've seeded the initial backup locally. In these cases, nightly incremental backups complete in a reasonable window and the offsite coverage is genuine.
Cloud backup is impractical when: Your dataset is 4 TB or larger, you're on NBN 50 or slower, or you need fast recovery time objectives. Restoring 4 TB from the cloud over an NBN connection takes just as long as uploading it did. Potentially weeks. For large datasets, a local NAS-to-NAS backup (to a second NAS at a relative's house or office) is often more practical for Australian conditions than cloud.
Australian cloud storage options worth considering include Backblaze B2 (cost-effective for large datasets, Synology Hyper Backup compatible), Wasabi (no egress fees, important if you need to do a full restore), and Amazon S3 (via Synology or QNAP native integration, but egress costs add up on large restores). Cloudflare R2 has no egress fees and is increasingly supported by third-party backup tools. For any cloud backup, calculate your restore time as carefully as your backup time. The backup is only half the equation.
Backup Window Strategies That Actually Work
If you're struggling to fit your backup into a window, these strategies. Roughly in order of impact. Are worth considering:
- Switch from full to incremental nightly. This is usually the single biggest improvement available. A 5% daily change rate on a 4 TB dataset means 200 GB moves nightly instead of 4 TB. A 20× reduction in transfer volume.
- Run full backups weekly, not daily. Schedule the full backup for Saturday night when you have the whole weekend. Use incrementals Mon-Fri.
- Enable compression if your NAS has a capable CPU. Intel Celeron J-series and above handle AES-NI and compression well. Realtek and Marvell ARM CPUs are slower. Test before enabling compression in production.
- Upgrade your network if you're on 1GbE and backing up 8 TB or more. 2.5GbE (roughly 250 MB/s real-world) nearly triples throughput for around $60-80 in adapters. 10GbE is faster still. See our 10GbE networking guide for NAS for AU pricing and compatibility.
- Use a NAS-to-NAS offsite strategy for large datasets. A second NAS at a relative's home, connected over NBN, handles initial seed via physical transport and then runs incrementals overnight. This sidesteps the NBN upload limitation for the initial seed and keeps restore times fast.
- Stagger your backup jobs. If you're backing up to two destinations (local + cloud), don't run them simultaneously. They'll compete for disk I/O and network. Run local backup 10 PM-4 AM, cloud incremental 4 AM-7 AM.
Model your specific backup setup. Enter your dataset size, connection speed, and backup window to get realistic time estimates and window-fit analysis.
Open Backup Time Calculator →Related reading: our NAS buyer's guide.
How long does it take to back up 1 TB on a home NAS?
Over a 1GbE home network at real-world speeds (~110 MB/s sustained), a full backup of 1 TB takes approximately 2.5 hours. Over NBN 50 upload (~37 Mbps real-world, about 4.6 MB/s), the same 1 TB backup takes roughly 62 hours. Just over 2.5 days. After the initial full backup, nightly incremental backups for a typical 5% daily change rate (50 GB changed) take around 8 minutes on 1GbE and about 3 hours over NBN 50.
Will my backup finish overnight?
It depends on your dataset size, backup type, and connection speed. A full backup of 4 TB takes about 10 hours on 1GbE. Tight but usually fits in an overnight window. A nightly incremental for that same dataset (assuming 5% daily change, ~200 GB) takes about 30 minutes. Over NBN, a 200 GB incremental takes about 12 hours on NBN 50. Workable but only just. The Backup Time & Window Calculator gives you specific numbers for your setup and flags whether your backup fits, runs tight, or overruns.
Why is my NAS backup so slow?
The most common causes, in order of frequency: (1) you're backing up over NBN upload instead of LAN. NBN is typically 20-25× slower than a 1GbE local network; (2) you're running a full backup every night on a large dataset. Switch to weekly full + nightly incremental; (3) your destination drive is the bottleneck (older HDD or slow USB drive); (4) you've enabled compression on a NAS with a weak CPU, which adds CPU overhead faster than it saves transfer time; (5) backup software overhead. Some tools add significant overhead per-file, making them slow on datasets with millions of small files even if disk speeds are fine.
What's the difference between incremental and differential backups for NAS?
An incremental backup copies only what changed since the last backup. Whether that was a full or another incremental. Each run is small and fast, but restoration requires the last full plus every incremental since. A differential backup copies everything changed since the last full backup. Each run grows until the next full, but restoration only requires the last full plus one differential. For most home NAS users, incremental is the right choice: smaller daily transfers, and modern backup software (Hyper Backup, Active Backup for Business) handles the multi-file restoration automatically.
Can I speed up the initial full backup to the cloud?
Yes. Use a local seed strategy. Back up your data to a portable USB drive or external HDD, then ship or physically carry that drive to the cloud provider's ingestion facility. Many cloud providers accept physical drives for initial seed import. After ingestion, the cloud backup switches to incremental-only sync over NBN, which is far more manageable. If your provider doesn't offer seed import, an alternative is to do the initial backup locally to a NAS at an offsite location (a relative's home), then transition to remote incremental sync once the seed is complete.
Does Synology Hyper Backup or QNAP Hybrid Backup Sync support incremental backups?
Yes, both do. Synology Hyper Backup supports scheduled full backups with configurable incremental intervals. You can run a full backup weekly and incrementals nightly. QNAP Hybrid Backup Sync similarly supports mixed schedules. Both tools also support compression and encryption, though you should test the performance impact of compression on your specific NAS model before enabling it in production. For a Synology setup guide including backup configuration, see the linked article.
How does Australian Consumer Law affect NAS purchases for backup use?
Australian Consumer Law provides statutory warranty protections beyond the manufacturer's stated warranty period. Typically 2-3 years for NAS devices priced in the consumer range, based on reasonable expectations for that product category. This applies when purchasing from Australian retailers (Mwave, PLE, Scorptec, Umart). If your NAS fails within a period that a reasonable person would expect it to last, you're entitled to a remedy from the retailer regardless of the manufacturer's warranty terms. This is relevant for backup use because NAS units running 24/7 may develop faults earlier than expected. And ACL protections provide recourse even if the hardware warranty has expired.