Novell is now a part of Micro Focus

SBACKUP Configuration and Usage Notes

Articles and Tips: article

01 Aug 1995


This document covers various technical aspects of installing, configuring, and using the NetWare 4.1 release of SBACKUP.NLM and its associated support modules. This information is adapted from an SBACKUP training document produced by Novell Technical Services.

Introduction

This document covers various technical aspects of installing, configuring, and using the NetWare® 4.1 release of SBACKUP.NLM and its associated support modules. This information is adapted from an SBACKUP training document produced by Novell Technical Services.

The terms "host" and "target" are used throughout this document. Host refers to a file server with a tape drive attached and that is running SBACKUP.NLM. Target refers to any server or workstation with the appropriate Target Service Agent (TSA) module loaded.

Compatibility Issues

The TSAxxx NetWare Loadable Modules™ (NLMs) for SBACKUP have undergone major changes their initial release with NetWare 3.11. Incompatibility problems experienced in the past between SMS TSAs and SBACKUP's supporting modules (SMDR.NLM, SMDR31X.NLM, and so on) have been resolved with the release of NetWare 4.1. The necessary SBACKUP support modules are now compatible with all versions of NetWare, and with each other. These include SMDR.NLM, TAPEDAI.NLM, and all TSA xxx.NLM components. The only exception is SBACKUP.NLM itself. A different SBACKUP.NLM is required if a NetWare 3.1x server is used as the SBACKUP host.

As of this writing, the current versions of the files necessary to run SBACKUP in a NetWare 3, NetWare 4, or mixed NetWare 3-4 environment are found in the SMSUP2.EXE and SBACK3.EXE files available on NetWire and on Novell's World Wide Web site on the Internet.

Loading the SBACKUP Software

This section lists the dependent modules that SBACKUP.NLM needs when loaded on a host server, a target server, and a combination host-target server. It also gives some examples of loading the SBACKUP software with various types of server and backup device hardware.

Module Dependencies

When SBACKUP.NLM or TSA xxx. NLM is loaded on a file server, several other NLMs will be automatically loaded (if they are not already loaded).

Below are lists of modules that are necessary for SBACKUP to function. The indication A(manual)@ identifies those that you must load manually by typing a LOAD module command.

Host Server (NetWare 4) SBACKUP.NLM(manual) SMSDI.NLM TAPEDAI.NLM(manual - optional depending on controller )

Target Servers TSA xxx.NLM(manual) WSMAN.NLM(autoloads when TSADOS is loaded)

Host-and-Target Servers CLIB.NLM STREAMS.NLM TLI.NLM SPXS.NLM SMDR.NLM DSAPI.NLM(NetWare 4 server only) AFTER311.NLM(NetWare 3.1x server only) A3112.NLM(NetWare 3.1x server only)

Make sure you have the latest versions of all modules that autoload with SBACKUP. CLIB and the update NLMs for NetWare 3 servers are found in the LIBUP5.EXE file. STREAMS, TLI, and SPXS are found in the STRTL3.EXE file. Both files are available on NetWire and on Novell's World Wide Website on the Internet.

Load Command Examples

This section provides several examples of loading SBACKUP software for host and target servers and for target workstations. The examples cover several types of host bus adapters that can be used in the host server to support the tape device. Many other variations are possible beyond those shown here.

NetWare 4 (Non-SFT III) Host Server

Adaptec Controller

  1. Place the following command in the server's STARTUP.NCF file:

    SET RESERVED BUFFERS BELOW 16 MEG=200

  2. Load the driver that comes with the Host Bus Adapter. For an Adaptec 1740 controller, you would load AHA1740.DSK with ASPITRAN.DSK.

  3. Load TAPEDAI.DSK.

  4. Issue the following command (unless TAPEDAI.DSK is loaded in the STARTUP.NCF file):

    SCAN FOR NEW DEVICES

  5. Load SBACKUP.NLM

  6. If this Host server is also going to be a Target, load TSAxxx as described later.

