Hi,

 

Thank you for the reply. I am building another environment today, so I will run through the backup and restore again. I do recall one issue I had with the restore was that it gave an error that one of the storage domains were already in use. This was a new storage domain I added, with no VMs on.

 

I just want to make sure, I probably cannot deploy the HE on a storage domain that is in maintenance, correct? I will try and create a new storage domain again, but remove it from the data center, and perhaps see if the HE will deploy to it.

 

The main goal was to have no downtime, but if it is going to be too complex, I think my next option will be to create a new HE, and attach the current storage domains. Obviously it is going to take a bit of planning, as I will need to configure all the networks etc. from scratch again.

 

Thanks

 

Anton Louw

Cloud Engineer: Storage and Virtualization at Vox

T:  087 805 0000 | D: 087 805 1572 M: N/A E: anton.louw@voxtelecom.co.za A: Rutherford Estate, 1 Scott Street, Waverley, Johannesburg www.vox.co.za

From: Strahil Nikolov <hunter86_bg@yahoo.com>
Sent: 26 April 2020 08:55
To: Yedidyah Bar David <didi@redhat.com>; Anton Louw <Anton.Louw@voxtelecom.co.za>
Cc: users@ovirt.org
Subject: Re: [ovirt-users] Re: Move Hosted Engine VM to a different storage domain

 

On April 26, 2020 9:39:07 AM GMT+03:00, Yedidyah Bar David <didi@redhat.com> wrote:
>On Fri, Apr 24, 2020 at 1:04 PM Anton Louw
><Anton.Louw@voxtelecom.co.za>
>wrote:
>
>>
>>
>> Hi All,
>>
>>
>>
>> I know this question has been asked before, by myself included. I was
>> hoping that someone has run through the exercise of moving the hosted
>> engine VM to a different storage domain. I have tried many routes,
>but the
>> backup and restore does not work for me.
>>
>
>The "standard answer" is backup and restore. Why does it not work?
>
>
>>
>>
>> Is there anybody that can perhaps give me some guidelines or a
>process I
>> can follow?
>>
>
>I didn't try that myself.
>
>The best guidelines I can give you are: Try first on at a test system.
>Do
>the backup on the real machine, create some isolated VM (isolated so
>that
>it does not interfere with your hosts/storage) somewhere to be used as
>a
>test host (or a physical machine if you have one), some storage
>somewhere,
>and restore on it. Make it work. Document what you needed to do. Ask
>here
>with specific questions if/when you have them. Then do on the
>production
>setup.
>
>Also clarify your needs. Do you need no-downtime for the VMs? If so,
>that's
>more complex. If you don't, it might be enough/simpler to deploy a new
>setup and just import the existing storage. Do you have HA VMs? etc.
>
>
>>
>>
>> The reason I need to move the HE VM is because we are decommissioning
>the
>> current storage array where the HE VM is located.
>>
>
>Good luck!
>
>Best regards,
>
>
>>
>>
>> Thank you very much
>>
>> *Anton Louw*
>> *Cloud Engineer: Storage and Virtualization* at *Vox*
>> ------------------------------
>> *T:* 087 805 0000 | *D:* 087 805 1572
>> *M:* N/A
>> *E:* anton.louw@voxtelecom.co.za
>> *A:* Rutherford Estate, 1 Scott Street, Waverley, Johannesburg
>> www.vox.co.za
>>
>> [image: F] <https://www.facebook.com/voxtelecomZA>
>> [image: T] <https://www.twitter.com/voxtelecom>
>> [image: I] <https://www.instagram.com/voxtelecomza/>
>> [image: L] <https://www.linkedin.com/company/voxtelecom>
>> [image: Y] <https://www.youtube.com/user/VoxTelecom>
>>
>> [image: #VoxBrand]
>> <https://www.vox.co.za/fibre/fibre-to-the-home/?prod=HOME>
>> *Disclaimer*
>>
>> The contents of this email are confidential to the sender and the
>intended
>> recipient. Unless the contents are clearly and entirely of a personal
>> nature, they are subject to copyright in favour of the holding
>company of
>> the Vox group of companies. Any recipient who receives this email in
>error
>> should immediately report the error to the sender and permanently
>delete
>> this email from all storage devices.
>>
>> This email has been scanned for viruses and malware, and may have
>been
>> automatically archived by *Mimecast Ltd*, an innovator in Software as
>a
>> Service (SaaS) for business. Providing a *safer* and *more useful*
>place
>> for your human generated data. Specializing in; Security, archiving
>and
>> compliance. To find out more Click Here
>> <https://www.voxtelecom.co.za/security/mimecast/?prod=Enterprise>.
>>
>>
>> _______________________________________________
>> Users mailing list -- users@ovirt.org
>> To unsubscribe send an email to users-leave@ovirt.org
>> Privacy Statement: https://www.ovirt.org/privacy-policy.html
>> oVirt Code of Conduct:
>> https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
>>
>https://lists.ovirt.org/archives/list/users@ovirt.org/message/V3PRBRZD7SLUQSXPRJHWVR3FWNZM5SJS/
>>

If youchange the gluster volume you can use the 'hosted-engine' tool + migration of the data ?

The example is for Gluster, but also
hosted-engine --set-shared-config storage <server1>:/engine

hosted-engine --set-shared-config mnt_options
backup-volfile-servers=<server2>:<server3>

Best Regards,
Strahil Nikolov