Hi folks, current vaules for commtimeout and idletimout are 1200 and 180. i don't think that increasing these vaules solve my problem. maybe it will stop writing in logs that kind of errors but please remember that i cannot backup up my whole database (ms sql) environment. log for that operation (for scheduled operations only) looks like that :
Beginning full backup for database model, 13 of 21. Full: 0 Read: 867840 Written: 867840 Rate: 617.71 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 357.81 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 251.70 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 194.13 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 157.99 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 133.20 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 115.13 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 101.38 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 90.56 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 81.83 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 74.63 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 68.60 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 63.47 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 59.05 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 55.21 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 51.84 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 48.86 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 46.20 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 43.81 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 41.66 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 39.71 Kb/Sec Full: 0 Read: 869104 Written: 869104 Rate: 37.94 Kb/Sec ....... Full: 0 Read: 869104 Written: 869104 Rate: 0.74 Kb/Sec so as u can see, the transfer is going lower and lower so the backup operation couldn't finish proper. all the time it stops on database model (msdb). manualy i can backup it without any problems. what's wrong? have u seen similar problem? p.s. oh i almoust forget - i'm using storageagent in version 5.1.7.0. this database server is connected to the san. -----Wiadomość oryginalna----- Od: alkina [mailto:[EMAIL PROTECTED] Wysłano: 29 paYdziernika 2003 10:44 Do: [EMAIL PROTECTED] Temat: Re: TDP for MSSQL - huge problem In dsmserv.opt increase the value of two parameters 1. commtimeout 3000 2. idletimeout some suitable value. Regards Alkina L "ADSM: Dist Stor Manager" wrote: >4 more than one week I've been receiving the error code listed below during >my night backup process on MS SQL 7 (NT 4.0): > >28-10-2003 07:58:40 ANS1512E Scheduled event 'MARTINI_SQLFULL' failed. >Return code = -1073741510. >28-10-2003 07:58:41 ANS1005E TCP/IP read error on socket = 1320, errno = >10054, reason : 'Unknown error'. >28-10-2003 07:58:45 ANS1005E TCP/IP read error on socket = 656, errno = >10054, reason : 'Unknown error'. > >The scheduled backup completes just few databases but always stop on msdb. >The problem doesn't occur when I start up backup manualy. >Yesterday I upgraded the TDP client to the latest 5.2.1 version. It didn't >solve this problem. >What can I do next? Have u evere had similar problem? >Waitin' for some suggestion from ya wizards:-) Sebastian - The 10054 TCP/IP errno reflects a connection being reset by peer, which in TSM terms means that the server terminated the session with the client. Thus, the place to look is in the server Activity Log, which should explain why it did so. It may be that server timeout values are too low. Richard Sims, BU Get Your Private, Free E-mail from Indiatimes at http://email.indiatimes.com Buy The Best In BOOKS at http://www.bestsellers.indiatimes.com Bid for Air Tickets on Air Sahara Flights. For Best Deals, log on to http://airsahara.indiatimes.com and Bid Now !
