Is it possible to recover from a failed Engine host?
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --fxLCZxSOl6pkKRnM6nkz3jT54eXm9sPCZ Content-Type: multipart/mixed; boundary="fZelWLxoG42Wr2qdshltYuoQLPuE0QWyK"; protected-headers="v1" From: ~Stack~ <i.am.stack@gmail.com> To: users <users@ovirt.org> Message-ID: <34dcadc9-6e2c-657a-d065-9af80582860d@gmail.com> Subject: Is it possible to recover from a failed Engine host? --fZelWLxoG42Wr2qdshltYuoQLPuE0QWyK Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable Greetings, I have a dev environment where it seems the hard drive on our Engine host kicked the bucket (Yeah, I know. Smartmon. I watch it closely on the systems I care about - this was a learning environment for me so I didn't). The Hypervisors are fine and the VM's running on the Hypervisors are fine...But I can't manage any of the Hypervisors. To make things a bit more tricky, the SQL and the backups were on the drive that died. I really don't have anything from that host. It's dev. I can rebuild. But it is also a learning environment for me so might as well use this to lea= rn. Is it possible for me to build a new Engine host and attach it to an existing hypervisor environment? Better yet, would this be something I could do as a hosted-engine-deploy? (something I haven't experimented with yet.) Again, this is a play ground so if it goes horrifically wrong...oh well. But I would really like to try to recover it for the learning experience. I've been poking around in the documentation but I haven't seen anything that seems to address this issue directly. Thoughts? Thanks! ~Stack~ --fZelWLxoG42Wr2qdshltYuoQLPuE0QWyK-- --fxLCZxSOl6pkKRnM6nkz3jT54eXm9sPCZ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJa6akpAAoJELkej+ysXJPmLgkQAJCtNrBb1y5mUb6pgP+DIXUn 8Z+0edlh0Q+hiSv/v6py+rk6pvviHxRIcWkSnI+TSKBKTavjel1aiSJoqUFcDHl0 olTkCrinB7Vq88bR1HNDB9UFK6FHUjIgvGwnMbM9KnczlKTr7rC6K+K7/f+GcrVS +nT76smXRz41TRT5I3xwy0K6gaSnRJvthR1ywDvxTHk5IkSuMmiBf3EpdZzTojBT /hYPXk0o68L0i20837pzMLILEnC54pzvUbbDykHrQ2tr2U/M/KySkwsUkgnZBCME HJ1YYE4ZGbAS0+V4rOmKAprVL59w9Yjq6ek44TVtxsgRtg+W/5+YszfkaGEi51jz G8ZVNrejUdLbXxsRfAhR2SNambRxa8qQpZA2l+5YjX0/OgmxdmWAH2A+pHXSMad/ R5Q22jghRsdfJ8CSai6oAoeJAPLO211nz8iMergpKdL/lsZXxFMXqI1D5zbTdy18 JsiG47jMm2dYK+mlFNUkBs7bPzFPpkKVxXBfl0IjOquuGSujpZ39+M7he7FtJEdB VcqCVA1wL7rGV1QbOj2ITUu3OSpoTSoSRZ/2cK/DWNSEShcw2vslcyU1qcot+G0S hsoFncCvkHrao/Nycar9F77peTlxueqimQIauYi0sLJ4CI3cC1lBerwU/X85TqLL uw5PcdbZjWWFVXQ1kcSR =kTvV -----END PGP SIGNATURE----- --fxLCZxSOl6pkKRnM6nkz3jT54eXm9sPCZ--
On Wednesday, May 2, 2018 8:03:53 AM EDT ~Stack~ wrote:
Greetings,
I have a dev environment where it seems the hard drive on our Engine host kicked the bucket (Yeah, I know. Smartmon. I watch it closely on the systems I care about - this was a learning environment for me so I didn't).
The Hypervisors are fine and the VM's running on the Hypervisors are fine...But I can't manage any of the Hypervisors. To make things a bit more tricky, the SQL and the backups were on the drive that died. I really don't have anything from that host. It's dev. I can rebuild. But it is also a learning environment for me so might as well use this to learn.
Is it possible for me to build a new Engine host and attach it to an existing hypervisor environment? Better yet, would this be something I could do as a hosted-engine-deploy? (something I haven't experimented with yet.)
Again, this is a play ground so if it goes horrifically wrong...oh well. But I would really like to try to recover it for the learning experience. I've been poking around in the documentation but I haven't seen anything that seems to address this issue directly.
Thoughts?
Thanks! ~Stack~
As long as the storage domain is in tact you should be able to recover everything. And it does sound like this is the case as the VMs are still running. Basically you just install a new engine somewhere and then do the following: - Create new Data Center - Create new Cluster - You will need a host to add to your cluster. Add this host. - Create a small temporary storage domain, this will allow you to bring up the data center which in turn will allow you to IMPORT the existing storage domain. - Once the DC is up, you can 'import' the existing storage domain, it will warn you that the storage domain is still attached to another DC, but since that engine is gone, you can ignore that. - Once the new DC is imported you can stop/detach/remove the small temporary storage domain, which will make the imported storage domain, the master domain. Once all that is done, you can simply go to the storage domain, and 'import' whatever VM/template you have stored on the storage domain, and it will show up in the VM/template list. Then you add all your hosts and you should have a running environment again.
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --ctfx53MiZqRCLQuN349Q7xayO9KnTDvGF Content-Type: multipart/mixed; boundary="GvF5nnjZrCIy1kZudBM12Y9sRVO2O51nM"; protected-headers="v1" From: ~Stack~ <i.am.stack@gmail.com> To: users@ovirt.org Message-ID: <da7c2988-3777-021c-20cd-83f3ddd8c055@gmail.com> Subject: Re: [ovirt-users] Is it possible to recover from a failed Engine host? References: <34dcadc9-6e2c-657a-d065-9af80582860d@gmail.com> <1970074.h4FrLtsj84@awels> In-Reply-To: <1970074.h4FrLtsj84@awels> --GvF5nnjZrCIy1kZudBM12Y9sRVO2O51nM Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 05/02/2018 07:27 AM, Alexander Wels wrote:
On Wednesday, May 2, 2018 8:03:53 AM EDT ~Stack~ wrote:
Greetings,
I have a dev environment where it seems the hard drive on our Engine host kicked the bucket (Yeah, I know. Smartmon. I watch it closely on the systems I care about - this was a learning environment for me so I=
didn't).
The Hypervisors are fine and the VM's running on the Hypervisors are fine...But I can't manage any of the Hypervisors. To make things a bit=
more tricky, the SQL and the backups were on the drive that died. I really don't have anything from that host. It's dev. I can rebuild. Bu= t it is also a learning environment for me so might as well use this to = learn.
Is it possible for me to build a new Engine host and attach it to an existing hypervisor environment? Better yet, would this be something I=
could do as a hosted-engine-deploy? (something I haven't experimented with yet.)
Again, this is a play ground so if it goes horrifically wrong...oh wel= l. But I would really like to try to recover it for the learning experience. I've been poking around in the documentation but I haven't=
seen anything that seems to address this issue directly.
Thoughts?
Thanks! ~Stack~ =20 As long as the storage domain is in tact you should be able to recover =
everything. And it does sound like this is the case as the VMs are stil= l=20 running. Basically you just install a new engine somewhere and then do = the=20 following: =20 - Create new Data Center - Create new Cluster - You will need a host to add to your cluster. Add this host. - Create a small temporary storage domain, this will allow you to bring= up the=20 data center which in turn will allow you to IMPORT the existing storage= =20 domain. - Once the DC is up, you can 'import' the existing storage domain, it w= ill=20 warn you that the storage domain is still attached to another DC, but s= ince=20 that engine is gone, you can ignore that. - Once the new DC is imported you can stop/detach/remove the small temp= orary=20 storage domain, which will make the imported storage domain, the master= =20 domain. =20 Once all that is done, you can simply go to the storage domain, and 'im= port'=20 whatever VM/template you have stored on the storage domain, and it will= show=20 up in the VM/template list. Then you add all your hosts and you should = have a=20 running environment again. =20
Thank you! I will give it a try and see what happens. ~Stack~ --GvF5nnjZrCIy1kZudBM12Y9sRVO2O51nM-- --ctfx53MiZqRCLQuN349Q7xayO9KnTDvGF Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJa6bESAAoJELkej+ysXJPmSp4P/2ALK0ms28mbCSdryBymH4QL 29OrcSk+8LdMjwQiH1Xdl2Kv/fCWnC+6Eup7N35Zp0+DACWTghbiiIzAAxPOXEmh OGj+DR1MT8RG8w/2UocaadwPZPLhIMHnFw/zl0jj5FS9tVxqn25kcthePKxP5oC3 TmYT+NKGPd9sIMK6JQbUSlyVcUV8u/bB0hKCe22cOBZ7Qi/aKQ3McT7Blddh97zl wq5/1vKQmt/QWcCPw31DEJbvu1gpifBv9FoJV/CKc+EtpI7NOYJf/zDz6epuddQ3 7Usw1GBZp3p9cVUDAvl8vZtsr1ydfzxxPQ1ZD/lfCpAL/RSSlbeQZjh6t332LwCh Y8qNLn5xg2e/TQw/oO726QZVrmIBvXu3sWrwYXcVBjL0tS12VhS3ILxAVJ0L1NMr uFRl/x/NMgl1bi7pgR3S5dApi9shpwHUsuvEeB9NNDr1L3IU+uDjlffJU6V3myaN lrtNMd95RWUN+1LsAjTURKYJegS4V1XKTv8JRW+ETTICm4G+KCQG5/uBBI845ynJ Pydb7Ga5Qb04cIlfdRPpr0Ar/ekhHyIo034rY0GTERGqdjjeXMxfyQw1aM3sPMJl Xh1wCnTck2bAuAaU9DjDRJO2/S/4NeOHVBsDVPOLBXkicLEiorlcdVKTQ4gJqHof VDVyPtPfMBNOGahLDmyl =Ar9t -----END PGP SIGNATURE----- --ctfx53MiZqRCLQuN349Q7xayO9KnTDvGF--
participants (2)
-
Alexander Wels -
~Stack~