Synology Active Backup for Business: Setup and Review
Small Australian offices often spread critical files across laptops, desktops and a Synology NAS without a dependable recovery plan. Active Backup for Business (ABB) turns the NAS into a central endpoint repository, giving small teams one console for backup schedules, retention and restore points.
This review follows setup from DSM installation through agent enrolment, retention, security and recovery testing. It also examines where ABB fits beside Hyper Backup, RAID, snapshots and off-site copies for businesses in Sydney, Melbourne and regional Australia.
What the package actually protects
ABB backs up supported Windows and macOS endpoints with scheduled or continuous runs, covering system content, user data and recovery options for supported applications. Incremental transfers resend only changed blocks, while the DSM interface centralises client status and retention policies.
ABB is a workstation recovery tool rather than a complete continuity system. A NAS failure, deleted repository or ransomware event can affect every stored version, and cloud copies are not automatic. Separate snapshots and an off-site target remain necessary.
Preparing the Synology NAS
Begin on a current DSM release, create a dedicated administrator account with multifactor authentication, and install Active Backup for Business from Package Center. Prepare a dedicated shared folder for backup repositories, apply a quota, and update DSM before enrolling clients.
Where supported, Btrfs is the sensible choice for snapshots, checksums and storage efficiency. RAID improves availability within a pool but cannot stop deletion, corruption or device loss. The RAID configuration guide explains that distinction, so ABB repositories still need snapshots or replication.
Installing and configuring the service
After installation, choose the repository, define retention, and generate any required encryption material. Install the matching agent on each endpoint, enter the NAS address, select the shared folder, and complete the trust prompt. Service accounts and firewall rules must allow scheduled access.
Pilot with one machine before expanding. For a Melbourne office, an arvo schedule could combine a mid-afternoon run with an evening incremental job. Use version control or rotation instead of unlimited retention, and document the policy before adding more laptops.
A non-sensitive workflow walkthrough from a business video service can help staff recognise the agent, but it must not display credentials, recovery keys or customer records. Keep the administrator guide in a controlled location.
Where it fits with other Synology tools
The recovery stack separates endpoint, file and volume protection:
| Recovery need | Active Backup for Business | Hyper Backup | Snapshot Replication |
|---|---|---|---|
| Primary workload | Windows and macOS endpoints | NAS files, settings and selected data | Volumes or LUNs on supported targets |
| Backup style | Agent-based incremental imaging | File-level versioning and schedules | Block-level snapshots and replication |
| Typical recovery | Rebuild a failed computer | Recover a deleted folder or configuration | Restore a volume quickly after site loss |
| Main limitation | Licensing and agent deployment | Not a complete endpoint system image | Replication needs suitable targets |
ABB offers the most useful image for rebuilding a lost laptop. Hyper Backup is stronger for NAS shares and configuration data, while Snapshot Replication speeds volume recovery on supported targets. Using one package for every task tends to leave recovery gaps.
Performance and storage behaviour
First full backups consume the most bandwidth; later jobs transfer only changed data. Test throughput between an office and the NAS over its NBN link, including laptops on busy Wi-Fi. A router change cannot rebuild a failed disk, so endpoint images and NAS data require separate recovery paths.
Deduplication and compression can limit repository growth, although savings depend on the workload and DSM features enabled. Monitor capacity, snapshot growth and restore duration rather than trusting estimates. Australian listings, including Amazon.com.au, usually show GST-inclusive prices, but storage expansion and endpoint licences belong in the budget.
Security and practical Australian use
Use encrypted transport, unique administrator credentials, multifactor authentication and least-privilege client accounts. Protect the NAS with immutable snapshots where supported, test their configuration, and keep encryption keys and administrator recovery details outside the NAS. Snapshots alone are not an off-site copy.
For Australian businesses subject to the Privacy Act 1988, the Australian Privacy Principles make backup access, retention and breach response operational concerns. A branch office should apply the same controls to its NAS as to a central records store and document who can restore personal information.
Connectivity ranges from metropolitan NBN to regional fixed-wireless or satellite services, so retry policies need realistic timeouts. Router performance is separate: the ASUS ZenWiFi XT8 review helps assess mesh coverage, but no Wi-Fi system replaces backups for data held on the NAS.
Verdict and a safe first deployment
ABB suits small teams wanting a manageable central view of endpoint recovery without a complex enterprise stack. Setup is straightforward on supported DSM and client versions, and incremental imaging makes rebuilds faster than manual reinstallation. The trade-offs are licensing, repository capacity, NAS dependence and disciplined restore testing.
Before rollout, verify that an important endpoint can be restored onto replacement hardware, confirm its application and network settings, and measure recovery time. The next step is to restore one non-critical workstation from a disposable test repository and record the result.