Welcome to the Demo version of the IBM DualStor Backup
Program for OS/2 Version 3.0!

All operations of the DualStor for OS/2 program are enabled with this
Demo version EXCEPT that the Backup and Restore operations will
only process 10 meg of data.

After you have expanded the files in the DSOS230.EXE package,
copy the files to a high-density 3.5" floppy diskette.  Then insert
the diskette (DualStor for OS/2) in a 3.5" floppy drive and enter 
'x:setup' where x=your 3.5" floppy drive designator (for example, a:setup)
from an OS/2 window.  After DualStor for OS/2 is installed and you have
Shutdown OS/2 and rebooted, double-click on the DualStor folder on the
Desktop and then double-click on the DualStor icon to star the DualStor
application.  Due to the process used to make this Demo version, the
icons within the DualStor folder may not appear as they should but they
are all still functional.

We hope you like DualStor!  If you would like to purchase DualStor for
OS/2 you can call Options by IBM at 1-800-426-7299 in the U.S. or in
Canada call 1-800-IBM-CALL.  You may also be interested in purchasing 
the DualStor 800 Tape Drive which can store up to 800 meg of data when 
using a Travan TR-1 tape and level 2 compression (data dependent).

DualStor part numbers:
44H3366  DualStor for OS/2 version 3.0 (software only)
31H5622  DualStor for OS/2 version 3.0 and DualStor 800 Tape Drive
            (hardware, software, & 1 Travan TR-1 tape cartridge)
44H3393  DualStor for DOS/Windows version 3.0 (software only)
44H3111  DualStor 800 Tape Drive (hardware only)
31H5621  DualStor for DOS/Windows version 3.0 and DualStor 800 Tape Drive
           (hardware, software, & 1 Travan TR-1 tape cartridge)

The following is the README that ships with the product.

----------------------------------------------------------------------
TABLE OF CONTENTS
  1 - DualStor Installation Notes
  2 - DualStor Installation and PMTAPE
  3 - DualStor Stand-Alone Restore
  4 - DualStor Execution
  5 - DualStor and OS/2
  6 - DualStor Job (Parameter) Files
  7 - DualStor and Networks
  8 - Compatibility with Other Software and Hardware
  9 - Problem Determination
 10 - DualStor 3.0 Changes from Versions 2.x
 11 - Miscellaneous
 12 - Errorlevel Return Codes for Command Files

----------------------------------------------------------------------
  1 - DUALSTOR INSTALLATION NOTES
----------------------------------------------------------------------

*Installing Into the Same Directory as a Previous Version of DualStor*

If you are going to install DualStor for OS/2 into the same directory
as a previous version of DualStor for OS/2 then follow these steps
prior to your installation.  These steps will avoid conflicts with current
DualStor for OS/2 files and ensure all of the latest DualStor for OS/2
files are installed correctly:
1.  If AutoTape is currently installed:
    a.  Make sure the currently installed AutoTape program is closed.
2.  Use a text editor to modify your config.sys file in the following manner:
    a.  Locate the DualStor 'DEVICE=x:\x\IP22IDRV.SYS' statement (it is most
        likely at the bottom of your config.sys).
    b.  Insert 'REM ' in front of 'DEVICE' (this will cause this statement
        to be 'remarked out' and not executed the next time config.sys
        is executed).  (If you prefer you could delete this line instead of
        remarking it out).
    c.  Locate the DualStor 'RUN=x:\x\IP2XMN.EXE' statement (it is most
        likely at the bottom of your config.sys).
    d.  Insert 'REM ' in front of 'RUN' (this will cause this statement
        to be 'remarked out' and not executed the next time config.sys
        is executed).  (If you prefer you could delete this line instead of
        remarking it out).
    e.  Save and file these changes.
3.  Shutdown your OS/2 system and reboot it.
4.  You are now ready to install DualStor for OS/2 in the same
    directory as a currently installed DualStor for OS/2 using the
    normal installation procedure.
    a.  If AutoTape was currently installed, the scheduled events can be 
        saved if during the installation when prompted with the File
        Overwrite Warning for the DUALSTRP.INI file you check the
        'Keep existing file' box.

