Thank you to u/mBionicBeaver for sharing a ZimaBoard journey that grew from academic experimentation into everyday household infrastructure. Two generations of compact hardware now support work that ranges from family media and documents to automation and shared peripherals. The story shows how a small server becomes valuable through the routines it supports.
The Self-Hosting Day contribution describes the progression and supplies the dashboard screenshot used below. The applications and personal milestones are attributed to that account. Recovery considerations explain the responsibilities created by such a collection of services without inventing a deployment layout or testing results.
A Useful Experiment Can Travel into Everyday Life
The creator first noticed ZimaBoard in 2023, bought the 832 in 2024 and brought it home to Sri Lanka in 2025. Family video playback and Home Assistant gave that earlier academic purchase an everyday role before the newer board joined it.
A computer bought for learning does not need to remain a temporary lab device. When useful applications follow the owner into a household, the definition of success changes. It becomes less about whether a service can be installed and more about whether people can keep using it.
That change is worth recording. Identify which services are experiments and which already hold something a family expects to find. The distinction can guide when to update, what to back up first and how to explain an interruption to someone who does not administer the machine.

Two Generations Create Room for Different Responsibilities
Retaining an earlier machine while adding another generation creates options for organizing services. It does not establish a cluster or a failover mechanism. Those are configurations that would need to be described and tested separately.
The contributor reports a ZimaBoard 832 and a later ZimaBoard 2 1664, with two 6 TB disks mirrored on the newer setup. The account gives a useful progression, while leaving the exact application placement across the two machines unspecified. This article therefore groups services by their household purpose rather than assigning each one to an unconfirmed host.
| Component or service | Role in the story |
|---|---|
| Networking and access | DNS filtering, reverse proxy and private remote connectivity |
| Household applications | Automation, groceries and UPS monitoring |
| Files and knowledge | Photos, documents, notes, books and shared files |
| Media and peripherals | Video, radio, printer and scanner services |
A Household Service List Is Also a Dependency List
Examples in the account include Immich for photographs, Paperless-ngx for a document collection of more than 700 items, Nextcloud for shared files and Actual Budget for finances. These are distinct kinds of retained household information, even when their interfaces sit beside one another on a dashboard.
A family may experience several applications as one continuous routine. A phone uploads a photograph, a browser retrieves a document and a television opens a library. Underneath, each action needs the application, its retained state and a reachable data path.
Mapping those relationships is more useful for maintenance than preserving an application list alone. For one service, record its host, persistent folders, database if applicable and normal client address. Repeat that process for the services people rely on most before documenting every optional experiment.
The contribution includes document management and knowledge tools alongside storage. That matters because a useful archive can contain more than original files. Indexes, labels and application configuration may be part of what makes the collection usable after recovery.
Readers starting with the photo-library role can use our Immich setup guide on ZimaOS alongside the official Immich backup and restore documentation. Immich’s database and the uploaded media are separate parts of a comprehensive recovery copy; a database dump alone does not contain the photographs.
Mirroring and Synchronization Need a Separate Backup Plan
Mirrored storage and synchronized files address useful problems, but neither should be treated as a complete description of historical recovery. Syncthing’s FAQ explains that file changes, including deletion, can propagate between connected devices. Its backup discussion distinguishes that behaviour from retaining independent recovery material.
For a household archive, define what should remain recoverable after an accidental change. Then decide which retained versions and copies provide that result. A second disk or another synchronized device is not enough information to answer the question.
The contributor’s reported storage arrangement is part of the story, while a tested disaster-recovery procedure is not supplied. No claim of validated failover or a guaranteed recovery time is made here. Readers should check one sample restore before relying on their own plan for an irreplaceable collection.
The Syncthing file-sync and data-protection guide develops the synchronization role, while a ZimaBoard 2 NAS with a separate ZimaBlade backup companion provides a community example of assigning backup work to another machine.
Shared Peripherals Can Make Self-Hosting Immediately Useful
Some of the most approachable benefits come from equipment people already own. Making a household printer or scanner available through a server connects a familiar task with infrastructure that might otherwise feel abstract.
That usefulness also creates an operational responsibility. A successful software installation does not establish that a client can print or retrieve a scan after a restart. When reviewing a similar service, follow the ordinary user action through to its result and record which machine and connected peripheral it requires.
The same principle applies to media libraries and document tools: keep the verification close to the task a person is trying to finish. That helps identify whether an interruption belongs to networking, an application, storage or the attached device.
Automation Should Remain Recoverable as the Lab Grows
A home automation configuration can accumulate device integrations and routines gradually. Preserve its recovery information before changing hosts or rebuilding the surrounding service stack. Home Assistant backup documentation describes backup scope, destinations and encryption material needed for restoration.
The screenshot below is an official example, separate from the contributor’s dashboard. It illustrates the choices involved without implying a particular backup schedule in this home. A recovery archive needs an accessible destination and the information needed to use it.
This household perspective also appears in Pi-hole to family server: u/2Hard4Him’s ZimaOS story. IKEA cabinet mini-rack with ZimaBoard 2 shows a different physical arrangement with the same practical need to connect applications to equipment, maintenance and recovery.
Prioritize a small set of recovery checks before expanding the service collection:
- 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 readers planning that service for the first time, the official Home Assistant installation guide explains the available deployment choices. Pick the method that matches the intended host and maintenance responsibilities before copying an application list.
FAQ
Does the original post assign every application to one board?
No. It describes both machines and a combined service collection. The article does not invent a per-host application map.
Does the mirrored disk pair replace backups?
No. The intended recoverable history and independent copies still need to be defined. Mirroring alone does not establish that deleted or damaged application data can be restored.
Is this presented as a tested high-availability cluster?
No. Running two servers does not establish clustering or application failover. Those results would require separate evidence.
Why include printer and scanner services in a homelab story?
They connect server administration to ordinary household tasks. Their value is visible when someone can complete the task through a familiar client.
Conclusion
This story is about a learning machine becoming useful household infrastructure. Its breadth is meaningful because the services connect to photographs, documents, entertainment and equipment already used at home.
The lesson for a growing installation is to preserve that connection: know which routines depend on the servers, keep their data and configuration recoverable, and test the tasks people actually expect to work.
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.



