Home | Contact
whichnas.com

Configure a NAS to Wake on LAN for Scheduled Scans

A NAS can save energy by sleeping or shutting down when nobody is using it, yet scheduled antivirus checks, file indexing, integrity tests and backup jobs still need computing time. Wake on LAN (WoL) solves this by allowing a network packet to start the NAS shortly before a planned task, then letting the system return to sleep afterwards.

This arrangement suits home offices, media libraries and small businesses that do not need storage running around the clock. It is particularly useful in Australia, where electricity costs can be significant and many households rely on an NBN connection, a compact router and a NAS tucked away in a study, garage or comms cupboard.

Understand the wake-and-scan workflow

Wake on LAN does not start a scan by itself. It sends a “magic packet” to the NAS network interface, prompting the device to boot or resume from a supported low-power state. A scheduler then waits for the NAS to become available and launches the scan through the NAS operating system, a package, a script or a management computer.

A typical sequence is to wake the NAS at 2:00 am, wait five to fifteen minutes, run a malware scan or storage check, perform a backup if required, and shut the NAS down at 4:00 am. Allow extra time for systems with several hard disks, encrypted volumes or large RAID arrays. A scan that is reliable on a small SSD pool may take much longer on a multi-disk archive.

Wake on LAN usually works best from another device on the same local network. Sending a packet across the public internet is more complicated because routers may discard broadcast traffic, and carrier-grade NAT can prevent inbound connections. For remote administration, use a VPN into the home or office network rather than exposing NAS management ports.

Check hardware, firmware and network support

First confirm that the NAS model, network adapter and operating system support WoL. Synology devices commonly expose the relevant setting under hardware or power controls, while QNAP systems may place it under power management or network services. Menu names vary by model and firmware release, so consult the current documentation for the exact interface.

The NAS must normally be connected by Ethernet. Wi-Fi adapters, USB network dongles and some inexpensive switches do not maintain the standby state needed to receive a magic packet. Update the NAS firmware, router firmware and network adapter drivers before testing. Older hardware can support wake from sleep but not wake after a complete shutdown.

Power interruptions matter as well. A UPS is worthwhile for a NAS holding business records, family photos or surveillance footage. Configure the NAS to shut down safely when the UPS battery reaches a chosen threshold, and check whether the device resumes automatically after mains power returns. In regional areas affected by storms or unstable supply, this can prevent a scheduled job from being interrupted repeatedly.

Prepare a dependable network path

Give the NAS a stable address through a DHCP reservation on the router, or configure a static address outside the router’s automatic allocation range. This prevents a scheduled script from attempting to contact a different device after a lease change. Record the NAS MAC address, which is the identifier used by most WoL tools.

Avoid placing the NAS behind an aggressive energy-saving switch that powers down its Ethernet port. Managed switches may have green Ethernet or port sleep features that interfere with standby listening. If the NAS connects through a mesh Wi-Fi system, test whether the mesh forwards local broadcast packets correctly; some systems isolate wireless and wired clients.

A practical local setup might use a fixed NAS address such as 192.168.1.20, a router reservation, and a small always-on Raspberry Pi, mini PC or desktop to send the wake packet. That control device can also run a shell script, Windows Task Scheduler job or home-automation routine. Keep the NAS and controller on the same trusted LAN, especially when the equipment is installed in a shared office.

Build a preflight checklist

Before creating the schedule, verify the conditions that allow the NAS to wake and complete its work. A short manual test is more valuable than assuming that a setting will behave correctly overnight.

The BIOS or UEFI option may be called Wake on LAN, Power On by PCI-E, Resume by LAN or a similar name. Some systems have separate settings for wake from sleep and wake from soft shutdown. Test both states, because a NAS that wakes from sleep may remain unresponsive after a full shutdown.

After changing a setting, shut down the NAS, wait at least one minute, and send a magic packet from the controller. Repeat the test three times. If it only works occasionally, do not schedule important backups yet. The cause may be a switch, router broadcast rule, firmware issue or a power-management feature on the NAS.