----------
*Boot-up Problems After DualStor Installation*

If after installation, your system has an error during boot-up (such
as hanging on the 'Minicartridge tape driver.  Version x.xx' message),
edit your config.sys file using a text editor and move the DualStor
'DEVICE=x:\x\IP22DRV.SYS' and 'RUN=x:\x\IP2XDMN.EXE'
statements (which will be at the bottom of config.sys) to the top
of config.sys and re-boot your system as a possible solution.
(For example, for DualStor and the FAXWORKS products to co-exist,
the DualStor RUN and DEVICE statements usually have to be moved
above the first DEVICE statement in CONFIG.SYS.)

----------
*Duplicate Icons in DualStor Folder After Subsequent DualStor Installation*

If you have a 1.x version of DualStor already installed and then install
DualStor version 2.x on the same system and choose to Replace the
Identical Folder on the Desktop, you could see duplicate icons in the
DualStor folder when you open it.

If this happens and you installed the 2.x version of DualStor into the
same directory as the 1.x version of DualStor then you can delete either
one of each of the duplicate icons.   Once you open the DualStor folder
place the mouse over the icon you want to delete.  Single click on
mouse button 2 to display the pop-up menu.  Move the mouse to 'Delete'
and click on mouse button 1 to delete the icon.

If you installed the 2.x version of DualStor into a different
directory than the 1.x version of DualStor then you need to place
the mouse over each icon, single click on mouse button to display
the pop-up menu, move the mouse to 'Settings' and click on mouse
button 1, move the mouse to the 'Program' tab or the 'File' tab
and look at the 'Path' to determine which icon is in the 1.x
version directory.  Close the 'Settings' and place the mouse over
the 1.x version of the icon you want to delete, single click on
mouse button 2 to display the pop-up menu, move the mouse to
'Delete' and click on mouse button 1 to delete the icon.

----------
*DualStor and Migrating Windows Applications to OS/2*

If you have DualStor for Windows installed on your system and
you install OS/2, do not migrate the DualStor for Windows to the OS/2
Desktop.  DualStor for Windows will not work properly in the Win-OS/2
session.  If you did migrate DualStor for Windows to the OS/2 Desktop,
you should delete the DualStor for Windows folder.

----------
*Suppressing the Minicartridge Tape Driver Message*

If you would like to suppress the 'Minicartridge Tape Driver' message
when OS/2 is booting up, simply edit CONFIG.SYS and change the
DualStor 'DEVICE=' statement to the following (where x= the hard drive
partition where DualStor is installed):

           DEVICE=x:\DUALSTOR\IP22DRV.SYS /q

----------------------------------------------------------------------
  2 - DUALSTOR INSTALLATION and PMTAPE
----------------------------------------------------------------------

If you have PMTAPE installed on your system in the '\PMTAPE' directory,
during the DualStor installation you will receive a message indicating
a previous tape driver was found.  If you choose to have the PMTAPE
driver removed, your '\PMTAPE' LIBPATH and PATH entries and RUN and
DEVICE statements will be removed from your CONFIG.SYS.  You will
not receive this message if PMTAPE is installed in a directory other
than '\PMTAPE'.

DualStor and PMTAPE can co-exist on your system.  If you have them
both installed make sure the first entry in your LIBPATH and PATH
statements in CONFIG.SYS is '.;' and if you run DualStor or PMTAPE
from an OS/2 command prompt you must run them from the directories
in which they are installed.  However, if you are using AutoTape and
you have both PMTAPE and DualStor installed on your system you will
need to delete both entries in CONFIG.SYS and then enter the full working
directory for each in the AutoTape command field.

----------------------------------------------------------------------
  3 - DUALSTOR STAND-ALONE RESTORE
----------------------------------------------------------------------

