missed schedules

[pichi]

Hi everybody ,
i have a prblem with TSM software,
i have 2000 and 2003 windows servers..
my tsm server is windows2003 server
my clients 2000 and 2003 servers..
versions
server: 5.3.5
client: 5.3.4 (windows server 2003) or 5.3.5 (windows server 2000)
(i have tried in 2 servers with diff versions).

My problem is:
when i schedule a backup, and query the event with (q event * * ) i get this:
schedule start: 10/08/2007 11:42
actual start:
schedule name: srv07name
node name: srv07name
status: Future

when i execute
> q sched
on the console at the client i get this result:

IBM Tivoli Storage Manager
Command Line Backup/Archive Client Interface
Client Version 5, Release 3, Level 4.0
Client date/time: 10/08/2007 11:41:19
(c) Copyright by IBM Corporation and other(s) 1990, 2006. All Rights Reserved.

Node Name: SRV07name
Session established with server SRV09_SERVER1: Windows
Server Version 5, Release 3, Level 5.0
Server date/time: 10/08/2007 11:41:20 Last access: 10/08/2007 11:39:04

tsm> q sched
Schedule Name: SRV07name
Description:
Schedule Style: Classic
Action: Incremental
Options:
Objects:
Priority: 5
Next Execution: 1 Minute
Duration: 30 Minutes
Period: One Time
Day of Week: Weekday
Month:
Day of Month:
Week of Month:
Expire: Never

tsm>

when the schedule should have start.. i get this in the command line at the server:

Status: Pending...

and after the start window (duration) has finish..

Status: Missed...


if i use the TSM GUI client at the client, i can communicate with the server..
i can backup some files.. but manually.. i haven´t tried schedule a backup at the client..
but i think it may work.. but i need the server schedule to work.. because i have a lots of
servers... and i'll use cloptset.. etc etc..

Hope somebody can help me.. thanks in advance..

Pichi

 

[TSch]

Hi there,

do you have any output in dsmsched.log and dsmerror.log ?

Regards
Thomas

 

[pichi]

Hi, no, there isn't information in the logs...
that's why i don't know where the problem is...
thanks in advance..

Pichi

 

[pichi]

hi, the dsmerror.log is createad but doesn´t register information about the schedule,, only information if i execute a wrong commando..
and the dsmsched.log is not created... i don't know why.. i created manually, but also doesn´t register anything... maybe that's the problem... i don't know..
help will be apreciated...

Pichi

 

[TSch]

Hi,

be sure to do a "chmod 777 dsmsched.log" just to make sure it is accessable for all users.

Are there any entries in the actlog (q act) of the TSM server at the time the schedule is supposed to run ?

Regards
Thomas

 

[pichi]

Hi, remember is windows, so chmod is not permited.. but the file doesn't exist.. i created it manually but also no data was register... (with the right permissions).
About "q act", the only thing the tsm server registers is the execution of the command "q act" nothing else..

Pichi

 

[ProbablyDown]

your TSM scheduler service is running on the windows client?

 

[pichi]

I think it is.. but how could i confirm that? what windows process is? ...
thanks in advance..

Pichi

 

[TSch]

As far as I know the "TSM Client Acceptor" service should be started on your Client ...

 

[mbourne2006]

Hi

Take a look at :

dsmcutil help

run from the BAclient directory

You can use this to list Windows TSM services and run queries against them.

HTH

Have Fun !
Matthew Bourne
"Find a job you love and never do a day's work in your life.

 

[pichi]

hi to all, i resolve my problem...
i run the wizard and configure the scheduler service... and now is working..
thanks to everyone..

Pichi