Welcome to the Demo version of the IBM DualStor Backup Program for OS/2 Version 2.0! All operations of the DualStor for OS/2 program are enabled with this Demo version EXCEPT the Restore operation. You can Select the Restore operation but after you enter the Restore parameters, you will receive a message indicating the Restore operation is disabled. To install this Demo version, insert the DualStor for OS/2 diskette 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. 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 (US Only) or IBM Direct at 1-800-465-7999 (Canada Only). You may also be interested in purchasing the DualStor 450 Tape Drive which can store up to 450 meg of data when using a Sony QIC-wide tape QW5122XL and level 2 compression (data dependent). DualStor part numbers: 11H1568 DualStor for OS/2 version 2.0 (software only) 11H1505 DualStor for OS/2 version 2.0 and DualStor 450 Tape Drive 11H1594 DualStor for DOS/Windows version 2.0 (software only) 11H1504 DualStor for DOS/Windows version 2.0 and DualStor 450 Tape Drive (hardware, software, & 1 Sony QIC-wide QW5122XL tape cartridge) 11H1571 Upgrade from DualStor for DOS/Windows 1.0x 11H1549 Upgrade from DualStor for OS/2 1.0x 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 - DualStor 2.0 Changes from Versions 1.x 10 - Miscellaneous 11 - 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. Open the OS/2 Startup folder from the Desktop. b. Move the mouse over to the AutoTape icon and single click on mouse button 1 to select the AutoTape icon. c. Single click on mouse button 2 to display the AutoTape pop-up menu. d. Move the mouse to 'Delete' and click on mouse button 1 to delete the current AutoTape icon. 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. If you receive a window during installation indicating that DualStor found an older version of IBM1FLPY.ADD or IBM2FLPY.ADD installed on your system you need to select the 'Install new file' button. This newer module is required to run DualStor properly under OS/2 2.x. ---------- *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. ---------- *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. ---------------------------------------------------------------------- 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-7 and 1-8 and User's Guide manual pages 4-10 through 4-13 please be aware of the following information: 1. 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. 2. If you are using an IBM model 9595 with OS/2 2.0 you must have the OS/2 2.0 Service Pak XR06100A installed. 3. MakeSR does not support XDF-formatted diskettes. 4. 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 than the one described above under 'DualStor Installation and OS/2 2.0' before making the Stand-Alone restore diskettes as described in the Getting Started manual on pages 1-7 and 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 XR0F034.1DK and XR0F034.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 XR0F034.1DK D XR0F034.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 XR0F034.1DK and XR0F034.2DK. 5. 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. 6. There is an undocumented option, SR /ds, you can enter to see the filenames scroll to the screen as they are being restored. 7. 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: 8. 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. ---------- *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 at 916-356-3600 and search for 'BIOS' for information that could resolve these problems. ---------- *National Semiconductor Floppy Controller DP8473* If DualStor for OS/2 detects this floppy controller on your system, DualStor will use a maximum transfer rate of 500Kbps (vs. 1Mbps). This is due to the floppy controller not containing a FIFO. ---------- *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 1540 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 Note that the Y must be in upper case. You can also add the same statement to your CONFIG.SYS. ---------------------------------------------------------------------- 9 - DUALSTOR 2.0 CHANGES FROM VERSIONS 1.x ---------------------------------------------------------------------- *Default Backup Set Names* If you mark specific directories and/or files for backup as opposed to marking an entire hard drive, the default backup set name will be "Partial-X" where 'X' is the drive designator of the hard drive on which the directories and/or files marked for backup reside. DualStor versions 1.x used a default backup set name of "Full-X". ---------- *Column Headers* Column headers were added to the tops of the file windows. These column headers identify the column by name (ex. "Name", "Date", etc.). The columns can be sized by dragging the separator line between each column (the separator line to the left of "Name" is not enabled). Click the left mouse button on any column to sort the entire list by that column. ---------------------------------------------------------------------- 10 - MISCELLANEOUS ---------------------------------------------------------------------- *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. ---------------------------------------------------------------------- 11 - 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 follows: 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 on restore 14 = Disk full in \temp directory 15 = No files selected 17 = Non-critical verify warning (Verify miscompares seen in Session log) 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 16 goto :nomsgfl 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).