	    Mountain FileSafe for Windows Rescue NLM
			    Release V1.01

		Mountain Network Solutions, Inc.


Contents
=============================================
1. How to print this file
2. System Requirements
    2.1 Supported Network Software
    2.2 Client workstation
    2.3 Server System 3.1x
    2.4 Server System 4.x
    2.5 Server Memory Requirements
    2.6 Compatible SCSI Host Adapters
    2.7 Compatible Backup Devices
    2.8 Compatible Media Cartridges
3. General Information
    3.1 Multiple Backup Devices
    3.2 Multiple SCSI Devices
    3.3 Unsupported 8mm Drives
4. Installation Files/Directories
    4.1 Installation Disk 1, 3 1/2"
    4.2 Installation Disk 2, 3 1/2"
    4.3 Installation Disk 3, 3 1/2"
    4.4 Server Files and Target Directories
    4.5 Server System File Modifications
    4.6 Client Files and Target Directories
    4.7 Client System File Modifications
5. Trouble Shooting
    5.1 Server-Side Installation Problems
	5.1.1 Server Performance During Installation
	5.1.2 Task-Switching During Installation
	5.1.3 Device Drivers
	5.1.4 ADF File for Mountain SCSI MCA Host Adapter
	5.1.5 Adding, Changing or Removing Backup Devices
	5.1.6 Monitor Driver problems when using RCONSOLE
	5.1.7 Support of other DAI-compliant tape devices and drivers
	5.1.8 Adding Unsupported Backup Devices
	5.1.9 Note to Adaptec controller users
    5.2 Client-Side Setup Problems
    5.3 Problems during Operation
	5.3.1 "Out of Memory" Errors
	5.3.2 "Out of Disk Space" Errors
	5.3.3 Remote Server Backup Failures
	5.3.4 Tape Importing -- Special Notes
	5.3.5 Importing SBACKUP Tapes
	5.3.6 Disabling Login
	5.3.7 SMS Transport Failures
	5.3.8 NetWare Popup Messages Under Windows
	5.3.9 Notes to NetWare 4.x users
	5.3.10 "Read Media Name" Errors
	5.3.11 Device Deactivation
	5.3.12 MACINTOSH Name Space Users
	5.3.13 Assigning Job Names
	5.3.14 Retensioning Errors
	5.3.15 RESQ.NLM and Security
        5.3.16 Error 2000 No eligible media (Device Fault Errors)
    5.4 Known Problems with Novell VLM Client Software (VLM V1.02)
    5.5 Known Problems with Novell TSA Software
	5.5.1 Problem backing up partially locked files
	5.5.2 Incorrect Restore of the Kbytes Limit Space attribute (DSPACE)
        5.5.3 VDSPACE fixup utility for Kbytes Limit Space problems
	5.5.4 MAC files restored with similar DOS short names fails
6. Limitations
    6.1 Exabyte 8200 and FileSafe 2100 (2 GB 8mm) drives not supported.
    6.2 Displaying more than 2560 files in the File or Librarian Window

7. Known Bugs
    7.1 Problem Importing SBACKUP Tapes on an 8MM 5GB drive
    7.2 Problem Importing SBACKUP Tapes on a FileSafe 7500
    7.3 Low Priority Threads Console Warning Message
    7.4 Note to Norton Desktop for Windows users


1. How to print this file
=============================================

This file is an ASCII text file that can be viewed and printed in
any of the usual ways.

2. System Requirements
=============================================

The System Requirements needed to run FileSafe for Windows Rescue
NLM are:

2.1 Supported Network Software
------------------------------
	> NetWare, versions 3.11, 3.12 and 4.01.

     NOTE to NetWare 3.x users: Always use IPX version
     3.10 or newer and NETX version 3.26 or newer. NetWare VLM
     users must use the most recent version of the VLM shell.

     NOTE to NetWare 3.12 users: This release of Rescue NLM has
     not been fully tested with NetWare 3.12. For best results,
     be sure to use the most up-to-date version of the file
     TSA312.NLM, dated 11/5/93 2:28 PM. If an older version of
     this module is loaded on your server, please down your server,
     then replace it with the one on the Rescue NLM  installation
     diskettes.  If this program is NOT loaded, you may merely
     replace it with the one from the Rescue NLM installation diskettes.

     IMPORTANT: If Rescue NLM will be used to backup NetWare 4.01
     servers, the Windows Client workstation MUST be using the new
     NetWare DOS Requester (VLM)software. The old NETX shell does
     not support NetWare Directory Services operations required for
     NetWare 4.01 support under Rescue NLM.


2.2 Client workstation
----------------------
- A 386 or 486 PC System
- At least 4 MB of total memory (suggested; actual system memory
  requirements may vary)
- DOS 4.01 or greater
- Windows 3.1 running in 386 Enhanced Mode

2.3 Server System 3.1x
----------------------
- A 386 or 486 PC System
- At least 8 MB of total memory (suggested; actual system memory
  requirements may vary)
- NetWare 386 version 3.11 or 3.12
- A SCSI tape drive
- Mountain SCSI host adapter or Adaptec SCSI host adapter with
  ASPI drivers
- 3 MB free disk space (to install)

2.4 Server System 4.x
---------------------
- A 386 or 486 PC System
- At least 12 MB of total memory (suggested; actual system memory
  requirements may vary)
- NetWare version 4.01
- A SCSI tape drive
- Mountain SCSI host adapter or Adaptec SCSI host adapter with
  ASPI drivers
- 3 MB free disk space (to install)

2.5 Server Memory Requirements
------------------------------
Rescue NLM needs 2.5 Megabytes of (available) server memory to
function optimally. Run-time parameters can be adjusted to
enable it to operate (less-than-optimally) in systems with less
memory than this.

