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 the SERVICE trace in order to get a better handle on where
that ANS1301E is coming from.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 2005-03-10
11:01:55:

> 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 fail all seem
> to have an odd archive attribute (not due to TSM). I was just interested
> in some background info on archives as the NetWare client manual is
> terser than the Windows client.
>
> Andrew Ferris
> Network Support Analyst
> iCAPTURE Research Centre
> University of British Columbia
>
> >>> rbs AT BU DOT EDU 3/10/2005 4:57:27 AM >>>
> On Mar 9, 2005, at 9:05 PM, Andrew Ferris wrote:
>
> > 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 candidacy of a file. See the client manual doc of
> the Resetarchiveattribute option.
>
>     Richard Sims