Well I found a way! Since now formally arm is supported I tried again. And this time I got it to work. Cloud flare tunnels would probably work @yankluf.
I have been working on a writeup blog article. Have a look if you are curious...
Hi Everyone,
Every few months someone asks some version of "why can't I use LVM-thin on my shared SAN LUN?" Thick LVM works fine as shared storage, but has no native snapshots. LVM-thin has snapshots but is local-only... it's natural to wonder...
Yes. Your choice to keep your "franken-cluster" :) or go for a better manageable / supportable configuration. I would remove Ceph and use ZFS replication, but don't want to lecture anyone or take the thread off topic.
I would add PVE to that PBS...
@tschmidt @kanemari I would remove the custom mon and install PVE on that external host/VM, add it to the cluster and use PVE Ceph integration. If that extra mon is running inside the cluster, get an external host.
@kanemari if I were you I...
Recent security findings and fixes in Ceph make it necessary to upgrade ceph and migrate authentication keys from the aes to the aes256k cipher. This is to address weaknesses in the old Cephx authentication method, especially if your Ceph service...
There's probably a saying that exists in every country - if you have nothing good to say, dont say anything.
Ive read the pages there a long time ago and, as mentioned, tried the fixes. There's still people in that thread encountering the issue...
We are pleased to share two major milestones that will help us better serve our customers and partners worldwide.
Global 24/7 enterprise support
Starting October 19, 2026, Proxmox Enterprise Support will be available around the clock, 365 days a...
Because we could suppose that there is no support, which seems more or less expected given the way QEMU creates backups, but we we can as well think that there is no problem running different backup solutions given that no vendor or PVE docs...
Sorry, I don't understand what you mean with that.
I'm asking about the official support of Proxmox PBS to do backups of QEMU VMs in a PVE cluster that is also backed up by other backup solution (Hornet, Veeam, Nakivo), whether of the same VMs...
Which is the official support status of doing PVE QEMU backups with PBS and other backup solutions?
Specifically, would like to know the support status from Proxmox PBS for:
Veeam
Hornetsecurity (Altaro)
Nakivo
There are a few use cases that...
There is now a newer pve-manager with version 9.2.12 available on the pve-test repo and a backport of that as 8.4.22 for PVE 8's pvetest repo, matching our respective test repo of the ceph-squid and ceph-tentacle releases.
There is some better...
This should be the same for VMs and CTs as the HA Manager handles affinity rules the same for both. In a quick test, the migration blocker with the same node affinity rule as above was shown to me for both VMs and CTs, so I couldn't move either...
It should not let you migrate neither the CT nor the VM. If it did, once you migrate a VM from pve-4 to pve-2, in the next ha cycle (~10 seconds) HA would say "this VM on pve-2 has another node with higher priority and the node is up, let's...
This can be done gradually, but needs a bit of care. We're currently in the process of finishing a migration helper tool and providing documentation for how to do this.
@yangsm AFAIK, Ceph 20.2.4 / 19.2.6 packages are only available in Test repository, you should avoid using it unless for testing. Proxmox is working on the process to rotate the keys [1], although we still don't know the details, on paper it...
You right, somehow I understood that there are SSD for OS but not SSD to dedicate to SD, so imagined that OP wanted to devote some space on those SSD for SD.
This is only HDD, zero SSD. (As of #1)
Having a "separate" Special Device on the very same spindles makes no sense.
Actually we know not much at all. What actual drives are available? How many? How many (unused) connectors has the controller...