Tivoli Header
Tivoli Storage Manager for NetWare Backup-Archive Client Installation and User's Guide
Following is a summary of changes since Tivoli Storage Manager Version
4.2:
- Enhanced Web Client Interface
- The Web client interface is enhanced to support a JRE 1.3.1
Swing-enabled browser. The Web client facilitates the use of assistive
devices for users with disabilities and contains improved keyboard
navigation.
- Support for Long File Names for Backup Sets
- Tivoli Storage Manager supports the use of long file names for backup sets
on the NetWare client. See Location for more information.
- Support for Long File Name Conversions
- Tivoli Storage Manager supports long file name conversions without being
affected by the memoryefficientbackup option. See Support for Long Names for more information.
- Support for files greater than 4 GB on Novell Storage Services (NSS)
Volumes
- Tivoli Storage Manager supports files larger than 4 GB for NSS file spaces
on NetWare 5.1 and NetWare 6. See Maximum File Size for Operations for more information.
- Multiple Session No Query Restore
- The backup-archive clients can now utilize multiple restore sessions for
no query restore operations, increasing the speed of restores. This is
similar to the multiple backup session support. It exploits the mount
point available on the server. If data is backed up on multiple tapes,
and if the server has multiple mount points available, then the restore starts
a session for each tape, up to the number your administrator
configures. See Resourceutilization for more information.
- Consistent Client Return Codes
- Reliable, consistent, and documented return codes have been added to the
command line client and the scheduler. This facilitates automation of
client operations via user-written scripts. By using the QUERY
EVENT command with the FORMAT=DETAILED option,
administrators can now distinguish between scheduled backups that completed
successfully with no skipped files and scheduled backups that completed
successfully with one or more skipped files. Also if you use the
processing optionpreschedulecmd to run a command, and that command
returns a non-zero return code, the scheduled event will not run. This
ensures that scheduled events will not run if prerequisite commands do not
complete successfully. See Return Codes from the Command Line Interface, Preschedulecmd, and Postschedulecmd for more
information.
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]