Sorry for the delay ... we just got to a maintenance window where we
could install the fix ... and it did NOT resolve our problem. I will
report any progress we make, as one of our lead networking people is
still working on the problem.
cheers, wayne
Wayne T Smith wrote, in part, on 8/30/2005 5:30 PM:
> A few weeks ago I reported inability to restore a file (times out),
> except to the backup server itself.
>
> After a few weeks and getting several people involved, we've discovered
> the cause: our router has a sensitivity to a certain sequence of
> characters of data ... and this file had that sequence! There is a
> fix available to the router and it should be applied next week.
>
> Thanks to all who offered suggestions!
>
> cheers, wayne
>
> Wayne T Smith wrote, in part, on 8/2/2005 4:14 PM:
>
>> My Solaris NetBackup server is v5.1MP3 and I have a problem with some
>> Linux restores. On a few machines a full restore results in some
>> (many!) files not being restored. Some files are restored; others
>> aren't. If I pick one of the "problem" files and restore just it, I
>> get a status code 5, with a "Socket write failed" error, 9-11 minutes
>> into the restore. An example Admin Console log is listed below.
>> Failures are always 9-11 minutes into the restore, with the below
>> example almost exactly 10 minutes.
>>
>> A restore to another Linux machine (version & MP do not seem to
>> matter) results in the same error. However, a restore to my backup
>> server succeeds! For what it is worth, the data was backed up with
>> NetBackup v4.5MP5.
>>
>> I could use suggestions for how to debug this problem (socket write
>> failed is not very informative) and any suggestions on settings to
>> tweak, should that be the problem.
>>
>> (My master/media server has the following timeouts reported: Client
>> connect timeout: 900 seconds, Client read timeout: 1800 seconds,
>> Media server connect timeout: 60 seconds, Use OS dependent timeouts
>> is checked. On the client, the Client read timeout is 300 seconds).
>>
>> Thanks and cheers, wayne
>>
>>
>> ash:~$ less
>> /usr/openv/netbackup/logs/user_ops/wsmith/logs/jbpUJAmua4gi.log
>> Restore started 08/02/2005 14:45:49
>>
>> 14:45:57 (248339.xxx) Restore job id 248339 will require 1 image.
>> 14:45:57 (248339.xxx) Media id NB0361 is needed for the restore.
>> 14:45:57 (248339.xxx) Media id NB0263 is needed for the restore.
>> 14:45:57 (248339.xxx) Media id NB0145 is needed for the restore.
>>
>> 14:46:02 (248339.001) Restoring from image created Sat 30 Jul 2005
>> 12:19:57 AM EDT
>> 14:46:10 (248339.001) INF - Waiting for mount of media id NB0263 on
>> server ash for reading.
>> 14:53:56 (248339.001) INF - Waiting for positioning of media id
>> NB0263 on server ash for reading.
>> 14:54:31 (248339.001) INF - Beginning restore from server ash to
>> client cedar.unet.maine.edu.
>> 15:04:37 (248339.001) The following files/folders were not restored:
>> 15:04:38 (248339.001) UTF -
>> /usr/local/blackboard/content/vi/bb_bb60/courses/1/00230_K_042/groups/_9839_1/_276333_1/Presenta
>>
>>
>> tion.ppt
>> 15:04:39 (248339.001) Status of restore from image created Sat 30 Jul
>> 2005 12:19:57 AM EDT = socket write failed
>>
>> 15:04:40 (248339.xxx) INF - Status = the restore failed to recover
>> the requested files.
>> _______________________________________________
>> Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
>> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
>
>
> _______________________________________________
> Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|