Forum Discussion

Jay_Son's avatar
Jay_Son
Level 5
14 years ago

File read failed (13)

When backing up DB2 delta (incremental) db, intermittently, some of the child process fail with Status 13. the rest of trhe the child processes completes just fine. So, after a couple of tries, the parent job fails with a status 6. Again the jobs that fail start backing up fine but, eventually, some will fail

OS - AIX 6.0

NBU 6.5.5

I will attach the bpbkar, bpcd, bpbrm, and pbptm of the media server. I will also send the bpcd and bpbkar of the client. The job starts at 5:00pm (17:00)

Any assistance would be appreciated.

Thanks.

  • It looks like a timeout:

    17:19:29.300 [16599] <16> bpbrm readline: socket read failed: errno = 62 - Timer expired
    

    Increase CLIENT_READ_TIMEOUT on media server to at least 1800.

  • It looks like a timeout:

    17:19:29.300 [16599] <16> bpbrm readline: socket read failed: errno = 62 - Timer expired
    

    Increase CLIENT_READ_TIMEOUT on media server to at least 1800.

  • bpbrm logs

     

     EXIT STATUS = 6: the backup failed to back up the requested filessds

     

    NetBackup status code: 6
    Message: the backup failed to back up the requested files
    Explanation: Errors caused the user backup to fail.
    Recommended Action: Do the following as appropriate:
    ■ Verify that you have read access to the files. Check the status or the progress
    log on the client for messages on why the backup failed. Correct problems and
    retry the backup.
    ■ The following information applies only to Windows clients:
    Verify that the account used to start the NetBackup Client service has read
    access to the files.
    ■ The following information applies only to Macintosh clients:
    This code can be due to multiple backups being tried simultaneously on the
    same client.
    Some possible solutions are as follows:
    ■ Adjust the backup schedules.
    ■ If the client is only in one policy, set the policy attribute, Limit jobs per
    policy, to 1.
    ■ Set the NetBackup global attribute, Maximum jobs per client, to 1 (note
    that this limits all clients in all policies).
    ■ For a UNIX or Linux database extension client (for example, NetBackup for
    Oracle), this status code can indicate a problem with the script that controls
    the backup.
    Check the progress report on the client for a message such as Script exited
    with status code = number (the number varies). The progress log usually
    names the script.
    Check the script for problems. Also, check that the troubleshooting logs created
    by the database extension. See the NetBackup guide that came with the database
    extension for information on the scripts and the troubleshooting logs.
  • Once the child jobs are going through successfully, the parent job will also be successful. Status 6 will disappear.

  • Thank you Marianne. I will give 1800 seconds a try and give you an update. Yes. Once we resolve the issue with the child processes the Status 6 will disappear.