juandiego13 Absent Member.
Absent Member.
5788 views

OES2 Linux Cluster and TSM

Hello.

I'm looking for some with getting TSM configured in an OES2 Cluster environment. We currently have a two node cluster with 9 resources which provide NSS volumes. We want to be able to backup these resources with TSM. I can't find any documentation on how to configure this. There are several documentation on configuring TSM to run on a Netware cluster (which we are currently doing), but I don't see any information on using TSM to backup the OES2-Linux resources.

It does look like IBM supports OES2 and NSS, but this document [http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/FQ120981] seems vague on the clustering support (since it specific refers to NCS for Netware).

Thanks,
Labels (2)
0 Likes
3 Replies
Anonymous_User Absent Member.
Absent Member.

Re: OES2 Linux Cluster and TSM

juandiego13 wrote:
> Hello.
>
> I'm looking for some with getting TSM configured in an OES2 Cluster
> environment. We currently have a two node cluster with 9 resources
> which provide NSS volumes. We want to be able to backup these
> resources with TSM. I can't find any documentation on how to configure
> this. There are several documentation on configuring TSM to run on a
> Netware cluster (which we are currently doing), but I don't see any
> information on using TSM to backup the OES2-Linux resources.
>
> It does look like IBM supports OES2 and NSS, but this document
> [http://tinyurl.com/38rysw seems vague on the clustering support (since
> it specific refers to NCS for Netware).
>
> Thanks,
>
>


I would also be interested in this as we are about to move to TSM for
all our backups

Lance
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: OES2 Linux Cluster and TSM

After installing tivoli client on cluster's node , copy whole structure
/opt/tivoli to somewhere on resource , which you have backup ,
/media/nss/VOL/tivoli for example . In
/media/nss/VOL/tivoli/tsm/client/ba/bin create two files :
dsm.sys :
------beginning of file dsm.sys----
SErvername tsm_vol
COMMmethod TCPip
TCPPort 1500
TCPServeraddress 10.1.1.1
httpport 1582
NODENAME VOL
COMPRESSION YES
TCPNODELAY YES
TCPBUffsize 512
SCHEDLOGRetention 30
ERRORLOGRetention 30
SCHEDLOGName /media/nss/VOL/tivoli/log/dsmsched.log
ERRORLOGName /media/nss/VOL/tivoli/log/dsmerror.log
SCHEDMODE polling
PASSWORDACCES generate
PASSWORDDIR /media/nss/VOL/tivoli/tsm/client/ba/bin
*USERS root
*MAILPROG /usr/bin/mail admins@novell.com
INCLEXCL
/media/nss/VOL/tivoli/tsm/client/ba/bin/inclexcl.def
DOMAIN /media/nss/VOL
------end of file dsm.sys-----



dsm_vol.opt:
----beginning of file dsm_vol.opt-------
SErvername tsm_vol

DATEFORMAT 2
MEMORYEFFICIENTBACKUP NO
COMPRESSALWAYS NO
------end of file dsm_vol.opt--------

Now create two scripts , one for start dsmc console and second to start|stop
tsm scheduler .

convol (for dsmc console)
------------
#!/bin/bash
export DSM_DIR=/media/nss/VOL/tivoli/tsm/client/ba/bin
export DSM_CONFIG=/media/nss/VOL/tivoli/tsm/client/ba/bin/dsm_vol.opt
$DSM_DIR/dsm
------------


tsmvol (for scheduler)
-------
#!/bin/bash
#
# description: Starting TSM'a

# Source function library.

.. /etc/rc.status


rc_reset
export DSM_DIR=/media/nss/VOL/tivoli/tsm/client/ba/bin
export DSM_CONFIG=/media/nss/VOL/tivoli/tsm/client/ba/bin/dsm_vol.opt


case "$1" in
start)
echo -n "Starting TSM "
$DSM_DIR/dsmc sched >> /dev/null &
if [ $? -ne 0 ];
then
rc_failed
else
$DSM_DIR/dsmcad
if [ $? -ne 0 ];
then
rc_failed
fi
fi
rc_status -v
;;
stop)
echo -n "Stoping TSM "
killproc $DSM_DIR/dsmc
if [ $? -ne 0 ];
then
rc_failed
fi
killproc $DSM_DIR/dsmcad
if [ $? -ne 0 ];
then
rc_failed
fi
rc_status -v
;;
restart)
$0 stop
$0 start
;;
*)
echo "Uzycie: tsm {start|stop|restart}"
exit 1
esac
rc_exit

-------------------------------

After that , create on tsm server client node name VOL , define association
with scheduler .
Run first time :
/media/nss/VOL/tivoli/convol

this create TSM.PWD in /media/nss/VOL/tivoli/tsm/client/ba/bin/

After that , quit from dsmc console and run :
/media/nss/VOL/tivoli/tsmvol start

this start scheduler .

In this example log directory is in: /media/nss/VOL/tivoli/log .

For second volume (VOL1) run again above procedure , change VOL to VOL1 ,
change httpport to another free port .
You can modify load|unload cluster script and add start|stop tsm scheduler
command :
load script add
export DSM_DIR=/media/nss/AGIT/tivoli/tsm/client/ba/bin
export DSM_CONFIG=/media/nss/AGIT/tivoli/tsm/client/ba/bin/dsm_agit.opt
$DSM_DIR/dsmc sched >> /dev/null &
$DSM_DIR/dsmcad

unload script add
.. /opt/novell/ncs/lib/ncsfuncs
export DSM_DIR=/media/nss/AGIT/tivoli/tsm/client/ba/bin
export DSM_CONFIG=/media/nss/AGIT/tivoli/tsm/client/ba/bin/dsm_agit.opt
ignore_error killproc $DSM_DIR/dsmc
ignore_error killproc $DSM_DIR/dsmcad
sleep 8
ignore_error fuser -k $DSM_DIR







>>> On 11 January 2008 at 10:49, in message

<XYGhj.18258$k06.7650@kovat.provo.novell.com>, Lance
Haig<lhaig@NO.haigmail.SPAM.com> wrote:
> juandiego13 wrote:
>> Hello.
>>
>> I'm looking for some with getting TSM configured in an OES2 Cluster
>> environment. We currently have a two node cluster with 9 resources
>> which provide NSS volumes. We want to be able to backup these
>> resources with TSM. I can't find any documentation on how to configure
>> this. There are several documentation on configuring TSM to run on a
>> Netware cluster (which we are currently doing), but I don't see any
>> information on using TSM to backup the OES2-Linux resources.
>>
>> It does look like IBM supports OES2 and NSS, but this document
>> [http://tinyurl.com/38rysw seems vague on the clustering support (since
>> it specific refers to NCS for Netware).
>>
>> Thanks,
>>
>>

>
> I would also be interested in this as we are about to move to TSM for
> all our backups
>
> Lance

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: OES2 Linux Cluster and TSM

Mariusz Michalak wrote:

Thank you this will go into my to keep docs

Lance
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.