Data Protector Support and News Forum
Showing results for 
Search instead for 
Do you mean 

reached its inactivity timeout of 7200 seconds.

Frequent Advisor

reached its inactivity timeout of 7200 seconds.

Hi,

                          reached its inactivity timeout of 7200 seconds.  My backup not completed due to this error message .

please suggest for solution.

2 REPLIES
Esteemed Contributor

Re: reached its inactivity timeout of 7200 seconds.

Hi Pankaj,

 

This is usually due to a timeout in the global file. Where do you get this message? (At the beginning of the backup job before data is transferred? At the end?) And for what agent? (BMA/VBDA/OB2BAR?) You need to give us a bit more info so we can point you in the right direction.

 

For example: If it's the DA and you have treewalk enabled and it is a filesystem with millions of files then sometimes the timeout SmDaIdleTimeout is too low. But if you extend this timeout then you also need to extend SmMaIdleTimeout.

cheers,
jenni

--------------------------------------------------------------------------------
If my post was useful, please click on KUDOS! "White Star"
Frequent Advisor

Re: reached its inactivity timeout of 7200 seconds.

Hi , Here is the full details of error message with Warning-

 


[Warning] From: BDA-NET@punmwbe1 "/home" Time: 10/27/2012 10:18:31 PM
Connection to BMA on host moh-ila-bkp1 lost, trying to reconnect.

 

 

Major] From: BSM@moh-ila-bkp1 "DC46_NSN_ASR_Incr" Time: 10/28/2012 8:00:37 AM
[61:1002] The BMA named "VLS2-DRV1" on host moh-ila-bkp1
reached its inactivity timeout of 8400 seconds.
The agent on host will be shutdown.