Thank you to u/Ok-Nectarine6833 for sharing a home-server journey in which a ZimaBoard 2 became the main NAS and a ZimaBlade gained a separate backup role. The central idea is a useful one: growth can mean giving retained copies their own machine, rather than making a single server responsible for every task.
The Self-Hosting Day contribution describes the hardware transition and everyday applications. An earlier official community showcase also identifies this contributor’s ZimaOS setup. The dashboard image reproduced here comes from that earlier showcase; it is not presented as a current screenshot of the later two-machine arrangement.
A Storage Appliance Can Be the Beginning of a Learning Process
Many people begin with the straightforward need to keep files in one place. Learning about services, access and recovery often follows after the first storage system is already useful. The important transition is from treating a NAS as a box of disks to understanding the responsibilities assigned to it.
A replacement is a good moment to describe those responsibilities explicitly. File storage, media playback, remote access and retaining recovery copies are related, but they do not have the same requirements. A clear list helps avoid carrying every old assumption into a new installation.

Give the Main Server and Backup Machine Different Jobs
The contributor’s later arrangement distinguishes a daily-use server from a companion intended for backups. That is a more informative description than simply saying that the homelab contains two computers. It identifies why the second device exists.
For a similar installation, decide which directories and application state need to reach the backup destination. Also record what is deliberately excluded. A backup plan is easier to assess when its scope is explicit than when a second machine is simply assumed to hold everything.
| Component or service | Role in the story |
|---|---|
| ZimaBoard 2 | Primary NAS and application host |
| ZimaBlade | A separate backup companion |
| SSD, NVMe and hard-drive storage | Different storage media mentioned in the account |
| Tailscale, AdGuard Home, Jellyfin and RustDesk | Reported examples of daily-use applications |
The contributor uses the historical ZimaBlade name. Current hardware bundles use the ZimaBoard SE name; our ZimaBlade to ZimaBoard SE product update explains the naming and bundle changes without changing the hardware history of this build.
More Drives Do Not Explain the Protection Strategy
Storage media describe capacity and connections; they do not describe how a previous version is retained or how an application is recovered. A collection of disks may be useful for live data, backups or both, depending on how it is configured.
The original comment does not supply a complete disk topology, backup schedule or restore procedure. It would therefore be misleading to turn the storage list into a claimed RAID layout or a verified recovery guarantee. The practical question for another builder is which failure each retained copy is intended to address.
A complementary perspective comes from a dual-ZimaBoard family homelab with mirrored storage. That account also illustrates why the disk arrangement and the application recovery plan need to be explained separately.
A Backup Destination Still Needs a Recovery Procedure
A second host creates room to separate duties, but the recovery path needs its own explanation. Identify the source of a copy, the destination, the time it was made and the access needed to retrieve it. Where an application keeps a database separately from its files, both parts need consideration.
A useful check restores a representative item somewhere isolated. That protects the live installation while testing whether the retained material is understandable and usable. The Proxmox Backup Server documentation illustrates the distinction between inspecting completed jobs and working with retained backups; it is supporting context, not a claim that this contributor uses PBS.
For a new backup arrangement, begin with a bounded recovery exercise:
- Identify the application and the persistent data it needs.
- Locate a retained copy and the access needed to retrieve it.
- Restore a sample separately and check it through the normal client.

For a worked example of file synchronization, our Syncthing setup and data-protection guide provides additional context. The official Syncthing guidance on synchronization and backups explains why changes propagated to another device should not automatically be treated as independent backup history. This is a planning reference, not an additional application attributed to the contributor.
Remote Access and Backup Retention Solve Different Problems
Remote access makes a service reachable from another place. It does not determine how long a recovery point is kept, and it does not by itself create a second copy. Treating those as separate responsibilities makes a home-server plan easier to maintain.
For readers considering routed access, Tailscale’s subnet-router documentation distinguishes access to networks from installing a client directly on every device. That is a deployment option to understand, not evidence of the exact topology in the creator’s home. Begin by listing who needs access to which service, then configure the required path.
Check the user-facing service as well as the connection itself. Reaching the network is different from opening a library or retrieving a file. A successful connection can coexist with an application permission or storage problem.
Keep the Upgrade Small Enough to Understand
Moving from an older NAS to separate service and backup roles introduces new choices. A short inventory should connect each application with its data location and retained recovery material. That makes later expansion less dependent on remembering the order in which disks and containers were added.
The household perspective in Pi-hole to family server: u/2Hard4Him’s ZimaOS story is useful here. A project becomes infrastructure when people rely on its files and services. small-homelab service roles in u/jc-21’s build provides another example of defining a few useful responsibilities clearly rather than judging a server only by its size.
FAQ
Is the ZimaBlade the primary server in this story?
The contributor describes it as a backup companion to the ZimaBoard 2.
Does the comment prove a particular RAID arrangement?
No. It names storage media without publishing a complete topology. This article does not infer a RAID configuration.
Is the displayed dashboard from the current two-node setup?
It is an earlier screenshot credited to the same contributor in the official community showcase. It should not be read as documentation of the later hardware arrangement.
Does a second server automatically provide a complete backup?
No. Scope, retention, independent access and a usable restore procedure still need to be defined and checked.
Conclusion
This contribution gives a small homelab a clear direction: one machine provides the services used today, while another has a defined role in protecting the ability to recover. That distinction is more useful than treating additional hardware as an end in itself.
The transferable lesson is to connect each new device to a responsibility, then check the result through the files and applications that matter to the household.
Welcome to the ZimaSpace community! Share your setup, ask questions, and explore practical build guides, real user stories, and product updates with fellow self-hosters.
Zima Campaign Hub
More to Read

A ZimaBoard 2 Prototype with Two 22 TB Drives on the Test Bench
Explore sabitech2k’s early ZimaBoard 2 drive test, the reported power conditions, and the existing ZimaBoard used for Proxmox backups.

A Quiet ZimaCube and ZimaBoard Homelab with Debian and Docker
A ZimaCube and ZimaBoard split everyday applications from smart-home services, with Debian, Docker, Pi-hole and a Homepage dashboard.

A LEGO Rack for a First ZimaBoard 2 Home Server
See how a first-time builder organized a ZimaBoard 2 and two SSDs in a LEGO rack, with Home Assistant and home-office storage planned next.