2.6 Compatible SCSI Host Adapters
---------------------------------
Rescue NLM is designed to work with several SCSI host adapters:

	Mountain
		> AT/ISA Bus Systems: 16-Bit SCSI Adapter.
		> MCA Bus Systems: 16-Bit SCSI Adapter.
	Adaptec
		> AT/ISA Bus Systems: AHA 1510, 152x, 154x.
		> MCA Bus Systems: AHA 164x.
		> EISA Bus Systems: AHA 174x.

2.7 Compatible Backup Devices
-----------------------------
	Mountain Backup Devices
		Mountain FileSafe 1200.
		Mountain FileSafe 1400.
		Mountain FileSafe 7500.
		Mountain FileSafe 71000.
		Mountain FileSafe 72000.
		Mountain FileSafe 1200Plus.
		Mountain FileSafe 1200-4.
		Mountain FileSafe 1200-4Dual.
		Mountain FileSafe 1400.
		Mountain FileSafe 1400-8.
		Mountain FileSafe 5000.
		Mountain NetSafe DC/2.
		Mountain NetSafe DAT/4.
		Mountain NetSafe DAT/8.
		Mountain NetSafe MC/750.
	DAT Backup Devices
		Hewlett Packard JetStore.
		WangDAT.
		Conner.
	QIC Format Backup Devices
		Wangtek 525 MB, 1 GB.
		Tandberg 525 MB, 1 GB, 2 GB.
	8 MM Backup Devices
		Exabyte 8500.
		Exabyte 8505.
		Exabyte 8205.

2.8 Compatible Media Cartridges
-------------------------------
Consult your backup device's hardware manual for recommendations.

Reading tapes created with a FileSafe 2100 or an Exabyte 8200 tape
drive is NOT supported.

3. General Information
=============================================

3.1 Multiple Backup Devices
---------------------------

FileSafe for Windows Rescue NLM supports multiple backup devices
of the same type, on a single SCSI Bus, using the same media
type.

All import operations are attempted from the lowest SCSI
ID addressed unit on the bus.

3.2 Multiple SCSI Devices
-------------------------

When a backup device shares the SCSI bus with a hard disk
drive, the SCSI ID for the hard drive should be lower than the
backup device's.

Additionally, use the following syntax for loading the
Adaptec device driver:

