Re: SV: Slow TSM Client after Symantec installation
Thanks people I have got the admin to make the necessary change and we'll see what happens over night. Regards Farren -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Christian Svensson Sent: 23 September 2008 12:59 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] SV: Slow TSM Client after Symantec installation Hi, Symantec did have the same issue in one of the older client also. We reported back to Symantec and did get a fix later on for that. Best Regards Christian Svensson WW Support: +44-1453-84 7009 U.S. Support: +1-866-832-2267 Cell: +46-70-325 1577 E-mail: [EMAIL PROTECTED] Skype: cristie.christian.svensson Från: ADSM: Dist Stor Manager [EMAIL PROTECTED] för Minns, Farren - Chichester [EMAIL PROTECTED] Skickat: den 23 september 2008 12:00 Till: ADSM-L@VM.MARIST.EDU Ämne: Slow TSM Client after Symantec installation Hi All Last weekend, an administrator installed Symantec Endpoint Protection on a few of our large Windows clients (details below). Since then, the backups have slowed to a crawl, and we have proves that if we stop the antivirus scanning specific large directories the performance is restored. But of course they want to have this software running on all drives/folders. Has anyone else dealt with this issue? Thanks in advance Farren Minns - John Wiley & Sons Ltd CLIENT OS - Windows Server 2003 R2 SP1 AV - Symantec Endpoint Protection 11.0.2010.25 TSM Client - 5.3.5.0 TSM SERVER OS - Solaris 9 Server lvl - 5.4.1.2 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Phillip Burgess Sent: 02 July 2008 13:21 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Cluster Scheduler Question Hi Farren Yes that's correct From: Minns, Farren - Chichester [mailto:[EMAIL PROTECTED] Sent: Wed 02/07/2008 12:29 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Cluster Scheduler Question Thanks Phil, I have now located Cluster Manager :-) One more question, I assume the state of the scheduler on either of the actual cluster nodes should be set to manual? Thanks Farren -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Phillip Burgess Sent: 02 July 2008 11:55 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Cluster Scheduler Question Hi Farren Both of servers in the cluster will have a utility called Cluster administrator, you must use this to start and stop the TSM scheduler services for the backups on the clustered drives, if you stop them via computer manager (services.msc) then you could cause the cluster to fail to the other node. The cluster administrator utility should automatically start the services on the other node in the case of a failover. If you want to restart the TSM scheduler for the local drive backups then you can do this in the same manner as a non-cluster server. cheers Phil From: Minns, Farren - Chichester [mailto:[EMAIL PROTECTED] Sent: Wed 02/07/2008 10:19 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Cluster Scheduler Question Hi all again I am still (I think) having issues with this, although due to another issue which is nothing to do with me, I can't even get onto the servers in question to do more digging. I have a question though regarding the schedulers. In this case we have a cluster called CHI-MB with two cluster nodes (CHI-MB01 and CHI-MB02). Now, when stopping/starting the scheduler/s in question do I make sure to do this from the actual cluster (CHI-MB)? Sorry my terminology is off because I'm not the system administrator for this kit, just TSM. Will this then effect the active node? And if so, is there some mechanism in place that starts the scheduler on the passive node if there is a failover? Thanks Farren -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of PAC Brion Arnaud Sent: 01 July 2008 11:15 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Cluster Scheduler Question Farren, You may be affected by a faulty configuration, where the password in MS cluster's checkpoint file is not synchronized with the local registry password anymore, thus making the service fail ... It happened several times in our shop already ! IBM noticed the problem, and published a solution here : http://www-1.ibm.com/support/docview.wss?uid=swg21243061 May be of interest for you ! Cheers. Arnaud ** Panalpina Management Ltd., Basle, Switzerland, CIT Department Viadukstrasse 42, P.O. Box 4002 Basel/CH Phone: +41 (61) 226 11 11, FAX: +41 (61) 226 17 0
SV: Slow TSM Client after Symantec installation
Hi, Symantec did have the same issue in one of the older client also. We reported back to Symantec and did get a fix later on for that. Best Regards Christian Svensson WW Support: +44-1453-84 7009 U.S. Support: +1-866-832-2267 Cell: +46-70-325 1577 E-mail: [EMAIL PROTECTED] Skype: cristie.christian.svensson Från: ADSM: Dist Stor Manager [EMAIL PROTECTED] för Minns, Farren - Chichester [EMAIL PROTECTED] Skickat: den 23 september 2008 12:00 Till: ADSM-L@VM.MARIST.EDU Ämne: Slow TSM Client after Symantec installation Hi All Last weekend, an administrator installed Symantec Endpoint Protection on a few of our large Windows clients (details below). Since then, the backups have slowed to a crawl, and we have proves that if we stop the antivirus scanning specific large directories the performance is restored. But of course they want to have this software running on all drives/folders. Has anyone else dealt with this issue? Thanks in advance Farren Minns - John Wiley & Sons Ltd CLIENT OS - Windows Server 2003 R2 SP1 AV - Symantec Endpoint Protection 11.0.2010.25 TSM Client - 5.3.5.0 TSM SERVER OS - Solaris 9 Server lvl - 5.4.1.2 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Phillip Burgess Sent: 02 July 2008 13:21 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Cluster Scheduler Question Hi Farren Yes that's correct From: Minns, Farren - Chichester [mailto:[EMAIL PROTECTED] Sent: Wed 02/07/2008 12:29 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Cluster Scheduler Question Thanks Phil, I have now located Cluster Manager :-) One more question, I assume the state of the scheduler on either of the actual cluster nodes should be set to manual? Thanks Farren -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Phillip Burgess Sent: 02 July 2008 11:55 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Cluster Scheduler Question Hi Farren Both of servers in the cluster will have a utility called Cluster administrator, you must use this to start and stop the TSM scheduler services for the backups on the clustered drives, if you stop them via computer manager (services.msc) then you could cause the cluster to fail to the other node. The cluster administrator utility should automatically start the services on the other node in the case of a failover. If you want to restart the TSM scheduler for the local drive backups then you can do this in the same manner as a non-cluster server. cheers Phil From: Minns, Farren - Chichester [mailto:[EMAIL PROTECTED] Sent: Wed 02/07/2008 10:19 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Cluster Scheduler Question Hi all again I am still (I think) having issues with this, although due to another issue which is nothing to do with me, I can't even get onto the servers in question to do more digging. I have a question though regarding the schedulers. In this case we have a cluster called CHI-MB with two cluster nodes (CHI-MB01 and CHI-MB02). Now, when stopping/starting the scheduler/s in question do I make sure to do this from the actual cluster (CHI-MB)? Sorry my terminology is off because I'm not the system administrator for this kit, just TSM. Will this then effect the active node? And if so, is there some mechanism in place that starts the scheduler on the passive node if there is a failover? Thanks Farren -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of PAC Brion Arnaud Sent: 01 July 2008 11:15 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Cluster Scheduler Question Farren, You may be affected by a faulty configuration, where the password in MS cluster's checkpoint file is not synchronized with the local registry password anymore, thus making the service fail ... It happened several times in our shop already ! IBM noticed the problem, and published a solution here : http://www-1.ibm.com/support/docview.wss?uid=swg21243061 May be of interest for you ! Cheers. Arnaud ** Panalpina Management Ltd., Basle, Switzerland, CIT Department Viadukstrasse 42, P.O. Box 4002 Basel/CH Phone: +41 (61) 226 11 11, FAX: +41 (61) 226 17 01 Direct: +41 (61) 226 19 78 e-mail: [EMAIL PROTECTED] ** -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Henrik Vahlstedt Sent: mardi 1 juillet 2008 11:58 To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM Cluster Scheduler Question
Fw: Slow TSM Client after Symantec installation
There's a setting in Symantec Antivirus to enable/disable checking on backup access to files - I'd assume that Endpoint Protection has the same thing. It's under Configure/Filesystem Auto Protect. That's probably what's hitting you. Nick Cassimatis - Forwarded by Nicholas Cassimatis/Raleigh/IBM on 09/23/2008 07:40 AM - "ADSM: Dist Stor Manager" wrote on 09/23/2008 06:00:09 AM: > [image removed] > > Slow TSM Client after Symantec installation > > Minns, Farren - Chichester > > to: > > ADSM-L > > 09/23/2008 06:03 AM > > Sent by: > > "ADSM: Dist Stor Manager" > > Please respond to "ADSM: Dist Stor Manager". > > Hi All > > > > Last weekend, an administrator installed Symantec Endpoint > Protection on a few of our large Windows clients (details below). > > > > Since then, the backups have slowed to a crawl, and we have proves > that if we stop the antivirus scanning specific large directories > the performance is restored. But of course they want to have this > software running on all drives/folders. > > > > Has anyone else dealt with this issue? > > > > Thanks in advance > > Farren Minns - John Wiley & Sons Ltd > > > > > > > > CLIENT > > OS - Windows Server 2003 R2 SP1 > > AV - Symantec Endpoint Protection 11.0.2010.25 > > TSM Client - 5.3.5.0 > > > > TSM SERVER > > OS - Solaris 9 > > Server lvl - 5.4.1.2 > > > > > > > > > > > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On > Behalf Of Phillip Burgess > Sent: 02 July 2008 13:21 > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] TSM Cluster Scheduler Question > > > > Hi Farren > > > > Yes that's correct > > > > > > > > > > > > From: Minns, Farren - Chichester [mailto:[EMAIL PROTECTED] > > Sent: Wed 02/07/2008 12:29 > > To: ADSM-L@VM.MARIST.EDU > > Subject: Re: [ADSM-L] TSM Cluster Scheduler Question > > > > > > > > Thanks Phil, I have now located Cluster Manager :-) > > > > One more question, I assume the state of the scheduler on either of > the actual cluster nodes should be set to manual? > > > > Thanks > > > > Farren > > > > > > > > > > -Original Message- > > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On > Behalf Of Phillip Burgess > > Sent: 02 July 2008 11:55 > > To: ADSM-L@VM.MARIST.EDU > > Subject: Re: [ADSM-L] TSM Cluster Scheduler Question > > > > > > Hi Farren > > > > Both of servers in the cluster will have a utility called Cluster > administrator, you must use this to start and stop the TSM scheduler > services for the backups on the clustered drives, if you stop them > via computer manager (services.msc) then you could cause the cluster > to fail to the other node. > > The cluster administrator utility should automatically start the > services on the other node in the case of a failover. > > If you want to restart the TSM scheduler for the local drive backups > then you can do this in the same manner as a non-cluster server. > > > > cheers > > Phil > > > > > > > > From: Minns, Farren - Chichester [mailto:[EMAIL PROTECTED] > > Sent: Wed 02/07/2008 10:19 > > To: ADSM-L@VM.MARIST.EDU > > Subject: Re: [ADSM-L] TSM Cluster Scheduler Question > > > > > > > > Hi all again > > > > I am still (I think) having issues with this, although due to > another issue which is nothing to do with me, I can't even get onto > the servers in question to do more digging. > > > > I have a question though regarding the schedulers. > > > > In this case we have a cluster called CHI-MB with two cluster nodes > (CHI-MB01 and CHI-MB02). Now, when stopping/starting the scheduler/s > in question do I make sure to do this from the actual cluster (CHI- > MB)? Sorry my terminology is off because I'm not the system > administrator for this kit, just TSM. Will this then effect the > active node? And if so, is there some mechanism in place that starts > the scheduler on the passive node if there is a failover? > > > > Thanks > > > > Farren > > > > > > > > > > > > -Original Message- > > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On > Behalf Of PAC Brion Arnaud > > Sent: 01 July 2008 11:15 > >
Slow TSM Client after Symantec installation
Hi All Last weekend, an administrator installed Symantec Endpoint Protection on a few of our large Windows clients (details below). Since then, the backups have slowed to a crawl, and we have proves that if we stop the antivirus scanning specific large directories the performance is restored. But of course they want to have this software running on all drives/folders. Has anyone else dealt with this issue? Thanks in advance Farren Minns - John Wiley & Sons Ltd CLIENT OS - Windows Server 2003 R2 SP1 AV - Symantec Endpoint Protection 11.0.2010.25 TSM Client - 5.3.5.0 TSM SERVER OS - Solaris 9 Server lvl - 5.4.1.2 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Phillip Burgess Sent: 02 July 2008 13:21 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Cluster Scheduler Question Hi Farren Yes that's correct From: Minns, Farren - Chichester [mailto:[EMAIL PROTECTED] Sent: Wed 02/07/2008 12:29 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Cluster Scheduler Question Thanks Phil, I have now located Cluster Manager :-) One more question, I assume the state of the scheduler on either of the actual cluster nodes should be set to manual? Thanks Farren -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Phillip Burgess Sent: 02 July 2008 11:55 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Cluster Scheduler Question Hi Farren Both of servers in the cluster will have a utility called Cluster administrator, you must use this to start and stop the TSM scheduler services for the backups on the clustered drives, if you stop them via computer manager (services.msc) then you could cause the cluster to fail to the other node. The cluster administrator utility should automatically start the services on the other node in the case of a failover. If you want to restart the TSM scheduler for the local drive backups then you can do this in the same manner as a non-cluster server. cheers Phil From: Minns, Farren - Chichester [mailto:[EMAIL PROTECTED] Sent: Wed 02/07/2008 10:19 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Cluster Scheduler Question Hi all again I am still (I think) having issues with this, although due to another issue which is nothing to do with me, I can't even get onto the servers in question to do more digging. I have a question though regarding the schedulers. In this case we have a cluster called CHI-MB with two cluster nodes (CHI-MB01 and CHI-MB02). Now, when stopping/starting the scheduler/s in question do I make sure to do this from the actual cluster (CHI-MB)? Sorry my terminology is off because I'm not the system administrator for this kit, just TSM. Will this then effect the active node? And if so, is there some mechanism in place that starts the scheduler on the passive node if there is a failover? Thanks Farren -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of PAC Brion Arnaud Sent: 01 July 2008 11:15 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Cluster Scheduler Question Farren, You may be affected by a faulty configuration, where the password in MS cluster's checkpoint file is not synchronized with the local registry password anymore, thus making the service fail ... It happened several times in our shop already ! IBM noticed the problem, and published a solution here : http://www-1.ibm.com/support/docview.wss?uid=swg21243061 May be of interest for you ! Cheers. Arnaud ** Panalpina Management Ltd., Basle, Switzerland, CIT Department Viadukstrasse 42, P.O. Box 4002 Basel/CH Phone: +41 (61) 226 11 11, FAX: +41 (61) 226 17 01 Direct: +41 (61) 226 19 78 e-mail: [EMAIL PROTECTED] ** -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Henrik Vahlstedt Sent: mardi 1 juillet 2008 11:58 To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM Cluster Scheduler Question Hi, First, de-select "affect group" in the cluster resource properties for the TSM Cluster Scheduler in cluster administrator, cluadmin.exe. This prevents the whole cluster to failover when the TSM service stops due to whatever.. ex. bad password. Verify that the correct registry parameter is replicated as a part of the cluster resource: HKEY_LOCAL_MACHINE\SOFTWARE\IBM\ADSM\CurrentVersion\Nodes\ \ Consider to set passexp=0 on the TSM server for the Exchange node. Update PW on both cluster nodes. "what does the Cluster Scheduler actually do?" Backing up Exchange? :-
