Hi Henry,
A few clarifications:
1) OVF is updated every 60 minutes by default:
$ ./engine-config --get OvfUpdateIntervalInMinutes
OvfUpdateIntervalInMinutes: 60 version: general
You can update that to another value, i.e., 5 minutes (engine restart is required afterwards):
$ ./engine-config --set OvfUpdateIntervalInMinutes=5
$ ./engine-config --get OvfUpdateIntervalInMinutes
OvfUpdateIntervalInMinutes: 5 version: general

2) If the primary engine crashed and some of the environment structure changes were done after the last OVF update, they will be "lost" - that is will not be recreated on the secondary engine.
I'm not aware of any solution for that, except a manual "Update OVFs" retrigger on a Storage Domain.
image.png

Thank you!

Pavel


On Fri, 15 Jan 2021 at 06:13, Henry lol <pub.virtualization@gmail.com> wrote:
Thanks Pavel,
it becomes clear now.

Have a nice weekend~!!

Sincerely

2021년 1월 15일 (금) 오전 9:24, Pavel Bar <pbar@redhat.com>님이 작성:
Hi Henry,
Answers inside!

Have a nice weekend :)

Pavel

On Thu, 14 Jan 2021 at 20:22, Henry lol <pub.virtualization@gmail.com> wrote:
Hi,

I have 2 questions about Disaster Recovery with Ansible.

1)
regarding Ansible failover, AFAIK, a mapping file must be generated before running failover.
then, should I periodically generate a new mapping file to reflect the latest structure of the environment?

Yes, generate it while your primary environment is up-and-running.
Regenerate after the environment structure changes.
Although no need to manually update it with the secondary site specific values (which are by default commented out) until you actually want to run the failover flow, just keep the created mapping skeleton file.
 

2)
I guess Ansible failover uses OVF_STOREs to restore the environment and OVF_STOREs in storage domains are updated every 1 min as default.
then, how to recover the changes made in the meantime?

AFAIK you might be "back in time" to the latest time when the OVF_STOREs were updated.
Not sure there is a solution.
I will verify that for you after the weekend.
 
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@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/IPMQQ4PXH7AG3YDFPJMOO772AI3UOWEQ/