CAD service logging repeatedly during backups?

opeth

ADSM.ORG Member
Joined
Feb 3, 2016
Messages
81
Reaction score
1
Points
0
PREDATAR Control23

Have an odd issue that I am sure has a simple solution.
I have a Linux client that during its backup windows the CAD services appears to continuously poll the TSM server, and log the action creating a huge log file. It starts when the scheduler cranks up and continues till 8am then stops.
Any ideas?
 
PREDATAR Control23

I have a Linux client that during its backup windows the CAD services appears to continuously poll the TSM server, and log the action creating a huge log file.
What type of info is it logging? In which file do you see that?
 
PREDATAR Control23

06/01/2017 22:16:28 TSM Backup-Archive Client Version 6, Release 3, Level 0.5 


06/01/2017 22:16:28 Querying server for next scheduled event. 

06/01/2017 22:16:28 Node Name: XXXXXXXXXXX

06/01/2017 22:16:28 Session established with server TSM01: Windows 

06/01/2017 22:16:28 Server Version 7, Release 1, Level 6.0 

06/01/2017 22:16:28 Data compression forced off by the server 

06/01/2017 22:16:28 Server date/time: 06/01/2017 22:16:27 Last access: 06/01/2017 22:11:43 

06/01/2017 22:16:28 --- SCHEDULEREC QUERY BEGIN 

06/01/2017 22:16:28 --- SCHEDULEREC QUERY END 

06/01/2017 22:16:28 Next operation scheduled: 

06/01/2017 22:16:28 ------------------------------------------------------------ 

06/01/2017 22:16:28 Schedule Name:XXXXXXXXX_INCR 

06/01/2017 22:16:28 Action: Incremental 

06/01/2017 22:16:28 Objects: 

06/01/2017 22:16:28 Options: 

06/01/2017 22:16:28 Server Window Start: 20:00:00 on 06/02/2017 

06/01/2017 22:16:28 ------------------------------------------------------------ 

06/01/2017 22:16:28 Scheduler has been stopped. 

. 

. 

. 

. 

06/02/2017 08:09:37 Scheduler has been started by Dsmcad. 

06/02/2017 08:09:37 TSM Backup-Archive Client Version 6, Release 3, Level 0.5 

06/02/2017 08:09:37 Querying server for next scheduled event. 

06/02/2017 08:09:37 Node Name: XXXXXXXX

06/02/2017 08:09:37 Session established with server XXXXXXXX: Windows 

06/02/2017 08:09:37 Server Version 7, Release 1, Level 6.0 

06/02/2017 08:09:37 Data compression forced off by the server 

06/02/2017 08:09:37 Server date/time: 06/02/2017 08:09:36 Last access: 06/02/2017 08:09:04 

06/02/2017 08:09:37 --- SCHEDULEREC QUERY BEGIN 

06/02/2017 08:09:37 --- SCHEDULEREC QUERY END 

06/02/2017 08:09:37 Next operation scheduled: 

06/02/2017 08:09:37 ------------------------------------------------------------ 

06/02/2017 08:09:37 Schedule Name: XXXXXXXXX_INCR 

06/02/2017 08:09:37 Action: Incremental 

06/02/2017 08:09:37 Objects: 

06/02/2017 08:09:37 Options: 

06/02/2017 08:09:37 Server Window Start: 20:00:00 on 06/02/2017 

06/02/2017 08:09:37 ------------------------------------------------------------ 

06/02/2017 08:09:37 Scheduler has been stopped.
 
PREDATAR Control23

What's the queryschedperiod set at? You can check using:

dsmc query option queryschedperiod
 
PREDATAR Control23

Set to 12
I am lost, i cant seem to figure out why its doing this
 
PREDATAR Control23

The scheduler queries the server every time CAD starts it.
CAD starts the scheduler when CAD starts, and repeats every QUERYSCHEDPERIOD.

Check to see if CAD is restarted often, you can use this command to see how often CAD is started/restarted:
cd /opt/tivoli/tsm/client/ba/bin
grep "Dsmcad is working in" dsmwebcl.log
 
PREDATAR Control23

I only see "Dsmcad is working in" occurring once last week:
06/07/2017 11:53:36 (dsmcad) Dsmcad is working in Webclient Schedule mode.

no occurrence after that
 
PREDATAR Control23

And how often does the scheduler query the server? In your earlier post, I see once in the evening and once in the morning, I'm suspecting there may be more between those 2 instances?

grep "Querying server for next scheduled event" dsmsched.log
 
PREDATAR Control23

It dots in between were to represent repeating, it does it over and over that is the problem
 
PREDATAR Control23

Looks like every 30 seconds till about 8am
 
PREDATAR Control23

Check dsmwebcl.log, just in case there are errors reported for CAD which would cause it to keep waking up the scheduler.

Also, it would be worth while to upgrade that client to 7.1.6 (or 8.1.0), just in case it's a defect. It would also bring you back into a support release.
 
PREDATAR Control23

This still continues, and I have recreated it by pointing more Linux clients to the new server. It has to be something related to the configuration on the new TSM server. Nothing on the clients changed except the server name in the dsm file and restarting the cad service.
 
PREDATAR Control23

Correction, windows clients are doing it as well
 
PREDATAR Control23

Compare your two servers then, look at
Q STATUS
Q OPTION
Q SCHEDULES F=D
 
PREDATAR Control23

I went through that, I even did a export server to the new tsm server. I guess I need to open a ticket with IBM, just seems like this should be something simple.
 
PREDATAR Control23

For whatever reason, upgrading the server to 8.1.1 resolved this. No settings changed at all.
Very strange.
 
Top