3:37 p.m.
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(a)gmail.com>
To: users(a)ovirt.org
Message-ID: <da7c2988-3777-021c-20cd-83f3ddd8c055(a)gmail.com>
Subject: Re: [ovirt-users] Is it possible to recover from a failed Engine
host?
References: <34dcadc9-6e2c-657a-d065-9af80582860d(a)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--