Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Error code 14

Created: 02 Oct 2012 | 11 comments

Hi All

Master server NBU version : VERSION NetBackup 7.1.0.2

Master OS version: SunOS 5.10
 

Client OS version:  Windows2003 5

client NBU version: 5.0
 

10/01/2012 17:00:00 - Info nbjm (pid=4796) starting backup job (jobid=821411) for client Client name, policy Policy name, schedule Differential-Inc
10/01/2012 17:00:00 - Info nbjm (pid=4796) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=821411, request id:{7DC21944-0C2C-11E2-9D43-00151714095E})
10/01/2012 17:00:00 - requesting resource tus1bkpnbupeb01-hcart-robot-tld-1
10/01/2012 17:00:00 - requesting resource <Master server>.NBU_CLIENT.MAXJOBS.Client
10/01/2012 17:00:00 - requesting resource <Master server>.NBU_POLICY.MAXJOBS.Policy name
10/01/2012 17:00:01 - granted resource  <Master server>.NBU_CLIENT.MAXJOBS.Client
10/01/2012 17:00:01 - granted resource  <Master server>.NBU_POLICY.MAXJOBS.Policy name
10/01/2012 17:00:01 - granted resource  PX0005
10/01/2012 17:00:01 - granted resource  VTL_18
10/01/2012 17:00:01 - granted resource  tus1bkpnbupeb01-hcart-robot-tld-1
10/01/2012 17:00:03 - estimated 1712361 kbytes needed
10/01/2012 17:00:03 - Info nbjm (pid=4796) started backup job for client tus1supwebpeb06, policy Policy name, schedule Differential-Inc on storage unit tus1bkpnbupeb01-hcart-robot-tld-1
10/01/2012 17:00:04 - started process bpbrm (pid=29565)
10/01/2012 17:00:06 - Info bpbrm (pid=29565) starting bptm
10/01/2012 17:00:06 - Info bpbrm (pid=29565) Started media manager using bpcd successfully
10/01/2012 17:00:07 - Info bpbrm (pid=29565) Clientis the host to backup data from
10/01/2012 17:00:07 - Info bpbrm (pid=29565) telling media manager to start backup on client
10/01/2012 17:00:07 - Info bptm (pid=29577) using 262144 data buffer size
10/01/2012 17:00:07 - Info bptm (pid=29577) using 128 data buffers
10/01/2012 17:00:07 - Info bptm (pid=29577) start backup
10/01/2012 17:00:07 - Info bptm (pid=29577) Waiting for mount of media id PX0005 (copy 1) on server <Master server>.
10/01/2012 17:00:07 - Info bpbrm (pid=29565) spawning a brm child process
10/01/2012 17:00:07 - Info bpbrm (pid=29565) child pid: 29584
10/01/2012 17:00:07 - Info bpbrm (pid=29565) sending bpsched msg: CONNECTING TO CLIENT FOR Client_1349139603
10/01/2012 17:00:07 - mounting PX0005
10/01/2012 17:00:07 - connecting
10/01/2012 17:00:14 - Info bptm (pid=29577) media id PX0005 mounted on drive index 37, drivepath /dev/rmt/39cbn, drivename VTL_18, copy 1
10/01/2012 17:00:14 - mounted PX0005; mount time: 0:00:07
10/01/2012 17:00:14 - positioning PX0005 to file 490
10/01/2012 17:00:25 - Info bptm (pid=29583) setting receive network buffer to 262144 bytes
10/01/2012 17:00:25 - Info bpbrm (pid=29565) start bpbkar on client
10/01/2012 17:00:25 - connected; connect time: 0:00:00
10/01/2012 17:00:25 - positioned PX0005; position time: 0:00:11
10/01/2012 17:00:25 - begin writing
10/01/2012 17:00:26 - Info bpbkar (pid=0) Backup started
10/01/2012 17:00:26 - Info bpbrm (pid=29565) Sending the file list to the client
10/01/2012 17:16:38 - Warning bpbrm (pid=29584) from client Client: WRN - can't open file: C:\Program Files\System Center Operations Manager 2007\Health Service State\Health Service Store\edb.log (WIN32 32: The process cannot access the file because it is being used by another process. )
10/01/2012 17:16:48 - Warning bpbrm (pid=29584) from client Client: WRN - can't open file: C:\Program Files\System Center Operations Manager 2007\Health Service State\Health Service Store\edbtmp.log (WIN32 32: The process cannot access the file because it is being used by another process. )
10/01/2012 17:16:48 - Warning bpbrm (pid=29584) from client Client: WRN - can't open file: C:\Program Files\System Center Operations Manager 2007\Health Service State\Health Service Store\HealthServiceStore.edb (WIN32 32: The process cannot access the file because it is being used by another process. )
10/01/2012 17:16:48 - Warning bpbrm (pid=29584) from client Client: WRN - can't open file: C:\Program Files\System Center Operations Manager 2007\Health Service State\Health Service Store\tmp.edb (WIN32 32: The process cannot access the file because it is being used by another process. )
10/01/2012 17:23:12 - Warning bpbrm (pid=29584) from client tus1supwebpeb06: WRN - Removable Storage Management: unable to export database (WIN32 21: The device is not ready. )
10/01/2012 17:23:12 - Error bpbrm (pid=29584) from client Client: ERR - failure reading file: C:\WINDOWS\system32\NtmsData\NTMSDATA (WIN32 33: The process cannot access the file because another process has locked a portion of the file. )
10/01/2012 17:33:17 - Critical bpbrm (pid=29584) from client Client: FTL - tar file write error (10054)
10/01/2012 17:33:18 - Info bpbrm (pid=29565) media manager for backup id Client_1349139603 exited with status 150: termination requested by administrator
10/01/2012 17:33:18 - end writing; write time: 0:32:53
10/01/2012 17:43:18 - Info nbjm (pid=4796) starting backup job (jobid=821411) for client Client, policy win_prod_supweb_all, schedule Differential-Inc
10/01/2012 17:43:19 - Info bpbrm (pid=29604) Clientis the host to backup data from
file write failed  (14)
 