If you are going to use the Stand-Alone Restore function as decribed
in the Getting Started manual pages 1-6 through 1-8 and User's Guide
manual pages 4-10 through 4-13 please be aware of the following
information:

1.  The Stand-Alone Restore function is a disaster recovery procedure.
    When using this function you must restore to the same hardware
    configuration/platform.

2.  On page 1-6 of the DualStor Getting Started manual under the section
    'Creating Disaster Recovery Disks' the bullet that reads 'The first
    two OS/2 2.x install disks-...' should read 'The first two OS/2 install
    disks that match the OS/2 version installed on your hard drive - OS/2
    Installation Diskette and OS/2 Diskette #1.'

3.  While Creating the Disaster Recovery Disks you may also want to make
    a note of the volume label of your hard disk partitions as it may be
    needed during a disaster recovery to format a crashed hard drive.

4.  You need REXX installed for MakeSR to retrieve the correct keyboard.dcp
    statement from your hard file config.sys.  If REXX is not installed when
    you start MAKESR you can press any key and MakeSR will continue and SR
    disk 2 will have the statement 'devinfo=kbd,us,keyboard.dcp'.  If the
    'us' parameter in this statement does not match your statement in your
    hard file config.sys then you must manually edit the config.sys on SR
    disk 2 to change the 'us' to your parameter before booting the SR disks.

    If you do not wish to continue with MakeSR because REXX is not installed,
    you can press CTRL-C to quit MakeSR and refer to your OS/2 documentation
    on how to install REXX.

5.  After performing an SR and rebooting the system, DualStor for OS/2
    may be open.  This is normal and is caused by the
    'SET AUTOSTART=PROGRAMS' line in config.sys.  Make sure all the
    open programs are closed and re-opened before use.

6.  MakeSR does not support XDF-formatted diskettes.

7.  If you are using an IBM 9553, 9556, or 9557, or any AT bus, EISA bus,
    or ISA bus system you need to obtain a newer version of the OS/2 file
    IBM1FLPY.ADD before making the Stand-Alone restore diskettes
    as described in the Getting Started manual on pages 1-6 through 1-8.
    You ONLY need this module if you are going to use the Stand-Alone
    restore function for OS/2 2.1 and OS/2 2.11.

    To obtain the updated file you may download it from the IBM PCCBBS
    (PC Company Bulletin Board System); or you may contact the IBM OS/2
    Support Center at 1-800-992-4777 and ask for APAR PJ12214 if you
    have OS/2 2.1 and for OS/2 2.11 you need files XR0F035.1DK and
    XR0F035.2DK.

    The fix will be mailed to you via regular first class mail.

    1. To download from PCCBBS, dial into the PCCBBS at (919) 517-0001.
       (You need a modem/Communications software to download the fix
        electronically).

    2. Enter your first and last name when prompted.

    3. Enter your password when prompted. Note: Choose a password
       that you will remember because you will need to specify
       it the next time you log onto the PCCBBS.

    4. You will next be asked a series of questions. Please provide
       information when prompted.

    5. To fast forward to the Main Menu, enter "N" and press the enter
       key when PCCBBS NEWS screens are displayed.

    6. Once at the "IBM PCC Public BBS New User Main Menu" screen, you
       are ready to download the fix.
       a.  To download the fix for OS/2 2.1 or earlier enter:

           D PJ12214.EXE

          Specify communications information when prompted.
          This is a self exploding file. Once the file has been downloaded
          and installed on your system hardfile, insert a blank diskette
          in drive A of your system, enter PJ12214 A: This will unpack
          the fix files to diskette. Read the README.1ST to install the
          fix.

      b.  To download the fix for OS/2 2.11 enter:

          D XR0F035.1DK
          D XR0F035.2DK

    7.  If you are a Middle East, Europe, or Africa customer, to
        obtain the updated file you may download it from the IBM
        PCCBBS (PC Company Bulletin Board System); or you may
        contact the IBM OS/2 Support Centre and ask for OS/2 2.1
        APAR PJ12214 and for OS/2 2.11 you need files XR0F035.1DK
        and XR0F035.2DK.

