Try setting the timeout value in the client setup higher - from 30 to 60. I've seen volumes with thousands of small files timeout while Networker "crawled" the directory structure. Bumping the timeout value has ensured successful/complete backups since then. Although I don't recall ever getting the 'no output' error.

Michael Cope UNIX/Linux Systems Administrator Isis Pharmaceuticals mcope@isisph.com

UNIX is very user friendly... it's just highly selective about who it makes friends WITH!

On 9/17/2001 6:46:51 AM, "Weng-Kiam Lim" wklim@rand.com@mathworks.com wrote:

Had been experiencing on unsuccessful saveset since last week, with "no output error". It only fails on one particular volume while other volumes are fine. Any hints?

--- Unsuccessful Save Sets ---

• netapp1:/vol/vol2/pdm 1 retry attempted
• netapp1:/vol/vol2/pdm ! no output

--- Successful Save Sets ---

• netapp1:/vol/vol0/etc Warning: unsynchronized client clock detected netapp1: /vol/vol0/etc level=incr 547 KB 00:00:31 14 files netapp1: /vol/vol0/db level=incr 537 MB 00:12:17 929 files server5: /vol5/netapp1 level=9, 1.4 MB

00:00:14 4 files

Regards, wk