Re: Network settings and poor backup performance.

2005-12-22 Thread Egon Blouder
Dear Rafa, could you me an invitation to get a gmail account? Thanks --.. -Original Message- From: Rafa [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU Sent: Wed, 30 Nov 2005 12:24:36 -0500 Subject: Re: [ADSM-L] Network settings and poor backup performance. On 11/30/05, Ray

Network settings and poor backup performance.

2005-11-30 Thread Ray Louvier
Can anyone give the technical reason why auto detect on Server NICs cause such horrible performance for TSM server backups and restores. We have our TSM server NIC set to 100MB Full also our switch Port set to 100 Full but we have users with sorted networks such as 1 GB switches plugged into 100 M

Re: Network settings and poor backup performance.

2005-11-30 Thread Mark Stapleton
ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 11/30/2005 10:00:06 AM: Can anyone give the technical reason why auto detect on Server NICs cause such horrible performance for TSM server backups and restores. sound of hollow laughter This is a bone of network contention (no pun intended),

Re: Network settings and poor backup performance.

2005-11-30 Thread Troy Frank
Because nic switch vendors never seem to implement the autodetect spec in the same and/or correct way. Depending on the manufacturer of the switch/nic, sometimes you have to use auto on both, sometimes you have to hardcode both, sometimes you have to hard code one but set the other to auto.

Re: Network settings and poor backup performance.

2005-11-30 Thread Rafa
On 11/30/05, Ray Louvier [EMAIL PROTECTED] wrote: Can anyone give the technical reason why auto detect on Server NICs cause such horrible performance for TSM server backups and restores. We This sounds like a network problem, not a TSM one. Quick way to prove it: try a backup/restore to

Re: Network settings and poor backup performance.

2005-11-30 Thread Allen S. Rout
== On Wed, 30 Nov 2005 10:20:59 -0600, Mark Stapleton [EMAIL PROTECTED] said: sound of hollow laughter This is a bone of network contention (no pun intended), particularly with Cisco networks. It is *not* a TSM problem. (As usual, TSM is the World's Best IT Infrastructure Problem Finder.)