cancel
Showing results for 
Search instead for 
Did you mean: 

file read failed(13)

Hello,

 

Does anyone have a solutin about this issue?

 

02/07/2014 05:10:58 - Info nbjm(pid=21492) starting backup job (jobid=9093) for client JSS-DATA-S2, policy LD5_JSS_FILES_A, schedule Full  
02/07/2014 05:10:58 - Info nbjm(pid=21492) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=9093, request id:{61E0440F-85F6-4DBD-85C7-19072C59857F})  
02/07/2014 05:10:58 - requesting resource Any
02/07/2014 05:10:58 - requesting resource ld4-netbackup.NBU_CLIENT.MAXJOBS.JSS-DATA-S2
02/07/2014 05:10:58 - requesting resource ld4-netbackup.NBU_POLICY.MAXJOBS.LD5_JSS_FILES_A
02/07/2014 05:10:58 - granted resource ld4-netbackup.NBU_CLIENT.MAXJOBS.JSS-DATA-S2
02/07/2014 05:10:58 - granted resource ld4-netbackup.NBU_POLICY.MAXJOBS.LD5_JSS_FILES_A
02/07/2014 05:10:58 - granted resource NEMA40
02/07/2014 05:10:58 - granted resource HP.ULTRIUM5-SCSI.001
02/07/2014 05:10:58 - granted resource ld5-netbackup-hcart2-robot-tld-0
02/07/2014 05:10:59 - estimated 464298 Kbytes needed
02/07/2014 05:10:59 - Info nbjm(pid=21492) started backup (backupid=JSS-DATA-S2_1404274258) job for client JSS-DATA-S2, policy LD5_JSS_FILES_A, schedule Full on storage unit ld5-netbackup-hcart2-robot-tld-0
02/07/2014 05:10:59 - started process bpbrm (22696)
02/07/2014 05:11:05 - Info bpbrm(pid=22696) JSS-DATA-S2 is the host to backup data from     
02/07/2014 05:11:05 - Info bpbrm(pid=22696) reading file list for client        
02/07/2014 05:11:05 - connecting
02/07/2014 05:11:08 - Info bpbrm(pid=22696) starting bpbkar32 on client         
02/07/2014 05:11:08 - connected; connect time: 0:00:03
02/07/2014 05:11:10 - Error bpbrm(pid=22696) socket read failed, An existing connection was forcibly closed by the remote host.  (10054)
02/07/2014 05:11:13 - Info bpbkar32(pid=0) done. status: 13: file read failed       
02/07/2014 05:11:13 - end writing
file read failed(13)

1 Solution

Accepted Solutions
Accepted Solution!

Sure the client NBU version

Sure the client NBU version is up to date (7.6.0.1 or 7.6.0.2)?

I have seen instances in the past where a similar issue was resolved with NBU patching (but that was back in NBU 6.5.x days).

Another possibility is AntiVirus or other security software killing NBU processes.
See http://www.symantec.com/docs/TECH56658 

Because this seems to be the only client that is affected, you need to speak to system owners to find out what is different.
Has NBU backup ever worked on this system?
If so, when did it stop working?
What has changed?

View solution in original post

18 Replies

More Details please.. what is

More Details please..

what is the Netbackup version on the Client?

what is the backup selection on the policy?

Does the Mulitstream is enable do not?

 

File read failed could be

File read failed could be caused by few factors on the client side.

Are you able to capture the bpbkar log(also touch bpbkar_tr_touch) to know at which file is bptm timingout/crashed.

If you have the corresponding bptm/bpbrm log from the media server handling this job, will also help you to match the findings from both logs and drive further.

 

Thanks for your reply.   My

Thanks for your reply.

 

My netbackup is 7.6.0.1

It's backup C:\\ device

Does the Mulitstream is enable do not? <-- I'm not sure

Backup fails within 1 minute

Backup fails within 1 minute of starting and withing 2 seconds of connection established between media server and client.

We need to find out if network connection is broken on media server side or client side.

Is this the only client backing up to this media server that is failing?

OS on media server?
Windows version on client?

Logs needed for troubleshooting:

On media server: bpbrm
On client: bpbkar

If log folders do not exist, please create them under netbackup\logs on media server and client.

