
So the ovirt manager hard disk died, 3.3.4 version, i can't get it to spin up to get any data off. I have an old copy of the manager database which was living on the manager machine. What is the best procedure for restoring my ovirt setup? I've not been able to import the data store, only export and iso in the past. Thanks in advance, David

I meant ovirt-engine (i was calling it the manager) also i'll need to reinstall version 3.3.4, whats the best path for that w/restore? On Thu, May 22, 2014 at 11:58 AM, David Smith <dsmith@mypchelp.com> wrote:
So the ovirt manager hard disk died, 3.3.4 version, i can't get it to spin up to get any data off. I have an old copy of the manager database which was living on the manager machine.
What is the best procedure for restoring my ovirt setup? I've not been able to import the data store, only export and iso in the past.
Thanks in advance, David

This is a multi-part message in MIME format. --------------010507050806090802010600 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 05/22/2014 03:08 PM, David Smith wrote:
I meant ovirt-engine (i was calling it the manager) also i'll need to reinstall version 3.3.4, whats the best path for that w/restore?
One thing, if all else fails, is to convert your Export Domain to a Data Domain with a few edits to the metadata. Then install a fresh engine and import your old VMs. Personally, I'd install the same version as you had previously, then make sure you can attach your new Export domain (old Data domain), then upgrade. Some guides for conversion are in this thread: http://lists.ovirt.org/pipermail/users/2012-October/010258.html http://lists.ovirt.org/pipermail/users/2012-November/010273.html Note that's from a while ago. I am not sure it still works exactly the same. Make sure to backup your metadata file first. I did something a bit similar earlier today, by editing the metadata on an Export domain to remove information about the previously-attached Data Center. -Bob
On Thu, May 22, 2014 at 11:58 AM, David Smith <dsmith@mypchelp.com <mailto:dsmith@mypchelp.com>> wrote:
So the ovirt manager hard disk died, 3.3.4 version, i can't get it to spin up to get any data off. I have an old copy of the manager database which was living on the manager machine.
What is the best procedure for restoring my ovirt setup? I've not been able to import the data store, only export and iso in the past.
Thanks in advance, David
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
--------------010507050806090802010600 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit <html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> On 05/22/2014 03:08 PM, David Smith wrote:<br> <blockquote cite="mid:CAMKtzE_NBKDVkTZwsRsFdqFtgmgSocJBWTBeCy40S7sMtKhGzg@mail.gmail.com" type="cite"> <div dir="ltr"> <div>I meant ovirt-engine (i was calling it the manager)</div> also i'll need to reinstall version 3.3.4, whats the best path for that w/restore?</div> </blockquote> <br> One thing, if all else fails, is to convert your Export Domain to a Data Domain with a few edits to the metadata.<br> Then install a fresh engine and import your old VMs.<br> <br> Personally, I'd install the same version as you had previously, then make sure you can attach your new Export domain (old Data domain), then upgrade.<br> <br> Some guides for conversion are in this thread:<br> <a class="moz-txt-link-freetext" href="http://lists.ovirt.org/pipermail/users/2012-October/010258.html">http://lists.ovirt.org/pipermail/users/2012-October/010258.html</a><br> <a class="moz-txt-link-freetext" href="http://lists.ovirt.org/pipermail/users/2012-November/010273.html">http://lists.ovirt.org/pipermail/users/2012-November/010273.html</a><br> <br> Note that's from a while ago. I am not sure it still works exactly the same. Make sure to backup your metadata file first.<br> <br> I did something a bit similar earlier today, by editing the metadata on an Export domain to remove information about the previously-attached Data Center.<br> <br> -Bob<br> <br> <blockquote cite="mid:CAMKtzE_NBKDVkTZwsRsFdqFtgmgSocJBWTBeCy40S7sMtKhGzg@mail.gmail.com" type="cite"> <div class="gmail_extra"><br> <br> <div class="gmail_quote"> On Thu, May 22, 2014 at 11:58 AM, David Smith <span dir="ltr"><<a moz-do-not-send="true" href="mailto:dsmith@mypchelp.com" target="_blank">dsmith@mypchelp.com</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div dir="ltr">So the ovirt manager hard disk died, 3.3.4 version, i can't get it to spin up to get any data off. <div>I have an old copy of the manager database which was living on the manager machine.</div> <div><br> </div> <div>What is the best procedure for restoring my ovirt setup? I've not been able to import the data store, only export and iso in the past.</div> <div><br> </div> <div>Thanks in advance,</div> <div>David</div> </div> </blockquote> </div> <br> </div> <br> <fieldset class="mimeAttachmentHeader"></fieldset> <br> <pre wrap="">_______________________________________________ Users mailing list <a class="moz-txt-link-abbreviated" href="mailto:Users@ovirt.org">Users@ovirt.org</a> <a class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/users">http://lists.ovirt.org/mailman/listinfo/users</a> </pre> </blockquote> <br> </body> </html> --------------010507050806090802010600--