Compaq (using a Compaq tape drive)

  1. Place the following command in the server's STARTUP.NCF file:

    SET RESERVED BUFFERS BELOW 16 MEG=200

  2. Load CPQSXPT.

  3. Load CPQS710.

  4. Insert the tape into the tape drive.

  5. Load CPQSTAPE.

  6. Load SBACKUP.NLM.

Compaq (using a tape drive supported under TAPEDAI)

  1. Place the following command in the server's STARTUP.NCF file:

    SET RESERVED BUFFERS BELOW 16 MEG=200

  2. Load CPQSXPT.

  3. Load CPQS710.

  4. Load CPQSASPI.

  5. Load TAPEDAI.

  6. Issue the following command (unless TAPEDAI.DSK is loaded in the STARTUP.NCF file):

    SCAN FOR NEW DEVICES

  7. Load SBACKUP.NLM

IBM (using the .DSK method)

  1. Place the following command in the server's STARTUP.NCF file:

    SET RESERVED BUFFERS BELOW 16 MEG=200

  2. Load PS2SCSI.DSK. (You should see the tape drive listed when you type the LIST DEVICEScommand at the server console.)

  3. Load SBACKUP.NLM.

PS2SCSI.DSK supports the following tape devices:

  • 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, 2 inch tape

IBM (using the .HAM/.CDM method)

  1. Place the following command in the server's STARTUP.NCF file:

    SET RESERVED BUFFERS BELOW 16 MEG=200

  2. Load SCSIPS2.HAM.

  3. Load SCSI2TP.CDM.

  4. Issue the SCAN FOR NEW DEVICEScommand.

  5. Load SBACKUP.NLM.

SCSI2TP.CDM supports the same backup devices as TAPEDAI.DSK (these are listed under the heading "Using TAPEDAI" later in this document).

NetWare SFT III Host Server

NetWare SFT III requires modules for SMS and SBACKUP to be loaded in the proper engines (IOengine or MSengine). For both NetWare SFT III 3.11 and 4.1, the drivers for the host bus adapter are loaded in the IOengine. All TSAs load in the MSengine.

The main difference between NetWare SFT III 3.11 and 4.1 is where SBACKUP.NLM itself is loaded. In version 3.11, SBACKUP.NLM loads in the IOengine; in version 4.1 it loads in the MSengine. For version 3.11, the IOSHIM and MSSHIM modules must also be loaded, along with their respective patch managers. These are available in the file SFTIT2.EXE which can be downloaded from the NSD area of CompuServe (GO NSD).

Here are some sample load sequence for NetWare SFT III 4.1 and 3.11 using an Adaptec AHA1740 Host Bus Adapter.

NetWare SFT III 4.1 with Adaptec 1740 Adapter

Load the following modules in the IOengine:

  1. Load AHA1740 (auto-loads ASPITRAN).

  2. Load TAPEDAI.DSK.

Load the following modules in the MSengine:

  1. Load TSA410.

  2. Load TSANDS.

  3. Load SBACKUP.NLM.

NetWare SFT III 3.11 with Adaptec 1740 Adapter

Load the following modules in the IOengine:

  1. Load IOSHIM.

  2. Load AHA1740 (auto-loads ASPITRAN).

  3. Load SBACKUP.NLM (select the HP DIBI-2 driver from the menu).

Load the following modules in the MSengine:

  1. Load MSSHIM.

  2. Load TSA311.

Target Servers

On target servers, load the appropriate TSA xxx modules according to the following table.


Module
Description

TSA311.NLM

Load on a NetWare3.11 server for backup and restore of the 3.11 file system

TSA312.NLM

Load on a NetWare3.12 server for backup and restore of the 3.12 file system

TSA400.NLM

Load on a NetWare4.01 or 4.02 server for backup and restore of the 4.0x file system

TSA410.NLM

Load on a NetWare4.1 server for backup and restore of the 4.10 file system

TSANDS.NLM

Load on a NetWare 4.xx server for backup and restore of NetWare Directory Services (only needs to be loaded on one 4.xx server in the tree, preferablyone with a copy of the largest partition)

