Search results

dmesg -T: [Fri Mar 4 13:24:04 2022] [ 155799] 0 155799 648872 468354 4890624 0 0 proxmox-backup- [Fri Mar 4 13:24:04 2022]...

proxmox-backup-client version client version: 2.1.2 Client for Rocky 8 is from https://github.com/sg4r/proxmox-backup-client Starting backup: vm/NAME/2022-03-04T12:12:34Z Client name: NAME Starting backup protocol: Fri Mar 4 13:12:34 2022 Using default encryption key.. Encryption key...

Hi, we currently test proxmox-backup-client and experience that the backup of all VM with a memory <= 2GB fail due to a memory issue. Fiddled around with --entries-max 524288 and --chunk-size 2048 with no success. I have read that the size of chunk is crucial for performance, so we would not...

Okay, clear. Thank you. :)

Hi, currently, we evaluate Proxmox Backup Server. We have some dozen server that needs to have backups on a file level. For that we use proxmox-backup-client. We experience, that without a key all backups are accessible from all server which is bad. So we started to use encryption. Then the...

A way to put the key from a server backup (proxmox-backup-client backup ... --keyfile ... --repository ...) on the backup server into the GUI or somewhere else would be very nice to be able to browse also encrypted backups. Is that realistic to hope?

Thank you, we did this several times :-) It turned out that it was a side effect in our 10G Unifi switch where the IP address of the MAC was doubled in the ARP table. Removing the redundant entry solved every problem. On earth. Things are really nice now :-) Thank you for taking care!

Hi, we just upgraded our three node cluster from 6.4 to 7.1. This went fine as an In-place upgrade. On this occasion, we took a closer look at the log files and found these three occurrences in a row. We also looked into old log files, it was there too. So it has nothing to do with the upgrade...

We solved it by removing the (disabled!) replication job for this vm.

We have a cluster with two nodes for testing PVE 7. The qcow2 images (virtio0 and ide0 for cloudinit) are on a shared nfs storage. Migration form on node to the other fails in this scenario: root@node2:/etc/pve # qm migrate 112 node1 --online 2021-10-22 22:32:37 starting migration of VM 112 to...

We provision our CentOS 8 kvm template with kickstart which works fine. We clone with cloud-init of Proxmox. Now we want to add an Ubuntu template. Ubuntu uses now and in future "cloud-init" autoinstall (https://ubuntu.com/server/docs/install/autoinstall) Ubuntus new autoinstall works quite...

Hi, we want to replicate our machines every 15 minutes. We scheduled the replication before every two hours: */2:00 Now we want to switch to each 15 minutes but not from 0 to 6 o-clock: mon..sun 06..23:0/15 This works but we do not understand the ':0' part in the pattern. What is the meaning...

Hi, we have a Centos7 template with cloud-init integration. cloud-init is awful ;) but it does what it should do. We face just one problem which we could not solve till now. It is the automatic configuration of nameserver in resolv.conf. Our cloud-init template has a nameserver in resolv.conf...

Danke, der Kernel scheint das nfs-Problem zu lösen. Wir beobachten das Thema weiter. Wir wüssten auch gerne, was die Ursache für das Problem war. Könnten Sie das Problem und die Lösung bitte kurz erläutern?

Hallo, wir haben die aktuelle pve-Version im Cluster installiert und Probleme mit den nfs-Shares bekommen. Sporadisch waren die nfs-Shares nicht mehr zu erreichen. Beispiel: Oct 16 23:03:05 server pvestatd[2210]: unable to activate storage 'backup_pve_vm' - directory '/mnt/pve/backup_pve_vm'...

Wir hatten einmal den Effekt bei einer Maschine, dass das Erkennen des zfs einen Moment gedauert hat. GRUB_TIMEOUT=5 in /etc/default/grub hatte das behoben.

Hallo BobX, wir haben mehrere Installation mit Proxmox, eine davon bei Hetzner und dort nutzen wir die Firewall. Am Anfang haben wir auch gestaunt, warum das nicht geht mit der Firewall. Aber nachdem wir alle Glaubenssätze über Bord geworfen haben und die Doku und Forenbeiträge in Ruhe studiert...

We are experiencing the same problem. Is there any progress?

Versuche auf einen anderen zpool zu migrieren oder ein neues Storage-Image zu erstellen scheitern auch während ein Replication Task läuft. Migrieren wir auf ein nicht-zfs Storage oder erstellen in einem nicht-zfs Storage ein Storage-Image, funktionierts. Ist also zfs bezogen, ein Lock der beim...

Wir glauben das ist die Ursache des Problems: Der Effekt tritt nur auf, wenn ein Replication Task aktiv läuft. Läuft keiner kann Storage in den zpool migriert werden. Auch neue Storage-Images für VM können nicht erstellt werden, wenn ein Replication Task läuft. Das wirkt wie ein Bug, oder?