WARNING: Long append
I have just placed the Release 1 Version 2 Level 8 NetWare ADSM client
on the FTP server, index.storsys.ibm.com, in the adsm/incoming directory.
The file name is nov20396.3d1.
It is not the official version, but it's close. We will be system testing
it for just a few more days. The main fixes in this level address large
file space processing. Both performance and processor utilization
problems are addressed. ie, larger buffers for memory allocation, more
ThreadSwitches, etc.
I would appreciate any feedback your time schedules allow
before we release it. Thanks!
I've included the read.me file below.
Regards,
Frank Ramke
-----------------------------------------------------------------
ADSTAR Distributed Storage Manager Novell NetWare client READ.ME
ADSTAR Distributed Storage Manager Novell NetWare client READ.ME
Version 1, Release 2, Level 0.8
IP20396
=================================================================
This readme contains updated information that did not make our
printed publications. It is divided into the following categories.
o New Information
o Installation
o Limitations
o Document Updates
o General Information
o Fixes
=================================================================
=================================================================
New Information:
Memory.
This package updates how DSMC.NLM allocates memory. The
memory for larger memory operations now will be allocated
from the large memory pool. This memory is returned to
the system for file caching. SLOWINCREMENTAL is still
advised for the incremental backups, but the memory
allocation was changed to use the large memory pool
for backup as well.
Processor Utilization.
If your processor utilization goes too high during backup or
restore processing, check to see if tracing is active by
editing the dsm.opt file and look for a TRACEFLAGS or TF
entry. Comment out this entry with an asterisk. Tracing
can cause ADSM to use too much of the processor.
Performance.
This PTF has a new option that may prove benificial in certain
instances. The option ProcessorUtilization, can be used
to tell ADSM how often to ThreadSwitch. Since NetWare
is non-preemptive, the ThreadSwitch call is how an NLM releases
control of the processor. The parameter to the ProcessorUtilization
option tells ADSM how often to call threadswitch. The number
is based on NetWare ticks, so 1 would instruct ADSM to not
threadSwitch if a threadSwitch had been made less than 1/100 second
ago. If you specify 0, ADSM will threadSwitch every time.
This will be most useful during file compression, as this
is very processor intensive.
Example:
PROCESSORUTILization 0
will use the CPU the least.
PROCESSORUTILization 1000
will use the CPU the most.
(1 is the default)
TCPIP timeouts.
TCPIP problem:
Novell has uplifted a new TCPIP package onto NetWire. This fixes
a problem many ADSM users have reported. The problem manifest itself
as a communication loss with the ADSM server. If you begin a backup
and get a loss of connection, get the Novell fix TCP188.EXE from NetWire.
There is still a known problem with this package. We are not
seeing the TCPIP window size higher than 3 or 4k. Novell is aware
of this limitation, and is working on the resolution. I am told
that the TCPIP.NLM for 4.1 can go up to 16k.
ADSM Screen problems.
If your having trouble with the ADSM screen not going away after
stoping the NetWare client. Put NWWAIT NO in the dsm.opt file.
This will cause the ADSM screen to be destroyed after your finished
with the program.
SMS modules.
New TSA MODULES:
A few of the names of the SMS modules from Novell have changed.
You may need to update your autoexec.ncf file. For instance,
the TSA's on all platforms now share a common SMDR.NLM. The
TSA's autoload the correct version. If you use the new ones,
they all load SMDR.NLM. All underscores have been removed
from the workstation TSA's.
For 3.11 Servers the SMS modules should have these dates/revisions.
TSA311.NLM
4.02f June 21, 1994
SMDR.NLM
3.12b May 17, 1994
IMPORTANT NOTICE:
This version contains refreshed versions of the Novell SMS modules. These
modules will not load correctly if your CLIB.NLM is down level. The
Reason is that Novell has made SMDR (Storage Management Data Requestor)
the same on all operating systems, SMDR.NLM. ADSM interacts with SMDR.NLM
and the TSA for all file IO on your NetWare system.
NetWare v3.1x users should have CLIB.NLM version 3.12g or higher
NetWare 4.x users should have CLIB.NLM version 4.01e or higher
To obtain these fixes, obtain the latest LIBUPn package from NetWire.
If the CLIB.NLM is not at a current level, you will see the following
errors when trying to load SMDR.NLM on a 3.11 server:
Loader cannot find public symbol: ThreadSwitchWithDelay
Loader cannot find public symbol: ImportSymbol
Load file referenced undefined public variable.
Module SMDR.NLM NOT loaded
The new SMS modules resolve the problem documented by IBM APAR IC07951;
external messages for this problem are as follows:
DSMC.NLM reports:
ANS4031S Internal program error.
NetWare console reports:
TSA311 1.0 272 the program was processing a record or subrecord
and did not find the trailer field.
If you've already updated the SMS modules, the ADSM
install program has made a backup copy of the old
module for you. The modules are in the SYS:\SYSTEM
subdirectory. ADSM will run with the older SMS version
(v4.01b), but the newer SMS modules are recommended.
The precise package names that are known to update the
OS to the now needed levels are:
1) STRTL3.EXE
2) LIBUP3.EXE
note: a newer LIBUP4.EXE package is now available.
MODULE DEPENDENCIES
SMS is dependent on the modules listed below. Novell
recommends that you upgrade to the following versions of
these modules or later (NOTE the actual released modules
may have dates that differ from those listed):
3.x
after311.nlm 1-07-94 14411
a3112.nlm 1-07-94 11371
clib.nlm 2-24-94 328124
spxs.nlm 9-14-93
streams.nlm 7-20-93
tli.nlm 9-14-93
4.x
clib.nlm 2-24-94 202021
spxs.nlm 3-02-94
streams.nlm 9-14-93
tli.nlm 9-14-93
dsapi.nlm 2-25-94 43389
=================================================================
Installation:
To install ADSM, please use the instdsm nlm. Put the disk
into your server's A: drive. Enter "LOAD A:INSTDSM" from
the server's console prompt.
Copy dsm.smp to dsm.opt and edit dsm.opt. Dsm.opt is the options
file which must be tailored. You can find out what needs to go
in here from your ADSM server administrator. A list of all valid
options for NetWare with examples can be found by editing
the file options.doc.
Now, at the NetWare console prompt enter "SEARCH ADD SYS:ADSM".
You can now type "DSMC", which invokes the client in 'loop' mode.
Or simply type LOAD DSMC.
The "Install SMS Modules" option can be chosen to install the
SMS modules. Do this if there is a problem connecting to the
server's TSA. The installation program is sensitive to which
server it's running on. That is, it will install the 3.11
TSAs if running on a 3.11 server, and the 4.01 TSAs if running
on a 4.01 server and 3.12 TSAs if running on 3.12.
=================================================================
Limitations:
July 20, 1994
IPXSPX on 3.11, 3.12, 4.01, and 4.02
You need to apply a ptf from Novell called STRTL3. This fix
is available from CompuServe. STRTL3 is also needed for the
new SMS modules. It has fixes for SPX2.NLM, STREAMS.NLM, and
others. It is located in "go novlib" lib1.
Other helpful "hints" for running IPXSPX to an OS/2 server.
1) Set the commtimeout parameter high in dsmserv.opt.
COMMTIMEOUT 600
2) If an OS/2 ADSM server, look at the file net.cfg. Add a
stanza for protocol stack spx with the following numbers:
protocol stack spx
abort timeout 300000 <---------+
verify timeout 300000 |-keep these numbers same ratio
listen timeout 600000 <---------+
retry count 255
3) in dsmserv.opt "ipxbuff=1"
4) Install strtl2 on the NetWare server. It's available on Compuserve
send us a note and we'll e-mail it to you.
5) in dsm.opt "ipxbuff=1"
=================================================================
General Information:
To backup the NetWare Directory Services, you have to LOAD TSANDS.
To back up the directory issue "load dsmc sel dir". You can
also back up just parts of the directory. However, you have to be
careful that you enter the name of the object in the directory
correctly. "load dsmc sel dir\.cn=admin.o=ibm.c=usa" will back up
the userid admin in the organizational unit ibm, in the country usa.
You can also back up containers in the directory. You can
think of containers as directories. They are directories of objects.
For instance, "load dsmc sel dir\.o=ibm.c=usa" will back up all the
objects in the "directory" ibm in the country usa.
The above object ".cn=admin.c=us.o=ibm" will have the following
name in the ADSM server's catalogue "/.C=US/.O=IBM.C=US/.CN=ADMIN.O=IBM.C=US"
This is due to NDS using reverse order for directory objects.
But, you can just enter "load dsmc res dir\.cn=admin.o=ibm.c=usa"
to restore the object.
Let's say that you have been running incrementals on the directory.
A userid may have been deleted from the directory tree last week,
but now you find that you need to add it back. Since incrementals
have been running, chances are the user object, a .cn name, is
now inactive. You can restore that user by using the inactive switch
on the restore. You can also restore the whole container he was in.
EXAMPLE:
dsmc> rest dir/.cn=admin.o=ibm.c=us -inactive
or
dsmc> rest dir/.o=ibm -sub=yes
The latter example will restore the entire organization IBM!
=================================================================
Document Updates:
Limiting size of log files
-----------------------------------------------------------------------
Support has been added to limit the sizes of the ADSM schedule and error log
Support has been added to limit the sizes of the ADSM schedule and error log
files. The error log files will only retain entries for a specified number
of days. The two new options to 'prune' log files are SCHEDLOGRETENTION
and ERRORLOGRETENTION:
SCHEDLOGRetention <days>(,<Save>)
SCHEDLOGRet specifies the number of days to keep log file entries
from the Schedule log and whether or not to save these 'pruned'
entries. Values from 0 to 9999 or 'N'o are allowed for the number
of days. The default is not to prune any entries (logs will grow
indefinitely). The second parameter on SCHEDLOGRet specifies whether
or not to save pruned entries. 'S' or 's' specifies to save the
pruned entries, any other value will cause pruned entries to be
discarded. Pruned entries when saved are saved to the file
DSMSCHED.PRU. A space or comma must separate the parameters.
ERRORLOGRetention <days>(,<Save>)
ERRORLOGRet specifies the number of days to keep log file entries
from the Error log and whether or not to save these 'pruned'
entries. Values from 0 to 9999 or 'N'o are allowed for the number
of days. The default is not to prune any entries (logs will grow
indefinitely). The second parameter on ERRORLOGRet specifies whether
or not to save pruned entries. 'S' or 's' specifies to save the
pruned entries, any other value will cause pruned entries to be
discarded. Pruned entries when saved are saved to the file
DSMERLOG.PRU. A space or comma must separate the parameters.
============================================================================
MACRO <macroname>
-----------------
Use the dsmc MACRO command to issue a series of valid ADSM backup
Use the dsmc MACRO command to issue a series of valid ADSM backup
commands as specified in a named macro file.
SYNTAX
Macro macroname
where macroname is the name of a file containing valid ADSM backup
command line commands.
Commands may be nested to a maximum of 10 levels. It is permissable to
include the MACRO command within a macro file.
This command can be executed in either batch mode or interactive mode.
=========================================================================
REPlace <all>
-------------
A new parameter value has been added to the -replace= command line and
A new parameter value has been added to the -replace= command line and
replace option-file option. This new parameter will allow the client to
restore or retrieve all files in a file-space whether they are read-only
or not. This is intended to be an unattended restore option allowing read
only files to be restored without prompting the user. If for some reason
the file still cannot be restored or retrieved (it be open by another user
on the system), an error will be logged.
Example:
From the command line: dsmc rest x:* -replace=all
will not prompt the user to restore any files including read-only
Within the DSM.OPT file: replace all
========================================================================
Tapeprompt
----------
The default for tapeprompt is tapeprompt=yes. This was not
The default for tapeprompt is tapeprompt=yes. This was not
working as documented for the command line client until
ptf# IP20198. After installation of ptf# IP20198 (and later),
you will be prompted if a tapemount is required for backup,
archive retrieve or restore unless tapeprompt=no is specified.
Tape prompting will now not occur when running the scheduler,
no matter what the tapeprompt option is set to.
=====================================================================
New Messages
------------------------------------------------------------------------
ANS4995E *** VOLINFO IS NOT A VALID OPTION FOR THIS OPERATION.
ANS4995E *** VOLINFO IS NOT A VALID OPTION FOR THIS OPERATION.
EXPLANATION: Unable to back up volume information.
SYSTEM ACTION: ADSM canceled volinfo backup attempt.
USER RESPONSE: Use the volinformation option when using the selective
or restore command while backing up a NetWare volume.
------------------------------------------------------------------------
ANS4410E UNABLE TO ACCESS THE NETWORK PATH
ANS4410E UNABLE TO ACCESS THE NETWORK PATH
EXPLANATION: The network path cannot be accessed due to a possible
network problem.
SYSTEM ACTION: The client terminates.
USER RESPONSE: Ensure that the network is up and the path can be
accessed using a system command, and retry the operation.
-----------------------------------------------------------------------
ANS4411E A COMMUNICATION SESSION WAS DROPPED
ANS4411E A COMMUNICATION SESSION WAS DROPPED
EXPLANATION: A communication session was dropped due to a possible
network problem.
SYSTEM ACTION: The client terminates.
USER RESPONSE: Ensure that the network is up and retry the operation.
-----------------------------------------------------------------------
ANS4184E MAXIMUM MACRO NESTING LEVEL EXCEEDED
ANS4184E MAXIMUM MACRO NESTING LEVEL EXCEEDED
EXPLANATION: Too many levels of macro nesting are encountered.
SYSTEM ACTION: The macro is ignored and an error is returned.
USER RESPONSE: Reduce the level of macro nesting.
-----------------------------------------------------------------------
ANS4185E MACRO FILE 'filespec' COULD NOT BE OPENED
ANS4185E MACRO FILE 'filespec' COULD NOT BE OPENED
EXPLANATION: A macro command has been entered that specifies the macro
file name shown. However, that file cannot be opened for reading.
SYSTEM ACTION: The macro is ignored and an error is returned.
USER RESPONSE: Reissue the command with the proper macro name.
-----------------------------------------------------------------------
ANS4230E STALE NFS FILE HANDLE
ANS4230E STALE NFS FILE HANDLE
EXPLANATION: An NFS file system became stale.
SYSTEM ACTION: File system skipped.
USER RESPONSE: Check the NFS mounted filesystem.
-----------------------------------------------------------------------
ANS4483I SCHEDULE LOG PRUNING STARTED.
ANS4483I SCHEDULE LOG PRUNING STARTED.
EXPLANATION: The schedule log pruning function has begun.
SYSTEM ACTION: The schedule log is pruned.
USER RESPONSE: None.
-----------------------------------------------------------------------
ANS4484I SCHEDULE LOG PRUNING FINISHED SUCCESSFULLY.
ANS4484I SCHEDULE LOG PRUNING FINISHED SUCCESSFULLY.
EXPLANATION: The schedule log pruning function completed with no
errors.
SYSTEM ACTION: None.
USER RESPONSE: None.
-----------------------------------------------------------------------
ANS4485E SCHEDULE LOG PRUNING FAILED.
ANS4485E SCHEDULE LOG PRUNING FAILED.
EXPLANATION: The schedule log pruning function failed.
SYSTEM ACTION: The schedule log pruning function stops.
USER RESPONSE: Retry the command with the tracing turned on to help
determine why the pruning function failed.
-----------------------------------------------------------------------
ANS4932I ERROR LOG PRUNING STARTED.
ANS4932I ERROR LOG PRUNING STARTED.
EXPLANATION: The error log pruning function has begun.
SYSTEM ACTION: The error log is pruned.
USER RESPONSE: None.
-----------------------------------------------------------------------
ANS4933I ERROR LOG PRUNING FINISHED SUCCESSFULLY.
ANS4933I ERROR LOG PRUNING FINISHED SUCCESSFULLY.
EXPLANATION: The error log pruning function completed with no errors.
SYSTEM ACTION: None.
USER RESPONSE: None.
-----------------------------------------------------------------------
ANS4934E ERROR LOG PRUNING FAILED.
ANS4934E ERROR LOG PRUNING FAILED.
EXPLANATION: The error log pruning function failed.
SYSTEM ACTION: The error log pruning function stops.
USER RESPONSE: Retry the command with the tracing turned on to help
determine why the pruning function failed.
-----------------------------------------------------------------------
ANS4166I ***** EXAMINED 'number' FILES *****
ANS4166I ***** EXAMINED 'number' FILES *****
EXPLANATION: Indicates the number of files ADSM processed.
SYSTEM ACTION: None.
USER RESPONSE: Continue with normal operations.
-----------------------------------------------------------------------
ANS4314E FILE DATA CURRENTLY UNAVAILABLE ON SERVER
ANS4314E FILE DATA CURRENTLY UNAVAILABLE ON SERVER
EXPLANATION: The file data is currently unavailable on the server. A
retrieve or restore operation was attempted, but either the:
o Data was corrupted at the server
o Server found a read error
o File is temporarily involved in a reclaim operation at the server
o Server requested a tape volume that was marked unavailable.
SYSTEM ACTION: Processing stopped.
USER RESPONSE: Retry the operation. If the problem continues, see your
system administrator to determine the problem from the server console or
the activity log. Check whether any requests were made for a tape volume
that was unavailable. A tape volume may be marked unavailable if prior
read errors were encountered or the volume is checked out of the tape
library.
=================================================================
Fixes:
IC09632 -
Use memory from Non-movable memory pool instead of short term memory
pool. Changed increments from 2k to 8k memory allocations.
IC09755-
Performance enhancement:
Use larger compress buffer for read and write and threadSwitch instead
of SwitchProcess. Removed a good deal of code done repetitively during
restore. A new option has been added called PROCESSORUTILIZATION.
|