TSADOS.NLM

Load on NetWare 3.1x and 4.xx servers for backup and restoreof attached DOS workstations

TSAPROXY.NLM

Load on NetWare 3.1x and 4.xx servers for backup and restore of attached OS/2, Macintosh, and UnixWare workstations

Target Workstations

To back up workstations with SBACKUP, load the appropriate TSA module for the type of target workstation. Currently, Novell provides TSAs for DOS, OS/2, Macintosh, and UnixWare workstations. A brief rundown of TSA configuration is given below. Refer to the SBACKUP documentation for more information about loading and configuring TSAs for workstations.

DOS Workstations. On target DOS workstations, run TSASMS.COM according to the following instructions (taken from the online help).

Usage:

tsasms /h
tsasms /b=buffers /d=drive [/n=name]
[/p=[password]] [/se=server] /st'size [/t]
tsasms /u

The TSA parameters are:


/h[elp] or ?

Displays this help message

/b[uffers]=buffers

TSA Buffers (1KB) forfaster access (1-30)

/d[rive]=xxx

DOS Drives to Use where x=DriveLetters

/n[ame]=name

Workstation Name for Server NLM

/p[assword]=[password]

User password

/se[rver]=server

Name of server to connect to

/st[ack]=stacksize

Decimal stack size (512to 4096 bytes)

/t[rust]

Trust the system administrator to backup/restore

/u[nload]

Unload TSASMS from memory

For example, to specify the server as FS1, the workstation name as WS1, and indicate that you trust the system administrator to back up local drive C, type:

TSASMS /se=FS1 /n=ws1 /d=c /t

TSASMS parameters can also be specified in the NET.CFG file. You can add the parameters when installing the NetWare DOS Requester (VLMs) or later using any standard ASCII text editor. The syntax is as follows:

NetWare DOS TSA
  TSA Server Name=FS1
  Workstation Name=WS1
  Password=John
  Disk Buffers=2
  Stack Size=2048
  Drives=C

Parameters specified from the command line override parameters in the NET.CFG file. For example, a user could override the TSA Server Name parameter by entering TSASMS /se=FS2. This would change the server to attach to from FS1 to FS2.

OS/2 Workstations. For target OS/2 workstations, a graphical utility called TSAOS2.EXE can be loaded either from an OS/2 command prompt or from the TSAOS2 icon in the Novell group. Parametersfor TSAOS2.EXE can be configured using the appropriate menu options, or they can be loaded at runtime from a file named TSAOS2.CFG, which must reside in the same directory as TSAOS2.EXE.

A sample TSAOS2.CFG file is as follows:

WSName        WS1
ServerName    FS1
UserName      admin john
AutoRegister  On

You can use any standard ASCII text editor to create or edit the TSAOS2.CFG file.


Note: TSAPROXY.NLM must be loaded on the preferred server before theOS/2 client can register itself with that server.

Macintosh Workstations. For target Macintosh workstations, a graphical program is used to execute the MacTSA Prefs and MacTSA icons. The MacTSA Prefs icon opens a window that allows the user to enter the UserName, password, and preferred server name - for example: 

User Name: admin
Password: ****
Server: FS1

The user then clicks on the MacTSA to launch the TSA and make the Macintosh client available to the preferred server for backup and restore operations.


Note: TSAPROXY.NLM must be loaded on the preferred server before theMacintosh client can register itself with that server.

UnixWare Workstations. For target UnixWare workstations, the tsadand tsaunix files must be loaded on the workstation. You must also configure the /etc/hostsand /etc/unixtsa.conffiles. The /etc/hosts file must specify the TCP/IP address and name of the NetWare server. For example: 

130.11.1.12 sales2
130.11.1.13 fs1

The /etc/unixtsa.conf file must specify the name of the NetWare server and the protocol being used. For example:

sales2 spx
sales2 tcpip
fs1 tcpip

