Hi @Link State . Thanks for sharing. So, for clarification, the error is both in the Oracle LVM Plugin as well as Proxmox? Proxmox isn’t officially GA yet, so that shouldn’t be too big a deal..though good to know Veeam is addressing it there as well.
coolsport00 wrote:
Hi @Link State . Thanks for sharing. So, for clarification, the error is both in the Oracle LVM Plugin as well as Proxmox? Proxmox isn’t officially GA yet, so that shouldn’t be too big a deal..though good to know Veeam is addressing it there as well.
Yes the Proxmox VE plugin is in beta and is affected by this kind of bug, as @DChiavari informed me in the link in the VUG Italy.
Link State wrote:
coolsport00 wrote:
Hi @Link State . Thanks for sharing. So, for clarification, the error is both in the Oracle LVM Plugin as well as Proxmox? Proxmox isn’t officially GA yet, so that shouldn’t be too big a deal..though good to know Veeam is addressing it there as well.
Yes the Proxmox VE plugin is in beta and is affected by this kind of bug, as @DChiavari informed me in the link in the VUG Italy.
Ok, thanks for clarifying.
coolsport00 wrote:
Hi @Link State . Thanks for sharing. So, for clarification, the error is both in the Oracle LVM Plugin as well as Proxmox? Proxmox isn’t officially GA yet, so that shouldn’t be too big a deal..though good to know Veeam is addressing it there as well.
good day, I experienced this behaviour on Oracle LVM.
+11
+21
+3
