----------------------------------------------------------------------

Avail NetSpace 3.50 README.TXT                       December 18, 1995

----------------------------------------------------------------------



This file contains important information about NetSpace configuration,
utilities, and troubleshooting methods.  You should print this file
and keep it as a reference with other NetSpace documentation.

WARNING:    Currently, NetWare 3.x has severe problems with losing
            extended attributes if a volumes block size is greater
            than 4k.  Novell does have a patch that can be acquired
            through their BBS. The patch is named EAALLCFX.NLM.

WARNING:    Novell's NW 4.10 has, as of this writing, a problem with
            volume compression.  When all files eligible for
            compression have been compressed and the volume is filled
            to the point that a compressed file cannot be
            uncompressed, trying to access a compressed file results
            in the server reporting an inability to uncompress the
            file; the client reports an Invalid Function.  Attempting
            to access the file again results in the client locking up
            and the server may lock up.  Novell does have a patch
            available.

WARNING:    If running NetWare 4.10 on the NetSpace HSM server, it is
            best to avoid using the SYS: volume as the installation
            volume.  Currently, if the SYS: volume crashes for any
            reason the user may be forced to reinstall NetWare.

WARNING:    If running NetWare 4.10 on the NetSpace HSM server and
            managed servers, make sure that the server language is the
            same on all servers.

NOTE: NetSpace will only work under NetWare 4.x with bindery emulation
      enabled.


----------------------------------------------------------------------
                              CONTENTS
----------------------------------------------------------------------

1.  WHAT'S NEW IN NETSPACE 3.50

    1.1  Usability Enhancements
    1.2  Performance Enhancements
    1.3  Reliability Enhancements
    1.4  Diagnostic Enhancements


2.  PRIMARY NETWORK BACKUP/RESTORE AND NETSPACE

    2.1  Required Backup Product Capabilities
    2.2  Backup Procedure for Managed File Server Volumes
    2.3  Backup Procedure for NetSpace System and Domain Volumes
    2.4  Scheduling Backups and Sweeps
    2.5  General Restore Information
    2.6  Restore Procedure for Managed File Server Volumes
    2.7  Restore Procedure for NetSpace System and Domain Volumes
    2.8  Overall Recovery Procedure for a Site Wide Disaster


----------------------------------------------------------------------
                   1. WHAT'S NEW IN NETSPACE 3.50
----------------------------------------------------------------------
* Microsoft Windows graphical user interface (GUI)
* Documentation in softcopy format
* Usability enhancements
* Performance enhancements
* Reliability enhancements
* Diagnostic enhancements