These files can be created or edited using any standard ASCII text editor. Once the files are properly configured on the target UnixWare workstation, you must load the tsad file and the tsaunixexecutable, in that order.


Note: TSAPROXY.NLM must be loaded on the preferred server before theUnixWare client can register itself with that server.

DIBI, DAI, DIBIDAI and TAPEDAI Explained

This section explains the relationship between Device Independent Backup Interface (DIBI), Device Application Interface (DAI), DIBIDAI.NLM, and TAPEDAI.DSK in both the NetWare 3 and NetWare 4 environments.

NetWare 3 Environment

Device Independent Backup Interface (DIBI) is a specification designed by Novell. SBACKUP.NLM for NetWare 3.11 and 3.12 uses DIBI calls to access the tape device(s). The tape device, however, expects to be accessed using Device Application Interface (DAI) calls. The DIBIDAI.NLM is used to translate calls between SBACKUP and the DAI device drivers (such as TAPEDAI.DSK).

TAPEDAI.DSK is a device driver written to control certain tape devices. It is used with DIBIDAI.NLM on NetWare 3.1x servers.

Figure 1 shows the interaction of these various layers in the NetWare 3 environment.

Figure 1: Interaction between SBACKUP and related modules in the NetWare 3 server environment.

Editing the DIBI2$DV.DAT File. To use TAPEDAI.DSK and DIBIDAI.NLM, the DIBI2$DV.DAT file in SYS:SYSTEM\DIBI may require editing. SBACKUP scans this .DAT file to see what drivers to include on the initial SBACKUP menu, which is used for driver for selection. In NetWare 3.11, DIBIDAI.NLM was not one of the default choices.

The DIBI2$DV.DAT file is a DOS text file and can be edited using EDIT.NLM at the server or any DOS text editor from a workstation. To edit the DIBI2$DV.DAT file in the SYSTEM\DIBI subdirectory, follow these steps:

  1. Using FILER or FLAG, flag the DIBI2$DV.DAT file as read/write.

  2. Start your text editor and retrieve the file. If you are editing the file using EDIT.NLM, type the following at the console prompt:

    LOAD EDIT SYS:SYSTEM\DIBI\DIBI2$DV.DAT

  3. When the file is displayed, it will look something like this:

    "Wangtek Tape Drive"           WANGTEK  PORT=280  DMA=3  IRQ=5
"HP DIBI-2 Tape Driver"        NOVADIBI
"DC00 DIBI-2 Tape Driver"      TAPEDC00

    Add a line similar to the following: "DibiDai Driver" DibiDai

    The description string on the left can be anything. The string DibiDaion the right refers to DIBIDAI.NLM.

  4. Exit the text editor and save your changes.

NetWare 4 Environment

On a NetWare 4 server, TAPEDAI.DSK does not require DIBIDAI.NLM. NetWare 4 and SBACKUP for NetWare 4 no longer use the DIBI interface. They use the Media Manager instead.

Figure 2 shows the interaction of the various layers in the NetWare 4 environment.

Figure 2: Interaction between SBACKUP and related modules in the NetWare 4 server environment.

Using TAPEDAI.DSK

TAPEDAI.DSK targets any ASPI-compliant disk driver. Consequently, an ASPI-compliant disk driver (such as ASPITRAN.DSK or CPQSASPI.DSK) must be loaded prior to loading TAPEDAI.DSK. In both NetWare 3 and 4, TAPEDAI.DSK or equivalent functionality must be loaded prior to loading SBACKUP. If SBACKUP is used often, the administrator may want to load TAPEDAI.DSK from within the STARTUP.NCF file to avoid having to enter the SCAN FOR NEW DEVICES command that is required if TAPEDAI.DSK is loaded after STARTUP.NCF.


Note: TAPEDAI.DSK is not needed when using PS2SCSI.DSK for IBM or whenusing CPQSTAPE for Compaq. Tape support is built into these drivers.

TAPEDAI works with the devices listed in the following table.


Manufacturer
Device

Archive

Anaconda

Archive

Python

Archive

Viper 2525

