Recent content by weehooey-bh

@bravo0916 Not sure. What I can tell you is if you are going to find some information about capability, Ubuntu is the place you will find it.

Hi @bravo0916 Sorry, I gave you an incomplete answer. PVE is based on Debian with a Ubuntu kernel. There isn’t a Debian HCL but there is some compatibility information available from Ubuntu. Others have asked similar questions: https://forum.proxmox.com/threads/compatibility-matrix.168096/...

Proxmox does not publish hardware compatibility lists (HCL). Under the hood, Proxmox products are Debian. If the NIC will work with Debian, it will work with Proxmox products. We have found that Intel is a very reliable network interface card manufacturer.

Right now, restores are not included in the built-in notifications. As a starting point, you could monitor journalctl for restore entries and act upon that event (i.e. send an email). /usr/bin/journalctl -f -n 0 | /usr/bin/grep --line-buffered "vzrestore" Hope this helps.

Carefully read and follow: Corosync Redundancy

Yes, you can configure up to eight (8) separate Corosync links. Just make the primary link (link 0) entirely separate from all other traffic.

There are different types of "cluster" traffic. By default, it all goes over the host network. Corosync is not migration traffic; the Corosync traffic should be moved to its own network. You can leave the migration traffic on the host network to take advantage of the 10G link. Setup your...

No worries. Perfect! Corosync is what makes a cluster work. You will be unhappy if your Corosync is unhappy. :) Cluster Manager

You are asking a lot from a single forum post. Since we became a Proxmox Training Partner, we have noticed that our clients fall into one of two broad categories: Those who have taken the Proxmox VE Training. Those who have learned Proxmox VE on their own. Those who have taken training...

You have left out important information. Are your drives NVMe, or are they slower? If you have NVMe, Ceph could choke your other traffic. In most cases, the host and guests (VMs and LXCs) will not saturate a 10G link, but Ceph can. If this is a production environment (i.e. not a lab or home...

Thank you for sharing the video. I had not noticed that exact behaviour before. I have checked on multiple clusters, and it does appear that you can only select one node or all nodes. You will need to create one backup task for each node. It's not ideal, but it will achieve what you want to do.

Looking at your storage.cfg, it appears -dc1 and -dc2 in the PVE hostname corresponds to -jdm and -sta Node pve01-dc3 is not included in the storage definition for bkp: nodes pve02-jdm,pve01-jdm,pve03-sta,pve04-sta Your backup job vzdump: backup-1fd712c4-51a3 is set to run on all your nodes: all...

Okay. Then provide the full output of cat /etc/pve/storage.cfg If you cannot select the nodes in the Create: Backup Job dialog box, then it is likely you have an issue with your storage configuration.

You can do that with the backup. PVE is telling you something is wrong when accessing bkp on node pve01-dc3. Please post the output from this command: cat /etc/pve/storage.cfg | awk 'BEGIN{RS=""} /^bkp:/' It will output your cluster storage configuration and filter for the bkp storage...

Please post your VM's configuration in oVirt and PVE. In PVE, you can get it by running the following command (on the same PVE node as the VM), replacing <VMID> with the VM ID of the VM: qm config <VMID>