12:45 a.m.
Hi Nir and Strahil.
On 6 Mar 2022, at 19:09, Nir Soffer
<nsoffer@redhat.com<mailto:nsoffer@redhat.com>> wrote:
On Fri, Mar 4, 2022 at 8:28 AM Vinícius Ferrão via Users
<users@ovirt.org<mailto:users@ovirt.org>> wrote:
Hi again, I don’t know if it will be possible to import the storage domain due to
conflicts with the UUID of the LVM devices. I’ve tried to issue a vgimportclone to chance
the UUIDs and import the volume but it still does not shows up on oVirt.
LVM can change VG/PV UUIDs and names, but storage domain metadata kept in the
VG tags and volume metadata area contain the old VG and PV names and UUIDs,
so it is unlikely to work.
The system is designed so if the original PVs are bad, you can
disconnect them and
connect a backup of the PVs, and import the storage domain again to the system.
Can you explain in more details what you are trying to do?
Nir
What I was trying to accomplish is get some VM snapshots from days ago.
On my storage system it generates a snapshot of the entire disk pool in a daly basis. So
it was natural, at least for me, to mount a snapshot at a given time to export some VMs
from those snapshots. The environment had an attack and needed to be recovered from it,
and rolling back was the approach.
But that what the issue happened, when trying to import the snapshot from the iSCSI share
it conflicted with the running iSCSI share, since it’s a storage snapshot, it have the
exactly same metadata.
I think the issue here is a missing feature on oVirt to remap the metadata and permit the
mount in this situation, right?
What I ended up doing:
* Removed one of the servers from oVirt Cluster / Datacenter
* Reinstalled from the ground
* Fired up a new hosted engine on a new iSCSI HE dedicated share
* Reconfigured everything: network, VLAN, iSCSI, etc.
* == IMPORTED the snapshot on this new engine
* Created an export domain on another NFS share
* Exported the 6 VM’s that I need to export from the storage-level snapshot to the export
domain
* Detached the export domain from the temporary engine
* Added the export domain on the production engine
* Deleted the compromised VMs
* Imported the “snapshoted" VM’s from the export domain
* == INFRA is back
* Destroyed the new engine, the snapshot iSCSI share and the export domain
* Reinstalled the host
* Added back to the original Datacenter / Cluster.
As you can see was a tiresome work just to get the VM’s back from an storage level
snapshot of the iSCSI share, but is what I’ve ended up doing.
Lesson learned: it’s too difficult to recover storage-level snapshots, it’s hard on NFS
and on iSCSI is extremely worse since you can’t mount iSCSI whatever you want to.
My opinion: Should be a feature on oVirt to at least allow to mount this kind of
conflicting volume as readonly for recovery reasons only.
Thanks.
I don’t know how to mount the iSCSI volume to recover the data. The data is there but it’s
extremely difficult to get it.
Any ideias?
Thanks.
On 3 Mar 2022, at 20:56, Vinícius Ferrão
<ferrao@versatushpc.com.br<mailto:ferrao@versatushpc.com.br>> wrote:
I think I’ve found the root cause, and it’s the LVM inside the iSCSI volume:
[root@rhvh5 ~]# pvscan
WARNING: Not using device /dev/mapper/36589cfc000000db9cf56949c63d338ef for PV
fTIrnd-gnz2-dI8i-DesK-vIqs-E1BK-mvxtha.
WARNING: PV fTIrnd-gnz2-dI8i-DesK-vIqs-E1BK-mvxtha prefers device
/dev/mapper/36589cfc0000006f6c96763988802912b because device is used by LV.
PV /dev/mapper/36589cfc0000006f6c96763988802912b VG
9377d243-2c18-4620-995f-5fc680e7b4f3 lvm2 [<10.00 TiB / 7.83 TiB free]
PV /dev/mapper/36589cfc000000a1b985d3908c07e41ad VG
650b0003-7eec-4fa5-85ea-c019f6408248 lvm2 [199.62 GiB / <123.88 GiB free]
PV /dev/mapper/3600605b00805d8a01c2180fd0d8d8dad3 VG rhvh_rhvh5
lvm2 [<277.27 GiB / 54.55 GiB free]
Total: 3 [<10.47 TiB] / in use: 3 [<10.47 TiB] / in no VG: 0 [0 ]
The device that’s not being using is the snapshot. There’s a way to change the ID of the
device so I can import the data domain?
Thanks.
On 3 Mar 2022, at 20:21, Vinícius Ferrão via Users
<users@ovirt.org<mailto:users@ovirt.org>> wrote:
Hello,
I need to import an old snapshot of my Data domain but oVirt does not find the snapshot
version when importing on the web interface.
To be clear, I’ve mounted a snapshot on my storage, and exported it on iSCSI. I was
expecting that I could be able to import it on the engine.
On the web interface this Import Pre-Configured Domain finds the relative IQN but it does
not show up as a target.
Any ideas?
_______________________________________________
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/3WEQQHZ46DK...
_______________________________________________
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/3XDKQK32V6E...