Forum Discussion

prats's avatar
prats
Level 4
14 years ago

Vaulting failing with file read failed -13

Hi,

Our vaulting is failing with file read failed -13 message.

The vaulting log got the following lines:

vltrun@ImageInterface::next_image^476: db_IMAGEreceive FAIL: 13 (file read failed)

Any ideas?

And if this vault run failed, will the vaulting with other profiles also get affected?

7.1.x and Earlier
Backing Up
Backup and Recovery
Managing Backup Devices
NetBackup
Reporting
Tip-How to
Troubleshooting
  • watsons's avatar
    watsons
    14 years ago

    The vault log (or session log) shall tell you the specific image that it cannot read.

    Then you can go into your image database (/usr/openv/netbackup/db/images/..) to look for it, make sure it has a corresponding header file, and the size is not 0. You can also do a bpimagelist against it to see if the detail is correct, and make sure the image file permission is readable.

    This is basically what "bpdbm -consistency" is checking. Most likely it is a corrupted image file, or missing a file header.

  • prats's avatar
    prats
    Level 4
    14 years ago

    Other vault jobs also affected - failed with the same error?

    Did anyone encounter the issue before?

    Any inputs wud be of help.

  • prats's avatar
    prats
    Level 4
    14 years ago
    I did run that command yesterday, but unfortunately our images folder is too big and the command was still running.Also we have a very small quite time window in our daily jobs, so was wondering whether running this command when there were jobs active would make any sense and that the check may run for ever... is there any way to check the consistency of a subset of the images folders say last 48 hrs or so? Coz we got the error for the first time yesterday.So if its due to an inconsistent image, the image was created only in last 48 hrs and not earlier. Thanks for the link!!
  • watsons's avatar
    watsons
    Level 6
    14 years ago

    The vault log (or session log) shall tell you the specific image that it cannot read.

    Then you can go into your image database (/usr/openv/netbackup/db/images/..) to look for it, make sure it has a corresponding header file, and the size is not 0. You can also do a bpimagelist against it to see if the detail is correct, and make sure the image file permission is readable.

    This is basically what "bpdbm -consistency" is checking. Most likely it is a corrupted image file, or missing a file header.

  • prats's avatar
    prats
    Level 4
    14 years ago

    resolved the issue .

    first ran the bpdbm -consistency, it pointed to the same image which was indicated in the vault log file.Found it was generated by a failed backup.Removed the image and vault ran successfully.

  • Iwan_Tamimi's avatar
    Iwan_Tamimi
    Level 6
    14 years ago

    I got exactly the same problem: I have logged the call to symantec and they gave the same sugestion just like you did, here for other who want to know the detail:

    /usr/openv/netbackup/bin/bpdbm -consistency 2 > /tmp/bpdbm_error.txt (it could take several hours depends on your catalog size). Find (grep) for word bad or inconsistency, it will show you a pair inconsistent image record, it need to be removed.

    Since the consistency check took very long you can get the hint for the which record got the error  from /usr/openv/netbackup/vault/sessions/Operations/sid????/detail.log it will show you the first inconsistence record it could find.