Highlighted
Respected Contributor.
Respected Contributor.
2660 views

Data Protector backup impossible with error 61:1005

Hi guys,
 
I searched and read a lot of messages, but cannot have solution for the error 61:1005.
I have 90 servers and only 1 get this error.
 
I reset the memory on the host, the backup started and the session was stopped after a few minutes, always with the same error.
 
On the host, I get :
 
Mar 31 01:01:55 myhost kernel: vbda[17716]: segfault at 0 ip 00007f3ae034e70c sp 00007fffbd469458 error 4 in libc-2.12.so[7f3ae02d3000+18a000]

 

I already reinstalled the agences, deployed from GUI and manually. But still doesn't work.
 
DP 6.2 
Cell on Windows 2008 R2
Host system : CentOS 6.4 64bits
 
What can I do ?
Can someone has idea for a solution ?
 
Thanks.
0 Likes
5 Replies
Highlighted
Absent Member.
Absent Member.

Re: Data Protector backup impossible with error 61:1005

You really haven't given us much to go on here.  What type of backup are you doing?  For example is it a File system backup, and Applications Integration backup, a VMware backup, something else?  What is teh full text of the error?  You can edit it to take out specific machine names

 

The snippet you included indicated a segmentation fault, which means a Core file was probably created.  It is coming from the VBDA (Disk  Agent) module.  I did find one lab case with the 'libc-2.12.so' error, but that was for DP 7.0 and was coming from the Media Agent.  This was resolved by getting current with patches

 

I found a fix when doing a VMware backup which was implemented in the 6.21 patch bundle.  There were a lot of fixes made in this patch bundle, and, if you are oly on 6.20, I would recommend that you upgrade to 6.21, and install subsequent patches

 

I suggest that, if you are not on 6.21, to download the patch bundle from

 

http://support.openview.hp.com/selfsolve/patches

 

You will need to have a UNIX-based (HPUX, Linux or Solaris) Installation server to download this patch bundle.  Get teh bundle installed, and also download the subsequent patches that you will find on the same site.  For this issue, I recommand that you download and install at least the Core and Disk Agent patches

0 Likes
Highlighted
Respected Contributor.
Respected Contributor.

Re: Data Protector backup impossible with error 61:1005

Hi Bob,

 

Sorry for too poor information from me.

It is a File system backup in incremental (incr).

 

 

This is the session output :

===

[Normal] From: BSM@bkpinst.domain.com "homes"  Time: 2014-04-03 01:00:05
Backup session 2014/04/03-3 started.
 
[Normal] From: BMA@bkpinst.domain.com "LTO4_2"  Time: 2014-04-03 01:00:10
STARTING Media Agent "LTO4_2"
 
[Normal] From: BMA@bkpinst.domain.com "LTO4_2"  Time: 2014-04-03 01:00:15
Par : UMA@bkpinst.domain.com@Changer0:0:1:1
Loading medium from slot 68 to device Tape1:0:1:0C
 
[Normal] From: VBDA@myhost.domain.com "/exports/home"  Time: 2014-04-03 01:01:35
STARTING Disk Agent for myhost.domain.com:/exports/home "/exports/home".
 
[Major] From: BSM@bkpinst.domain.com "homes"  Time: 2014-04-03 01:02:07
[61:1005]   Got unexpected close from VBDA on myhost.domain.com.
 
[Normal] From: BMA@bkpinst.domain.com "LTO4_2"  Time: 2014-04-03 01:05:12
Tape1:0:1:0C
Medium header verification completed, 0 errors found.
 
[Normal] From: BMA@bkpinst.domain.com "LTO4_2"  Time: 2014-04-03 01:05:32
Par : UMA@bkpinst.domain.com@Changer0:0:1:1
Unloading medium to slot 68 from device Tape1:0:1:0C
 
[Normal] From: BMA@bkpinst.domain.com "LTO4_2"  Time: 2014-04-03 01:05:52
COMPLETED Media Agent "LTO4_2"
 
[Critical] From: BSM@bkpinst.domain.com "homes"  Time: 2014-04-03 01:05:52
None of the Disk Agents completed successfully.
Session has failed.
 
