Tivoli Storage Manager for Windows: Administrator's Reference


Changes for Version 4 Release 2--June 2001

The following changes have been made for this edition:

Tivoli Storage Manager (TSM) Management Console
The TSM Management Console is a Microsoft(R) Management Console (MMC) snap-in that provides all of the function previously available in the TSM Server Utilities interface. In addition, the TSM Console provides the following:

The MMC framework allows you to create custom consoles that can incorporate different toolsets to support various administrative roles. For more information about MMC components and features, refer to the Windows online help.

Expanded Support for Managed System for SAN Environments
The types of clients that can use LAN-free data transfer now include backup-archive clients and API clients on Windows, AIX(R), and Sun operating systems. Also now included are additional Tivoli Data Protection application clients, on the Sun and AIX operating systems. Tivoli Data Protection application clients for Microsoft Exchange Server, Microsoft SQL Server, and Lotus(R) Domino(TM) already had this support.

See TSM Managed System for SAN Storage Agent User's Guide and the user's guide for the appropriate client.

See the following new server option:

RESOURCETIMEOUT

Additional Devices that Support LAN-Free Data Transfer for Clients
Support has been added for using the following devices for LAN-free data transfer:

See the following changed commands:

DEFINE DRIVEMAPPING

DEFINE DEVCLASS (TYPE= FILE)

DEFINE DRIVE

DEFINE LIBRARY

UPDATE LIBRARY

See also TSM Managed System for SAN Storage Agent User's Guide.

SCSI Tape Failover
Tivoli Storage Manager supports Microsoft Cluster Services (MSCS) in a Microsoft Datacenter Server operating environment. However, MSCS does not support the failover of tape devices. When correctly set up, TSM servers in a cluster can now support SCSI tape failover. The server cluster uses and is limited to two computers. The computers must be physically connected to each other and must exclusively share a SCSI bus to which the tape devices are attached. When failover occurs, the remaining TSM server issues a SCSI bus reset during initialization, which allows the server to acquire the tape devices. See Administrator's Guide.

Maximum Size of the Recovery Log Increased
The maximum size of the recovery log is increased to 13GB. Significantly increasing the size of your recovery log could also significantly increase the time required to restart the server, to back up the database, and to restore the database. See the following changed commands:

DEFINE LOGVOLUME

DEFINE SPACETRIGGER

UPDATE SPACETRIGGER

Using the TSM Client Acceptor to Manage the Scheduler
The client acceptor daemon or service manages the Web backup-archive client. Users can now select to have the client acceptor also manage the scheduler on the clients. The client acceptor starts the scheduler and the client only when needed to run a TSM schedule. Using the client acceptor to start the scheduler can alleviate problems with memory consumed by the scheduler. Also, if users are already running the client acceptor to manage the Web client, they can reduce the number of processes running continuously on their machines. See the user's guide for the appropriate client.

Improved ANR9999D Messages
By setting message context reporting to ON, you get additional information when the server issues ANR9999D messages. The additional information can help to identify problem causes. See the following new command:

SET CONTEXTMESSAGING

Also see Messages.

Support for Unicode-enabled Client File Spaces
For Windows NT(R) and Windows 2000 client systems that are Unicode, the server now supports storing Unicode file space names, directory names, and file names in Unicode-enabled file spaces. Unicode is a universal character encoding standard that supports the interchange, processing, and display of text that is written in any of the languages of the modern world. The Unicode-enabled TSM client software must be installed on the client systems. New clients that do not yet have data stored on the server automatically store data in Unicode-enabled file spaces.

While clients that already have data stored on the server will store any new file spaces as Unicode-enabled, these clients do not automatically store their existing data in Unicode-enabled file spaces. As an administrator, you can migrate these clients by using the function for automatic file space renaming. TSM renames existing file spaces to force the creation of new, Unicode-enabled file spaces. You can also allow clients to make the choice about renaming. Once the existing file spaces are renamed on the server, a backup or archive operation causes the file spaces to be created again in server storage, this time as Unicode-enabled file spaces. If you have a large number of clients that are Unicode, or a large amount of data on clients that are Unicode, you need to plan the migration. For information on migration, see Administrator's Guide.

The addition of support for Unicode may affect the results of some SELECT commands, because the sorting of information such as file space names is affected.

See the following changed commands for details:

DELETE FILESPACE

EXPORT NODE

GENERATE BACKUPSET

IMPORT NODE

QUERY BACKUPSETCONTENTS

QUERY CONTENT

QUERY FILESPACE

QUERY NODE

QUERY OCCUPANCY

QUERY RESTORE

REGISTER NODE

RENAME FILESPACE

UPDATE NODE

Support for Long File Names
Support for long file names has been added. See the following changed commands:

DEFINE DBCOPY

DEFINE DBVOLUME

DEFINE DEVCLASS (TYPE=FILE)

DEFINE LOGCOPY

DEFINE LOGVOLUME

DEFINE VOLUME

UPDATE DEVCLASS (TYPE=FILE)

Reclaiming Space in Aggregates During Data Movement
You can specify to have the server reconstruct aggregates during data movement. Reconstruction reclaims empty space that has accumulated as a result of deletion of logical files from an aggregate. See the following changed command:

MOVE DATA


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]