Richard, Ian, I'd thought the same thoughts as you. But when I started to prepare to do a rename filespace, I deleted 28 of the 35 filespaces on the machine, which also cleared about 2Tb of storage, process that days to complete as there were millions of objects involved. The day after I deleted a bunch, 3 new filespaces appeared, and the error messages reference the new filespaces instead of one of the reused filespaces from the original machine. The more I think,or worry, about it, I think there may be some confusion in the mapping of the volumes on what seems to be some sort of file share. If that is true, wouldn't the same 34k + errors reappear on the rename client?
At 04:42 PM 1/19/2007 +0000, you wrote:
Fred, My experience has shown this type of error frequently relates to the fact that the Mac TSM client is unicode-enabled (as of v5.2) and is trying to parse the filelist of a non-unicode enabled filespace - i.e. a filespace backed up previously using an earlier, non-unicode enabled TSM Mac client. Richard's notes suggest the same. To prevent this in the future, look at the AUTOFSrename options on both the Client and Server. To get out of this instance, rename the filespace or node out the way and backup afresh. Ian Smith Oxford University Computing Services England On Thursday 18 Jan 2007 9:01 pm, fred johanson wrote: > ANS1228E
Fred Johanson ITSM Administrator University of Chicago 773-702-8464
