Re: [Veritas-bu] Very slow client
any client set to auto detect is only very slow if there is a misconfiguration in the chain. auto neg has worked flawlessly for years assuming both sides are configured to auto. The documented (IEEE 802.3??) behaviour if one side is auto and the other side hardcoded is for the auto neg configured side to go to 100Mb/s Half Duplex. (lowest common denominator.) Since the hardcoded side is usually set to FULL, you end up with a duplex mismatch which kills performance. If you've still got old Sun HME cards ardoun, there is some auto-meg issues with those, in combination with some older Cisco versions, but for the most part, Auto is where it's at. Auto is actually a requirement for proper flow control in GigE. Paul -- -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kennedy, Cameron Sent: August 15, 2007 7:49 PM To: Deiter, Scott; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Very slow client did you check network settings on the NIC? Is it set to 100/Full (or whatever your network standard is)? I find any Windows clients set to auto detect run very slow. La version française suit le texte anglais. This email may contain privileged and/or confidential information, and the Bank of Canada does not waive any related rights. Any distribution, use, or copying of this email or the information it contains by other than the intended recipient is unauthorized. If you received this email in error please delete it immediately from your system and notify the sender promptly by email that you have done so. Le présent courriel peut contenir de l'information privilégiée ou confidentielle. La Banque du Canada ne renonce pas aux droits qui s'y rapportent. Toute diffusion, utilisation ou copie de ce courriel ou des renseignements qu'il contient par une personne autre que le ou les destinataires désignés est interdite. Si vous recevez ce courriel par erreur, veuillez le supprimer immédiatement et envoyer sans délai à l'expéditeur un message électronique pour l'aviser que vous avez éliminé de votre ordinateur toute copie du courriel reçu. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Very slow client
Hi All, This debate will continue to go on forever. I have found that hard coding works extremely well when set. In many cases setting to auto and auto still gave issues. As far as 1GB copper is concerned, the IEEE standard should be followed to the nth degree. Use a minimum of CAT 5E or definitely CAT6 cable and don't go beyond 90 metres. Going outside of these specifications will cause you issue, a very expensive experience as on of my clients found? They had to switch all NICS and switch ports to 100 full duplex for DataProtector and NetBackup as their network was designed to CAT5. Rather change to 1GB fibre which will always work. Kind Regards, Clem Kruger From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Keating Sent: 17 August 2007 15:30 PM To: Kennedy, Cameron; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Very slow client any client set to auto detect is only very slow if there is a misconfiguration in the chain. auto neg has worked flawlessly for years assuming both sides are configured to auto. The documented (IEEE 802.3??) behaviour if one side is auto and the other side hardcoded is for the auto neg configured side to go to 100Mb/s Half Duplex. (lowest common denominator.) Since the hardcoded side is usually set to FULL, you end up with a duplex mismatch which kills performance. If you've still got old Sun HME cards ardoun, there is some auto-meg issues with those, in combination with some older Cisco versions, but for the most part, Auto is where it's at. Auto is actually a requirement for proper flow control in GigE. Paul -- -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kennedy, Cameron Sent: August 15, 2007 7:49 PM To: Deiter, Scott; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Very slow client did you check network settings on the NIC? Is it set to 100/Full (or whatever your network standard is)? I find any Windows clients set to auto detect run very slow. La version française suit le texte anglais. This email may contain privileged and/or confidential information, and the Bank of Canada does not waive any related rights. Any distribution, use, or copying of this email or the information it contains by other than the intended recipient is unauthorized. If you received this email in error please delete it immediately from your system and notify the sender promptly by email that you have done so. Le présent courriel peut contenir de l'information privilégiée ou confidentielle. La Banque du Canada ne renonce pas aux droits qui s'y rapportent. Toute diffusion, utilisation ou copie de ce courriel ou des renseignements qu'il contient par une personne autre que le ou les destinataires désignés est interdite. Si vous recevez ce courriel par erreur, veuillez le supprimer immédiatement et envoyer sans délai à l'expéditeur un message électronique pour l'aviser que vous avez éliminé de votre ordinateur toute copie du courriel reçu. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Very slow client
We are running 5.1 mp4 across the board with a solaris 9 master media a few other media servers and numerous solaris and windows clients. on the master/media we just added a windows 2003 client only for system state backups. we cancelled these attempts because of performance. Less than 10K/sec Yes I mean Kilobytes. So we tried this in a test policy to backup the c drive. Same result. ftp is moving at 2-3 meg/sec bpgetconfig and bpclntcmd all look and feel normal. The client softwhere was removed and reinstalled. open file backup disabled tracker disabled. Where else do I look for the bottleneck? Scott Deiter System Administrator Hanover Direct, Inc. Hanover, PA Voice: 717-633-3298 Fax: 717-633-3101 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Very slow client
did you check network settings on the NIC? Is it set to 100/Full (or whatever your network standard is)? I find any Windows clients set to auto detect run very slow. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Deiter, Scott Sent: Wednesday, August 15, 2007 4:44 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Very slow client We are running 5.1 mp4 across the board with a solaris 9 master media a few other media servers and numerous solaris and windows clients. on the master/media we just added a windows 2003 client only for system state backups. we cancelled these attempts because of performance. Less than 10K/sec Yes I mean Kilobytes. So we tried this in a test policy to backup the c drive. Same result. ftp is moving at 2-3 meg/sec bpgetconfig and bpclntcmd all look and feel normal. The client softwhere was removed and reinstalled. open file backup disabled tracker disabled. Where else do I look for the bottleneck? Scott Deiter System Administrator Hanover Direct, Inc. Hanover, PA Voice: 717-633-3298 Fax: 717-633-3101 - This email (including any attachments) is confidential. If you are not the intended recipient you must not copy, use, disclose, distribute or rely on the information contained in it. If you have received this email in error, please notify the sender immediately by reply email and delete the email from your system. Confidentiality and legal privilege attached to this communication are not waived or lost by reason of mistaken delivery to you. Lend Lease does not guarantee that this email or the attachment(s) are unaffected by computer virus, corruption or other defects. Lend Lease may monitor incoming and outgoing emails for compliance with its Email Policy. Please note that our servers may not be located in your country.___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Very slow client
Scott, The 2003 server should be protecting the shadow copy components not the system state which is for Windows 2000. As for the other performance my first suggestion is to check the NIC setting. If GigE then auto negotiate is acceptable; however, if 100Mbps Ethernet is used force the NIC to 100 FULL duplex. The C:\ drive, especially the Windows directory will always be a pain from a speed and feed perspective, but not to the limits you're seeing. Lastly, set the virus scan to scan inbound only, using the outbound on a backup is a performance hit no one wants to experience. Thanks, Rockey J. Reed You're not obligated to win. You're obligated to keep trying to do the best you can every day. Marian Wright Edelman From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Deiter, Scott Sent: Wednesday, August 15, 2007 3:44 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Very slow client We are running 5.1 mp4 across the board with a solaris 9 master media a few other media servers and numerous solaris and windows clients. on the master/media we just added a windows 2003 client only for system state backups. we cancelled these attempts because of performance. Less than 10K/sec Yes I mean Kilobytes. So we tried this in a test policy to backup the c drive. Same result. ftp is moving at 2-3 meg/sec bpgetconfig and bpclntcmd all look and feel normal. The client softwhere was removed and reinstalled. open file backup disabled tracker disabled. Where else do I look for the bottleneck? Scott Deiter System Administrator Hanover Direct, Inc. Hanover, PA Voice: 717-633-3298 Fax: 717-633-3101 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
