Search results

we did end up deleting all snapshots with failed verification, using a combination of oneliners and manually. unfortunate the one liner is lost in the bash history.

Hello I am trying to create a DR setup with a second proxmox cluster. the idea is that all vm's from primary cluster is regularly replicated to this secondary cluster, and sit's ready to boot on demand. The clusters have shared lvm storage on multipath Fiberchannel SAN. the first proxmox...

is there a way to quick and easy delete all backups that have missing chunks ? GC fail with non-exsisting chunks all the time. and the vm's are unrecoverable anyways.

when a large vm is powered down, and have not been powered on since the last backup. Reading the whole disk without the running dirty bitmap can be quite time consuming, even if the actual backup transfer is 0. is there a way to skip reading this large disk for every backup run without having...

awesome thank you, upgrading is on the roadmap

could certainly be too old version proxmox. (5.4-2) # pveversion -v proxmox-ve: 5.4-2 (running kernel: 4.15.18-25-pve) pve-manager: 5.4-13 (running version: 5.4-13/aee6f0ec) pve-kernel-4.15: 5.4-16 pve-kernel-4.15.18-27-pve: 4.15.18-55 pve-kernel-4.15.18-25-pve: 4.15.18-53...

Does not connect. just shows: "API Error" 401: no ticket. Tried with both PVE and PAM user. EDIT: It seems that it works on a proxmox node that have an legacy ip address as well as an ipv6 address. (dual stack) allmost all of our proxmox servers are ipv6 only.

seems to fail on pve 5.4 pveversion pve-manager/5.4-11/6df3d8d0 (running kernel: 4.15.18-18-pve) root@node-b:~# sha256sum libhttp-daemon-perl_6.01-2.1_all.deb dfcc4b4d03857c10c2f2dbef42ffd2921d9c478207d2fd8f6f0fbddfa0f7d939 libhttp-daemon-perl_6.01-2.1_all.deb root@node-b:~# dpkg -i...

thank you ! it is a crutch until they fix the bug :) Ronny

I see the same issue as dotsam. the socat trick works, but i assume it will fail on renewals ?

if you do need a simple NAS style storage you can do what i do. 8 nodes with some SSD OSD for vm RBD images, and some large spinning osd's for slow storage. using the osd classes i can place pools on either ssd or spinning disk. i have these pools rbd 3x replication on ssd cephfs-metadata...

most of my installs use lacp, but in this case i do not have control of that part. The servers are in a blade chassis where the blade switches does not have mclag, and i was trying to replicate the vmware way where vm's are split across the 2 switches with a form of switch independant bond...

i have a problem with ipv6 networking on my guest vm's. The vm show a message saying IPv6: ens18: IPv6 duplicate address [link local address] detected! on boot or when i up the interface. My googeling led me to a thread where it was claimed that bonding with the round robin method could cause...