Recent content by VictorSTS

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 states otherwise. I haven't found any specific mention...

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 or different VMs for each backup software.

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 may affect this: Backing up the same VMs with...

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 migrate it to pve-4" and the VM would be moved back...

@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 should be possible to rotate the keys without...

I'm not aware of a bug that won't allow install, mind posting a link to some reference?

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.

I would put the RAID controller in JBOD / IT mode to convert it to an HBA, the use ZFS for both the OS and special device. Remember that ZFS isn't supported on RAID controllers/LUNs. When installing PVE/PBS, set the disk size to ~50G, should be enough for PBS, even after some time (PBS may need...

Yes, but not every single time. Depends essentially on the size of the datastore, how much work PBS has to do (i.e. backup once a day vs once an hour, many replicas, many verify, etc), and how much time you have to run GC, which is the task that really requires an special device. I.e. I don't...

Yes, but there should be a "Hit:" line for every repo. Maybe OP didn't post the whole apt update output. Edit: we posted at once :)

In the apt update output above I'm missing a line referencing Proxmox repositories, although the apt list --upgradable does indeed show upgradable Proxmox packages. Are you sure the Proxmox repositories are correctly configured?

Check this point of view: there's no ZFS without ARC: it's and inherent part of ZFS architecture and ZFS performance is designed around it, so you do relay on it and expect it to behave correctly to get the most of your ZFS. Like why not raise all sails on the boat to make it faster. Something...

Finally got a chance to check on this. The problem seems to be related to a recently reported bug [1] that causes ARC to evict all/most of it's contents erroneously, even when there's plenty of RAM available. This causes ARC to almost never reach it's arc_max setting, even less to keep it...

That's good news, but remember that you are using an unsupported storage stack that will sooner or later give you some issue that no one will be willing to investigate / fix. Take your time to rebuild your storage to a proper ZFS setup, which might be as easy as configuring the RAID controller...

My option is: Install PVE using ~50G with a mirror of SSD. Leave the rest unused. Coinstall PBS (add repo, add package) [1]. From PVE, add a RAIDz/RAID10 (capacity vs performance decision, although on that hardware won't be too relevant). Could use CLI, but avoid the temptation to use /dev/sd*...