At the server console type:
:load aha1540 bus_on=4 bus_off=12 io_combine=1...(add'l options)

If you do not load the Adaptec device driver with these
parameters, attempts to write to the backup device will
fail.

Recommended reading: Novell NetWare Information for Adaptec
SCSI Host Adapters and Hard Disk Controllers Date: Jan 1992

3.3 Unsupported 8mm Drives
--------------------------

The FileSafe 2100 and Exabyte 8200 tape drives are not
supported by Mountain's FileSafe for Windows Rescue NLM.
SBackup tapes made with these drives cannot be imported by
Rescue NLM.

4. Installation Files/Directories
=============================================

4.1 Installation Disk 1, 3 1/2"
-------------------------------

	DISKID.1...........Disk Number 1 ID File
	FILELST1.311.......Copy List for Disk 1 on a 3.1x Server
	FILELST1.40........Copy List for Disk 1 on a 4.01 Server
	CLIB.311...........Updated Novell CLIB Version 3.11d
	RESQINST.NLM.......Rescue Installation Program Loader
	INSTLOAD.NLM.......Rescue Installation Program
	RESQLANG.ENG.......Error Message File for ResqMain.NLM
	MNS16S.DSK.........Driver for the Mountain SCSI Adapter
	MNS16SA.DSK........Driver for Mountain & Adaptec SCSI Adapter
	MNS8MM.DSK.........Driver for 8mm Tape Drives
	MNSDAT.DSK.........Driver for DAT Tape Drives
	MNSQIC.DSK.........Driver for QIC Tape Drives
	MNSINQ.NLM.........Mountain Driver Inquiry Program
	RESQMAIN.311.......Mountain Rescue Program for a 3.1x Server
	RESQMAIN.400.......Mountain Rescue Program for a 4.01 Server
	RESQNLM.INI........Parameter file for ResqMain program
	DEVINFO.INF........Tape Device Configuration File
	NWCALLS.DLL........Supporting Netware DLL for Client App
	NWLOCALE.DLL.......Supporting Netware DLL for Client App
	NWNET.DLL..........Supporting Netware DLL for Client App
	SH20W16.DLL........Memory Manager DLL for Client App
	TSA_NDS.NLM........Novell TSA for NDS support (Version 4.00)
			   dated 2/13/93 12:07 PM
	@7DDE.ADF..........PS/2 configuration file for MNS MC/SCSI adapter
	README.TXT.........This File
	VDSPACE.EXE........Utility to Fix invalid Kbytes Path Limit settings

4.2 Installation Disk 2, 3 1/2"
-------------------------------

	DISKID.2...........Disk Number 2 ID File
	FILELST2.311.......Copy List for Disk 2 on a 3.1x Server
	FILELST2.40........Copy List for Disk 2 on a 4.01 Server
	RESQENG.311........Rescue Tape Engine for a 3.1x Server
	RESQ.311...........'Rescue' Program for a 3.1x Server
	PHYSADDR.DSK.......Supporting Program used by the Device Drivers
	TSA311.NLM.........Novell's TSA - Version 4.01b for a 3.11 Server
			dated 11/5/93 2:36 PM
	SMDR31X.NLM........Novell's SMS - Version 4.01b for a 3.1x Server
			dated 10/28/93 5:14 PM
	TSA312.NLM.........Novell's TSA - Version 4.01b for a 3.12 Server
			dated 11/5/93 2:28 PM
	RESQENG.400........Rescue Tape Engine for a 4.01 Server
	RESQ.400...........'Rescue' Program for a 4.01 Server
	TSA400.NLM.........Novell's TSA - Version 4.01b for a 4.01 Server
			dated 11/5/93 2:20 PM
	SMDR.NLM...........Novell's SMS - Version 4.01b for a 4.01 Server
			dated 10/28/93 5:11 PM

4.3 Installation Disk 3, 3 1/2"
-------------------------------

	DISKID.3...........Disk Number 3 ID File
	FSPLWN.EXE.........Windows Client Application
	FSPL.INI...........FSPLWN configuration file in INI format
	FSPLWN.HLP.........FSPLWN Help File
	IDJOB.IJF..........ID Job File Template
	RADTMPL.IJF........Job File Template
	DEFAULT.MDA........Default library media file
	NBACKUP.NVR........Backup Global Filters Exclude List
	NRESTORE.NVR.......Restore Global Filters Exclude List
	JSCHED2.EXE........Scheduler program
	JSCHED2.HLP........Scheduler help file
	JSCHED.INI.........Scheduler INI file
	JSCHED2.ALR........Scheduler alarm file
	JSQUE.EXE..........Scheduler Utility
	JSLOG.EXE..........Scheduler Utility
	JSLOADN.EXE........Scheduler Utility


4.4 Server Files and Target Directories
---------------------------------------

		Copied to               Copied to              Copied to
Files\Server      3.11                    3.12                   4.01
==============================================================================
Disk 1
 INSTLOAD.NLM   RESQINST.NLM            RESQINST.NLM          RESQINST.NLM
 RESQLANG.ENG   RESQLANG.ENG            RESQLANG.ENG          RESQLANG.ENG
 MNS16S.DSK     MNS16S.DSK              MNS16S.DSK            MNS16S.DSK
 MNS16SA.DSK    MNS16SA.DSK             MNS16SA.DSK           MNS16SA.DSK
 MNS8MM.DSK     MNS8MM.DSK              MNS8MM.DSK            MNS8MM.DSK
 MNSDAT.DSK     MNSDAT.DSK              MNSDAT.DSK            MNSDAT.DSK
 MNSQIC.DSK     MNSQIC.DSK              MNSQIC.DSK            MNSQIC.DSK
 MNSINQ.NLM     MNSINQ.NLM              MNSINQ.NLM            MNSINQ.NLM
 RESQNLM.INI    RESQNLM.INI             RESQNLM.INI           RESQNLM.INI
 DEVINFO.INF    JOBCOMMS\DEVINFO.INF    JOBCOMMS\DEVINFO.INF  JOBCOMMS\DEVINFO.INF
 NWCALLS.DLL    FSPLN\NWCALLS.DLL       FSPLN\NWCALLS.DLL     FSPLN\NWCALLS.DLL
 NWLOCALE.DLL   FSPLN\NWLOCALE.DLL      FSPLN\NWLOCALE.DLL    FSPLN\NWLOCALE.DLL
 NWNET.DLL      FSPLN\NWNET.DLL         FSPLN\NWNET.DLL       FSPLN\NWNET.DLL
 SH20W16.DLL    FSPLN\SH20W16.DLL       FSPLN\SH20W16.DLL     FSPLN\SH20W16.DLL
 README.TXT     FSPLN\README.TXT        FSPLN\README.TXT      FSPLN\README.TXT
 RESQMAIN.311   RESQMAIN.NLM            RESQMAIN.NLM
 RESQMAIN.400                                                 RESQMAIN.NLM


Disk 2
 RESQENG.311    RESQENG.NLM             RESQENG.NLM
 PHYSADDR.DSK   PHYSADDR.DSK            PHYSADDR.DSK
 RESQ.311       FSPLN\RESQ.NLM          FSPLN\RESQ.NLM
 TSA311.NLM*    TSA311.NLM              TSA311.NLM
 SMDR31X.NLM*   SMDR31X.SAV             SMDR31X.SAV
		SYS:SYSTEM\SMDR31X.NLM  SYS:SYSTEM\SMDR31X.NLM
 TSA312.NLM*    TSA312.NLM              TSA312.NLM
 RESQENG.400                                                  RESQENG.NLM
 RESQ.400                                                     FSPLN\RESQ.NLM
 TSA400.NLM*                                                  TSA400.NLM
 SMDR.NLM*                                                    SMDR.SAV
							      SYS:SYSTEM\SMDR.NLM

* NOTE:  THESE FILES ARE ALSO COPIED TO THE SYS:SYSTEM DIRECTORY.
	 IF THE FILE ALREADY EXISTS IN THIS DIRECTORY AND IT
	 IS OLDER THAN THE FILE ON THE RESCUE NLM INSTALLATION DISK,
	 THE OLD FILE WILL BE RENAMED AS .001.

Disk 3
 FSPLWN.EXE     FSPLN\FSPLWN.EXE      FSPLN\FSPLWN.EXE      FSPLN\FSPLWN.EXE
 FSPL.INI       FSPLN\FSPL.INI        FSPLN\FSPL.INI        FSPLN\FSPL.INI
 FSPLWN.HLP     FSPLN\FSPLWN.HLP      FSPLN\FSPLWN.HLP      FSPLN\FSPLWN.HLP
 IDJOB.IJF      FSPLN\IDJOB.IJF       FSPLN\IDJOB.IJF       FSPLN\IDJOB.IJF
 RADTMPL.IJF    FSPLN\RADTMPL.IJF     FSPLN\RADTMPL.IJF     FSPLN\RADTMPL.IJF
 DEFAULT.MDA    FSPLN\DEFAULT.MDA     FSPLN\DEFAULT.MDA     FSPLN\DEFAULT.MDA
 NBACKUP.NVR    FSPLN\NBACKUP.NVR     FSPLN\NBACKUP.NVR     FSPLN\NBACKUP.NVR
 NRESTORE.NVR   FSPLN\NRESTORE.NVR    FSPLN\NRESTORE.NVR    FSPLN\NRESTORE.NVR
 JSCHED2.EXE    FSPLN\JSCHED2.EXE     FSPLN\JSCHED2.EXE     FSPLN\JSCHED2.EXE
 JSCHED2.HLP    FSPLN\JSCHED2.HLP     FSPLN\JSCHED2.HLP     FSPLN\JSCHED2.HLP
 JSCHED.INI     FSPLN\JSCHED.INI      FSPLN\JSCHED.INI      FSPLN\JSCHED.INI
 JSCHED2.ALR    FSPLN\JSCHED2.ALR     FSPLN\JSCHED2.ALR     FSPLN\JSCHED2.ALR
 JSQUE.EXE      FSPLN\JSQUE.EXE       FSPLN\JSQUE.EXE       FSPLN\JSQUE.EXE
 JSLOG.EXE      FSPLN\JSLOG.EXE       FSPLN\JSLOG.EXE       FSPLN\JSLOG.EXE
 JSLOADN.EXE    FSPLN\JSLOADN.EXE     FSPLN\JSLOADN.EXE     FSPLN\JSLOADN.EXE
=================================================================================

Note: All file paths listed above assume the default installation
directory, SYS:\SYSTEM\RESQNLM).

