Forum Discussion

kybeer's avatar
kybeer
Level 5
11 years ago

error 87: media close error / accelerator / full backup

Hi On one specifc Accelerator-enabled (Standard) Policy I get: Critical bptm(pid=11100) sts_close_handle failed: 2060017 system call failed        Error bptm(pid=11100) cannot write image to...
7.5
Backing Up
Backup and Recovery
Error messages
NetBackup
Troubleshooting
Windows Server (2003-2008)
  • Marianne's avatar
    Marianne
    11 years ago

    Probably best to log a Support call.

    Symantec Support will probably need level 5 bptm and bpdm logs as well as other MSDP logs.

    I found references to corrupt images that were related to disk full condition on the MSDP volume. I do not see any reference here.
    Other TNs described bugs in older NBU and PureDisk versions.

    Otherwise, expire the problematic backup image and take another full backup.

    PS:
    Was the problematic image duplicated to tape or other storage?
    Was the duplication successful?
    Have a look at output of:
    bpimagelist -backupid 11111111111111111111_1400389801 -L

kybeer's avatar
kybeer
Level 5
11 years ago

Hi,

Yes, the master and media server is the same machine.

Yes, I have three log files in log\bptm. 051814_00001.log should be for the correct date. I'm cheking for the matching time, and image-file (1400389801). One suspicious entry I find is (I have replaced the hostnames with 11111...):

 

07:13:29.415 [3384.9808] <16> 67413:bptm:3384:11111111111111111111: [ERROR] PDVFS: pdvfs_fcache_flushfile: file 11111111111111111111_1400389801_C1_F1.img now marked CORRUPT

Please see bptm.log

 

Maybe I need to do a new complete full backup of this policy?

 

The only tuning is the recommended setup steps from Symantec when installing MSDP.

The worker thread is 64 atm

Please see details.log for Job log.