After next failure, copy logs to .txt files (e.g. bpbrm.txt) and upload as File attachments.

As a matter of interest - this is what NBU Status Code guide says about the 10054 TCP error seen in Job details:

On Windows systems, the client bpbkar log may contain a 10054 Connection
Reset Error (usually indicates a hardware error). Somewhere between the
NetBackup client and server, the connection was reset. When NetBackup
receives this error, it cannot continue the backup. This error has been attributed
to the following:
■ A hiccup in the network.
■ A bad network interface card on a NetBackup client.
■ A bad network interface card on the NetBackup server.
■ Faulty routers.
■ Any other applications that interfere with NetBackup connections.

do you have Stornext Client

do you have Stornext Client installed by any chance?

Thank Marianne,   My Media

Thank Marianne,

 

My Media Server OS: windows server 2008

Client: Windows server 2003

Attached is the log file

I think the problem is on client because we have total 30 clients, only this client is facing this issue. 

Thank again,

Thang

Have anyone can help, please?

Have anyone can help, please?

bpbkar log on the client

bpbkar log on the client shows that the backup was started but logging simply stopped before any data was transfered. As if bpbkar process was terminated/killed/crashed.

Please check Client's event logs - System and Application to see what happened at about 04:10 am yesterday morning.

You may also want to create a small test policy for this client and logon to this client before starting the backup.
Open Task Manager and Event Viewer, then start the backup. 

Check which processes are started and for errors in Event Viewer logs.

Hi Marianne, I just checked

Hi Marianne,

I just checked event view log ò client and see that at that time have an error as attached file.

Accepted Solution!

Sure the client NBU version

Sure the client NBU version is up to date (7.6.0.1 or 7.6.0.2)?

I have seen instances in the past where a similar issue was resolved with NBU patching (but that was back in NBU 6.5.x days).

Another possibility is AntiVirus or other security software killing NBU processes.
See http://www.symantec.com/docs/TECH56658 

Because this seems to be the only client that is affected, you need to speak to system owners to find out what is different.
Has NBU backup ever worked on this system?
If so, when did it stop working?
What has changed?

View solution in original post

I have been upgarde netbackup

I have been upgarde netbackup from 7.5 to 7.6.0.1

At this time, all master server and client is running on 7.6.0.1

 

Please see the rest of my

Please see the rest of my previous post as well.

FYI.  When i open netbackup

FYI. 

When i open netbackup client, and click "Select for backup"

I am facing an issue. Please see attached image.

I was remove and re-install netbackup client but still the same.

Do you have any idea?

I cannot tell you what is

I cannot tell you what is killing NBU on this client.

Have a look again at these points/questions in my earlier post:

Another possibility is AntiVirus or other security software killing NBU processes.
See http://www.symantec.com/docs/TECH56658 

Because this seems to be the only client that is affected, you need to speak to system owners to find out what is different.
Has NBU backup ever worked on this system?
If so, when did it stop working?
What has changed?

Is the backup of CIFS/SMB

Is the backup of CIFS/SMB shares?

Perhaps try:   http://www.symantec.com/business/support/index?page=content&id=TECH166496

(note how this TN says that in rare cases it can also happen with SAN attached storage).

You say client is W2003, which SP? Which x86/x64? Which Std, DC, Ent?

 

Oops - just seen that screen

Oops - just seen that screen shot of NbWin - ignore my post.  Sorry.

Have previous backups to this

Have previous backups to this client been successful? If so, there is the possibility of a DNS error.

When a bpbkar is started the client does a reverse lookup on the master server to authenticate. If the reverse lookup fails the client terminates the connection. To verify reverse lookup run the following commands from the client.

 

1.Install Path\Program Files\Veritas\Netbackup\bin > bpclntcmd -pn

This command will query the Master server and ask Who Am I.

   The Output should return the client's correct name and ip address

 

2.Install Path\Program Files\Veritas\Netbackup\bin > bpclntcmd -ip <ip address of master server>

  This command will do a reverse lookup on the master

To circumvent DNS Errors Symantec recommends the use of /etc/hosts files for host name resolution

 

 

Re: Have previous backups to this

create new policy .. it will work.