Video Screencast Help

client backups Status 87 & 83, with 5020 appliance

Created: 05 Mar 2013 | 4 comments

Hi,

I have been encountering some issues with backups within a netbackup 7.5.0.4 environment. The topology is 

1 x Master server 7.5.0.4 - RHEL 6.3 (virtualised)
2 x Symantec 5220 2.5.1 appliances (media servers)
2 x Symantec 5020 1.4.3.1 appliances (single storage pool)

 

The issues encountered (failed backups with status 87, 83) are not always isolated to the same clients; the client log below shows the errors.

<FQDN-CLIENT> is windows 2008 R2
 

 

03-Mar-2013 22:02:31 - Info nbjm (pid=17817) starting backup job (jobid=17249) for client <FQDN-CLIENT> policy <POLICY>, schedule Differential-Inc
03-Mar-2013 22:02:31 - estimated 18694576 kbytes needed
03-Mar-2013 22:02:31 - Info nbjm (pid=17817) started backup (backupid=<FQDN-CLIENT>_1362348151) job for client <FQDN-CLIENT>, policy <POLICY>, schedule Differential-Inc on storage unit <PDDO-STORAGE-POOL>
03-Mar-2013 22:02:32 - started process bpbrm (pid=28362)
03-Mar-2013 22:02:35 - Info bpbrm (pid=28362) <FQDN-CLIENT> is the host to backup data from
03-Mar-2013 22:02:35 - Info bpbrm (pid=28362) reading file list from client
03-Mar-2013 22:02:38 - Info bpbrm (pid=28362) accelerator enabled
03-Mar-2013 22:02:43 - connecting
03-Mar-2013 22:02:44 - Info bpbrm (pid=28362) starting bpbkar on client
03-Mar-2013 22:02:44 - connected; connect time: 0:00:00
03-Mar-2013 22:02:50 - Info bpbkar (pid=4468) Backup started
03-Mar-2013 22:02:50 - Info bpbrm (pid=28362) bptm pid: 28369
03-Mar-2013 22:02:51 - Info bptm (pid=28369) start
03-Mar-2013 22:02:51 - Info bptm (pid=28369) using 262144 data buffer size
03-Mar-2013 22:02:51 - Info bptm (pid=28369) using 256 data buffers
03-Mar-2013 22:02:51 - Info <FQDN-5220> (pid=28369) Using OpenStorage client direct to backup from client <FQDN-CLIENT> to <FQDN-5020>
03-Mar-2013 22:02:54 - begin writing
03-Mar-2013 22:02:55 - Info bpbkar (pid=4468) change journal NOT enabled for <N:\>
03-Mar-2013 22:03:38 - Info bpbkar (pid=4468) 876 entries sent to bpdbm
04-Mar-2013 00:10:26 - Info bpbkar (pid=4468) 119586 entries sent to bpdbm
04-Mar-2013 00:10:53 - Info bpbkar (pid=4468) 119837 entries sent to bpdbm
loads of bpbkar messages, all info.
04-Mar-2013 00:11:10 - Info bpbkar (pid=4468) 119917 entries sent to bpdbm
04-Mar-2013 00:11:43 - Info bpbkar (pid=4468) 120237 entries sent to bpdbm
04-Mar-2013 00:12:26 - Info bpbkar (pid=4468) 120594 entries sent to bpdbm
04-Mar-2013 00:12:34 - Info bpbkar (pid=4468) accelerator sent 2112291328 bytes out of 4642415616 bytes to server, optimization 54.5%
04-Mar-2013 00:12:35 - Info bpbkar (pid=4468) bpbkar waited 1569 times for empty buffer, delayed 6161 times.
04-Mar-2013 00:12:35 - Critical bptm (pid=28369) sts_close_handle failed: 2060019 error occurred on network socket
04-Mar-2013 00:12:35 - Critical bptm (pid=28369) cannot write image to disk, media close failed with status 2060019 
04-Mar-2013 00:12:35 - Info <FQDN-5220> (pid=28369) StorageServer=PureDisk:<FQDN-5020>; Report=PDDO Stats for (<FQDN-5020>): scanned: 4533610 KB, CR sent: 0 KB, CR sent over FC: 0 KB, dedup: 100.0%, cache hits: 0 (0.0%)
04-Mar-2013 00:12:35 - Critical bptm (pid=28369) sts_close_server failed: error 2060005 object is busy, cannot be closed
04-Mar-2013 00:12:39 - Info bptm (pid=28369) EXITING with status 87 <----------
04-Mar-2013 00:12:43 - Info bpbkar (pid=4468) done. status: 87: media close error
04-Mar-2013 00:12:43 - end writing; write time: 2:09:49
media close error  (87)
 
Has anyone encountered this before?
 
Thanks
David
Operating Systems:

Comments 4 CommentsJump to latest comment

Marianne's picture

Seems nobody has encountered this before...

Probably best to log a support call?

 

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

Mark_Solutions's picture

When you do client side de-dupe the client needs to properly resolve the appliances and each node of a 5020 SPA

Make sure your clients can resolve the appliances and the appliances can resolve the clients as they communicate directly with each other when doing client side de-dupe

Use hosts files if needs be

Also check on the client under its ost-plugins directory in case it has gathered false media server name due to incoreectly resolving an appliance

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!!.

S Williamson's picture

I am also getting this error

9/06/2013 9:19:53 AM - Critical bptm(pid=8352) sts_close_handle failed: 2060019 error occurred on network socket     
9/06/2013 9:19:53 AM - Critical bptm(pid=8352) cannot write image to disk, media close failed with status 2060019

Did you get this resolved? Im using Windows 2008R2 7.5.0.5 Master/media and a Windows 2008R2 7.5.0.5 Client. This is its first backup and server is about 1.5TB backed up via Lan.

Simon

Brook Humphrey's picture

Also along with what Mark suggested. 

You don't mention if you are doing client side dedupe or weather these are writing to the 5220 or the 5020.

With the 5220 there are known performance issues at 2.5.1 that is resolved in 2.5.2 that may be causing this issue. This would mean you would need to patch your master to 7.5.0.5 also.

http://www.symantec.com/docs/TECH145136

this technote lists a few patches you will want to apply once you install 2.5.2.

http://www.symantec.com/docs/TECH178334

as well as the 7.5.0.5 late breaking news page for downloads and patches.

I would suspect though with those errors that you are hitting the performance issue with 2.5.1.

If you have any further questions please ask

Thanks

Brook Humphrey
Managed Backup Service

Principal Backup Administration Specialist