4.5 Server System File Modifications
------------------------------------
[1] RESQINST will write RESQPATH.INI file to 'SYS:\PUBLIC' directory. This
    file contains all the information for installation path and software
    version information.

[2] AUTOEXEC.NCF will be updated to include these two lines,

	REM Load device driver here
	SYS:\SYSTEM\MNSDRVR.NCF

    Execution of the NetWare batch file MNSDRVR.NCF will add our installation
    directory into the search path when the server is rebooted.

[3] STARTUP.NCF is updated to have a line similar to this,

	set reserved buffers below 16 meg = n

    where n is calculated by the formula,

	n = (# of drives + 1) * 32

To back up the target server (it doesn't matter if it's a local or remote
server) you need to load:

      3.11                         3.12                     4.01
  =============                =============            =============
   TSA311.NLM                   TSA312.NLM               TSA400.NLM
   SMDR31x.NLM                  SMDR31x.NLM              SMDR.NLM
				TSA_NDS.NLM

During the installation, four directories are created. They are all under
the installation directory (By default, it's SYS:SYSTEM\RESQNLM).
    TEMP\
    JOBCOMMS\
    FSPLN\JOB\
    FSPLN\LIB\

These directories are created with the Purge attribute assigned.
This is because temporary files are created and deleted each time a
job is run.  Some files can get very large, depending on how big your
file structures are.  By setting the purge attribute for these
directories, any files that are deleted will not take up valuable
disk space in between Purge intervals.  Because these directories
are assigned this attribute, take extreme caution when deleting files
from these directories.  If you accidentally delete your Job or
Library files, you will not be able to SALVAGE them.

4.6 Client Files and Target Directories
---------------------------------------
Files Copied to client workstation:
To C:\WINDOWS\JSCHEDN:
JSCHED2  EXE
JSCHED   INI
JSCHED2  ALR
JSCHED   HLP
JSQUE    EXE
JSLOG    EXE
NWNET    DLL
NWCALLS  DLL
NWLOCALE DLL
JSCHED2  HLP

To C:\WINDOWS:
JSLOADN.EXE

4.7 Client System File Modifications
------------------------------------
WIN.INI MODIFICATIONS:

[windows]
LOAD=JSLOADN.EXE  (If scheduler was selected for activation)

[FSPLN]
SchedulerInitialized=Yes  (or no depending on initialization)
ApplicationPath=G:\SYSTEM\RESQNLM\FSPLN (used in determining creation
of program group)

5. Trouble Shooting
=============================================

5.1 Server-Side Installation Problems
=============================================

5.1.1 Server Performance During Installation
--------------------------------------------
Because Rescue NLM installs from floppies at the server, the
NLM which performs the installation (RESQINST.NLM) must make
system calls to the DOS I/O services provided by the NetWare Server
Kernel's CLIB. These services can disrupt the normal timeslicing
during the time that files are actually being copied; users logged
into the server may notice a significant performance degradation
during the time it takes for the RESQINST installation program to
copy the files from the floppies to the server's hard disk.

Once the copying from floppies ceases, server responsiveness will
return to normal levels.

5.1.2 Task-Switching During Installation
----------------------------------------
Avoid task-switching while the installation program is copying files
from diskette to server. This means that you should perform the
installation during a period when you know you will not need the
console.

5.1.3 Device Drivers
--------------------
When using Rescue NLM, be sure to use the device drivers that you
received with this product. Don't use older versions of these drivers.

On the other hand, if you have been using SBACKUP with old drivers
and wish for some reason to go back to using it, be sure to use the
older drivers.

     Device         SBACKUP             RESQNLM
     Driver         Version             Version
     =======        =======             =======
     MNS16S         1.02                1.02
     MNS16SA        1.06                1.06
     MNSDAT         1.06a               1.06d
     MNS8MM         1.06                1.06a
     MNSQIC         1.01                1.02e

You can determine which drivers are currently in use in your system
by typing MODULES and pressing the Enter key at the server console.

5.1.4 ADF File for Mountain SCSI MCA Host Adapter
-------------------------------------------------
The ADF (@7DDE.ADF) file for Mountain's MCA SCSI host adapter
can be found on Disk #1 of the Rescue NLM software disk set.
This file is required for MCA Setup operations after
you have installed your host adapter. Refer to your hardware
installation documentation, and the appropriate IBM PS/2 (TM)
reference for further information.

5.1.5 Adding, Changing or Removing Backup Devices
-------------------------------------------------
1) If you add, change, or remove backup devices on your server,
remember to unload and reload the device drivers for your backup
device(s) before running RESQINST from the server console. In
addition, if you've added devices, you'll need to down and
re-boot the server. You may also need to power off and back on
any backup device you have changed, e.g., changing the SCSI ID.

2) If you wish to daisy-chain your SCSI backup device onto an
existing SCSI installation which supports your server boot
drive, you may encounter boot difficulties unless you set your
tape drive to SCSI ID 2 through 6. This is especially true when
the SCSI adapter has a boot ROM. Some boot ROMs expect to find
a bootable disk device at SCSI ID #0 or #1. Setting a backup
device to one of these ID's can "confuse" the boot ROM, and
prevent your server from booting.

