Administrator's Guide

Changes for Version 3--October 1997

The new functions of ADSM Version 3 are:

Event logging and monitoring

You can set up event logging of ADSM client and server events. See "Using Event Logging" for details.

SQL queries of the ADSM database

You can use SQL queries to get information about the ADSM server and clients. See "Using SQL to Query the ADSM Database" for details.

Storing data on another ADSM server

You can store data for one ADSM server (a source server) on another ADSM server (a target server). Using another ADSM server is especially useful for storing backups of the ADSM database and ADSM storage pools. See Chapter 4. "Storing Data on Another Server" for details.

Server file aggregation

ADSM allows small client files to be combined and stored as larger aggregated files. Aggregation can improve performance in some cases and reduce database overhead. See "How ADSM Stores Files in a Storage Pool Hierarchy" for details.

Device support

Device support has been enhanced to allow ADSM to use the following devices:

• IBM 3570 tape devices.

• Optical devices that use 12-inch and 14-inch write-once optical cartridges.

• DTF tape devices.

• Tape devices that are supported by AIX device drivers (instead of ADSM device drivers). These devices have the device type of GENERICTAPE.

See Chapter 8. "Defining Device Classes" for details.

A LABEL LIBVOLUME command allows you to label and check in volumes to an automated library in one step. See "Labeling Sequential Access Volumes" for details.

Administrative client web interface

You can access ADSM server functions from any workstation that is connected to your intranet. The workstation must have a web browser that supports HTML 2.0 or higher, but does not need to have an administrative client installed. See ADSM Quick Start for details.

Immediate processing of commands on a client

You can use an ADSM administrative command to run operations immediately on a client workstation. See "Issuing Commands for Immediate Processing on a Client Node" for details.

Point-in-time restoration of client files

Clients can restore files to a specific point in time if incremental backups have been performed and policy is set up appropriately. See "Special Considerations: Enabling Point-in-Time Restore for Clients" for details.

Restarting client restoration sessions

Clients can restart restore sessions that have been interrupted. Administrators can request information about these sessions and cancel them. See "Managing Client Restartable Restore Sessions" for details.

Defining client options at the server

You can define sets of client options at the server, and assign a set to a client when registering the client. See "Defining Client Options from the Server" for details.

Changing server options without stopping the server

You can change some server options and have the changes take effect without stopping and starting the server. See "Adding or Updating Server Options" for details.