Cipher

T826 (1/2 inch - 2.6 GB)

Cipher

T860 (1/2 inch - 6 GB)

DEC

ARDAT TLZ06

Exabyte

EXB-8500

Hewlett-Packard

HP 35450A

Hewlett-Packard

HP 35470A*

Hewlett-Packard

HP 35480A*

Hewlett-Packard

C1553A (DDS2, 4mm DAT)

Hewlett-Packard

C1533A (DDS2, 4mm DAT magazine)

Tandberg

TDC 3800

Tandberg

TDC 4100

Tandberg

TDC 4200

WangDAT

1300

WangDAT

3200

Wangtek

5150

Wangtek

5525ES

Wangtek

6130

Wangtek

6130 HS

* The HP 35470A and HP 35480A must be set through 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.

SBACKUP Usage Notes

This section presents notes and tips on using SBACKUP to achieve the desired backup/restore results. These notes cover the most commonly asked questions about using SBACKUP. The examples are for the NetWare 4 version of SBACKUP, except as noted otherwise.

Include/Exclude Options

SBACKUP's include and exclude options can be used to perform a custom backup or restore, in which only certain data is actually backed up or restored. To decide whether to use Include or Exclude, compare the amount of data to be backed up or restored with the amount of data not to be backed up or restored. Use the following guidelines to help you decide.

When to Use Exclude. To back up or restore most of the data while omitting only a small part, use Exclude to omit the unwanted data. Everything you don't specifically Exclude is Included. Be aware that once a directory is Excluded, all files and subdirectories below that directory will not be backed up or restored. Once a directory has been Excluded, Include cannot be used to override the exclusion of any subdirectories or files beneath that point.

For example, if you list SYS:MAIL under Exclude Directories, none of the user's mail subdirectories (or the files they contain) will be backed up.

When to Use Include. To back up or restore a relatively small part of the directory structure, use Include to list the desired data. Everything that is not specifically Included is automatically Excluded. Unlike Exclude, however, subdirectories and/or files beneath the specified Include can then be selectively Excluded.

For example, if you list SYS:PUBLIC under Include Directories, the PUBLIC directory, along with all of its files and subdirectories, will be backed up or restored. If desired, you can exclude the \NLS subdirectory and its files from the backup or restore by listing SYS:PUBLIC\NLS in the Exclude Directories list.

Directing SBACKUP to the Desired Target

To direct SBACKUP to the desired target workstation, server, file system, or NDS, do the following:

  1. From the main menu, select the option "Change Target to Back Up From or Restore To".

  2. A list of all servers running SMDR.NLM will be displayed. Select the desired server.

  3. If multiple TSAs are running on that server, select the desired TSA.

  4. Enter the UserName and password as prompted. If the administrative user's object exists in the current NDS context, you can simply enter the relative object name (for example, admin).

If you are in a different context, enter the UserName in typeful distinguished name format, with a leading dot (.). For example:

.cn=admin.ou=services.o=novell

Restoring a Single File to the Same Directory

Use the following steps to restore a single file to the same directory from which it was backed up. As an example, suppose you want to restore just the LOGIN.EXE file to SYS:LOGIN from a full server backup session.

  1. From the main menu, select Restore.

  2. From the Restore menu, follow the prompts to select the session to be restored (with or without session files). Enter/select the media and device as prompted.

  3. From the "Restoring from session name" menu, choose the option "Restore One File or Directory".

  4. Enter the file name (LOGIN.EXE in our example).

  5. Enter the directory name where the file existed when it was backed up (for example, SYS:LOGIN).

  6. Press <F10< to proceed with the restore.

Restoring a Single File to a Different Directory