5.1.6 Monitor Driver problems when using RCONSOLE
-------------------------------------------------
If you've loaded Rescue NLM on a server with a color VGA monitor, you
may not be able to see highlighting on an attached client with a
gray-scale VGA monitor when using RCONSOLE to run RESQMAIN.

Additionally, the display of some characters may not be correct.

5.1.7 Support of other DAI-compliant tape devices and drivers
-------------------------------------------------------------
Rescue NLM should be able to operate third-party tape drives and
controllers which are supported by DAI-compliant device drivers
(e.g.: TAPEDAI.DSK, provided by Novell). To use these devices with
Rescue NLM, make sure the required controller drivers are loaded
PRIOR to running RESQINST (the installation program), and then skip
the hardware configuration portion of the installation program setup.
You should be able to then run RESQMAIN with your third-party hardware
and drivers. Mountain can provide no assurances that any particular
third-party hardware and/or .DSK driver will be 100% compatible
with Rescue NLM.

For example, if you're using a COMPAQ SCSI II fast controller, you'll
need to issue the following commands at the server console:

load CPQS710.DSK     COMPAQ's controller driver
load CPQSTAPE.DSK    COMPAQ's device (drive) driver
scan for new devices Causes NetWare to identify any new devices
list devices         To obtain the device string required for DEVINFO.INF

5.1.8 Adding Unsupported Backup Devices
---------------------------------------
The file DEVINFO.INF contains the raw string names of all the backup devices
tested on Rescue NLM. If you wish to install an unlisted backup device
you'll need to edit this file (using any ASCII editor). The raw string device
name can be obtained either by using MONITOR's Disk Information option, or
by using "scan for new devices", followed by "list devices" at the server
console (4.x users only).

Be sure to follow the syntax template established in the file.

This file is located in the \SYSTEM\RESQNLM\JOBCOMMS subdirectory.

5.1.9 Note to Adaptec controller users:
---------------------------------------
When running the server-side installation, ResQInst, in the Adapter Card
Driver menu, the selection of option "Add Adaptec's Controller Driver" will
only give instructions about installing Adaptec cards.  It does not perform
the installation itself.  If you are installing more than one Adaptec adapter,
you should load the drivers for ALL of them before reselecting "Adapter:" in
the "Hardware Configuration" screen.

For best results, we recommend that you install and load the Adaptec drivers
before you run RESQINST.NLM.

5.2 Client-Side Setup Problems
=============================================
1) Since Rescue NLM is a completely NetWare-aware program, it relies heavily
on the Windows drivers for NetWare to perform correctly. You MUST
setup your Windows installation to run with NetWare using the Windows
Setup program and the drivers provided by Novell. Mountain does
NOT provide these drivers (NETWARE.DRV, VNETWARE.386, VIPX.386,
VNETBIOS.386).

One way to test if Windows is setup to work with NetWare is to
run the File Manager in Windows, and then pull down the Disk menu from
the Menu bar. If you do not see a menu item called "Network Connections",
you have NOT properly setup your Windows to run with NetWare. Or, try running
the Control Panel, and clicking the Networks Icon. If there is no Networks
icon, your setup is not correct.

Another test you can perform is to run Novell's own Windows
utilities. If you have NetWare 4.01, try running NWADMIN or
NWUSER from within Windows. Successfully running NWADMIN will
ensure that you have correctly installed NetWare's support for
NetWare Directory Services on your client workstation.

2) Before setting up the client-side interface for Rescue NLM,

a) Be sure Windows has been installed to run with NetWare. See your
Windows documentation on how to set up Windows to run with NetWare.

b) Be sure that you are logged in as SUPERVISOR, ADMIN, or a user
with equivalent rights. Otherwise, installation will not complete
successfully.

5.3 Problems during Operation
=============================================

5.3.1 "Out of Memory" Errors
----------------------------
If your system meets the requirements for FSW Rescue NLM but "out of
memory" errors are generated during operation, check your system's
reserved buffer settings. To eliminate the error, reduce the number
of buffers specified in STARTUP.NCF.

Also: backup operations are memory intensive, and tend to allocate
and free memory often. NetWare 4.01 users should therefore be sure
to set their systems for frequent garbage collection.
In the STARTUP.NCF file one might set:

Garbage Collection Interval = 5 minutes
Number of Frees For Garbage Collection = 200
Minimum Free Memory for Garbage Collection = an amount greater than
    RESQNLM.INI's Transfer Buffer Pool Size.

These are illustrative values only, of course; every system's needs
are different.

5.3.2 "Out of Disk Space" Errors
--------------------------------
This error usually occurs when backing up very large data sets.
To clear up this problem, you will have to offload data
from the server volume you have installed Rescue NLM to.
There must be enough disk space to hold the necessary job files
required to perform an operation.

The formula for determining how much disk space is needed for
temporary files during a backup (during Restore or Verify, cut 20%
from this value) is:

number of files * (175 + (average file name length *
  number of name spaces))

where:
  number of files = total number of files and directories to back up
  average file name length = most users can assume an average file name length
       of 50 characters.  If there are a lot of really deep directories or wide
       directory paths, you might want to increase this to get a safety margin.
  number of name spaces = the number of supported name space on the volume that
       is being backed up (DOS, MAC, OS/2).

