NetWare v3.11 and SBACKUP on Apricot SCSI based servers

With NetWare v3.11, Novell supply a server-based backup utility called SBACKUP. This software can be used in conjunction with a SCSI based tape drive to back up a NetWare v3.1x server. Initially, NetWare v3.11 was released with SBACKUP v3.11. Since then, Novell have issued an update to SBACKUP, version 3.11b, that overcomes a number of issues found with the initial release. This new release can be obtained through Novell's NetWire service, from most NetWare distributors, or from the Apricot Technical Support BBS (from File Area 37 as a file called SBACKUP.ZIP).

Apricot currently supply two types of SCSI controllers for their FTs and FTe servers (the Adaptec AHA1640 card and the BusLogic BT-646S), and one SCSI controller for the XEN-LS II systems (the Adaptec AHA1510). SCSI tape drives, such as the Archive 150MB and 525MB tape streamers, and the Archive Python 1.3GB DDS, can be used in conjunction with these adapters. (Please note however that the Apricot ESDI/SCSI (or Petrel) card does not support the use of SCSI tape devices.)

To successfully implement SBACKUP on an Apricot SCSI based server, two things need to be observed.

Firstly, the ASPI (Advanced Scsi Programming Interface) driver needs to be loaded for the SCSI card being used. In the case of the Adaptec AHA1640 and AHA1510 cards, the Adaptec ASPI module, ASPITRAN.DSK, is loaded automatically as the disk driver (AHA1640.DSK or AHA1510.DSK) loads. With the BusLogic controller, the BusLogic ASPI module does NOT load automatically, so should be explicitly loaded from the server's STARTUP.NCF as follows......

load BT311 port=330 (loading the disk driver)
LOAD BTASPI (loading the ASPI module)

Secondly, SBACKUP version 3.11b should be used. When installing SBACKUP version 3.11b, it is essential that ALL the files from the SBACKUP.ZIP archive be copied to SYS:SYSTEM, as a partial upgrade will result in SBACKUP not operating at all. In order to achieve this, flag all the .DSK and .NLM files in SYS:SYSTEM read-write (rw), copy over the files from SBACKUP.ZIP, and then flag all the .DSK and .NLM files read-only (ro).

SBACKUP v3.11b with an Archive 150MB or 525MB SCSI Tape Streamer.

1. Ensure that the ASPI module for the SCSI card in the server has been loaded
   • For an Adaptec AHA1510, that would mean loading AHA1510.DSK, which would auto-load ASPITRAN.DSK.
     
   • For an Adaptec AHA1640, that would mean loading AHA1640.DSK, which would auto-load ASPITRAN.DSK.
     
   • For a BusLogic BT-646S, that would mean loading BT311.DSK and then loading BTASPI.DSK.
2. Load the NetWare Target Service Agent module, TSA.NLM. This module enables the transfer of data between the server disk system and the tape unit.
3. Load SBACKUP.NLM. After logging on to the server with a suitable username to enable a full system backup (such as supervisor), select the 'HP DIBI-2 Tape Driver' option from the list of device drivers. This will then check the ASPI interface and report back any devices found (typically this will just be the tape drive installed in the server). Ensure the device you want to use is highlighted, and press return. You can then continue to use SBACKUP as usual.

SBACKUP v3.11b with an Archive Python 1.3GB SCSI DDS drive.

With the new version of SBACKUP, two new drivers are included for use with certain tape drives (see SBACK1.DOC from the archive for full details). One of the drives listed is the Archive Python DDS drive. If your server includes an Archive Python DDS drive, you should therefore do the following (fully explained in SBACK1.DOC).....

Before loading SBACKUP, you will need to edit the DIBI2$DV.DAT file that is kept in the SYS:SYSTEM\DIBI directory. SBACK1.DOC explains this procedure, but we have supplied a sample DIBI2$DV.DAT file in SBACKUP.ZIP that has the changes already made, so you should just copy this into the SYS:SYSTEM\DIBI directory over the existing version (you should take a backup copy of the existing file, flag it rw, copy over the new file then flag it ro).

1. Ensure that the ASPI module for the SCSI card in the server has been loaded
   • For an Adaptec AHA1510, that would mean loading AHA1510.DSK, which would auto-load ASPITRAN.DSK.
     
   • For an Adaptec AHA1640, that would mean loading AHA1640.DSK, which would auto-load ASPITRAN.DSK.
     
   • For a BusLogic BT-646S, that would mean loading BT311.DSK and then loading BTASPI.DSK.
2. Load the PHYSADDR.DSK module. This is a support file for the Novell TAPEDAI.DSK driver and is needed.
3. Load the TAPEDAI.DSK module. TAPEDAI.DSK is a NetWare 386 device driver written to control certain tape devices such as the Archive Python DDS.
4. Load the NetWare Target Service Agent module, TSA.NLM. This module enables the transfer of data between the server disk system and the tape unit.
5. Load SBACKUP.NLM. After logging on to the server with a suitable username to enable a full system backup (such as supervisor), select the option from the list of device drivers that has been set up for the DIBIDAI interface (if using the sample DIBI2$DV.DAT file supplied, this option will be listed as 'ASPI Compliant Driver.'). This will then check the ASPI interface and report back any devices found (typically this will just be the tape drive installed in the server). Ensure the device you want to use is highlighted, and press return. You can then continue to use SBACKUP as usual.
   
   The SBACKUP.ZIP archive contains a NetWare command file called SBACK.NCF that will load the extra modules needed for the Archive Python DDS drive. It is recommended that the appropriate commands be built into the AUTOEXEC.NCF file if the tape system is to be used regularly.

The DIBIDAI.DSK module is used with SBACKUP to present a DIBI interface to SBACKUP, and then translates the DIBI requests into NetWare DAI calls. This results in device driver calls getting passed to TAPEDAI.DSK through the same I/O request mechanism used by NetWare to obtain disk service.

The file SBACK1.DOC explains the complete installation process for this version, along with an explanation of the new files and their purposes, and also includes a useful tips and info section. We strongly recommend that this document file is read fully prior to implementing version 3.11b of SBACKUP.

Additional SBACKUP Recommendations:

1. Once SBACKUP is loaded, leave it loaded. Every time SBACKUP is unloaded, it will fail to release 28 resources from the short term memory pool. After repeated unloads, this could cause the server to crash.
2. Do not make Appended backups. You should always ensure that the 'Append this session' option at the bottom of the 'Backup Options' screen within SBACKUP is set to NO. Certain tape backup devices, such as the Archive 150MB SCSI tape streamer, do not support this mode of backup, and will give errors when backing up to or restoring from a tape if Appended mode is used.

----------oOo----------