
              NOVELL TECHNICAL INFORMATION DOCUMENT

TITLE:              SBACKUP files
DOCUMENT ID:        TID014522
DOCUMENT REVISION:  B
DATE:               01FEB94
ALERT STATUS:       Yellow
INFORMATION TYPE:   Symptom Solution
README FOR:         SBACK2.EXE

NOVELL PRODUCT and VERSION:
NetWare 3.12
NetWare 4.01

ABSTRACT:

SBACKUP files for NetWare 3.12 and NetWare 4.0x.  


DISCLAIMER
THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO NOVELL.  NOVELL
MAKES EVERY EFFORT WITHIN ITS MEANS TO VERIFY THIS INFORMATION.  HOWEVER, THE
INFORMATION PROVIDED IN THIS DOCUMENT IS FOR YOUR INFORMATION ONLY.  NOVELL
MAKES NO EXPLICIT OR IMPLIED CLAIMS TO THE VALIDITY OF THIS INFORMATION.


SYMPTOM

     General enhancements needed.

SOLUTION

     Apply SBACK2.EXE

     Self-Extracting File Name:  SBACK2.EXE     Revision:  B

     Files Included     Size     Date      Time

     \
       SBACK2.TXT         (This File)
         SMDR.NLM      41362   10-28-93    5:11p
       WS_MAN.NLM      35146   12-16-93   10:51a
      TSA_DOS.NLM      77820   11-08-93    8:46a
      TSA_OS2.NLM       7814   11-02-93    5:20p
      TSA_SMS.COM      17724   10-18-93    4:37p  (DOS version only)
      TAPEDAI.DSK      34231   05-18-93    8:36a
     \3.12\
       TSA311.NLM     129464   11-05-93    2:36p
       TSA312.NLM     129461   11-05-93    2:28p
      SMDR31X.NLM      41649   10-28-93    5:14p
     \4.0X\
       TSA400.NLM     122492   11-05-93    2:20p
      SBACKUP.NLM     234976   08-17-93    1:56p


     Installation Instructions:

     Installation instructions for NetWare 4.0x and 3.12

     1.   Flag all SBACKUP files SRW in the SYS:SYSTEM directory for the
          version of NetWare being updated (see list above).  Note: The
          TSA_SMS.COM file for DOS resides in the SYS:PUBLIC subdirectory.

     2.   Rename the SBACKUP files to *.OLD.

     3.   Copy all update files, for the version of NetWare being updated, to
          the SYS:SYSTEM directory.

     4.   Change the file flags back to ROS.

               **********************
               * A WORD OF CAUTION: *
               **********************

     Currently, SBACKUP does not do READ-AFTER-WRITE verification of the data
     that is backed up.  Therefore, it is important to manually verify all
     backups.  One way of accomplishing this is to follow example one in the
     Commonly Asked Questions section -- "How to Restore a file to a new
     location."

          -Restore several files to a new location on the system.  Execute a
          DOS compare on the restored files against their originals, which
          will verify that the files are being backed up correctly and that
          they can be restored.

     NOTE: This does not represent a complete verification.  Novell recommends
     that the user follow this process with every backup set made and the
     process should be made a regular step in the backup procedure.


     Solution Specifics:

     Explanation of TAPEDAI.DSK and DIBIDAI.NLM.

     TAPEDAI.DSK
     
          The TAPEDAI.DSK file is a NetWare 386 device driver written to
          control certain tape devices.  It is used with the DIBIDAI.NLM
          program.

          The DIBIDAI.NLM program presents a DIBI interface to the SBACKUP.NLM
          program.  Additionally, the DIBIDAI.NLM program translates the DIBI
          requests into NetWare DAI calls.  This eventually results in device
          driver calls getting passed to the TAPEDAI.DSK driver through the
          same IO request mechanism used by NetWare to obtain disk service.

          The TAPEDAI.DSK driver must be loaded prior to loading the SBACKUP
          utility.  If the driver is used often, the user may want to load it
          from within the STARTUP.NCF file.  However, with NetWare 4.0x and
          3.12, if the TAPEDAI.DSK driver is loaded anywhere other than the
          STARTUP.NCF file (i.e., the server console prompt or the
          AUTOEXEC.NCF file) the command "SCAN FOR NEW DEVICES" will need to
          be executed after the driver is loaded and before SBACKUP is loaded
          or the tape drive will not be seen.

     Dependencies

          The TAPEDAI.DSK driver targets any ASPI compliant disk drivers. 
          Check with the driver manufacturer to confirm ASPI compliancy.

          Consequently,  the ASPI compliant disk driver must be loaded prior
          to loading TAPEDAI.DSK.

     Target Devices

          The TAPEDAI.DSK driver has been tested (not necessarily certified)
          with the following devices:

          Manufacturer    Product                 

          ARCHIVE         Python
          CIPHER          T826 (half inch - 2.6 Gig)
          CIPHER          T860 (half inch - 6 Gig)
          EXABYTE         EXB-8500                        
          HP              HP35450A                        
          HP              HP35470A*                       
          HP              HP35480A*
          TANDBERG        TDC 3800
          TANDBERG        TDC 4100
          TANDBERG        TDC 4200
          WANGDAT         1300
          WANGDAT         3200
          WANGTEK         5525ES
          WANGTEK         6130
          WANGTEK         WANGTEK_6130_HS 

     A GENERIC driver has been added to the TAPEDAI.DSK driver, which will
     support most SCSI interface tape drives (the ONLY Exabyte that will work
     with TAPEDAI.DSK is the EXB-8500 -- all others will not be seen).  Novell
     makes no guarantee as to the correct functionality of any drive not
     listed above.  The user assumes all responsibility for testing their tape
     drive solution with SBACKUP to ensure correct functionality.

          * (The HP35470A and HP35480A must be set through their dip switches
          so that the SCSI Valid Bit is set upon crossing Early Warning.  If
          this is not done, sessions that span tapes won't be reliable.  Users
          should perform a test backup and restore across tapes to confirm
          that the switches are set properly.  The file that actually spans
          tapes is the one to test.)

     SMDR.NLM        

          Storage Management Data Requester.  Controls transfer of data and
          commands between the SBACKUP engine and the TSA.

     TSA Files
     
          TSA311.NLM
               Target Service Agent for the NetWare 3.11 server.  The program
               loads in conjunction with the SMDR31x.NLM program.  The file
               allows a 3.11 server to be backed up or restored from a 3.12 or
               4.0x server.

          TSA312.NLM
               Target Service Agent for the Netware 3.12 server.

          SMDR31x.NLM
               Support module for the NetWare 3.1x service agents.

          TSA400.NLM
               Target Service Agent for the NetWare 4.0x server.

          TSA_DOS.NLM
               Target Service Agent for DOS clients.  This file is used in
               conjunction with the TSA_SMS.COM file.

          WS_MAN.NLM
               This file is the support module for the TSA_DOS.NLM file.

          TSA_OS2.NLM
               Target Service Agent for OS/2 clients.  This file is used in
               conjunction with the TSA_SMS.COM file for OS/2.


