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/ti
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
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
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
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.
Business Accounts
Answer for Membership
by: woolmilkporcPosted on 2009-05-05 at 12:16:08ID: 24308128
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:/us
wmp