This is a multi-part message in MIME format. --------------040808000900040307040104 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 05/22/2014 03:17 PM, Bob Doolittle wrote:
On 05/22/2014 03:08 PM, David Smith wrote:
I meant ovirt-engine (i was calling it the manager) also i'll need to reinstall version 3.3.4, whats the best path for that w/restore?
One thing, if all else fails, is to convert your Export Domain to a Data Domain with a few edits to the metadata.
Grrr. Visa-versa. Convert to an Export Domain from your old Data Domain.
Then install a fresh engine and import your old VMs.
Personally, I'd install the same version as you had previously, then make sure you can attach your new Export domain (old Data domain), then upgrade.
Some guides for conversion are in this thread: http://lists.ovirt.org/pipermail/users/2012-October/010258.html http://lists.ovirt.org/pipermail/users/2012-November/010273.html
Note that's from a while ago. I am not sure it still works exactly the same. Make sure to backup your metadata file first.
I did something a bit similar earlier today, by editing the metadata on an Export domain to remove information about the previously-attached Data Center.
-Bob
On Thu, May 22, 2014 at 11:58 AM, David Smith <dsmith@mypchelp.com <mailto:dsmith@mypchelp.com>> wrote:
So the ovirt manager hard disk died, 3.3.4 version, i can't get it to spin up to get any data off. I have an old copy of the manager database which was living on the manager machine.
What is the best procedure for restoring my ovirt setup? I've not been able to import the data store, only export and iso in the past.
Thanks in advance, David
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
--------------040808000900040307040104 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit <html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> <br> <div class="moz-cite-prefix">On 05/22/2014 03:17 PM, Bob Doolittle wrote:<br> </div> <blockquote cite="mid:537E4D4C.5080404@doolittle.us.com" type="cite"> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> On 05/22/2014 03:08 PM, David Smith wrote:<br> <blockquote cite="mid:CAMKtzE_NBKDVkTZwsRsFdqFtgmgSocJBWTBeCy40S7sMtKhGzg@mail.gmail.com" type="cite"> <div dir="ltr"> <div>I meant ovirt-engine (i was calling it the manager)</div> also i'll need to reinstall version 3.3.4, whats the best path for that w/restore?</div> </blockquote> <br> One thing, if all else fails, is to convert your Export Domain to a Data Domain with a few edits to the metadata.<br> </blockquote> <br> Grrr. Visa-versa. Convert to an Export Domain from your old Data Domain.<br> <br> <blockquote cite="mid:537E4D4C.5080404@doolittle.us.com" type="cite"> Then install a fresh engine and import your old VMs.<br> <br> Personally, I'd install the same version as you had previously, then make sure you can attach your new Export domain (old Data domain), then upgrade.<br> <br> Some guides for conversion are in this thread:<br> <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.ovirt.org/pipermail/users/2012-October/010258.html">http://lists.ovirt.org/pipermail/users/2012-October/010258.html</a><br> <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.ovirt.org/pipermail/users/2012-November/010273.html">http://lists.ovirt.org/pipermail/users/2012-November/010273.html</a><br> <br> Note that's from a while ago. I am not sure it still works exactly the same. Make sure to backup your metadata file first.<br> <br> I did something a bit similar earlier today, by editing the metadata on an Export domain to remove information about the previously-attached Data Center.<br> <br> -Bob<br> <br> <blockquote cite="mid:CAMKtzE_NBKDVkTZwsRsFdqFtgmgSocJBWTBeCy40S7sMtKhGzg@mail.gmail.com" type="cite"> <div class="gmail_extra"><br> <br> <div class="gmail_quote"> On Thu, May 22, 2014 at 11:58 AM, David Smith <span dir="ltr"><<a moz-do-not-send="true" href="mailto:dsmith@mypchelp.com" target="_blank">dsmith@mypchelp.com</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div dir="ltr">So the ovirt manager hard disk died, 3.3.4 version, i can't get it to spin up to get any data off. <div>I have an old copy of the manager database which was living on the manager machine.</div> <div><br> </div> <div>What is the best procedure for restoring my ovirt setup? I've not been able to import the data store, only export and iso in the past.</div> <div><br> </div> <div>Thanks in advance,</div> <div>David</div> </div> </blockquote> </div> <br> </div> <br> <fieldset class="mimeAttachmentHeader"></fieldset> <br> <pre wrap="">_______________________________________________ Users mailing list <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Users@ovirt.org">Users@ovirt.org</a> <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/users">http://lists.ovirt.org/mailman/listinfo/users</a> </pre> </blockquote> <br> </blockquote> <br> </body> </html> --------------040808000900040307040104--