[Normal] From: BSM@bkpinst.domain.com "homes"  Time: 2014-04-03 01:05:52
 
Backup Statistics:
          
Session Queuing Time (hours)         0.00        
-------------------------------------------      
Completed Disk Agents ........          0          
Failed Disk Agents ...........          1          
Aborted Disk Agents ..........          0          
-------------------------------------------      
Disk Agents Total  ...........          1          
===========================================      
Completed Media Agents .......          1          
Failed Media Agents ..........          0          
Aborted Media Agents .........          0          
-------------------------------------------      
Media Agents Total  ..........          1          
===========================================      
Mbytes Total .................       0 MB        
Used Media Total .............          0          
Disk Agent Errors Total ......          0    
===
 
 
 
 
This is the 61:1005 error description
===
[Major] From: BSM@bkpinst.domain.com "homes"  Time: 2014-04-03 01:02:07
[61:1005]      Got unexpected close from VBDA on myhost.domain.com.
 
The agent or monitor did not properly terminate. There are 
several probable causes. First is, that the process was killed by user 
or administrator of the machine, second, that there was not enough memory 
for the agent to complete the backup. 
===
 
 
Ok, I try patches.
Thanks for your help.
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Data Protector backup impossible with error 61:1005

Before you apply patches, check the Disk Agent server 'myhost.domain.com', and run a 'ps -ef | grep omni' to see if there are any hanging 'vbda' processes (or any other process for that matter, the 'ps -ef' should return only the 'grep').  If you find any, go ahead and kill them, you may need to use 'kill -9'

0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Data Protector backup impossible with error 61:1005

So what's the result?

0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Data Protector backup impossible with error 61:1005

yes, what was the result.

Im having what seems to be the same issue where the VBDA is core dumping on RHEL 6.4

 

Dec 4 00:00:16 hsmplfs017 xinetd[15053]: START: omni pid=32722 from=::ffff:10.195.43.50
Dec 4 00:00:16 hsmplfs017 kernel: vbda[32422]: segfault at 7ffd60000000 ip 00007f8fed3f05fc sp 00007ffd60973ac8 error 4 in libc-2.12.so[7f8fed375000+18a000]
Dec 4 00:00:16 hsmplfs017 abrt[32723]: Saved core dump of pid 32422 (/opt/omni/lbin/vbda) to /var/spool/abrt/ccpp-2015-12-04-00:00:16-32422 (1687552 bytes)
Dec 4 00:00:16 hsmplfs017 abrtd: Directory 'ccpp-2015-12-04-00:00:16-32422' creation detected
Dec 4 00:00:16 hsmplfs017 xinetd[15053]: EXIT: omni signal=11 pid=32422 duration=21(sec)
Dec 4 00:00:37 hsmplfs017 xinetd[15053]: START: omni pid=32724 from=::ffff:10.195.43.50
Dec 4 00:00:37 hsmplfs017 kernel: vbda[32722]: segfault at 7ffd60000000 ip 00007fa77d1235fc sp 00007ffd603209c8 error 4 in libc-2.12.so[7fa77d0a8000+18a000]
Dec 4 00:00:37 hsmplfs017 abrt[32725]: Saved core dump of pid 32722 (/opt/omni/lbin/vbda) to /var/spool/abrt/ccpp-2015-12-04-00:00:37-32722 (1687552 bytes)
Dec 4 00:00:37 hsmplfs017 abrtd: Directory 'ccpp-2015-12-04-00:00:37-32722' creation detected
Dec 4 00:00:38 hsmplfs017 xinetd[15053]: EXIT: omni signal=11 pid=32722 duration=22(sec)
Dec 4 00:00:58 hsmplfs017 xinetd[15053]: START: omni pid=32727 from=::ffff:10.195.43.50
Dec 4 00:00:58 hsmplfs017 kernel: vbda[32724]: segfault at 7fff20000000 ip 00007f1aa8b195fc sp 00007fff20b72928 error 4 in libc-2.12.so[7f1aa8a9e000+18a000]

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.