sts_close_handle failed on Nearstore.

[Soumyaa]

 Hi All,

I am getting a frequent error of 84 on Nearstore disk.

 Master and Media server is same and its in NBU Ver 7.1. Client NBU is 6.0MP5. Both master and Cleint is Windows 2003 Operating system.

Storage Unit is Nearstore with FIle system export and Block sharing enabled. I am very much new to VTLs and Nearstore. Please let me know if you need more info on this. Please help me. Thanks

Activity monitor Log:

17/05/2012 18:56:51 - Info nbjm(pid=7492) starting backup job (jobid=40150) for client fruinb, policy TC_nt_fs_TC_82-2_noman_fruin, schedule Weekly_Full 
17/05/2012 18:56:51 - estimated 0 Kbytes needed
17/05/2012 18:56:51 - Info nbjm(pid=7492) started backup job for client fruinb, policy TC_nt_fs_TC_82-2_noman_fruin, schedule Weekly_Full on storage unit sq02_fs_nt_tc_01_18
17/05/2012 18:56:51 - started process bpbrm (6984)
17/05/2012 18:56:55 - Info bpbrm(pid=6984) fruinb is the host to backup data from    
17/05/2012 18:56:55 - Info bpbrm(pid=6984) reading file list from client       
17/05/2012 18:56:58 - connecting
17/05/2012 18:57:06 - Info bpbrm(pid=6984) starting bpbkar32 on client        
17/05/2012 18:57:06 - Info bpbkar32(pid=0) Backup started          
17/05/2012 18:57:06 - connected; connect time: 00:00:08
17/05/2012 18:57:07 - Info bptm(pid=7072) start           
17/05/2012 18:57:07 - Info bptm(pid=7072) using 262144 data buffer size       
17/05/2012 18:57:07 - Info bptm(pid=7072) setting receive network buffer to 1049600 bytes     
17/05/2012 18:57:07 - Info bptm(pid=7072) using 30 data buffers        
17/05/2012 18:57:07 - Info bptm(pid=7072) start backup          
17/05/2012 18:57:09 - Info bptm(pid=7072) backup child process is pid 3176.6304      
17/05/2012 18:57:09 - Info bptm(pid=3176) start           
17/05/2012 18:57:09 - begin writing
17/05/2012 19:00:37 - Critical bptm(pid=7072) image write failed: error 2060022: software error     
17/05/2012 19:00:49 - Critical bptm(pid=7072) sts_close_handle failed: 2060022 software error       
17/05/2012 19:00:53 - Error bptm(pid=7072) cannot write image to disk, Invalid argument     
17/05/2012 19:00:53 - Info bptm(pid=7072) EXITING with status 84 <----------       
17/05/2012 19:00:59 - end writing; write time: 00:03:50
17/05/2012 19:01:04 - Info bpbkar32(pid=0) done. status: 84: media write error      
media write error(84) 

[Mark_Solutions]

Check your All Log Entries report to see if the unit keeps going up and down

Quite often adding the following configuration file to your media servers can resolve this:

/usr/openv/netbackup/db/config/DPS_PROXYDEFAULTRECVTMO (or equivalent path on Windows)

Once created open it and add a value of 800 inside it.

Re-Start NetBackup to take effect.

Alternatively it can be Keep Alive Settings which need registry kets adding:

HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\

 DWORD - KeepAliveTime – Decimal value of 510000

DWORD – KeepAliveInterval – Decimal Value of 3

Reboot to take effect

Hoipe this helps

[Marianne]

Please share more info about HOW the NearStore is configured at OS level as well as NBU level?

The only reference to NearStore that I can find in the Hardware Compatibility Guide is for NearStore Virtual Tape Library - Fibre Channel .

Seems yours is configured as some sort of Disk Storage and not as VTL?

[Soumyaa]

Hi,

I tried doing above said methods and nothing turned up good. Still I am with 84. To add on I had 3 drives in the client and I am getting this 84 error only for Shadow copy components.