Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE
prapul Absent Member.
Absent Member.
2034 views

Reached its inactivity timeout of 7200 seconds The agent on host will be shutdown

Hi ,

While tacking daily backup got the error below. please some one help me to sort out the issue.

Note-For this back we are faceing the issue day by one day back up got succssed and next day the same problem we are faceing.

 

[Normal] From: BSM@appsrv5.apeasternpower.com "" Time: 12-04-2016 11:23:50
Backup session 2016/04/12-6 started.

[Normal] From: BSM@appsrv5.apeasternpower.com "" Time: 12-04-2016 11:23:50
The session "2016/04/12-5" will be restarted.

[Warning] From: BSM@appsrv5.apeasternpower.com "Rman and Logical Backup" Time: 12-04-2016 11:23:51
[61:7010] Medium 3302960a:56ac4c68:0640:0001 in prealloc list of the device "HP:Ultrium 6-SCSI_1_appsrv5"
is protected and full or have copies.

[Warning] From: BSM@appsrv5.apeasternpower.com "Rman and Logical Backup" Time: 12-04-2016 11:23:51
[61:7010] Medium 3302960a:56b01e4b:0edc:0001 in prealloc list of the device "HP:Ultrium 6-SCSI_1_appsrv5"
is protected and full or have copies.

[Warning] From: BSM@appsrv5.apeasternpower.com "Rman and Logical Backup" Time: 12-04-2016 11:23:51
[61:7010] Medium 3302960a:568611d1:126c:0001 in prealloc list of the device "HP:Ultrium 6-SCSI_1_appsrv5"
is protected and full or have copies.

[Warning] From: BSM@appsrv5.apeasternpower.com "Rman and Logical Backup" Time: 12-04-2016 11:23:51
[61:7010] Medium 3302960a:569379ce:33c0:0001 in prealloc list of the device "HP:Ultrium 6-SCSI_1_appsrv5"
is protected and full or have copies.

[Warning] From: BSM@appsrv5.apeasternpower.com "Rman and Logical Backup" Time: 12-04-2016 11:23:51
[61:7010] Medium 3302960a:569379cf:31b0:0001 in prealloc list of the device "HP:Ultrium 6-SCSI_1_appsrv5"
is protected and full or have copies.

[Warning] From: BSM@appsrv5.apeasternpower.com "Rman and Logical Backup" Time: 12-04-2016 11:23:51
[61:7010] Medium 3302960a:56a730dc:24b0:0001 in prealloc list of the device "HP:Ultrium 6-SCSI_1_appsrv5"
is protected and full or have copies.

[Warning] From: BSM@appsrv5.apeasternpower.com "Rman and Logical Backup" Time: 12-04-2016 11:23:51
[61:7010] Medium 3302960a:569f17b8:1120:0001 in prealloc list of the device "HP:Ultrium 6-SCSI_1_appsrv5"
is protected and full or have copies.

[Warning] From: BSM@appsrv5.apeasternpower.com "Rman and Logical Backup" Time: 12-04-2016 11:23:51
[61:7010] Medium 3302960a:568df3d0:1fa4:0001 in prealloc list of the device "HP:Ultrium 6-SCSI_1_appsrv5"
is protected and full or have copies.

[Warning] From: BSM@appsrv5.apeasternpower.com "Rman and Logical Backup" Time: 12-04-2016 11:23:51
[61:7010] Medium 3302960a:56a7325b:1818:0001 in prealloc list of the device "HP:Ultrium 6-SCSI_1_appsrv5"
is protected and full or have copies.

[Warning] From: BSM@appsrv5.apeasternpower.com "Rman and Logical Backup" Time: 12-04-2016 11:23:51
[61:7010] Medium 3302960a:54eab991:28f8:0001 in prealloc list of the device "HP:Ultrium 6-SCSI_1_appsrv5"
is protected and full or have copies.

[Warning] From: BSM@appsrv5.apeasternpower.com "Rman and Logical Backup" Time: 12-04-2016 11:23:51
[61:7010] Medium 3302960a:56ac4c6a:33c0:0001 in prealloc list of the device "HP:Ultrium 6-SCSI_1_appsrv5"
is protected and full or have copies.

[Normal] From: BMA@appsrv5.apeasternpower.com "HP:Ultrium 6-SCSI_1_appsrv5" Time: 12-04-2016 11:23:52
STARTING Media Agent "HP:Ultrium 6-SCSI_1_appsrv5"

[Normal] From: BMA@appsrv5.apeasternpower.com "HP:Ultrium 6-SCSI_1_appsrv5" Time: 12-04-2016 11:23:55
=> UMA@appsrv5.apeasternpower.com@Changer0:0:4:1
Loading medium from slot 18 to device Tape3:0:4:0C

[Normal] From: VBDA@oracls3 "/logicalbkp" Time: 12-04-2016 11:25:12
STARTING Disk Agent for oracls3:/logicalbkp "/logicalbkp".

[Normal] From: VBDA@oracls3 "/logicalbkp" Time: 12-04-2016 11:25:13
Filesystem Statistics:

Directories ........ 54
Regular files ...... 4263
Symbolic links ..... 0
SYSV FIFOs ......... 0
BSD sockets ........ 0
Block Devices ...... 0
Character Devices .. 0
Alias files ........ 0
Unknown Objects .... 0
------------------------------
Objects Total ...... 4317
Total Size ......... 430.09 GB

[Normal] From: VBDA@oracls2 "/Bkp" Time: 12-04-2016 11:23:56
STARTING Disk Agent for oracls2:/Bkp "/Bkp".

