[ovirt-users] help, manager hard drive died (3.3.4)

[David Smith]

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 at 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 at 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 at 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 at 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 at ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users
>>>
>>>
>>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20140523/b1dadcd3/attachment-0001.html>