TSM sysback scheduler on AIX


I want to create a new schedule for our AIXs to make a sysback  backup to TSM. I finally found the tsm sysback licenses and now I can use it on our AIXs.

On the TSM-scheduler I created SYSBACK action type (command)  to execute on AIX side this script:

See image attached.

This script execute 'sysback -ftsm0 -x -u' and I'm not sure this is the right command I should  execute  to make a SYSBACK of rootvg or other VG on AIX? Which do you think is the right command to make this sysback?

If you see there is a parameter on the command above ' -ftsm0 ' which I found is in this place:

[root@lpar2rrd:/] cat /usr/lpp/sysback/tsm/dsm.opt.tsm0

Any, as always, brilliant idea? ;)
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

If you have installed complete Sysback in TSM then first try doiing what you want using SMIT. In this way you can select the choices you want, and then view the command that it is going to execute. You can take that command and execute using "at" or any other scheduler you want.

sorry for the delay, I had to travel around all day and half of the night.


sbtsmdevice -l

to list the TSM virtual devices. I think it will indeed be "tsm0", because there is an opton file containing that string in its name.

"SErvername SYSBACK_LPAR2RRD" in the options file points to a server stanza of that name in dsm.sys. Is there such a stanza?


sbtsmlist -l -n tsm0 -m

If you see your management class bindings then "tsm0" is correct, as well as the TSM access configuration.

The "-x" flag of sysback is useless in a script, because it activates the progress indicator.
Rather use "-v" and redirect the script's output to a logfile.

"-u" is not a valid flag for sysback. "-U" (uppercase U) designates the host to be backed up, which is also useless if you're going to back up the local machine where the script runs on.

All in all, the command to use should just be something like

sysback -v -f tsm0

That's all.

And maybe you should read this:

Good night!


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
sminfoAuthor Commented:
OK Wmp!! That's what I needed... Thanks
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Unix OS

From novice to tech pro — start learning today.