5.3.3 Remote Server Backup Failures
-----------------------------------
When performing operations (eg: backup, restore) involving
remote servers (those other than where Rescue NLM is installed),
be sure to load the correct versions of the SMDR and TSA
programs on those remote servers.  These programs can be found
on the Rescue NLM install diskettes.  For NetWare 3.11 servers,
load SMDR31x, then load TSA311.  For NetWare 4.x servers, load
SMDR, then load TSA400, then load TSA_NDS.  Again, be sure to
get the latest copies of these programs from the Rescue NLM
installation diskettes.

5.3.4 Tape Importing -- Special Notes
-------------------------------------
In this version of Rescue NLM, importing of tape cartridges into the
Librarian database must be done using the first SCSI device (the
backup device with the lowest SCSI ID number).

The Progress Bar on the Import Status screen may not appear to
give accurate readings during some operations. Import will make
two passes for each session on the media cartridge.  During the
first pass, the estimated file count and KBytes are unknown.
The second pass actually imports the files and lists the actual
and estimated values.  Therefore no updating of the "% complete"
is done during the first pass.

5.3.5 Importing SBACKUP Tapes
-----------------------------
1) Rescue NLM imports SBACKUP tapes and can restore DOS files, NDS,
and binderies.

2) Attempting to restore imported MAC & OS/2 data backed up with
SBACKUP 3.11b or 4.0 is not supported.

3) Rescue NLM does not append data sets to media cartridges created
using SBackup. Also data recovery from SBACKUP tapes created on a
NetWare 3.12 server is not supported in this release of Rescue NLM.

4) When importing tapes created with SBackup, the directory field
displays a directory name only once per occurrence.  This field
will be empty for all other files contained in that directory.

5.3.6 Disabling Login
---------------------
Some administrators prefer to run ":disable login" at the server
console to prevent users from logging in during a backup. Note
that this prevents TSAs from logging in. If you do this, be sure
you log in from the NLM client station and begin the backup,
restore, or verify operation before running ":disable login".

5.3.7 SMS Transport Failures
----------------------------
You may encounter errors when attempting to back up a slower
NetWare 3.1x volume from a faster NetWare 4.x server. To solve
this problem, change the SPX parameters. To do this, from the
4.x server console type:

  LOAD SERVMAN

Go to IPX-SPX Configuration, select SPX parameters, and increase the parameter
values in this order: 540, 110, 1500, 50, 1000. Continue to increase the
parameters until the error message is no longer displayed.

5.3.8 NetWare Popup Messages Under Windows
------------------------------------------
You can receive a NetWare popup message when you need to load Rescue
NLM to run a job, provided you've added NWPOPUP.EXE to the load= command
line of your client station's WIN.INI file.

5.3.9 Notes to NetWare 4.x users:
---------------------------------
1) The Auto Login User name must be 47 characters or less. Although NDS allows
longer names than this, the bindery does not.

2) Do not use INSTALL.NLM to modify AUTOEXEC.NCF or STARTUP.NCF files
while performing operations using Rescue NLM. Doing so will cause a system
abend. This is a problem in NetWare's EDIT.NLM per NOVELL.

3) Auto Login to a 4.x Server has several special requirements for setting
up the client workstation.  You must add the following statement to your 
NET.CFG file:
                 Preferred Server = <my_server>

where <my_server> is the server where ResqNLM is installed.  Also, make sure
you don't have a statement of the form:

                 Preferred Tree = <tree_name>

Taking these steps ensures that the Auto Login function can establish the 
connection to the ResqNLM server.

Another thing you should know about Auto Login concerns the current 
Directory Services context in effect when the login takes place. The
Auto Login function only uses the Common Name you specified during
installation; it does not use a fully-qualified Directory Services
object name. (e.g.: "FileSafeUser" rather than "CN=FileSafeUser.O=Myorg").

For this reason, you might find it convenient to add the following
statement to your NET.CFG file:

                Name Context = <your organization>

where <your organization> is the DS container object (Organization or
Organizational Unit) which contains the ResqNLM installation server.
Alternatively, you can use the CX command to ensure that your current
DS context is set to <your organization> after logging out, but before
restarting Windows in preparation for scheduled, autologin jobs:

                C> CX <your organization>

If the Directory Services context is not set to the proper container
object, you will get Auto Login errors in the -600 thru -699 range,
indicating that Auto Login could not find the NDS object in the current
context. If this should happen to you, use one of the techniques above
to correct the problem.

5.3.10 "Read Media Name" Errors
-------------------------------
If running Read Media Name and the name is not displayed after a few minutes,
it may be caused by a few reasons:
  1.) Using an incorrect tape type (e.g., a 2 GB capacity tape
      in an FS7500 drive)
  2.) A blown fuse in the SCSI adapter (make sure when you plug in the
      SCSI cable from the adapter to the SCSI device that the
      device is powered OFF.)
  3.) Powering off the device while it is reading the media cartridge
      (in this case the device eventually times out rather than hang the
      server).

If you perform a Read Media Name with no media cartridge inserted
into any of the backup devices, an "Error (undetermined device not
active)..." is displayed. If you insert a media cartridge and select
Retry, it will read the media cartridge.

5.3.11 Device Deactivation
--------------------------
When a backup device deactivates itself because of a drive failure,
the drive with the failure remains locked after RESQMAIN is exited
(for backup devices that permit soft locking).  Since the drive has
deactivated there is no way to release it.  The backup device should
be powered off and back on before attempting any operations again.

5.3.12 MACINTOSH Name Space Users
---------------------------------
When backing up, restoring or verifying MACINTOSH files on a NetWare
server volume, the progress bar goes to 100% before all the data has
been processed.  This is also reflected in the KBytes estimated.
This is because the TSA does not pass back valid size information
for the resource fork during the preliminary file scan. (During the
actual backup and restore operations, however, ALL forks and namespace
information is maintained.)

