The safest way to back up a ZimaOS server to another NAS is to protect the data that must survive a reinstall—not to clone the entire operating system. Back up user folders, persistent Docker app data, and any application databases to your LAN target, then keep at least one additional copy on different media or offsite.
ZimaOS uses a lightweight appliance-style system with dual system slots for recovery. That makes its recovery model different from a Synology DSM migration backup: the OS can be recovered or reinstalled separately, while your valuable data lives on storage volumes and mapped app folders. The goal is therefore a recoverable server, not necessarily a byte-for-byte image of the running system.
What Should a ZimaOS Backup Actually Include?
A useful backup plan starts by separating replaceable software from irreplaceable data. Docker containers and App Store packages can usually be recreated. Your files, app settings, databases, and media libraries cannot.
User folders and shared data
Back up Documents, Media, Photos, project folders, website data, and any other directories that users or applications actively modify. The current ZimaOS 3-2-1 backup guide supports LAN, USB, cloud, and Zima-to-Zima sources and destinations.
Persistent Docker app data
App Store containers are disposable, but their mapped folders are not. ZimaOS documents that configuration and persistent files live outside the container under the configured App Data location. Check the ZimaOS app storage paths before deciding what to include in the backup.
Databases and stateful services
For services such as Nextcloud, WordPress, Home Assistant, Immich, MariaDB, or PostgreSQL-backed applications, copying a live data directory is not always enough. When the upstream application provides a database dump, export, or maintenance procedure, use it. A clean database backup plus the app’s configuration folders is usually more portable than copying an inconsistent database while it is actively writing.
How to Build a LAN Backup Job
Step 1: Decide which machine is the destination
A Synology, another NAS, a file server, or another Zima device can all serve as a LAN destination if ZimaOS can reach a writable shared folder. Confirm the share has enough free space and that the account used by ZimaOS has permission to create, modify, and delete files as required by your retention policy.
Step 2: Create separate backup tasks by data type
Do not put everything into one giant job unless you have a reason. Create independent tasks for critical documents, media, app data, and other categories. This makes failures easier to diagnose and lets you give irreplaceable data a more aggressive schedule than replaceable media.
Step 3: Schedule and test the job
Run the first backup manually, confirm the destination contains the expected files, then enable scheduling. A green task state is not enough: open a few restored files and verify that permissions, filenames, and timestamps are acceptable.
How Should You Back Up Docker Apps?
The key is to back up the host paths mapped into the container, not the ephemeral container filesystem. The current ZimaOS guide recommends keeping App Data off the small system drive and on your main storage pool. That also makes backup scope easier to understand.
If you use custom Docker Compose stacks, keep a copy of the Compose YAML, environment variables, custom configuration files, and secrets in a protected location. Do not rely on screenshots of settings. A Compose file plus persistent data folders is much easier to rebuild on new hardware.
The ZimaOS backup overview is useful when planning where each copy should live, while the Docker storage basics explains the container-versus-data boundary.
What About the ZimaOS System Itself?
ZimaOS has a dual-slot system design. The current system recovery guide describes booting the alternate system slot when one partition has a problem.
That recovery path protects you from some OS failures, but it is not a substitute for data backup. If the system disk itself fails, the practical recovery plan is to reinstall or recover ZimaOS, reconnect or recreate storage, reinstall apps, then restore persistent app data and user files.
Use the 3-2-1 Rule Instead of a Single LAN Copy
A LAN backup on another NAS is valuable, but both devices can still be affected by the same theft, power event, ransomware incident, or user mistake. For irreplaceable data, follow the 3-2-1 pattern: three copies, two different storage types, and one offsite copy.
For example, keep the live copy on ZimaOS, a scheduled copy on the Synology, and an encrypted offsite copy in a supported cloud destination or a rotated USB drive stored elsewhere.
Common Backup Mistakes to Avoid
- Backing up only Docker images. Images can be downloaded again; AppData and databases are the important part.
- Assuming RAID is backup. RAID helps with drive failure but not accidental deletion, corruption, or ransomware.
- Installing a host-level backup agent without checking compatibility. ZimaOS is not a conventional mutable Debian server, so system agents can conflict with its protected OS design.
- Never testing a restore. A backup that has not been restored is only an assumption.
- Keeping every copy in the same chassis or room. That does not protect against device-level or site-level loss.
How to Test That Your ZimaOS Backup Is Recoverable
Choose a small representative set: one document folder, one media file, one app configuration directory, and one database export. Restore them to a temporary location, open the files, and verify that the app can read the restored data. Repeat this after major storage or application changes.
For a critical server, also keep a short recovery note listing storage names, app ports, custom Compose stacks, database restore commands, and any domain or reverse-proxy dependencies. That documentation often saves more time than a raw system image.
FAQ
Can ZimaOS create a Synology Hyper Backup-style full system image?
Current ZimaOS documentation focuses on data backup plus system-slot recovery rather than a documented one-click migration image that recreates the full OS, every app, and every setting on different hardware.
Can I use my Synology as the ZimaOS backup destination?
Yes. A reachable SMB/LAN share can be part of the backup design. Verify credentials, free space, and restore access before relying on it.
Do I need to back up Docker containers themselves?
Usually no. Preserve Compose definitions, application configuration, mapped AppData, and databases. Containers and images are typically replaceable.
Will a ZimaOS system recovery restore deleted user files?
No. Slot recovery addresses the operating-system layer. Deleted or corrupted user data requires a separate backup.
