ADSM-L

Re: [ADSM-L] TSM Cluster Scheduler Question

2008-07-02 05:21:16
Subject: Re: [ADSM-L] TSM Cluster Scheduler Question
From: "Minns, Farren - Chichester" <fminns AT WILEY DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 2 Jul 2008 10:19:32 +0100
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:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
PAC Brion Arnaud
Sent: 01 July 2008 11:15
To: ADSM-L AT VM.MARIST DOT 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: arnaud.brion AT panalpina DOT com
************************************************************************
******


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Henrik Vahlstedt
Sent: mardi 1 juillet 2008 11:58
To: ADSM-L AT VM.MARIST DOT 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\
<nodename>\<TSM server instance name>

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? :-) You will find the answer if you search on the
nodename and schedule in TSM.


//Henrik



-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Minns, Farren - Chichester
Sent: den 1 juli 2008 11:31
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] TSM Cluster Scheduler Question

Hi All

TSM 5.4.1.2 on Solaris 2.9
Backing up Exchange (MS Windows Server 2003, RC2 SP") - 5.5.0.0 in a
clustered environment.

We had this set up by an outside company and are now seeing some
problems with the TSM Cluster Scheduler automatically failing over the
cluster due to a password issue (this is as far as I can see anyway).

So, the dumb question, what does the Cluster Scheduler actually do?
I can see there is a separate schedule for the Exchange TDP backups.

Thanks

Farren




------------------------------------------------------------------------
------------------------------------
This email (and any attachment) is confidential, may be legally
privileged and is intended solely for the use of the individual or
entity to whom it is addressed. If you are not the intended recipient
please do not disclose, copy or take any action in reliance on it. If
you have received this message in error please tell us by reply and
delete all copies on your system.

Although this email has been scanned for viruses you should rely on your
own virus check as the sender accepts no liability for any damage
arising out of any bug or virus infection. Please note that email
traffic data may be monitored and that emails may be viewed for security
reasons.

John Wiley & Sons Limited is a private limited company registered in
England with registered number 641132.

Registered office address: The Atrium, Southern Gate, Chichester, West
Sussex, PO19 8SQ.
------------------------------------------------------------------------
------------------------------------


-------------------------------------------------------------------
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of
the information or copying of this message is prohibited. If you are not
the addressee, please notify the sender immediately by return e-mail and
delete this message.
Thank you.
------------------------------------------------------------------------------------------------------------
This email (and any attachment) is confidential, may be legally privileged and 
is intended solely for the 
use of the individual or entity to whom it is addressed. If you are not the 
intended recipient please do 
not disclose, copy or take any action in reliance on it. If you have received 
this message in error please 
tell us by reply and delete all copies on your system.
 
Although this email has been scanned for viruses you should rely on your own 
virus check as the sender 
accepts no liability for any damage arising out of any bug or virus infection. 
Please note that email 
traffic data may be monitored and that emails may be viewed for security 
reasons.

John Wiley & Sons Limited is a private limited company registered in England 
with registered number 641132.

Registered office address: The Atrium, Southern Gate, Chichester, West Sussex, 
PO19 8SQ.
------------------------------------------------------------------------------------------------------------

<Prev in Thread] Current Thread [Next in Thread>