This is also true when viewing file information in the File
System window. This can result in MAC files showing a size of 0
bytes when viewing file information using Edit, Properties.

5.3.13 Assigning Job Names
--------------------------
Do NOT use device names such as COM1, LPT1, etc., when saving
new jobs.  This results in an attempt to write to that device,
causing your backup job to fail.

5.3.14 Retensioning Errors
--------------------------
Retensioning when selected from the server console does not read
the MEDIA ID, therefore allowing any media type to be retensioned.
However, selecting Retension from the client side reads the MEDIA ID.
If an invalid cartridge type is inserted, RESQMAIN is locked up and
the drive deactivates itself. To avoid this, ensure that you are always
using the correct media for the backup device you are using.

5.3.15 RESQ.NLM and Security
----------------------------
With this release of Rescue NLM, there are no security
restrictions set for using RESQ.NLM at the server console to
recover volumes that have crashed.  To ensure that all data is
correctly restored, you should supply the SUPERVISOR or ADMIN
user name and password when prompted.  The user performing the
RESQ restore must have SUPERVISORY rights to root in order to
correctly recover all data.

5.3.16 Error 2000 No eligible media (Device Fault Errors)
---------------------------------------------------------
If during a backup operation you receive an error "2000 There
is no eligible media in any drives..." and you know the media
in the backup device is indeed eligible to be overwritten,
there may be a Device or Media problem.  If you receive this
error, go to the ResqMAIN console screen and select READ MEDIA
NAME.  This function will inform you as to whether you have a
Device or Media error.  This is usually caused by a media
cartridge that was written in a variable length sector size
or by a backup device that uses hardware compression.  You
will have to use the same backup device you wrote the media
cartrige with previously in order to write to this tape.  If
this is not possible, use SBACKUP to perform a small overwrite
backup using the desired backup device.  This will clear any
bad or incompatible sector size information on the media
cartridge.


5.4 Known Problems with Novell VLM Client Software (VLM V1.02)
==============================================================
During testing of Rescue NLM, several errors and problems were
discovered that were attributed to the currently shipping versions
of Novell's VLM V1.02 for DOS client workstations. We were given
the opportunity to test Novell's BETA release of VLM V1.03 and
confirmed that Novell has fixed these problems. As of this writing,
Novell is close to releasing the VLM V1.03 software. If you
encounter the errors listed below, you may wish to upgrade your
VLM client software to V1.03 when it becomes available from
Novell.

Various error messages indicating failure attaching to various
servers, or that "server XXXX already attached" (during Volume
Scan and during JSLOG setup of scheduled jobs). This usually
occurs when attempting to scan a 3.11 server in a mixed 3.x/4.x
NetWare NDS environment.

Initialization error stating "your connection table is corrupt".

Selecting a Volume for display in the File System window and
get a message: "Error mapping drive: can't create CDS."

5.5 Known Problems with Novell TSA Software
=============================================

5.5.1 Problem backing up partially locked files
-----------------------------------------------
Novell has been informed of a problem in the SMS/TSA during a Backup which
does not handle the deliverance of a partially locked file to the RESQ.NLM
engine properly.

If the "Prompt for NonFatal Errors" option is NOT set in the FileSafe for
Windows ResqNLM Advanced Options in the backup dialog box, this problem
will not affect any users.  The partially locked file will NOT be written
to tape and will be added to the SKIPLIST.

If the "Prompt for NonFatal Errors" option is set in the FileSafe for
Windows ResqNLM Advanced Options in the backup dialog box, and the ResqNLM
engine detects a partially locked file during a backup, ResqNLM will
prompt the user asking whether or not to backup the file anyway.  If the
user answers NO (recommended), the file is not backed up and placed on the
skiplist.  If the user answers YES, the file is backed up.

**** WARNING: We have found that Novell's SMS/TSA delivers NULLs in place
    of the locked portion AND subsequent unlocked portions to the ResqNLM
    engine.  If the user is prompted about a partially locked file and answers
    YES to indicate "backup anyway", the file will be written to tape as all
    zeros from the locked portion onward.  If this file is restored to disk,
    the file on disk will be corrupt.

    Therefore, we recommended that the user Selects -NO- during any Partial
    Lock prompting.  We provide this option to you, however, in case Novell
    releases a new version of the SMS/TSA.

5.5.2 Incorrect Restore of the Kbytes Limit Space attribute (DSPACE)
--------------------------------------------------------------------
The KBytes Limit Space attribute is not being restored correctly.
This appears to be a TSA bug and is being reported to Novell for
further investigation.

Additionally, if your values are set larger than your total
disk space or are illegal values, you may experience problems
when attempting to perform a Restore operation.  You can
recover your data by performing a Redirected Restore to a
different directory so that this invalid KBytes Limit Space
value does not get restored.

There is a utility on the Installation Disk #1 of your Rescue 
NLM disk set called VDSPACE.EXE that can scan your server volumes
for invalid values and, optionally, correct them.  See the 
section below for more details.

5.5.3 VDSPACE fixup utility for Kbytes Limit Space problems
-----------------------------------------------------------
The program called VDSPACE.EXE on Disk #1 of your Rescue NLM 
installation disk set is a utility to find and fix problems 
with DSPACE settings on your NetWare volumes. Read this prior 
to performing your first backup using Rescue NLM!

If you have directory space limits setup on your disk, you 
might encounter problems restoring directories using Rescue NLM 
if the space limit is more than 65,535 4K blocks (262,140 KB or 
268,431,360 bytes). This is because the current versions of 
TSA31x and TSA400 seem to truncate the DSPACE limit in 
subdirectories to 16 bits. The result is that you can't store 
files in any of these subdirectories, or subdirs below them, 
because the DSPACE limit is now smaller that it was when the 
data was backed up (even though the correct DSPACE value was 
recorded on your NLM backup tape.).

