I'm seeing Retrieves fail on certain older files. The error is ANS1301E Server detected system error. These are files from 2003 or earlier on NetWare file servers and they have odd archive date attri
Author: Andrew Raibeck <storman AT US.IBM DOT COM>
Date: Tue, 8 Mar 2005 06:26:35 -0700
I'm not convinced the archive attribute is the problem. If you look up the ANS1301E message, you will see it is apprising you of a problem on your TSM server, which is almost certainly not related to
Thank you Andy for the reply. Here's the server's activity log during an archive and retrieve with a failure: 03/08/2005 10:16:11 ANR0402I Session 27276 started for administrator AFERRIS (WebConsole)
Author: Andrew Raibeck <storman AT US.IBM DOT COM>
Date: Tue, 8 Mar 2005 16:19:20 -0700
Hmmm..... it seems odd to me that you'd get ANS1301E without a corresponding message on the server. That message should derive from a transaction that the server aborted, and I'd think the server wou
Thanks Andy. I'll talk to support but I'm still curious about if TSM looks at the archive attribute at all. Andrew Ferris Network Support Analyst iCAPTURE Research Centre University of British Columb
Thanks Andy. I'll talk to support but I'm still curious about if TSM looks at the archive attribute at all. TSM has historically not used the Archive Attribute in Windows to evaluate the backup cand
Thank you Richard. I'm sorry if it wasn't clear before but this is a slightly odd scenario where data on NetWare clustered volumes will not get retrieved correctly after an archive. The files that fa
Author: Andrew Raibeck <storman AT US.IBM DOT COM>
Date: Thu, 10 Mar 2005 11:09:46 -0700
Yes.... the client doesn't actively use any archive bit info for TSM archive or retrieve functionality (other than the data is stored on the TSM server and put back during retrieve). I'd need to see