← sources

Mikrotik homelab 45U

source: reddit (reddit:homelab)published 2026-11-13 05:18ingested 2026-11-14 02:40

retained text

**TL;DR:** MikroTik RB1100AHx4 router, three switches (24-port PoE, 24-port Linksys, 16-port Ruijie) serving 16 IP cams, 16 Mikrotik APs, Raspberry 5 Home Assistant, and a single Proxmox host running a handful of LXCs for file management, web hosting and a few apps. I recently reworked the storage so any container can read the same data, with nightly rsync + ZFS snapshots to a second disk.

**## Network**

* Router: MikroTik RB1100AHx4 (13x GbE, quad-core). Handles routing, firewall, static DNS, NAT and a WireGuard tunnel to a small VPS.
* Switches: 24-port PoE switch, 24-port Linksys, and a 16-port Ruijie.
* Remote access: a Caddy reverse proxy on the VPS (Let's Encrypt) forwards over WireGuard to services at home, so I don't expose my home IP or open inbound ports.

**## Proxmox host**

A small SSD pool (LVM-thin) for container root disks

A 4 TB HDD (ext4) for data

An older 4 TB drive formatted as a single-disk ZFS pool, used only as the backup target

**## What's running (all LXC)**

*| CT | Purpose |*

*| Ubuntu-web | aaPanel + nginx, a few sites |*

*| Debian-file | FileBrowser Quantum, Samba (for iOS Files), Syncthing (Mac backups) |*

*| Debian-go | a small personal Go app |*

*| Debian-list | OpenList, to browse local folders and cloud storage (e.g. Dropbox) in one place |*

*| Debian-frigate | Frigate (testing) |*

**## Storage design (the part I'm happiest with)**

I used to keep data inside each container's raw disk image. That meant only one container could use it, the image never shrank after deleting data (a 2 TB image held about 360 GB of real files but took 600+ GB on disk), and backups were painful.

Now the data lives in plain folders on the host's HDD and is *bind-mounted into whichever LXC needs it*:

* FileBrowser / Samba / Syncthing mount it read-write.
* OpenList mounts the same folder (and my web root, read-only).
* No SMB/NFS in between, so it's as fast as local disk.

**## Backups**

* Nightly \`rsync\` from the data folders to a ZFS dataset on the second disk, run with \`nice\` / \`ionice\`.
* A ZFS snapshot after each run, keeping the last 14, so accidental deletions are recoverable via \`.zfs/snapshot/...\`.
* The script refuses to run if the source or destination isn't mounted, so \`--delete\` can't wipe the backup.
* Vzdump now only covers the (tiny) container root disks.

**## Lessons learned**

* Don't use vzdump "stop" mode on a container holding a multi-TB volume. It shuts the service down for hours.
* A bind mount silently disappears if you reuse its \`mpN\` slot. Use the next free number.
* Run long jobs through \`systemd-run\` or tmux, not a browser console tab. A plain \`nohup rsync\` got killed when the tab closed.

**## Next**

* An off-site copy (cloud or a second location), since my backup disk is a single old drive.
* Monitoring and alerting.



Any suggestion what other services I should on my Proxmox?

document fetched 2026-11-14 00:39 · canonical https://reddit.com/r/homelab/comments/1xuzbvm/mikrotik_homelab_45u