We have also found that some customer sites did not establish 
their own DSPACE limits, but nevertheless, their volumes have 
various subdirectories with VERY LARGE DSPACE limits 
(0x0FFFFFFF hex, or 268,435,455 4K blocks, or 1,073,741,820 
KB). These users didn't notice such large DSPACE limits, 
because the limits are larger than their volume sizes, and thus 
don't restrict space usage. However, when these large numbers 
are backed up, then restored, the TSA's will perform the same 
truncation, and one can end up with a directory limit of about 
260+ MB. If you have gigabyte disks, this CAN result in 
"Insufficient disk space" error messages).

To assist our customers in dealing with this situation, we have 
provided the VDSPACE (Verify DSPACE) utility. You can use it to 
see if any directory has a DSPACE limit set larger than the 
volume size by typing:

     VDSPACE servername\volumename:

at the DOS command prompt. If VDSPACE finds any negative DSPACE 
values, or ones that are bigger than the volume size, it will 
print out the directory path and the DSPACE setting.

If you want to see the DSPACE settings for ALL directories that 
have a setting, you can use the 'all' option:

     VDSPACE all servername\volumename:

You will get a complete listing of every directory that has a 
DSPACE setting.

If you find that you have invalid DSPACE values, you can have 
VDSPACE remove the obviously erroneous ones (bigger than the 
volume size) by adding the 'fixup' option:

     VDSPACE fixup servername\volumename:

If you use the fixup option, and then run VDSPACE again without 
the fixup option, it should NOT report any directories as 
having invalid values.

Finally, if you wish to remove ALL existing DSPACE settings, 
whether "reasonable" or not, you can add the 'all' option along 
with the 'fixup' option:

     VDSPACE fixup all servername\volumename:

Working with just part of a volume: if you want to perform any 
of the above operations on just a subtree (a particular 
directory and all of its subdirs), you can add a path to ANY of 
the above forms of the VDSPACE command to restrict VDSPACE to 
just that part of your volume. For example:

VDSPACE fixup all MYSERVER\SYS:SYSTEM\APPDIR

will cause VDSPACE to remove all DSPACE restrictions in the 
subdirectory SYS:SYSTEM\APPDIR and all of the subdirectories of 
that directory.

Other options: If you type VDSPACE with no other parameters, 
VDSPACE will explain its options for you. Please note that we 
have made two other options available for VERY EXPERT USERS, 
and we DISCOURAGE THEIR USE! These two options are 'dump' and 
'torque'. The VDSPACE usage screen is self-explanatory; if you 
use these options, you are responsible for the consequences! 
Notice, though, that the effect of a 'torque' can be 
subsequently undone with a 'fixup all'....

5.5.4 MAC files restored with similar DOS short names fails.
------------------------------------------------------------
Attempting to restore or redirect restore a MAC directory that has
a similar short name to a MAC file in the same subdirectory ( i.e. -
both file and directory have the same parent ), causes a failure
to restore the directory properly. For example, a file's DOS short
name could be TRASHCAN, and a directory could be named TRASHCA0.
This is due to a limitation in the Novell O/S file handling and
is currently under investigation.

6. Limitations
=============================================

6.1 Exabyte 8200 and FileSafe 2100 (2 GB 8mm) drives are not supported.
-----------------------------------------------------------------------
No support is currently provided for reading tapes written using
SBACKUP on Exabyte 8200 and FileSafe 2100 drives. SBackup can be
used to restore from these tapes. There are no current plans to
provide support for these drives.

6.2 Displaying more than 2560 files in the File or Librarian Window
-----------------------------------------------------------------------
FileSafe for Windows will not display more than 2560 files in the 
File System or the Librarian Window.  An error message will appear
indicating the there is not enough memory and that other window apps should
be shutdown.  This will not fix the problem.  This error message is only
applicable if there are less than 2560 files in the directory.  The user
can still individually select the files that are displayed for Restore or
Backup operations, but the files that are not displayed can not be selected.
Otherwise, the user must select the entire directory via the F9 - Select all 
function key for Backup and Restore operations.

7. Known Bugs
=============================================

7.1 Problem Importing SBACKUP Tapes on an 8MM 5GB drive
-------------------------------------------------------
Some 4.01 systems may experience problems importing multiple
sessions off of an SBackup tape using an Exabyte 8500 or
FileSafe 5000 tape drive.  This is due to conflicting return
codes from the driver on some 4.01 systems. The user should
try to import using a different 4.01 system ( if available ),
or a different drive.

7.2 Problem Importing SBACKUP Tapes on a FileSafe 7500
------------------------------------------------------
Importing spanned SBackup tapes on a 7500 drive will only
import the first tape. This bug is currently fixed, but
is not available in this release.  It will be available
in the next subsequent release.

7.3 Low Priority Threads Console Warning Message
------------------------------------------------
Some 4.01 systems may experience console messages stating that
the NLM is not allowing low priority threads to run ( these
are threads like the file compression thread, etc. ). This
appears to only happen on some 4.01 systems and is related
to the way the system is configured. The user can get rid
of this by setting Upgrade Low Priority Threads to ON, or
by increasing the number of threads that are allowed to
run prior to switching in the ResqNLM thread. These are
both settable parameters ( via SET command on the server
console ). Note : see NetWare v4.0 System Messages Volume
pg. 145, message 1616 for clarification on this message.

7.4 Note to Norton Desktop for Windows users:
---------------------------------------------
Using a system with Norton Desktop as the Windows shell, attempts to create
a Desktop icon for the RAD_CMPL job may cause an error message "The RAD_CMPL
program item could not be added to the FileSafe for Windows program group."
Under Norton Desktop for Windows, a desktop backup icon cannot be created.

