Hi all,One of our engines has had a DB failure* & it seems there was an unnoticed problem in its backup routine, meaning the last backup I've got is a couple of weeks old.
Luckily, VDSM has kept the underlying VMs running without any interruptions, so my objective is to get the HE back online & get the hosts & VMs back under its control with minimal downtime.
So, my questions are the following...
- What problems can I expect to have with VMs added/modified since the last backup?
- As it's only the DB that's been affected, can I skip redeploying the Engine & jump straight to restoring the DB & rerunning engine-setup?
- The original docs I read didn't mention that it's best to leave a host in maintenance mode before running the engine backup, so my plan is to install a new temporary host on a separate server, re-add the old hosts & then once everything's back up, remove the temporary host. Are there any faults in this plan?
- When it comes to deleting the old HE VM, the docs point to a paywalled guide on redhat.com...?
Note: If the Engine database is restored successfully, but the Engine virtual machine appears to be Down and cannot be migrated to another self-hosted engine host, you can enable a new Engine virtual machine and remove the dead Engine virtual machine from the environment by following the steps provided in https://access.redhat.com/solutions/1517683.Source: http://www.ovirt.org/documentation/self-hosted/chap-Backing_up_and_Restoring_an_EL-Based_Self-Hosted_Environment/
CentOS 7oVirt 4.0.4Gluster 3.8* Apparently a write somehow cleared fsync, despite not actually having been written to disk?! No idea how that happened...Many thanks,--Doug