In NetBackup, when running "bpdbm -consistency -move," valid NDMP images may be found to be "corrupt" and moved when they should not be moved.

Article:TECH204140  |  Created: 2013-03-21  |  Updated: 2013-10-29  |  Article URL
Article Type
Technical Solution


One cause of status code 13 failures (file read failed) reported when running certain commands such as bpimmedia or bpimagelist is the presence of one or more corrupt images in the images database.  Troubleshooting the status 13 is frequently performed by running a consistency check -  bpdbm -consistency - sometimes with the -move option.

It has been determined that running bpdbm -consistency -move can lead to valid images incorrectly being moved to the db.corrupt directory. 

This issue only affects NDMP images on NetBackup


Valid images that are incorrectly detected and moved are preceded in the bpdbm consistency check output with a message stating:
found 2 bad record entries

The status 13 seen when running either bpimagelist and bpimmedia results from legitimately identified corrupt images, such as "bad image headers," and not because of the incorrectly detected bad images.  In the bpdbm consistency output, such images are identified with lines beginning with:
Bad image header:

There may also be messages including a status code 229:
events out of sequence - image inconsistency (229)


This issue affects only NDMP images on all operating systems on NetBackup  No other NetBackup version is affected by this issue.  Other image types are not affected by this issue.


The recommendation for troubleshooting status 13 issues with bpimagelist and bpimmedia in environments is to run bpdbm -consistency without the -move switch, collect the output file for inspection, and then manually move/remove only the corrupt images - that is, NDMP images identified by a Bad image header: message.  (If every NDMP image in the output is identified by a Bad image header: message, the bpdbm -consistency -move command may be safely run - however, if any NDMP images are identified by a bad record entries message, this command should not be run.)

Workaround to restore incorrectly moved images
For images erroneously relocated under db.corrupt, either of the following procedures may be used to work around this issue:

1. NetBackup may be used to back up incorrectly moved images in db.corrupt as well as to perform an alternate location restore back to the image's original location.

2. tar may be used to create tarballs of individual client directories under db.corrupt/images, which may then be extracted back to the same client directory under db/images.

Supplemental Materials


In NB, running bpdbm -consistency thinks NDMP images are bad. If used with -move, will move NDMP images to db.corrupt.

SourceError Code

file read failed

SourceError Code

events out of sequence - image inconsistency

Article URL

Terms of use for this information are found in Legal Notices