Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

System Call Failed (11) Error reading File

Status
Not open for further replies.
joenok

joenok

MIS
Feb 27, 2002
49
US
This is happening on my file server - Windows 2003, it hangs on a few files and ends up killing my job before its over, is it not sophisticated enough to just go on when it gets to a file with a problem? - I have the user go in and remove the file but it just finds another one eventually. Is it a timeout settings issue?

I know its a very generic system error.

thanks!

here's the detailed status log entry

8/11/2004 4:07:46 AM - connected; connect time: 00:00:01
8/11/2004 6:36:14 AM - Error bpbrm(pid=1420) from client jpmc-home: ERR - OTM Error:0xe0001005 (WIN32 -536866811: Unknown error)
8/11/2004 6:36:24 AM - Error bpbrm(pid=1420) from client jpmc-home: ERR - OTM Error while reading file: F:\users\KParker\Personal\JCAHO\PP Worksheet RI Hospice.doc
8/11/2004 6:36:24 AM - Critical bpbrm(pid=1420) from client jpmc-home: FTL - Backup operation aborted!
8/11/2004 6:36:25 AM - end writing; write time: 02:28:40
 
Sort by date Sort by votes
This is one of those horrid errors which are difficalt to pin down. In most cases it is not the files that are the problem which is why you remove what you think is a bad file only for the system to find another one. Look at your system resorces, you may be low on memory or space at a critical moment.
 
Upvote 0 Downvote
joenok,

I have encountered this issue several times and have used the following Veritas tech note to resolve the problem:


I don't remember the exact key that you need to change, but go into the registry on the file server you are having a problem with and look for a max cache size key (under HKLM/Software/Veritas/Netbackup/...) and change the value to 0. After you make the change, just restart the service and you should be all set.

Hope that helps.

John
 
Upvote 0 Downvote
thanks for all the replys, I have fixed the problem, i had 2 partitions on my netbackup server, when I loaded netbackup I just loaded it to the smaller partition, I then went back and used <altpath> to move the catalogs to the bigger partition. I had to free up space on c: and reran the backups and its working great!
 
Upvote 0 Downvote
Another fix is going ot th ecline tproperties and setting OTM to "retry OTM" this works for my 11s when OTM is specified
 
Upvote 0 Downvote
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top