Thanks Bob, I had already gone through this path once early in my ovirt lifetime and didn't get it working, I was able to make it happen this time. Thanks. I was hoping for some other method, but this will work, it's going to be slow-going to get everything online this way since we have to re-import everything which essentially copies it all. And with only 1 export domain allowed at a time, and 3 nfs machines, i'm going to have to do them in sequence.. urgghhh On Thu, May 22, 2014 at 12:17 PM, Bob Doolittle <bob@doolittle.us.com>wrote:
On 05/22/2014 03:08 PM, David Smith wrote:
I meant ovirt-engine (i was calling it the manager) also i'll need to reinstall version 3.3.4, whats the best path for that w/restore?
One thing, if all else fails, is to convert your Export Domain to a Data Domain with a few edits to the metadata. Then install a fresh engine and import your old VMs.
Personally, I'd install the same version as you had previously, then make sure you can attach your new Export domain (old Data domain), then upgrade.
Some guides for conversion are in this thread: http://lists.ovirt.org/pipermail/users/2012-October/010258.html http://lists.ovirt.org/pipermail/users/2012-November/010273.html
Note that's from a while ago. I am not sure it still works exactly the same. Make sure to backup your metadata file first.
I did something a bit similar earlier today, by editing the metadata on an Export domain to remove information about the previously-attached Data Center.
-Bob
On Thu, May 22, 2014 at 11:58 AM, David Smith <dsmith@mypchelp.com>wrote:
So the ovirt manager hard disk died, 3.3.4 version, i can't get it to spin up to get any data off. I have an old copy of the manager database which was living on the manager machine.
What is the best procedure for restoring my ovirt setup? I've not been able to import the data store, only export and iso in the past.
Thanks in advance, David
_______________________________________________ Users mailing listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users

Hey Bob, Get this.. So this process worked great for one of the nfs servers, however, we had two nfs servers. One was a primary data center (master) and the other non-master. When I try to import the non-master data directory with the metadata file edit method, it imports but then shows no VMs/templates/etc available for import. On the other hand, when i activate the master data center nfs filesystem, i can see VMs that were stored on the non-master NFS, if I try to import them, it blows an error, the files aren't there, and I look at the log on the hv manager and I see the folder that it's looking for which is on the non-master NFS. Right now I'm trying to copy the folders over from the non-master nfs to the imported master data (now export domain) to see if I can import those VMs. I wonder if there's a better way to import VMs from a non-master domain. On Thu, May 22, 2014 at 12:17 PM, Bob Doolittle <bob@doolittle.us.com>wrote:
On 05/22/2014 03:08 PM, David Smith wrote:
I meant ovirt-engine (i was calling it the manager) also i'll need to reinstall version 3.3.4, whats the best path for that w/restore?
One thing, if all else fails, is to convert your Export Domain to a Data Domain with a few edits to the metadata. Then install a fresh engine and import your old VMs.
Personally, I'd install the same version as you had previously, then make sure you can attach your new Export domain (old Data domain), then upgrade.
Some guides for conversion are in this thread: http://lists.ovirt.org/pipermail/users/2012-October/010258.html http://lists.ovirt.org/pipermail/users/2012-November/010273.html
Note that's from a while ago. I am not sure it still works exactly the same. Make sure to backup your metadata file first.
I did something a bit similar earlier today, by editing the metadata on an Export domain to remove information about the previously-attached Data Center.
-Bob
On Thu, May 22, 2014 at 11:58 AM, David Smith <dsmith@mypchelp.com>wrote:
So the ovirt manager hard disk died, 3.3.4 version, i can't get it to spin up to get any data off. I have an old copy of the manager database which was living on the manager machine.
What is the best procedure for restoring my ovirt setup? I've not been able to import the data store, only export and iso in the past.
Thanks in advance, David
_______________________________________________ Users mailing listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users

