Option Set it's forced to YES
All those nodes are using a server cloptset with the following entry: CHANGINGRETRIES 0 Yes 0 -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of Guido Martínez Sent: terça-feira, 21 de Setembro de 2010 11:56 To: [email protected] Subject: Re: [ADSM-L] Several TSM Clients with files that retries has exceed the maximum number of retries Update the Option Set. Instead of Force=NO use Force=YES. Regards. El sep 21, 2010 7:50 a.m., "Botelho, Tiago (External)" < [email protected]> escribió: Hello, I have several TSM clients reporting error "ANS8010E An attempt to backup or archive a file has exceed the maximum number of retries." All those nodes are using Management Classes / copy groups with the bellow configuration: Policy Domain Name: WIN_SERVERS Policy Set Name: STANDARD Mgmt Class Name: WIN_SRV_DATA Copy Group Name: STANDARD Copy Group Type: Backup Versions Data Exists: 5 Versions Data Deleted: 2 Retain Extra Versions: 30 Retain Only Version: No Limit Copy Mode: Modified Copy Serialization: Dynamic Copy Frequency: 0 Copy Destination: WIN_SRV_D Table of Contents (TOC) Destination: Last Update by (administrator): TMB Last Update Date/Time: 08/31/10 09:19:55 Managing profile: Changes Pending: No All those nodes are using a server cloptset with the following entry: CHANGINGRETRIES 0 Yes 0 Examples: 09/21/2010 01:09:25 ANS1228E Sending of object '\\ptvwaepas00068\c$\QuirlNT10\logfiles\import.log' failed 09/21/2010 01:09:25 ANS8010E An attempt to backup or archive a file has exceed the maximum number of retries. Some dsm.opt files have the parameter: changingretries 0 Any ideas with the clients are send the "ANS8010E" messages ? Thank you
