On 10-03-14 10:46, Itamar Heim wrote:
On 03/10/2014 12:30 AM, Boudewijn Ector wrote:
How should I go on recovering those VMs?
change the domain into an export domain, attach it, and import the VMs from it (currently, you can only import an export domain) i think this thread has the relevant info: https://www.mail-archive.com/users@ovirt.org/msg04257.html
Okay thank you very much for pointing that out. I now realise the difference between the regular and export shares.
I just changed the metadata file (at /raid/ovirt-old/data/1979444d-b79a-494c-8c1a-bcc132e31a04/dom_md0) from:
[root@leiden dom_md]# cat metadata.backup CLASS=Data DESCRIPTION=leiden-data IOOPTIMEOUTSEC=10 LEASERETRIES=3 LEASETIMESEC=60 LOCKPOLICY= LOCKRENEWALINTERVALSEC=5 MASTER_VERSION=613 POOL_DESCRIPTION=Default POOL_DOMAINS=dafe25c2-1ce7-4979-9d8d-a35688da207a:Active,1979444d-b79a-494c-8c1a-bcc132e31a04:Active,d2676b04-e2ff-420f-8f29-36dafc2df47b:Active
POOL_SPM_ID=1 POOL_SPM_LVER=0 POOL_UUID=5849b030-626e-47cb-ad90-3ce782d831b3 REMOTE_PATH=192.168.1.44:/raid/ovirt/data ROLE=Master SDUUID=1979444d-b79a-494c-8c1a-bcc132e31a04 TYPE=NFS VERSION=3 _SHA_CKSUM=cab6c41e19812714ba79c48fc98b7037032725e4
into:
CLASS=Backup DESCRIPTION=export-storage IOOPTIMEOUTSEC=10 LEASERETRIES=3 LEASETIMESEC=60 LOCKPOLICY= LOCKRENEWALINTERVALSEC=5 MASTER_VERSION=613 POOL_DESCRIPTION=Default POOL_DOMAINS= POOL_SPM_ID=1 POOL_SPM_LVER=0 POOL_UUID= REMOTE_PATH=nfsserver:/raid/ovirt-old/data ROLE=Regular SDUUID=1979444d-b79a-494c-8c1a-bcc132e31a04 TYPE=NFS VERSION=3
(there's another storage doman which has to be converted too but that's not that relevant imo).
Now I log in onto the webinterface, select storage domain -> import domain :
Domain function set to export/NFS export path: 192.168.1.44:/raid/ovirt-old/data/
(192.168.1.44 is the server's IP)
Now this error pops up:
Error while executing action: Cannot add Storage. Storage format V3 is not supported on the selected host version.
I just had a look for this one and found this bug (in which you replied... such a small world :) ) : https://bugzilla.redhat.com/show_bug.cgi?id=1059604 But there's no obvious solution over there.
the bug is about a host with a cluster not associated with a DC. is your cluster associated with a DC?
Yes it is, so my buglink isn't that relevant after all. Thanks :). Despite of that, my setup still isn't running and I haven't got a clue on how to get it to work again. Cheers, Boudewijn