Recent content by bbgeek17

Presumably you saw the IO error somewhere. You should post exactly what you saw and describe where (inside VM, in Hypervisor, elsewhere?). It could be a log snippet, a screenshot, anything that can help describe your situation. For all we know you could have a network drive mounted and had a...

Great to hear! You can mark the thread as solved by editing the first post and selecting the appropriate subject prefix. That will help organize things for other readers in the future. Cheers Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Hi @sgw, Having dealt with MultiProtocol access in prior life with multiple enterprise storage products I can tell you things are not simple there. Each vendor implements permissions mappings differently. Some store additional metadata in the filesystem, others change the model based on the...

Hi @ebarrios08 , welcome to the forum. The error message is produced by Veeam, I would recommend starting with their support to help zoom in on a particular part of the process that failed. I don't know the compatibility requirements for Veeam&PVE off the top of my head. I would recommend that...

Hi @m.gaggiano , welcome to the forum. It seems as you may have omitted the actual complete error from your post. The "I/O" error is a generic symptom. It can be caused by many different things. Please provide an actual error message, system logs around the time of the message (journalctl ...

Thank you for coming back and sharing your findings - they will assist others who run into similar situation. You can mark the thread as Solved by editing the first post and selecting the appropriate subject prefix. This assist with keeping the forum tidy. Cheers Blockbridge : Ultra low...

Hi @nleistad, Confidently attributing the issue to NFS, QCOW, ZFS, network, or any other component requires proper analysis. This typically includes log review, reproducible testing, and potentially network trace reading. There are known edge cases with QCOW on NFS, particularly around...

Hi @Vladyslav , There is no documentation, as far as I am aware, that can guide you to use a non-root account. That said, you can use a tool (for example "govc") that uses the same network/API path as PVE and troubleshoot the connectivity easier than trying to bring up the ESXi storage in PVE...

Hi @Eric Thornton , welcome to the forum. MTU size is not tied to network speed. You can use non-standard MTU values on 1 Gbit just as well as on 25 Gbit or higher links. The key point is consistency: all devices participating in the same network path must use the same MTU. This includes all...

I recommend that you figure out a curl based way to upload a file to local storage with the same account that Veeam is using. Run it local to PVE first, if that works - run it from the Veeam network segment. If that works, convert it to PS command and test from Veeam server. Network issue is...

post your /etc/pve/storage.cfg Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Hi @Bones558 , welcome to the forum. There could be multiple issues that affect your connectivity. For example, you have two interfaces on the same network segment. This will lead to confusion and unpredictable results, like the ones you are experiencing now. Your LACP mode is different...

That really defeats the primary goal of the HA subsystem. Plus it would only work in a managed migration. As you can imagine on node failure there will be no way to either shutdown or live-migrate the VM. If you are only looking to address managed/manual migration - you likely need to create a...

Hi @acsinc , welcome to the forum. Veeam is a partner of PVE and they theoretically have access to PVE support to assist with common customer issues. However, you seem to be a Veeam only customer at this point. You may benefit from the help from a PVE implementation partner - they can usually...

Have you tried 127.0.0.1 ? It would be helpful if you posted your configuration and commands you run here, rather than just reporting the results. The output of these commands in text format and encoded with CODE tags is a good start: pveversion -v uname -a uptime systemctl list-units --failed...