1.1 USABILITY ENHANCEMENTS:
----------------------------------------------------------------------
    - The install program will install off of CD instead of flexible
      diskettes.  This will result in a much faster installation time.

    - Placeholder files may now be relocated from one managed volume
      to another, as long as both volumes are managed by the same HSM
      server.  Care must be taken to preserve the extended file
      attributes on placeholders when moving them.

    - SCSI Adapter/ID pairs that are to be excluded from the NetSpace
      SCSI bus scan are now configurable via a new initialization
      file, AVDEVICE.INI (found in the HSM\INI directory of the HSM
      server's HSM system volume).

    - Placeholder files that are viewed via the DOS DIR command,
      Windows File Manager, etc., will now display the file size at the
      time of migration, not the placeholder stub file size. This
      enhancement makes it possible for the XCOPY and PKZIP programs
      to operate correctly, with no HSM awareness.  UNIX clients will
      also benefit from this enhancement.  NOTE: If desired, this new
      feature can be disabled on a workstation with the AVSETHSM /Z0
      option.  AVSETHSM.EXE can be found on the domain server in the
      HSM\EXE directory.

    - The minimum migratable file size for NetWare 4.x managed server
      volumes now takes into account the NetWare block sub-allocation
      parameter.  With block sub-allocation, the minimum migratable
      file size now becomes 512 bytes plus catalog and EA overhead
      instead of the volume block size plus catalog and EA overhead.

    - The maximum number of file exclusion rules that may be set for a
      single managed volume has been increased from 30 to 100 rules.

    - On the HSM console screen, the keystroke used to shut down the
      HSM has been changed from CONTROL-S to CONTROL-Q in order to
      avoid inadvertently shutting down the HSM when all that was
      desired was to delete the currently displayed notice (keystroke
      CONTROL- D, which is right next to CONTROL-S).

    - The HSM now supports the re-enabling of critical migrates and
      low space scans without having to take the HSM offline and back
      online again.  This new feature is accessible under the
      Status tab of the Managed Volume window in the new Storage
      Manager program.

    - It is now possible to disable critical migrate and low space
      scan activity for an HSM server. For some HSM applications,
      customers find it beneficial to disable this automatic
      management feature of  NetSpace.  These options can be set via
      the HSM Setup program (AVSETUP.NLM).

    - Optional primary backup:  In some very specific HSM
      applications, it is not necessary to require that files be
      backed up via the primary storage backup system prior to
      migration into secondary storage.  Additionally a few backup
      products do not reset the "archive needed" file attribute bit
      when backing up a file.  The HSM server now supports the ability
      to specify the file backup requirement, via the HSM Setup
      program (AVSETUP.NLM).  Three options are available:

          1. Use the "archive needed" file attribute to determine
             whether or not a file is backed up prior to migrating it
             into secondary storage.

          2. Use the "archive date" file attribute to determine
             whether or not a file is backed up prior to migrating it.

          3. Do not require the file to have been backed up prior to
             migrating it.

      Contact Avail Technical Support before changing the primary
      storage backup requirement.

    - Optional secondary backup:  In rare instances, it is not
      necessary to require that data migrated to secondary storage be
      backed up via the HSM backup function.  The HSM server now
      supports the ability to specify whether secondary storage backup
      is required.   

      Contact Avail Technical Support before changing the secondary
      storage backup requirement.

    - With release 3.50, the HSM Application Programming Interface
      (HAPI) is available for third party applications and OEMs to
      customize the end user interface to the NetSpace system.  The
      HAPI is available as either an object library for DOS programs,
      a NetWare NLM, or a Windows DLL.  Call Avail Systems Corp. at
      1-800-96AVAIL for further information.


1.2 PERFORMANCE ENHANCEMENTS:
----------------------------------------------------------------------
    - Recall operations no longer require access to the storage
      catalog that the HSM keeps on the managed volume.  This results
      in a faster response on recall requests, as recalls do not have
      to compete with migration activity for access to the storage
      catalog.

    - The storage catalogs maintained by the HSM have been totally
      redesigned for faster access during migration activity, and for
      improved scalability on very large managed volumes.

    - Compatibility is maintained with old placeholders and old
      storage catalogs.  The upgrading of placeholders and storage
      catalogs is optional (but highly recommended), and can be
      accomplished at any time via the new Rebuild Storage Catalog
      feature of the Database Recovery Manager program.

    - The automatic backup of Backup Access Groups (BAGs) has been
      optimized to avoid holding up migrations whenever possible.

    - The remote procedure call (RPC) and file system information
      components of NetSpace have been improved to provide more
      efficient operation during the scanning of managed volumes and
      during data migration operations.

    - Data transfer performance for 8mm Exabyte tape transports has
      been improved by eliminating a redundant verification step from
      the data transfer operation.


1.3 RELIABILITY ENHANCEMENTS:
----------------------------------------------------------------------
    - The storage catalog that is maintained on managed volumes by the
      HSM server has been redesigned to reduce the possibility that a
      user will inadvertantly delete it.

    - Placeholders have been redesigned to allow recall of migrated
      data without the need for storage catalog access.  The function
      of the storage catalog is now primarily to provide redundancy
      for disaster recovery.

    - HSM detection of damaged data in secondary storage has been
      improved.  Damage to secondary storage migrate volumes can occur
      when the NetWare operating system that is hosting the HSM server
      crashes, if problems occur with the File Allocation Table on a
      migrate volume, or if power is unexpectedly cut to the HSM
      server.  The HSM server performs an integrity check on each
      migrate volume when the system is started or brought online, and
      also prior to copying a migrate volume's data to either a lower
      secondary storage layer or to the HSM backup device.  Early
      detection of damage to data on migrate volumes enables better
      fault isolation and data recovery.


1.4 DIAGNOSTIC ENHANCEMENTS:
----------------------------------------------------------------------
    - A new Rebuild Storage catalog feature has been added to The
      Database Recovery Manager program (AVRECMAN.NLM).

    - The HSM server now supports browsing the Error Log from the HSM
      console screen.  The keystroke CONTROL-E invokes the error log
      browser.

    - A new DOS utility (AVSTOCAT.EXE) will display a high level dump
      of the contents of the storage catalog.  This dump is more along
      the lines of a directory listing of storage catalog contents.
      File specifications with wildcards are supported to restrict the
      dump output to a particular file or range of files.  Options for
      searching subdirectories, pausing with each screen full of
      information, and tailoring the output information are provided.

    - A Make Placeholder DOS utility program (AVMAKEPH.EXE) is
      provided with release 3.50 that gives the administrator the
      ability to recreate placeholders that have been lost or damaged.
      Specification of which placeholder to recreate may be done via
      the DOS command line, or from a list stored in a file. (The
      AVSTOCAT.EXE program has an option to create this list file,
      which may be edited with any standard text editor.)

    - A Backup Access Group (BAG) Table of Contents Dumper DOS utility
      program (AVBAGTOC.EXE) is provided that will generate a list of
      files that are contained within a specific BAG in secondary
      storage.

    - A Backup Cartridge Table of Contents Dumper DOS utility program
      (AVBKPTOC.EXE) is provided that will generate a list of BAGs
      that are backed up on a specific secondary storage backup tape
      (or tapes).  The utility also provides information about which
      backup cartridges are media replaceable units (MRUs).


----------------------------------------------------------------------
            2. PRIMARY NETWORK BACKUP/RESTORE AND NETSPACE
----------------------------------------------------------------------

2.1 Required Backup Product Capabilities
----------------------------------------------------------------------
In order for NetSpace and primary storage backup systems to cooperate
successfully, a few guidelines must be observed.  This is necessary
to keep the backup system from recalling files and to allow the
backup system to get a consistent image of the primary storage
volumes.

    - The backup system chosen must not alter a file's Last Accessed
      Date when backing up files.  Most backup systems designed for
      NetWare do not alter the date.  If your backup system alters the
      Last Access Date it will prevent files from aging enough to
      migrate.

    - The backup system should backup and restore a file's OS/2 style
      Extended Attributes.  This is necessary if you wish to use the
      zero length placeholder option.  All SMS compatible backup
      systems will backup and restore the Extended Attributes.
      Before choosing the zero length placeholder option you must
      verify that your backup system will backup and restore the
      Extended Attributes.


2.2 Backup Procedure for Managed File Server Volumes
----------------------------------------------------------------------
This section describes the procedure for backing up file servers
being managed by the NetSpace system.  These steps are necessary to
allow the backup system to get a copy of the managed volume's files
and the NetSpace catalogs that are consistent.  It also allows the
backup system to backup and restore placeholder files without
recalling them.

If you have an SMS compatible backup system and have the latest Target
Service Agents (TSAs) (Version 4.02f or later) for your NetWare 3.x
and 4.x servers the backup notification will be sent by the TSA when a
backup or restore is started.  This may be verified by watching the
AVRECALL screen of a server when a backup or restore starts.  You
should see a message indicating that the backup has started.  NetSpace
will terminate any migration jobs running for that server and not
start any new jobs until the backup/restore is complete.  In this
configuration AVLOGMON is not required.

If you have a non-SMS backup system or do not have the latest Novell
TSAs, the preferred method is to dedicate a login name on each
managed file server for backup (some products have a pre-assigned
login name).  It may be a different login name on each server,
however it will be easier for you to manage if it is the same login
name on all servers.  This login name should only be used to login
when a backup or restore is being performed.  The program
AVLOGMON.NLM should be loaded on each managed server.  AVLOGMON will
detect when the backup user logs into the server and will inform the
NetSpace system that a backup or restore is taking place.  The
NetSpace system will suspend migration activity on that server until
the backup/restore is complete.  Demand Recalls will still work for
other users, however the connection that the backup user is using
will be disabled so it can access placeholders without recalling
them.  The backup user should logout as soon as possible after the
backup/restore is complete.  This will allow the NetSpace to resume
activity on that server.

To set up a server, edit the AUTOEXEC.NCF file to include the
following line (see information about specific products below):

                load AVLOGMON /Busername

The "username" parameter should be set to the login name you wish to
dedicate for backup.  Once this is done you should either restart the
server or manually load AVLOGMON from the server console.

Once this step is complete you may run your backup/restore as you
normally would - just be sure that the backup system logs in as the
backup user.

If you have a DOS based backup system you may use an alternate method
to backup/restore servers.  This method uses the DOS program AVSETHSM
to inform the NetSpace that a backup/restore is beginning or ending.
To use this method you need to run AVSETHSM before and after the
backup/restore session.  For instance:

        AVSETHSM /Sserver /B11  ; (Tell NetSpace backup is starting)
        XXX                     ; (Run your backup program)
        AVSETHSM /Sserver /B12  ; (Tell NetSpace backup is complete)

For a description of all of the parameters for AVSETHSM see the
NetSpace Installation Guide, or run AVSETHSM with no parameters to
display the parameters on your screen.

Both of these methods require AVRECALL to be loaded on any managed
file server that is being backed up.

The only other safe method of backing up is to unload AVRECALL from
the server being backed up and shut down the NetSpace system.  This
is the least desirable since it means that Demand Recalls will not
work while the backup is running and that other servers are affected
along with the server being backed up.


2.3 Backup Procedure for NetSpace System and Domain Volumes
----------------------------------------------------------------------
The NetSpace system may remain on-line during backup of the NetSpace
system volume.  If the NetSpace domain volume is also a managed
volume, then the procedures for a managed volume apply (see the
preceding section).  Otherwise, the NetSpace domain volume may be
backed up while NetSpace is on-line.  No special procedures are
required for backup.  However, a special procedure is required for
restoration of a NetSpace system or domain volume.  Details on
restoration procedures are discussed later.


2.4 Scheduling Backups and Sweeps
----------------------------------------------------------------------
To avoid interrupting HSM Sweep jobs unnecessarily, the optimal
arrangement for nightly primary storage backup and NetSpace volume
Sweep jobs is to schedule them so that they are unlikely to overlap
with each other.  In other words, avoid scheduling Sweep and backup
jobs to run against the same file server at the same time.  Some
experimentation may be necessary to determine how long Sweep and
backup jobs take to run.

The correct order to backup primary storage volumes is: backup the
managed volumes first, then the domain volume, then the NetSpace
system volume.  Do not back up any of the NetSpace migration
volumes;  they are protected by the NetSpace secondary storage
backups.


2.5 General Restore Information
----------------------------------------------------------------------
Since each disaster situation is unique, it is a good idea to contact
technical support when recovering from any disaster involving HSM.
Sometimes significant time can be saved by following the advice of
qualified technical support personnel.


2.6 Restore Procedure for Managed File Server Volumes
----------------------------------------------------------------------
When restoring an entire managed file server volume from primary
storage backup, no special procedures are required.  The storage
catalog files that reside on the volume will be synchronized with the
placeholder files for that volume if the backup procedure discussed
above has been followed.

When restoring only selected directories on a managed file server
volume, no special procedures are required, as long as the
directories being restored do not include the HSM directory and/or
any of its subdirectories.  This is where the NetSpace storage
catalog files are kept.

If the NetSpace storage catalog files are lost and must be restored
from backup, be aware that access to any file migrated since the
catalog files were backed up may be lost.  In this case, contact
Technical Support for assistance.


2.7 Restore Procedure for NetSpace System and Domain Volumes
----------------------------------------------------------------------
If the NetSpace system or domain volume must be recovered from
primary storage backup, make sure that the NetSpace system is
shutdown, if it is not already.  Restore the volume via your primary
storage backup product.

If the system volume has been restored, before bringing up NetSpace,
run the AVRECMAN program on the NetSpace storage server.  Choose the
Synchronize Databases option, specify that the system volume NOT be
used as the reference for synchronization.  Once this step is
complete, exit AVRECMAN and start NetSpace.

If the domain volume has been restored, before bringing up NetSpace,
run the AVRECMAN program on the NetSpace storage server.  Choose the
Synchronize Databases option, specify that the system volume IS to be
used as the reference for synchronization.  Once this step is
complete, exit AVRECMAN and start NetSpace.

If the synchronization via AVRECMAN fails, consult the chapter on
Database Recovery Manager in the NetSpace Administrator's Guide for
alternate recovery procedures.


2.8 Overall Recovery Procedure for a Site Wide Disaster
----------------------------------------------------------------------
If an entire site has been destroyed in a disaster, recovery is still
possible if off site copies of primary and secondary storage backups
have been kept.  Procedures for recovery of a disaster of this
magnitude are quite involved, unique for each organization, and
beyond the scope of this document.  However, a very high level view
of the recovery would include the following steps:

    1. Rebuild the physical facility, or move to an alternate
       facility.

    2. Acquire and install new hardware for the network,
       workstations, file servers, and NetSpace server.

    3. Restore/reinstall base operating system code on all computers.
       At this point you may bring up the base operating system on
       the NetSpace storage server, but do not start the NetSpace
       system yet.

    4. Restore all files to workstations, file servers, and the
       NetSpace server from primary storage backups.


    At this point call Avail Technical Support for assistance with the
    following three steps.

    5. Before starting NetSpace for the first time, run the AVRECMAN
       program on the NetSpace storage server.  Choose the Restore
       Databases option.  Once this step is complete, exit AVRECMAN
       and start NetSpace by typing LOAD AVSERVER /OFFLINE.

    6. Run the AVMEDMAN program on the NetSpace storage server.  Use
       the Replace Media option to restore secondary storage media
       from the NetSpace secondary storage backups.

    7. Exit AVMEDMAN and put the NetSpace server ONLINE.  NetSpace
       will initiate restore-BAG activity - there may be a
       considerable amount of activity depending on how much data
       needs to be restored from HSM backup to secondary storage.  Be
       prepared to respond to mount requests for the HSM backup
       tapes.


----------------------------------------------------------------------
                       End of README.TXT file
----------------------------------------------------------------------        