If you read the whole thread I referenced it says the conversion only works for Master. It does not say how to handle non-Master. Good luck. -Bob On May 23, 2014 2:48 AM, "David Smith" <dsmith@mypchelp.com> wrote:
Hey Bob,
Get this.. So this process worked great for one of the nfs servers, however, we had two nfs servers. One was a primary data center (master) and the other non-master. When I try to import the non-master data directory with the metadata file edit method, it imports but then shows no VMs/templates/etc available for import. On the other hand, when i activate the master data center nfs filesystem, i can see VMs that were stored on the non-master NFS, if I try to import them, it blows an error, the files aren't there, and I look at the log on the hv manager and I see the folder that it's looking for which is on the non-master NFS.
Right now I'm trying to copy the folders over from the non-master nfs to the imported master data (now export domain) to see if I can import those VMs. I wonder if there's a better way to import VMs from a non-master domain.
On Thu, May 22, 2014 at 12:17 PM, Bob Doolittle <bob@doolittle.us.com>wrote:
On 05/22/2014 03:08 PM, David Smith wrote:
I meant ovirt-engine (i was calling it the manager) also i'll need to reinstall version 3.3.4, whats the best path for that w/restore?
One thing, if all else fails, is to convert your Export Domain to a Data Domain with a few edits to the metadata. Then install a fresh engine and import your old VMs.
Personally, I'd install the same version as you had previously, then make sure you can attach your new Export domain (old Data domain), then upgrade.
Some guides for conversion are in this thread: http://lists.ovirt.org/pipermail/users/2012-October/010258.html http://lists.ovirt.org/pipermail/users/2012-November/010273.html
Note that's from a while ago. I am not sure it still works exactly the same. Make sure to backup your metadata file first.
I did something a bit similar earlier today, by editing the metadata on an Export domain to remove information about the previously-attached Data Center.
-Bob
On Thu, May 22, 2014 at 11:58 AM, David Smith <dsmith@mypchelp.com>wrote:
So the ovirt manager hard disk died, 3.3.4 version, i can't get it to spin up to get any data off. I have an old copy of the manager database which was living on the manager machine.
What is the best procedure for restoring my ovirt setup? I've not been able to import the data store, only export and iso in the past.
Thanks in advance, David
_______________________________________________ Users mailing listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users

Hey Bob, Yea my method worked. I was able to copy the non-master data center VM data into the images folder on the master data center (now "export" domain) and import everything. This would have been tragic if there wasn't the hard disk space, would have required lots of big data shuffling. I've split the data center model so now we have two clusters with two masters, and will avoid using a non-master data center entirely due to this issue. The good news is it looks like we didn't lose any data. On Fri, May 23, 2014 at 3:56 AM, Bob Doolittle <bob@doolittle.us.com> wrote:
If you read the whole thread I referenced it says the conversion only works for Master. It does not say how to handle non-Master. Good luck.
-Bob On May 23, 2014 2:48 AM, "David Smith" <dsmith@mypchelp.com> wrote:
Hey Bob,
Get this.. So this process worked great for one of the nfs servers, however, we had two nfs servers. One was a primary data center (master) and the other non-master. When I try to import the non-master data directory with the metadata file edit method, it imports but then shows no VMs/templates/etc available for import. On the other hand, when i activate the master data center nfs filesystem, i can see VMs that were stored on the non-master NFS, if I try to import them, it blows an error, the files aren't there, and I look at the log on the hv manager and I see the folder that it's looking for which is on the non-master NFS.
Right now I'm trying to copy the folders over from the non-master nfs to the imported master data (now export domain) to see if I can import those VMs. I wonder if there's a better way to import VMs from a non-master domain.
On Thu, May 22, 2014 at 12:17 PM, Bob Doolittle <bob@doolittle.us.com>wrote:
On 05/22/2014 03:08 PM, David Smith wrote:
I meant ovirt-engine (i was calling it the manager) also i'll need to reinstall version 3.3.4, whats the best path for that w/restore?
One thing, if all else fails, is to convert your Export Domain to a Data Domain with a few edits to the metadata. Then install a fresh engine and import your old VMs.
Personally, I'd install the same version as you had previously, then make sure you can attach your new Export domain (old Data domain), then upgrade.
Some guides for conversion are in this thread: http://lists.ovirt.org/pipermail/users/2012-October/010258.html http://lists.ovirt.org/pipermail/users/2012-November/010273.html
Note that's from a while ago. I am not sure it still works exactly the same. Make sure to backup your metadata file first.
I did something a bit similar earlier today, by editing the metadata on an Export domain to remove information about the previously-attached Data Center.
-Bob
On Thu, May 22, 2014 at 11:58 AM, David Smith <dsmith@mypchelp.com>wrote:
So the ovirt manager hard disk died, 3.3.4 version, i can't get it to spin up to get any data off. I have an old copy of the manager database which was living on the manager machine.
What is the best procedure for restoring my ovirt setup? I've not been able to import the data store, only export and iso in the past.
Thanks in advance, David
_______________________________________________ Users mailing listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users

On 05/23/2014 01:28 PM, David Smith wrote:
Hey Bob,
Yea my method worked. I was able to copy the non-master data center VM data into the images folder on the master data center (now "export" domain) and import everything.
This would have been tragic if there wasn't the hard disk space, would have required lots of big data shuffling. I've split the data center model so now we have two clusters with two masters, and will avoid using a non-master data center entirely due to this issue.
The good news is it looks like we didn't lose any data.
also worth mentioning the upcoming 3.5 feature which will allow you to import a data domain (master or not) to the engine, which is most useful for this case, and reduces the need for the 'convert to export, then import' games.
participants (3)
-
Bob Doolittle
-
David Smith
-
Itamar Heim