This document describes the current, single-node Proxmox architecture powering TorresVault 2.0.

This page replaces and supersedes all references to:

• pve1
• pve2
• The old 2-node cluster
• The Raspberry Pi qdevice
• All Intel-based legacy hardware

All of that hardware has been decommissioned.

The sole hypervisor is now:

Running on enterprise-grade Ryzen hardware with TrueNAS virtualized via HBA passthrough, and acting as the centralized compute + storage backbone for TorresVault 2.0.

Future expansions (backup NAS, mini-PC cluster, GPU with Jarvis, Flex 10G, etc.) will be documented on a separate roadmap page.

• Proxmox VE 9.x
• Single-node design (no cluster)
• System name: pve-nas
• Management IP: 192.168.1.153
• IPMI: 192.168.1.145

• 8 × Samsung PM863 1.92 TB enterprise SSDs passed directly to TrueNAS via HBA
• TrueNAS manages all storage pools
• PVE-NAS uses:
  • NVMe mirror → Proxmox OS
  • 1.9 TB SSDs → VM storage
  • ZFS replication & snapshots inside TrueNAS
  • PBS nightly backups

• PBS VM on PVE-NAS
• Writes into pbs-main datastore on TrueNAS

Core services:

• Immich
• Nextcloud
• Jellyfin
• Web landing page
• NPM reverse proxy
• Prometheus / Grafana
• Kuma
• Wiki
• n8n automations

• Home Assistant (external Pi 4)
• BLE tracking
• FPP (192.168.60.55)
• WLED (including car warning system)

This is currently the entire virtualization footprint for TorresVault 2.0.

This is now your single most powerful and consolidated host in TorresVault.

Proxmox sees only the main LAN and storage networks you define.

• VLAN10 – User
• VLAN20 – IoT
• VLAN50 – IoT+
• VLAN60 – Lighting
• VLAN30 – Guest
  (all managed via UniFi)

• 192.168.1.145
  Always available even if Proxmox is offline.

There are three main storage components:

TrueNAS acts as your central storage authority.

PBS backs up:

• Immich
• Nextcloud
• Jellyfin
• Web / Wiki
• Prometheus / Kuma
• n8n
• NPM

Excluded:

• PBS (cannot back itself)
• TrueNAS VM (contains the datastore itself)

Everything is now consolidated on one hypervisor.

Backed up nightly:

• Core services (web, Nextcloud, Immich, Jellyfin)
• Monitoring stack
• Wiki
• n8n
• NPM
• Portainer (if re-added)
• All IPERF lab images (optional)

• TrueNAS VM (contains datastore)
• PBS VM (cannot self-backup)
• VMs with external data stores (e.g., Nextcloud files on TrueNAS)

1. In PBS: pick snapshot
2. Restore to local-lvm or ZFS
3. Boot VM
4. Validate with service health checks

Monitoring stack includes:

• Proxmox UI (graphs)
• ZFS ARC graphs
• IO delay graphs

• Prometheus (metrics)
• Grafana dashboards
• Kuma for ping/HTTP checks

• TrueNAS SMART monitoring
• PBS datastore stats
• Verification/prune jobs

• UniFi metrics
• HA sensors & automations

1. Apps (Immich, Nextcloud, NPM, web, wiki)
2. Monitoring (Prometheus, Kuma)
3. PBS
4. TrueNAS
5. PVE-NAS

1. Network gear
2. PVE-NAS
3. TrueNAS
4. PBS
5. Core apps
6. Monitoring

apt update && apt full-upgradereboot

• Single-node setup (no HA)
• TrueNAS + PBS + all VMs on same hardware = consolidated risk
• No shared storage
• Heavy workloads can spike RAM (currently ~65% used steady)
• Future GPU / AI workloads may require more RAM

These are acceptable for home lab usage.

• Add FLEX 10G for 10GbE uplink
• Build backup NAS with matching SSDs
• Add UM890 Pro mini-PC cluster
• Add Jarvis AI GPU node
• Scale-out TrueNAS pool to 10–11 SSDs
• Offload PBS to dedicated hardware
• Move Home Assistant to a VM
• Add ZFS replication between NAS → backup NAS

Roadmap page will detail this further.