>My job cancels exactly 15 min after entering the wait mode for a new
>tape. In the VMware settings there is an idle timeout set to 900 sec
>(i.e. 15 min).
>
>The timeout doesn't exactly fit to that kind of connection, but you
>never know.
>
>I disabled this timeout now and restarted my backup. In 7 hours I will
>see the result.
>
>But even if this setting caused the trouble, I would have thought the
>heartbeat should solve this (idle connection timeout).
>
>Again, it would be good to know if the heartbeat should be active during
>waiting for a tape.
>
>
>
>Thank you again.
>
>Markus
>
>
>
>Hi Markus,
>
>
>
>I searched for an appropriate idle setting, but didn't find some. Can
>you give me a hint, where to look?
>
>
>
>By the way, all jobs, which are failing, have "Run Before" and "Run
>After" scripts assigned (create and delete a systemstate file or stop
>and start a SQL-Server).
>
>Regards
>
>Michael
Hi Michael,
it seems that this mentioned setting solved my problem. The weekend job finished without errors.
Here is the setting I changed:
In the vCenter server settings go to advanced settings (in German Erweiterte Einstellungen).
There you will find the switch: vpxd.httpClientIdleTimeout
The default value is 900.
I changed it to -1 (disable).
That worked for me.
The description of this switch doesn’t exactly fit on my problem, but the value of 900 sec (15 min) matched exactly. Therefore I gave it a try. I hope this really was the reason and my backup keeps running.
Perhaps this solves your problems, too.
@Tom:
I’m using bacula 5.2.5 from Ubuntu.
But I would believe the heartbeat should be the same here as in 5.2.10 which you checked.
Maybe I’ll find out some more…
Regards,
Markus