ADSM-L

Re: Clustered Servers and Tivoli

2006-04-10 20:08:22
Subject: Re: Clustered Servers and Tivoli
From: John Bortscheller <JBortscheller AT SDDPC DOT ORG>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 10 Apr 2006 17:00:22 -0700
Hey Andrew, thanks for the help on this.  What are you using for a node name.  
We were using the server name in this instance SDFP04c but now we are going to 
have our Tivoli Administrator change it to FPCLUSTER_NDPS_SERVER.  Also, below 
I have cut and pasted our opt file.  Anyway you could take a look at it and 
give us suggestions.  Thanks much
 
 
 NODENAME                 FPCLUSTER_NDPS_SERVER
 COMMMETHOD               TCPip
 TCPSERVERADDRESS         10.9.8.196
 TCPBUFFSIZE              512 
 TCPWINDOWSIZE            64
* TCPPORT                  1500
 ERRORLOGR                7
 SCHEDLOGR                7
*  SCHEDMODE                PROMPTED
 PASSWORDACCESS           GENERATE
 PROCESSORUTILIZATION     10
 
 
 NWUSER .cn=gwback.ou=users.ou=em.ou=rc.o=sandiego:conan123
 
***********************************************************************
* Tivoli Storage Manager
*
* Sample client options file for Tivoli Novell NetWare client
************************************************************************
 
   *********************************************************************
   * Copy DSM.SMP (this file) to DSM.OPT.
   *
   * To specify the communication method used between the client node
   * and server.  Select one of the following communication methods
   * by removing the '*'. Fill in NODENAME and this will represent a
   * minimum set of options to get started.
   *
   * You may also exclude some operating system files.  A recommended
   * list is at the bottom of this file.  These files typically are
   * system level files that, even if backed up, could not be properly
   * restored.  If they are restored, they could corrupt the operation
   * of the system.  If you decide to use the list, simply remove the
   * '*'.
   *
   * (for the communication method values, you may have to
   * contact your system administrator)
   *********************************************************************
 
*  Communications settings
*  -------------------------------------------------------
 
*  Setting Options for the TCP/IP Communication Method
*  -------------------------------------------------------
*
 

*  Setting Nodename
*  -------------------------------------------------------
   DOMAIN       ALL
   CLUSTERNODE  YES 
 

*  NDS leaf objects can be included/excluded;
*  container objects are not affected. This example
*  shows how to include only objects in container
*  .O=TIVOLI.OU=Development
*  ---------------------------------------------------------
* EXCLUDE          directory:.O=TIVOLI.*
* INCLUDE          directory:.O=TIVOLI.OU=Development.*
 

*  Recommended exclude list for NetWare
*  -------------------------------------------------------
*
*  NetWare general excludes
*  ---------------------------------------------------------
 
 
 
*  NetWare Memory management option
*  ---------------------------------------------------------------
*  The following option uses a memory conserving algorithm for
*  processing incremental backups as each directory is backed up.
*  This option may increase the duration of time required for
*  backups and increase CPU utilization on the TSM Server.
*  But will decrease the required NetWare memory needed for backups.
*
* MEMORYEFFICIENTBACKUP YES
 
*  NetWare Screen option
*  ---------------------------------------------------------------
*  The following option instructs the NetWare client to destroy
*  the TSM screen when quitting the dsmc program.
*
* NWEXITNLMP NO
 
*  NetWare user ID and password option
*  --------------------------------------------------------------
*  The following option specifies a user ID and password to connect
*  to a local or remote NetWare resource (server or NDS tree). The
*  user ID must have NetWare supervisory equivalence. Use this
*  option for each resource which will be managed by TSM.
*
*  If this option is not specified in the client options file, TSM
*  will check for a user ID and password in an encrypted file (if
*  NWPWFILE is set to YES).  If a correct user ID and password
*  is not found in a file (or NWPWFILE is set to NO), TSM will prompt
*  for a user ID and password when a backup or archive operation
*  is initiated.
*
* NWUSER server_1_name\user:password
* NWUSER server_2_name\user:password
* NWUSER nds_tree_name\user:password
 
*  NetWare user ID and password file
*  --------------------------------------------------------------
*  The following option specifies that the user ID and password used
*  to connect to a NetWare resource (server or NDS tree) will be stored
*  in an encrypted file in the installation directory after the intiial
*  prompt. An encrypted file will be created for each resource with the
*  extension .PWD
*
* NWPWFILE YES
 
*  Silencing screen output
*  -----------------------------------------------------------------
*  Use the QUIET option to keep messages from being displayed on the
*  NetWare console and the schedule log file.  This option will enhance
*  the performance during scheduled backups.
*
*  Note that by using this option, schedule event windows, schedule
*  statistics and errors during schedule processing will still be
*  written to the schedule log file.
*
*  If this option is not specified, the default VERBOSE will be taken.
*
QUIET

 
John Bortscheller
Network Administrator
San Diego Data Processing Corporation
(858) 581-9718
jbortscheller AT sddpc DOT org


>>> AFerris AT MRL.UBC DOT CA 4/10/2006 4:42:57 PM >>>

Oh and one more thing. You'll want to edit Sys:/ETC/SMS/TSA.cfg file and change 
the Disable Cluster value to "yes" from no. Then you will have to start and 
stop SMS. That will also block cluster node visibility. 

Andrew Ferris
Network Support Analyst
iCAPTURE Research Centre
University of British Columbia 

<Prev in Thread] Current Thread [Next in Thread>