[ovirt-users] Re: Veeam Backup for RHV (oVirt)

2022-07-27 Thread Artur Socha
Hi, I will document the required steps to revert from Keycloak. I only need some time to test the procedure. Definitely, it is possible. Stay tuned, I will post it first here (today) Artur On Thu, Jul 28, 2022 at 8:30 AM wrote: > Ah, I see.. > Then, is there any good guide or documentation ho

[ovirt-users] Re: Veeam Backup for RHV (oVirt)

2022-07-27 Thread markeczzz
Ah, I see.. Then, is there any good guide or documentation how to revert from Keycloak to AAA? All I could find is how to move from AAA to Keycloak, but not reverse. ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ov

[ovirt-users] Re: Veeam Backup for RHV (oVirt)

2022-07-27 Thread Yury Panchenko via Users
Hello there, Thank you for the report. The problem is described there https://bugzilla.redhat.com/show_bug.cgi?id=2111207 Veeam backup for RHV isn't supporting this credentials format now > > 2022-07-27 08:08:44.176 00031 [19545] INFO | [RhevCluster_31]: Test > connection to cluster [IP: engin

[ovirt-users] Re: Veeam Backup for RHV (oVirt)

2022-07-27 Thread Nir Soffer
On Wed, Jul 27, 2022 at 2:56 PM wrote: > > Hi! > Not really sure if this is right place to ask, but.. > > I am trying to use Veeam Backup for Red Hat Virtualization on oVirt 4.5.1. > I have been using it on version 4.4.10.7 and it works ok there. > > On Veeam Release page it says that supported OS

[ovirt-users] Veeam Backup for RHV (oVirt)

2022-07-27 Thread markeczzz
Hi! Not really sure if this is right place to ask, but.. I am trying to use Veeam Backup for Red Hat Virtualization on oVirt 4.5.1. I have been using it on version 4.4.10.7 and it works ok there. On Veeam Release page it says that supported OS is RHV 4.4SP1 (oVirt 4.5). When i try to do backup,

[ovirt-users] Re: Moving raw/sparse disk from NFS to iSCSI fails on oVirt 4.5.1

2022-07-27 Thread Guillaume Pavese
Did anyone have the chance to look at this problem? It seems that it may be related to another problem we have encountered when trying to import a vm with qcow2 disks that have been sparsified first (virt-sparsify), from a kvm/libvirt provider to a iSCSI storage domain. In those case, we get an er