8.  After you have run MAKESR and made your SR diskettes, you should
    immediately boot the SR diskettes to make sure there are no problems.
    If you do experience an error during boot-up (such as hanging on the
    'Minicartridge tape driver.  Version x.xx' message), edit the config.sys
    file on SR disk #2 using a text editor and move the DualStor
    'DEVICE=x:\x\IP22DRV.SYS' and 'RUN=x:\x\IP2XDMN.EXE' statements
    to the top of config.sys and re-boot your system as a possible
    solution.

9.  There is an undocumented option, SR /ds, you can enter to see
    the filenames scroll to the screen as they are being restored.

10. If you are using SR to restore a Dual Boot system, in order for
    the system to be able to boot DOS, you must do the following
    once you are able to use the hard drive to boot your OS/2 system:

    a.  At the OS/2 prompt, type CD\OS2.

    b.  Type Boot /DOS.

    c.  Place a DOS Startup diskette in the diskette drive.

    d.  Enter Y at the prompt to reboot the system.

    e.  At the A:\ prompt, type SYS C:

11. If you are using SR to restore a Boot Manager system, in order for
    the system to be able to boot DOS, you must do the following
    once your hard drive is restored.

    a.  Place a DOS Startup diskette in the diskette drive.

    b.  Re-boot the system.

    c.  At the A:\ prompt, type SYS C:


----------------------------------------------------------------------
  4 - DUALSTOR EXECUTION
----------------------------------------------------------------------

*Undocumented Copy/Paste Capability*

In the Session Logs window, the Control menu includes a copy
capability not documented in the User Manual. To copy a session log,
select Copy to Clipboard from the Control Menu. The text of the
session log will be copied to the clipboard and can be pasted into
another application that has a paste command.

----------
*Backing up Files and EXCLUDEP.CFG

The file EXCLUDEP.CFG located in the DualStor install directory
contains a list of system files that DualStor excludes from the
backup.  It is not necessary for these files to be backed up.

One of the files in this list is EA DATA. SF.  This file contains
the Extended Attributes for the files on a FAT file system.  During
backup the extended attributes for a given file are extracted from
EA DATA. SF and stored on the tape with the file.  During the Restore
operation the attributes are restored to EA DATA. SF correctly.
If EA DATA. SF were backed up and restored, the restore of these
extended attributes could adversely affect files on the system
that were not backed up at the time of the original backup.

If you add other statements to the EXCLUDEP.CFG file please note
you cannot use the '&' to exclude directories.  It can only be used
with filenames.

If you are using Stacker, you may want to add the file DONT.DEL.ME
to the EXCLUDEP.CFG file as it is not necessary to back it up.  Refer
to the User's Guide page 5-7 section Excluding Files From Backup on
how to add a file to EXCLUDEP.CFG.

----------
*Incremental vs. Differential Backup Methods*

The difference between Incremental and Differential backups
is that the Incremental method will reset the archive bits and the
Differential method will not reset the archive bits.  Both methods
will back up the same files from your hard disk.  Checked files
that have the archive bit set on will be backed up by both methods.

----------
*AutoTape Command Prompt*

When entering a command in the AutoTape command box, be sure to use
the extension of the file being used so that the operation will work
properly. For example:

        DUALSTRP.EXE FULL-CDE.TPF

----------
*~BEX Files*

Files that begin with ~BEX are temporary files used by DualStor. If
you see one of these files when DualStor is not running, you can
delete them. ~BEX files will be found either in your TEMP directory or
your DualStor directory.

----------
*Ignoring Drives in DualStor*

You can tell DualStor to ignore specified drives, if you have drives
that are creating error messages or speed problems when you run
DualStor. For example, if you have a computer with a single floppy
drive (drive A:), you can have DualStor ignore your non-existent B
drive.  You may also want to use this setting to tell DualStor to
ignore both A: and B: drives so that they do not appear in your
DualStor Drives window.  The default Drives selection would then
always be your C: drive.

