Hi Niklas,
This is one way to do it.
We have a two machine solaris (Veritas) cluster and there is a client for each
machine.
We also have a client running for each application in the cluster.
Each application has its own group of filesystems e.g. /p11,/p12,/p13..,/p19
all belong to one application, /p21../p29 all belong to a second application
and so on.
Application code/config is always installed in /px1/app e.g oracle in
/px1/app/oracle, tivoli monitoring in /px1/app/tivoli and so on.
We only have one TSM client install on the box, but for each application the
config files are in /px1/app/tsm
in the dsm.sys for the box we have a stanza for each client. The TCPPORT and
HTTPPORT are incremented for each client e.g.
=====================================================================================
*----------------------------------------------------------------------
* Acceptance Cluster
* QHSU007 and QHSU008 with associated apps
*
SErvername QHSU007
nodename qhsu007
COMMmethod TCPip
TCPServeraddress qhiu008
COMPression Yes
PasswordAccess generate
errorlogname /var/log/dsmerror.log
errorlogretention 7
schedlogname /var/log/dsmsched.log
schedlogretention 7
schedmode prompted
tcpclientaddress qhsu007
postschedulecmd 'su - fred -c "scp -q -B /var/log/dsmsched.log
qhsu009:/dct/tsm/logs/$(hostname)_dsmsched.log"'
* /var/VRTSvcs/log/tmp files often cause spurious errors by disappearing
* before they are backed up. Excluded by SJH 5/3/01
exclude /var/VRTSvcs/log/tmp/*
SErvername QHSU008
nodename qhsu008
COMMmethod TCPip
TCPServeraddress qhiu008
COMPression Yes
PasswordAccess generate
errorlogname /var/log/dsmerror.log
errorlogretention 7
schedlogname /var/log/dsmsched.log
schedlogretention 7
schedmode prompted
tcpclientaddress qhsu008
postschedulecmd 'su - fred -c "scp -q -B /var/log/dsmsched.log
qhsu009:/dct/tsm/logs/$(hostname)_dsmsched.log"'
* /var/VRTSvcs/log/tmp files often cause spurious errors by disappearing
* before they are backed up. Excluded by SJH 5/3/01
exclude /var/VRTSvcs/log/tmp/*
* This stanza is used by an additional dsmc sched process and the opt
* file in /p01/app/tsm/app_dsm.opt to backup the acceptance ottr
* data
SErvername ACC-ORA-OTTR
nodename acc-ora-ottr
COMMmethod TCPip
tcpclientaddress acc-ora-ottr
HTTPPORT 1582
TCPServeraddress qhiu008
TCPWIndowsize 1024
COMPression Yes
PasswordAccess generate
schedmode prompted
errorlogname /p01/app/tsm/dsmerror.log
errorlogretention 7
schedlogname /p01/app/tsm/dsmsched.log
schedlogretention 7
postschedulecmd 'su - fred -c "scp -q -B /p01/app/tsm/dsmsched.log
qhsu009:/dct/tsm/logs/acc-ora-ottr_dsmsched.log"'
* This stanza is used by an additional dsmc sched process and the opt
* file in /a01/app/tsm/app_dsm.opt to backup the acceptance datagate
* data
SErvername ACC-datagate
nodename acc-datagate
COMMmethod TCPip
tcpclientaddress app-egte-test
HTTPPORT 1583
TCPServeraddress qhiu008
TCPWIndowsize 1024
COMPression Yes
PasswordAccess generate
schedmode prompted
errorlogname /a01/app/tsm/dsmerror.log
errorlogretention 7
schedlogname /a01/app/tsm/dsmsched.log
schedlogretention 7
postschedulecmd 'su - fred -c "scp -q -B /a01/app/tsm/dsmsched.log
qhsu009:/dct/tsm/logs/acc-datagate_dsmsched.log"'
SErvername acc-vivas
nodename acc-vivas
COMMmethod TCPip
tcpclientaddress acc-ora-vivas
HTTPPORT 1584
TCPServeraddress qhiu008
TCPWIndowsize 1024
COMPression no
PasswordAccess generate
schedmode prompted
errorlogname /p11/app/tsm/dsmerror.log
errorlogretention 7
schedlogname /p11/app/tsm/dsmsched.log
schedlogretention 7
postschedulecmd 'su - fred -c "scp -q -B /p11/app/tsm/dsmsched.log
qhsu009:/dct/tsm/logs/acc-vivas_dsmsched.log"'
SErvername ORA-PMDB-TEST
nodename ora-pmdb-test
COMMmethod TCPip
tcpclientaddress ora-pmdb-test
HTTPPORT 1585
TCPServeraddress qhiu008
TCPWIndowsize 1024
COMPression Yes
PasswordAccess generate
schedmode prompted
errorlogname /p41/app/tsm/dsmerror.log
errorlogretention 7
schedlogname /p41/app/tsm/dsmsched.log
schedlogretention 7
postschedulecmd 'su - fred -c "scp -q -B /p41/app/tsm/dsmsched.log
qhsu009:/dct/tsm/logs/ora-pmdb-test_dsmsched.log"'
=====================================================================================
The dsmc sched and dsmcad commands are started with
optfile=/px1/app/tsm/app_dsm.opt and this contains for example
SERVERNAME ACC-VIVAS
DOMAIN /p11 /p12 /p13
DATEFORMAT 2
This works fine for us.
the only issue that we have - and this is a cluster problem, not a multiple
client problem - is that client passwords must be set up on both machines and
the password expiry must be set very long, so that the client always works
after a failover.
Hope this helps
Steve Harris
AIX and TSM Admin
Queensland Health, Brisbane Australia
>>> Niklas Lundstrom <niklas.lundstrom AT FORENINGSSPARBANKEN DOT SE>
>>> 19/02/2002 19:36:35 >>>
Hello
Is it possible to install multiple BA-clients on Solaris and how do I do it?
MVH
Niklas Lundström
Föreningssparbanken IT
08-5859 5164
**********************************************************************
This e-mail, including any attachments sent with it, is confidential
and for the sole use of the intended recipient(s). This confidentiality
is not waived or lost if you receive it and you are not the intended
recipient(s), or if it is transmitted/ received in error.
Any unauthorised use, alteration, disclosure, distribution or review
of this e-mail is prohibited. It may be subject to a statutory duty of
confidentiality if it relates to health service matters.
If you are not the intended recipient(s), or if you have received this
e-mail in error, you are asked to immediately notify the sender by
telephone or by return e-mail. You should also delete this e-mail
message and destroy any hard copies produced.
**********************************************************************
|
