2:59 a.m.
Hi All,
I've been asked to test the HE restore process but after taking a look at the
documentation I'm afraid I'm none the wiser.
I thought there would be a simple 'restore in situ' option but it appears not.
My environments were build using ansible with a hostedengine .json answer file.
From what I've read so far it appears that a new HE VM needs to be built with new
engine storage etc
3:01 a.m.
...Hit send before I'd finished.
Is there a tried and tested simple solution for restoring a hosted engine in a 3 node HCI
GlusterFS 2+1 environment please?
Regards
Simon...
5:27 a.m.
On Tue, Aug 2, 2022 at 11:01 AM <simon(a)justconnect.ie> wrote:
Hi All,
I've been asked to test the HE restore process but after taking a look at the
documentation I'm afraid I'm none the wiser.
I thought there would be a simple 'restore in situ' option but it appears not.
Please clarify exactly what you mean.
Are you currently already in a restore situation, where something is
broken enough so that you want to restore from backup? What's broken?
Are you preparing/exercising for a future restore event? What
use-cases do you want to prepare/test for? E.g. it's very different to
prepare to a case where a trivial corruption/user-error/bug/whatever
"just" removed some critical files on your engine VM, and to prepare
to a case where the complete site/hardware went through a natural
disaster and you buy new hardware/storage/etc. and want to restore on
them. And obviously there are many other cases in-between/around
these.
My environments were build using ansible with a hostedengine .json
answer file.
Meaning, running the hosted_engine_setup role directly? Without
'hosted-engine --deploy'?
Nice to know about that - it's quite rare.
From what I've read so far it appears that a new HE VM needs to
be built with new engine storage etc
Correct, in most cases.
We do have a section about restoring a backup inside the engine VM,
assuming that it's still ok - search for "Overwriting a Self-Hosted
Engine from an Existing Backup".
On Tue, Aug 2, 2022 at 11:03 AM <simon(a)justconnect.ie> wrote:
...Hit send before I'd finished.
Is there a tried and tested simple solution for restoring a hosted engine in a 3 node HCI
GlusterFS 2+1 environment please?
Not sure about HCI/gluster - adding Ritesh.
Best regards,
--
Didi
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)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/IQ6P7L6H3BF...
--
Didi
6:51 p.m.
Many thanks for your help Didi.
I must've missed the following section you pointed out:
| We do have a section about restoring a backup inside the engine VM,
| assuming that it's still ok - search for "Overwriting a Self-Hosted
| Engine from an Existing Backup".
It worked perfectly thanks.
As for the build of a 3 node environment using Foreman and ansible, it takes about 1-2
hours from start to finish.
Kind Regards
Simon...
12:13 a.m.
On Thu, Aug 4, 2022 at 2:51 AM <simon(a)justconnect.ie> wrote:
Many thanks for your help Didi.
I must've missed the following section you pointed out:
| We do have a section about restoring a backup inside the engine VM,
| assuming that it's still ok - search for "Overwriting a Self-Hosted
| Engine from an Existing Backup".
It worked perfectly thanks.
Glad to hear that. Thanks for the update!
As for the build of a 3 node environment using Foreman and ansible, it
takes about 1-2 hours from start to finish.
Yes, we do run it routinely in our QE - but I seldom hear about real users
doing that...
And our QE did sometimes find bugs there, that did not affect
'hosted-engine --deploy', but I can't recall even one such bug report from
a real user.
The main practical difference between them, other than the obvious one of
having to provide all answers in a var file beforehand, is that it does not
use our ansible callback for generating the log files. Depending on how you
run ansible, this will likely make it somewhat harder to investigate
problems - with the callback, we log each time an ansible var changed its
value, but without this callback, you rely on the code having enough
'debug' tasks at relevant points.
Best regards,
--
Didi
640
days inactive
642
days old
4 comments
2 participants
participants (2)
-
simon＠justconnect.ie -
Yedidyah Bar David