To do this, add the following statement to your CONFIG.SYS file.

        SET IRSKIPDISK=ab

You can list as many drive letters as you want, putting no spaces
between them, for example, IRSKIPDISK=abcd (to ignore your A:, B:,
C:, and D: drives).

----------------------------------------------------------------------
  5 - DUALSTOR AND OS/2
----------------------------------------------------------------------

*Error Message "User INI File Corrupt"*

Restoring OS/2 system files to your hard disk may give you an error
message stating: "The workplace desktop could not be located. The user
INI file or hardfile may be corrupt." The message appears because OS/2
sees system files momentarily not synchronized. Ignore this message.
Your restore should complete without any problems.

----------------------------------------------------------------------
  6 - DUALSTOR JOB (PARAMETER) FILES
----------------------------------------------------------------------

*Using Parameter Files from PS2Tape and PMTape*

If you have parameter files created for PS2Tape or PMTape, they will
work with DualStor by copying them into the DualStor directory.
Parameter files are now called job files and can be created more
easily using options in the DualStor Jobs menu. Be sure that your
existing parameter files have names different from the five job files
created during DualStor installation (FULL.TPF, DIFFR.TPF, INCR.TPF,
REST.TPF, and TAPEINFO.TPF), so you don't overwrite any of them.

Because of enhancements to job file capabilities, some of the syntax
for job file commands has changed.  Your existing parameter files will
still run, but first you should review Appendix B in your User Manual
for detailed information on the new job file command syntax.

----------
*Logging a DualStor Operation*

All DualStor operations, including operations launched from job files,
are logged in a DualStor Session Log. If you want to create a log file
in a specific location with a specific name, open the job file using a
text editor and add the following command:

   /l log_name

The /l command is a job file "option" available in backup and restore
modes. The log file will be saved in your DualStor directory or you
can specify a full path. For example:

   /l c:\bulogs\backup.log

The log file will list files that were included and/or excluded from
the operation depending on the logging settings specified in DualStor.
DualStor creates the log file after you exit the program. See Appendix
B in the DualStor User Manual for more information on job file
editing.

----------
*Mode Variables*

There is only one mode variable allowed in each Job file (i.e. *.tpf)
Mode variables are !backup, !restore, !init, !util, and !shortcuts.

----------
*Encryption and Password Options*

The Encryption and Password options are not available for use with
Job files.  Therefore, if you check the Encryption option in your
Settings pull-down, Backup defaults window it will not be enabled
(it will be grayed out) when you save a Job file.

----------
*Date Specification*

When using the '/d' option in a DualStor Job file you must have a
space on both sides of the date_spec value.

-----------------------------------------------------------------------
  7 - DUALSTOR AND NETWORKS
----------------------------------------------------------------------

*LAN Server 3.0*

LAN Server 3.0 users must perform local backups of Domain Controllers
by selecting the drive letter of their local OS/2 boot drive.

For example, if

          D: is the local OS/2 boot drive
          Q: is the alias of the path D:\*.*

you must select drive "D:" for the backup.

----------
*Novell Volume Restrictions*

Novell volume restrictions will only be backed up if you use QIC tapes
with the DualStor file system or you use Servo (AccuTrak) tapes.
Volume restrictions are not backed up using QIC tapes with the
QIC-Compatible file system (QIC-80 and QIC-113).  See your DualStor
User's Guide for more information on file systems.

----------------------------------------------------------------------
  8 - COMPATIBILITY WITH OTHER SOFTWARE AND HARDWARE
----------------------------------------------------------------------
*Intel Premiere II PCI Motherboard*

If you have a Pentium system with the Intel P90 motherboard
(Premiere II PCI, codename Plato) and you are experiencing
slow transfer rates, 'DMA Overruns', or excessive shoe-shining
(tape spins backward and forward continuously) when performing
DualStor backup operations, you should first call the Intel Bulletin
Board and search for 'BIOS' for information that could resolve these
problems.  In the U.S. the number is 916-356-3600.

