Re: TSM client on a Netware Cluster
2006-11-30 13:38:03
Hi Timothy,
Here's how we do it on two clusters with 4 and 16 cluster volumes:
TSM on a Netware Cluster
Assumptions:
TSM Clients on NetWare servers already running
Client nodes and schedules for cluster backups defined in TSM
SYS:/ETC/SMS/TSA.CFG has ?Disable Cluster? value set to ?yes?
Up to date on TSAFS and SMS patches
Create a /Tivoli folder in the root of all clustered volumes. This is where the
clustered clients will live.
Copy over every file and folder from SYS:/TIVOLI/TSM/CLIENT/BA (or wherever the
server TSM clients are) to the /Tivoli folder except these:
TSM.PWD
*.log
dsm.opt
Rename the ?DSMCAD.NLM? file to something like ?DSMCAD-CV01.NLM?.
In other words make each cluster node?s DSMCAD unique.
Create a dsm.opt file for the clustered resource. Here?s an example:
******************************************************
* TSM Config file for [ClusterVOL01]
* -------------------------------------------------------
COMMMETHOD TCPIP
TCPSERVERADDRESS tsm01.mrl.ubc.ca
TCPPORT 1500
NODENAME [ClusterVOL01]
HTTPPORT 1611
ERRORLOGRETENTION 7
SCHEDLOGRETENTION 7
MANAGEDSERVICES WEBCLIENT SCHEDULE
DOMAIN [ClusterVOL01]
CLUSTERNODE YES
PASSWORDDIR [ClusterVOL01]:\Tivoli
PASSWORDACCESS GENERATE
NWPWFILE YES
ERRORLOGNAME [ClusterVOL01]:\Tivoli\dsmerror.log
SCHEDLOGNAME [ClusterVOL01]:\Tivoli\dsmsched.log
SCHEDMODE POLLING
NWEXITNLMP NO
*******************************************************
The dsm.opt file should have a different ?HTTPPORT? value for each cluster
resource such as:
[ClusterVOL01] 1611
[ClusterVOL02] 1612
[ClusterVOL03] 1613
[ClusterVOL04] 1614
The ?CLUSTERNODE? value should be ?YES?.
THE ?NWEXITNLMP? value (aka press any key to close) should be ?NO?
We have an account with read rights to all clustered objects and servers (i.e
their OU).
Let?s call it ?backer.users.ourOU?. Use this account with all TSM clients.
Run ?[Path:/to/]dsmc -optfile=[Path:/to/dsm.opt]?
Enter ?q tsa? on command line.
If it asks for a NetWare account and password then use the ?backer? account.
If it doesn?t ask then the output should look like this:
tsm> q tsa
NetWare TSA Information
TSA Name................: [Server_Name]
TSA Module Name.........: TSAFS.NLM
TSA Version.............: 6.57.1
SMDR Version............: 6.57.1
User/Password Location..: [ClusterVOL01]:/TIVOLI/TSM.PWD
User/Password Valid.....: YES
Modify the cluster resource?s load and unload scripts.
Add these entries to the end of the cluster volume?s load script:
delay 5
load [ClusterVOL01]:\tivoli\dsmcad-CV01.nlm
-optfile=[ClusterVOL01]:\tivoli\dsm.opt
Add the entries to the start of the cluster volume?s unload script:
unload dsmagent
unload dsmcad-CV01
delay 2
The ?delay? values may to be tweaked to add more time depending on the nature
of cluster resources.
The above setup means that cluster resource CADs will follow their cluster
object as it loads and unloads. Bad things will most likely happen if you try
and move a clustered resource during a backup so I'd advise against that. But
other than that everything been fine for us.
Andrew Ferris
Network Support Analyst
iCAPTURE Research Centre
University of British Columbia
>>> Timothy Hughes <Timothy.Hughes AT OIT.STATE.NJ DOT US> 11/30/2006 6:57 AM
>>> >>>
Hello,
About 2 years ago we tried unsuccessfully to implement a Novell
Tivoli client Cluster in a Netware environment. We are going to try
to implement this again, Does anyone have a working Novell cluster and
can offer any advice, Tips or dsm.opt file (s) examples of this is
implemented?
Or If there anyone knows where I can get some good documentation
on how to configure the backup-arhive client in a Novell cluster
environment outside of the documentation thats in the Novell client guide it
would be appreciated, From what I understand it would be on 6 cluster
services.
Thanks for any help or advice in advance!
TSM 5.3.4
AIX 5.3
TSM client 5.3
Netware 6.5 SP5
***CONFIDENTIALITY NOTICE***
This electronic message is intended only for the use of the addressee and may
contain information that is privileged and confidential. Any dissemination,
distribution or copying of this communication by unauthorized individuals is
strictly prohibited. If you have received this communication in error, please
notify the sender immediately by reply e-mail and delete the original and all
copies from your system.
|
|
|