Also if you look at the blog post linked on github page it has info about
increasing the ansible timeout on ovirt engine machine. This will be
necessary when dealing with large vms that take over 2 hours to export
On Sun, Aug 30, 2020 at 8:52 AM Jayme <jaymef(a)gmail.com> wrote:
You should be able to fix by increasing the timeout variable in
main.yml.
I think the default is pretty low around @ 600 seconds (10 minutes). I have
mine set for a few hours since I’m dealing with large vms. I’d also
increase poll interval as well so it’s not checking for completion every 10
seconds. I set my poll interval to 5 minutes.
I backup many large vms (over 1tb) with this playbook for the past several
months and never had a problem with it not completing.
On Sun, Aug 30, 2020 at 3:39 AM Stefan Wolf <shb256(a)gmail.com> wrote:
> Hello,
>
>
>
> >https://github.com/silverorange/ovirt_ansible_backup
>
> I am also still using 4.3.
>
> In my opinion this is by far the best and easiest solution for disaster
> recovery. No need to install an appliance, and if there is a need to
> recover, you can import the ova in every hypervisor - no databases, no
> dependency.
>
>
>
> Sometimes I ve issues with "TASK [Wait for export] " sometime it takes to
> long to export the ova. an I also had the problem, that the export already
> finished, but it was not realized by the script. In ovirt the export was
> finished and the filename was renamed from *.tmp to *.ova
>
>
>
> maybe you have an idea for me.
>
>
>
> thanks bye
>
> _______________________________________________
>
> Users mailing list -- users(a)ovirt.org
>
> To unsubscribe send an email to users-leave(a)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/Q7TKVK5TL6H...
>
>