----------
*DualStor and 5.25" External Diskette Drive*

If you have a 5.25" external diskette drive device driver loaded
via your OS/2 config.sys (for example, driver EXT5DD.SYS), the
DualStor Scan function will not execute properly.  To avoid this
problem add the following line to your config.sys:

        SET IRSKIPDISK=x

where 'x' = the drive letter designator of your 5.25" external
diskette drive.

----------
*Compatibility with QICstream*

QICstream backup software cannot read DualStor backup sets that are
compressed.

----------
*Compatibility with Colorado Memory System Backup Software*

CMS's Colorado Backup software cannot read DualStor backup sets that
are compressed.

----------
*4100MC and IBM Model 9577*

The 4100MC controller card in an IBM Model 9577 will cause DualStor
to work improperly. To avoid this problem, connect your tape drive to
your computer's floppy controller rather than the 4100MC card. See
your tape drive's installation guide for more information.

----------
*SCSI Hard Drives and the Adaptec 1540 Controller*

If you are using:

        * a tape drive with a floppy controller AND
        * a SCSI hard drive with an Adaptec 1540A or 1540B controller,

you must set the IROPT environment variable. To set IROPT, enter the
following command at the OS/2 prompt before you start up DualStor:

        SET IROPT=Y

Do not use this command if your Adaptec controller is a 1540C.
Note that the Y must be in upper case. You can also add the same
statement to your CONFIG.SYS.

----------------------------------------------------------------------
  9 - PROBLEM DETERMINATION
----------------------------------------------------------------------
*Determining Your Floppy Controller*

Knowing what floppy controller is installed on you system can
help determining problems.  To find out what floppy controller
you are using do the following:

1.  Use a text editor and edit CONFIG.SYS.
2.  Locate the DualStor 'DEVICE=' statement.
3.  Add ' irdbg=a' to the end of this 'DEVICE=' statement.
4.  Shutdown OS/2 and re-boot.
5.  DualStor will output information to your screen.
6.  The floppy controller is designated by the 'fdc=' field
    towards the bottom of the output.

1.  765A, 765B, or 8473 - these floppy controllers only support the
    500Kbps transfer rate.  You should be seeing transfer rates
    averaging 2meg/min (with no compression).
2.  All other floppy controllers should support the 1Mpbs transfer
    rate.  You should be seeing transfer rates averaging 4meg/min
    (with no compression).
3.  37C66x - if you have this floppy controller and you are
    experiencing problems try using IROPT=d or IROPT=o
    (see 'Setting Environment Variables' below).
4.  8477 - if you have this floppy controller and you are
    experiencing problems try using sysfdc=b:1 or sysfdc=b:2
    (see 'Setting Environment Variables' below).

*Slow Transfer Rates*

