12:03 p.m.
--_000_D05C1D04061DE64AA1AE65E2D40211EE3A51FBD5AMXPRD0610MB378_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hello everybody,
I managed to re-install the server the oVirt engine was running on in my te=
stlab. All the cpu and storages are still there and the VMs are still runni=
ng without problems. Is there a way, I can attach the still existing nodes =
to the new oVirt engine and recover/import the VMs?
Alternatively, is there a way, I can import the VMs disks? I still know how=
the data center and clusters were set up and the specs for the VMs are als=
o documented, so I'd like to re-attach the disks, which would save me some =
time compared to the re-installs.
Kind regards
J=F6rn
--_000_D05C1D04061DE64AA1AE65E2D40211EE3A51FBD5AMXPRD0610MB378_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<html xmlns:v=3D"urn:schemas-microsoft-com:vml"
xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word"
=
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml"
xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html;
charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";
mso-fareast-language:EN-US;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"DE" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hello everybody,<o:p></o:p
</p>
<p
class=3D"MsoNormal"><o:p> </o:p</p>
<p class=3D"MsoNormal"><span
lang=3D"EN-US">I managed to re-install the ser=
ver the oVirt engine was running on in my testlab. All the cpu and storages=
are still there and the VMs are still running without problems. Is there a=
way, I can attach the still existing
nodes to the new oVirt engine and recover/import the
VMs?<o:p></o:p></span=
</p>
<p class=3D"MsoNormal"><span
lang=3D"EN-US"><o:p> </o:p></span</p>
<p class=3D"MsoNormal"><span
lang=3D"EN-US">Alternatively, is there a way, =
I can import the VMs disks? I still know how the data center and clusters w=
ere set up and the specs for the VMs are also documented, so I’d like=
to re-attach the disks, which would save
me some time compared to the re-installs.<o:p></o:p></span</p>
<p class=3D"MsoNormal"><span
lang=3D"EN-US"><o:p> </o:p></span</p>
<p class=3D"MsoNormal"><span
lang=3D"EN-US"><o:p> </o:p></span</p>
<p class=3D"MsoNormal"><span
lang=3D"EN-US">Kind regards<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span
lang=3D"EN-US">J=F6rn</span><span lang=3D"EN-U=
S"
style=3D"mso-fareast-language:DE"><o:p></o:p></span</p>
<p class=3D"MsoNormal"><span
lang=3D"EN-US"><o:p> </o:p></span</p>
</div>
</body>
</html>
--_000_D05C1D04061DE64AA1AE65E2D40211EE3A51FBD5AMXPRD0610MB378_--
12:32 p.m.
On 11/23/2012 11:03 AM, Joern Ott wrote:
Hello everybody,
I managed to re-install the server the oVirt engine was running on in my
testlab. All the cpu and storages are still there and the VMs are still
running without problems. Is there a way, I can attach the still
existing nodes to the new oVirt engine and recover/import the VMs?
Alternatively, is there a way, I can import the VMs disks? I still know
how the data center and clusters were set up and the specs for the VMs
are also documented, so I’d like to re-attach the disks, which would
save me some time compared to the re-installs.
is this an iscsi or nfs data storage domain?
3:58 p.m.
Hey Itamar,
this is an NFS storage.
KR
Jörn
-----Original Message-----
From: Itamar Heim [mailto:iheim@redhat.com]
Sent: Freitag, 23. November 2012 10:32
To: Joern Ott
Cc: users(a)ovirt.org; Ayal Baron
Subject: Re: [Users] Recovering VMs when the engine is lost
On 11/23/2012 11:03 AM, Joern Ott wrote:
> Hello everybody,
>
> I managed to re-install the server the oVirt engine was running on in
> my testlab. All the cpu and storages are still there and the VMs are
> still running without problems. Is there a way, I can attach the still
> existing nodes to the new oVirt engine and recover/import the VMs?
>
> Alternatively, is there a way, I can import the VMs disks? I still
> know how the data center and clusters were set up and the specs for
> the VMs are also documented, so I'd like to re-attach the disks, which
> would save me some time compared to the re-installs.
>
is this an iscsi or nfs data storage domain?
4:11 p.m.
On 11/23/2012 02:58 PM, Joern Ott wrote:
Hey Itamar,
this is an NFS storage.
we don't currently support importing an existing data storage domain. so
you need to create a new nfs data domain.
i suggest two 'hacky' options after that
1. less hacky - convert the current nfs data domain to an export domain,
and import the VMs from it.
2. more hacky - recreate the VMs on the new nfs data domain with exact
same details, and copy the disk over the newly created disks.
benefit of the other is you may be able to move the data, instead of
full blown copy, while in option 1 (which is much simpler/less error
prone), you need to import all vm's again.
there is current work to detect disks from a storage domain:
http://wiki.ovirt.org/wiki/Features/Domain_Scan
when it will be ready (and better when import existing storage domain
will be supported), this would be easier.
KR
Jörn
> -----Original Message-----
> From: Itamar Heim [mailto:iheim@redhat.com]
> Sent: Freitag, 23. November 2012 10:32
> To: Joern Ott
> Cc: users(a)ovirt.org; Ayal Baron
> Subject: Re: [Users] Recovering VMs when the engine is lost
>
> On 11/23/2012 11:03 AM, Joern Ott wrote:
>> Hello everybody,
>>
>> I managed to re-install the server the oVirt engine was running on in
>> my testlab. All the cpu and storages are still there and the VMs are
>> still running without problems. Is there a way, I can attach the still
>> existing nodes to the new oVirt engine and recover/import the VMs?
>>
>> Alternatively, is there a way, I can import the VMs disks? I still
>> know how the data center and clusters were set up and the specs for
>> the VMs are also documented, so I'd like to re-attach the disks, which
>> would save me some time compared to the re-installs.
>>
>
> is this an iscsi or nfs data storage domain?
>
>
5:16 p.m.
Hello Itamar,
-----Original Message-----
From: Itamar Heim [mailto:iheim@redhat.com]
Sent: Freitag, 23. November 2012 14:11
To: Joern Ott
Cc: users(a)ovirt.org; Ayal Baron
Subject: Re: [Users] Recovering VMs when the engine is lost
On 11/23/2012 02:58 PM, Joern Ott wrote:
> Hey Itamar,
>
> this is an NFS storage.
we don't currently support importing an existing data storage domain. so you
need to create a new nfs data domain.
i suggest two 'hacky' options after that 1. less hacky - convert the current nfs
data domain to an export domain, and import the VMs from it.
Is there any info on how to do this, I didn't find much info on export domains on the
wiki. The last time I tried to move thin disks with ovirt GUI from one storage to another,
they were expanded and filled up the destination. In the database, the disks were shown to
be on the destination host and were marked as "invalid", so this procedure also
has some risks.
2. more hacky - recreate the VMs on the new nfs data domain with
exact
same details, and copy the disk over the newly created disks.
benefit of the other is you may be able to move the data, instead of full
blown copy, while in option 1 (which is much simpler/less error prone), you
need to import all vm's again.
The advantage of this would be faster speed as most disks are thin provisioned disks. So I
think, I will go for this option.
there is current work to detect disks from a storage domain:
http://wiki.ovirt.org/wiki/Features/Domain_Scan
when it will be ready (and better when import existing storage domain will
be supported), this would be easier.
>
> KR
> Jörn
>
>> -----Original Message-----
>> From: Itamar Heim [mailto:iheim@redhat.com]
>> Sent: Freitag, 23. November 2012 10:32
>> To: Joern Ott
>> Cc: users(a)ovirt.org; Ayal Baron
>> Subject: Re: [Users] Recovering VMs when the engine is lost
>>
>> On 11/23/2012 11:03 AM, Joern Ott wrote:
>>> Hello everybody,
>>>
>>> I managed to re-install the server the oVirt engine was running on
>>> in my testlab. All the cpu and storages are still there and the VMs
>>> are still running without problems. Is there a way, I can attach the
>>> still existing nodes to the new oVirt engine and recover/import the
VMs?
>>>
>>> Alternatively, is there a way, I can import the VMs disks? I still
>>> know how the data center and clusters were set up and the specs for
>>> the VMs are also documented, so I'd like to re-attach the disks,
>>> which would save me some time compared to the re-installs.
>>>
>>
>> is this an iscsi or nfs data storage domain?
>>
>>
>
>
Kind regards
Jörn
5:34 p.m.
On 11/23/2012 04:16 PM, Joern Ott wrote:
Hello Itamar,
> -----Original Message-----
> From: Itamar Heim [mailto:iheim@redhat.com]
> Sent: Freitag, 23. November 2012 14:11
> To: Joern Ott
> Cc: users(a)ovirt.org; Ayal Baron
> Subject: Re: [Users] Recovering VMs when the engine is lost
>
> On 11/23/2012 02:58 PM, Joern Ott wrote:
>> Hey Itamar,
>>
>> this is an NFS storage.
>
> we don't currently support importing an existing data storage domain. so you
> need to create a new nfs data domain.
>
> i suggest two 'hacky' options after that 1. less hacky - convert the current
nfs
> data domain to an export domain, and import the VMs from it.
Is there any info on how to do this, I didn't find much info on export domains on the
wiki. The last time I tried to move thin disks with ovirt GUI from one storage to another,
they were expanded and filled up the destination. In the database, the disks were shown to
be on the destination host and were marked as "invalid", so this procedure also
has some risks.
check this one, and please wikify for others if you find it helpful:
http://comments.gmane.org/gmane.comp.emulators.ovirt.user/4428
> 2. more hacky - recreate the VMs on the new nfs data domain with exact
> same details, and copy the disk over the newly created disks.
>
> benefit of the other is you may be able to move the data, instead of full
> blown copy, while in option 1 (which is much simpler/less error prone), you
> need to import all vm's again.
The advantage of this would be faster speed as most disks are thin provisioned disks. So
I think, I will go for this option.
just to make it clear - this is risky, and you should know what you are
doing when copying/moving files over the new layout, which must be
identical to previous definitions.
>
> there is current work to detect disks from a storage domain:
> http://wiki.ovirt.org/wiki/Features/Domain_Scan
>
> when it will be ready (and better when import existing storage domain will
> be supported), this would be easier.
>
>>
>> KR
>> Jörn
>>
>>> -----Original Message-----
>>> From: Itamar Heim [mailto:iheim@redhat.com]
>>> Sent: Freitag, 23. November 2012 10:32
>>> To: Joern Ott
>>> Cc: users(a)ovirt.org; Ayal Baron
>>> Subject: Re: [Users] Recovering VMs when the engine is lost
>>>
>>> On 11/23/2012 11:03 AM, Joern Ott wrote:
>>>> Hello everybody,
>>>>
>>>> I managed to re-install the server the oVirt engine was running on
>>>> in my testlab. All the cpu and storages are still there and the VMs
>>>> are still running without problems. Is there a way, I can attach the
>>>> still existing nodes to the new oVirt engine and recover/import the
> VMs?
>>>>
>>>> Alternatively, is there a way, I can import the VMs disks? I still
>>>> know how the data center and clusters were set up and the specs for
>>>> the VMs are also documented, so I'd like to re-attach the disks,
>>>> which would save me some time compared to the re-installs.
>>>>
>>>
>>> is this an iscsi or nfs data storage domain?
>>>
>>>
>>
>>
>
>
Kind regards
Jörn
11:59 a.m.
On Fri, 23 Nov 2012 09:03:24 +0000
Joern Ott <joern.ott(a)ciao.leguide.com> wrote:
Hello everybody,
I managed to re-install the server the oVirt engine was running on in
my testlab. All the cpu and storages are still there and the VMs are
still running without problems. Is there a way, I can attach the
still existing nodes to the new oVirt engine and recover/import the
VMs?
Do you have old DB dump in /var/lib/ovirt-engine/backup? If so, maybe
restoring DB would be sufficient, won't be?
jbelka
2:38 p.m.
Hello Jiri,
as this was a testlab setup, there were no backups, but I managed to recover things
another way.
KR
Jörn
-----Original Message-----
From: Jiri Belka [mailto:jbelka@redhat.com]
Sent: Montag, 26. November 2012 10:00
To: Joern Ott
Cc: users(a)ovirt.org
Subject: Re: [Users] Recovering VMs when the engine is lost
On Fri, 23 Nov 2012 09:03:24 +0000
Joern Ott <joern.ott(a)ciao.leguide.com> wrote:
> Hello everybody,
>
> I managed to re-install the server the oVirt engine was running on in
> my testlab. All the cpu and storages are still there and the VMs are
> still running without problems. Is there a way, I can attach the still
> existing nodes to the new oVirt engine and recover/import the VMs?
Do you have old DB dump in /var/lib/ovirt-engine/backup? If so, maybe
restoring DB would be sufficient, won't be?
jbelka
4191
days inactive
4196
days old
7 comments
3 participants
participants (3)
-
Itamar Heim -
Jiri Belka -
Joern Ott