Re: Windows 2000 and 2003 servers backups very poor performance
Thanks Justin and Miguel Miguel for the client we are using those recommended settings, they have been in place since we started backung up the clients. As for the TSM server settings I don't believe they need to be adjusted as we have many other clients that are running fine. Thanks Miguel Saez wrote: Review the following tunning: Client TSM: - Set Ethernet speed and duplex settings (Don't rely on Auto Detect) - Specifies: tcpwindowssize 63(recommended) 2048 (max) in KB tcpbufsize 32(recommended) 2048 (max) in KB tcpnodelay yes diskbuffsize 32 (recommended) 1023 (max) in KB compression yes Server TSM - Set Ethernet speed and duplex settings (Don't rely on Auto Detect) - Specifies BufPoolSize 131072 (for server with 1 GB RAM) UseLargeBuffers yes tcpwindowsize 63 (recommended)2048 (max) in KB tcpbuffsize 32 (recommended)2048 (max) in KB -- Use up to 3/4 of real memory for a dedicated TSM server (no other applications). tcpnodelayyes And Use dedicated networks for backup (LAN or SAN). Regards Miguel Sáez Sáez IBM Certified Deployment Professional Tivoli Configuration Manager IT Specialist IBM de Chile S.A.C. mail: [EMAIL PROTECTED] Phone: 562-2006638
Re: Windows 2000 and 2003 servers backups very poor performance
Thanksto all who responded I appreciate it. I will have a co-worker check the Nics and Switch first since that seems to be the place to start. Richard, I did take a look at the backup performance section and as I suspected several factors can affect a backup's performance. I was just curious as to if there was a setting in the clients the dsm.opt file that I could change that might make difference. Thanks again! Jeremy Curtis wrote: I agree on the speed/duplex. I have personally seen speed/duplex mismatch cause this. I don't personally have issues with Auto, just make sure both sides(server and switch) match. Jeremy Curtis Backup Administrator / Network Technician Vail Resorts, Inc. (970) 845-1921 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Kelly Lipp Sent: Thursday, March 22, 2007 3:56 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Wiindows 2000 and 2003 servers backups very poor performance I will amplify Curtis' call on this: check the NICs. Especially if you are on 100MB Ethernet. For GigE, you generally can't choose, but make it all the same in the path between the server and TSM. As for testing: try an ftp of a large file (a gig or so so it stays on the wire for a minute or so). If this is faster than you are getting from TSM, you have a TSM problem. If it is the same speed, you have a network problem. Kelly J. Lipp VP Manufacturing CTO STORServer, Inc. 485-B Elkton Drive Colorado Springs, CO 80907 719-266-8777 [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Carpenter, Curtis Sent: Thursday, March 22, 2007 3:52 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Wiindows 2000 and 2003 servers backups very poor performance I would make sure whatever speed and duplex setting you have the nic set to, you should set the switch port to match. I would try to avoid setting both to autonegotiate, as I have personally seen horrible performance with that setting. Also, run diags on network interfaces to rule out any hardware problems. Are u using a seperate nic for your tivoli backups or are u using just one nic for all network communication on these servers? --Original Message-- From: Timothy Hughes To: ADSM-L ReplyTo: ADSM-L Sent: Mar 22, 2007 3:33 PM Subject: [ADSM-L] Wiindows 2000 and 2003 servers backups very poor performance Hello, We have about 5 or 6 Windows Servers whose backups performance is very very poor these backups start a midnight and run throughout the whole day and sometimes run for a couple days I have been reading different options including the DISKBuffsize option, I know poor networking performance can be caused by a number of factors and not sure which parameter to look at first. Here is an example of one of the clients dsm.opt file, They all basically look the same and the parameters matches TSM windows clients recommendations. Lang Ameng Domain ALL-LOCAL TCPSERVERADDRESS .xxx.x.xx.xx Passwordaccess generate TCPCLIENTADDRESS xx.xx.xxx.xx NODENAME SUBDIR YES REPLACE PROMPT TCPB 32 TCPW 63 SCHEDMODE PROMPTED TXNBYTELIMIT 25600 ERRORLOGNAME SCHEDLOGNAME ERRORLOGRETENTION 14 SCHEDLOGRETENTION 7 TCPNODELAY YES RESOURCEUTILIZATION 3 LARGECOMMBUFFERS YES CHANGINGRETRIES 2 COMPRESSION BACKUPREG YES MANAGEDSERVICES WEBCLIENT SCHEDULE Windows 2000 and 2003 servers TSM server 5.3.4 TSM client 5.3.4
Re: Windows 2000 and 2003 servers backups very poor performance
We are using GigE and Curtis we are using a separate nic for tivoli backups. Thanks Tim Carpenter, Curtis wrote: I would make sure whatever speed and duplex setting you have the nic set to, you should set the switch port to match. I would try to avoid setting both to autonegotiate, as I have personally seen horrible performance with that setting. Also, run diags on network interfaces to rule out any hardware problems. Are u using a seperate nic for your tivoli backups or are u using just one nic for all network communication on these servers? --Original Message-- From: Timothy Hughes To: ADSM-L ReplyTo: ADSM-L Sent: Mar 22, 2007 3:33 PM Subject: [ADSM-L] Wiindows 2000 and 2003 servers backups very poor performance Hello, We have about 5 or 6 Windows Servers whose backups performance is very very poor these backups start a midnight and run throughout the whole day and sometimes run for a couple days I have been reading different options including the DISKBuffsize option, I know poor networking performance can be caused by a number of factors and not sure which parameter to look at first. Here is an example of one of the clients dsm.opt file, They all basically look the same and the parameters matches TSM windows clients recommendations. Lang Ameng Domain ALL-LOCAL TCPSERVERADDRESS .xxx.x.xx.xx Passwordaccess generate TCPCLIENTADDRESS xx.xx.xxx.xx NODENAME SUBDIR YES REPLACE PROMPT TCPB 32 TCPW 63 SCHEDMODE PROMPTED TXNBYTELIMIT 25600 ERRORLOGNAME SCHEDLOGNAME ERRORLOGRETENTION 14 SCHEDLOGRETENTION 7 TCPNODELAY YES RESOURCEUTILIZATION 3 LARGECOMMBUFFERS YES CHANGINGRETRIES 2 COMPRESSION BACKUPREG YES MANAGEDSERVICES WEBCLIENT SCHEDULE Windows 2000 and 2003 servers TSM server 5.3.4 TSM client 5.3.4
Re: Windows 2000 and 2003 servers backups very poor performance
Doesn't matter the speed of your card if there is a mismatch on the nic and port. [EMAIL PROTECTED] 03/23/07 1:33 PM We are using GigE and Curtis we are using a separate nic for tivoli backups. Thanks Tim Carpenter, Curtis wrote: I would make sure whatever speed and duplex setting you have the nic set to, you should set the switch port to match. I would try to avoid setting both to autonegotiate, as I have personally seen horrible performance with that setting. Also, run diags on network interfaces to rule out any hardware problems. Are u using a seperate nic for your tivoli backups or are u using just one nic for all network communication on these servers? --Original Message-- From: Timothy Hughes To: ADSM-L ReplyTo: ADSM-L Sent: Mar 22, 2007 3:33 PM Subject: [ADSM-L] Wiindows 2000 and 2003 servers backups very poor performance Hello, We have about 5 or 6 Windows Servers whose backups performance is very very poor these backups start a midnight and run throughout the whole day and sometimes run for a couple days I have been reading different options including the DISKBuffsize option, I know poor networking performance can be caused by a number of factors and not sure which parameter to look at first. Here is an example of one of the clients dsm.opt file, They all basically look the same and the parameters matches TSM windows clients recommendations. Lang Ameng Domain ALL-LOCAL TCPSERVERADDRESS .xxx.x.xx.xx Passwordaccess generate TCPCLIENTADDRESS xx.xx.xxx.xx NODENAME SUBDIR YES REPLACE PROMPT TCPB 32 TCPW 63 SCHEDMODE PROMPTED TXNBYTELIMIT 25600 ERRORLOGNAME SCHEDLOGNAME ERRORLOGRETENTION 14 SCHEDLOGRETENTION 7 TCPNODELAY YES RESOURCEUTILIZATION 3 LARGECOMMBUFFERS YES CHANGINGRETRIES 2 COMPRESSION BACKUPREG YES MANAGEDSERVICES WEBCLIENT SCHEDULE Windows 2000 and 2003 servers TSM server 5.3.4 TSM client 5.3.4 The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain information that is confidential, privileged, and/or otherwise exempt from disclosure under applicable law. If this electronic message is from an attorney or someone in the Legal Department, it may also contain confidential attorney-client communications which may be privileged and protected from disclosure. If you are not the intended recipient, be advised that you have received this message in error and that any use, dissemination, forwarding, printing, or copying is strictly prohibited. Please notify the New York State Thruway Authority immediately by either responding to this e-mail or calling (518) 436-2700, and destroy all copies of this message and any attachments.
Re: Windows 2000 and 2003 servers backups very poor performance
Hi Lawrence, I was informed there is no mismatch, and since that is the case I was curious since we are using GigE as opposed to what we used to before (100mb ethernet full) and the dsm.opt files were based on those settings could we adjust those parameters and is there any documentation or guides that says use different parameters for GigE. Thanks Tim Lawrence Clark wrote: Doesn't matter the speed of your card if there is a mismatch on the nic and port. [EMAIL PROTECTED] 03/23/07 1:33 PM We are using GigE and Curtis we are using a separate nic for tivoli backups. Thanks Tim Carpenter, Curtis wrote: I would make sure whatever speed and duplex setting you have the nic set to, you should set the switch port to match. I would try to avoid setting both to autonegotiate, as I have personally seen horrible performance with that setting. Also, run diags on network interfaces to rule out any hardware problems. Are u using a seperate nic for your tivoli backups or are u using just one nic for all network communication on these servers? --Original Message-- From: Timothy Hughes To: ADSM-L ReplyTo: ADSM-L Sent: Mar 22, 2007 3:33 PM Subject: [ADSM-L] Wiindows 2000 and 2003 servers backups very poor performance Hello, We have about 5 or 6 Windows Servers whose backups performance is very very poor these backups start a midnight and run throughout the whole day and sometimes run for a couple days I have been reading different options including the DISKBuffsize option, I know poor networking performance can be caused by a number of factors and not sure which parameter to look at first. Here is an example of one of the clients dsm.opt file, They all basically look the same and the parameters matches TSM windows clients recommendations. Lang Ameng Domain ALL-LOCAL TCPSERVERADDRESS .xxx.x.xx.xx Passwordaccess generate TCPCLIENTADDRESS xx.xx.xxx.xx NODENAME SUBDIR YES REPLACE PROMPT TCPB 32 TCPW 63 SCHEDMODE PROMPTED TXNBYTELIMIT 25600 ERRORLOGNAME SCHEDLOGNAME ERRORLOGRETENTION 14 SCHEDLOGRETENTION 7 TCPNODELAY YES RESOURCEUTILIZATION 3 LARGECOMMBUFFERS YES CHANGINGRETRIES 2 COMPRESSION BACKUPREG YES MANAGEDSERVICES WEBCLIENT SCHEDULE Windows 2000 and 2003 servers TSM server 5.3.4 TSM client 5.3.4 The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain information that is confidential, privileged, and/or otherwise exempt from disclosure under applicable law. If this electronic message is from an attorney or someone in the Legal Department, it may also contain confidential attorney-client communications which may be privileged and protected from disclosure. If you are not the intended recipient, be advised that you have received this message in error and that any use, dissemination, forwarding, printing, or copying is strictly prohibited. Please notify the New York State Thruway Authority immediately by either responding to this e-mail or calling (518) 436-2700, and destroy all copies of this message and any attachments.
Re: Windows 2000 and 2003 servers backups very poor performance
Are you certain this is a network problem? I know we had similar problems with some Windows servers here and it turns out that TSM was spending hours and hours just scanning the files on the box because there were literally millions of them. We turned on the TSM journaling service and that dramtically cut down the overall backup time. Justin Timothy Hughes [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 03/23/2007 01:50 PM Please respond to ADSM: Dist Stor Manager To: ADSM-L@VM.MARIST.EDU cc: Subject:Re: [ADSM-L] Windows 2000 and 2003 servers backups very poor performance Hi Lawrence, I was informed there is no mismatch, and since that is the case I was curious since we are using GigE as opposed to what we used to before (100mb ethernet full) and the dsm.opt files were based on those settings could we adjust those parameters and is there any documentation or guides that says use different parameters for GigE. Thanks Tim Lawrence Clark wrote: Doesn't matter the speed of your card if there is a mismatch on the nic and port. [EMAIL PROTECTED] 03/23/07 1:33 PM We are using GigE and Curtis we are using a separate nic for tivoli backups. Thanks Tim Carpenter, Curtis wrote: I would make sure whatever speed and duplex setting you have the nic set to, you should set the switch port to match. I would try to avoid setting both to autonegotiate, as I have personally seen horrible performance with that setting. Also, run diags on network interfaces to rule out any hardware problems. Are u using a seperate nic for your tivoli backups or are u using just one nic for all network communication on these servers? --Original Message-- From: Timothy Hughes To: ADSM-L ReplyTo: ADSM-L Sent: Mar 22, 2007 3:33 PM Subject: [ADSM-L] Wiindows 2000 and 2003 servers backups very poor performance Hello, We have about 5 or 6 Windows Servers whose backups performance is very very poor these backups start a midnight and run throughout the whole day and sometimes run for a couple days I have been reading different options including the DISKBuffsize option, I know poor networking performance can be caused by a number of factors and not sure which parameter to look at first. Here is an example of one of the clients dsm.opt file, They all basically look the same and the parameters matches TSM windows clients recommendations. Lang Ameng Domain ALL-LOCAL TCPSERVERADDRESS .xxx.x.xx.xx Passwordaccess generate TCPCLIENTADDRESS xx.xx.xxx.xx NODENAME SUBDIR YES REPLACE PROMPT TCPB 32 TCPW 63 SCHEDMODE PROMPTED TXNBYTELIMIT 25600 ERRORLOGNAME SCHEDLOGNAME ERRORLOGRETENTION 14 SCHEDLOGRETENTION 7 TCPNODELAY YES RESOURCEUTILIZATION 3 LARGECOMMBUFFERS YES CHANGINGRETRIES 2 COMPRESSION BACKUPREG YES MANAGEDSERVICES WEBCLIENT SCHEDULE Windows 2000 and 2003 servers TSM server 5.3.4 TSM client 5.3.4 The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain information that is confidential, privileged, and/or otherwise exempt from disclosure under applicable law. If this electronic message is from an attorney or someone in the Legal Department, it may also contain confidential attorney-client communications which may be privileged and protected from disclosure. If you are not the intended recipient, be advised that you have received this message in error and that any use, dissemination, forwarding, printing, or copying is strictly prohibited. Please notify the New York State Thruway Authority immediately by either responding to this e-mail or calling (518) 436-2700, and destroy all copies of this message and any attachments.
Re: Windows 2000 and 2003 servers backups very poor performance
Review the following tunning: Client TSM: - Set Ethernet speed and duplex settings (Don't rely on Auto Detect) - Specifies: tcpwindowssize 63(recommended) 2048 (max) in KB tcpbufsize 32(recommended) 2048 (max) in KB tcpnodelay yes diskbuffsize 32 (recommended) 1023 (max) in KB compression yes Server TSM - Set Ethernet speed and duplex settings (Don't rely on Auto Detect) - Specifies BufPoolSize 131072 (for server with 1 GB RAM) UseLargeBuffers yes tcpwindowsize 63 (recommended)2048 (max) in KB tcpbuffsize 32 (recommended)2048 (max) in KB -- Use up to 3/4 of real memory for a dedicated TSM server (no other applications). tcpnodelayyes And Use dedicated networks for backup (LAN or SAN). Regards Miguel Sáez Sáez IBM Certified Deployment Professional Tivoli Configuration Manager IT Specialist IBM de Chile S.A.C. mail: [EMAIL PROTECTED] Phone: 562-2006638
