Recent content by Eduardo Taboada

Do yo need to go to the Datacenter -> Storage and then in the Proxmox Backup Server settings, set the storage with encryption

I have same version with a lot of 5 node cluster and no failures in VM count. When you add a remote, do you add the entire cluster or nodes itself? If you add nodes tree times, you will see 3 instead of 1 VM. In my case for VM 725 running, 32 stopped, 74 template - total 831 with 40 nodes in 5...

VyOS is a Debian based router, so you don't have limitations in VirtIO drivers, but I doesn't test performance of VyOS used for another use case than routing, and the performance in routing is not the same as use it as a firewall.

1) the bridge is the correct? 2) you can ping the LXC? 3) try to do a pct enter LXC-number and show listening ports (ss -nltp)

Are you booting BIOS or UEFI?

Read this post: https://forum.proxmox.com/threads/pci-passthrough-fails-on-boot-with-dmar-error-read-access-is-not-set.67074/ "I think it's related to the fact that this card can work in both RAID and NON-RAID (Passthrough) modes. When IOMMU is enabled it doesn't see your raid configurations...

This thread may help you https://forum.proxmox.com/threads/migrating-proxmox-ha-cluster-with-ceph-to-new-ip-subnet.165537/

Is a good practice to separate Ceph data traffic in another interface or almost another VLAN and use 10 Gb or more for this traffic, You should keep in mind that modern SSDs have a very high transfer rate and need a network to match this requirements.

To know which is the cause of this problem: Do you have a separate VLAN or network for Ceph? Check the network interfaces for errors, and also the smart values of disks

Is not a critical error, blueStore has recovered the failure, and the cause can be a puntual problem with the network, or some hardware element (controller, disk) but it appears to be for a low response of these OSD. To remove the warning: ceph config set osd...

There is no reason to loose backups, because you only are moving the storage network, not the storage itself. I mean, for example if you put another PVE and add storage pointing for this datastore yo can see all the backups of the first PVE. The network has no effect in the storage, is only the...

This may help you https://forum.proxmox.com/threads/osd-have-spurious-read-error.100443/

Do you have another device on these IP's?, try to execute arp -a If you find two ip with the same mac address, you have to devices with the same IP

Sometimes RAM errors in fact can be due a power supply failure. RAM needs precise voltage to reliably store data; too low voltage causes data corruption and may be the cause of the problem also.

iperf show performance in a short time, but as i told, if the buffers of the network equipment collapse the speed will be reduced. Also will be a reduced time if the destination PBS cannot write so fast. I experienced the buffer collapse with mikrotik switches a few weeks ago with a customer