Three ZimaBoards for Proxmox HA, One ZimaBlade for Backups

Eva Wong is the Technical Writer and resident tinkerer at ZimaSpace. A lifelong geek with a passion for homelabs and open-source software, she specializes in translating complex technical concepts into accessible, hands-on guides. Eva believes that self-hosting should be fun, not intimidating. Through her tutorials, she empowers the community to demystify hardware setups, from building their first NAS to mastering Docker containers.

Thank you to u/proxmox2025, the creator behind Syncbricks, for sharing a homelab where three ZimaBoards form a Proxmox high-availability learning environment and a separate ZimaBlade provides backup duties. The division gives each small machine a clear role in exploring service availability and recovery.

The Self-Hosting Day contribution comes from Melbourne and reflects roughly 25 years of the author’s work in IT. The lab continues to evolve, with a separate GPU-equipped Proxmox host opening another area of exploration: local AI and automation.

Three Small Nodes Make Infrastructure Questions Tangible

The creator’s ZimaBoard cluster is used to explore quorum, node failures and service availability. Three independent computers provide a way to investigate what happens when part of an environment becomes unavailable, rather than leaving clustering as an abstract topic.

The author has worked across networking, virtualization, security and cloud infrastructure, but still values the room a home lab provides for experiments. Familiar professional concepts become questions that can be explored on equipment under personal control.

The attraction of compact hardware is part of that experience. A full enterprise rack is not the starting point for this particular cluster. The contribution describes using three ZimaBoards to work with infrastructure concepts at home, while leaving exact board models and their resource allocations unspecified.

The official Proxmox VE feature overview introduces its virtualization, clustering and availability tools. The Reddit account adds the creator’s reason for experimenting with those tools on several small hosts.

A Separate ZimaBlade Gives Backups Their Own Destination

A fourth compact machine has a different responsibility. The contributor identifies a ZimaBlade as a dedicated Proxmox backup server, keeping backups separate from the primary virtualization environment.

This is the clearest architectural lesson in the account. Availability and recovery answer different questions. Keeping a service running when a host fails is one concern; recovering earlier data or rebuilding after a wider problem is another.

The Proxmox Backup Server documentation provides the operational reference for readers investigating that role. The contribution itself does not give the backup device’s storage layout, retention settings or a measured recovery time.

Part of the lab Reported responsibility What remains unspecified
Three ZimaBoards Proxmox HA cluster and experiments with quorum and failures Board generation, RAM, guest allocation and storage design
One ZimaBlade Dedicated Proxmox backup server Backup capacity, retention and restore-test results
Ryzen 9 5950X computer Separate Proxmox host for GPU and AI experiments Final application architecture and workload measurements
Syncbricks videos and courses Sharing installation and troubleshooting experience The older linked video is not a photograph of the current cluster

There is a useful parallel in the Proxbox 360 backup-server story, where an earlier machine receives a separate protection role as a lab grows. The hardware differs, but the act of assigning a distinct recovery destination is easy to compare.

The Linked Video Is Part of the Creator’s Teaching Work

The contributor also runs Syncbricks and links a ZimaBoard video directly in the activity post. The video is titled “ZimaBoard: The Ultimate Single Board Server” and belongs to the creator’s existing educational work.

Original cover of the Syncbricks ZimaBoard video linked in proxmox2025’s Self-Hosting Day story
The original cover of the Syncbricks video linked by the contributor. It is a video title graphic, not a photograph of the current three-node cluster. Source: Syncbricks on YouTube.

The video gives readers a direct route to the author’s presentation of the platform. It should be understood alongside its own publication context. The current cluster’s layout and backup arrangement are described in the Reddit contribution; the cover image alone does not document those details.

Teaching is also part of the motivation for keeping the lab active. The contributor describes hearing from viewers who have built their first homelab or solved an infrastructure problem after following a tutorial. Sharing the work becomes another reason to keep experimenting.

A Different Host Carries the GPU Experiments

The next area of the lab uses a larger Proxmox machine with a Ryzen 9 5950X, 64 GB of DDR4 memory and an RTX 3080 with 10 GB of VRAM. NVMe and SATA storage are also listed. This is separate from the compact ZimaBoard cluster.

The author is exploring Ollama, llama.cpp, OpenClaw, Hermes, n8n, local speech processing and other GPU-related workloads. The longer-term ambition is to combine infrastructure, agents and automation in an environment where local tools can help with development and repetitive work.

Those are directions being investigated. The contribution does not identify a finished agent architecture, a tested model configuration or an inference benchmark. Keeping that distinction visible lets the hardware list explain the experiment without promising a particular AI result.

The separation of hosts also explains the lab’s growth. Existing compact machines continue to support clustering and backups while another computer provides resources for a different class of work. The original machines retain their roles as the project expands.

The Unfinished Questions Are Part of the Value

The account names a familiar collection of problems: Proxmox installation, NVIDIA drivers, boot parameters, GPU configuration and networking. It also raises questions about Ceph versus ZFS replication, network throughput and what happens when a node loses connectivity.

These are questions the creator is working through, not a specification for a completed storage design. The story is useful because it makes the learning process visible, including the decisions that remain open.

Even connecting a detached garage to the home network becomes part of the account. After investigating wireless possibilities, a simple Ethernet cable emerged as the practical answer. That detail fits the broader approach: let a real requirement determine the next change.

Readers can compare another set of explicitly assigned network and virtualization roles in the ZimaBoard pfSense and Proxmox homelab story. Both contributors use their own equipment to understand what the infrastructure is doing.

FAQ

Does the source identify the cluster as three ZimaBoard 2 units?

No. It says three ZimaBoards without specifying the generation or model. The article preserves that description rather than adding a newer product label.

Is the RTX 3080 attached to a ZimaBoard in this account?

The graphics card is listed in a separate Ryzen 9 5950X Proxmox machine with 64 GB of RAM. It should not be attributed to the compact cluster or backup device.

Has the author chosen Ceph or ZFS replication?

The contribution presents that as one of the infrastructure questions being explored. It does not document a final choice or a measured comparison.

Where can readers compare the current compact product range?

The backup device is called ZimaBlade in the original story. The current ZimaBoard SE compact home-server range provides a product reference for readers considering a separate new build; the original contribution does not specify the backup unit’s SKU.

Does the story report failover or restore timings?

No measured failover time, recovery point or restore time is supplied. The account explains the machines’ responsibilities and the concepts the creator uses them to investigate.

Conclusion

proxmox2025’s lab gives compact Zima hardware clear responsibilities: several nodes for availability experiments and a separate machine for backups. A larger GPU host then adds another place to explore local AI without changing those earlier roles.

The contribution connects practical experiments with the habit of sharing what was learned. After years in IT, the creator still finds value in building, troubleshooting and learning how to recover the services they run.

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

Get More Builds Like This

Stay in the Loop

Get updates from Zima - new products, exclusive deals, and real builds from the community.

Stay in the Loop preferences

We respect your inbox. Unsubscribe anytime.