Hi all, this is my first post, so I hope I did choose the right forum
My scenario: a two-nodes Windows Server 2003 SP1 Cluster, with a Exchange 2003 SP1 virtual server, a MS Sql 2000 SP4 virtual server and some file share resources. Every single resource has a separated SAN disk resource.
I installed TSM Server 5.3 on another machine, in order to backup the cluster and several other servers/clients. All is running fine, but I've got a nasty problem with the scheduler for the sql resource. For every disk resource (Exchange, MS SQL and file server) I created a generic service resource on the cluster, using the reg key SoftwareIBMADSMCurrentVersionBackupClientNodesNodename ,
after having installed on both nodes the three scheduler services using this command line instruction:
<TABLE BORDER=0 ALIGN=CENTER WIDTH=85%><TR><TD><font class="pn-sub">Code:</font><HR></TD></TR><TR><TD><FONT class="pn-sub"><PRE> dsmcutil install scheduler /name:"tsm scheduler 1" /clientdir:"Crogram filesTivoliTSMBaclient" /optfile:"X:ackup_exchangedsm.opt" /node:nodename /passwordass /validate:no /autostart:yes /startnow:no</PRE></FONT></TD></TR><TR><TD><HR></TD></TR></TABLE>
Scheduler services for the Exchange Resource and for the File server Resource started immediately, receiving the right schedule from the TSM server and they are running smoothly now. The MS Sql one instead, after a few days of right schedules, began to crash!
I can't start the service: after a few seconds in fact it stops suddenly and then it goes in failed state. I'm currently receiving these errors:
Windows Event Log ->
Event 4099 - Adsm Client Service - Scheduler exited with a result code of 12.
Event 4098 - Adsm Client Service - Error Initializing TSM Api, unable to verify Registry Password, see dsierror.log
My Dsmsched.log ->
21-06-2005 15:30:47 Querying server for next scheduled event.
21-06-2005 15:30:47 Node Name: TGSQL
21-06-2005 15:30:47 ANS2050E TSM needs to prompt for the password but cannot prompt because the process is running in the background.
21-06-2005 15:30:47 ANS2050E TSM needs to prompt for the password but cannot prompt because the process is running in the background.
21-06-2005 15:30:47 ANS1029E Communication with the TSM server is lost.
21-06-2005 15:30:47 Scheduler has been stopped.
Here's my dsm.opt
<TABLE BORDER=0 ALIGN=CENTER WIDTH=85%><TR><TD><font class="pn-sub">Code:</font><HR></TD></TR><TR><TD><FONT class="pn-sub"><PRE> NODename Node
CLUSTERnode yes
DOMAIN S:
COMPRESSIon Off
Errorlogname S:Backup_SQLdsmerror.log
Schedlogname S:Backup_SQLdsmsched.log
Errorlogretention 14
Schedlogretention 7
DATEFORMAT 2
COMMMethod TCPip
TCPPort 1500
TCPServeraddress TGTSM
TCPWindowsize 63
TCPBuffSize 32
SCHEDLOGRetention 15 D
SCHEDMODE Prompted
DIRMC MCDIR
</PRE></FONT></TD></TR><TR><TD><HR></TD></TR></TABLE>
I tried to delete the cluster generic service resource, uninstall the scheduler service and then reinstall all, but the result didn't changed :cry: .
I did try also to update the password via command line, but I didn't solve the problem.
The other schedulers are running fine, but I can't fix this one, can someone help me, please?
PS: I am a really tsm newbie!!
PS2: Sorry for my english!!!
My scenario: a two-nodes Windows Server 2003 SP1 Cluster, with a Exchange 2003 SP1 virtual server, a MS Sql 2000 SP4 virtual server and some file share resources. Every single resource has a separated SAN disk resource.
I installed TSM Server 5.3 on another machine, in order to backup the cluster and several other servers/clients. All is running fine, but I've got a nasty problem with the scheduler for the sql resource. For every disk resource (Exchange, MS SQL and file server) I created a generic service resource on the cluster, using the reg key SoftwareIBMADSMCurrentVersionBackupClientNodesNodename ,
after having installed on both nodes the three scheduler services using this command line instruction:
<TABLE BORDER=0 ALIGN=CENTER WIDTH=85%><TR><TD><font class="pn-sub">Code:</font><HR></TD></TR><TR><TD><FONT class="pn-sub"><PRE> dsmcutil install scheduler /name:"tsm scheduler 1" /clientdir:"Crogram filesTivoliTSMBaclient" /optfile:"X:ackup_exchangedsm.opt" /node:nodename /passwordass /validate:no /autostart:yes /startnow:no</PRE></FONT></TD></TR><TR><TD><HR></TD></TR></TABLE>
Scheduler services for the Exchange Resource and for the File server Resource started immediately, receiving the right schedule from the TSM server and they are running smoothly now. The MS Sql one instead, after a few days of right schedules, began to crash!
I can't start the service: after a few seconds in fact it stops suddenly and then it goes in failed state. I'm currently receiving these errors:
Windows Event Log ->
Event 4099 - Adsm Client Service - Scheduler exited with a result code of 12.
Event 4098 - Adsm Client Service - Error Initializing TSM Api, unable to verify Registry Password, see dsierror.log
My Dsmsched.log ->
21-06-2005 15:30:47 Querying server for next scheduled event.
21-06-2005 15:30:47 Node Name: TGSQL
21-06-2005 15:30:47 ANS2050E TSM needs to prompt for the password but cannot prompt because the process is running in the background.
21-06-2005 15:30:47 ANS2050E TSM needs to prompt for the password but cannot prompt because the process is running in the background.
21-06-2005 15:30:47 ANS1029E Communication with the TSM server is lost.
21-06-2005 15:30:47 Scheduler has been stopped.
Here's my dsm.opt
<TABLE BORDER=0 ALIGN=CENTER WIDTH=85%><TR><TD><font class="pn-sub">Code:</font><HR></TD></TR><TR><TD><FONT class="pn-sub"><PRE> NODename Node
CLUSTERnode yes
DOMAIN S:
COMPRESSIon Off
Errorlogname S:Backup_SQLdsmerror.log
Schedlogname S:Backup_SQLdsmsched.log
Errorlogretention 14
Schedlogretention 7
DATEFORMAT 2
COMMMethod TCPip
TCPPort 1500
TCPServeraddress TGTSM
TCPWindowsize 63
TCPBuffSize 32
SCHEDLOGRetention 15 D
SCHEDMODE Prompted
DIRMC MCDIR
</PRE></FONT></TD></TR><TR><TD><HR></TD></TR></TABLE>
I tried to delete the cluster generic service resource, uninstall the scheduler service and then reinstall all, but the result didn't changed :cry: .
I did try also to update the password via command line, but I didn't solve the problem.
The other schedulers are running fine, but I can't fix this one, can someone help me, please?
PS: I am a really tsm newbie!!
PS2: Sorry for my english!!!