Use the following steps to restore a single file to a different directory. As an example, suppose you want to restore SYS:LOGIN\LOGIN.EXE from a full server backup session to SYS:TEST\LOGIN.EXE.

  1. From the main menu, select Restore.

  2. From the Restore menu, follow the prompts to select the session to be restored (with or without session files). Enter/select the media and device as prompted.

  3. From the "Restoring From session name" menu, choose the option "Restore One File or Directory".

  4. Enter the file name under "Name of file" (for example, LOGIN.EXE).

  5. Enter the directory path where the file existed when it was backed up (for example, SYS:LOGIN) under the option "Name of directory (full path)".

  6. Enter the pathname of the directory to restore to under the option "Different location to restore to (full path)" (for example, SYS:TEST). If the path specified does not exist, it will be created.

  7. Press <F10< to proceed with the restore.

Restoring a Parent Directory

Use the following steps to restore a parent directory along with all of its subdirectories and files. As an example, suppose you want to restore the directories SYS:LOGIN, SYS:LOGIN\OS2, SYS:LOGIN\NLS, and SYS:LOGIN\NLS\ENGLISH, with all files in each of these directories, from a full server backup.

  1. From the main menu, select Restore.

  2. From the Restore menu, follow the prompts to select the session to be restored (with or without session files). Enter/select the media and device as prompted.

  3. From the "Restoring From session name" menu, choose the option "Restore One File or Directory".

  4. Leave the "Name of File" field blank. Enter the directory path of the parent directory to be restored (in the example, it would be SYS:LOGIN). Make sure "Include subdirectories" is marked Yes.

  5. Press <F10< to proceed with the restore.

Combining Volumes During a Restore

It is possible to combine the data from two volumes that were backed up separately onto a single volume during a restore. For example, suppose you backed up volumes SYS and VOL1, but now want to restore all of the data they contained to just volume SYS. Follow these steps:

  1. From the main menu, select Restore.

  2. From the Restore menu, follow the prompts to select the session to be restored (with or without session files). Enter/select the media and device as prompted.

  3. From the "Restoring From session name" menu, choose the option "Custom Restore".

  4. From the "Restore Options" menu, select the option "Restore data to different location".

  5. Insert the name of the source and destination locations (VOL1: and SYS:, respectively, for the example). Press <F10< to save.

  6. Press <F10< again to proceed with the restore.

Restoring Data from One Volume to Another Volume

It is possible to restore data from one volume to a directory on another volume. For example, suppose you backed up volumes SYS and VOL1, but now need to restore just the VOL1 data to volume SYS, subdirectory SYS:VOL1DATA. Follow these steps:

  1. From the main menu, select Restore.

  2. From the Restore menu, follow the prompts to select the session to be restored (with or without session files). Enter/select the media and device as prompted.

  3. From the "Restoring From session name" menu, choose the option "Custom Restore".

  4. From the "Restore Options" menu, select "Subsets of the Session to Be Restored".

  5. Select "Include Directories (Full Path)". For this example, you would insert the path SYS:VOL1DATA.

  6. Press <Esc< until you return to the "Restore Options" menu.

  7. Select the option "Restore data to different location". For this example, you would insert the name of the source location as VOL1:, and the destination location as SYS:VOL1DATA . Press <F10< to save.

  8. Press <F10< again to proceed with the restore.

Restoring the Bindery in NetWare 3

On a NetWare 3 server, the bindery is included by default in SBACKUP's Custom or Full Server backup options. However, it is not included by default during a restore. To include the bindery on a restore, follow these steps:

  1. From the main menu, select Restore.

  2. From the Restore menu, select "Custom Restore".

  3. Select "Subsets of the Session to be Restored".

  4. Select "Include Major TSA Resources".

  5. Press <Ins< and select "Bindery".

  6. Press <Esc< until you return to the Restore Session menu.

  7. Press <F10< to proceed with the restore.


Note: If the file system is restored before the bindery objectsexist, trustee assignments cannot be restored. Errors similarto the following are posted in the error log: "TrusteeTED was not restored for SYS:USERS\TED\ because the trustee IDsare different".

* Originally published in Novell AppNotes

Disclaimer

The origin of this information may be internal or external to Novell. While Novell makes all reasonable efforts to verify this information, Novell does not make explicit or implied claims to its validity.

© Copyright Micro Focus or one of its affiliates