10:25 a.m.
Hi friends of oVirt,
Roughly 3 years ago a user asked about the options he had to move the hosted engine to
some other storage.
The answer by Simone Tiraboschi was that it would largely not be possible, because of
references in the database to the node the engine was hosted. This information would
prevent a successful move of the engine even with backup/restore.
The situation seem to have improved, but I'm not sure. So I ask.
We have to move our engine away from our older Cluster with NFS Storage backends (engine,
volumes, iso-images).
The engine should be restored on our new cluster that has a gluster volume available for
the engine. Additionally this 3-node cluster is running Guests from a Cinder/Ceph storage
Domain.
I want to restore the engine on a different cluster to a different storage domain.
Reading the documentation at
https://www.ovirt.org/documentation/self-hosted/chap-Backing_up_and_Resto...
I am wondering whether oVirt Nodes (formerly Node-NG) are capable of restoring an engine
at all. Do I need EL-based Nodes? We are currently running on oVirt Nodes.
- Andreas
1:51 p.m.
On Mon, Apr 1, 2019 at 5:26 PM <andreas.elvers+ovirtforum(a)solutions.work>
wrote:
Hi friends of oVirt,
Roughly 3 years ago a user asked about the options he had to move the
hosted engine to some other storage.
The answer by Simone Tiraboschi was that it would largely not be possible,
because of references in the database to the node the engine was hosted.
This information would prevent a successful move of the engine even with
backup/restore.
The situation seem to have improved, but I'm not sure. So I ask.
We have to move our engine away from our older Cluster with NFS Storage
backends (engine, volumes, iso-images).
The engine should be restored on our new cluster that has a gluster volume
available for the engine. Additionally this 3-node cluster is running
Guests from a Cinder/Ceph storage Domain.
I want to restore the engine on a different cluster to a different storage
domain.
Reading the documentation at
https://www.ovirt.org/documentation/self-hosted/chap-Backing_up_and_Resto...
I am wondering whether oVirt Nodes (formerly Node-NG) are capable of
restoring an engine at all. Do I need EL-based Nodes? We are currently
running on oVirt Nodes.
Yes, now you can do it via backup and restore:
take a backup of the engine with engine-backup and restore it on a new
hosted-engine VM on a new storage domain with:
hosted-engine --deploy --restore-from-file=mybackup.tar.gz
- Andreas
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/Y7EPAGSARSU...
3:19 a.m.
New subject: 4.2 / 4.3 : Moving the hosted-engine to another storage
Thanks for your answer.
Yes, now you can do it via backup and restore:
take a backup of the engine with engine-backup and restore it on a new
hosted-engine VM on a new storage domain with:
hosted-engine --deploy --restore-from-file=mybackup.tar.gz
That is great news. Just to clear things up completely:
- This backup command is sufficient ? No further switches ?
"engine-backup --mode=backup --file=[EngineBackupFile] --log=[LogFILE]"
- Do I need to place the node to which I want to deploy engine into maintenance
before doing the backup? This is referred in the stated documentation as:
"If a hosted-engine host is carrying a virtual load at the time of backup [...]
then a host [...] cannot be used to deploy a restored self-hosted engine."
This is still true? If yes: all other precautions apply from that documentation?
- before creating the new engine on the new storage, the old engine need to be
un-deployed on all engine-HA hosts. I am unable to find information about this
issue. Just un-deploy via web ui?
- I want to deploy on a gluster volume that has been automatically created by the
Node setup. The file /etc/gluster/glusterd.vol does not carry
"option rpc-auth-allow-insecure on" which is mentioned in the documentation.
Do I need to follow the instructions for gluster, or are settings already sufficiently
set by the automatic gluster deployment done by oVirt Node setup? I already
have some VM images running on that gluster storage anyway.
Thanks for your help.
- Andreas
3:22 a.m.
On Tue, Apr 2, 2019 at 10:20 AM <andreas.elvers+ovirtforum(a)solutions.work>
wrote:
Thanks for your answer.
> Yes, now you can do it via backup and restore:
> take a backup of the engine with engine-backup and restore it on a new
> hosted-engine VM on a new storage domain with:
> hosted-engine --deploy --restore-from-file=mybackup.tar.gz
That is great news. Just to clear things up completely:
- This backup command is sufficient ? No further switches ?
"engine-backup --mode=backup --file=[EngineBackupFile] --log=[LogFILE]"
Yes, right.
- Do I need to place the node to which I want to deploy engine into
maintenance
before doing the backup? This is referred in the stated documentation as:
"If a hosted-engine host is carrying a virtual load at the time of
backup [...]
then a host [...] cannot be used to deploy a restored self-hosted
engine."
This is still true? If yes: all other precautions apply from that
documentation?
It's a good idea but it's not strictly required.
- before creating the new engine on the new storage, the old engine
need
to be
un-deployed on all engine-HA hosts. I am unable to find information
about this
issue. Just un-deploy via web ui?
No need for that; but you will required to redeploy them from the new
engine to update their configuration.
- I want to deploy on a gluster volume that has been automatically created
by the
Node setup. The file /etc/gluster/glusterd.vol does not carry
"option rpc-auth-allow-insecure on" which is mentioned in the
documentation.
Do I need to follow the instructions for gluster, or are settings
already sufficiently
set by the automatic gluster deployment done by oVirt Node setup? I
already
have some VM images running on that gluster storage anyway.
Thanks for your help.
- Andreas
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/TQNWNUHROMQ...
3:36 a.m.
On Tue, Apr 2, 2019 at 11:24 AM Simone Tiraboschi <stirabos(a)redhat.com> wrote:
On Tue, Apr 2, 2019 at 10:20 AM <andreas.elvers+ovirtforum(a)solutions.work> wrote:
>
> Thanks for your answer.
>
> > Yes, now you can do it via backup and restore:
> > take a backup of the engine with engine-backup and restore it on a new
> > hosted-engine VM on a new storage domain with:
> > hosted-engine --deploy --restore-from-file=mybackup.tar.gz
>
> That is great news. Just to clear things up completely:
>
> - This backup command is sufficient ? No further switches ?
> "engine-backup --mode=backup --file=[EngineBackupFile] --log=[LogFILE]"
Yes, right.
Just 'engine-backup' should be enough for taking a backup, in 4.3.
See also: https://bugzilla.redhat.com/show_bug.cgi?id=1530031
>
>
> - Do I need to place the node to which I want to deploy engine into maintenance
> before doing the backup? This is referred in the stated documentation as:
>
> "If a hosted-engine host is carrying a virtual load at the time of backup
[...]
> then a host [...] cannot be used to deploy a restored self-hosted engine."
>
> This is still true? If yes: all other precautions apply from that documentation?
It's a good idea but it's not strictly required.
>
> - before creating the new engine on the new storage, the old engine need to be
> un-deployed on all engine-HA hosts. I am unable to find information about this
> issue. Just un-deploy via web ui?
No need for that; but you will required to redeploy them from the new engine to update
their configuration.
>
>
> - I want to deploy on a gluster volume that has been automatically created by the
> Node setup. The file /etc/gluster/glusterd.vol does not carry
> "option rpc-auth-allow-insecure on" which is mentioned in the
documentation.
> Do I need to follow the instructions for gluster, or are settings already
sufficiently
> set by the automatic gluster deployment done by oVirt Node setup? I already
> have some VM images running on that gluster storage anyway.
>
> Thanks for your help.
> - Andreas
> _______________________________________________
> Users mailing list -- users(a)ovirt.org
> To unsubscribe send an email to users-leave(a)ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/TQNWNUHROMQ...
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/A3H7FUPRUU4...
--
Didi
5:27 a.m.
New subject: 4.2 / 4.3 : Moving the hosted-engine to another storage
No need for that; but you will required to redeploy them from the
new
engine to update their configuration.
so I keep the old engine running while deploying the new engine on a different
storage? Curious.
I don't understand what "redeploy them [the old engine hosts] from
the new engine to update their configuration" means.
In fact the current engine incarnation is running on an old cluster, that
has no access to the new storage (the cluster is to go away).
The engine is also managing the new cluster to which we want to move the engine.
The engine is the only piece that keeps us from shutting down the old cluster.
That's the motivation for restoring the engine on the new cluster.
3:12 a.m.
On Tue, Apr 2, 2019 at 12:40 PM Andreas Elvers <
andreas.elvers+ovirtforum(a)solutions.work> wrote:
> No need for that; but you will required to redeploy them from the new
> engine to update their configuration.
so I keep the old engine running while deploying the new engine on a
different
storage? Curious.
No, you will need to shut it down: having two distinct engines running at
the same time can be really destructive.
Please carefully follow the documentation.
Other hosts and other virtual machines can be up at restore time.
I don't understand what "redeploy them [the old engine
hosts] from
the new engine to update their configuration" means.
In fact the current engine incarnation is running on an old cluster, that
has no access to the new storage (the cluster is to go away).
The engine is also managing the new cluster to which we want to move the
engine.
The engine is the only piece that keeps us from shutting down the old
cluster.
That's the motivation for restoring the engine on the new cluster.
You will have only the new cluster:
then choose the remaining hosted-engine hosts one by one, set them into
maintenance mode, and click reinstall from the engine to update their
hosted-engine configuration.
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/WVOFX4ZXDF4...
2090
days inactive
2092
days old
6 comments
4 participants
participants (4)
-
Andreas Elvers -
andreas.elvers+ovirtforum＠solutions.work
-
Simone Tiraboschi -
Yedidyah Bar David