Hello,
I come from synology and the hyper backup allows for a full system backup, including all folders, all applications and system settings.
So, when migrating to a new synology box, you can start up hyper backup on the new system, point it to the backup and it will fully restore everything.
I’ve done that several times being a 20+ year synology user.
A few months ago I got the zimaboard2 and have been migrating my websites to this.
It was a bit of a learning curve, it still is.
Now, I searched on the forum but did not find a clear answer.
Like if I were to buy a ZimaCube, how would I transfer my existing system?
Also, would all docker apps with volumes and what else be restored ?
Thanks for clarification,
Christian
I believe your understanding is correct and aligns with current best practice.
ZimaOS does not offer a Hyper Backup–style full system restore or DSM migration. It’s a different architecture, designed around a lightweight OS and Docker with data living on disk.
I suggest treating a Synology → ZimaOS move as a data-only migration:
- Copy data over LAN (SMB or rsync)
- Migrate files, media, and database exports only
- Avoid restoring DSM apps, settings, or system backups
On ZimaOS, I suggest:
- A fresh install
- Recreating services as Docker containers
- Restoring data under
/DATA and /DATA/AppData
- Adjusting ownership via the Files app if required
This approach avoids compatibility issues and matches what’s recommended in ZimaOS documentation and community discussions.
1 Like
I’m checking how well synology active backup for business would work to make a full copy of my zimaboard system including all attached drives.
I did that for my yunohost server and it runs automatic and daily.
I would have to install the linux client which is available for debian systems.
now , the big question: wouldn’t that interfere with zimaboard2/zimaOS ?
My synology is still in use (DS1513+) with 60TB of storage and could run for the next ten years, so , yes, I would like to continue use it for backup and my zimaboard as a webserver/appserver
Any thoughts?
Christian
I believe your assessment is sound.
ZimaOS is built as a lightweight, mostly immutable system (SquashFS + OverlayFS) with a strong focus on Docker and data living under /DATA. Because of that, I suggest not installing Synology Active Backup for Business agents on ZimaOS. System-level backup agents are likely to conflict with the overlay filesystem, Docker storage layers, and ZimaOS update/rollback mechanisms.
I suggest continuing to use your Synology as a backup destination, not as a system controller:
- Back up
/DATA (especially /DATA/AppData) from ZimaOS to Synology
- Use file-level methods like SMB, rsync, or the ZimaOS Backup app
- Let ZimaOS handle OS recovery via its own rollback or a clean reinstall if ever needed
This keeps things clean and safe: Synology for long-term storage and backups, ZimaOS for apps and services, without introducing unnecessary risk.
1 Like