Cluster Failover backup

G

Gotti

ADSM.ORG Member
Joined
Oct 3, 2002
Messages
3
Reaction score
0
Points
0
We are setting up a backup on a cluster and when we configure the Scheduler Service on Node 1 (or Node 2 for that matter) we type the following command:



C:\Program Files\Tivoli\TSM\baclient>dsmcutil install sched /name:"TSM Scheduler Service: Server-A" /clientdir:"C:\Program Files\Tivoli\Tsm\Baclient" /optfile:Q:\TSM\DSM.OPT /node:Server-A /password:hello /validate:yes /autostart:yes /clusternode:yes /clustername:SERVERCLU



After typing this I get the following confirmation that everything was successful:



TSM Windows NT Client Service Configuration Utility

Command Line Interface - Version 5, Release 1, Level 1.0

(C) Copyright IBM Corporation, 1990, 2002, All Rights Reserved.

Last Updated May 24 2002

TSM Api Verison 5.1.1



Command: Install TSM Client Service

Machine: Server(Local Machine)





Locating the Microsoft Cluster Server service ...





Installing TSM Client Service:



Machine : Server

Service Name : TSM Scheduler Service: Server-A

Client Directory : c:\program files\tivoli\tsm\baclient

Automatic Start : yes

Logon Account : LocalSystem



The service was successfully installed.





Creating Registry Keys ...



Updated registry value 'ImagePath' .

Updated registry value 'EventMessageFile' .

Updated registry value 'TypesSupported' .

Updated registry value 'TSM Scheduler Service: Server-A' .

Updated registry value 'ADSMClientKey' .

Updated registry value 'OptionsFile' .

Updated registry value 'EventLogging' .

Updated registry value 'ClientNodeName' .

Updated registry value 'ClusterNode' .

Updated registry value 'ClusterGroupName' .



Generating registry password ...

Authenticating TSM password for node Server-A ...

Connecting to TSM Server via client options file 'q:\tsm\dsm.opt' ...



Password authentication successful.

The registry password for TSM node Server-A has been updated.



Starting the 'TSM Scheduler Service: Server-A' service ......

The service was successfully started.



After doing this the password should have been set to hello, however when I issue the following command :



C:\Program Files\Tivoli\TSM\baclient>dsmcutil showpw /name:"TSM Sched

e: SERVER-A" /optfile:q:\tsm\dsm.opt /node:SERVER-A



I get back the following results:



TSM Windows NT Client Service Configuration Utility

Command Line Interface - Version 5, Release 1, Level 1.0

(C) Copyright IBM Corporation, 1990, 2002, All Rights Reserved.

Last Updated May 24 2002

TSM Api Verison 5.1.1



Command: Display Registry Password

Machine: Server(Local Machine)



Connecting to TSM Server via client options file 'q:\tsm\dsm.opt' ...



Registry password for node Server-A = '2' .



Authenticating password with TSM for node Server-A ....





Connecting to TSM Server via client options file 'q:\tsm\dsm.opt' ...



Authentication of the specified password failed .



Password Authentication failed.



WHY WAS THE PASSWORD CHANGED TO 2. Removed the service and tried it again and I get something different everytime. One time it was P1| I dont see where this comes from. But because of this my service fails with a incorrect password in the dsmerrorlog.



DSMERRORLOG

10/03/2002 09:05:13 ReadPswdFromRegistry(): getRegValue(): Win32 RC=2 .

10/03/2002 09:05:13 ReadPswdFromRegistry(): getRegValue(): Win32 RC=2 .

10/03/2002 09:05:51 sessOpen: Error 137 from signon authentication.

10/03/2002 09:06:07 sessOpen: Error 137 from signon authentication.





ANY ADVICE! :confused:
 
Well, Gotti,



I think your are not quite right in the cluster resource backup concept.

I think you have crossed over the scheduler for the local client with the scheduler for the cluster group... You should install the scheduler for the cluster failover and the Q:\TSM\DSM.OPT file for the cluster group and not for the Server-A. And when you install the scheduler for the local client on Server-A you should choose the c:\Program Files\Tivoli\TSM\baclient\dsm.opt file...





Here I give you an example:



You are to backup 2 nodes with 1 cluster group

1. Install a client on each node

2. Install the scheduler service for each TSM Client node on the local dsm.opt path.

3. Switch the cluster group to the node1.

4. Install the TSM Scheduler service for the cluster group with the dsm.opt on the cluster disk (your case is Q:\TSM\DSM.OPT)

5. Switch the cluster to the node2.

6. Install the TSM Scheduler service for the cluster group now on the node2 with the dsm.opt on the cluster disk.

7. In the Cluster Administrator of Windows 2000 install a generic service resource for the cluster failover.

8. Actualize the password by DSMC QUERY SESSION -OPT="Q:\TSM\DSM.OPT"



;)



For more information you should see the Appendix E from the Tivoli Storage Manager for Windows Backup-Archive Clients Installation and User's Guide and the DSMCUTIL HELP print result.





Regards.











<TABLE BORDER=0 ALIGN=CENTER WIDTH=85%><TR><TD><font class="pn-sub">Quote:</font><HR></TD></TR><TR><TD><FONT class="pn-sub"><BLOCKQUOTE>We are setting up a backup on a cluster and when we configure the Scheduler Service on Node 1 (or Node 2 for that matter) we type the following command:



C:program FilesTivoliTSMbaclient>dsmcutil install sched /name:"TSM Scheduler Service: Server-A" /clientdir:"C:\Program Files\Tivoli\Tsm\Baclient" /optfile:Q:\TSM\DSM.OPT /node:Server-A /password:hello /validate:yes /autostart:yes /clusternode:yes /clustername:SERVERCLU



After typing this I get the following confirmation that everything was successful:



TSM Windows NT Client Service Configuration Utility

Command Line Interface - Version 5, Release 1, Level 1.0

(C) Copyright IBM Corporation, 1990, 2002, All Rights Reserved.

Last Updated May 24 2002

TSM Api Verison 5.1.1



Command: Install TSM Client Service

Machine: Server(Local Machine)





Locating the Microsoft Cluster Server service ...





Installing TSM Client Service:



Machine : Server

Service Name : TSM Scheduler Service: Server-A

Client Directory : c:\program files\tivoli\tsm\baclient

Automatic Start : yes

Logon Account : LocalSystem



The service was successfully installed.





Creating Registry Keys ...



Updated registry value 'ImagePath' .

Updated registry value 'EventMessageFile' .

Updated registry value 'TypesSupported' .

Updated registry value 'TSM Scheduler Service: Server-A' .

Updated registry value 'ADSMClientKey' .

Updated registry value 'OptionsFile' .

Updated registry value 'EventLogging' .

Updated registry value 'ClientNodeName' .

Updated registry value 'ClusterNode' .

Updated registry value 'ClusterGroupName' .



Generating registry password ...

Authenticating TSM password for node Server-A ...

Connecting to TSM Server via client options file 'q:\tsm\dsm.opt' ...



Password authentication successful.

The registry password for TSM node Server-A has been updated.



Starting the 'TSM Scheduler Service: Server-A' service ......

The service was successfully started.



After doing this the password should have been set to hello, however when I issue the following command :



C:\Program Files\Tivoli\TSM\baclient>dsmcutil showpw /name:"TSM Sched

e: SERVER-A" /optfile:q:\tsm\dsm.opt /node:SERVER-A



I get back the following results:



TSM Windows NT Client Service Configuration Utility

Command Line Interface - Version 5, Release 1, Level 1.0

(C) Copyright IBM Corporation, 1990, 2002, All Rights Reserved.

Last Updated May 24 2002

TSM Api Verison 5.1.1



Command: Display Registry Password

Machine: Server(Local Machine)



Connecting to TSM Server via client options file 'q:\tsm\dsm.opt' ...



Registry password for node Server-A = '2' .



Authenticating password with TSM for node Server-A ....





Connecting to TSM Server via client options file 'q:\tsm\dsm.opt' ...



Authentication of the specified password failed .



Password Authentication failed.



WHY WAS THE PASSWORD CHANGED TO 2. Removed the service and tried it again and I get something different everytime. One time it was P1| I dont see where this comes from. But because of this my service fails with a incorrect password in the dsmerrorlog.



DSMERRORLOG

10/03/2002 09:05:13 ReadPswdFromRegistry(): getRegValue(): Win32 RC=2 .

10/03/2002 09:05:13 ReadPswdFromRegistry(): getRegValue(): Win32 RC=2 .

10/03/2002 09:05:51 sessOpen: Error 137 from signon authentication.

10/03/2002 09:06:07 sessOpen: Error 137 from signon authentication.





ANY ADVICE! :confused: </BLOCKQUOTE></FONT></TD></TR><TR><TD><HR></TD></TR></TABLE> ;)
 
I have 2 nodes and 2 groups. I read in Tivoli's recommendations (within their setup procedure for cluster failover) that the DSM.OPT file should be kept on the drive letter of the group being backed up. In our case we have group Server-A with the DSM.OPT file in the Q: drive and group Server-B with it's DSM.OPT file located on the D: drive.this way when it fails over the Q: and D: drive will fail over to node2 and still have the d=same DSM.OPT file.



We also verified the passsword with the DSMC QUERY SESSION -OPT="Q:\TSM\DSM.OPT" command and it logs in fine. The when we use the dsmcutil showpw /name:"TSM Scheduler: SERVER-A" /optfile:q:\tsm\dsm.opt /node:SERVER-A command it shows an password that we never seen. We even went as far as going to the Node on the TSM Server (GUI) and changed ithe password to reflect what the registry is bringing back.



Lost!







:confused:
 
Gotti,



Please, give me a little bit more information on your situation, please:



1. Node1 name, local drive names

2. Node2 name, local drive names

3. Cluster group 1 name

4. Cluster group 1 shared resource drive names

5. Cluster group 2 name

6. Cluster group 2 shared resource drive names

7. Output of DSMCUTIL L command in Node1 and Node2

8. DSM.OPT contents of each node: Node1, Node2, Cluster Group 1, Cluster Group 2



I will try to make it clear for myself and help you if possible.



Thanx.



Regards,



Alex
 
You must log in or register to reply here.

Data Privacy Impact Assessment

Compliance Assurance in Every Byte: Discover the Impact of Our DPIA Services.

Sponsor ADSM.ORG

If you are reading this, so are your potential customer. Advertise at ADSM.ORG right now.

Navigation Menu

Forums
   IBM TSM
   EMC Backup and Recovery
   Symantec NetBackup  
   SAN  
   NAS
   Platforms / OS
Mailing List Archives
   ADSM-L
User Groups

NordVPN 3 Months FREE

Help Support ADSM.ORG and Get NordVPN with 64% Off and 3 Months FREE.

NordVPN with 64% off + 3 months FREE

Forum statistics

Threads
31,974
Messages
135,447
Members
21,952
Latest member
gatherpc
Back
Top