If you have an IBM model 8580 and you are experiencing slow
transfer rates try using IROPT=I or IROPT=i (see 'Setting
Environment Variables' below). This variable changes the
wait for index setting.

*DMA Overruns or DMA Underruns'

If you are receiving these errors try using the IROPT=d environment
variable.

*Setting Environment Variables*

Environment variables are special parameters that can be added to the
end of the DualStor 'DEVICE=' statement in CONFIG.SYS.  Use a text
editor to edit config.sys and add a space followed by the environment
variable to the end of the DualStor 'DEVICE=' statement.

Environment variables that could solve slow transfer rates are:
IROPT=d - changes the DMA mode (may help Pentium systems especially)
IROPT=o - indicates the FIFO is not usable and to run at 500Kpbs rate
IROPT=O - indicates the FIFO is not usable and to run at 1Mpbs rate
IROPT=x - indicates FIFO is usable and run at 500Kpbs rate
IROPT=X - indicates FIFO is usable and run at 1Mpbs rate
sysfdc=b:x - where x can be set to 1,2 or 4-10hex.  The default is 3.
               Changes the FIFO threshold.

All environment variables are case-sensitive to the right of the '='.

----------------------------------------------------------------------
 10 - DUALSTOR 3.0 CHANGES FROM VERSIONS 2.x
----------------------------------------------------------------------
*Tape Formatting*

Unless a tape is in an error state, the Format option will always
be enabled.  If an unformatted tape is inserted in the tape drive
when the Format option is selected, the tape will be formatted.

If a pre-formatted Rhomat (servo) tape is inserted in the tape
drive when the Format option is selected, a dialog box will be
displayed indicated the tape must be bulk-erased before it can
be formatted.

If a pre-formatted Ximat tape is inserted in the tape drive
when the Format option is selected, a dialog box will be
displayed giving the user the choice to 'Certify' or 'Format'   
the tape.  A Certify is a subset of a Format and takes about
half the time of a Format.  A Certify looks for bad blocks on
the tape and marks them as unusable (like a surface analysis
of a hard drive).  If you select the Certify option the dialog
box showing the time-line indicates 'Format' in the title.

If any errors occur during a Certify or Format the tape must
be bulk-erased (again in the case of Rhomat tapes) and
the Format option selected.

There is more information on Formatting in the User's Guide
that you should read on pages 9-7 through 9-9.

----------
*Sorting Tapes by Name*

If a tape is named the name will now be displayed along with
the tape number in the left side of the Tapes window.  Page 4-1
in the User's Guide describes how to sort the tapes by name.
The text on page 4-1 is slightly incorrect.  The sorting of
Alphanumeric tape names is NOT case-sensitive.

----------
*Updating Tape IDs*

It is possbile to receive to pre-formatting tapes with the
identical tape number.  DualStor will not allow both tapes
to be added to the catalog.  To update the tape number on
a tape (the tape must be 'Unused') do the following:

1.  Hold the 'Shift' key down.
2.  Click on the Operations pull-down.
3.  Select the 'Update Tape ID' operation.

----------------------------------------------------------------------
  11 - MISCELLANEOUS
----------------------------------------------------------------------
*CPU Intensive Operations*

There are some DualStor operations that are very CPU intensive in
which you may notice a slow-down in your system's performance.
Examples of these include 'Resetting archive bits' at the end of
a backup, 'Add Tape to Catalog', 'Remove Tape from Catalog', and
'Deleting backup sets'.

----------
*Minimizing Backup Basics*

If you select a Backup or Restore in Backup Basics you can
minimize Backup Basics (to get to your Desktop) by minimizing
the Backup (or Restore) transfer window.

----------
*Verify after Backup*

It is a good practice to check the 'Verify after Backup' option on when
selecting your Backup Parameters.  This will cause DualStor to
perform a byte-by-byte comparison between the data backed up on
the tape and the data on the hard drive increasing your confidence
in the backup.  It may, however, double the time of your backup.
If you want to set this option on permanently for all of your backups,
simply select the Settings pull-down, Backup..., and check the
'Verify after Backup'.

----------
*Setting RESTARTOBJECTS in Config.sys*

It is a good practice to add the following statement in your Config.sys
file.

         SET RESTARTOBJECTS=STARTUPFOLDERSONLY

This will only start objects in your startup folder and your startup.cmd
during boot-up.

----------
*Passwords*

If you are using the QIC file system with the Password option, only 8
characters are significant even though DualStor will accept 15
characters.  All 15 characters are significant when using the DualStor
file system.

----------
*Hardware Compression*

The DualStor User's Guide shows a Hardware Compression radio button
on the Backup Set Parameters windows but you will not see it in the
application itself as DualStor does not support any tape drives that
support Hardware compression.

----------------------------------------------------------------------
  12 - ERRORLEVEL RETURN CODES FOR COMMAND FILES
----------------------------------------------------------------------

You can use ERRORLEVEL to check the return codes of a DualStor
tape operation if you are using DualStor job files through an OS/2
command file(filename.CMD).
The values returned by DualStor in ERRORLEVEL are as follow.  

0  = No errors, successful completion
1  = No tape cartridge in drive
2  = Tape is full, cannot write
3  = Tape is write protected
4  = Mount failed or incompatible tape
5  = Invalid command line arguments
6  = Fatal disk error
7  = Not enough memory available to run
8  = No tape drive present
9  = User aborted operation
10 = Fatal tape error
11 = Critical verify failure, backup set deleted
12 = Internal software error
13 = Disk full 
14 = Disk full in \temp directory
15 = No files selected
17 = Non-critical verify warning (Verify miscompares seen in Session log)

Notes:
1.  When using a Restore mode with an incompatible tape
    the ERRORLEVEL will = 15 and not 4.
2.  When using a Backup mode if you are using the DualStor
    file system AND add to catalog is 'off' ERRORLEVEL will
    = 14 if the disk is full.  If you are using the DualStor file
    system AND add to catalog is 'on' ERRORLEVEL will = 13. 
    If you are using the QIC-compatible file system ERRORLEVEL
    will always = 13 if the disk is full.

The following line is an example of the contents of a job
file to retension the tape first.  The 'Do not wait for errors'
option is set on.  Let's call the job file RETEN.TPF:

!util /w 0 /r

The following line is an example of the contents of a job file
to backup the C: drive. It will scan checked files, not wait
on error, name the backup set and backup the C: drive.  Let's call
the job file MYBACKUP.TPF:

!backup /m /w 0 /n "MYBACKUP" /s C:\*.*

The following OS/2 command file is an example of how you might
use the DualStor return codes and the above DualStor job
files.  Let's call the command file TAPEOPS.CMD:

rem --------Beginning of Sample Command program-------------------
@echo off
@echo.
rem Log Retension tape start message to TAPEOPS.LOG file
echo Execute DualStor job file to retension tape >>.\tapeops.log
DUALSTRP reten.tpf
rem next statement checks for errorlevel = 1 or greater
if errorlevel 1 goto :checkrc
echo Retension tape successful >>.\tapeops.log
rem
rem Log Backup start message to log file
rem Execute DualStor job file to backup C: drive >>.\tapeops.log
DUALSTRP mybackup.tpf
rem next statement checks for errorlevel = 1 or greater
if errorlevel 1 goto :checkrc
echo Backup of C: successful >>.\tapeops.log
goto :end
rem
rem Check which error DualStor found and go process the error
:checkrc
if errorlevel 17 goto :vrfymis
if errorlevel 15 goto :noflsckd
if errorlevel 14 goto :diskfull
if errorlevel 13 goto :diskfull
if errorlevel 12 goto :softerr
if errorlevel 11 goto :verfyerr
if errorlevel 10 goto :tapeerr
if errorlevel 9 goto :userabrt
if errorlevel 8 goto :nodrive
if errorlevel 7 goto :memerr
if errorlevel 6 goto :diskerr
if errorlevel 5 goto :invcl
if errorlevel 4 goto :inctape
if errorlevel 3 goto :wptape
if errorlevel 2 goto :tapefull
if errorlevel 1 goto :notape
rem
rem  Here are examples for a few of the return codes:
rem
:inctape
echo Either the mount failed or the tape is incompatible,
echo Check the tape condition and restart TAPEOPS.CMD
pause
goto end
rem
:notape
echo There is no tape in the drive, please insert a tape and
echo restart TAPEOPS.CMD
pause
goto :end
rem
:end
echo End of TAPEOPS.CMD >>.\tapeops.log
 rem ------------End of Sample Command program----------------



 TAPEOPS.CMD, RETEN.TPF, and MYBACKUP.TPF would all reside in the
 directory where DualStor is installed.  The above example would
 be executed by typing 'TAPEOPS.CMD' on the command line at the DualStor
 directory OS/2 prompt (\DUALSTOR\TAPEOPS.CMD).