Configure scheduled scans on Synology

On a Synology NAS, enable Wake on LAN in the relevant hardware or power-management settings, then configure the automatic power schedule. Depending on the DSM version and model, the schedule can control startup, shutdown, restart or sleep periods. Set the wake time earlier than the scan to allow DSM and storage services to initialise.

Create the scan in Security Advisor, an installed antivirus package or a scheduled task, depending on what you need to examine. For file-level scanning, choose the shared folders that contain downloaded files, documents and media imports. For a health check, use Storage Manager tools appropriate to the filesystem and RAID type. Do not confuse a malware scan with a RAID scrub or S.M.A.R.T. test: each stresses the disks differently.

Synology Hyper Backup and Active Backup jobs can also follow the wake period. Configure notifications for failure, skipped execution and insufficient storage. A useful alert should identify whether the NAS failed to wake, the volume was unavailable, the scan timed out or the task completed with findings. If researching older configuration references, preserve the source and its context; even a regional archive resource demonstrates why dated technical material should be checked against current software documentation.

Configure scheduled scans on QNAP

QNAP systems generally provide power schedules and Wake-on-LAN controls through the administration interface, though the precise location differs between QTS and QuTS hero releases. Enable WoL, set the automatic power-on time and allow enough boot time before launching Malware Remover, an antivirus package, a storage scan or a backup task.

For an automated workflow, use QNAP’s task scheduler where possible. A scheduled task can call a script, start a backup application or run a diagnostic command. If an external controller sends the magic packet, have it wait for a successful ping and then test a service port before starting the scan. A ping response alone does not prove that the storage pool is mounted.

RAID scrubbing, deduplication and large media indexing can create heavy disk activity. Schedule these jobs separately from antivirus scans when practical. On a QNAP used by a small Melbourne design studio, for example, a nightly document scan may be harmless, while a weekly RAID scrub is better placed on a weekend with notifications sent to the administrator.

Automate timing and account for Australian time

Use the controller’s local time zone and enable automatic daylight-saving changes where appropriate. Sydney, Melbourne, Canberra, Hobart and Adelaide observe daylight saving, while Brisbane, Darwin and Perth do not. A schedule copied between locations can therefore run an hour early or late for part of the year. Confirm the time zone on both the NAS and the device sending the wake packet.

The schedule should include a readiness check. A simple process is to send the packet, wait in stages, test connectivity, confirm that the required volume is mounted, start the scan, and record the exit status. Add a timeout so a failed boot does not leave the controller waiting indefinitely. If the task fails, send an alert rather than silently treating the night as successful.

For Australian households, avoid scheduling loud disk activity during times when it may disturb bedrooms or nearby neighbours, especially when the NAS uses older mechanical drives. In a home with a solar battery, you might also align a daytime maintenance job with surplus solar generation, while retaining an overnight wake schedule for urgent security scans.

Diagnose missed wakes and incomplete scans

If the NAS never wakes, check the physical link lights, MAC address and switch behaviour first. Send the packet from a device on the same subnet and try both a graphical WoL utility and a command-line tool. A wrong MAC address is common after replacing a motherboard, network adapter or NAS system board.

If the NAS wakes but the scan does not start, inspect the scheduler history, service dependencies and permissions. A task may fail because an encrypted volume has not unlocked, a shared folder is offline, a package update changed its command path or an administrator account is no longer authorised. Test the scan manually while logged in with the same account used by the scheduled task.

Security deserves equal attention. Do not publish the NAS administration interface or WoL service directly to the internet. Keep firmware current, disable unused services and restrict scheduled scripts to the permissions they need. Review logs after the first week, confirm that notifications arrive, and run an occasional restore test so the system proves it can protect data rather than merely report activity.

Set up the wake packet, readiness check and scheduled scan in stages, starting with a manual test during the day. Once the NAS reliably wakes, completes its task and shuts down safely, activate the overnight timetable and monitor the logs for several cycles. This creates an energy-conscious storage system that remains available when needed without running continuously.