Fastback Plus for OS/2   Version 1.0    Readme          Mar 15, 1994
=============================================================================

   Thank you for purchasing Fastback Plus for OS/2.  This file contains
some last minute information concerning the installation and use of Fastback
Plus for OS/2.
    Fastback Plus for OS/2 supports the following version levels of OS/2

     Version 2.0 with 2.10 Service pack ONLY.
     Version 2.10 release.
     Version 2.11 Service Pack.


SECTIONS:
=========
1.  Installation
2.  Fastback Object Classes
3.  Fastback Plus
4.  Fastback Procedure
5.  Floppy Support
6.  QIC Support
7.  SCSI support
8.  Network Drives, Hard Drives, Removables
9.  Setting CPU Priorities and Buffer Allocation
10.  Creating Recovery Disks
11.  Contacting Technical Support

1.  INSTALLATION:
=================

1.1 - Note on Install Procedure.

    Installation of Fastback Plus for OS/2 requires you to reboot.   At the end
of the first part of the installation process, INSTALL  will ask for a
confirmation to shut down.  You do not need to shutdown at this point, you may
switch to other applications, command shells, etc.  You must shutdown before
Fastback for OS/2 can be run, however.  When the system reboots, double click on
the Fastback Install Icon on the Desktop to complete the installation.

1.2 - Networks.

    Although Fastback Plus for OS/2 is fully compatible with Netware for OS/2,
IBM Lan Server, and Microsoft Lan Manager, do not attempt to install Fastback
Plus for OS/2 to a network resource.

    Central to the operation of Fastback Plus for OS/2 is one, or possibly two,
device drivers which will be installed.  For this reason, Fastback must be
installed LOCALLY.

If you have a diskless workstation that uses bootproms on the network card, then
you may install FB/2 on a network drive.

1.3 - HPFS naming.
    Fastback Plus should not be installed to an HPFS extended directory name.
In other words, you must install Fastback to a directory with up to 8 letters
and no spaces in the name.  Fastback will have no problems with backups or
restores from or to HPFS or FAT volumes, but for reasons involving the
device drivers used by Fastback Plus for OS/2, standard FAT directory naming
should be used when installing Fastback Plus.

1.4 - Changes made to config.sys.
    When Fastback Plus for OS/2 installation completes, your config.sys file
will have been backed up to a file named CONFIG.FBP.   Below is a list of the
changes made to the config.sys file:

    1.      The Fastback DLL directory  (ie C:\FASTBACK\DLL) will be added to
    the LIBPATH statement.

    2.  If SCSI support is desired, the OS2SCSI.DMD driver will be added as a
    BASEDEV statement if it is not there already.

        BASEDEV=OS2SCSI.DMD

        If you choose SCSI tape at install time you will also see a device entry
    in the config.sys as follows....

        DEVICE=C:\FASTBACK\DLL\FBSCSI.SYS

    3.      The Fastback HELP directory will be added to the HELP environment
    variable.

    4.  Fastback.sys will always be loaded from the config.sys.  It handles
    locked files at restore time.  Its syntax is....

        DEVICE=C:\FASTBACK\DLL\FASTBACK.SYS



1.5 - Uninstalling Fastback Plus for OS/2.

    Because Fastback Plus for OS/2 modifies the object hierarchy of OS/2, it
is very important that should you uninstall Fastback Plus, be sure to run
INSTALL from your distribution diskette again, and select "REMOVE" to complete
the removal.

    NOTE:    The DLL subdirectory of FASTBACK will be locked until its path is removed
from the LIBPATH statement in config.sys.  You will be unable to delete the
Fastback Plus for OS/2 directory until then.


2.  Fastback Object Classes:
============================

2.1 -  After Install.

    After install, you will notice that a Templates folder has been
created in the Fastback Folder.  This contains the Templates for the devices,
interface, and procedures that make up the Fastback Plus for OS/2 evironment.
Should problems occur with one or more objects, you can pull new objects from
this new templates folder after deleting the old ones.

2.2 - Device Objects.

    For multiple SCSI Devices, it would be preferable to have a separate object
for each tape drive, to allow ease of use.

2.3 - Rebuilding the Fastback Template Folder.

    Should for some reason one or more of the templates in the Fastback Plus
templates folder be deleted or damaged, a very simple way exists to rebuild it.
Simply open the OS/2 Templates Folder on your desktop, which issues a command
to recreate all templates that do not exist or are invalid.  If you want
multiple procedures or device icons, drag them from the Fastback Template folder.
It is an easy way to set up the backup environment you want.

3.  Fastback Plus:
==================

3.1 - For migrating DOS users.

    If you have ever used the DOS or Windows versions of the Fastback Plus
