A file system backup (Standard or Windows policy) fails with Exit Status 13
The bpbrm debug log and Job Details show the following error:
15:24:07.908  <2> bpbrm mm_sig: received ready signal from media manager
15:29:07.908  <16> bpbrm readline: socket read failed: errno = 62 - Timer expired
15:29:30.716  <2> bpbrm Exit: client backup EXIT STATUS 13: file read failed
The NetBackup Backup and Restore Manager (bpbrm) has not received any progress updates from the client host in recent minutes. In the example above, after exactly 5 minutes. Which is the default CLIENT_READ_TIMEOUT as configured under the host properties of the media server;
host properties > media servers > mymediaserver > Timeouts > Client Read Timeout
(default: 300 seconds)
Some clients may experience this problem when backing up very large file systems, very active file systems, or file systems with many small seldom-changing files. In those cases, the client may spend more time finding/reading files to backup than it does actually transferring the files to storage. In those cases, it may be useful to increase the Client Read Timeout on the media server. Start by doubling it from 300 to 600, and so on until the backup is successful.
Note: This same symptom can occur if the backup transfer is actually hanging or if the network is congested. See the related articles.
Client nfs4:NetBackup-RedHat2.6 7.0