Thank you to u/casareanderson for sharing a ZimaBlade and ZimaOS homelab built around family photos, everyday services and the patience to investigate things that stop working. Immich gives the household a photo library, while separate machines provide room for other applications and local AI.
The original Self-Hosting Day contribution describes both the useful services and the mistakes behind them. Companion projects under the same casareanderson GitHub account add diagnostic images and backup notes. Together, they make this a story about learning to operate a home server, with one GPU experiment still unfinished.
The ZimaBlade Has a Defined Job in a Larger Homelab
The setup separates storage from much of the application stack. That gives the small NAS a clear place in the household without making it responsible for every experiment.
| Part of the setup | Reported role |
|---|---|
| ZimaBlade with ZimaOS | NAS and Immich family photos; 5.5 TB RAID storage and Backblaze backup |
| Two Proxmox machines | Home Assistant, Vaultwarden, Uptime Kuma, CrowdSec and other services |
| Older Pop!_OS computer with a GPU | Ollama and local AI experiments |
| Authelia | Single sign-on in front of services |
For another builder, this division offers a useful planning question: which machine owns the data, and which machines can change around it? A storage host and an application host may need different maintenance windows. Making their responsibilities visible helps someone decide what a reboot will interrupt before making a change.
Our small homelab story from u/jc-21 explores another arrangement of compact machines. The comparison is useful because a service inventory can explain hardware choices more clearly than a device count alone.
DNS and Duplicate Addresses Made Healthy Services Look Broken
The creator reports nearly 40,000 dropped AdGuard queries. A migrated container also remained active on its old host with the same IP, MAC and name. Separately, a smart bulb occupied Vaultwarden’s address, contributing to confusing availability problems. The creator subsequently assigned static addresses.
These incidents give the story its practical value. A failed connection is a symptom with several possible causes: the destination may have moved, name resolution may have failed, or the application itself may be unavailable. Checking those layers separately is more useful than repeatedly restarting the service named in an alert.
AdGuard Home’s configuration reference documents a rate limit with a default value of 20 queries per second and says excess queries are silently dropped. It also documents subnet settings used for rate limiting. That context matters: the original comment’s description of a per-device limit should not become a universal explanation of how every version and configuration counts requests.
A sensible check is to compare client failures with the resolver’s settings and activity at the same time. For a migrated service, confirm which instance should own its address and whether the old instance is still running. Static addressing also needs coordination with the router’s allocation range; an address written into a container is only part of that plan.
A Family Photo Library Needs Its Files and Its Database
Immich makes the storage project meaningful to people beyond its administrator. The planning question becomes concrete: if this host stopped working, what would be needed to bring the household’s collection back?
Immich’s backup and restore documentation explains that comprehensive protection includes uploaded photos and videos together with the database. The database holds paths and user metadata; a database backup does not contain the media files themselves. Conversely, keeping image files without preserving application state is not equivalent to recovering the same working library.
The official documentation also recommends a 3-2-1 strategy. For someone evaluating their own installation, the useful exercise is to identify the media location, the database backup, the independent destination and the recovery procedure. A RAID capacity figure answers a different question from whether those copies can survive an accidental deletion or a failed host.
The creator’s companion recipes distinguish offsite copying from deletion-mirroring synchronization. That distinction fits a photo archive: an unwanted local deletion should not silently become the only state retained elsewhere. The repository describes its intended process; this article does not supply a measured recovery result for the family’s full collection.
The related Pi-hole-to-family-server ZimaOS story examines the same transition from experimenting with apps to looking after household data.
An Archive Can Exist While Important AppData Is Missing
In the companion repository, a small reproduction shows a protected TLS directory being omitted from a tar archive. The command returns an error but still leaves an archive file. The example is reproduced on Linux with sample data; it is not evidence that the creator lost those files from the production photo server.

This is a helpful distinction for backup reviews. Finding yesterday’s archive proves that a file was written. It does not, by itself, prove that the expected application state is inside it. Completeness, readability and recovery are separate checks, and each deserves an observable result.
The repository’s second image shows a backup dry run on a ZimaBlade 7700. In that particular run, every checked AppData directory was readable. The image also lists application definitions separately from AppData.

For a reader, the useful takeaway is to inspect what a backup includes before relying on its filename. Keep that inspection separate from a restore rehearsal, which answers whether the saved state can actually be used.
The Quadro P600 Experiment Is Still a Work in Progress
The GPU field report documents a ZimaBlade 7700, a Quadro P600 and a powered riser. Its status remains unfinished: the card can appear and work before disappearing from the PCIe bus until a reboot.

The output separates several observations: the hardware is visible, the driver reports a failure, and the shown Immich machine-learning container uses a CPU image. These observations describe different layers. The image is valuable precisely because it records the unresolved state rather than presenting a finished acceleration result.
Immich’s machine-learning acceleration documentation describes support for tasks such as Smart Search and Facial Recognition, with backend-specific requirements. A compatible GPU, host driver and container setup all matter. Machine-learning acceleration also needs to be distinguished from video transcoding; success with one workload does not establish the other.
That makes the field report useful as a record of investigation. It does not provide a stable P600 configuration or a performance benchmark to reproduce. Anyone considering similar hardware should evaluate the current application requirements and their own machine before spending money on an expansion card.
Small Improvements Keep the Lab Connected to Everyday Life
For Self-Hosting Day itself, the creator flashed an ESP32 as a Bluetooth proxy for garden-room LED strips. It is a small addition compared with the photo server, but it serves a clear household purpose.
The story’s common thread is learning enough about each dependency to explain a failure. A DNS setting, an address conflict, an archive’s contents and a GPU’s runtime state all become easier to investigate once they are treated as specific questions.
For readers exploring current compact hardware, the ZimaBoard SE product page lists today’s configurations under the newer name for the ZimaBlade line. The hardware described in the source remains the creator’s original ZimaBlade.
FAQ
Where can I read the original story?
The Self-Hosting Day comment is the starting point. The linked GitHub projects provide additional technical context and the original images.
Are the illustrations photographs of the hardware?
They are repository-provided diagnostic text images. The captions identify the reproduced example, dry run and GPU capture individually.
Does the P600 project demonstrate stable Immich acceleration?
No. The field report marks the build unfinished and describes the GPU disappearing from the bus.
Is a backup dry run a completed backup?
No. It checks the proposed operation. Creating the backup and testing recovery require separate steps.
What does Immich require for a comprehensive backup?
Its official documentation calls for both the uploaded media and the database. Preserve the relevant configuration and follow version-appropriate restore instructions as well.
Conclusion
This ZimaBlade homelab connects family photos and useful services with an honest account of what takes work to maintain. The unresolved GPU experiment belongs in that account too. Understanding the state of a service, keeping recoverable data and documenting what happened give the next experiment a stronger starting point.
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.



