Lost encryption keys in unix tsm client with two schedulers

[Josep]

In all our aix/linux boxes with two tsm schedulers encryption key is lost after reboot.

We have configured with "encryptkey save" in dsm.sys.

We have configured our schedulers to start like this:

AIX (in etc/inittab):
tsmw:nce:/usr/tivoli/tsm/client/ba/bin/dsmc sched >/dev/null 2>&1
tsmwo:nce:/usr/tivoli/tsm/client/ba/bin/dsmc sched -optfile=/usr/tivoli/tsm/client/ba/bin/dsmo.opt -servername=TSMDIPCAS_ora >/dev/null 2>&1

Linux (in rc.local):
export DSM_CONFIG=/opt/tivoli/tsm/client/ba/bin/dsm.opt
/opt/tivoli/tsm/client/ba/bin/dsmc sched > /dev/null &
export DSM_CONFIG=/opt/tivoli/tsm/client/ba/bin/dsmo.opt
/opt/tivoli/tsm/client/ba/bin/dsmc sched -servername=TSMDIPCAS_ora > /dev/null &

Anybody know other way to start two schedulers or have same trouble?

 

[moon-buddy]

For AIX:

(Note: there is NO space between tsmcad:2: and once - cannot eliminate the emoticon from showing without the space)

tsmcad:2: once:/usr/tivoli/tsm/client/ba/bin/dsmcad >/dev/null 2>&1 # TSM Client Acceptor Service

tdpcad:2: once:/usr/tivoli/tsm/client/ba/bin/dsmcad -optfile=/usr/tivoli/tsm/client/ba/bin/dsm.tdp.opt >/dev/null 2>&1 # TDP Client Acceptor Service

For Linux (RedHat) in /etc/init.d as script called dsmsvc or any name you want to call it:

#!/bin/sh
#
# chkconfig: - 91 35
# description: Starts and stops TSM client acceptor daemon
#
#Source function library.
. /etc/rc.d/init.d/functions

[ -f /opt/tivoli/tsm/client/ba/bin/dsmc ] || exit 0
[ -f /opt/tivoli/tsm/client/ba/bin/dsmcad ] || exit 0

prog="dsmcad"

export DSM_DIR=/opt/tivoli/tsm/client/ba/bin
export DSM_CONFIG=/opt/tivoli/tsm/client/ba/bin/dsm.opt

start() {
echo -n $"Starting $prog: "
cd $DSM_DIR
daemon $DSM_DIR/dsmc sched >/dev/null 2>&1 &
daemon $DSM_DIR/dsmc sched -se=TDPSERV >/dev/null 2>&1 &
daemon $DSM_DIR/dsmcad
RETVAL=$?
[ $RETVAL -eq 0 ] && touch /var/lock/subsys/dsmcad
return $RETVAL
}

stop() {
if test "x`pidof dsmcad`" != x; then
echo -n $"Stopping $prog: "
killproc dsmcad
fi
if test "x`pidof dsmc`" != x; then
echo -n $"Stopping $prog: "
killproc dsmc
echo
fi
RETVAL=$?
[ $RETVAL -eq 0 ] && rm -f /var/lock/subsys/dsmcad || rm -f /var/lock/subsys/dsmc
return $RETVAL
}

case "$1" in
start)
start
;;

stop)
stop
;;

status)
status dsmcad
;;
restart)
stop
start
;;
condrestart)
if test "x`pidof dsmcad`" != x; then
stop
start
fi
;;

*)
echo $"Usage: $0 {start|stop|restart|condrestart|status}"
exit 1

esac

exit 0

 

[Josep]

Thanks moon-buddy for answer but I need two DSM_CONFIG variables beacause my second scheduler is not a TDP is just another file based sheduler.

The main question in my post is not the way to start TSM-client services, is: is the tsm client inability to remember two encryption keys for the two tsm-nodes that ar defined on the same box.

regards

 

[Josep]

The solution is...

TSM support help me to find the solution:

As you know, tsm client save their passwords (pass to access the server and pass for encryption) in TSM.PWD file (in /etc/adsm/ forlder in linux, in /etc/secuity/adsm in aix).

The solution is to let the first scheduler to use the default TSM.PWD file for password storage, and use this entry in dsm.sys options file:
passworddir
to teach second scheduler to store their passwords in alternate file (folder).

Bye.