[Normal] From: VBDA@oracls2 "/Bkp" Time: 12-04-2016 11:23:56
Filesystem Statistics:

Directories ........ 6
Regular files ...... 442
Symbolic links ..... 0
SYSV FIFOs ......... 0
BSD sockets ........ 0
Block Devices ...... 0
Character Devices .. 0
Alias files ........ 0
Unknown Objects .... 0
------------------------------
Objects Total ...... 448
Total Size ......... 568.63 GB

[Critical] From: BDA-NET@oracls2 "/Bkp" Time: 12-04-2016 13:26:13
IPC failure reading NET message (IPC Read Error
System error: [110] Connection timed out
) => aborting.

[Critical] From: VBDA@oracls2 "/Bkp" Time: 12-04-2016 13:26:13
Unexpected close reading NET message => aborting.

[Critical] From: VBDA@oracls2 "/Bkp" Time: 12-04-2016 13:26:13
Connection to Media Agent broken => aborting.

[Normal] From: VBDA@oracls2 "/Bkp" Time: 12-04-2016 13:26:13
ABORTED Disk Agent for oracls2:/Bkp "/Bkp".

[Major] From: BSM@appsrv5.apeasternpower.com "Rman and Logical Backup" Time: 12-04-2016 15:11:46
[61:1002] The VBDA named "/logicalbkp" on host oracls3
reached its inactivity timeout of 7200 seconds.
The agent on host will be shutdown.

[Normal] From: BMA@appsrv5.apeasternpower.com "HP:Ultrium 6-SCSI_1_appsrv5" Time: 12-04-2016 15:13:07
Tape3:0:4:0C
Medium header verification completed, 0 errors found.

[Normal] From: BMA@appsrv5.apeasternpower.com "HP:Ultrium 6-SCSI_1_appsrv5" Time: 12-04-2016 15:13:27
Ejecting medium '18'.

[Normal] From: BMA@appsrv5.apeasternpower.com "HP:Ultrium 6-SCSI_1_appsrv5" Time: 12-04-2016 15:13:27
=> UMA@appsrv5.apeasternpower.com@Changer0:0:4:1
Unloading medium to slot 18 from device Tape3:0:4:0C

[Normal] From: BMA@appsrv5.apeasternpower.com "HP:Ultrium 6-SCSI_1_appsrv5" Time: 12-04-2016 15:14:09
COMPLETED Media Agent "HP:Ultrium 6-SCSI_1_appsrv5"

[Critical] From: BSM@appsrv5.apeasternpower.com "Rman and Logical Backup" Time: 12-04-2016 15:14:09
None of the Disk Agents completed successfully.
Session has failed.

[Normal] From: BSM@appsrv5.apeasternpower.com "Rman and Logical Backup" Time: 12-04-2016 15:14:09

Backup Statistics:

Session Queuing Time (hours) 0.00
-------------------------------------------
Completed Disk Agents ........ 0
Failed Disk Agents ........... 2
Aborted Disk Agents .......... 0
-------------------------------------------
Disk Agents Total ........... 2
===========================================
Completed Media Agents ....... 1
Failed Media Agents .......... 0
Aborted Media Agents ......... 0
-------------------------------------------
Media Agents Total .......... 1
===========================================
Mbytes Total ................. 605134 MB
Used Media Total ............. 1
Disk Agent Errors Total ...... 2

 

0 Likes
7 Replies
Micro Focus Expert
Micro Focus Expert

Re: Reached its inactivity timeout of 7200 seconds The agent on host will be shutdown

Hello

BMA server appsrv5.apeasternpower.com is losing connection with VBDA client for any reason, the first step will be enable " reconnect broken connection into backup specification.

Go to backup properties-options-backup specifications option-advance

Check option "reconnect broken conenction"

Best Regards

 

Honored Contributor.. TobiasPätz Honored Contributor..
Honored Contributor..

Re: Reached its inactivity timeout of 7200 seconds The agent on host will be shutdown

Does it appear during Oracle Redo Log backup?

If have a similar problem, but with SAP and Oracle, and if too many (e.g. >500) Redo Logs are created between two backups, the backup begins but don't backup any file.

You should give us a bit more information, which version of DP, is it happen to just one system or to any, and so on ..

 

BR

Tobias

0 Likes
Established Member.. dirkdevos
Established Member..

Re: Reached its inactivity timeout of 7200 seconds The agent on host will be shutdown

Thanks for the information. I started seeing similar errors. Does anybody know if there is a global variable that can be set instead of having to remember to do it for each backup spesification?

Thanks

0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: Reached its inactivity timeout of 7200 seconds The agent on host will be shutdown

What Data Protector version is this? Recent versions (A.09.05 and later) have TCP keep alive enabled by default usually removing this kind of issues.

Regards,
Sebastian Koehler

---
Please use the Like button below, if you find this post useful.
Established Member.. dirkdevos
Established Member..

Re: Reached its inactivity timeout of 7200 seconds The agent on host will be shutdown

We currently have version 9.06.

0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: Reached its inactivity timeout of 7200 seconds The agent on host will be shutdown

Another reason for this could be a very deep file system with loads of files and directories. Disabling tree walk and optimizing read operation (e.g. disable on-read scan in Virus scanners) could help to resolve the issue.

Regards,
Sebastian Koehler

---
Please use the Like button below, if you find this post useful.
Established Member.. dirkdevos
Established Member..

Re: Reached its inactivity timeout of 7200 seconds The agent on host will be shutdown

Sebastian,

Thank you for the suggestions but most of my servers are Linux based and on the few Windows servers disabling the on-read scan is not an option. It appears that the TCP keep-alive setting has done the trick for me.

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.