ADSM-L

Re: Novell Problems

2000-11-27 15:29:25
Subject: Re: Novell Problems
From: Zoltan Forray/AC/VCU <zforray AT VCU DOT EDU>
Date: Mon, 27 Nov 2000 15:25:25 -0500
I saw this error refered to in the FIXTEST 14 readme.




                    Marc David
                    <marc.david@P        To:     ADSM-L AT VM.MARIST DOT EDU
                    FPC.COM>             cc:
                    Sent by:             Subject:     Novell Problems
                    "ADSM: Dist
                    Stor Manager"
                    <ADSM-L AT VM DOT MA
                    RIST.EDU>


                    11/27/2000
                    02:51 PM
                    Please
                    respond to
                    "ADSM: Dist
                    Stor Manager"






I've  upgraded my older ADSM 3.7 Novell 4.11  clients to TSM 3.7.2  . Most
of the servers work fine but a few Novell servers keep hanging and in the
SYSTEM CONSOLE  this message keeps coming up.

An NLM has been loaded that does not allow  Low Priority Threads to be run.
Low Priority threads are used for file compression, ect.  Set  'Upgrade Low
Priority Threads'  to ON or unload the NLM.

Now first of all I'm not running compression on any of my 12 Novell
Servers.  It's only a couple of servers that giving me problems. At first I
though it was memory but two servers are about 512 Meg of memory,  below is
a copy the the DSM.OPT  file used.


************************************************************************
* ADSTAR Distributed Storage Manager
*
* Sample client options file for ADSM 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 SNA LU 6.2 Communication Method
*  -------------------------------------------------------
*  COMMMETHOD                 SNAlu6.2
*   SYMBOLICDESTINATION       server


*  Setting Options for the TCP/IP Communication Method
*  -------------------------------------------------------
*
   COMMMETHOD                TCPip
    TCPSERVERADDRESS         10.12.3.100
    TCPPORT                  1500


*  Setting Options for the IPX/SPX Communication Method
*  -------------------------------------------------------
*
* COMMMETHOD                  IPXSPX
*   IPXSERVERADDRESS         ipx_address
*   IPXSOCKET                ipx_socket


*  Setting Nodename
*  -------------------------------------------------------

  NODENAME                  BUFFALO


*
*  Recommended exclude list for NetWare
*  -------------------------------------------------------
*
*  NetWare 3.x specific - use the INCR BINDERY or SEL BINDERY
*  command to backup the bindery; exclude the real bindery
*  files:
*  -------------------------------------------------------
* EXCLUDE          sys:\system\net$obj.sys
* EXCLUDE          sys:\system\net$prop.sys
* EXCLUDE          sys:\system\net$val.sys
*
*  NetWare 4.x specific - NDS leaf objects can be included/
*  excluded; container objects are not affected. This example
*  shows how to include only objects in container
*  .OU=Development.O=ADSM
*  ---------------------------------------------------------
* EXCLUDE          directory:/.O=ADSM/.../*
* INCLUDE          directory:/.O=ADSM/.OU=Development.O=ADSM/.../*
*
*  NetWare general excludes
*  ---------------------------------------------------------
 EXCLUDE          sys:\system\secaudit.log
 EXCLUDE          sys:\system\events.log
 EXCLUDE          sys:\system\system.log
 EXCLUDE          sys:\system\btrieve.trn
 EXCLUDE          sys:\system\tsa\tsa$temp.*
 EXCLUDE          sys:\system\sys$log.err
 EXCLUDE          sys:\vol$log.err
 EXCLUDE          sys:\tts$log.err
 INCLUDE          APPS:\...\*
 INCLUDE          HOME1:\...\*
 EXCLUDE          *:\queues\...\*
 exclude          *:\queues\*
 exclude        *:\...\queues\*
 exclude             *:\...\queues\...\*

*  NetWare Screen option
*  ---------------------------------------------------------------
*  The following option instructs the NetWare client to destroy
*  the ADSM screen when quitting the dsmc program.
*
* NWWAIT 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 ADSM.
*
*  If this option is not specified in the client options file, ADSM
*  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), ADSM 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.
*
Verbose quiet
*  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.
*
dirmc      dirmc
schedlogretention 5 d
errorlogretention 10 d
Compression off
Compressa no
TXNBYTELIMIT 25600
tcpbuffsize    32
tcpwindowsize  64
memoryefficientbackup no
passwordaccess generate
nwpwfile  yes
<Prev in Thread] Current Thread [Next in Thread>
  • Novell Problems, Marc David
    • Re: Novell Problems, Zoltan Forray/AC/VCU <=