I would move PBS to the PVE environment since your just dumping data on the NAS anyways. At least then it’s replicated. Don’t forget to backup your encryption key.

minfree Defines the amount of free space left in the LVM volume group pve. With more than 128GB storage available the default is 16GB, else hdsize/8 will be used.

This is space to leave behind for snapshots. They suggest 1/8th the size of your hard drive.

I'll try and make a cleaner guide later..

First, spin up your ProxmoxVE system. During the install wizard, I left the boot drive as LVM but did change it to XFS instead of ext4. You do not setup secondary drives during the install wizard. Once up, you need to create the ZFS store on each system, named the same, prior to joining the cluster. The replication process wants the ZFS pool to be named the same on both systems and you cannot name it the same (at least in the GUI) if it already exists anywhere in the cluster.
3c9d3871-d8f6-4da0-93fd-22bf8526ef6b-image.png Then from the GUI, go to the disks of system 1.
67ae2a41-d84b-4fbc-9cd0-4dea04cb5465-image.png then click on ZFS and create the storage pool name it, single disk, compression off.
4379c8d3-edf1-4733-95ce-d3bc5f2400e9-image.png wait for it to show normal.
145f1381-2d1e-4215-b29c-30e2227c00d2-image.png then repeat the process on the second system. make sure to use the same name. Now create the cluster and join the second system to the cluster.
e9401472-ad68-433a-b569-5cc14f21552d-image.png You will not see the storage on ZFS storage on system 2 when it first loads up.
0e6e610a-21fd-4317-9f15-336eec787af3-image.png But it does exist if you look.
d5efc711-8126-4e30-955a-9d0deba7db10-image.png To make it available, go to storage under datacenter.
545a0b08-72e0-4912-bf3c-f10ce2527d73-image.png edit the existing "data" and add pve2
d8022847-45ea-46ce-be11-807f01e51449-image.png now it will show up and be available for use.
a68a5b5c-3024-4650-869b-c36065713c87-image.png

Is this perfect? No. but it is how I was able to get it setup to work.

The manual leave out quite a bit of specifics. on how to do things, but goes into detail on the technical of things.

@DustinB3403
I don't doubt it.
There wasn't really any added complexity though. PVE was installed with all the defaults.

It definitely seems joined. I cannot even do anything form the IP of the second instance now.
c0a3fa85-5326-4648-a318-08221c193f5a-image.png

But it is all enabled from the primary.
e0e8003c-9e55-44b2-9914-93dd29ab656f-image.png

@JaredBusch said in Proxmox pricing:

@stacksofplates said in Proxmox pricing:

but users on your LAN need a link or some way of knowing it exists

Users of the things running on it do not.

If they're interacting with the hypervisor. Not like windows users. But anyone using the hypervisor would. Should have been a little clearer.

@marcinozga said in Proxmox initial setup annoyances:

You may have to clear browser cache to fully get rid of the nag. Mine kept coming back, clearing caches got rid of it.

I run this prior to ever opening the web interface, so never an issue.