Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*fioScanDirEntry\s+error\s+messages\s+while\s+backing\s+up\s+a\s+windows\s+file\s+server\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*fioScanDirEntry\s+error\s+messages\s+while\s+backing\s+up\s+a\s+windows\s+file\s+server\s*$/: 3 ]

Total 3 documents matching your query.

1. fioScanDirEntry error messages while backing up a windows file server (score: 1): Author: James Choate <jchoate AT SOURCE1INC DOT COM>; Date: Mon, 24 Apr 2006 07:55:29 -0600; Any one seen this before? We just started backing up a new windows file server. The windows client is 5.3.0 Our TSM server is AIX 5.3 ML03 TSM server 5.3.1 We're getting the following error in the ds; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2006-04/msg00459.html (14,289 bytes)
2. Re: fioScanDirEntry error messages while backing up a windows file server (score: 1): Author: "Prather, Wanda" <Wanda.Prather AT JHUAPL DOT EDU>; Date: Mon, 24 Apr 2006 11:12:24 -0400; 1) DON"T use windows client 5.3.0. Get a 5.3.2 or 5.3.3 client. 2) In my experience, when TSM says the Windows directory is corrupted, it really is. If upgrading the client doesn't change anything, r; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2006-04/msg00461.html (15,045 bytes)
3. Re: fioScanDirEntry error messages while backing up a windows file server (score: 1): Author: James Choate <jchoate AT SOURCE1INC DOT COM>; Date: Tue, 25 Apr 2006 08:11:56 -0600; Thanks for your input. Just an FYI: The file systems mentioned in the log as corrupt, are corrupt. Should have trusted TSM in the first place. --Original Message-- From: ADSM: Dist Stor Manager [mail; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2006-04/msg00481.html (15,435 bytes)

Current List: 1 - 3
Page: [1]