Dear Quebek,
yes indeed, it is sap and we are experiencing serious problems with these queued jobs and unable to solve it for several months already even with the veritas support case we have.
your comments and suggestions would be more than welcome!
Hello
You did not confirm this is for sap hana... If it is try to extend this property backint_response_timeout on SAP end from default 10 minutes to 60.
Also in order to do not overtake NBU resources by this policy in its properties set "limit jobs per policy" to 16 or less. This should not acquire all NBU resources - jobs will be just queued...
Hope this helps anyhow...
Hi Quebek,
thanks for your comment. that's a very good direction
Yes, this is sap hana.
If i understand correctly the backint_response_timeout is the timeout that will cause a job to be canceled from the sap end if not completed.
this leads to the following article https://www.veritas.com/support/en_US/article.100043963 wich describes quite exctly our situation, i assume that this timeout does not work in our environment as described in the article.
I will have to check with the sap colleagues.
reducing the max jobs per policy limit has a negative impact instead of positive because of the way nbjm and nbrb allocate resources for the job and the load they put on the nbdb as per the following:
When a NetBackup media server is writing to disk storage, it updates the master server about the available capacity in each disk storage pool. After every 1 GB of data written, the media server sends the current capacity information to nbjm on the master server, and nbjm sends an RBdbUpdate message to nbrb, which triggers an update in NBDB.
article: https://www.veritas.com/support/en_US/article.100025235
however your comment was very helpful!
thank you
Hi
Well I can tell that in my env updating this property backint_response_timeout to bigger value helped... We were facing some issues where NBU domain was busy - and it did not accept the sap hana logs - when it was able to do it (after 10 mins) backint on hana end was already done/closed, and jobs were just piling up and exhausting the max streams and evetnually it was timing out with EC 54 ... so before I learnt about backint_response_timeout to bump it up I limited the policy to 16 instances and all other jobs were taken in and written to MSDP ;)
and what is your current config for backint_response_timeout?
thanks a lot!