product, you will feel right at home clicking on the Fastback Plus
Icon.  It provides you with a menu driven interface similar to the ones found
in the DOS or Windows environment.

3.2 - Where is my drive?

    You have gone into Fastback Plus and you select "Backup To".  What you
see listed are names of icons that appear in the Fastback folder.  But you
don't see your 5.25 floppy drive listed here.   What to do?

    Step 1:
          Close Fastback Plus and open the Fastback Templates folder and drag
          a new floppy to the Fastback Folder.

    Step 2:
          Open the settings page of the new floppy icon and select hardware.

    Step 3:
          Select the type of drive and media that you wish to use.

    Step 4:
          Then turn to the General Page and change the title so that you will
          recgonize this as your drive icon.

    Step 5:
          Start Fastback Plus and go to "Backup To".  You should now see your
          drive in the list.



3.3 - Selective Restore

    When using the Fastback Plus user interface for selective restore from
a multi-volume backup, a certain procedure must be followed.  After restoring
the history file, Fastback Plus will know which particular volume or volumes
contain the files you have selected for restore, so that when the restore
operation begins, Fastback Plus can prompt for the correct volume without the
necessity of reading through each volume.
     In order for this feature to function, however, you a certain procedure
must be followed.

     1. Retrieve your history file after setting restore from device.
     2. Select the appropriate set ( refer to user's manual for these steps ).
     3. Select Choose Files from the Restore menu.
---> 4. After making the necessary file selections, do not exit Choose Files,
         but instead, select the "Go" button (the right pointing arrowhead)
         and go directly to the operation progress.
     5. Click the Restore Button from the Progress panel which appears.
     6. Fastback Plus will begin the Selective Restore, prompting for the
         appropriate volumes, and ending the operation when all the selected
         files have been restored.



4.  Fastback Procedure:
=======================

4.1 - Chooser View

    The "Chooser View" is the window that you get when you double click on
the icon labeled Fastback Procedure.  It lets you choose files and settings for
your backups.

4.2 - Settings Pages

    All the same options found in the "Chooser View" are found in the settings
pages of the Icon.  The only thing you can not do from the settings pages is
select files.

4.3 - Scheduling Procedures

    Procedures

5.  Floppy Support:
===================

   Due to the baseline philosophy of OS/2, access of diskette drives
is much different from the logistics that Fastback Plus for DOS uses.  Fastback
Plus for OS/2 ties in to the existing DASD support of diskette drives, rather
than bypassing it.  Because of this, you may notice irregular behavior of
diskette drives while backing up (to diskette).

   When Fastback Plus begins backing up, the diskette will begin getting
polled for the existance of a diskette.  This will be evident by a flashing
of the diskette drive access lights about once per second.  Do not be alarmed
by this behavior, as it is normal for the operation of Fastback plus.

System Device (System Default)

       Using a diskette drive as a System Device is a different method.  This
requires that your diskettes be formatted, and will write compressed backup
segments to the path specified on the Hardware page of the Settings Notebook
for the System Device Icon.  This method should be used if you wish to "port"
data from one machine to another, and the target machine has a head alignment
difference with the source machine.  The system device can be used with any
logical drive letter, not just diskette drives. (See part 8, below, "Network
drives, Hard drives, and Removables" )

       Because of this, should OS/2 detect a write fault (unformatted sector,
unmarked bad sector, etc), you could have an annoying problem.  To prevent
this, ensure that you have enough preformatted diskettes available when using
this object as a target device.


6.  QIC Support:
================

6.1 - Drives Supported

    At time of release, Fastback Plus for OS/2 has been tested with, and will
support, QIC drives by the following manufacturers:

    Colorado Memory Systems.
      Jumbo 250 and Jumbo 120
    AIWA
    Archive
      XL-80 and 40
    IOMEGA 250

    Fastback Plus for OS/2 supports the FC-10 and TC-15 controller card
produced by CMS.  If you use one of these cards, you must first open the
SETTINGS NOTEBOOK for the QIC Tape object that is created in your Fastback
Folder. Refer to your Fastback Plus for OS/2 user's manual for configuration
instructions.

7.  SCSI Support:
=================

7.1 - SCSI Cards Supported

    The following SCSI adapters have been tested successfully with Fastback Plus
for OS/2:

   Adaptec 151x, 152x, 154xB, 154xC, 154xCF, 164x, 174x, 274x, 284x
   AMI Fast Disk
   Buslogic 445, 542, 545, 742, 747
   DPT Smartcache III
   Future Domain 850, 950, 16x0, 16x0 SVP
   IBM INT-4b, SCSI-III
   Trantor SCSI (Parallel and PAS-16)
   Ultrastor 14F, 24F, 24FA, 34F

   Any SCSI adapter which supports the IBM SCSI command specification via
   OS2SCSI.DMD should operate properly with Fastback OS/2.  The following
   card(s) DO NOT support this specification and are therefore unusable by
   Fastback Plus for OS/2 at this time:

   1.  Future Domain 7000EX

7.2 - SCSI Tape Drives supported

    The following SCSI Tape drives have been tested successfully with Fastback Plus
for OS/2:

    Archive Viper 2060
    Archive Viper 2150
    Archive Viper 2525
    Archive Python 4320*
    Archive Python 4322*
    Archive Python 4350*
    Colorado Memory Systems PowerTape PT-25
    Colorado Memory Systems PowerTape PT-25E
    Exabyte 2501
    Exabyte 4200c
    Exabyte 8200
    Exabyte 8205
    Exabyte 8500
    Exabyte 8505
    Exabyte 8500c
    HP 35470A
    HP 35480A
    IBM 3421 Model 023
    Sony SDT-4000
    Sony SDT-5000
    Tandberg 3600
    Tandberg 3620
    Tandberg 3800
    Tandberg 3820
    Tandberg 4100
    Tandberg 4120
    Tandberg 4200
    Tandberg 4220
    WangDAT 1300
    WangDAT 2600
    Wangtek 5099
    Wangtek 5150
    Wangtek 5250
    Wangtek 5525
    Wangtek 51000
    Wangtek 6130*

* These drives must be jumpered to SCSI-1 to operate properly.

7.3 - Bulk Erasing 4mm and 8mm Tapes.

    Often bulk erasing a tape is used as a security measure to wipe out any
confidential data on a tape.  These tapes are usually thrown away afterwards.
Make sure not to accidently use one of these tapes.  They will usually crash
the tape drive, maybe even crashing the SCSI card.  If the card locks, OS/2
is next.

7.4 - Transferring data between drives.

    Not all drives are created equal.  Many tape drives use the same tapes but
they do not always create tapes that are interchangeable.  For example:  The
Exabyte 4200c is a 4mm DAT drive that uses compression when it writes to the
tape.  The Sony SDT-4000 is also a 4mm DAT drive that uses compression, but it
can not read the data created on the Exabyte because they use different
compression techniques.

7.5 - Fastback does not see my SCSI drive.

    Should Fastback fail to "see" your SCSI drive, then there are some
possibilities that could correct your problems.

     1.  The SCSI device is locked.  Shutdown OS/2 and your machine and turn
off any external SCSI devices.  After pausing about 30 seconds, power on all
external SCSI devices and power on your CPU.  The Fastback Plus SCSI driver,
FBSCSI.SYS should load.

     2.  The SCSI Bus is improperly terminated.  Improper termination of the
SCSI bus can result in bizarre behavior from no identified devices to
multiple shadows of one or more devices to system lockups.

     3.  A SCSI device ID conflict exists.  Check the SCSI ID of each installed
device to be certain that no conflicts exist.


8.  Network Drives, Hard Drives, Removables:
============================================


    These resources can also be used as backup Targets using the System
Device Object.  On the hardware page of the Settings book for a System Device
Object is a setting for drive and path.  Define a logical drive that points
to the Network Resource which you wish to use as a target.  Pull a System
Device from the Fastback Plus for OS/2 Templates folder, and on the settings
page set the drive and path to match the desired target drive and path.  Any
device which is or can be defined as a logical drive and file system can be
backed up in this manner.


NOTE TO USERS OF IBM LAN SERVER V 3.0

   It is necessary to use the Lan Requester Service Pack for version 3.0 in
order to prevent problems with backup while accessing a Lan Server resource.
Should you encounter any problems during backup, contact your local IBM
Reseller or Support Center for an upgrade.


9.  Setting CPU Priorities and Buffer Allocation:
=================================================

9.1 - Streamer Tape Tweaking.

   Streamer devices may require some tweaking of the priorities and buffer
allocation.  These settings can be found on the Priorities page of each devices
settings notebook, as well as the slide switch icon in the chooser view of the
Fastback Plus interface and Procedures.  Each allocated buffer is 32k in size
for QIC, Diskette, and System devices, and 64k in size for SCSI devices.
(So that if all buffers are used, then a 1 Mb buffer results, except for SCSI
devices, which will result in a 2Mb buffer.)  Depending on the data throughput
of the selected device, you may need to increase or decrease the buffers
allocated.

9.2 - Device or Procedure buffer allocation?

   A potential for confusion exists in the order of precedence between the
buffers allocated in the device settings, and the buffer allocation found in
the procedure itself.  When a procedure is "pointed to" a particular device,
the procedure attempts to allocate the buffers as to its own settings, in as
much as the device's buffer allocation maximum will allow.

   For example, the Floppy Device will allow a total allocation of either 4 or
8 buffers ( 128k - 256k ), while the procedure allows up to 32.  If within
the procedure, you select 16 buffers, and within the device settings for the
Floppy Device, you have selected 4 buffers, then the buffers used in the
procedure will be set to 8.


9.3 - CPU priorites.

    Since OS/2 is a true multitasking operating environment, Fastback Plus
for OS/2 allows you to set the priority of operations, in case there are
other tasks which function in your environment that you do not wish to be
degraded by backups.  It is suggested, in any case, that your backups be set
to a low - medium priorities, so that the performance of your Workplace is
affected by Fastback Plus as little as possible.

9.4 - The Default button.

    As with most settings for objects within OS/2, there are default buttons
for the Priority and buffer allocation within the Fastback Procedure.  However,
this button ONLY sets the priority level, and leaves buffers completely
unaffected.  The hierarchy of buffer allocation level has no real defaults,
since this decision is a result of a comparison between the settings of the
Device and Procedure objects.


10.  Creating Recovery Sets
==============

   Recovering from disaster can be a very tedious task for OS/2 users.  Simply
"booting from a disk and restoring" as was the standard for Dos users is not
as simple.   To facilitate total recovery from a crash, Fastback Plus for OS/2
includes an option in the Fastback Plus user interface--Recovery Sets.

   This function can be found in the Utilities menu in the Fastback Plus for
OS/2 user interface.  This option can only be found in the full menus only, so
if you are an Express view user, you will have to select Full Menus from the
Options menu in order to select this.

   You will need your OS/2 installation diskettes 0 and 1, and three formatted
blank diskettes (Fastback Plus for OS/2 will call these the Target diskettes)
for this operation. Fastback Plus will create 3 diskettes, and on the third
will be the recovery program, FBCR.EXE, all associated backup devices and the
utilities required to re-partition and re-format your Fixed Disk partitions.
The first two are required for Bootstrap.  It is strongly recommended that you
perform a full backup and create the recovery set FIRST THING after installing
Fastback Plus for OS/2.

   Recovery set creation steps:

      1. Prepare 3 formatted diskettes, labeled Install (0), Disk 1, and
              Crash Recovery.  Locate your OS/2 installation set and put aside
              the first two diskettes (Installation and Disk 1).

      2. Start the Fastback Plus user interface by double-clicking on
              the Fastback Plus icon.

      3. Follow the directions on the screen.  Fastback Plus will create
               two boot diskettes using files from the installation diskettes,
               and then create the recovery disk.

      4. Put the diskettes in a safe place, where you can be sure to locate
               them when and if it becomes necessary.

  IMPORTANT:  Should you install a service pack or upgrade to OS/2, be sure to
              create a new recovery set! Otherwise, your file system may be
              inaccessable.

   Using the recovery set:

       1. Insert the diskette labelled INSTALL and reboot your system. The
               bootstrap procedure will be identical with the initial phase
               of the OS/2 installation process, the system will boot and ask
               for Disk 1. After boot, however, the system will be at a
               command prompt.

       2. Insert the third diskette.  The third diskette will contain
               CHKDSK.EXE, FDISK.EXE, and FORMAT.EXE.  Contact your local
               IBM support representative should you require assistance
               repartitioning and reformatting your Fixed Disk.

       3. Run the Crash Recovery Restore program by typing FBCR and pressing
               <ENTER> at the command prompt. Follow the instructions on
               screen to restore your Full Backup.


==========================================
*****   A Note to Advanced Users of OS/2 *
==========================================

   The installation of OS/2 can be most time consuming, and a quick and
easy method of restoring your OS/2 system without the necessity of
reconfiguring all of your applications.  Installing OS/2, create a partition
large enough to contain your OS/2 plus a reasonable swap area depending on
your needs and available RAM, and keep your Applications on another partition.
Should reinstall become necessary, you can easily re-partition and re-format
that partition, and restore OS/2 using FBCR (Fastback Plus Crash Recovery) to
restore the OS/2 System.


11.  Contacting Technical Support.
==================================

       Symantec provides free 90-day technical support to registered users
of Fastback Plus for OS/2.  Call the number below for technical support and
have the following information ready for the technical support representative:

     Technical Support:   (503) 465-8420

Information you should have ready:

       1. Your name and registration information.
       2. The make and model of your system, including hard drive
                 capacity and total installed RAM.
       3. The version of OS/2 installed (2.1, 2.1 service pack,
                 2.11 service pack).
       4. The make and model of installed storage devices, QIC tape,
                 SCSI tape, optical disks, etc.



============================================================================
End of File
============================================================================



