I'm not quite sure I understand what you mean here.

I never set a netware user id to come back in. And I was never required to
do so before.

All I did was set the node, node password and the first time I backup, the
user with rights to backup the system which is the same user on all the
servers....the system admini who has all rights to everything.

Mike

> -----Original Message-----
> From: Cook, Dwight E [SMTP:cookde AT BP DOT COM]
> Sent: ? ??? 27 2000 16:30
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: Netware backup problems on some servers running ADSM
> client V er 3 , Release 1, Level 0.8
>
> Look at the authority of the netware user id you've set up for the adsm
> server to come back in under...
> When YOU push an incremental you are using YOUR authority
> I don't see where you've specified a netware user id for adsm to come back
> in under for scheduled events but check the rights of that id and make
> sure
> it is listed in your option file
>
> Dwight
>
> > ----------
> > From:         Mike Glassman - Admin[SMTP:admin AT IAA.GOV DOT IL]
> > Reply To:     ADSM: Dist Stor Manager
> > Sent:         Monday, March 27, 2000 7:58 AM
> > To:   ADSM-L AT VM.MARIST DOT EDU
> > Subject:      Re: Netware backup problems on some servers running ADSM
> > client V er 3 , Release 1, Level 0.8
> >
> > Mark,
> >
> > As you requested The DSM.OPT is as follows :
> >
> > It's the same on all servers excepting the node name.
> >
> > Mike
> >
> >
> ==========================================================================
> > ==
> > ==================
> >
> > ************************************************************************
> > * 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         172.17.253.21
> >     TCPPORT                  1500
> >
> >
> > *  Setting Options for the IPX/SPX Communication Method
> > *  -------------------------------------------------------
> > *
> > * COMMMETHOD                  IPXSPX
> > *   IPXSERVERADDRESS         ipx_address
> > *   IPXSOCKET                ipx_socket
> >
> >
> > *  Setting Options for the PWSCS Communication Method
> > *  -------------------------------------------------------
> > * COMMMETHOD                 PWScs
> > *   SYMBOLICDESTINATION       server
> > *
> > * COMMMETHOD                 PWSCS
> > *   TPNAME                    server
> > *   PARTNERLUNAME             target_lu
> > *   CPICMODENAME              session_of_target_lu
> > *   CPICBUFFERSIZE            15
> >
> >
> > *  Setting Nodename
> > *  -------------------------------------------------------
> >
> >   NODENAME                  GIS
> >
> >
> > *
> > *  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/.../*
> >   INCLUDE          directory:/.O=IAA/.../*
> > *
> > *  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
> >  EXCLUDE          SYS:\QUEUES\*\*.SRV
> >  EXCLUDE          SYS:\QUEUES\*\*.SYS
> >
> >
> > *  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
> > * NWUSER NS_IAA_GIS\admin:reshet
> >
> > *  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
> > *
> >  PASSWORDACCESS GENERATE
> >  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
> >
> >
> > * Communication Paramaters
> > *--------------------------------------------------------------------
> >  TCPBUFFSIZE    31
> >  TCPWINDOWSIZE  48
> >  TXNBYTELIMIT   2048
> >
> >  SCHEDLOGname   V_VOL1:/ADSMLOG/dsmsched.log
> >  ERRORLOGname   V_VOL1:/ADSMLOG/error.log
> >  SCHEDLOGretention 6 D
> >
> >  SCROLLPrompt   YES
> >  SCROLLLines    20
> >
> >  COMPression    NO
> >
> >  LARGECOMMBUFFERS YES
> >  MEMORYEFFICIENTBACKUP NO
> >
> >
> ==========================================================================
> > ==
> > ==================
> >
> > > -----Original Message-----
> > > From: Remeta, Mark [SMTP:MRemeta AT SELIGMANDATA DOT COM]
> > > Sent: ? ??? 27 2000 15:18
> > > To:   ADSM-L AT VM.MARIST DOT EDU
> > > Subject:      Re: Netware backup problems on some servers running ADSM
> > > client V er 3 , Release 1, Level 0.8
> > >
> > > Mike, why don't you post your dsm.opt file too.
> > >
> > > thanks,
> > > Mark
> > >
> > >
> > > -----Original Message-----
> > > From: Mike Glassman - Admin [mailto:admin AT IAA.GOV DOT IL]
> > > Sent: Sunday, March 26, 2000 5:17 AM
> > > To: ADSM-L AT VM.MARIST DOT EDU
> > > Subject: Netware backup problems on some servers running ADSM client
> Ver
> > > 3 , Release 1, Level 0.8
> > >
> > >
> > > Hi all,
> > >
> > > Sending this a second time, as I didn't get and replies on the first.
> > >
> > > I am having some trouble on some of my Netware 5.0 servers when
> > attempting
> > > to run a Scheduled backup of the server with the above client.
> > >
> > > When running the scheduled backup, I end up with an error 4, and when
> > > looking in the logs, I see that I have no rights to backup the server
> > > specific info, or the volumes.
> > >
> > > The very strange thing is that if I run a manuall INC command using :
> > >
> > > Load DSMC INC -SUB=YES SYS: V_VOL1: V_VOL2:
> > >
> > > on the same server, I manage to backup fine with no errors at all.
> > >
> > > The command that I use to run the Scheduled backup is a simple :
> > >
> > > Load DSMC SCHED -pass=gis
> > >
> > > All servers also run the web based NLM - DSMCAD.NLM which is loaded
> one
> > > line
> > > after the SCHED command line.
> > >
> > > All servers load TSA500 and TSANDS prior to running the schedule
> command
> > > for
> > > backup.
> > >
> > > All servers have 128MB RAM.
> > >
> > > This started about 2 weeks ago, and occurs on 5 out of 13 servers. All
> > > servers run the same SCHED command line, (but with different -pass=
> > names
> > > of
> > > course), and all have the same scheduler set up at 10 minute
> intervals.
> > >
> > > Our ADSM server is an AS400 running Server Version 3, Release 1, Level
> > > 1.7.
> > >
> > > I would appreciate any and all assistance with this as I am at wits
> end
> > > already.
> > >
> > > The errors that appear in the log ar as follows :
> > >
> > > 03/19/2000 14:49:16 --- SCHEDULEREC QUERY BEGIN
> > > 03/19/2000 14:49:16 --- SCHEDULEREC QUERY END
> > > 03/19/2000 14:49:16 Next operation scheduled:
> > > 03/19/2000 14:49:16
> > > ------------------------------------------------------------
> > > 03/19/2000 14:49:16 Schedule Name:         GIS
> > > 03/19/2000 14:49:16 Action:                Incremental
> > > 03/19/2000 14:49:16 Objects:
> > > 03/19/2000 14:49:16 Options:
> > > 03/19/2000 14:49:16 Server Window Start:   21:45:00 on 03/19/2000
> > > 03/19/2000 14:49:16
> > > ------------------------------------------------------------
> > > 03/19/2000 14:49:16 Command will be executed in 7 hours and 9 minutes.
> > > 03/19/2000 14:49:16
> > > Time remaining until execution:
> > > Executing scheduled command now.
> > > 03/19/2000 21:58:16 Node Name: GIS
> > > 03/19/2000 21:58:17 Session established with server ADSM_SYSTEM2:
> AS400
> > > 03/19/2000 21:58:17   Server Version 3, Release 1, Level 1.7
> > > 03/19/2000 21:58:17   Server date/time: 03/19/2000 21:56:33  Last
> > access:
> > > 03/19/2000 14:47:33
> > >
> > > 03/19/2000 21:58:17 --- SCHEDULEREC OBJECT BEGIN GIS 03/19/2000
> 21:45:00
> > > 03/19/2000 21:58:26
> > > Connecting to a NetWare File System (NS_IAA_GIS).
> > >
> > > 03/19/2000 21:58:26
> > > Connected to NS_IAA_GIS.
> > >
> > > 03/19/2000 21:58:35
> > > Connecting to a Novell Directory (T_IAA).
> > >
> > > 03/19/2000 21:58:35
> > > Connected to T_IAA.
> > >
> > > 03/19/2000 21:58:35 Incremental backup of volume 'NS_IAA_GIS\SERVER
> > > SPECIFIC
> > > INFO'
> > > 03/19/2000 21:58:35 Normal File-->         1,048,576 Server Specific
> > > Info/Server Specific Info  ** Unsuccessful **
> > > 03/19/2000 21:58:36 ANS1228E Sending of object 'Server Specific
> > > Info/Server
> > > Specific Info' failed
> > > 03/19/2000 21:58:36 ANS4007E Error processing 'Server Specific
> > Info/Server
> > > Specific Info': access to the object is denied
> > > 03/19/2000 21:58:36 ANS1802E Incremental backup of 'NS_IAA_GIS\SERVER
> > > SPECIFIC INFO' finished with 1 failure
> > >
> > > 03/19/2000 21:58:36 Incremental backup of volume 'NS_IAA_GIS\SYS:'
> > > 03/19/2000 21:58:36 ANS1087E Access to the specified file or directory
> > is
> > > denied
> > > 03/19/2000 21:58:36 Incremental backup of volume 'NS_IAA_GIS\V_VOL1:'
> > > 03/19/2000 21:58:36 ANS1087E Access to the specified file or directory
> > is
> > > denied
> > > 03/19/2000 21:58:36 Incremental backup of volume 'NS_IAA_GIS\V_VOL2:'
> > > 03/19/2000 21:58:36 ANS1087E Access to the specified file or directory
> > is
> > > denied
> > > 03/19/2000 21:58:36 --- SCHEDULEREC OBJECT END GIS 03/19/2000 21:45:00
> > > 03/19/2000 21:58:36 --- SCHEDULEREC STATUS BEGIN GIS 03/19/2000
> 21:45:00
> > > 03/19/2000 21:58:36 Total number of objects inspected:        1
> > > 03/19/2000 21:58:36 Total number of objects backed up:        0
> > > 03/19/2000 21:58:36 Total number of objects updated:          0
> > > 03/19/2000 21:58:36 Total number of objects rebound:          0
> > > 03/19/2000 21:58:36 Total number of objects deleted:          0
> > > 03/19/2000 21:58:36 Total number of objects failed:           1
> > > 03/19/2000 21:58:36 Total number of bytes transferred:        0
> > > 03/19/2000 21:58:36 Data transfer time:                    0.00 sec
> > > 03/19/2000 21:58:36 Network data transfer rate:            0.00 KB/sec
> > > 03/19/2000 21:58:36 Aggregate data transfer rate:          0.00 KB/sec
> > > 03/19/2000 21:58:36 Objects compressed by:                    0%
> > > 03/19/2000 21:58:36 Elapsed processing time:           00:00:18
> > > 03/19/2000 21:58:36 --- SCHEDULEREC STATUS END GIS 03/19/2000 21:45:00
> > > 03/19/2000 21:58:36 ANS1512E Scheduled event 'GIS' failed.  Return
> code
> > =
> > > 4.
> > > 03/19/2000 21:58:36 Sending results for scheduled event 'GIS'.
> > > 03/19/2000 21:58:36 Results sent to server for scheduled event 'GIS'.
> > >
> > > 03/19/2000 21:58:37 ANS1483I Schedule log pruning started.
> > > 03/19/2000 21:58:37 Schedule Log Prune: 916 lines processed.  90 lines
> > > pruned.
> > > 03/19/2000 21:58:37 ANS1484I Schedule log pruning finished
> successfully.
> > > 03/19/2000 21:58:37 Querying server for next scheduled event.
> > > 03/19/2000 21:58:37 Node Name: GIS
> > > 03/19/2000 21:58:37 Session established with server ADSM_SYSTEM2:
> AS400
> > > 03/19/2000 21:58:37   Server Version 3, Release 1, Level 1.7
> > > 03/19/2000 21:58:37   Server date/time: 03/19/2000 21:56:53  Last
> > access:
> > > 03/19/2000 21:56:33
> > >
> > >
> > >
> > > Mike Glassman
> > > System & Security Admin
> > > Israeli Airports Authority
> > > Ben-Gurion Airport
> > > http://www.ben-gurion-airport.co.il
> > >
> > > Tel : 972-3-9710785
> > > Fax : 972-3-9710939
> > > Email : admin AT iaa.gov DOT il
> > >
> > > Usage of this email address or any email address at iaa.gov.il for the
> > > purpose of sales pitches, SPAM or any other such unwanted garbage, is
> > > illegal, and any person, whether corporate or alone doing so, will be
> > > prosecuted to the fullest possible extent.
> >