Recent content by hellfire

Ah. Thanks! I did not realize, that a simple SSL Cert fixes this. But one moment, the pbs here is accessed by private ip addresses. So ACME is no option here. A Wildcard-ACME-Certificate may be an option.

WARNING This procedere is not as intended and breaks the man in the middle protection! Use at your own risk! I have an issue that fingerprints of pbs keep changing with every new version and backups do no longer work due to unverified fingerprints. From what I've read, this is intended...

It is still marked as experimental in the man-page of qm: https://pve.proxmox.com/pve-docs/qm.1.html (See remote-migrate).

Yes. Shared Storage is when all nodes have access to the same Storage, like Ceph, GlusterFS (never used that), NAS or "Shared Nothing" like DRBD (=not supported out of the box by Proxmox). If shared storage is not available, Disk mirroring will be done too. Not having Shared Storage means, Live...

I just had a strange issue with Proxmox Backup Server. # proxmox-backup-manager versions proxmox-backup-server 3.2.9-1 running version: 3.2.8 The situation was: The storage was offline (grey question marks in admin interface) The storage could not be accessed (Error message something like...

I had errors with this too. My error had been, that the Authorization-Data was not correct: I also used PVEAPIToken instead of PBSAPIToken I used = instead of : as the separator between TOKENNAME and TOKENSECRET So I recommend to carefully check the Authorization token on such error...

Hi, I just played around with LinStor/DRBD/PVE and the size issue has a workaround now. If one wants to move a disk online to/from linstor-storage, one has to set exactsize yes Option temporarily in /etc/pve/storage.cfg. This needs the latest linstor-proxmox Plugin. This concerns at least...

Nachdem ich das Problem auch gerade habe und auf der Suche bin, habe ich diese mögliche Lösung gefunden ... Übersetzt: Du musst das manuell umsetzen: Das ZFS-Dataset löschen (zfs list; zfs destroy -r ... ) (Tip: Gut aufpassen, und doppelt prüfen, dass man das richtige Dataset erwischt! ;) )...

Some Experiences for the topics in question here: a) DRBD / LinStor I personally used to operate DRBD on two clusters for some time. I found it quite an effort to keep it up to date, since it is not tighly integrated within Proxmox VE. The experience was, that the drbd lost it's sync now and...

Just keeping it as it is, is ok for me.

Yes, @leesteken, that's about MIGRATION. But my concern is REPLICATION. I do not read anything specifically about storage replication there.

Hi, I have a cluster with 3 Nodes (2 full nodes, 1 quorum node as virtual server). Software is latest pve-non-subscription repository for version 8.2.4 (updated yesterday). I configured ZFS-Replication for VMs and it works fine. What I'm wondering is, that the replication does not use the...

Here's a quick and dirty script, which parses and analyzes the proxmox VE dump log files on a node. It prints id, name and type of the object beeing backed up, the data transferred, if a dirtymap existed, the average speed of the transfer and the duration of the backup of container/vm and the...

Hi, I sometimes have an issue with backups. Some virtual machines are still locked after the backup job run. Maybe this is linked to an automatic restart job, which restarts virtual machines when they get stuck. So not to end up with unmanageable locked vms I scheduled an unlock script, which...

Hi, I just did an upgrade to hyperconverged PVE-Cluster with Ceph. From Proxmox VE 8.1 -> 8.2. I noticed "Ceph" complained about crashes in its health status - I just rebooted the nodes after evacuating the VMs. So I upgraded 2 of 3 Cluster-Nodes. I also missed to set noout before the reboot...