Thank you for choosing Backup Exec 6.0.  We hope you enjoy the
new level of capability that this version provides.  As always,
your comments are welcome and suggestions requested.

This document contains release notes for Backup Exec; it also contains
information that may not be in the user's manual.  Information in
this document is more current than information in the manual.
Where this file conflicts with the user's manual, you should
assume that this file is correct.

This README includes the following sections:

    1. What's new in Backup Exec v6.0
    2. Installation Notes
    3. Troubleshooting - Hints and Tips
    4. Loader support installation & considerations
    5. Contacting Arcada Software


1.  What's New in Backup Exec v6.0
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Arcada's third generation Backup Exec is a comprehensive,
yet easy-to-use product for stand-alone or enterprise-
wide backup support.  Backup Exec minimizes administration
overhead, expands data accessibility and offers uncompromised
reliability.

Some of the enhancements provided in Backup Exec 6.0 include:

    1.  Remote Administration including RAS capability
        This allows a user to connect to another Backup Server on the
        network and manage its scheduled jobs as if you were
        there.

    2.  Agent Support
        Arcada agents allow a user to "publish" shares for backup
        that are available only to Arcada backup servers.  Arcada
        provides agent support for UNIX, Mac, and Windows 95 platforms.

    3.  User-defined Shares
        A user definable area in the Backup Exec desktop that
        allows configuration of frequently accessed share points,
        or those of network entities not generally available
        under the Microsoft Network (e.g., IBM LAN Server
        machines).

    4.  Pre & Post Processing
        Provides command line batch processes before and after a
        scheduled event (e.g., a shutdown of a database prior to
        backup and restart after the backup is complete).

    5.  Multiple Drive Loader Support
        Backup Exec manages loaders with multiple tape drives
        accessing the same medium changer.

    6.  Event Logging
        Logs errors, warnings, and information events in Windows NT's
        event viewer that may occur during the course of a backup
        operation.

    7.  ExecView
        Allows monitoring of any instances of Backup Exec
        presently running on the network.

    8.  Tape Read Compatibility
        Backup Exec reads and writes the Microsoft Tape Format.
        Backup Exec also reads other tape formats such as those
        made with Maynard Electronics' Maynstream 3.X and above,
        Sytron's Sytos Plus for OS/2, as well as Cheyenne's
        ARCserve for NetWare 4.x and 5.x.

    9.  Windows NT System Service-based
        Automatically executes backup operations without the need
        to first log into Windows NT.

2.  Installation Notes
    ~~~~~~~~~~~~~~~~~~
Note:  If Backup Exec is being installed on a machine to be
designated as a backup server, be sure the necessary software
drivers for attached tape drives and tape drive controllers have
been installed through Windows NT SETUP and loaded with a system
reboot prior to running the Backup Exec software.  Doing so will
simplify initial setup of Backup Exec once it is installed.
Also, if you select to install over Backup Exec for Windows NT
v5.x, Backup Exec v6.0 will convert all of the existing Catalogs,
Selection Lists, Jobs, and Schedules to the v6.0 format.
However, since Backup Exec v6.0 uses user-defined Tape Drive
Hardware Names, you will need to edit each job to set it to the
correct hardware you want the job to use.  In addition, Backup
Exec v6.0 will preserve all of the v5.x log files, but they
cannot be viewed through Backup Exec v6.0 - it is suggested that
you use Notepad to view these files.

    1. Only install Backup Exec on a local drive.
    2. If no serial number is entered during installation, an
       evaluation version is installed.
    3. If you want to install loader support, see the section
       titled "Installing Loader Support" below

3.  Troubleshooting - Hints and Tips
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    General Considerations
    ~~~~~~~~~~~~~~~~~~~~~~
1.  If you are prompted for a password for access to a share 
    and are attached successfully using this password, Backup 
    Exec. will then use this automatically whenever it 
    attaches to the same device.  You can use "Attach As" from
    the Network menu to change the user name or password used
    for a given device.

2.  Stopping the Server service in Control Panel|Services will
    remove any memory resident copies of Backup Exec.

3.  Exclude Files
    Backup Exec allows you to use a single "global" exclude list
    to exclude files that you *DO NOT* want to back up.  For
    example, you may want to exclude all temporary (.TMP) files
    from being backed up. To exclude these files, determine
    those files that are NEVER to be backed up, for ALL the
    servers desired.  Under the selections menu option choose
    'EDIT SELECTIONS'.  Select the 'Excludes' list and add
    the files that should never be backed up to it.


    Backup Exec Agents
    ~~~~~~~~~~~~~~~~~~
Note:  Information provided concerning agent installations on
Windows 95 machines is based on a beta version of Windows 95.
The issues listed below may be resolved by the final version
of Windows 95.


