2.1 Preparing to Use SBCON

2.1.1 Memory Requirements

To run the SBCON utility, the host server requires the following:

  • A minimum of 3 MB free memory for SBCON

  • Memory required to run NetWare 6.5 (currently 256 MB RAM)

  • Memory required to run the clients

If 3 MB of memory is not available, try setting the storage buffers lower than the default and still run the utility.

2.1.2 GuideLines to Use SBCON

Before you start SBCON and begin backups, follow these guidelines to make backups easier and to avoid problems later:

  • Log in: You will have limited success backing up and restoring if you log in without the Supervisor right.

    For security reasons, many SBCON options are limited to the network administrator.

  • Reserve disk space for temporary files: Make sure you have disk space available (1 to 2 MB) on the target server’s volume sys: to accommodate log and error files.

    SBCON creates temporary files on the target server during backup. If you have linked UNIX* files or files with extended attributes, the temporary files might be larger than 1 MB.

  • Do not mount or dismount volumes on NetWare or mount points on SLES during a backup or restore session: The data might be corrupted or an association might occur at the host server.

  • Use the correct name space and name space formats: If you do not use the correct name space and name space formats when entering paths and file names, files can’t be restored.

    Name spaces: NFS, and Long

    Name space formats:

    • For Macintosh, use Volume::directory:directory:filename

    • For NFS on Linux use /directory/directory/filename

    • For all others, use Volume:/directory/directory/filename

  • Exit SBCON before unloading drivers: If you unload a manually loaded driver (such as aha1740.dsk or aspitran.dsk) before exiting SBCON, you might cause the host server to abend.

  • Use original case for non-DOS names: Non-DOS pathnames and filenames are case sensitive. NetWare recognizes DOS pathnames and filenames only in uppercase. If you’re not sure of the original case, refer to your log file.

2.1.3 Loading Controller and Storage Device Drivers on the Server

Controller and device drivers control the mechanical operation, such as read, write, forward, back, and stop of various storage devices and media.

Ensure that you have installed the storage device controller and storage device according to the hardware manufacturer’s instructions.

When NetWare 6.5 is installed, the entries for the device drivers are automatically listed in the startup.ncf file.

Whenever you want to add new drivers, you can either list them in startup.ncf or use the following steps:

  1. At the server console prompt, enter:

    load controller_device_driver_names
    
    load storage_device_driver_names
    

    For example, to load the drivers from drive C:, enter:

    load scsi154x.hamport=24

    load scsihd.cdm

    load scsi2tp.cdm

  2. In NWCONFIG, select Driver Options > run hdetect.nlm from the server console.

  3. (Conditional) To register the storage device with the system, enter the following at the server console prompt:

    scan for new devices

    NOTE:If you load the drivers from the startup.ncf file, you do not need to use the scan for new devices command.

    To check the list of devices, enter the following at the server console prompt:

    list devices

2.1.4 Loading SBCON

To load SBCON from the server command line:

  1. At the server console, enter

    smsstart
    

    TSAFS and SMDR modules are loaded with default configuration values.

    TSANDS must be manually loaded for backup and restoration of Novell® eDirectory™.

    QMAN and SMSDI are auto loaded along with SBCON.

    For starting up SMS services on SLES machines see, NetWare 6.5 Storage Management Services Administration Guide.

  2. Load SBCON by entering

    load sbcon