[ovirt-users] Re: Is there a way to access VM data that is stored using iscsi block storage outside of the ovirt platform ?

Many thanks for your reply. It is giving me options. Kevin From: Alan G <alan+ovirt(a)griff.me.uk&gt; Date: Friday, 10 July 2020 at 15:35 To: Kevin Doyle <kevin.doyle(a)manchester.ac.uk&gt; Cc: users <users(a)ovirt.org&gt; Subject: Re: [ovirt-users] Is there a way to access VM data that is stored using iscsi block storage outside of the ovirt platform ? You can definitely build a bare metal Engine and do a DB restore onto it. I've done this before when I had problems. Obviously you will need a sane backup from your hosted engine. I'm surprised the NFS build didn't work though. You probably need to remove the stale iSCSI hosted_storage domain and then I think it will automagically discover the new NFS one and then everything should start working. ---- On Fri, 10 Jul 2020 14:14:04 +0100 Kevin Doyle <kevin.doyle(a)manchester.ac.uk&gt; wrote ---- We have had problems trying to get our broken hosted engine to work. The datastore for all the VM's was stored in an iscsi storage that was deactivated before the platform went down, I am now looking for a way to access this data and start the VM's outside of a running hosted-engine Can I build an new ovirt standalone engine on a new bare metal remote server and connect to the hosts and start up the domain ? I would be interested in your thoughts. The problem with rebuilding the hosted-engine is that it cannot reuse the lun dedicated for the hosted-engine. I have tried to rebuild using NFS but it complains about not seeing the master domain thanks Kevin _______________________________________________ Users mailing list -- users@ovirt.org<mailto:users@ovirt.org> To unsubscribe send an email to users-leave@ovirt.org<mailto:users-leave@ovirt.org> Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/KLWD7MUYZ4C...