Synology Active Backup for Business setup guide
Synology Active Backup for Business turns a compatible Synology NAS into a central backup hub for Windows workstations and servers. It combines agent-based backups, scheduling, retention and restore tools within DSM, giving small Australian offices one place to manage endpoint protection instead of separate backup utilities on every machine.
A reliable setup starts before installation. Capacity, user permissions, network paths and recovery tests need a clear plan, especially where staff work from home or across several sites. The steps below cover a practical deployment from package installation through the first verified restore.
Plan capacity and access
First, confirm that the NAS model and DSM version support Active Backup for Business and that a valid licence is available. Choose a storage volume for backup data, not the same folder used for live business files, and leave room for growth. Encryption is worth enabling for customer records, while separate DSM users and groups let administrators manage devices without sharing a broad admin account.
Australian connectivity needs to shape the plan. Staff in Sydney, Melbourne or regional areas may connect over NBN, fixed-wireless or broadband services with variable latency, so endpoint agents should cope with ordinary home connections and reconnect after outages. Remote sites should use a managed VPN rather than expose DSM directly to the internet. If staff need a simple restore drill, a business video service can create a short complement to the written runbook, although technical tests still belong to the IT owner.
Install the DSM package
Sign in to DSM with an administrator account, open Package Center and install Active Backup for Business. Follow the wizard to select the backup volume and shared-folder structure, then create a dedicated service account if the package requests one. Assign only the permissions needed for backup and restore, and record the licence details separately from the NAS.
If the NAS itself is new, this NAS setup walkthrough can help with the preceding hardware, storage and shared-folder preparation. For an existing system, take a current configuration backup and verify free space before changing packages; that gives the installer a clean rollback point.
Next, deploy the Synology Active Backup for Business agent on each supported Windows endpoint. Install it from a centrally staged package, use a descriptive device name such as “Finance-PC-01”, and assign the device to the correct business group. Avoid storing reusable passwords inside a task or shared notes.
Connect devices over a stable network
Agent traffic must reach the NAS over approved management and backup paths. Open the required firewall rules in one direction, test access using the NAS hostname or fixed address, and confirm that name resolution works from each site. A managed switch with VLANs can isolate backup traffic where appropriate, but the goal is a dependable route rather than unnecessary network complexity.
In a typical small business, every agent connects to the central NAS, creating a star topology explained pattern. This arrangement simplifies monitoring because one device and one policy govern the fleet. If the NAS becomes unavailable, affected agents should retry without losing their queue; local caching and schedule settings determine how quickly they resume.
Set group policies before the first broad deployment. Separate servers from laptops, give finance or health-related devices tighter access, and treat retention on temporary workstations differently from key servers. Schedule full initial backups during a quiet period, such as Tuesday arvo, then use incremental runs overnight to limit bandwidth use.
Test restores and operating controls
A backup job showing “successful” proves that data was sent, not that it can be recovered. Restore one ordinary file, one folder and one application-consistent item into a test area. Record the elapsed time, permissions and any missing steps, then compare the results with the business’s recovery point and recovery time objectives.
Before the first scheduled run, check these controls:
- Endpoint names, groups and owners are correct.
- The destination volume has capacity and write access.
- Encryption, retention and schedules match policy.
During each weekly review, check:
- Failed jobs are investigated and retested.
- A sample restore succeeds on a rotating device.
- Growth trends and retention use remain within budget.
Pay attention to time-zone handling as well. Schedule the NAS in Australia/Sydney and document daylight-saving changes; Brisbane does not shift, while Melbourne and Sydney do. For compliance-sensitive information, document how backups support the Privacy Act 1988, Australian Privacy Principles and Notifiable Data Breaches scheme without treating backup alone as complete compliance.
Roll out in controlled stages
Start with two representative endpoints, preferably one office desktop and one laptop used by a remote worker. Watch their initial uploads, retry behaviour and restore results over several days. The two branches work because they expose different network conditions, and fixing issues early is less disruptive than changing policy across the whole fleet.
Then add the remaining devices in small batches. Purchase hardware through Amazon Australia or an Australian Synology distributor, check the local warranty and included power supply, and keep the serial number and configuration export with business records. This suits the Australian market, where online marketplaces and local distributors are both normal purchasing routes and GST should be visible on the invoice.
The next checkpoint is a Friday 17:00 Sydney time review confirming two successful agent connections, one verified file restore and one documented recovery time.