On Fri, Dec 31, 2021 at 2:40 AM Strahil Nikolov via Users <users@ovirt.org> wrote: > > The migration from 4.3 to 4.4 is done by the same method... It always worked > but for major version upgrade there is a strict requirement which version the > backup was done.
A small clarification: engine-backup's backup/restore never intended to support, let's call this, "functional downgrade" - restoring to a version older than the one used for backup. For a long time, it supported only restoring to the same X.Y, ignoring Z. In 3.6->4.0 and 4.3->4.4 we also patched it to allow, as you mention, upgrading, as a means to migrate to a new OS version. It's quite likely we'll do the same in 4.4->4.5, because we plan to support also CentOS Stream 9. At some point in 4.4, we noticed that upgrading from a too-old 4.3 is broken, so we also patched it to require a minimal 4.3 (4.3.10). But until quite recently, downgrade inside the same X.Y was not prevented. See also: https://bugzilla.redhat.com/show_bug.cgi?id=1932392 Best regards, > > Even if it doesn't work - a fresh engine can still recover the VMs by > importing the storage domain (no VM snapshots are allowed), yet other > settings might be lost (VM networks, users,etc) > > Also, I forgot to mention that with GlusterFS, you can create a snapshot as a > point in time recovery (shut down the engine first as it has a DB) on the > Engine's volume. > > Happy Holidays! > > Best Regards, > Strahil Nikolov > > On Fri, Dec 31, 2021 at 2:33, Strahil Nikolov > <hunter86...@yahoo.com> wrote: > Well, you can shut down the engine (don't forget the global maintenance), yum > update, reboot -> the host is updated > > Then wait for ovirt-ha-agent & ovirt-ha-broker to bring the engine up. > Global maintenance, wipe the storage (assuming NFS/GlusterFS is used) or at > least rename the subdirectory to something different. > Restore from backup and it should be back as new. > > > > Best Regards, > Strahil Nikolov > > On Tue, Dec 28, 2021 at 0:27, Joseph Goldman > <jos...@goldman.id.au> wrote: > _______________________________________________ > Users mailing list -- users@ovirt.org > To unsubscribe send an email to users-le...@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/SZWVLPZDESDW24FHPDPOBXZR26RF3WAG/ > > _______________________________________________ > Users mailing list -- users@ovirt.org > To unsubscribe send an email to users-le...@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/FVFKEMSGQEMVOUMLRPPQE362SYDZRNF6/ -- Didi _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/QO3BNFISCEM4JZEHVPDISYHPNXILHQNS/
