If you take a look at the startup window of the "immediate" client
action, you will see that polling clients won't start their back-up
anytime soon..
Duration 1 
Duration units DAYS

Change, for this schedule, your schedmode to prompted and the schedule
will be started asap.

Regards,

Karel
 

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Prather, Wanda
Sent: dinsdag 28 december 2004 23:02
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Scheduler problem

Your "queryschedperiod" value appears to be 3 hours.

1) How big is the schedule window?  (i.e., duration)
2) What is your randomization %?

(If they are large, this could be correct behavior..)

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Thomas Denier
Sent: Tuesday, December 28, 2004 4:46 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Scheduler problem


We are in the progress of migrating our TSM clients to a new 5.2.2.0
server running under mainframe Linux. We just migrated an Intel Linux
client system with 5.2.3.0 client software. The client is not responding
to a request to start an incremental backup. The scheduler log on the
client seems to indicate that the client is fully aware of the pending
request but does not see fit to act on the request. The relevant portion
of the client log appears below:

12/28/2004 14:32:42 Querying server for next scheduled event.
12/28/2004 14:32:42 Node Name: RICHMOND
12/28/2004 14:32:42 Session established with server TSMP1: Linux/s390x
12/28/2004 14:32:42   Server Version 5, Release 2, Level 2.0
12/28/2004 14:32:42   Server date/time: 12/28/2004 14:27:55  Last
access:
12/28/2004 14:25:50

12/28/2004 14:32:42 --- SCHEDULEREC QUERY BEGIN
12/28/2004 14:32:42 --- SCHEDULEREC QUERY END
12/28/2004 14:32:42 Next operation scheduled:
12/28/2004 14:32:42
------------------------------------------------------------
12/28/2004 14:32:42 Schedule Name:         @64
12/28/2004 14:32:42 Action:                Incremental
12/28/2004 14:32:42 Objects:
12/28/2004 14:32:42 Options:
12/28/2004 14:32:42 Server Window Start:   13:46:05 on 12/28/2004
12/28/2004 14:32:42
------------------------------------------------------------
12/28/2004 14:32:42 Schedule will be refreshed in 3 hours.

The client has been running successful backups on our old TSM server,
and a number of other clients have been running successful backups on
our new TSM server. The client that is not responding to the central
scheduler is mildly unusual for our site in that it uses polling rather
than prompted scheduling. A 'query node' command with 'f=d' reveals one
oddity which may be related to the problem: the 'Last Communication
Method Used' field is blank.