If you encounter “file read failed” errors when you run bpimmedia, you likely have a corrupt image header.
To debug this problem, you can edit your /usr/openv/netbackup/bp.conf file on your master server and add this line:
BPDBM_VERBOSE = 5
You will not need to restart services for this to take effect.
Next you can run the command:
/usr/openv/netbackup/bin/admincmd/bpimmedia -M
For example:
/usr/openv/netbackup/bin/admincmd/bpimmedia -M mynbuserver.mydomain.com
You should see the command stop when it gets to an image with corrupt headers.
When you see the “file read failed” error you can review the logs and remedy the problem.
08:41:40.659 [471] <2> db_get_image_info: /usr/openv/netbackup/db/images/myclient/1260000000/my_policy_1260854496_FULL does not contain valid image info, the file may be corrupt
You can remove the files related to this backup.
In the above example, the files associated with one of the backup images in the example above may include:
* /usr/openv/netbackup/db/images/myclient/1260000000/my_policy_1260854496_FULL
* /usr/openv/netbackup/db/images/myclient/1260000000/my_policy_1260854496_FULL.f
Great care must be taken to only remove files which start with the same name and timestamp as the bad image header file which was listed on the is empty, no data retrieved or the file may be corrupt error message in the bpdbm log file (see examples above).
Removing any other files will prevent NetBackup from restoring data from valid backup images.
Once the file(s) are removed, re-run the /usr/openv/netbackup/bin/admincmd/bpimmedia -M
If you encounter the error again, review the logs again and clean up the new files.
Repeat this process as needed.
Once the errors have been resolved the /usr/openv/netbackup/bin/admincmd/bpimmedia -M