1.  Windows 95 Agent and Dial Up Networking
    Your Windows 95 Backup Exec Agent may not be visible to
    Backup Exec for Windows NT if ALL of the following
    conditions are met:

    * Your Windows 95 Backup Exec Agent is configured to use the
     SPX protocol

    * Your Windows 95 machine is acting as a Dial Up Networking
      Server (not client)

    * Your Windows 95 Dial Up Networking Configuration includes
      support for SPX.

    Under these circumstances, Arcada recommends using TCP/IP to
    back up the Windows 95 Agent.

    If the Windows 95 machine is listed and can be selected in
    the Backup Selections window, yet files do not appear to be
    backed up properly (a long delay reading the first file
    selected and then the message "Drive is not responding
    Backup set aborted") you likely have an older version
    of the Agent running on the Windows 95 Machine.  A copy of
    the latest Windows 95 agent is located on the Backup Exec.
    installation CD in the Win95 directory.

2.  Backup Exec Agents that use SPX

    If you are using Backup Exec Agents that communicate using
    SPX, you should ensure that you are using a consistent IPX
    frame type on your network.  If you do not, and Backup Exec
    for Windows NT is using a different IPX frame type than the
    workstations running the Backup Exec Agent software, all SPX
    packets must be routed through a server that can translate
    the packets.  This generates excessive network traffic and,
    if the router does not properly handle large SPX packets,
    packets may be lost. One symptom of this problem is a backup
    that times-out with a "Device not responding" error message.

3.  "Archive" operation on Backup Exec Agents

    Though the option to run an Archive operation on a Backup
    Exec agent is available, the delete pass will not occur.

4.  Using the "Enable Agent Network Protocols" option.

    If, in the settings/network window, one or more of the Agent
    protocols are turned on (or off), it will be necessary to
    refresh (F5) the backup selections window in order for the 
    new settings to take effect.

    Email Problems
    ~~~~~~~~~~~~~~
1.  Test messages are sent OK, but email is never sent during
    scheduled jobs.

    The current email support provided by Microsoft does not work
    in applications launched by a system service unless both the
    following requirements are met.

    A.  The user account the system service is running under must
    have a valid MSMail login.  This must be verified by logging
    into the user account and starting the MSMail application.

    B.  The user for the system service account must be logged
    into Windows NT when Backup Exec needs to send email. Email
    support requires that a user be logged into the machine sending
    email. The only way to accomplish this is to leave the user
    logged in while jobs are running.


2.  MSMail Spooler occasionally prevents Backup Exec from exiting
    after a Job.

    When Backup Exec is set up to send mail at the end of a job,
    the MSMail Spooler that is used to send the mail may hang on
    exit (you'll see the MSMail spooler's Icon display "exiting"
    at the bottom of the screen).  At this time, Backup Exec's
    mail has already been sent and the MSMail Spooler may be
    closed by clicking the icon and selecting "Close" -
    Backup Exec will then close and any subsequent jobs will
    execute.  A work around is to leave MSMail open on the
    computer that Backup Exec is running on, logged in as the
    same user the that Backup Exec is sending the mail as (i.e.,
    the same user name you typed in the Mail Logon: field in the
    EMail Confirmation Window in Backup Exec).

3.  Backup Exec does not send MSMail reliably after Jobs.

    Possible Cause 1.

    When using the MSMail Post office for storage, a limitation
    of MSMail is that only one instance of a MSMail user may be
    logged into MSMail at any one time (i.e. MSMail user Jerry
    cannot be logged into MSMail on two computers at the same
    time).  This affects Backup Exec in the following way: if
    Jerry (a MSMail user) is logged into MSMail on Computer A
    and Backup Exec is setup to EMail Jerry after a job on
    Computer B, Backup Exec will not be able to deliver the mail
    to Jerry since he is already logged into MSMail.  This
    situation can also happen when two Backup Exec's are sending
    mail to the same User at the same time.

    Possible Cause 2.

    If Backup Exec sends Mail as Jerry and MSMail is currently
    logged in as Sue, then Backup Exec will not be able to send
    mail as Jerry since Sue is currently logged in.

    To ensure Mail is sent properly, make sure MSMail is either
    logged in as the same person you have setup Backup Exec to
    send mail as, or MSMail is closed.

    Email Setup Recommendation

    a. Create a new MSMail user that has the same name as the
       Computer Name.
    b. Use this new name in the Mail Logon: field (in the EMail
       Confirmation Window in Backup Exec) and select to send
       mail to the person you would like notified.
    c. Leave MSMail logged in as the new user (Computer Name).

    Hardware Compression
    ~~~~~~~~~~~~~~~~~~~~
    Tapes made using hardware compression on one manufacturers
    drive may not be readable by a different manufacturers
    drive.  If exchange between different tape drive
    manufacturers is desired, then software compression
    (or no compression at all) should be used.  Additionally,
    it is recommended that when hardware compression is used
    on the first set on tape, all subsequent sets should also
    be hardware compressed.  Mixing of hardware and software
    compression on the same tape should be avoided.  However,
    mixing of software compression and sets containing no
    compression is acceptable.

    Write Protect & DEC DLT Drives
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    On certain tape read operations you may be prompted when the
    tape is write-protected.  Some of these operations are
    catalog, restore, & verify.  To avoid this error message and
    continue the desired operation, set the write-protection to
    off for the duration of the operation then back to protect
    after the operation is completed.  An updated driver
    resolving this problem is available on the Arcada BBS.  See
    the Contacting Arcada Software for information on the Arcada
    BBS.

    NetWare
    ~~~~~~~
    While you can back up NetWare networks with Backup Exec, it
    will only back up data and the primary name space. Binderies,
    security information, and Macintosh resource forks will not
    be backed up.

    Network Speed
    ~~~~~~~~~~~~~
    Here is a tip to speed up backup on Windows NT when
    selections are made from the networks window.

    In the registry, under HKEY_LOCAL_MACHINE, open the
    following - key:  System\CurrentControlSet\Services
    \LanmanWorkstation\networkprovider.  It has several values;
    double click on the "DeviceName" value and change the case
    of the first letter in the data. You'll be changing
    "\device\LanmanRedirector" to "\Device\LanmanRedirector".
    Change only the case of the first letter -- do not change
    anything else.  This will speed up backups from UNC shares,
    especially those with many small files.

    NT Security
    ~~~~~~~~~~~
    If the Backup Exec application is unable to connect to a
    remote share, check the permissions of the share as well
    as the security rights of the user.

    Percent Complete Bar
    ~~~~~~~~~~~~~~~~~~~~
    The percent complete bar requires that all devices to be
    backed up be prescanned before the backup begins.  Turning
    the percent complete option off will eliminate the prescan
    and reduce the time required to perform the backup.  To turn
    off the feature, go to the Settings menu and select
    Preferences, then deselect "Display Progress Indicator".

    Remote Registry Backup & Restore
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    In order to backup or restore a remote registry, the drive
    must be shared from the root of the remote drive.  If the
    shared directory is not the root, the registry files will be
    seen as open files and skipped.

    Restoring The Registry
    ~~~~~~~~~~~~~~~~~~~~~~
    To restore registry files you must have administrator
    privileges and enough free space on the drive to hold a
    second complete copy of the registry files being restored.
    The restored files will not become active until the machine
    is shutdown and restarted.

4.  Loader Support Installation & Considerations
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    Note: When Backup Exec v6.0 is started for the first time,
    it will scan the backup server for all attached tape drives
    and generate default Hardware Alias Names for each (e.g.,
    ARCHIVE 1, DEC 2, TANDBERG 3).  However, Backup Exec will
    not automatically associate a loader with its tape drive.
    You must manually edit the Hardware Alias of the Loader's
    Tape Drive and click on the correct loader for the tape
    drive.

    Installing Loader Support
    ~~~~~~~~~~~~~~~~~~~~~~~~~
    Installing Loader Support in Backup Exec is a two part
    process.  Follow the instructions in both parts to ensure
    correct loader installation.

    Part A - Installing Backup Exec's Loader Support
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    1.  Double-click on the Backup Exec Setup icon in the Backup
        Exec 6.0 group in Program Manager.

    2.  Click the "Loader" button and follow Setup's
        instructions.


    Part B - Installing the Medium Changer Device Driver
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    Use Windows NT Setup to install the Medium Changer Device
    Driver:

    1.  Double-click the "Windows NT Setup" icon in the "Main"
        program group.

    2.  Select "Add/Remove Tape Devices..." in the "Options" menu
        of Windows NT Setup.

    3.  Select "Add..." in the "Tape Device Setup" window.

    4.  Open/expand the "Device:" list in the "Select Tape Device
        Option" window.

    5.  Select "Other (Requires a disk from a hardware
        manufacturer)" at the bottom of the "Device:" list in the
        "Select Tape Device Option" window.

    6.  Enter the drive/path to the appropriate files on this
        disk in the "Insert Diskette" window (e.g., "a:\i386" for
        the files for the Intel (i386) version of Windows NT,
        "a:\mips" for the files for the Mips version of Windows
        NT, and "a:\alpha" for the files for the Alpha version of
        Windows NT).

    7.  Select "OK" in the "Insert Diskette" window.

    8.  The "Select OEM Option" dialog will appear.  Select the
        "Arcada supported SCSI-2 Medium Changer" driver.

    9.  Select "OK" in the "Select OEM Option" window.

    10. Select "Install" in the "Select Tape Device Option"
        window.

    11. If a copy of the driver is already on the system, a
        dialog will appear asking to install the current driver
        or install the new driver.  Select "New" in the
        "Windows NT Setup" window; otherwise, enter the same
        drive/path to the appropriate files on this disk that
        was used in step #6 above.

    12. Select "Continue" in the "Windows NT Setup" window.

    The "Tape Device Setup" window will re-appear with the Medium
    Changer selected in step #8 now included in the "Tape
    Devices installed on ..." list. Close the "Tape Device
    Setup" window, close/exit Windows NT Setup, and restart
    Windows NT to activate the changes made.

    Cleaning your Loader Automatically
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    To configure Backup Exec to clean your Loader on a scheduled
    basis, follow these directions:

    1.  Create a Loader Magazine Definition with one group
        designated as "Clean Slot" and assign it the last slot in
        the magazine.  Then assign the other slots in the
        magazine to groups according to your backup strategy.

    2.  Insert a cleaning tape into the slot you designated as
        "Clean Slot".

    3.  Create a new job called "Cleaning Tape" and assign it any
        valid selection file.

    4.  Finally, schedule the "Cleaning Tape" job according to
        the Loader Manufacturer's suggested cleaning cycle.

    Cleaning Tape Delay - To allow enough time for some loaders
    to complete a cleaning tape cycle, Backup Exec employs a
    Cleaning Tape Delay.  This delay affects all types of
    loaders and is set to 420 seconds (7 Min.) by default to
    accommodate loaders with the slowest cleaning tape cycles.
    However many loaders, especially those with DAT drives,
    need much less time for a cleaning tape cycle.  If you are
    adept at using RegEdt32, set the "Cleaning Tape Delay Time"
    value in the HKEY LOCAL MACHINE/SOFTWARE/ARCADA/
    BACKUP EXEC/BACKUP DEVICE/(ALIAS NAME) - the name you gave
    the loader during hardware setup - Loader key for the loader
    connected from the list below.

        ADIC 4mm DAT Autochanger  = 15 sec.
        ADIC VLS 8mm DAT Loader   = 360 sec.
        Compaq 4586 Loader        = 15 sec.
        Conner Diamondback Loader = 15 sec.
        Conner 7L-DLT             = Leave at default (420 sec.)
        Conner 5L-DLT             = Leave at default (420 sec.)
        DEC TLZ6 Loader           = Leave at default (420 sec.)
        DEC/Cipher L860 (L7a)     = Leave at default (420 sec.)
        DEC DLT2500 Loader        = Leave at default (420 sec.)
        Dilog Libra Loader        = 15 sec.
        Exabyte 10e Loader        = 15 sec.
        Exabyte 10i Loader        = 15 sec.
        Exabyte 210 Loader        = 240 sec.
        HP 1553A Loader           = 15 sec.
        HP SureStore 1200E        = 15 sec.


    Notes on specific loaders
    ~~~~~~~~~~~~~~~~~~~~~~~~~

    Spectra Logic  SPECTRA 4000 Tape Library
    ---------------------------------------------------------
    firmware tested: changer 0102, tape drives (HP 1533) 9406

    This loader's touch pad is not disabled during Backup Exec
    operation.  The only functionality that is disabled is tape
    movement from slots to the access door.  Therefore, it is
    possible to move tapes around in the magazine, to and from
    tape drive(s), causing various Backup Exec hardware errors.
    Occasional failure to eject tape at end of scheduled job
    causes future jobs scheduled for that tape drive to abort.
    The cleaning tape delay can be reduced to 60 seconds from the
    default of 420 seconds.

    IBM 4586 DiamondBack
    ------------------------------
    firmware tested: changer and tape drive !D04BJ

    This loader uses one SCSI ID and two Logical Unit Numbers (LUN).
    The cleaning tape delay can be reduced to 60 seconds from the
    default of 420 seconds.

    Lago LS/380 DataWheel
    ------------------------------
    firmware tested: changer 5.4, tapes drives (Exabyte 8500)
     06L0

    This loader uses three SCSI IDs.

5. CONTACTING ARCADA SOFTWARE
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

--------------------------------------------------------
TECHNICAL SUPPORT, PRODUCT INFORMATION, & BULLETIN BOARD
--------------------------------------------------------

Please refer to the Customer Service Guide included with the
product.


------------------------------
PURCHASE & PRICING INFORMATION
------------------------------

Please call 1-800-3ARCADA (1-800-327-2232)

Available weekdays from 8:30 a.m. to 8:00 p.m. (Eastern Time)

End of readme.
