cancel
Showing results for 
Search instead for 
Did you mean: 

Status 87 (media close error 2060014)

JNO_123
Level 4

hi,

Backups failing with status 87, randomly it seams.
Both Windows & Linux clients are affected.

our environmnet:

Master & Media WIN2K8R2, NBU7601
Disk-Storage Dell DR4000 OST. 3.0.0.113.1
 

The failing clients are within the same network as the media servers, and the occur on multiple media-servers, ost storage.

 

below is an excerpt from activity monitor info for one failing client:

4/16/2014 10:29:57 PM - Info bptm(pid=7268) start backup          
4/16/2014 10:29:57 PM - Info bptm(pid=7268) backup child process is pid 10120.10472      
4/16/2014 10:29:57 PM - Info bptm(pid=10120) start           
4/16/2014 10:29:57 PM - begin writing
4/16/2014 11:32:20 PM - Info bpbrm(pid=4572) from client linuxclient.fqdn.net: TRV - /var/lib/nfs/rpc_pipefs is in a different file system from /var. Skipping.
4/16/2014 11:32:39 PM - Info bptm(pid=7268) waited for full buffer 126 times, delayed 241115 times   
4/16/2014 11:57:16 PM - Critical bptm(pid=7268) sts_close_handle failed: 2060014 operation aborted       
4/16/2014 11:57:16 PM - Error bptm(pid=7268) cannot write image to disk, media close failed with status 2060014 
4/16/2014 11:57:19 PM - Info bptm(pid=7268) EXITING with status 87 <----------       
4/16/2014 11:57:23 PM - Info bpbkar32(pid=0) done. status: 87: media close error      
4/16/2014 11:57:23 PM - end writing; write time: 1:27:26
media close error(87)

Any suggestions, and what logs would be appropriate to enable?

Regards
Jonas

1 ACCEPTED SOLUTION

Accepted Solutions

JNO_123
Level 4

We have been running 3.0.0.154.2 since late april without any issues.

Note that, we also saw bad backup performance on 3.0.0.113.1, which also was solved with the new code.

 


Br
Jonas

 

 

View solution in original post

5 REPLIES 5

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Errors like this is normally on the OST storage device. Seems it is not sending confirmation back that image is successfully written.

Check logs on the Dell or log a call with your vendor.

SymTerry
Level 6
Employee Accredited

I'm also with Marianne on this.

You could look though logging for this in bptm and also OID logging. (OID 222, 220, 230, 202 are contained within the NBRMMS log when you increase logging)

But in the end, you would need to contact Dell as bptm is waiting and eventually bails.

JNO_123
Level 4

Hi,

Information update:

I have a case with Dell, and it looks like there is a known problem with the 3.0.0.113.1 code.

But the problems should be fixed in release: 3.0.0.154.2
The new code has not been released officially yet.

I have installed it on one system today, I'll report back with result.

Br
Jonas

PatrinisJ
Not applicable
Partner Accredited

Hi,

I have the same issue here.

I made DR4100 Update from version 2.1.0851.2 to 3.0.0113.1, I performed the update to use the optimized synthetic backup, start of supported on DR4x00 version 3.0.0113.1.

After update some JOBS fails randomly with status 84 and 87.

Dell was released the version 3.0.0.154.2.

http://www.dell.com/support/drivers/us/en/04/DriverDetails/Product/powervault-dr4100?driverId=WM9N2&osCode=LHS64&fileId=3366698130&languageCode=en&categoryId=DM

I'm updating the environment now with this firmware.

JNO_123
Level 4

We have been running 3.0.0.154.2 since late april without any issues.

Note that, we also saw bad backup performance on 3.0.0.113.1, which also was solved with the new code.

 


Br
Jonas