NOVELL TECHNICAL INFORMATION DOCUMENT
TITLE: Latest sbackup.nlm and supporting files
README FOR: SBACK6.EXE
NOVELL PRODUCTS and VERSIONS:
NetWare 3.11
NetWare 3.12
NetWare 4.02
NetWare 4.1
ABSTRACT:
This self-extracting file provides the current SBACKUP.NLM and supporting
files for 3.1X and 4.XX. The file SMSUPX.EXE (where X is the current revision
number of the file) should also be downloaded for the current TSA, SMDR, and
other support NLM's. SBACK6.EXE differs from SBACK5.EXE only in the file
SMSDI.NLM.
-----------------------------------------------------------------
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.
-----------------------------------------------------------------
ISSUE:
Several new features have been added to the 4.xx SBACKUP.NLM, including the
following:
1) The ability to recreate the log file from tape: this feature is in the
log/error file administration menu as "create session files".
2) The ability to search a log file for a string: this feature appears
when viewing log/error files.
3) Zeros the end of Transfer Buffers if not filled.
4) Confirm action before doing any Media Utilities procedures.
5) Increases backup display capacity from 4.2 gig to 4.2 Terrabytes per
session.
SMSDI.NLM:
Errors such as "media not present" have been resolved.
Self-Extracting File Name: sback6.exe
Files Included Size Date Time
..\
SBACK6.TXT (This file)
..\31X\
DIBIDAI.NLM 17315 1-12-94 9:05:50 am
NOVADIBI.NLM 17119 3-31-92 12:08:20 pm
SBACKUP.NLM 184708 3-28-95 5:44:42 pm
WANGTEK.NLM 15681 7-18-91 3:37:18 pm
..\4XX\
SBACKUP.NLM 250540 8-2-95 10:16:08 am
SMSDI.NLM 139296 12-21-95 1:17:20 pm
..\COMMON\
TAPEDAI.DDI 2484 12-14-94 11:09:34 am
TAPEDAI.DSK 33997 10-3-94 8:33:28 am
..\LANGUAGE\
..\LANGUAGE\ENGLISH\
SMSDI.MSG 8668 8-10-95 11:14:44 am
..\LANGUAGE\FRENCH\
SMSDI.MSG 9653 10-27-94 9:32:08 am
..\LANGUAGE\GERMAN\
SMSDI.MSG 9873 10-25-94 12:50:34 pm
..\LANGUAGE\ITALIAN\
SMSDI.MSG 9823 10-27-94 2:46:44 pm
..\LANGUAGE\SPANISH\
SMSDI.MSG 9068 10-26-94 3:01:52 pm
Installation Instructions:
Copy the files from the COMMON directory to SYS:SYSTEM on all 3.X and 4.X
servers. Copy the files from the 31X and 4XX directories according to server
version, again to the SYS:SYSTEM directory. Existing files with similar names
should be flagged RW in order for the copy to occur (rename or move the
existing file to a new location to maintain a copy if desired).
For 4.xx, the appropriate SMSDI.MSG file(s) in the \language subdirectories
should be copied to sys:system\nls\<language>, where <language> is one or more
of the five supported languages as shown on the file listing.
SFTIII
For SFTIII 3.11, the Sbackup.nlm and supporting driver files are loaded in the
IOengine. The TSA311.NLM module from SMSUPX.EXE is loaded in the MSengine. For
SFTIII 3.11, patches and shims from download file SFTITX.EXE ("X" represents
the download file version) on the NSD forum of compuserve must be loaded as
recommended and described in that file.
For SFTIII 4.10, Sbackup.nlm loads in the MSengine along with the
TSAxxx.NLM's. Tapedai and the HBA driver still load in the IOengine.
Module Dependencies
Sbackup is dependent on the modules listed below. It is recommended that you
upgrade to the versions of these modules listed or later. Current versions of
these files are available on Compuserve's NOVLIB forum, library 04, in download
files LIBUPX.EXE and STRTLX.EXE, where "X" denotes the current download file
revision.
3.1x
after311.nlm 3-29-94 (LIBUPX.EXE)
a3112.nlm 3-29-94 (LIBUPX.EXE)
clib.nlm 5-19-94 (LIBUPX.EXE)
spxs.nlm 5-17-94 (STRTLX.EXE)
streams.nlm 7-20-93 (STRTLX.EXE)
tli.nlm 9-14-93 (STRTLX.EXE)
4.0x
clib.nlm 5-25-94 (LIBUPX.EXE)
spxs.nlm 3-02-94 (STRTLX.EXE)
streams.nlm 9-14-93 (STRTLX.EXE)
tli.nlm 9-14-93 (STRTLX.EXE)
dsapi.nlm 6-03-94 (LIBUPX.EXE)
***************
** 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. At
the present time SBackup does NO READ-AFTER-WRITE verification of the data that
is backed up. Therefore it is important that you verify your backups manually.
It is recommended that you do this with every backup set that you make and
should be made a regular step in your backup procedures.
Explanation of TAPEDAI and DIBIDAI files:
TAPEDAI.DSK
TAPEDAI.DSK is a NetWare 386 device driver written to control certain tape
devices. It is used in conjunction with DIBIDAI.NLM in 3.1x servers.
TAPEDAI.DSK does not require DIBIDAI.NLM in a 4.x server.
DIBIDAI.NLM presents a DIBI interface to SBACKUP.NLM (on 3.1x only), but
translates the DIBI requests into NetWare DAI calls. This eventually results in
device driver calls getting passed to TAPEDAI.DSK through the same IO request
mechanism used by NetWare to obtain disk service. Note that 3.11 SFTIII
requires NOVADIBI.NLM, DIDIDAI.NLM is not compatible.
TAPEDAI.DSK must be loaded prior to loading SBACKUP. If it is used often, the
user may want to load it from within the STARTUP.NCF file.
In order to use TAPEDAI.DSK and DIBIDAI.NLM the DIBI2$DV.DAT file in
SYS:SYSTEM\DIBI may require editing to include DIBIDAI.NLM. The DIBI2$DV.DAT
file is a DOS text file and can be edited using EDIT.NLM or with any DOS text
editor from a workstation.
Editing the Dibi2$dv.dat file in the system\dibi subdirectory:
1. Flag the file as read/write.
2. Use a text editor to edit the file. If editing the file using the
EDIT.NLM type the following at the console prompt:
"LOAD EDIT SYS:SYSTEM\DIBI\DIBI2$DV.DAT"
3. When the file is brought up it may look like this:
"Wangtek Tape Drive." WANGTEK PORT=280 DMA=3 IRQ=5
"HP DIBI-2 Tape Driver." NOVADIBI
"DC00 DIBI-2 Tape Driver." TAPEDC00
A line like the following will need to be added:
"DibiDai Driver." DibiDai
The description on the left can be anything. The DibiDai on the right refers
to the the DibiDai.nlm.
4. Exit the editor and save changes.
Tape devices supported by TAPEDAI.DSK:
Manufacturer/Product
ARCHIVEAnaconda
ARCHIVEPython
ARCHIVEViper 2525
CIPHER T826 (half inch - 2.6 Gig)
CIPHER T860 (half inch - 6 Gig)
DEC ARDAT TLZ06
EXABYTEEXB-8500
HP HP35450A
HP HP35470A*
HP HP35480A*
HP C1553A (DDS2, 4mm DAT magazine)
HP C1533A (DDS2, 4mm DAT)
TANDBERG TDC 3800
TANDBERG TDC 4100
TANDBERG TDC 4200
WANGDAT1300
WANGDAT3200
WANGTEK5150
WANGTEK5525ES
WANGTEK6130
WANGTEKWANGTEK_6130_HS
*(The HP35470A and HP35480A must be set through its 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.)
Tape devices supported by PS2SCSI.DSK:
Exabyte 8200, 8mm
Exabyte 8500, 8mm
HP 35470, 4mm DAT
HP 35480A, 4mm DAT
HP 35450A, 4mm DAT
WangDat 3200, 4mm DAT
WangDat 1300, 4mm DAT
Archive Python, 4mm DAT
Cipher T860s, half inch tape
-----------------------------------------------------------------
Any trademarks referenced in this document are the property of their
respective owners. Consult your product manuals for complete trademark
information.
-----------------------------------------------------------------