Comments 11 CommentsJump to latest comment

sri vani's picture

Info bpbrm (pid=29565) media manager for backup id Client_1349139603 exited with status 150: termination requested by administrator

Stuart Green's picture

You havent stated what troubleshooting you performed.. so here is the generic error code and recommendations

 bperror -S 14 -r
file write failed
A write to a file or socket failed.
Possible causes include the following:
* An I/O error that occurred during a write to the file system.
* Write to a socket failed. Cause of this failure: a network problem or a problem with the process that reads from the socket.
* Writing to a full disk partition.
 
Do the following, as appropriate:
* Check the NetBackup Problems report for clues on where and why the problem occurred.
* For detailed troubleshooting information, create a debug log directory for the process that returned this status code. Then retry the operation and check the resulting debug log.
* Make sure that routers, bridges, and other network devices are all at "full" duplex.
See Backup Performance and NIC Cards in the Troubleshooting Guide.
* Use a "sniffer" program to determine the number of packets being rejected or re-requested.
* 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.
* On Novell systems, status code 14 has also been attributed to network issues. Try a "sniffer" program.
* The error occurs while you use the NetBackup-Java interface: The application server (bpjava processes) for the NetBackup-Java interface probably ran out of disk space in the file system containing /usr/openv/netbackup/logs/user_ops. The application server writes temporary files into directories in the /user_ops directory. Try clearing up disk space in the file system.
 
 
NTMSDATA is to do with the Removable Storage Management service. Exclude this. And also look to  stop the service.
 
(NBU 5.0 Don't let Marianne catch you!)

Tip: Get overview/document your NBU environment. Run 'nbsu' and review the output.

• If this provides help, please vote or mark appropriate solution.

sazz.'s picture

Wow!!! client NBU version: 5.0
 

10/01/2012 17:23:12 - Error bpbrm (pid=29584) from client Client: ERR - failure reading file: C:\WINDOWS\system32\NtmsData\NTMSDATA (WIN32 33: The process cannot access the file because another process has locked a portion of the file. )
 

It is stuck on this file and unable to read causing the error. Check if you have access to that file and it is accessible.

Better to upgrade the client.

bpbkar, bpbrm and bptm should be enabled if above doesn't resolve the issue.

Marianne's picture

I agree with Stuart - status 14 here is a network error:

10/01/2012 17:33:17 - Critical bpbrm (pid=29584) from client Client: FTL - tar file write error (10054)

You need to troubleshoot as per the recommendations in Stuart's post.

And YES! You need to upgrade this client. 
Any reason why you are running such and old, unsupported version?
 

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Mark_Solutions's picture

10/01/2012 17:23:12 - Error bpbrm (pid=29584) from client Client: ERR - failure reading file: C:\WINDOWS\system32\NtmsData\NTMSDATA (WIN32 33: The process cannot access the file because another process has locked a portion of the file. )
10/01/2012 17:33:17 - Critical bpbrm (pid=29584) from client Client: FTL - tar file write error (10054)
 That is 10 minutes between files it is trying to read and it then fails - this indicates that the client read timeout set on your media server is most likely 10 minutes

As well as upgrading your client you need to increase the Client Read timeouts on your Media Servers - try 1800

Hope this helps

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

V P S's picture

Hello Mark.

Its already 7200.

CLIENT_CONNECT_TIMEOUT = 300
CLIENT_READ_TIMEOUT = 7200
 

Mark_Solutions's picture

Is that on the client host properties or the media server host properties - as the client is so old it may be worth setting on both

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

V P S's picture

Hi Mark.

It is from media server bp.conf .

Mark_Solutions's picture

OK - try setting it to match on the client as well

I have to be honest the client upgrade may just fix it for you as V5 isn't going to be great on a 2003 server and it seems to be struggling with what are system state files.

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

V P S's picture

Hello Mark.

Done as per your suggestion and initiated backups.will let you know the status.

One more this what is the effect of this" communication buffer size" right now it is set to 32.

rajeshthink's picture

We can Should Not blame Netbackup for the error 14, Did we ever check the Network speed or the client end Nic card Setting.

Most of the setting i see above is done on the master. Did we check the Client NIC card setting to Auto and full duplex .

what is the speed the backup write before throwing the error 14 ?