Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*TSM\s+client\s+3\.7\.2\.14\s+backup\s+failure\s+due\s+to\s+non\-existant\s+NFS\s+mount\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*TSM\s+client\s+3\.7\.2\.14\s+backup\s+failure\s+due\s+to\s+non\-existant\s+NFS\s+mount\s*$/: 3 ]

Total 3 documents matching your query.

1. TSM client 3.7.2.14 backup failure due to non-existant NFS mount (score: 1): Author: Lisa Cabanas <CABANL AT MAIL.MODOT.STATE.MO DOT US>; Date: Wed, 12 Jul 2000 12:45:35 -0500; I thought I'd give a heads up on this. I've got an open PMR on this, and I am waiting to hear what Tivoli/IBM has to say. AIX 4.3.3.02 TSM server 3.7.3.1 TSM client 3.7.2.14 (applied fixtest level si; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2000-07/msg00362.html (13,480 bytes)
2. Re: TSM client 3.7.2.14 backup failure due to non-existant NFS mount (score: 1): Author: Richard Sims <rbs AT BU DOT EDU>; Date: Wed, 12 Jul 2000 14:36:25 -0400; fioGetDirEntries appears to be a function private to ADSM client software. The dsmerror log entry is reflecting the return code from the function, unrelated to operating system errno. As to event su; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2000-07/msg00365.html (11,099 bytes)
3. Re: TSM client 3.7.2.14 backup failure due to non-existant NFS mount (score: 1): Author: Steven Bridge <ccaasub AT UCL.AC DOT UK>; Date: Wed, 12 Jul 2000 19:43:10 +0100; I've certainly seen this error but largely from some of our Solaris clients - as it's these that lose their respective NFS servers more often. It does seem rather drastic that all backups from the c; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2000-07/msg00366.html (11,798 bytes)

Current List: 1 - 3
Page: [1]