2:39 p.m.
Hi users,
I'm using oVirt 3.4 on rhel 6.5 and it's working perfectly, but when i'm
setting up another Hypervisor and ovirt-engine I accidentally attach my
working storage "Data(Master)" to my 2nd one, and my problem is i'm unable
to re-attach it to my first one, is it possible to re-attach it without
loosing my vm guest disk images? And when I accidentally attach it to my
2nd one, It prompt me that "This operation might be unrecoverable and
distructive" is there a change that my 25 vm guest disk images will be
erased? God Bless.
TIA
Sandvik
6:06 p.m.
On 12/01/2015 02:39 PM, Sandvik Agustin wrote:
Hi users,
I'm using oVirt 3.4 on rhel 6.5 and it's working perfectly, but when i'm
setting up another Hypervisor and ovirt-engine I accidentally attach my
working storage "Data(Master)" to my 2nd one, and my problem is i'm unable
to re-attach it to my first one, is it possible to re-attach it without
loosing my vm guest disk images? And when I accidentally attach it to my
2nd one, It prompt me that "This operation might be unrecoverable and
distructive" is there a change that my 25 vm guest disk images will be
erased? God Bless.
Hi Sandvik,
I'm guessing this was iSCSI storage based on the error message.
If so, unfortunately the LVM metadata for the original storage domain will
have been overwritten due to attaching the domain to the second setup, so
it can't simply be re-attached to the first.
However, the images are probably still (mostly?) intact as long as the
storage has been relatively untouched. If you feel it's worthwhile and are
comfortable getting your hands a little dirty you may be able to recover
some of the images by finding them on the LUN.
To do this, I'd check your hypervisors' /etc/lvm/archive directories and
look for an lvm metadata backup as in [1],[2]. You want to look for a VG
with the UUID of your old master storage domain. The LV names within would
correspond to your old VM disk image UUIDs. If you find this (via the
backup, `pvck`, or even by scouring the first MB or so of the LUN), you
might be able to recover it via some hints in [1] or [2] (of course
maintenance/detach the domain from the second hypervisor first). You can
then copy the data onto a new storage domain.
Hope that helps,
Greg
[1]
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/...
[2]
http://serverfault.com/questions/223361/how-to-recover-logical-volume-del...
TIA
Sandvik
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
1:57 a.m.
Hi,
This is what inside my /etc/lvm/archive/
"ls /etc/lvm/archive/
39757758-c149-41da-8479-74b4d21635a0_00000-1936952678.vg
4a0a7b1a-a98c-4bc4-86eb-b215cfa8da24_00000-147069828.vg
4a0a7b1a-a98c-4bc4-86eb-b215cfa8da24_00001-849682777.vg
4a0a7b1a-a98c-4bc4-86eb-b215cfa8da24_00002-1626145851.vg
4c0c34ec-d44b-4f3e-8e10-76b82b5fa118_00000-1451865950.vg
4c0c34ec-d44b-4f3e-8e10-76b82b5fa118_00001-587463327.vg
4c0c34ec-d44b-4f3e-8e10-76b82b5fa118_00002-321869468.vg
4c0c34ec-d44b-4f3e-8e10-76b82b5fa118_00003-117963502.vg
aa2ae33a-47ad-43a2-a623-cbea4770cbd0_00000-1774160120.vg
aa2ae33a-47ad-43a2-a623-cbea4770cbd0_00001-937915900.vg
afb04ab7-ecc5-4079-9700-43b6d01c8a5b_00000-1996551186.vg
afb04ab7-ecc5-4079-9700-43b6d01c8a5b_00001-5564790.vg
afb04ab7-ecc5-4079-9700-43b6d01c8a5b_00002-617819029.vg
cce50b8e-a566-4ba9-a2b9-a978e44f3684_00000-1336023522.vg
cce50b8e-a566-4ba9-a2b9-a978e44f3684_00001-210534184.vg
cce50b8e-a566-4ba9-a2b9-a978e44f3684_00002-159368298.vg
HostVG_00000-1625691793.vg"
And this is what inside my /etc/lvm/backup/
"ls /etc/lvm/backup/
39757758-c149-41da-8479-74b4d21635a0 afb04ab7-ecc5-4079-9700-43b6d01c8a5b
4a0a7b1a-a98c-4bc4-86eb-b215cfa8da24 cce50b8e-a566-4ba9-a2b9-a978e44f3684
4c0c34ec-d44b-4f3e-8e10-76b82b5fa118 HostVG
aa2ae33a-47ad-43a2-a623-cbea4770cbd0"
How do I find my UUID of old master storage domain?
Thanks,
Sandvik
2:55 p.m.
On 12/14/2015 01:57 AM, Sandvik Agustin wrote:
Hi,
This is what inside my /etc/lvm/archive/
"ls /etc/lvm/archive/
39757758-c149-41da-8479-74b4d21635a0_00000-1936952678.vg
<http://39757758-c149-41da-8479-74b4d21635a0_00000-1936952678.vg>
4a0a7b1a-a98c-4bc4-86eb-b215cfa8da24_00000-147069828.vg
<http://4a0a7b1a-a98c-4bc4-86eb-b215cfa8da24_00000-147069828.vg>
4a0a7b1a-a98c-4bc4-86eb-b215cfa8da24_00001-849682777.vg
<http://4a0a7b1a-a98c-4bc4-86eb-b215cfa8da24_00001-849682777.vg>
4a0a7b1a-a98c-4bc4-86eb-b215cfa8da24_00002-1626145851.vg
<http://4a0a7b1a-a98c-4bc4-86eb-b215cfa8da24_00002-1626145851.vg>
4c0c34ec-d44b-4f3e-8e10-76b82b5fa118_00000-1451865950.vg
<http://4c0c34ec-d44b-4f3e-8e10-76b82b5fa118_00000-1451865950.vg>
4c0c34ec-d44b-4f3e-8e10-76b82b5fa118_00001-587463327.vg
<http://4c0c34ec-d44b-4f3e-8e10-76b82b5fa118_00001-587463327.vg>
4c0c34ec-d44b-4f3e-8e10-76b82b5fa118_00002-321869468.vg
<http://4c0c34ec-d44b-4f3e-8e10-76b82b5fa118_00002-321869468.vg>
4c0c34ec-d44b-4f3e-8e10-76b82b5fa118_00003-117963502.vg
<http://4c0c34ec-d44b-4f3e-8e10-76b82b5fa118_00003-117963502.vg>
aa2ae33a-47ad-43a2-a623-cbea4770cbd0_00000-1774160120.vg
<http://aa2ae33a-47ad-43a2-a623-cbea4770cbd0_00000-1774160120.vg>
aa2ae33a-47ad-43a2-a623-cbea4770cbd0_00001-937915900.vg
<http://aa2ae33a-47ad-43a2-a623-cbea4770cbd0_00001-937915900.vg>
afb04ab7-ecc5-4079-9700-43b6d01c8a5b_00000-1996551186.vg
<http://afb04ab7-ecc5-4079-9700-43b6d01c8a5b_00000-1996551186.vg>
afb04ab7-ecc5-4079-9700-43b6d01c8a5b_00001-5564790.vg
<http://afb04ab7-ecc5-4079-9700-43b6d01c8a5b_00001-5564790.vg>
afb04ab7-ecc5-4079-9700-43b6d01c8a5b_00002-617819029.vg
<http://afb04ab7-ecc5-4079-9700-43b6d01c8a5b_00002-617819029.vg>
cce50b8e-a566-4ba9-a2b9-a978e44f3684_00000-1336023522.vg
<http://cce50b8e-a566-4ba9-a2b9-a978e44f3684_00000-1336023522.vg>
cce50b8e-a566-4ba9-a2b9-a978e44f3684_00001-210534184.vg
<http://cce50b8e-a566-4ba9-a2b9-a978e44f3684_00001-210534184.vg>
cce50b8e-a566-4ba9-a2b9-a978e44f3684_00002-159368298.vg
<http://cce50b8e-a566-4ba9-a2b9-a978e44f3684_00002-159368298.vg>
HostVG_00000-1625691793.vg"
And this is what inside my /etc/lvm/backup/
"ls /etc/lvm/backup/
39757758-c149-41da-8479-74b4d21635a0 afb04ab7-ecc5-4079-9700-43b6d01c8a5b
4a0a7b1a-a98c-4bc4-86eb-b215cfa8da24 cce50b8e-a566-4ba9-a2b9-a978e44f3684
4c0c34ec-d44b-4f3e-8e10-76b82b5fa118 HostVG
aa2ae33a-47ad-43a2-a623-cbea4770cbd0"
How do I find my UUID of old master storage domain?
Thanks,
Sandvik
Hi Sandvik,
Executing the following (all one line) on your engine machine will list
the domain ids, names, and timestamp when that domain was master:
psql <dbname> -U <username> -c 'select id, storage_name,
last_time_used_as_master from storage_domain_static'
(where of course <dbname> and <username> are the properties you set up
during your initial engine installation.)
Greg
3299
days inactive
3313
days old
3 comments
2 participants
participants (2)
-
Greg Padgett -
Sandvik Agustin