The scheduled task does not start, the manual backup will be fine.

[Ston3]

Hi,
I have TSM 2 syslog servers and I would like to add a third one.
I have installed the TSM client according to these instructions:
https://www.shellhacks.com/install-tsm-client-centos-rhel/
So I see a new node on the TSM server.

I copied an existing scheduled task and assigned it to this new node.

But when this scheduled task starts at a given time, I can see this on the server in the log:
10/20/17 09:00:35 ANR0406I Session 63425 started for node SYS_SYSLOG3 (Linux
x86-64) (Tcp/Ip 10.251.231.170(42498)). (SESSION: 63425)

when I write q ses f = d I see an open session:
Sess Comm. Sess Wait Bytes Bytes Sess Platform Client Name Media Access Status User Name Date/Time First Data Sent Proxy By Storage
Number Method State Time Sent Recvd Type Agent
------ ------ ------ ------ ------- ------- ----- -------- -------------------- ---------------------------------------- -------------------- ---------------------------------------- --------------------
63,425 Tcp/Ip IdleW 5.8 M 11.4 K 1.1 K Node Linux SYS_SYSLOG3

After Duration expires:
10/20/17 09:30:01 ANR2578W Schedule SCH_SYSLOG3_HOSTS in domain DO_SYSLOG
for node SYS_SYSLOG3 has missed its scheduled start up
window.
Can I find out what this job is waiting for?

There is nothing on the client side, the /var/log/tsm/client/dsmsched.log file does not exist at all, even though I have it defined in the file "/opt/tivoli/tsm/client/ba/bin/dsm.sys" which I attach to here:
SErvername SYS_SYSLOG3
COMMMethod TCPip
TCPPort 1500
TCPServeraddress 10.251.200.202
TCPclientport 1500
TCPclientaddress 10.251.231.170
NODEName SYS_SYSLOG3
Passwordaccess generate
SCHEDMODE prompted
SCHEDLOGNAME /var/log/tsm/client/dsmsched.log
ERRORLOGNAME /var/log/tsm/client/dsmerror.log
SCHEDLOGRETENTION 365 D
ERRORLOGRETENTION 365 D


I also tried to run the backup process manually:
incremental / var / log / HOSTS / -sub = yes
and it was okay, I can see backups through the command:
q backup
...only the scheduled task does not start.
Please help me.

 

[RecoveryOne]

What release of cent/rhel/oracle/scientific linux are you running?
If its a systemd variant those instructions will not work for starting the dsmcad service. Check out https://www-01.ibm.com/support/docview.wss?uid=swg21976275

 

[LED888]

From the dsm.sys , managedservices is not set. The CAD daemon in not managing the schedule.
Start the schedule daemon in the foreground and see what messages will show up.
If there are no error messages. Define a test schedule, restart the schedule daemon and see if there are any errors. If not use schedmode prompted and see if the results are the same.

Good Luck,
Sias

 

[RecoveryOne]

From the dsm.sys , managedservices is not set. The CAD daemon in not managing the schedule.

Ahh yeah I missed that when I read Ston3's post. Was looking at what was being set in the link he followed.

Starting the scheduler in the foreground will be a big help, I just was thinking it was the dsmcad not coming up with a service dsmcad start command.

 

[Ston3]

What release of cent/rhel/oracle/scientific linux are you running?
If its a systemd variant those instructions will not work for starting the dsmcad service. Check out https://www-01.ibm.com/support/docview.wss?uid=swg21976275

This will be my problem. I have RHEL 7.4.
I will try the procedure in the link.
Thank you all!!

 

[Ston3]

First, I apologize for the stupid question.
but how do I start the process at the forefront?
I tried.
dsmc schedule
Here is the result:
dsmc schedule
IBM Spectrum Protect
Command Line Backup-Archive Client Interface
Client Version 8, Release 1, Level 2.0
Client date/time: 10/23/2017 10:35:39
(c) Copyright by IBM Corporation and other(s) 1990, 2017. All Rights Reserved.

ANS0991I IBM Spectrum Protect scheduler is listening for server requests on port 1500
IBM Spectrum Protect Backup-Archive Client Version 8, Release 1, Level 2.0
Querying server for next scheduled event.
Node Name: SYS_SYSLOG3
Session established with server TSMCMS: Linux/x86_64
Server Version 5, Release 5, Level 2.000
Server date/time: 10/23/2017 10:35:39 Last access: 10/23/2017 10:35:01

Next operation scheduled:
------------------------------------------------------------
Schedule Name: SCH_SYSLOG3_HOSTS
Action: Incremental
Objects: /var/log/HOSTS/
Options: -subdir=yes
Server Window Start: 10:38:00 on 10/23/2017
------------------------------------------------------------
Waiting to be contacted by the server.
but after three minutes nothing happened.

Then I tried to add this to dsm.sys:
managedservices schedule
but then I could not run dsmc schedule:
dsmc schedule
IBM Spectrum Protect
Command Line Backup-Archive Client Interface
Client Version 8, Release 1, Level 2.0
Client date/time: 10/23/2017 10:52:08
(c) Copyright by IBM Corporation and other(s) 1990, 2017. All Rights Reserved.
ANS0991I IBM Spectrum Protect scheduler is listening for server requests on port 1500
ANS0299E Scheduler cannot be started manually because the value of MANAGEDSERVICES option is SCHEDULE.
Scheduler has been stopped.

I found this on my server:
10/23/17 10:45:01 ANR2716E Schedule prompter was not able to contact client
SYS_SYSLOG3 using type 1 (10.251.231.170 35313).
(SESSION: 12)
10/23/17 10:49:01 ANR2578W Schedule SCH_SYSLOG3_HOSTS in domain DO_SYSLOG
for node SYS_SYSLOG3 has missed its scheduled start up
window.

 

[LED888]

Server Version 5, Release 5, Level 2.000

Your running TSM Server 5.5.2 with TSM Client 8.1.2.0 .
FYI: If you call IBM, they will tell you that this is not a supported configuration.
Technically it will still work, but the results are unknown.

Did not notice this earlier, we have tcpclientport set to 1500 rather than the default 1501.
Not sure how many TSM Clients that we have, would use the default port of 1501 or another port other than 1500 for the tcpclientport parameter.

dsmc sched is the proper syntax to start the schedule daemon in the foreground.
If not, would not see the messages that were posted.

From the messages, the schedule daemon is running and its waiting for the server to contact the client to perform the backup.
And we have managedservices schedule set in the dsm.sys file.
Did you define a test schedule? What time did you set the schedule to run?

In the dsm.sys file either remove or comment out the line that have managedservices schedule.
With managedservices schedule set, the CAD daemon will start the schedule daemon.
Which we do not want.
We want to start the schedule daemon in the foreground.

How I test a TSM B/A Client schedule backup.
1. On the TSM Client, stop the schedule daemon .
2. On the TSM Server issue the following on the test schedule, update schedule domain_name schedule_name startdate=today starttime=now+00:01
3. Start the schedule daemon on the TSM Client, the schedule backup should start in 1 minute. Then watch the messages.

NOTE: For the above to work the schedmode need to be set to prompted and managedservices not set.
If the schedmode is set to polling, randomization will be encounter. The TSM Server will then assign a start time.

Good Luck,
Sias

 

[Ston3]

Great, you're the best guy.
I changed TCPclientport to 1501, but I do not know why it works on the original syslog1 and 2.

* managedservices schedule
I canceled the comment back and tried to shift the scheduled task, restarted the dmscad service, and then I saw in the log that the task had started.

Thanks to this amazing discussion forum and thanks to people like you. Thank you, I'm a little smarter again.