Is there a way to change the length of time Avamar allows for the pre-execution and post-execution scripts to run? I have a job running on a Linux server with the Avamar v6.0.101-65 client that backs up an Informix database, but before backing it up, the database has to do a dump. I tell the database to perform the dump in a pre-execution script. Often the dump takes less than an hour, so it's usually not a problem, but every so often the dump may take longer. Unfortunately, Avamar seems to automatically give up on the pre-execution script after exactly one hour. I need to tell it somehow to not give up.
Solved! Go to Solution.
You can use the flag "--run-at-start-clause=timeout-seconds" to increase the timeout duration for your pre-script execution.
On linux server, create a file /usr/local/avamar/var/avtar.cmd and put this line in the file :
and specify the script timeout in seconds
For example, --run-at-start-clause=timeout-seconds=7200 will setup the script timeout for 2 hours
sandcruise beat me to it but I do have some information to add.
You can also specify this setting directly in the dataset:
Edit: Fixed a typo
Thank you both, sandcruise and ianderson, very much! I especially appreciate the prompt reply. This is exactly what I needed, and will save me a lot of headaches.
Ian Anderson When you make this change and click + button, is it supposed
to be listed under the Options variables on the far right of the screen for the specific dataset?
We are having the same timeout issue and I did the above fix twice to see where its registering this,
but still don't see it under Options - odd?
Also - does it ever revert back to the default option or does it keep your changes forever?
I have never seen a dataset value revert after one backup (except the "overtime" setting where there is an explicit option to permit overtime until successful backup).
I have had to make the dataset value edit 3 times now for 2 different db backups that work after I make the change, don't the next weekly backup. I never change it back, just change it to extend the timeout-seconds time.
Anyone else experience this? Ian Anderson can you ask QA to test this? Also it would be nice if the modified attribute displayed under Options when you do change it, otherwise not sure how you verify in the gui that you have made the modification?