ZimaOS Backup now supports scheduled backups, so the 2025 forum answer saying “there is no real schedule option” is no longer current. Current September 2026 documentation says each backup task can run automatically at the interval you set, and multiple tasks can use independent schedules.
The old thread is useful as a version boundary: documentation once described scheduling before the UI exposed it. Today, create or edit the backup task on a current release and configure its automatic schedule there instead of relying on the old “Auto” behavior.
What Changed Since the Source Thread
In November 2025, a community reply said Backup offered manual and “auto” behavior but no explicit daily/weekly schedule. Current Backup documentation now clearly describes Scheduled Backup and independent schedules per task.
Create a Backup Task First
The current ZimaOS Backup guide uses a source-to-destination model: Cloud, LAN, USB, or Zima as the source, then local disk, another Zima device, external drive, or cloud as the destination.
Set the Automatic Schedule
After defining the task, choose its schedule/interval in the current Backup workflow. Keep separate tasks for data that needs different frequencies—for example, documents nightly and a large media archive weekly.
Use Different Schedules for Different Destinations
You can point the same important source folder at a second local disk and an offsite cloud destination using separate tasks. The current guide explicitly says those tasks can run on different rhythms.
Do Not Schedule Everything at the Same Time
Stagger large USB, cloud, and LAN jobs so the NAS is not simultaneously saturating disks, network, and memory. This also makes failures easier to diagnose.
Check What Happens After an Interrupted Job
Current Backup documentation describes resume/fault tolerance so interrupted transfers can continue. Still, verify the destination after cable removal, power loss, or cloud-auth errors rather than assuming every file resumed correctly.
Test Restore, Not Just Schedule
A perfectly scheduled task can still be useless if the destination is wrong or the files cannot be restored. After the first scheduled run, restore one file and open it.
If Your UI Still Has No Schedule Option
Check the ZimaOS version and make sure you are using the current Backup app rather than an old 2025 build. Update first before applying cron-based workarounds.
The backup strategy guide helps decide how often each task should run.
Choose a Schedule Based on Change Rate
Frequently edited documents may deserve nightly or more frequent protection, while a mostly static media archive can run weekly. The goal is to limit how much work you could lose between backups without creating constant disk and network load.
Stagger Local and Offsite Copies
Run the fast local backup first, then the slower cloud/offsite task later. That gives you a second copy quickly and prevents two heavy tasks from competing for the same source disks at once.
Check the Next Run After Editing a Task
After changing a schedule, verify that the next run occurs when expected and that the task history records success. Do not assume saving the schedule automatically proves the task is enabled and healthy.
FAQ
Can ZimaOS Backup run every day automatically?
Current official documentation says scheduled backup runs automatically at the interval you set.
Can different tasks use different schedules?
Yes. Current docs explicitly describe independent task schedules.
Why did older forum posts say scheduling was missing?
The 2025 UI had not exposed the feature described in the documentation at that time.
Should I use cron instead?
Not for normal current Backup tasks. Use the built-in scheduler first.
