cancel
Showing results for 
Search instead for 
Did you mean: 

Linux filesystem backup failed

Iwan_Tamimi
Level 6

We have encountered this error:

08/25/2010 06:47:58 - positioning 500091 to file 347
08/25/2010 06:49:16 - positioned 500091; position time: 0:01:18
08/25/2010 06:49:16 - begin writing
08/25/2010 07:07:56 - Error bpbrm (pid=29427) socket read failed: errno = 52 - Stream ioctl timeout
08/25/2010 07:08:07 - end writing; write time: 0:18:51
file read failed (13)


I don't think the problem is related to the network since we have 2 different file system backup on that systems, let says one policy only backup /d01/etopup the other policy only backup /d01/app. I never have problem with the first backup. The difference between the two file system, the later one has lots of file (80.000 plus). The backup is not always failed.

There is another error I see on the netbackup GUI:
1: (13) file read failed


Master: HP-UX 11.23,  NBU 6.5.4
Client: Red Hat Enterprise Linux Server release 5.3 7.0, File System: gfs2, NBU 6.5.4
1 ACCEPTED SOLUTION

Accepted Solutions

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified


I found this TechNote:

http://seer.entsupport.symantec.com/docs/303147.htm 

But I'm note convinced that the filename to be created should be MAX_FILES_PER_CLIENT.
The TN points to another TN for explanation, but that TN (http://seer.entsupport.symantec.com/docs/273884.htm) does not mention this file name at all.
The only reference to anything remotely close is MAX_FILES_PER_ADD.
This file specifies how many files should be backed up before recording the information in the catalog database. This seems to be applicable to your situation where lots of files are backed up.

You might want to open a call with Support to double check to file name. Or simply try one of them and see if it makes a difference,,, (My choice would be MAX_FILES_PER_ADD.)
 

View solution in original post

4 REPLIES 4

varunprakash
Level 5

Please attach bpbkar and bpcd client logs to find out the issue.

r u using flash backup option for this policy? (You have mentioned that it contains large no of files)

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified


I found this TechNote:

http://seer.entsupport.symantec.com/docs/303147.htm 

But I'm note convinced that the filename to be created should be MAX_FILES_PER_CLIENT.
The TN points to another TN for explanation, but that TN (http://seer.entsupport.symantec.com/docs/273884.htm) does not mention this file name at all.
The only reference to anything remotely close is MAX_FILES_PER_ADD.
This file specifies how many files should be backed up before recording the information in the catalog database. This seems to be applicable to your situation where lots of files are backed up.

You might want to open a call with Support to double check to file name. Or simply try one of them and see if it makes a difference,,, (My choice would be MAX_FILES_PER_ADD.)
 

View solution in original post

Iwan_Tamimi
Level 6

Hi All,

Thanks for answering my question.

I got from email from support that Netbackup 6.5.4 (and v. 7) does not support the gfs2 file system. Is that statement correct?   I am still looking for alternative.

@varunprakash I attached the bpbkar from the client, but the bpcd was not there yet one of the problem happenned on 08/25/2010 20:02:38

@Marianne van den Berg I will try your suggestion anyway.

Thank you.

iwan


Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Oops - GFS not mentioned at all in O/S compatibility lists:

NetBackup 6.x Operating System (CL) for Client,Server,NOM,NDMP,BMR,SAN Client,MSEO:  
http://support.veritas.com/docs/325328

NetBackup 7 Operating System (CL) for Client,Server,Dedupe,OpsCenter,NDMP,BMR,SAN Client,MSEO:    http://support.veritas.com/docs/337048