Cannot start TSM Scheduler on AIX 6.1

Hello everyone.  I'm in the middle of building a new AIX environment in parallel to our current AIX environment.  I'm currently configurating the backups.  I've already done this on several LPARs without issues, but I'm encountering a strange new problem on two of the LPARs.  I have sysback (Tivoli Storage Manager for System Backup and Recovery) installed on these LPARs.  The dsm.sys and dsm.opt files are correctly configured and I'm able to successfully take manual backups with sysback.  The issue lies in the TSM Scheduler.  I added the following line to /etc/inittab, yet when I do a telinit q (or reboot) the TSM Scheduler won't start.

dsmsched:2:respawn:/usr/tivoli/tsm/client/ba/bin/dsmc sched -quiet >/dev/console 2>&1 #TSM Client Scheduler

This same exact line is in /etc/inittab on my other LPARs and the TSM Scheduler starts fine on those.  But on 2 of my LPARs, it won't start.  No errors received, either.  Does anyone with TSM/AIX experience know what the problem could be?

AIX version 6.1
oslevel: 6100-02
TSM BA client version 5.5
Sysback version 5.6
Need2BaGeekAsked:
Who is Participating?
 
Need2BaGeekAuthor Commented:
Sorry I took so long to reply to this post.  I ended up using crontab to schedule the backups of these servers.  Since the only issue was with starting the TSM scheduler and not with the communication between TSM and the LPAR (and having a million other things to get done) I decided to just paste the sysback command into crontab and schedule it there.  It's been working fine for several months.

Thanks wmp for all your suggestions.  I'm sure they would have helped if I wasn't so busy/impatient.
0
 
woolmilkporcCommented:
Hi,
1) first of all: can you start 'dsmc sched' from the command line?
2) inittab: you should see messages saying '... respawning too rapidly ...' at the console and/or in errpt. Is this the case?
3) dsmadmc: issue 'q actlog node=[yournode] begintime=[HH:MM]' where HH:MM should correspond to the point in time where you issued the 'telinit' (or rebooted). What do you see?
4) sorry for the question: Is 'passwordaccess generate" set in dsm.sys ? Can you start 'dsmc loop' without having to enter your nodename/password?
5) Sorry again: 'managedservices schedule' is not accidentally set?
6) Just to make it complete: Please try redirecting stdin from /dev/null in inittab, and try redirecting stdout/stderr to /dev/null instead of console. In some earlier versions this was mandatory. Perhaps this old bug is back when combining TSM 5.5 and AIX 6.1?
dsmsched:2:respawn:/usr/tivoli/tsm/client/ba/bin/dsmc sched -quiet >/dev/null 2>&1 </dev/null


wmp

0
 
woolmilkporcCommented:
Hi again,
dsmadmc: please try additionally 'q actlog search=[yournode] begintime=[HH:MM]'
btw.: there is not a firewall between your client lpar and the server so that you would need TCPCLIENTADDRESS and TCPCLIENTPORT (and the appropriate firewall config, of course) ??
Anyway, you should see the '...respawning too rapidly ...' thing in your console log, otherwise you have a big problem with inittab, and not with TSM alone.
 wmp
0
 
woolmilkporcCommented:
... one more thing -
afaik sysback uses the API to communicate with the server, and the API can have its own dsm.sys. Please verify that /usr/tivoli/tsm/client/ba/bin/dsm.sys and /usr/tivoli/tsm/client/api/bin64/dsm.sys are identical (or linked).
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.