IBM Tivoli Storage Manager
for Linux
Quick Start
Version 5 Release 2
GC23-4692-01
IBM Tivoli Storage Manager
for Linux
Quick Start
Version 5 Release 2
GC23-4692-01
Note
Before using this information and the product it supports, read the general information under Appendix G, “Notices”, on
page 79.
Second Edition (April 2003)
This edition applies to Version 5 Release 2 of IBM Tivoli Storage Manager for Linux (program numbers 5698-ISM,
5698-ISX, 5698-SAN, and 5698-HSM) and to any subsequent releases until otherwise indicated in new editions.
Order publications through your IBM sales representative or the branch office that serves your locality.
Your comments are important to help us provide the most accurate, quality information. If you have comments
about this book or any other IBM Tivoli Storage Manager documentation, please see “Contacting Customer
Support” on page 75.
© Copyright International Business Machines Corporation 2002, 2003. All rights reserved.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
Summary of Changes for IBM Tivoli
Storage Manager Version 5 . . . . . . v
Chapter 4. Customizing Your IBM Tivoli
Storage Manager System . . . . . . . 35
Technical Changes for Version 5 Release 2—April
2003 . . . . . . . . . . . . . . . . . v
Changes for Version 5 Release 1—March 2002 . . . vii
Increasing Database and Recovery Log Sizes . . .
Increasing Disk Storage Pool Sizes . . . . . . .
Adding Administrators . . . . . . . . . .
Adding Backup-Archive Clients . . . . . . .
Using Tape Devices and Optical Devices. . . . .
Attaching Devices . . . . . . . . . . .
Installing Device Drivers . . . . . . . . .
Adding a Manual Tape Library to the Server . .
Adding an Automated Tape Library to the Server
Displaying Information About Your Devices . .
Preparing Tape Volumes . . . . . . . . .
Including Tape in the Storage Hierarchy . . . .
Migrating Data from Disk to Tape . . . . . .
Creating a New Policy. . . . . . . . . . .
Invoking Expiration Processing . . . . . . . .
Creating a Client Include-Exclude List . . . . .
Automating Client Operations . . . . . . . .
Automating Administrative Commands . . . . .
Protecting IBM Tivoli Storage Manager and Client
Data . . . . . . . . . . . . . . . . .
Before You Begin . . . . . . . . . . ix
What You Should Know First .
IBM Tivoli Storage Manager Web
Accessibility Features . . . .
Conventions Used in This Book .
Types of Information . . .
Where Tasks Are Performed .
Installation and Setup Results .
Basic Tasks. . . . . . . .
Advanced Tasks . . . . . .
. .
Site .
. .
. .
. .
. .
. .
. .
. .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
ix
ix
ix
ix
ix
. . . . . x
. . . . . x
. . . . . xi
. . . . . xii
Chapter 1. Introducing IBM Tivoli
Storage Manager . . . . . . . . . . . 1
Tivoli Storage Manager Architecture . . . . .
Tivoli Storage Manager Server Overview . . .
Tivoli Storage Manager Client Overview . . .
How Tivoli Storage Manager Works . . . . .
Data Management . . . . . . . . . .
Storage Device and Media Management . . .
Putting it All Together . . . . . . . . .
Automating Tivoli Storage Manager Operations
Where to Go From Here . . . . . . . . .
Basic Storage Management Tasks . . . . .
Advanced Storage Management Tasks . . .
. 2
. 2
. 4
. 5
. 6
. 10
. 13
14
. 15
. 15
. 15
Chapter 2. Installing IBM Tivoli Storage
Manager . . . . . . . . . . . . . . 17
Evaluation (Try and Buy) Product . . . . . .
Using Softcopy Documentation . . . . . . .
System Requirements . . . . . . . . . .
Installation and Configuration . . . . . . .
Verifying Your Installation . . . . . . . .
Defining Environment Variables . . . . . .
Getting Started . . . . . . . . . . . .
Starting and Stopping the Server . . . . .
Running Multiple Servers on a Single Machine
Starting and Stopping an Administrative Client
or the Web Interface . . . . . . . . .
Registering Licenses . . . . . . . . .
.
.
.
.
.
.
.
.
17
18
18
20
23
24
25
25
25
. 26
. 27
Chapter 3. Specifying Server and Client
Communication Methods . . . . . . . 31
Setting TCP/IP Options .
Setting HTTP Options . .
Connecting with IBM Tivoli
a Firewall . . . . . .
. . .
. . .
Storage
. . .
© Copyright IBM Corp. 2002, 2003
. . .
. . .
Manager
. . .
. . . 31
. . . 32
across
. . . 32
|
|
35
36
37
37
37
39
40
43
45
46
47
49
49
50
52
52
53
55
55
Appendix A. Using Administrative
Interfaces . . . . . . . . . . . . . 57
Using the Administrative Web Interface . . .
Operation View . . . . . . . . . .
Network View . . . . . . . . . .
Configuration View. . . . . . . . .
Object View . . . . . . . . . . .
Using the Administrative Client Command-Line
Interface . . . . . . . . . . . . .
Starting and Stopping the Interface . . .
.
.
.
.
.
.
.
.
.
.
57
58
60
60
60
.
.
. 62
. 62
Appendix B. National Language
Support . . . . . . . . . . . . . . 63
Appendix C. Applying Updates to Tivoli
Storage Manager . . . . . . . . . . 65
Appendix D. Removing the IBM Tivoli
Storage Manager Server . . . . . . . 67
Before Removing IBM Tivoli Storage Manager .
.
. 67
Appendix E. Setting Up the Secure
Web Administrator Proxy . . . . . . . 69
Prerequisites . . . . . . . . . . . . .
Installing the Secure Web Administrator Proxy Overview . . . . . . . . . . . . . .
Setting Up the IBM Tivoli Storage Manager
Server . . . . . . . . . . . . . .
Installing the Secure Web Administrator Proxy
Using the Secure Web Administrator Proxy . .
. 69
. 70
. 70
. 71
. 72
iii
Moving to Another IBM Tivoli Storage Manager
Server While Using the Web Proxy . . . . .
Uninstalling the Secure Web Administrator Proxy
Troubleshooting the Secure Web Administrator
Proxy . . . . . . . . . . . . . . .
. 72
. 72
IBM Tivoli Storage Manager Publications
IBM Redbooks . . . . . . . . .
Translations . . . . . . . . . .
. 73
Appendix G. Notices . . . . . . . . . 79
Appendix F. Where to Look for
Information . . . . . . . . . . . . . 75
Contacting Customer Support .
Reporting a Problem . . .
Internet. . . . . . . . .
iv
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
IBM Tivoli Storage Manager for Linux: Quick Start
. 75
. 76
. 76
Trademarks .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 76
. 78
. 78
. 81
Glossary . . . . . . . . . . . . . . 83
Index . . . . . . . . . . . . . . . 93
Summary of Changes for IBM Tivoli Storage Manager Version
5
This section summarizes changes that have been made to the IBM Tivoli Storage
Manager product.
Technical Changes for Version 5 Release 2—April 2003
The following changes have been made to the product for this edition:
|
|
|
|
|
|
|
Security: Firewall Support
Tivoli Storage Manager has enhanced support for environments with
firewalls in which communication originating from outside the firewall is
to be restricted. Clients normally contact the server, but with the new
firewall support, you can choose to restrict session initiation to the server.
Scheduled, backup-archive client operations can be restricted to
server-initiated sessions.
|
See Administrator’s Guide and Quick Start for more information.
|
|
See the following new server option:
TCPADMINPORT
|
|
See the following changed server option:
TCPPORT
Reclamation Enhancements
See Quick Start for more information.
Linux for zSeries
The Tivoli Storage Manager server for Linux is now supported on zSeries
hardware.
See Quick Start for more information.
NDMP Operations
File Level Restore Tivoli Storage Manager currently provides backup and
recovery support for network-attached storage (NAS) file servers and
utilizes Network Data Management Protocol (NDMP) to communicate with
and provide backup and recovery services for NAS file servers.
Support for file level restore includes enhancements to allow tracking of
individual files within a backed-up filesystem image. This enhancement
makes it possible to display the contents of an image backup, and
individual files within that image can be selected for restore.
Implementation is achieved by generating a table of contents (TOC) during
backup which is stored on the server.
3494 Library Support NDMP support to the library types IBM 3494 Tape
Library Dataserver and IBM 3495 Tape Library DataServer is now
provided.
EMC Celerra NAS Device Support Backup and restore operations for
EMC Celerra file-servers via NDMP is now supported. This support
includes all base NDMP functions provided for NetApp file-servers as well
as the file-level restore function.
© Copyright IBM Corp. 2002, 2003
v
Accurate SAN Device Mapping
Device IDs within a SAN environment change when a bus reset or other
environmental changes occur. With accurate SAN device mapping, Tivoli
Storage Manager can now detect SAN changes and report that a
reconfiguration is required.
|
|
|
|
|
See Administrator’s Guide for more information.
|
Macintosh OS X Unicode Support for Backup-Archive Client
Unicode filespaces are now supported on the Macintosh client. By
supporting a Unicode-enabled client, the Tivoli Storage Manager server can
store file spaces with Unicode file space names, directory names, and file
names. The client can successfully process a Tivoli Storage Manager
operation even when the file spaces contain directory names or files in
multiple languages, or when the client uses a different code page from the
server.
|
|
|
|
|
|
|
|
See Administrator’s Guide for more information.
|
TapeAlert Device Support
TapeAlert is part of the SCSI specification for providing the software
application with detailed diagnostic information. It captures the TapeAlert
log page from the drive or library when tapes are dismounted or moved in
the library, allowing you to recognize hardware problems as early as
possible.
|
|
|
|
|
|
See Administrator’s Guide for more information.
|
Increased Archive Retention Limits
Tivoli Storage Manager now supports increased retention times for
archives and backup sets. These new retention values will allow data
archives to be kept longer.
|
|
|
|
See Administrator’s Guide for more information.
|
StorageTek VolSafe Support
Tivoli Storage Manager now supports the WORM tape device type
VOLSAFE.
|
|
|
See Administrator’s Guide for more information.
|
Server Performance Tuning
The maximum value of the server option TXNGROUPMAX has been
increased. When transferring multiple small files, increasing the
TXNGROUPMAX option can improve throughput for operations to tape. It
is now possible to set the TXNGROUPMAX option for individual clients.
See Administrator’s Guide for more information.
|
|
|
|
|
|
Licensing Changes
The Websphere Application Server has been added.
Product packaging and name changes
The following table lists changes to product packaging and names for IBM
Tivoli Storage Manager. See
www.ibm.com/software/tivoli/solutions/storage/ for complete details.
Table 1. Product Packaging and Name Changes
vi
Former name
Current name or term
Notes
Tivoli Data Protection for
NDMP
operations that use NDMP
This product is now part of
IBM Tivoli Storage Manager
Extended Edition.
IBM Tivoli Storage Manager for Linux: Quick Start
Table 1. Product Packaging and Name Changes (continued)
Former name
Current name or term
Notes
Tivoli Storage Manager
Managed System for SAN
IBM Tivoli Storage Manager
for Storage Area Networks
This product includes
LAN-free data movement
and library sharing on SANs.
Tivoli SANergy is a separate
product, licensed to users
through this product.
Tivoli Space Manager
IBM Tivoli Storage Manager
for Space Management
The client is called space
manager or HSM client.
Tivoli Data Protection
products
One of the following:
See the Web site for details.
IBM Tivoli Storage
Manager for Application
Servers
IBM Tivoli Storage
Manager for Databases
The clients are frequently
called application clients in the
product information.
IBM Tivoli Storage
Manager for Enterprise
Resource Planning
IBM Tivoli Storage
Manager for Hardware
IBM Tivoli Storage
Manager for Mail
Changes for Version 5 Release 1—March 2002
The following changes have been made to the product for this edition:
Changes in Defining Drives and Libraries
Device special file names and External Library managers are now specified
in the DEFINE PATH and UPDATE PATH commands, rather than in the
DEFINE DRIVE, UPDATE DRIVE, DEFINE LIBRARY, and UPDATE
LIBRARY commands.
See Adding a Manual Library, Adding an Automated Tape Library and
Tivoli® Storage Manager Administrator’s Reference.
Moving Data by Node
You can use the MOVE NODEDATA command to move data in a
sequential-access storage pool for one or more nodes, or move selected file
spaces for a single node. You can also use MOVE NODEDATA to move
data to another storage pool.
See Tivoli Storage Manager Administrator’s Reference.
Support for Simultaneous Writes to Primary and Copy Storage Pools
You can specify copy storage pools in a primary storage pool definition.
When a client backs up, archives, or migrates a file, the file is written to
the primary storage pool and is simultaneously stored into each copy
storage pool.
See Tivoli Storage Manager Administrator’s Reference.
High Availability Cluster Multiprocessing
Tivoli Storage Manager can now use High Availability Cluster
Multiprocessing (HACMP). HACMP provides the leading AIX-based
Summary of Changes for IBM Tivoli Storage Manager Version 5
vii
clustering solution, which allows automatic system recovery during system
failure detection. By using HACMP together with Tivoli Storage Manger,
you can ensure server availability.
Tivoli Data Protection for New Network Data Management Protocol Support
New Network Data Management Protocol (NDMP) support now extends
to the AIX® (32-bit and 64-bit) IBM Tivoli Storage Manager server platform.
The new Tivoli Data Protection for NDMP product supports NDMP
backup and restore for network-attached storage (NAS) file servers from
Network Appliance. NDMP allows a network storage-management
application to control the backup and restore of an NDMP-compliant file
server without installing third-party software on that server. The NAS file
server does not require installation of Tivoli Storage Manager software. The
Tivoli Storage Manager server uses NDMP to connect to the NAS file
server to initiate, control, and monitor a file system backup or restore
operation. The NDMP support for NAS file servers enables higher
performance backup to tape devices without moving the data over the
LAN. TDP for NDMP is a separately priced and licensed product.
See Tivoli Storage Manager Administrator’s Reference.
Data Validation with Cyclic Redundancy Checking
IBM Tivoli Storage Manager provides the option of specifying whether a
cyclic redundancy check (CRC) is performed during a client session with
the server, or for storage pools. The server validates the data by using a
cyclic redundancy check which can help identify data corruption. Data
validation can be enabled for one or all of the following:
v Tivoli Storage Manager client nodes at Version 5.1.
v Tivoli Storage Manager storage agents at Version 5.1.
v Storage pools
See Tivoli Storage Manager Managed System for SAN Storage Agent User’s
Guide and Tivoli Storage Manager Administrator’s Guidefor more information.
New Licensing Method
The new licensing method enables you to register the exact number of
licenses that are required, rather than in increments of 1, 5, 10, and 50.
See Licensing Wizard and Tivoli Storage Manager Administrator’s Reference.
Server Performance Enhancements
There are two new IBM Tivoli Storage Manager performance
enhancements:
v AIX Asynchronous I/O Support. This feature is available via a new
option in the server options file.
v AIX Direct I/O Support. This feature is available via a new option in the
server options file.
See Tivoli Storage Manager Administrator’s Reference.
viii
IBM Tivoli Storage Manager for Linux: Quick Start
Before You Begin
IBM Tivoli Storage Manager provides automated, policy-based storage
management for file servers and workstations. This publication helps you install
and configure a practical system. It explains how to:
v Install the server on Linux
v Define the communication network for server and clients
v Configure IBM Tivoli Storage Manager for your environment
What You Should Know First
Before using this publication, you should be familiar with:
v Linux operating systems
v Devices that Tivoli Storage Manager can use
v Workstation operating systems on which the clients reside
v Communication protocols installed on your client and server machines
IBM Tivoli Storage Manager Web Site
All Tivoli Storage Manager publications are available from the Tivoli Storage
Manager home page on the World Wide Web at this address:
www.ibm.com/software/sysmgmt/products/
support/IBMTivoliStorageManager.html
By accessing the Tivoli Storage Manager home page, you can access subjects that
interest you. You can also keep up-to-date with the newest Tivoli Storage Manager
product information.
Accessibility Features
Accessibility features help a user who has a physical disability, such as restricted
mobility or limited vision, to use software products successfully. These are the
major accessibility features of IBM Tivoli Storage Manager:
v Server and client command line interfaces provide comprehensive control of
Tivoli Storage Manager via a keyboard.
v The Web backup-archive client interface is fully HTML 4.0 compliant and
accessibility is limited only by the choice of Internet browser.
v All user documentation is provided in HTML and PDF format. Descriptive text
is provided for all documentation images.
Conventions Used in This Book
This section describes the conventions used in this book.
Types of Information
The following conventions help you to identify types of information:
Important tips or cautions
© Copyright IBM Corp. 2002, 2003
ix
Detailed information that is useful, but not essential, in performing a task
Tips to help you avoid or correct problems
Where Tasks Are Performed
The following conventions identify where to perform the associated tasks:
Linux
Linux command line
Administrative client command line
Administrative web interface
End user client command line
End user client graphical user interface
Installation and Setup Results
After you complete the tasks in Chapter 2, “Installing IBM Tivoli Storage Manager”
, on page 17, the default IBM Tivoli Storage Manager system will consist of the
following:
The Basic Configuration:
v The default communication method is TCP/IP.
v The server options file (dsmserv.opt) contains server configuration
options.
Database
The database has one 17MB volume named db.dsm. The size of log,
database, and storage pool volumes is for a new install only. If you have a
previous version of Tivoli Storage Manager installed, a migrate install will
occur and the new version will use the previously defined log, database,
and storage pool volumes.
Recovery Log
The recovery log has one 9MB volume named log.dsm.
Disk Storage Pools
The following disk storage pools are created:
v BACKUPPOOL with one 10MB volume defined, named backup.dsm
v ARCHIVEPOOL with one 5MB volume defined, named archive.dsm
One Server Administrator Defined
This server administrator has the following defaults:
v Name: admin
v Password: admin
x
IBM Tivoli Storage Manager for Linux: Quick Start
One Linux backup-archive client defined
This client has the following defaults:
v Name: client
v Password: client
Standard policy
Objects for a default storage policy are defined (all are named
STANDARD). This policy specifies the following:
v When a backed up file is no longer associated with a backup copy
group, it remains in server storage for 30 days.
v When an archived file is no longer associated with an archive copy
group, it remains in server storage for 365 days.
v Client files are not space managed.
v For backup operations:
– Files are backed up to the default disk storage pool, BACKUPPOOL.
– An incremental backup is performed only if the file has changed since
the last backup.
– Files cannot be backed up while they are being modified.
– Up to two backup versions of a file on the client’s system are retained
in server storage. The most recent backup version is retained for as
long as the original file is on the client file system. All other versions
are retained for up to 30 days.
– One backup version of a file that has been deleted from the client’s
system is retained in server storage for 60 days.
v For archive operations:
– Files are archived in the default disk storage pool, ARCHIVEPOOL.
– Files cannot be archived while they are being modified.
– An archive copy is kept for up to 365 days.
Basic Tasks
Here is an overview of the Tivoli Storage Manager installation and customization
tasks.
1. Chapter 2, “Installing IBM Tivoli Storage Manager”, on page 17, which
includes:
a. Installing the server. Information on installing the administrative client is in
the Backup-Archive Clients Installation and User’s Guide.
b. “Starting and Stopping the Server” on page 25
c. “Starting and Stopping an Administrative Client or the Web Interface” on
page 26
d. “Registering Licenses” on page 27
2. Chapter 4, “Customizing Your IBM Tivoli Storage Manager System”, on
page 35, which includes:
a. “Adding Administrators” on page 37
b. “Using Tape Devices and Optical Devices” on page 37
c. “Migrating Data from Disk to Tape” on page 49
d. “Creating a New Policy” on page 50
e. “Automating Client Operations” on page 53
f. “Automating Administrative Commands” on page 55
Before You Begin
xi
Advanced Tasks
To take full advantage of IBM Tivoli Storage Manager, you may want to perform
other tasks described in the Administrator’s Guide, including the following:
Network of servers
Create a network of servers that can:
v Share object definitions such as storage policies, administrators, and
command scripts
v Store information in each other’s storage pools
v Route commands to one or more servers
Server and storage pool protection
v Mirror your database and recovery log
v Back up your database and storage pools
v Recover lost or damaged database and storage pool data
Storage Pools and Volumes
v Back up your storage pools
v Move files from one volume to another
Storage Policies
v Provide clients on some platforms with space management services
v Provide additional functions to backup and archive services
Security
v Let clients access IBM Tivoli Storage Manager without requiring
passwords
v Modify the password expiration interval
v Assign levels of administrator authority
v Specify the minimum password length
v Force a client or administrator to change the password
Server Operations
Monitor and control:
v Server processes
v Client sessions
v Tivoli Storage Manager activity log
v Tivoli Storage Manager accounting records
v Logging facilities used to monitor server activity
xii
IBM Tivoli Storage Manager for Linux: Quick Start
Chapter 1. Introducing IBM Tivoli Storage Manager
IBM Tivoli Storage Manager provides automated, policy-based, distributed data
and storage management for file servers and workstations in an enterprise network
environment. The base functions provided by Tivoli Storage Manager include:
Backup and Restore:
The backup process creates a copy of the file or application data that can
be recovered if the original data is lost or destroyed. Unlike other backup
applications, Tivoli Storage Manager implements a progressive backup
methodology to move data quickly and reliably. Using progressive backup,
the number of file versions maintained by Tivoli Storage Manager and the
length of time they are retained can be specified by the storage
administrator. Refer to “Common Backup Methodologies” on page 6 for
more information.
Backups can be scheduled, performed manually from the Tivoli Storage
Manager client interface, or performed remotely using a Web-based
interface.
The restore process transfers a backup data copy from Tivoli Storage
Manager server-managed storage onto a designated machine.
Archive and Retrieval:
The archive process creates a copy of a file or a set of files and stores it as
a unique object for a specified period of time. This function is useful for
maintaining copies of vital records for historical purposes.
Like the backup process, the archive process can be scheduled, performed
manually from the Tivoli Storage Manager client interface, or performed
remotely using a Web-based interface.
The retrieval process transfers the archival data copy onto a designated
machine.
Instant Archive and Rapid Recovery:
IBM Tivoli Storage Manager allows for the creation of a complete set of
client files, called a backup set, on the Tivoli Storage Manager server system
using the most recent backup versions stored by the server. In a process
called Instant Archive, a backup set is used to retain a snapshot of a client
file system for a designated period of time. The Rapid Recovery process
allow you to copy backup sets onto portable media for LAN-free recovery
of a client system.
IBM Tivoli Storage Manager also offers a number of separately licensed optional
features. These include:
Space Manager Client:
This feature provides for the automatic and transparent movement of
operational data from a client system to server-managed storage. This
process, called Hierarchical Space Management (HSM), is implemented as a
client installation and controlled by policy defined to the Tivoli Storage
Manager server. HSM frees up space on a client machine by using
distributed storage media as a virtual hard drive for that machine. Files are
automatically moved and stored according to size, age, and usage. When a
user accesses this data, it is dynamically and transparently restored to the
client machine.
© Copyright IBM Corp. 2002, 2003
1
Tivoli Storage Manager Architecture
IBM Tivoli Storage Manager is implemented as a client/server software
application. Tivoli Storage Manager uses policies to manage the movement of data
between clients, servers, and storage devices. Table 2 lists the two primary Tivoli
Storage Manager components.
Table 2. Primary Tivoli Storage Manager Components
Component
For more information
Tivoli Storage
Manager Server
Refer to “Tivoli Storage Manager Server Overview”.
Tivoli Storage
Manager Client
Refer to “Tivoli Storage Manager Client Overview” on page 4.
Tivoli Storage Manager Server Overview
The Tivoli Storage Manager server component is installed on the computer that
manages storage devices. The Tivoli Storage Manager server provides the
following functions:
v Data management
v Storage device and media management
v Reporting and monitoring functions
v System security
The Tivoli Storage Manager server application is supported by a relational
database that is specifically designed to manage a data storage environment. The
server database operates transparently, requiring minimal administrative oversight.
The server relies on the database to maintain an inventory of metadata associated
with stored data objects. The database is not used to store actual client data, which
is maintained in server-managed storage.
All database transactions are written to an external log file called the recovery log.
The recovery log can be used to restore the database if necessary.
Tivoli Storage Manager server operations are configured, controlled, and monitored
using graphical or command-line interfaces. Some tasks can be performed several
different ways, so the interface you use depends on the type of task and your
preferences. Support for SQL SELECT statements and ODBC data transfer is also
available for advanced database management and reporting.
Data Management
The Tivoli Storage Manager server uses the database to intelligently map business
goals with storage management policies and procedures. The Tivoli Storage
Manager server tracks the origin and location of each client data copy. Policies
defined to the Tivoli Storage Manager server determine how data copies will be
stored, migrated, and eventually replaced with newer data.
Tivoli Storage Manager typically maintains several incrementally modified versions
of client data files, up to a maximum number defined by the administrator. When
the threshold number of files is reached, the oldest file version is marked for
expiration. A typical Tivoli Storage Manager data management scenario might look
something like this:
A new file is created on a Tivoli Storage Manager client workstation on a
Monday morning.
2
IBM Tivoli Storage Manager for Linux: Quick Start
A scheduled incremental backup of the workstation runs Monday evening.
The Tivoli Storage Manager server stores the file copy and marks it as
ACTIVE.
The next scheduled incremental backup of the workstation runs Tuesday
evening.
The Tivoli Storage Manager server compares the ACTIVE file copy with
the current version on the client node to see if the file has been modified.
If so, the modified version is backed up and becomes the ACTIVE copy.
The previous ACTIVE copy is marked as INACTIVE. Tivoli Storage
Manager will continue to store a new ACTIVE copy and inactivate
previous copies until the number of inactivated copies reaches a limit you
specify or the file is deleted from the client node.
The next scheduled incremental backup of the workstation runs Wednesday
evening.
v If the number of INACTIVE file versions reaches the specified limit:
the oldest INACTIVE file copy is deleted from Tivoli Storage Manager
storage and can no longer be restored.
v If the file has been deleted from the client node: all stored copies of
the file are marked INACTIVE and become eligible for deletion. You can
choose to maintain INACTIVE file versions indefinitely or specify a time
limit.
v If a file has been created and never modified or deleted: the ACTIVE
file version will never expire. Tivoli Storage Manager will maintain its
copy of this file indefinitely.
During expiration processing, the Tivoli Storage Manager server deletes expired
files from storage media and removes associated metadata from the database. Refer
to “Common Backup Methodologies” on page 6 for more information.
Storage Device and Media Management
The Tivoli Storage Manager server provides management function for storage
media and devices. A device driver is provided to run a wide variety of disk,
optical, tape, and robotic storage devices. Many native device drivers can also be
used with Tivoli Storage Manager. Refer to the Tivoli Storage Manager Web site at
www.ibm.com/software/sysmgmt/products/
support/IBMTivoliStorageManager.html
for a complete list of supported storage devices.
During ongoing Tivoli Storage Manager operation, expired files are automatically
deleted from storage media, causing volumes to become fragmented. When an
administrator-defined threshold of available space is reached, Tivoli Storage
Manager automatically reclaims the volume by consolidating its active files and
writing them to another volume. The reclaimed volume is returned to the pool of
available storage media for reuse. Refer to the chapter on media management in
the Administrator’s Guide for more information.
Tivoli Storage Manager also provides an external library manager interface, which
allows you to integrate Tivoli Storage Manager into third-party storage
management environments. Refer to the Administrator’s Guide for more information.
Server Customization
Tivoli Storage Manager server operational parameters, including communications
and performance settings, are defined in a server options file located in the server
Chapter 1. Introducing IBM Tivoli Storage Manager
3
directory. Tivoli Storage Manager sets default values for many of the options
during the initial configuration process. You can modify default options using a
text editor. Refer to the Administrator’s Guide and Administrator’s Reference for more
information about server options.
Tivoli Storage Manager server run-time settings are defined in the Tivoli Storage
Manager server database. These include security, accounting, and activity log
settings. Tivoli Storage Manager provides default values for these settings when
the Tivoli Storage Manager server is initialized. Administrators can modify default
settings using the administrative Web interface or the server command-line
interface. Refer to the Administrator’s Guide for more information about server
settings.
Stand-alone or Network Implementation
It is recommended that you install the Tivoli Storage Manager backup-archive
client on the Tivoli Storage Manager server machine to help you validate your
server configuration. A Tivoli Storage Manager server and client installed on the
same machine can be used stand-alone to manage storage for that machine. More
commonly, network-attached clients will be configured to backup data to the Tivoli
Storage Manager server instance.
Tivoli Storage Manager Client Overview
The Tivoli Storage Manager client component sends data to, and retrieves data
from, a Tivoli Storage Manager server. The Tivoli Storage Manager client must be
installed on every machine that will transfer data to server-managed storage. The
Tivoli Storage Manager server uses a unique node name to identify each Tivoli
Storage Manager client instance. A password can be used to authenticate
communications between the Tivoli Storage Manager client and server. Data can be
recovered to the same client machine that initially transferred it, or to another
client with a compatible file system format.
Client Customization
The Tivoli Storage Manager client basically consists of the software component and
a customization file. This customization file, called the client options file, specifies
client/server communications parameters and other Tivoli Storage Manager client
settings. Client communications parameters must agree with those specified in the
server options file. The client options file is located in the client directory and can
be modified using a text editor. The client graphical interface also provides a
wizard for editing this file.
Within the client options file, an include-exclude list can be specified. This list can be
used to identify how specific files or directories will be processed during backup
or archive operations. Tivoli Storage Manager will back up any file not specifically
excluded. Refer to Backup-Archive Clients Installation and User’s Guide for more
information.
Some client options can also be defined in the Tivoli Storage Manager server
database. Defining these client option sets allows for the centralized management of
certain client operations. Refer to the Administrator’s Guide for more information.
Available Clients
There are several types of Tivoli Storage Manager clients available on a wide
variety of platforms. The following list provides a brief description of some
common Tivoli Storage Manager clients. For more detailed information, including
installation and management instructions, refer to Backup-Archive Clients Installation
and User’s Guide.
4
IBM Tivoli Storage Manager for Linux: Quick Start
Backup-archive Client
The backup-archive client provides standard Tivoli Storage Manager client
function, which includes four operations: backup, restore, archive, and
retrieve. These operations can be performed manually from the client
machine or remotely using a web-based interface. Backup and archive
operations can also be scheduled to run automatically.
An administrative client can be optionally installed with the backup archive
client. The administrative client package consists of the Tivoli Storage
Manager server command line, which can be used to remotely manage a
Tivoli Storage Manager server from a network-attached machine. The
administrative Web interface is also commonly referred to as a Tivoli Storage
Manager administrative client.
The other available Tivoli Storage Manager clients are based on the
backup-archive client but offer additional specialized function.
Tivoli Storage Manager data protection
The Tivoli Storage Manager data protection client, also called an
application client, allows for the backup and restoration of data used by
various business applications. The Tivoli Storage Manager data protection
client receives backup and restore requests from the business application
and translates them for Tivoli Storage Manager server processing. Backup
and restore processing can be done while the business application is on
line. Refer to the Tivoli Storage Manager data protection documentation set
for more information.
Space Manager Client
The Space Manager client, also called a Hierarchical Storage Management
(HSM) client, transparently migrates data from the client hard drive to
Tivoli Storage Manager server-managed storage. When the migrated data is
accessed through the client file system, it is transparently recalled back
onto the local disk. The migration and management of files is controlled by
policy defined to the Tivoli Storage Manager server. End users can also
explicitly migrate and recall data. HSM client function is fully integrated
with Tivoli Storage Manager operational backup and archive functions.
Application Program Interface Client
The Application Programming Interface (API) client allows you to create
custom Tivoli Storage Manager client implementations. The API client can
be used to integrate business applications, such as databases or groupware,
into a Tivoli Storage Manager environment. Refer to IBM Tivoli Storage
Manager Using the Application Program Interface for more information.
How Tivoli Storage Manager Works
Tivoli Storage Manager is a highly flexible and scalable product that provides the
capability for fully managed storage. With Tivoli Storage Manager’s extensive
functionality, however, comes a certain amount of complexity. It is important to
take the time to learn and understand the Tivoli Storage Manager approach to
storage management. Tivoli Storage Manager differs from other common storage
solutions in several significant ways, including its client/server architecture,
progressive backup methodology, and unique data and storage policy objects.
This section provides a high-level overview of the Tivoli Storage Manager product
model, with an emphasis on its unique features. Table 3 on page 6 describes the
two interrelated discussions that make up the product model overview.
Chapter 1. Introducing IBM Tivoli Storage Manager
5
Table 3. Tivoli Storage Manager Product Model Overview Topics
Overview topic
Description
“Data Management”
This section compares the Tivoli Storage Manager
progressive backup methodology with other common
approaches. Tivoli Storage Manager data
management policy objects are also described.
“Storage Device and Media
Management” on page 10
This section describes Tivoli Storage Manager storage
policy objects. Tivoli Storage Manager tape rotation,
storage hierarchy, and data migration are also
described. The storage pool, a fundamental Tivoli
Storage Manager management object, is described in
some detail.
Data Management
The main difference between the data management approach of Tivoli Storage
Manager and other commonly used systems is that Tivoli Storage Manager
catalogs and controls data objects instead of simply relying on an operator to
manage storage media. Data objects can include:
v Sub-file components, files, directories, or raw logical volumes that are backed up
from client systems
v Blocks of client data that need to be archived for a fixed amount of time
v Tables or records from database applications
The way these data objects are handled is defined using data management policies.
The use of policy to control data allows Tivoli Storage Manager to implement its
unique backup methodology.
Common Backup Methodologies
Most backup products offer some variation of the three backup methodologies
described in Table 4.
Table 4. Common Backup Methodologies
Common Backup
Methodology
How it Works
Drawbacks
Full backup
v Every file on a given
computer or file system is
copied whether or not it
has changed since the last
backup
v Large amounts of data are
regularly moved.
Generally not feasible in a
networked environment
Full + incremental backup
v Full backups are done on a v Less data is regularly
moved than in a Full
regular basis, for example,
backup. Only the latest
weekly
incremental copy is
v In between Full backups,
restored.
regular Incremental
backups copy only files
that have changed since
the last backup
6
IBM Tivoli Storage Manager for Linux: Quick Start
Table 4. Common Backup Methodologies (continued)
Common Backup
Methodology
How it Works
Drawbacks
Full + differential backup
v Full backups are done on a v Better restore performance
than in a Full +
regular basis, for example,
Incremental backup.A
weekly
differential will back up
v In between Full backups,
more data because it
Differential backups copy
ignores differentials that
only files that have
were taken between the
changed since last Full
previous full and the
backup
current differential.
You are probably familiar with one or more of these approaches. Before Tivoli
Storage Manager, managing data required striking a balance between these
approaches to achieve the desired level of recoverability and cost efficiency.
A major drawback of these common backup methodologies is that all data is
moved on a regular basis, whether it has changed or not. If full backups are
performed weekly, every byte of data is moved weekly. In contrast, IBM Tivoli
Storage Manager’s approach, called Progressive Backup, starts with a full backup,
but then moves only changed data from that point on. Another full backup may
never be required.
Progressive Backup Methodology
Progressive Backup can be thought of as combining the backup benefits of the
incremental approach with the restore benefits of the differential approach. Files
are backed up incrementally to reduce network traffic, while recovery media is
consolidated to provide better restore performance. Together with the data
management features provided by the Tivoli Storage Manager database, the
progressive backup methodology reduces the potential for human error and helps
enforce your storage management procedures. Table 5 describes the progressive
backup methodology.
Table 5. Tivoli Storage Manager Progressive Backup Methodology
Tivoli Storage
Manager Backup
Methodology
How it Works
Benefits
Progressive backup
v A full backup is done only
once
v Entirely eliminates redundant
data backups
v Tivoli Storage Manager
automatically releases expired
file space to be overwritten;
this reduces operator
intervention and the chance of
v Metadata associated with
accidental overwrites of
backup copies is inventoried
current data
in the Tivoli Storage Manager
v Over time, less data is moved
database. The number of
than in Full + Incremental or
backup copies stored and the
Full + Differential backups,
length of time they are
and data restoration is
retained is specified by the
mediated by the database
storage administrator
v After the full backup,
Incremental backups copy
only files that have changed
since the last backup
Tivoli Storage Manager allows for a great deal of flexibility in the implementation
of a backup and restore strategy. This allows you to choose a practical
Chapter 1. Introducing IBM Tivoli Storage Manager
7
configuration that best supports the kinds of recovery scenarios you expect to
encounter. Some possible implementations include the following:
v Progressive backups can be combined with periodic full backups.
v Selective backups can be performed on-demand by users.
v Client or hardware data compression can be used.
v Client data can be collocated to minimize the number of media mounts required
for recovery.
v File system or raw volume images can be backed up from NAS file servers, and
client nodes.
v You can create a portable backup set from Tivoli Storage Manager server storage,
which can be copied to media and used to perform a LAN-free restore of a
client system.
In any implementation, the Tivoli Storage Manager server always knows the
location of the most current version of a given file, which reduces search times and
improves the recovery process. Refer to the Administrator’s Guide for more
information.
Data Management Policy
A Tivoli Storage Manager environment consists of three basic types of resources:
client systems, data, and rules. The client systems generate the data, and the rules
specify how that data will be managed. For example, in the case of Tivoli Storage
Manager backup, rules define how many versions of a file should be kept and
where they should be stored.
Tivoli Storage Manager uses policy to define the relationships between these three
resource categories. Depending on your needs, Tivoli Storage Manager policy can
be fairly simple or more complex.
Tivoli Storage Manager policy objects can be divided into two interrelated groups:
v The policy objects that map to your business environment and data management
goals
v The policy objects that map to your storage media and devices
One way to begin thinking about Tivoli Storage Manager data management policy
objects is to look at how they can reflect the organizational structure of your
business environment. Table 6 introduces the Tivoli Storage Manager data
management policy hierarchy, and provides examples of how you can use these
policy objects to achieve your administrative goals:
Table 6. Tivoli Storage Manager Data Management Policy
Tivoli Storage
Manager Policy
Object
Organizational Unit
Policy Domain
You could map to different categories of Tivoli Storage Manager
client nodes within your organization.
For example, you might set up different policy domains for
UNIX-based file server machines and Windows®-based
workstations. These domains could be used to provide customized
storage management and separate administrative control for each
logical group.
8
IBM Tivoli Storage Manager for Linux: Quick Start
Table 6. Tivoli Storage Manager Data Management Policy (continued)
Tivoli Storage
Manager Policy
Object
Organizational Unit
Policy Set
You could use policy sets to create subsets of Tivoli Storage
Manager client nodes within a domain. However, only one policy
set can be active within a given policy domain at any time. Because
of this restriction, many administrators implement just one policy
set and focus their management effort on policy domains,
management classes, and copy groups.
Management Class
You could map to different categories of data generated by your
Tivoli Storage Manager client nodes. A management class contains
one backup copy group, one archive copy group, or one of each.
One management class in a policy set must be designated as the
default. Additional management classes can be created and
specified for use by individual Tivoli Storage Manager clients.
For example, within the active policy set for the domain created for
UNIX® server machines, you might set up one management class
for general data (default) and one for directory structure
information.
Copy Group
The working elements of Tivoli Storage Manager policy are defined
in copy groups. These elements include the number of versions of
Tivoli Storage Manager client files to be maintained and the amount
of time those files will be stored. The other Tivoli Storage Manager
data management policy objects are primarily used to provide
implementation flexibility. There are two kinds of copy groups:
backup and archive.
For example, within the default management class created to handle
general data for the UNIX server policy domain, you might set up a
backup copy group that maintains three copies of existing data and
stores those copies for 100 days. By default, backup data for any
Tivoli Storage Manager client nodes associated with this domain
will be managed according to these specifications.
Figure 1 on page 10 shows how Tivoli Storage Manager uses these policy objects to
manage client data.
Chapter 1. Introducing IBM Tivoli Storage Manager
9
Figure 1. How Tivoli Storage Manager Controls Backup, Archive, and Space Management
1 A client backs up, archives, or migrates a file. The file is bound to either the
default management class or a management class specified in the client’s
include-exclude list.
2 If, according to the management class, the file is eligible for backup,
archive, or space management, the client sends the file and file information to
the server.
3 The server checks the management class or copy group to determine where
in server storage to store the file initially.
If enough space is not available in the initial storage pool, the server examines
the next pool in the hierarchy and places the file there if space is available.
4 The server stores the file in the appropriate storage pool and stores
information about the file in the database.
When files in server storage are migrated from one pool to another, the server
updates the associated metadata in the database.
Storage Device and Media Management
To store and manage data objects on various kinds of storage media and devices,
Tivoli Storage Manager implements several logical entities to classify the available
storage resources. Table 7 on page 11 describes the Tivoli Storage Manager media
and device policy set.
10
IBM Tivoli Storage Manager for Linux: Quick Start
Table 7. Tivoli Storage Manager Storage Device and Media Policy
Tivoli Storage
Manager Policy
Object
What it Represents
Volume
Represents one physical or logical unit of storage media.
For example, a volume can represent a tape or a disk partition.
Each volume is associated with a single storage pool.
Storage Pool
Represents a collection of available storage volumes of the same
media type. Tivoli Storage Manager stores all managed data objects
in storage pools. Storage pools are typically arranged in a hierarchy,
with data migrating from one type of storage to another.
For example, a storage pool with an LTO tape device class consists
of a number of LTO tape volumes. Clients that need to back up data
directly to LTO tape are associated with this storage pool. Other
client data might go first to a DISK storage pool, and then migrate to
the LTO storage pool.
Each storage pool is associated with a single device class.
Device Class
Represents the type of storage device that can use the volumes
defined to a given storage pool.
For example, an LTO tape device class can be used to associate a
storage pool with any library device that handles LTO tape.
Each removable media-type device class is associated with a single
library.
Library
Represents a specific storage device.
For example, a library can represent a standalone drive, a set of
standalone drives, a multiple-drive automated device, or a set of
drives controlled by an external media manager.
Drive
Represents a specific physical drive within a storage device. Each
drive is associated with a single library.
Path
Represents a data and control path from a source to a destination.
To use a library or drive with Tivoli Storage Manager, a path must
be defined between the device and either the Tivoli Storage Manager
server or another designated data mover.
Data Mover
Represents a SAN-attached device used to transfer Tivoli Storage
Manager client data.
For example, a NAS file server with attached storage must be
defined as a data mover, so it can transfer client data to and from
the storage device as required by the Tivoli Storage Manager server.
Storage Hierarchy and Data Migration
The storage pool is the central element of the Tivoli Storage Manager storage
management environment because it provides the link between Tivoli Storage
Manager data and storage objects. Tivoli Storage Manager allows you to organize
storage pools into one or more hierarchical structures. Each storage hierarchy can
span multiple Tivoli Storage Manager server instances. Storage policy is used to
migrate data objects automatically from one storage pool to another. This allows
you to initially back up data to fast storage media like disk, and then migrate the
Chapter 1. Introducing IBM Tivoli Storage Manager
11
data to slower, less expensive media like tape during off-peak hours. Refer to the
Administrator’s Guide for more information.
Tape Rotation
By providing policy objects that focus your management effort on data instead of
media, Tivoli Storage Manager can help you fill in the gaps inherent in any tape
rotation scheme. Instead of setting up a traditional tape rotation, you set up policy.
Tape rotation, as it applies to Tivoli Storage Manager, can be thought of as the
ongoing automated circulation of media through the storage management process.
Once Tivoli Storage Manager selects an available tape, the tape is used and
eventually reclaimed according to its associated policy.
Policy-based storage management takes a little time to understand and implement,
but it allows for a great deal of automation and flexibility. Automating backup and
recovery functions reduces the likelihood of human error, and also helps enforce
data management goals. Refer to the chapter on managing media in the
Administrator’s Guide for more information.
12
IBM Tivoli Storage Manager for Linux: Quick Start
Putting it All Together
Figure 2 summarizes the relationships between the physical device environment,
Tivoli Storage Manager storage management objects, and Tivoli Storage Manager
data management objects.
Figure 2. Putting it All Together
1
When a Tivoli Storage Manager client is registered, it is associated with a
policy domain. The other Tivoli Storage Manager policy objects are defined
within the policy domain.
2, 3
When the Tivoli Storage Manager client backs up or archives files, the data
Chapter 1. Introducing IBM Tivoli Storage Manager
13
is bound to one or more management classes in the domain’s active policy
set. Backup and archive copy groups within the management class route
the data to an appropriate storage pool.
4, 5
The storage pool specifies where and how the client data will be stored.
Storage pools are mapped to device classes, which represent devices. The
storage pool contains volumes as indicated in the device type associated
with the device class. For example, a storage pool that is mapped to a
device class with a device type of 8MM contains only 8MM tapes.
All devices require a device class that specifies a device type. Removable
media devices also require library and drive definitions, which enable
Tivoli Storage Manager to mount and manage media.
6
Files that are initially stored in disk storage pools can migrate to tape
storage pools if the pools are set up in a storage hierarchy.
Automating Tivoli Storage Manager Operations
You can define schedules to automate Tivoli Storage Manager server and client
operations. A comprehensive and integrated set of schedules can provide the basis
for efficient data management with little need for intervention during normal
operations.
To schedule Tivoli Storage Manager server operations, you only need to create a
schedule or set of schedules on the Tivoli Storage Manager server.
To schedule Tivoli Storage Manager client operations, you need to do two things:
v Create a schedule or set of schedules on the Tivoli Storage Manager server
v Install and start a scheduler component on the Tivoli Storage Manager client
machine
Any of the following storage management tasks can be automated:
v Backup and restore
v Archive and retrieve
v Tivoli Storage Manager server administrative commands
v Running administrative scripts and macros
After defining a schedule for a client task, you must specify which clients can use
the schedule. This task is called associating clients with schedules. You can
associate all the nodes in a given policy domain, or just a subset. Schedule
associations can be modified at any time.
To automate client operations, the scheduler component must be installed and
configured on each Tivoli Storage Manager client machine. This is done with a
wizard accessed from the backup-archive client graphical interface. Refer to
Backup-Archive Clients Installation and User’s Guide for more information.
14
IBM Tivoli Storage Manager for Linux: Quick Start
Where to Go From Here
Basic Storage Management Tasks
This publication is primarily intended to help you do the following:
1. Install and configure Tivoli Storage Manager.
2. Set up client/server communications.
3. Customize your Tivoli Storage Manager installation.
Additional information and instructions are also provided, including the following:
v Using administrative interfaces
v Setting up the Secure Web Administrator Proxy
v National language support
v Applying maintenance updates
v Removing Tivoli Storage Manager
Advanced Storage Management Tasks
The Administrator’s Guide is intended to help you perform a wide range of
customization and ongoing management tasks, including the following:
Storage area network implementation
You can configure Tivoli Storage Manager to allow multiple servers to
share storage devices over a SAN. You can also configure Tivoli Storage
Manager clients to use a SAN to directly access storage devices.
Server and storage pool protection
You can:
v Mirror your database and recovery log
v Back up your database and storage pools
v Recover lost or damaged database and storage pool data
v Move files from one storage pool volume to another
Data management policy
You can provide clients on some platforms with hierarchical space
management services (HSM). You can also extensively customize backup
and archive functions.
Security
You can modify the password access requirements for Tivoli Storage
Manager clients, as well as other password parameters. You can also assign
different levels of administrator authority.
Server operations
You can monitor and control:
v Server processes
v Client sessions
v Activity log
v Accounting records
v Logging facilities used to monitor server activity
Network of servers
You can create a network of IBM Tivoli Storage Manager servers that can:
v Share object definitions such as storage policies, administrators, and
command scripts
v Store information in each other’s storage pools
v Route commands to one or more servers
Chapter 1. Introducing IBM Tivoli Storage Manager
15
To store data from clients more efficiently, you may find that having IBM
Tivoli Storage Manager servers located close to your clients is the best way
to manage network bandwidth limitations. As a result, you may have
servers at many locations. Tivoli Storage Manager provides functions to
help you configure, manage, and monitor the servers connected to a
network consistently and efficiently.
Tivoli Storage Manager provides a number of functions to help you
manage a network of servers. You can:
v Maintain and distribute server configuration information such as policy
from a single configuration manager to many managed servers
v Monitor many servers and clients from a single server
v Issue commands on one server to other servers and groups of servers
v Use the storage on one server for data from another server
|
Use of these functions requires licensing. See “Registering Licenses” on
page 27.
16
IBM Tivoli Storage Manager for Linux: Quick Start
Chapter 2. Installing IBM Tivoli Storage Manager
Installing IBM Tivoli Storage Manager consists of the following:
1. Installing the Tivoli Storage Manager server and related components on the
server machine.
2. Installing Tivoli Storage Manager client code on every machine that will
transfer data to Tivoli Storage Manager server-managed storage.
|
|
|
|
|
|
IBM Tivoli Storage Manager client install packages for Linux and desktop clients
are available on separate CDs included in the product package. The client code can
also be installed from the internet. For detailed Tivoli Storage Manager client
installation and configuration instructions, see Backup-Archive Clients Installation and
User’s Guide. To view Tivoli Storage Manager publications before installation, see
“Using Softcopy Documentation” on page 18.
This chapter provides instructions for installing the IBM Tivoli Storage Manager
server and related components, including the following tasks:
v “Using Softcopy Documentation” on page 18
v “Installation and Configuration” on page 20
v “Verifying Your Installation” on page 23
v “Getting Started” on page 25
To remove the Version 5.1 server, see Appendix D, “Removing the IBM Tivoli
Storage Manager Server”, on page 67.
Evaluation (Try and Buy) Product
A 60-day evaluation (try and buy) of IBM Tivoli Storage Manager is available on
CD. The CD try and buy version provides the same functions as the standard
licensed product. However, the licensing package is not available with the try and
buy product, and you are limited to 50 clients.
The installation instructions in this chapter (“Installation and Configuration” on
page 20) apply to both the standard licensed product and the CD try and buy
product.
Note: You can apply maintenance to a try and buy version of IBM Tivoli Storage
Manager.
To upgrade to the licensed product, do the following:
1. Mount the IBM Tivoli Storage Manager server licensed product CD in your CD
drive.
|
2. Install the license packages (TIVsm-license_keys-5.2.0-0 and TIVsm-license-5.2.0-0)
Only the license file is installed, and no server or user data is lost. After installing
the license package, register any licensed features that you purchased.
© Copyright IBM Corp. 2002, 2003
17
Using Softcopy Documentation
This book is shipped as a hardcopy with the product. Server and client books in
PDF and HTML formats are available on the publications CD. Client
platform-specific books in PDF and HTML formats are available on the installation
CD shipped with the product.
|
|
|
|
You can download the Adobe Acrobat Reader from the Adobe Web site at
http://www.adobe.com/.
To view the books in HTML format, you can use any browser that supports the
HTML 2.0 specification or later. For example, you can download the Netscape
Communicator browser from the Web site at http://www.netscape.com/.
System Requirements
Before you install IBM Tivoli Storage Manager, ensure that you have the
following:
v For IBM xSeries™ servers, Version 2.2.4 or higher of the GNU libc libraries
installed on the Tivoli Storage Manager machine.
v For IBM zSeries™ servers, Version 2.2.5-81 or higher of the GNU libc libraries
installed on the Tivoli Storage Manager machine.
v For IBM pSeries™ servers, Version 2.2.5-108 or higher of the GNU libc libraries
installed on the Tivoli Storage Manager machine.
|
|
|
|
|
|
|
|
|
|
|
v The correct kernel levels. See Table 8 on page 19 for kernel levels and basic
install packages.
v An IA32 Intel processor on an xSeries server, an s390/s390x processor on a
zSeries 900 or 800 server with either native LPARs or VM guests, or a 64-bit
PowerPC® processor on a pSeries server.
v A minimum of 68MB hard disk space (includes full install, 9MB recorvery log,
17MB database). Add 6MB for each additional language support package.
v A minimum 128MB of RAM.
v A TCP/IP communication protocol.
|
|
v A CD device available for installation or an Interenet connection to obtain the
Linux installation packages.
The IBM Tivoli Storage Manager Administrative Web Interface and Web Client
Interface require a Java Swing-capable Web browser with Java Runtime
Environment (JRE) 1.3.1 installed. Web browsers that meet these requirements
include:
v Netscape Navigator 6.0 (which provides Java Swing support) or later.
v Netscape Navigator 4.7 or later with the Java Plug-In (JRE 1.3.1).
v Microsoft Internet Explorer 5.0 or later with the Java Plug-In (JRE 1.3.1 for
Windows users).
If your browser meets these requirements but does not correctly display a Tivoli
Storage Manager Web-based interface, consider trying a different browser.
The table below shows Tivoli Storage Manager for Linux OS support. Use it as a
reference when determining the correct kernel level.
Tivoli Storage Manager supports release 243 of the 2.4.18 UP kernel on
SuSE Linux Enterprise Server 7, and release 224 of the SMP kernel.
18
IBM Tivoli Storage Manager for Linux: Quick Start
|
Table 8. Tivoli Storage Manager for Linux OS Support
|
Machine
Linux OS
|
|
|
IBM pSeries
SuSE Enterprise 8/United Linux
Server 8/United 1.0
Linux 1.0
2.4.19-ul1-ppc64- ppc64
SMP
|
|
|
|
IBM xSeries
Red Hat AS
2.1
2.4.9–e.10 for
UP 2.4.9–e.10
enterprise for
SMP
IA32
|
|
|
IBM xSeries
SuSE Linux
Enterprise
Server 7
7
2.4.18
IA32
|
|
|
|
IBM xSeries
|
|
|
|
|
IBM zSeries servers, SuSE Enterprise 8/United Linux
800 or 900 models, Server 8/United 1.0
Linux 1.0
with S/390 and
S/390x architecture
OS Level
Kernel Level
Architecture
SMP,UP
SuSE Enterprise 8/United Linux
Server 8/United 1.0
Linux 1.0
2.4.19-4GB(for
UP),
2.4.19-64GBSMP
IA32
2.4.19suse
31-bit (S/390)
and 64-bit
(S/390x)
SMP
Note: The vendor kernel configurations supported by IBM Tivoli Storage Manager
are:
|
|
|
|
v 2.4.9-e.10
v 2.4.9-e.10enterprise
v 2.4.18-4GB
v
v
v
v
2.4.18-64GB-SMP
2.4.19-4GB
2.4.19-64GB-SMP
2.4.19-ul1-ppc64-SMP
For requirements, supported devices, client install packages, and fixes, go
to the IBM Tivoli Storage Manager Web site at
www.ibm.com/software/sysmgmt/products/
support/IBMTivoliStorageManager.html
After you have installed IBM Tivoli Storage Manager and before you
customize it for your use, go to the IBM Tivoli Storage Manager Web site.
Download and apply any applicable fixes.
Here is an overview of the installation directories:
v Default Server Directory (/opt/tivoli/tsm/server/bin), which contains:
– Storage pool volumes (backup.dsm, archive.dsm, spcmgmt.dsm)
– Database volume (db.dsm)
– Recovery log volume (log.dsm)
– Server and licensing
v Related Server Directories:
– The message repository, online help, and supported languages
(/opt/tivoli/tsm/server/bin/en_US).
Chapter 2. Installing IBM Tivoli Storage Manager
19
– Device support (/opt/tivoli/tsm/devices/bin).
– Tivoli inventory (/opt/tivoli/tsm/tivinv)
Installation and Configuration
Use the following procedure to install the server and device support.
1. Log in as the root user.
2. Insert the Tivoli Storage Manager CD into a CD drive. The following discussion
assumes that the CD is mounted on directory /mnt/cdrom.
3. See the README file on the CD for changes to the installation procedure.
4. Use the rpm command to install the Tivoli Storage Manager packages. For
example:
|
|
rpm -ivh <packagename>
|
|
|
|
|
|
Where packagename is one or more package name (separted by spaces) listed in
Tables 8, 9, 10, and 11. Tables 8, 9, and 10 list the minimum required install
packages.
|
|
|
|
Notes:
a. The Tivoli Storage Manager server will install by default in the path
/opt/tivoli/tsm/server/bin. You have the option of installing under a different
file system. For example:
rpm -ivh --prefix /usr TIVsm-server-5.1.5-0.i386.rpm
|
|
|
This will install the server under /usr/tivoli/tsm/server/bin.
b. The Web administrator, license and Web help packages need to be installed
under the same file system as the Tivoli Storage Manager server.
|
|
|
|
Table 9. Minimum Required Install Packages for IA32
|
Package
Components
|
TIVsm–server–5.2.0-0.i386.rpm
Server package for IA32
|
TIVsm–license–5.2.0-0.i386.rpm
License enabler for IA32
|
|
TIVsm–license_keys-5.2.0-0.i386.rpm
License keys for various Tivoli Storage
Manager licensed features.
|
|
TIVsm–tsmscsi–5.2.0-0-i386.rpm
Tivoli Storage Manager SCSI device drivers
and utilities
|
|
|
TIVsm–webadmin-5.2.0-0.noarch.rpm
Files needed by the Web-based
administrative interface
|
Table 10. Minimum Required Install Packages for ppc64 pSeries
|
Package
Components
|
TIVsm–server–5.2.0-0.ppc64.rpm
Server package for ppc64
|
TIVsm–license–5.2.0-0.ppc64.rpm
License enabler for ppc64
|
|
TIVsm–license_keys-5.2.0-0.ppc64.rpm
License keys for various Tivoli Storage
Manager licensed features.
|
|
TIVsm–tsmscsi–5.2.0-0-ppc64.rpm
Tivoli Storage Manager SCSI device drivers
and utilities
20
IBM Tivoli Storage Manager for Linux: Quick Start
|
Table 10. Minimum Required Install Packages for ppc64 pSeries (continued)
|
|
|
TIVsm–webadmin-5.2.0-0.noarch.rpm
|
Table 11. Minimum Required Install Packages for 31-bit zSeries
|
TIVsm-server.5.2.0-0.s390.rpm
Server package for S/390
|
TIVsm-licence.5.2.0-0.s390.rpm
License enabler for S/390
|
|
TIVsm-licence_keys.5.2.0-0.s390.rpm
License keys for various Tivoli Storage
Manager licensed features
|
|
TIVsm-tsmscsi.5.2.0-0.s390.rpm
Tivoli Storage Manager SCSI device drivers
and utilities
|
|
|
TIVsm-webadmin.5.2.0-0.noarch.rpm
Files needed by the Web-based
administrative interface
|
Table 12. Minimum Required Install Packages for 64-bit zSeries
|
TIVsm-server.5.2.0-0.s390x.rpm
Server package for S/390x
|
TIVsm-licence.5.2.0-0.s390x.rpm
License enabler for S/390x
|
|
TIVsm-licence_keys.5.2.0-0.s390x.rpm
License keys for various Tivoli Storage
Manager licensed features
|
|
TIVsm-tsmscsi.5.2.0-0.s390x.rpm
Tivoli Storage Manager SCSI device drivers
and utilities
|
|
TIVsm-webadmin.5.2.0-0.noarch.rpm
Files needed by the Web-based
administrative interface
Files needed by the Web-based
administrative interface
5. When the installation is finished, remove the CD from the drive.
Notes:
1. Messages and help will install to /opt/tivoli/tsm/server/bin/<locale>, where
<locale> is one of the locales specified in Appendix B, “National Language
Support”, on page 63. The message catalogs will always be called dsmserv.cat,
while the help files will be called dsm<locale>.hlp.
2. Help for the Web-based administrator will be installed in
/opt/tivoli/tsm/server/bin/<locale>/webhelp.
3. GIF images for the Web-based administrator will be installed in
/opt/tivoli/tsm/server/bin/webimages. The Web-based administrator is optional and
only needed if the Web-based administrative interface will be used.
|
|
|
|
Following is a list of Tivoli Storage Manager Messages, Help and Web-based
Administrator packages including their components. Use these packages to
customize your installation after the basic installation is complete. These packages
are architecture-independent. They can be installed on pSeries, xSeries, and zSeries.
|
Table 13. Tivoli Storage Manager Messages, Command Line Help and HTML help
|
Package
Components
|
|
TIVsm-cmdlinehelp.de_DE5.2.0.0.noarch.rpm
German messages and command line help.
|
|
TIVsm-cmdlinehelp.es_ES5.2.0.0.noarch.rpm
Spanish messages and command line help.
|
|
TIVsm-cmdlinehelp.fr_FR5.2.0.0.noarch.rpm
French messages and command line help.
Chapter 2. Installing IBM Tivoli Storage Manager
21
|
|
Table 13. Tivoli Storage Manager Messages, Command Line Help and HTML
help (continued)
|
Package
Components
|
|
TIVsm-cmdlinehelp.it_IT5.2.0.0.noarch.rpm
Italian messages and command line help.
|
|
TIVsm-cmdlinehelp.ja_JP5.2.0.0.noarch.rpm
Japanese messages and command line help.
|
|
TIVsm-cmdlinehelp.ko_KR5.2.0.0.noarch.rpm
Korean messages and command line help.
|
|
TIVsm-cmdlinehelp.pt_BR5.2.0.0.noarch.rpm
Brazilian Portuguese messages and command line
help.
|
|
TIVsm-cmdlinehelp.zh_TW5.2.0.0.noarch.rpm
Traditional Chinese messages and help (big5
codepage)
|
|
TIVsm-cmdlinehelp.zh_TW.euctw5.2.0.0.noarch.rpm
Traditional Chinese messages and help (euctw
codepage)
|
|
TIVsm-cmdlinehelp.zh_CN5.2.0.0.noarch.rpm
Simplified Chinese messages and help (eucCN
codepage)
|
|
TIVsm-cmdlinehelp.zh_CN.gb180305.2.0.0.noarch.rpm
Simplified Chinese messages and help (gb18030
codepage)
|
Webhelp Packages
HTML Help for Web Administrative Interface
|
|
TIVsm-webhelp.en_US-5.1.50.noarch.rpm
U.S. English HTML help panels
|
|
TIVsm.webhelp-de_DE5.2.0.0.noarch.rpm
German HTML help files
|
|
TIVsm.webhelp-es_ES5.2.0.0.noarch.rpm
Spanish HTML help files
|
|
TIVsm.webhelp-fr_FR5.2.0.0.noarch.rpm
French HTML help files
|
TIVsm.webhelp-it_IT-5.2.0.0.noarch.rpm Italian HTML help files
|
|
TIVsm.webhelp-ja_JP5.2.0.0.noarch.rpm
Japanese HTML help files
|
|
TIVsm.webhelp-ko_KR5.2.0.0.noarch.rpm
Korean HTML help files
|
|
TIVsm.webhelp-pt_BR5.2.0.0.noarch.rpm
Brazilian PortugueseHTML help files
|
|
TIVsm.webhelp-zh_CN5.2.0.0.noarch.rpm
Simplified Chinese HTML help files
|
|
TIVsm.webhelp-zh_CN.gb180305.2.0.0.noarch.rpm
Simplified Chinese HTML help files
|
|
TIVsm.webhelp-zh_TW5.2.0.0.noarch.rpm
Traditional Chinese HTML help files
|
|
|
TIVsm.webhelp-zh_TW.euctw.V.R.MP.noarch.rpm
Traditional Chinese HTML help files
22
IBM Tivoli Storage Manager for Linux: Quick Start
Verifying Your Installation
You can verify the installation by backing up client data from a backup-archive
client. The client must have been installed from the UNIX client CD. If the
backup-archive client is not installed, see Backup-Archive Clients Installation and
User’s Guide for instructions.
||
|
|
|
Do not select files to back up that exceed your storage pool capacity. A
10MB backup storage pool, a 5MB archive storage pool, and an 8MB space
management pool were allocated at installation.
1. The server must be running before you can use the administrative and
backup-archive clients. See “Starting and Stopping the Server” on page 25 for
the procedure for starting the server.
2. Configure the backup-archive client by doing the following:
a. Copy the sample client system options file (dsm.sys.smp) to dsm.sys, and the
sample client user options file (dsm.opt.smp) to dsm.opt. The sample files are
in /opt/tivoli/tsm/client/ba/bin/.
b. Edit the options files to include the options listed below:
In dsm.opt:
servername server_name
where server_name is the name of your server. The default server is
SERVER1.
In dsm.sys:
servername server_name
commmethod tcpip
tcpport port_address
tcpserveraddress server_address
nodename client
Note: The server names specified in dsm.opt and dsm.sys must match. See
Backup-Archive Clients Installation and User’s Guide for more
information.
3. Start the backup-archive client graphical user interface by entering the
following command:
dsm
The default ID and password for the backup-archive client are:
v ID Name: client
v Password: client
4. To back up several files, perform the steps listed below. For more detailed
information and other backup procedures, see the appropriate IBM Tivoli
Storage Manager client manual.
a. Click on Backup. The Backup window displays.
b. You can select files from a directory tree, or you search a drive or directory
to select files:
Chapter 2. Installing IBM Tivoli Storage Manager
23
v To select files from a directory tree, expand the tree and click on the files
you want to back up.
v To search for files, do the following:
1) Click on the Find icon on the tool bar. The Find Files (Backup)
window displays
2) Enter your search criteria in the Find Files (Backup) window.
3) Click on Search. The Matching Files (Backup) window displays.
4) Click on the selection boxes next to the files you want to back up.
5) Close the Matching Files (Backup) window by Clicking on the
backup-archive icon on the menu bar and selecting Close.
c. Click on Always Backup from the Type of Backup list.
d. Click on Backup. The Backup Status window displays the backup
processing status. You will receive a message when the backup has
completed successfully.
Defining Environment Variables
An environment variable describes the operating environment of a process, such as
the home directory or terminal in use. To run the server from a directory other
than the default directory (/opt/tivoli/tsm/server/bin), you have to define environment
variables for Tivoli Storage Manager. To locate where the server is installed, Tivoli
Storage Manager uses the DSMSERV_DIR variable. To define this variable, enter:
export DSMSERV_DIR=/opt/tivoli/tsm/server/bin
Note: The above example assumes the server is installed under /opt
You can define an environment variable to point to the server options file
(dsmserv.opt). This allows two Tivoli Storage Manager servers running on the same
machine to share the same options file or to use different options files. For
example, to define the DSMSERV_CONFIG environment variable to point to
dsmserv.opt, enter:
export DSMSERV_CONFIG=/opt/tivoli/tsm/server/bin/dsmserv.opt
You can define an environment variable to point to the accounting log file.
Accounting records are stored in the dsmaccnt.log file. The
DSMSERV_ACCOUNTING_DIR environment variable specifies the directory
where the accounting file is opened. If this variable is not set when the server is
started, the dsmaccnt.log file is placed in the current directory when the server
starts.
For example, to set the environment variable to place the accounting records in the
/home/engineering directory, enter this command:
export DSMSERV_ACCOUNTING_DIR=/home/engineering
Notes:
1. You can also use the -o parameter of the DSMSERV command to specify an
options file name.
2. Use the following command if your shell is in the csh family:
24
IBM Tivoli Storage Manager for Linux: Quick Start
setenv DSMSERV_DIR /opt/tivoli/tsm/server/bin
3. Use the following command if your shell is in the ksh or bash family:
export DSMSERV_DIR=/opt/tivoli/tsm/server/bin
4. To save this environment, save these entries in the .bash_profile file of your
$HOME directory.
Getting Started
This section describes the following tasks:
v “Starting and Stopping the Server”
v “Starting and Stopping an Administrative Client or the Web Interface” on
page 26
v “Running Multiple Servers on a Single Machine”
v “Changing the Administrative Client Password” on page 27
v “Registering Licenses” on page 27
Examples of Tivoli Storage Manager administrative tasks are shown for
both the command line and the Web interface. All Web examples are begun
from the Object view.
Starting and Stopping the Server
To start the server from the /opt/tivoli/tsm/server/bin directory, enter:
./dsmserv
You can stop the server without warning if an unexpected problem requires you to
return control to the operating system. To avoid losing administrative and client
node connections, stop the server only after current sessions have completed or
been canceled.
To stop the server, do one of the following:
halt
OR
1. Select Server.
2. Select Server Status.
3. From Operations, select Halt Server and then Finish.
This shuts down the server immediately and cancels all client sessions, even if
activity has not completed.
Running Multiple Servers on a Single Machine
To run multiple IBM Tivoli Storage Manager servers on the same machine, you
must create multiple pairs of database and recovery log files. If the DSMSERV_DIR
Chapter 2. Installing IBM Tivoli Storage Manager
25
environment variable points to the server executable directory, you do not have to
copy the server executable files in more than one directory.
Note: You need licenses for each server distributed on a particular system. To
avoid having multiple copies of the server on the same system, you can
have multiple users running the same server, and each user can use a
different database, recovery log, and options file.
Use the following procedure to set up an additional server:
1. Make the directory where you want the files created (for example
/usr/local/newserv) and copy the server options file into that directory:
mkdir /usr/local/newserv
cp /opt/tivoli/tsm/server/bin/dsmserv.opt /usr/local/newserv/dsmserv.opt
If necessary, you can use a different options file for each server. Or, if the
DSMSERV_CONFIG environment variable points to a server options file, that
file can be used by both servers.
Note: If you are using two different options files, ensure that the
communication method parameters are unique. For example, the servers
cannot use the same TCPPORT or HTTPPORT.
2. During installation, set your path on the server console or from a Linux
terminal session by defining the environment variables (see “Defining
Environment Variables” on page 24). Ensure that you are in the new directory
before continuing.
3. Format the database and recovery log files. For example, to format two 300MB
database volumes and a 30MB recovery log volume, enter:
dsmfmt -db dbvol2 300 dbvol3 300
dsmfmt -log logvol2 30
4. Initialize the database and recovery log in the new server directory:
dsmserv format 1 logvol2 2 dbvol2 dbvol3
5. Set up the server for the administrative Web interface:
dsmserv runfile /opt/tivoli/tsm/server/bin/dsmserv.idl
Starting and Stopping an Administrative Client or the Web
Interface
When you start an administrative client or the web interface, you must enter an
administrator name and password. The installation defaults are:
v ID Name: admin
v Password: admin
To change the password, see “Changing the Administrative Client Password” on
page 27.
v To start the administrative client command line interface, enter the following
command from the /usr/tivoli/tsm/clien/ba/bin/dsmadmc directory:
dsmadmc
26
IBM Tivoli Storage Manager for Linux: Quick Start
v Before the administrative Web interface can be used, Tivoli Storage Manager
must first be configured. To start the Web interface, enter the URL for your
Tivoli Storage Manager server from the Web browser on your machine. For
example:
http://tsmserv:1580
Where:
tsmserv
Specifies the server address (which can also be a numeric IP address)
1580
Specifies an HTTP port number.
To end an administrative client session do one of the following:
v From an administrative command line:
quit
OR
v From an administrative Web interface:
From Options, select Log Off
Changing the Administrative Client Password
To change the password of the default administrative client from ADMIN to
TUCSON, do the following:
update admin admin tucson
OR
1. Select Administrators.
2. Select the desired administrator name.
3. From Operations, select Update an Administrator.
4. Enter the administrator information and Finish.
Registering Licenses
When you install IBM Tivoli Storage Manager, your system is licensed for the base
support, which includes:
v An unlimited number of administrative clients
v One backup-archive client
v Enterprise Administration functions
v Server-to-server virtual volume support
You should immediately register any Tivoli Storage Manager licensed functions
that you purchase.
Chapter 2. Installing IBM Tivoli Storage Manager
27
Note: If you migrate from ADSM, your existing licenses are no longer valid. You
must update your license information.
You must register a new license if you want to add support for any of the
following features that are not already in your existing license agreement. Tivoli
Storage Manager uses a license file and the REGISTER LICENSE command to
complete this task. Licenses are stored in enrollment certificate files, which contain
licensing information for the server product. The enrollment certificate files are on
the installation CD-ROM. When registered, the licenses are stored in a
NODELOCK file within the current directory.
Table 14. Licensed Features
License File Name
Description
domino.lic
Each managed system that uses IBM Tivoli Storage Manager for
Mail
Also required: Managed System for LAN license if you use a
communication protocol other than shared memory.
drm.lic
IBM Tivoli Storage Manager Extended Edition (disaster recovery
manager includes server-to-server virtual volumes for database and
storage pool backup)
Required on a source server but not on a target server.
Note: The full function of disaster recovery manager is not
supported on IBM Tivoli Storage Manager for Linux.
Server-to-server virtual volumes for database and storage pool
backups are supported if you register the drm.lic. Disaster recovery
plans, automatic expiration of database backups, and off-site media
management are not supported on IBM Tivoli Storage Manager for
Linux.
@
@
@
@
@
@
@
emcsymm.lic
Each managed system that uses IBM Tivoli Storage Manager for
Hardware (EMC Symmetrix)
Also required: Managed System for LAN license if you use a
communication protocol other than shared memory.
emcsymr3.lic
Each managed system that uses IBM Tivoli Storage Manager for
Hardware (EMC Symmetrix R/3)
Also required: Managed System for LAN license if you use a
communication protocol other than shared memory.
ess.lic
Each managed system that uses IBM Tivoli Storage Manager for
Hardware (ESS)
Also required: Managed System for LAN license if you use a
communication protocol other than shared memory.
essr3.lic
Each managed system that uses IBM Tivoli Storage Manager for
Hardware (ESS R/3)
Also required: Managed System for LAN license if you use a
communication protocol other than shared memory.
informix.lic
Each managed system that uses IBM Tivoli Storage Manager for
Databases (Informix)
Also required: Managed System for LAN license if you use a
communication protocol other than shared memory.
28
IBM Tivoli Storage Manager for Linux: Quick Start
Table 14. Licensed Features (continued)
License File Name
Description
library.lic
IBM Tivoli Storage Manager Managed Library
Required for each library in the Extended Device Category that is
managed by a IBM Tivoli Storage Manager server. For current
information on supported devices, visit the IBM Tivoli Storage
Manager page on the World Wide Web at
www.ibm.com/software/sysmgmt/products/
support/IBMTivoliStorageManager.html.
libshare.lic
IBM Tivoli Storage Manager Tape Library Sharing
Required on an IBM Tivoli Storage Manager server that can access a
shared library, including the library manager. The Managed Library
license is required only on the library manager.
lnotes.lic
Each managed system that uses IBM Tivoli Storage Manager for
Lotus® Notes
Also required: Managed System for LAN license if you use a
communication protocol other than shared memory.
msexch.lic
Each managed system that uses IBM Tivoli Storage Manager for
Mail (MS Exchange)
Also required: Managed System for LAN license if you use a
communication protocol other than shared memory.
mgsyslan.lic
IBM Tivoli Storage Manager Managed System for LAN
mgsyssan.lic
IBM Tivoli Storage Manager Managed System for SAN
Required for each storage agent. The Tape Library Sharing feature
is required on the IBM Tivoli Storage Manager server.
IBM Tivoli Storage Manager requires this license for each client
using server-free data movement.
mssql.lic
Each managed system that uses IBM Tivoli Storage Manager for
Databases (MS SQL Server)
Also required: Managed System for LAN license if you use a
communication protocol other than shared memory.
ndmp.lic
IBM Tivoli Storage Manager Extended Edition includes support for
the use of NDMP to back up and recover NAS file servers.
Required on an IBM Tivoli Storage Manager server that performs
backup and restore operations of a NAS file server, using Network
Data Management Protocol.
oracle.lic
Each managed system that uses IBM Tivoli Storage Manager for
Databases (Oracle)
Also required: Managed System for LAN license if you use a
communication protocol other than shared memory.
r3.lic
Each managed system that uses IBM Tivoli Storage Manager for
Enterprise Resource Planning
Also required: Managed System for LAN license if you use a
communication protocol other than shared memory.
Chapter 2. Installing IBM Tivoli Storage Manager
29
Table 14. Licensed Features (continued)
License File Name
Description
spacemgr.lic
Each managed system that uses Tivoli Storage Manager for Space
Management
Also required: Managed System for LAN license if you are using a
communication protocol other than shared memory. Only one
Managed System for LAN license is required if an HSM client and
backup-archive client are on the same system with the same node
ID.
|
|
was.lic
|
|
Each managed system that uses IBM Tivoli Storage Manager for
Application Servers (WebSphere)
Also required: Managed System for LAN license if you use a
communication protocol other than shared memory.
You must register any Tivoli Storage Manager licensed functions that you
purchase.
register license <filename>
where the filename is one of the licensed functions above.
OR
1. Select Server.
2. Select License Information.
3. From Operations, select Register License.
4. Enter the required information and Finish.
Note: The register license command is also used to update the number of licenses.
When using the register license command to update the number of licenses,
the command replaces the number of licenses. The command does not add
to the number of licenses already registered. For instance if you had 10
Tivoli Storage Manager for Space Management licenses registered and need
to register an additional 5 licenses, do the following:
register license file=spacemgr.lic number=15
30
IBM Tivoli Storage Manager for Linux: Quick Start
Chapter 3. Specifying Server and Client Communication
Methods
This chapter describes how to specify communication methods between the IBM
Tivoli Storage Manager server and clients. A sample server options file, called
dsmserv.opt.smp, is created by default by the installation. To set up communications,
you must create a new server options file by copying the sample file. Name the
new file dsmserv.opt and edit the options. Each sample or default entry in the
sample options file is a comment, a line beginning with an asterisk (*). When
editing the options file, follow these guidelines:
v To activate an option, remove the asterisk at the beginning of the line.
v Options can begin in any column.
v Enter only one option per line, and the option must be on only one line.
v Options are not case-sensitive.
v One or more blank spaces are allowed between keywords and values.
If you change the server options file, you must restart the server for the changes to
take effect. See Administrator’s Reference for a description of all server options.
You can specify one or more of the following communication methods:
v TCP/IP
v HTTP (for the administrative client Web interface)
Note: You can also specify that no communication method be used by adding the
following server option to the server options file:
commmethod none
With this option, users cannot connect to the server. It is useful for
experimenting with policy commands.
Setting TCP/IP Options
Here is a sample TCP/IP setting:
commmethod
tcpport
tcpwindowsize
tcpnodelay
tcpip
1500
0
yes
TCPPORT
The server TCP/IP port address. The default value is 1500.
TCPWINDOWSIZE
The size of the TCP/IP buffer used when sending or receiving data. The
window size used in a session is the smaller of the server and client
window sizes. Larger window sizes use additional memory but may
improve performance.
You can specify an integer from 0 to 2048. To use the default window size
for the operating system, specify 0.
© Copyright IBM Corp. 2002, 2003
31
TCPNODELAY
Whether or not the server sends small messages or lets TCP/IP buffer the
messages. Sending small messages may improve throughput but increases
the number of packets sent over the network. Specify YES to send small
messages or NO to let TCP/IP buffer them. The default is YES.
TCPADMINPORT
(Optional) Specifies the port number on which the server TCP/IP
communication driver is to wait for requests other than client sessions. See
the Administrator’s Reference for futher information.
|
|
|
|
Setting HTTP Options
Use the HTTP communication method for the administrative web interface.
TCP/IP must be active for you to use the administrative client Web interface. Here
is a sample HTTP communication setting:
commmethod
httpport
http
1580
HTTPPORT specifies the TCP/IP port address of a server when using HTTP. The
default value is 1580.
Note: If you use the administrative web interface, your browser must have Java™
1.1.6 support. See “System Requirements” on page 18 for a list of supported
browsers.
Connecting with IBM Tivoli Storage Manager across a Firewall
The IBM Tivoli Storage Manager server and clients can work across a firewall, or
the server can securely manage client backup and restore operations and
administrative functions across a firewall. To enable clients to work across a
firewall, configure the firewall to open the ports that the server and clients need.
Ports need to be opened only if functions beyond those of server-prompted
sheduling are required. Server-prompted scheduling can be handled with the
SESSIONINIT=SERVERONLY and HLA and LLA options of the REGISTER NODE
or UPDATE NODE commands. Because firewalls differ in the manner in which
ports open, follow the instructions that accompanied the firewall software or
hardware that you are using. If you need help configuring the firewall, contact the
supplier of your firewall.
The following operations require that you open ports on the firewall:
v To enable clients to communicate with a server across a firewall, open the
TCP/IP port for the server on the TCPPORT option in the dsmserv.opt file. The
default TCP/IP port is 1500. When authentication is turned on, the information
that is sent over the wire is encrypted.
Note: If the TCPADMINPORT option is specified, sessions from clients without
administration authority can be started on the TCPPORT port only.
v To use the administrative Web interface for a server across a firewall, open the
HTTP port for the server on the HTTPPORT option in the dsmserv.opt file. The
default HTTP port is 1580.
The information that is transmitted is not encrypted. To encrypt information
between the server and the web browser, use the Tivoli Storage Manager Secure
Web Administrator Proxy for the Web and administration of the IBM Tivoli
32
IBM Tivoli Storage Manager for Linux: Quick Start
Storage Manager server. Install the proxy on a web server that sits on the
firewall so that the web server can access resources on both sides of the firewall.
After you set up the proxy, use it to administer any Tivoli Storage Manager
server at Version 3.7 or higher. For more information about installing and using
the proxy, see Appendix E, “Setting Up the Secure Web Administrator Proxy”, on
page 69.
v
To use the Web backup-archive client to connect to a client across a firewall, use
the client at Version 4.1.2 or later. Open these ports on the firewall:
– The HTTP port for the client on the HTTPPORT option in the client dsm.opt
file. The default client HTTP port is 1581.
– The two ports that are specified on the WEBPORTS option in the dsm.opt file.
By default, Web ports are assigned randomly which do not work across a
firewall. Specify this option with non-zero values for both ports; then, open
these ports on the firewall. Information is encrypted over the wire when
authentication is turned on.
You can specify a separate port on which the server TCP/IP communication driver
waits for requests for sessions other than client sessions. This includes
administrative sessions, server-to-server sessions, library client sessions, storage
agent sessions, SNMP subagent sessions, managed server sessions, and event
server sessions. Use the TCPADMINPORT option in the dsmserv.opt file to specify
the port number. The default port is 1500. Using different port numbers for the
options TCPPORT and TCPADMINPORT enable you to create one set of firewall
rules for client sessions and another set for the other session types.
If TCPPORT and TCPADMINPORT specify different ports, any client sessions
attempting to use the port that is specified on the TCPADMINPORT option will
end. Administrative sessions are permitted on either port but, by default, will use
the port that is specified on the TCPADMINPORT option.
If you use the SessionInitiation parameter of the REGISTER NODE or UPDATE
NODE commands and no other function is required, you can close the port at the
firewall that is specified on the TCPPORT option and specify nodes whose
scheduled sessions are started from the server. If you need an ad hoc session or a
restore session, you must open the port.
By default, clients contact the server. To permit the start of scheduled
backup-archive client sessions to the server only, change the SessionInitiation
parameter to ServerOnly either on the REGISTER NODE command, or on the
UPDATE NODE command and specify the HLA and LLA options. These options
must match what the client is using, otherwise the server will not know how to
contact the client. By doing so, you specify that the server will not accept client
requests for sessions. All sessions must be started by server-prompted scheduling
on the port that was defined for the client with the REGISTER NODE or the
UPDATE NODE commands. If you select the CLIENTORSERVER option, the client
might start sessions with the server by communicating on the TCP/IP port that
was defined with the TCPPORT server option. Server-prompted scheduling also
can be used to prompt the client to connect to the server.
Note: This function is for server-prompted scheduling only.
Scheduled backup-archive client sessions are started by the server. You can permit
individual clients to start sessions with a server on a node-by-node basis.
Scheduling uses the high-level address and the low-level address that you set on
the REGISTER NODE or UPDATE NODE commands.
Chapter 3. Server and Client Communication Methods
33
To start a session outside a firewall, specify a port on which the server listens for
client session requests on the port that the client defined. Use the TCPPORT option
in the dsmserv.opt file to specify the port number. The default TCP/IP port is 1500.
34
IBM Tivoli Storage Manager for Linux: Quick Start
Chapter 4. Customizing Your IBM Tivoli Storage Manager
System
You have installed, set up, and started the IBM Tivoli Storage Manager server and
administrative clients. This chapter describes the following customization tasks:
v “Increasing Database and Recovery Log Sizes”
v “Increasing Disk Storage Pool Sizes” on page 36
v “Adding Administrators” on page 37
v “Adding Backup-Archive Clients” on page 37
v “Using Tape Devices and Optical Devices” on page 37
v “Creating a New Policy” on page 50
v
v
v
v
“Invoking Expiration Processing” on page 52
“Creating a Client Include-Exclude List” on page 52
“Automating Client Operations” on page 53
“Automating Administrative Commands” on page 55
The customization described here does not include all IBM Tivoli Storage Manager
functions. However, it does provide a flexible, powerful system that can meet most
customers’ needs. If the server that you have just installed will be part of a
network of IBM Tivoli Storage Manager servers, your customization tasks may be
affected. For example, your server may receive configuration information from a
server that is designated as a configuration manager. This information could
include objects such as administrator definitions, policy definitions, and server
definitions. On the other hand, your server may be the configuration manager, and
your definitions will be provided to a network of managed servers. In addition,
you may have to define one or more other servers to your server. For details, see
Administrator’s Guide.
v Examples of administrative tasks are shown for both the command line
and the Web interface. All Web examples are begun from the Object
view.
v The IBM Tivoli Storage Manager server must be running to perform the
tasks described here. Start the server if it is not running (see “Starting
and Stopping the Server” on page 25 for the procedure).
Increasing Database and Recovery Log Sizes
The first-time installation procedure creates a default 17MB database volume
(db.dsm) and a default 9MB recovery log volume (log.dsm). Databases and recovery
logs are allocated in 4MB increments with an additional 1MB for overhead.
The database size is largely determined by the number of client files being stored
on server storage. As you add clients, you may need to increase your database
size. The recovery log size may need to be increased depending on the current
utilization.
To increase the size of the database or recovery log, do the following:
1. Format and define a 500MB database volume and a 25MB recovery log volume
and extend the database and recovery log, by entering:
© Copyright IBM Corp. 2002, 2003
35
define dbvolume db2.dsm formatsize=500
define logvolume log2.dsm formatsize=25
extend db 500
extend log 25
OR
Format and define the database volume, and extend the database:
a.
b.
c.
d.
Expand Database.
Select Database Volumes.
From Operations, select Define Database Volume.
Enter the required information and Finish.
e. Return to Database and from Operations, select Extend.
f. Enter the required information and Finish.
Format, define and extend the recovery log volume:
a. Expand Recovery Log.
b. Select Recovery Log Volumes.
c.
d.
e.
f.
Select Define Recovery Log Volume.
Enter the required information and Finish.
Return to Recovery Log and select Extend.
Enter the required information and Finish.
Increasing Disk Storage Pool Sizes
At server installation, these storage pool volumes are created:
The disk storage pool volumes should be at least large enough to hold one day’s
worth of client backups. As you add clients, you may need to increase your disk
storage pool size. You can format and define additional storage pool volumes. For
example, to create a 100MB volume named sbkup01.dsm in BACKUPPOOL, do the
following:
define volume backuppool sbkup01.dsm formatsize=100
OR
1.
2.
3.
4.
5.
6.
36
Expand Server Storage.
Expand Storage Pools.
Expand Disk Storage Pools.
Select Volumes.
From Operations, select Define a disk storage pool volume.
Enter the required information and Finish.
IBM Tivoli Storage Manager for Linux: Quick Start
Adding Administrators
If you have installed any additional administrative clients, you should register
them and grant an authority level to each. For details about authority levels, see
Administrator’s Guide.
The user ID SERVER_CONSOLE cannot be used by another administrator.
For example, register an administrator with a user ID of MARK and a password of
MISSOURI and grant system authority.
register admin mark missouri
grant authority mark classes=system
OR
1. Select Administrators.
2. Select Register an Administrator.
3. Enter the administrator information and Finish.
Adding Backup-Archive Clients
You are ready to register any additional backup-archive clients that you have
installed. For example, register a node named MERCEDES with the password
MONTANA.
register node mercedes montana userid=none
OR
1. Select Client Nodes.
2. Select Register a New Node.
3. Enter the node information and Finish.
Two commands, DEFINE CLOPTSET and DEFINE CLIENTOPT, allow you
to define client options affecting backup, archive, restore, and retrieval
operations. See Tivoli Storage Manager Administrator’s Guide and
Backup-Archive Clients Installation and User’s Guide for details.
Using Tape Devices and Optical Devices
|
|
|
Before you can use tape and optical devices with IBM Tivoli Storage Manager, you
must do the following:
1. Attach the devices to your system, which includes physically attaching the
devices, configuring the device drivers, and determining the device names.
2. Define the following: a library for the drives, the drives, paths from the server
to library and drives, a device class, and a storage pool associated with the
device class.
Chapter 4. Customizing Your IBM Tivoli Storage Manager System
37
3. Include the storage pool in your storage hierarchy.
To perform these tasks you can use the administrative client command line or Web
interface.
This section describes the following tasks:
v
v
v
v
v
“Attaching Devices” on page 39
“Adding a Manual Tape Library to the Server” on page 43
“Adding an Automated Tape Library to the Server” on page 45
“Preparing Tape Volumes” on page 47
“Migrating Data from Disk to Tape” on page 49
If you want to use a tape management system with IBM Tivoli Storage Manager
see the Administrator’s Guide for details.
The examples in this section set up the following configuration:
v A manual library consisting of two 8mm tape drives.
v An 8mm automatic tape library with two drives.
v A tape storage pool associated with these libraries. All the disk storage pools
migrate data to this tape storage pool.
Here are some concepts that can help you to set up your tape environment
(see Administrator’s Guide):
Storage pool migration
To prevent disk storage pools from becoming filled with client data, you
can specify that client data be automatically migrated to the tape storage
pool.
A disk’s high migration threshold (default value: 90%) determines when data
is migrated. The low migration threshold (default value: 70%) determines
when migration stops. Thus data migration from the default backup disk
storage pool begins when the pool is 90% full and continues until it is at
70% full or less.
Another default is to cache data (leave the data on the storage pool) even
after the data has been migrated. Cached data stays on disk for quick
access until the space is needed for new data.
Scratch volumes
A scratch volume is a volume that is available for the server to use. The
volume is labeled, is either blank or contains no valid data, and is not
defined to IBM Tivoli Storage Manager. You must specify the number of
scratch volumes that the server can request for this pool (MAXSCRATCH
parameter).
Collocation
Collocation means that the server tries to keep a client’s files on a minimal
number of tape volumes. It is turned off by default. Once clients begin
storing data in a storage pool with collocation off, you cannot easily change
the data in the storage pool so that it is collocated. To understand the
advantages and disadvantages of collocation, see the Administrator’s Guide.
38
IBM Tivoli Storage Manager for Linux: Quick Start
|
Attaching Devices
|
|
|
|
For IBM Tivoli Storage Manager to use a device, you must physically attach the
devices to the server and install the appropriate device driver on your system. The
following sections discuss how this is done for drives in a manual library and for
the drives and controller in automated libraries.
|
|
|
|
|
Attaching a Manual Drive
|
|
|
|
|
|
|
|
|
Perform the following steps to attach a manual drive:
1. Install the SCSI adapter card in your system, if not already installed.
2. Determine the SCSI IDs available on the SCSI adapter card to which you are
attaching the device. Find one unused SCSI ID for each drive.
3. Follow the manufacturer’s instructions to set the SCSI ID for the device to the
unused SCSI ID that you found. Usually this means setting switches on the
back of the device.
Note: Each device that is connected in a chain to a single SCSI bus through a
fibre channel adapter card must be set to a unique SCSI ID. If devices
are not set sequentially, and there is a gap in the sequence, the system
will only see the first device.
4. Follow the manufacturer’s instructions to attach the device to your server
system hardware.
|
Attention:
|
|
|
|
|
a. Power off your system before attaching a device to prevent damage to the
hardware.
b. Attach a terminator to the last device in the chain of devices connected on
one SCSI adapter card.
Install the appropriate device driver.
See “Installing Device Drivers” on page 40.
Find the device worksheet that applies to your device. See
www.ibm.com/software/sysmgmt/products/
support/IBMTivoliStorageManager.html.
Determine the name for the device and record the name on the device
worksheet. The device name for a tape drive is a special file name. Enter in the
worksheet the device special file name. See “Installing Device Drivers” on
page 40.
|
|
|
|
|
|
|
|
|
5.
6.
7.
8.
See “Determining Device Special File Names” on page 41 for details.
|
|
|
Keep the Worksheets: The information you record on the worksheets can help you
when you need to perform operations such as adding volumes. Keep the
worksheets for future reference.
|
|
|
Attaching an Automated Library Device
|
|
|
|
|
|
Perform the following steps to attach an automated library device:
1. Install the SCSI or FC adapter card in your system, if not already installed.
2. Determine the SCSI IDs available on the adapter card to which you are
attaching the device. Find one unused SCSI ID for each drive, and one for the
library or autochanger controller.
Note: In some automated libraries, the drives and the autochanger share a
single SCSI ID, but have different LUNs. For these libraries, only a single
SCSI ID is required. Check the documentation for your device.
Chapter 4. Customizing Your IBM Tivoli Storage Manager System
39
|
|
|
3. Follow the manufacturer’s instructions to set the SCSI ID for the drives and
library controller to the unused SCSI IDs that you found. Usually this means
setting switches on the back of the device.
|
|
|
|
|
Note: Each device connected in a chain to a single SCSI bus must be set to a
unique SCSI ID. If each device does not have a unique SCSI ID, you may
have serious system problems.
4. Follow the manufacturer’s instructions to attach the device to your server
system hardware.
|
|
|
Attention:
a. Power off your system before attaching a device to prevent damage to the
hardware.
|
|
|
|
|
|
|
b. You must attach a terminator to the last device in the chain of devices
connected on one SCSI adapter card. Detailed instructions should be in the
documentation that came with your hardware.
5. Install the appropriate device driver. See “Installing Device Drivers”.
6. Go to www.ibm.com/software/sysmgmt/products/
support/IBMTivoliStorageManager.html. Find the device worksheet that applies
to your device, and determine the name for the device.
|
|
7. Enter in the worksheet the device special file name. See “Installing Device
Drivers”.
|
|
|
|
Keep the Worksheets: The information you record on the worksheets can help
you when you need to perform operations such as
adding volumes to an autochanger. Keep them for
future reference.
|
|
|
|
Setting the Library Mode: For IBM Tivoli Storage Manager to access a SCSI
library, the device must be set for the appropriate mode. The mode that the server
requires is usually called random mode; however, terminology may vary from one
device to another. Two examples follow:
|
|
|
|
|
|
v Some libraries have front panel menus and displays that can be used for explicit
operator requests. However, if the device is set to respond to such requests, it
typically will not respond to requests made by IBM Tivoli Storage Manager.
v Some libraries can be placed in sequential mode, in which volumes are
automatically mounted in drives by using a sequential approach. This mode
conflicts with how IBM Tivoli Storage Manager accesses the device.
|
|
Refer to the documentation for your device to determine how to set it to the
appropriate mode.
Installing Device Drivers
|
To use a device, you must install the appropriate device driver. Tivoli Storage
Manager provides its own device driver for non-IBM devices. Use IBM device
drivers for IBM devices, as shown in Table 15 on page 41 and Table 16 on page 41.
These device drivers are available on the ftp site
ftp://ftp.software.ibm.com/storage/devdrvr/. Using a device class with a third
party vendor device driver is not recommended. The availability of IBM device
drivers required by Tivoli Storage Manager to support IBM 3570, 3590, and LTO
Ultrium tape drives and libraries on Linux for pSeries servers will be posted on
the Web at ftp://ftp.software.ibm.com/storage/devdrvr/Linux/README.
|
|
|
|
|
|
|
|
|
|
40
IBM Tivoli Storage Manager for Linux: Quick Start
|
|
|
|
|
|
IBM tape drives and libraries
Install the device driver that IBM supplies. See “Installing Device Drivers
for IBM SCSI Tape Devices” on page 42 and “Installing Device Drivers for
IBM 349X Libraries” on page 42.
|
|
|
|
|
Non-IBM tape drives and autochangers
You must ensure that you have installed the appropriate device drivers.
When you install Tivoli Storage Manager, you must choose whether to
install the Tivoli Storage Manager device driver or the native operating
system device driver for tape devices.
|
|
|
Selecting Device Drivers
Table 15 and Table 16 list the device drivers needed for Tivoli Storage Manager
drives and libraries.
| Table 15. Device Drivers for Tape Drives
| Device
Device Type
Library
| 4MM drive
4MM
External, Manual, SCSI
| 8MM drive
|
| DLT drive
|
| DTF drive
8MM
External, Manual, SCSI
DLT
External, Manual, SCSI
DTF
External, Manual, SCSI
| QIC drive
QIC
External, Manual, SCSI
| IBM 3590, 3590E, 3590H drive
|
3590
External, Manual, SCSI, 349X
IBM TotalStorage™
tape device drivers
| IBM LTO Ultrium 3580 drive
|
|
LTO
External, Manual, SCSI
IBM Ultrium device
drivers
Device Driver
Tivoli Storage
Manager device
driver (mt)
| Table 16. Device Drivers for Automated Libraries
| Device
Library Type
Device Driver
| IBM LTO Ultrium 3581, 3583, 3584
| Library
SCSI
IBM Ultrium device driver
| IBM 3494, 3495 Library
349X
IBM Tape Library Driver (ibmatl)
| Non-IBM SCSI libraries
|
|
SCSI
Tivoli Storage Manager device driver
(lb)
|
|
See www.ibm.com/software/sysmgmt/products/
support/IBMTivoliStorageManager.html for a list of supported libraries.
|
|
|
|
Determining Device Special File Names
To work with removable media devices, Tivoli Storage Manager needs the device’s
special file name. You specify the device special file name when you issue the
DEFINE PATH commands for drives and libraries.
Chapter 4. Customizing Your IBM Tivoli Storage Manager System
41
Note: To see the special file names, use the command:
|
ls /dev/IBM*
|
|
|
|
|
|
When a device configures successfully, a logical file name is returned. Table 17
specifies the name of the device (or the special file name) that corresponds to the
drive or library. In the examples, x denotes any positive number.
|
Table 17. Device Examples
|
Device
Device Special File Name
|
|
Tape drives that are supported by the Tivoli Storage
Manager device driver
/dev/tsmscsi/mtx
|
Tape drives that are supported by the IBM device driver
/dev/IBMtapex
|
|
SCSI-attached libraries that are supported by the Tivoli
Storage Manager device driver
/dev/tsmscsi/lbx
|
|
Automatic Cartridge Facility feature of the IBM 3590 B11 as /dev/IBMchangerx
a library
|
IBM 349X libraries
/dev/3494lib
|
IBM 3581, 3583, 3584 libraries
/dev/IBMchangerx
|
|
Mount point to use on REMOVABLEFILE device type
(CD-ROM)
/mnt/cdrom
|
|
|
File system to use on REMOVABLEFILE device type (zip
drive)
/zip
|
|
|
|
Installing Device Drivers for IBM SCSI Tape Devices
For information on how to install device drivers for IBM 358X, and 3590 devices,
see
v IBM TotalStorage Tape Device Drivers Installation and User’s Guide
v IBM Ultrium Device Drivers: Installation and User’s Guide
|
|
|
|
|
|
Installing Device Drivers for IBM 349X Libraries
|
|
|
|
|
To determine the name to use to define the path for the library, check what you
entered in the /etc/ibmatl.conf file for the library’s symbolic name. Use this
information to complete the Device Name field on your worksheet. For example, if
the symbolic name for the library in the /etc/ibmatl.conf file is 3494a, enter that
name on the worksheet in the Device Name field for the library.
|
|
The drives that are in the library are set up separately. See “Installing Device
Drivers for IBM SCSI Tape Devices”.
|
|
|
|
|
|
|
|
Obtaining Information About Your System’s SCSI Devices
For an IBM 349X Tape Library Dataserver, refer to IBM TotalStorage Tape Device
Drivers Installation and User’s Guide (GC35-0154) to install the driver. The driver is
the IBM Tape Library Driver, which consists of the ibmatl (a daemon) and other
components.
Information about the devices seen by your system is available in the file
/proc/scsi/scsi.This file contains a list of every recognized SCSI device. For example,
if a system contains some STK and IBM libraries, a SAN Gateway, and some
Quantum DLT drives, the /proc/scsi/scsi file will look similar to this:
Attached devices:
Host: scsi2 Channel: 00 Id: 00 Lun: 00
Vendor: STK
Model: 9738
Rev: 2003
42
IBM Tivoli Storage Manager for Linux: Quick Start
|
|
|
|
|
|
|
|
|
|
Type: Medium Changer
ANSI SCSI revision: 02
Host: scsi2 Channel: 00 Id: 01 Lun: 02
Vendor: PATHLIGHT Model: SAN Gateway
Rev: 32aC
Type: Unknown
ANSI SCSI revision: 03
Host: scsi2 Channel: 00 Id: 01 Lun: 02
Vendor: QUANTUM Model: DLT7000
Rev: 2560
Type: Sequential-Access
ANSI SCSI revision: 02
Host: scsi2 Channel: 00 Id: 01 Lun: 04
Vendor: IBM
Model: 7337
Rev: 1.63
Type: Medium Changer
ANSI SCSI revision: 02
|
|
From this listing, the type of devices, as well as the model name, vendor, and SCSI
channel/ID data is available.
|
|
|
Configuring Device Drivers for Non-IBM Tape Drives and
Libraries
|
|
To use the Tivoli Storage Manager device drivers, you must perform the following:
1. Verify that the device is connected to your system, and is powered on and
active
2. Ensure that the Tivoli Storage Manager device driver package
(TIVsm-tsmscsi-5.2.0-0) is installed for your corresponding architecture.
|
|
|
|
Note: To load the device driver, enter ./tsmscsi from the install location of the
Tivoli Storage Manager device driver.
3. Copy the two sample configuration files located in the installation directory
from lb.conf.smp and mt.conf.smp to lb.conf and mt.conf, respectively.
|
|
|
|
|
|
4. Edit the lb.conf and mt.conf files. Add one stanza (as shown in the example at
the top of the file) for each SCSI target ID and LUN combination you want the
device driver to probe for supported tape drives.
5. To load the device driver, run the tsmscsi script from the device driver
installation directory.
6. Determine the special file names for the tape drives and libraries.
The special file for each tape drive and library appears in the /dev/tsmscsi
directory. The tape drive special file has the form /dev/tsmscsi/mtx, where x is
a number. The library special file has the form /dev/tsmscsi/lbx, where x is a
number. To determine the names for the tape drives, issue the following
command:
|
|
|
|
|
|
|
|
||
|
|
||
|
> ls /dev/tsmscsi/mt*
To determine the names for the libraries issue the following command:
> ls /dev/tsmscsi/lb*
Adding a Manual Tape Library to the Server
In the following example, two stand-alone 8mm drives are added to IBM Tivoli
Storage Manager. IBM Tivoli Storage Manager requires that all drives are
associated with a library. For standalone drives, you must define a manual library.
Unlike other library types, no path is defined for manual libraries. You can use this
example as a guide when configuring other manual tape and optical devices. This
example presents the procedure with a minimum of customization. If you want to
do more, see the references in the steps for more details.
The commands, in the order entered, for defining a manual tape library are:
Chapter 4. Customizing Your IBM Tivoli Storage Manager System
43
DEFINE LIBRARY
DEFINE DRIVE
DEFINE PATH
DEFINE DEVCLASS
DEFINE STGPOOL
1. Define a manual library and two drives associated with it. The library is named
manuallib. The two drives, named DRIVE01 and DRIVE02, are at SCSI adaptor 0
and SCSI IDs 1 and 2.
define library manuallib libtype=manual
define drive manuallib drive01
define path server1 drive01 srctype=server desttype=drive
library=manuallib device=/dev/tsmscsi/lb2 online=yes
define drive manuallib drive02
define path server1 drive02 srctype=server desttype=drive
library=manuallib device=/dev/tsmscsi/mt2 online=yes
OR
a. Expand Server Storage.
b. Expand Libraries and Drives.
c.
d.
e.
f.
g.
Select Manual Libraries.
From Operations, select Define Manual Library.
Enter the library information and Finish.
Under Libraries and Drives, select Manual Drives.
From Operations, select Define Manual Drive.
h. Enter the drive information and Finish.
i. Under Server Storage, select Tape Paths.
j. From Operations, select Define Drive Path.
k. Enter the path information and Finish.
2. Classify the devices by device type. It is helpful to choose a device class name
that identifies the type of device for which it is intended (in this example,
TAPECLASS).
define devclass tapeclass devtype=8mm format=8500 library=manuallib
OR
a. Expand Device Classes.
b. Select 8MM Device Classes.
c. From Operations, select Define Device Class.
d. Enter the device class information and Finish.
3. Define a storage pool named TAPEPOOL for the device class.
define stgpool tapepool tapeclass maxscratch=20
OR
44
IBM Tivoli Storage Manager for Linux: Quick Start
a.
b.
c.
d.
Expand Server Storage.
Expand Storage Pools.
Select Sequential Access Storage Pools.
From Operations, select Define Sequential Access Storage Pool.
e. Enter the storage pool information and Finish.
Adding an Automated Tape Library to the Server
The following example shows how to add an Exabyte EXB-210 library containing
two drives. You can use this example as a guide when configuring other
automated tape devices. This example presents the procedure with a minimum of
customization. If you want to do more, see the references in the steps.
The commands, in the order entered, for defining an automated tape library are:
DEFINE LIBRARY
DEFINE PATH
DEFINE DRIVE
DEFINE PATH
DEFINE DEVCLASS
DEFINE STGPOOL
1. Define an automated tape library and its two internal drives.
The library is an Exabyte EXB-210, named lib2, whose SCSI library mechanism
is at SCSI ID 3. The two drives, named mt5 and mt6, are at SCSI IDs 5 and 6.
The element addresses for the drives in an EXB-210 are 82 and 83.
OR
a. Expand Server Storage.
b. Expand Libraries and Drives.
c.
d.
e.
f.
g.
h.
Select Automated Libraries.
From Operations, select Define Automated Library.
Enter the library information and Finish.
Under Server Storage, select Tape Paths.
From Operations, select Define Library Path.
Enter the path information and Finish.
i. Under Libraries and Drives, select Automated Drives.
j. From Operations, select Define Automated Drive.
k. Enter the drive information and Finish.
l. Under Server Storage, select Tape Paths.
m. From Operations, select Define Drive Path.
n. Enter the path information and Finish.
Element address
The element address is a number that indicates the physical location of a
drive within an automated library. IBM Tivoli Storage Manager needs the
element address to connect the physical location of the drive to the drive’s
SCSI address. When you define a drive, the element address is required if
there is more than one drive in an automated library.
Chapter 4. Customizing Your IBM Tivoli Storage Manager System
45
2. Classify the drives in the library by device type. It is helpful to choose a device
class name that identifies the type of device for which it is intended (in this
example, AUTOCLASS).
define devclass autoclass devtype=8mm format=8500 library=autolib
OR
a.
b.
c.
d.
Expand Device Classes.
Select 8MM Device Classes.
From Operations, select Define Device Class.
Enter the device class information and Finish.
3. Define a storage pool named AUTOPOOL for the device class.
define stgpool autopool autoclass maxscratch=20
OR
a. Expand Storage Pools.
b. Select Sequential Access Storage Pools.
c. From Operations, select Define Sequential Access Storage Pool.
d. Enter the storage pool information and Finish.
Displaying Information About Your Devices
Before continuing, you can view the results of your definitions. If necessary, you
can update these definitions by using update commands.
v To query the libraries:
query library
v To query the drives:
query drive
v To query the paths:
query path
v To query the device classes:
query devclass format=detailed
v To query the storage pools:
query stgpool
OR
v To query the libraries and drives:
46
IBM Tivoli Storage Manager for Linux: Quick Start
1. Expand Server Storage.
2. Expand Libraries and Drives.
3. Select:
– Manual Libraries or Automated Libraries and then the libraries you have
defined
– Manual Drives or Automated Drives and then the drives you have
defined
v To query the path:
1. Expand Server Storage.
2. Select:
Tape Paths and the tape paths you have defined
Disk Paths and the disk paths you have defined
v To query the device classes:
1.
2.
3.
v To
1.
Expand Server Storage.
Expand Device Classes.
Select 8MM and then the device classes you have defined.
query the storage pools:
Expand Server Storage.
2. Expand Storage Pools.
3. Select Sequential Access Storage Pools and then the storage pools you have
defined.
Preparing Tape Volumes
All tape volumes must be labeled before they can be used. If you want a volume
to be used only when it is requested by name, you must also define it to IBM
Tivoli Storage Manager. A defined volume is a private volume and is assigned to a
specific storage pool. A volume that is not defined is a scratch volume. A storage
pool can request available scratch volumes up to the number specified for that
storage pool.
Preparing Tape Volumes with a Manual Drive
If you are using only one tape drive, consider labeling several tapes at this time.
1. From an administrative client command line, use a drive in the library named
MANUAL to label a volume as DSM001:
label libvolume manual dsm001
OR
a. Expand Server Storage.
b. Expand Libraries and Drives.
c. Select Library Volumes.
d. From Operations, select Label Library Volume.
e. Enter the volume information and Finish.
2. Define any volumes that are to be used as private volumes. For example, define
the volume you just labeled:
Chapter 4. Customizing Your IBM Tivoli Storage Manager System
47
define volume tapepool dsm001
OR
a.
b.
c.
d.
Expand Storage Pools.
Select Sequential Access Storage Pools.
Select the storage pool you want.
Select Volumes.
e. From Operations, select Define Sequential Access Volume.
f. Enter the volume information and Finish.
Preparing Tape Volumes with an Automated Library
To label tapes with an automated library, remove any tapes that you do not want
to use with IBM Tivoli Storage Manager, and load the tapes to be labeled.
1. Use the LABEL LIBVOLUME command to label and check in the volumes.
From an administrative client command line, begin a search of an automated
library named AUTOLIB for unlabeled volumes and label them based on their
barcodes:
label libvolume autolib search=yes labelsource=barcode
checkin=scratch
OR
a. Expand Server Storage.
b. Expand Libraries and Drives.
c. Select Library Volumes.
d. From Operations, select Label Library Volume.
e. Enter the volume information and Finish.
2. Define any volumes that are to be used as private volumes.
define volume autopool dsm001
OR
a.
b.
c.
d.
e.
f.
48
Expand Storage Pools.
Select Sequential Access Storage Pools.
Select the storage pool you want.
Select Volumes.
From Operations, select Define Sequential Access Volume.
Enter the volume information and Finish.
IBM Tivoli Storage Manager for Linux: Quick Start
Including Tape in the Storage Hierarchy
You can now configure the server so that client data can be migrated to tape. To
migrate from BACKUPPOOL to AUTOPOOL and from ARCHIVEPOOL to
TAPEPOOL do the following:
update stgpool backuppool nextstgpool=autopool
update stgpool archivepool nextstgpool=tapepool
OR
1.
2.
3.
4.
5.
Expand Server Storage.
Expand Storage Pools.
Select Disk Storage Pools.
Select the pool to be updated.
Select Update Disk Storage Pool.
6. Enter the storage pool information and Finish.
Migrating Data from Disk to Tape
To verify that the tape devices are properly set up, migrate data from a disk
storage pool. Migration requires tape mounts. The mount messages are directed to
the console message queue and to any administrative client that has been started
with either the mount mode or console mode option.
Trigger migration from a disk storage pool (BACKUPPOOL, for example) by
setting the high and low migration thresholds to 0:
update stgpool backuppool highmig=0 lowmig=0
After migration occurs, reset the thresholds to their original settings:
update stgpool backuppool highmig=90 lowmig=70
OR
To migrate data from a disk storage pool and, after migration occurs, to reset the
thresholds to their original settings, update the storage pool:
1. Expand Server Storage.
2. Expand Storage Pools.
3.
4.
5.
6.
Select Disk Storage Pools.
Select the pool to be updated.
Select Update Disk Storage Pool.
Enter the storage pool information and Finish.
Chapter 4. Customizing Your IBM Tivoli Storage Manager System
49
Controlling when migration occurs
Because migration from a disk to a tape storage pool uses resources such as
drives and operators, you may want to control when migration occurs. To
do so, leave the high migration threshold set to 100 most of the time, and
lower it when you want migration to occur.
In the preceding step, you lowered both migration thresholds to 0 to verify
that migration occurred. You may not want to empty the disk storage pool
by setting the low migration threshold to 0 every time you want migration
to occur. Normally, you may want to keep the low threshold at 40%, and
vary the high threshold from as high as 90% to as low as 50%. See
Administrator’s Guide for details.
Creating a New Policy
The Tivoli Storage Manager default policy specifies how Tivoli Storage Manager
manages client files. For example, it specifies that Tivoli Storage Manager retains
up to two backup versions of any file that exists on the client (see “Installation and
Setup Results” on page x for details). Two versions may be enough for most clients.
However, if some clients need the last ten versions to be kept, you can do either of
the following:
v Create a new policy domain and assign these clients to that domain (described
in this section).
v Create a new management class within the default policy domain. The
include-exclude lists for all the affected clients must now be updated.
Storing Directly to Tape
Under the default policy, client files are stored directly to disk. You can also
define policies for storing client files directly to tape. In a copy group,
simply name a tape pool as the destination. Note, however, that if you store
directly to tape, the number of available tape drives limits the number of
client nodes that can store data at the same time.
To create a new policy, you can start by copying the policy domain, STANDARD.
This operation also copies the associated policy set, management class, and copy
groups. You then assign clients to the new domain.
1. Copy the default policy domain, STANDARD, to the new policy domain,
NEWDOMAIN.
copy domain standard newdomain
OR
a.
b.
c.
d.
Select Policy Domains.
Select STANDARD domain.
From Operations, select Copy Policy Domain.
Enter the domain information and Finish.
This operation copies the policy domain, and all associated policy sets,
management classes, and copy groups. Within the policy domain named
NEWDOMAIN and the policy set named STANDARD, you have:
50
IBM Tivoli Storage Manager for Linux: Quick Start
v Management class named STANDARD
v Backup copy group named STANDARD
v Archive copy group named STANDARD
For our example, you update only the backup copy group.
2. Update the backup copy group by specifying that ten versions of backed up
files are to be kept.
update copygroup newdomain standard standard standard type=backup verexists=10
OR
a. Expand Policy Domains, Policy Sets, and then Management Classes.
b. Select Backup Copy Groups.
c. Select the NEWDOMAIN STANDARD STANDARD STANDARD copy
group.
d. From Operations, select Update Copy Group.
e. Enter the copy group information and Finish.
3. Validate and activate the STANDARD policy set in NEWDOMAIN.
validate policyset newdomain standard
activate policyset newdomain standard
OR
a. Expand Policy Domains and then select Policy Sets.
b. Select NEWDOMAIN STANDARD policy set.
c. From Operations, select Validate Policy Set and then Finish.
d. From Operations, select Activate Policy Set and then Finish.
The following conditions result in warning messages during validation:
v A destination storage pool is not a defined storage pool.
v The default management class does not contain a backup or archive copy
group.
v The current ACTIVE policy set names a management class that is not
defined in the policy set being validated.
v The current ACTIVE policy set contains copy groups that are not defined
in the named policy set.
v A management class specifies that a backup version must exist before a
file can be migrated from a client node, but the management class does
not contain a backup copy group.
4. Assign client nodes to the NEWDOMAIN policy domain by either updating
existing client nodes or registering new nodes. For example, to update client
node mercedes, do either of the following:
update node mercedes domain=newdomain
Chapter 4. Customizing Your IBM Tivoli Storage Manager System
51
OR
a.
b.
c.
d.
Expand Clients.
Select Client Nodes.
Select the desired node.
From Operations, select Update this Node.
e. Enter the node information and Finish.
Tivoli Storage Manager will now keep up to ten versions of backed up files for
client node mercedes because it is assigned to the NEWDOMAIN policy
domain.
Attention: If you associate a client that is currently running with a new
domain, the client must be stopped and restarted before the new association
will take effect.
Invoking Expiration Processing
Expired files are not deleted from server storage until expiration processing occurs.
You can invoke expiration processing in a number of ways:
v The expiration interval server option can specify that processing be invoked at a
set interval from the time the server is started. The default is a 24 hour interval.
v You can issue the EXPIRE INVENTORY command manually whenever you wish
(see the following example).
v You can schedule the EXPIRE INVENTORY command to be issued regularly at a
specific time (see “Automating Administrative Commands” on page 55). If you
schedule expiration processing, set the expiration interval server option to 0.
expire inventory quiet=yes wait=no
OR
1. Select Server.
2. Select Server Status.
3. From Operations, select Expire Inventory.
4. Select any desired options and Finish.
Creating a Client Include-Exclude List
Any client can exclude some files from some policy operations and include other
files in other operations. This is done with statements in an include-exclude list or,
on UNIX clients, in an include-exclude file. For example, an include-exclude file
should exclude system files that, if recovered, could corrupt the operating system.
Tivoli Storage Manager server and client directories should also be excluded. See
the appropriate Tivoli Storage Manager client user’s guide for details.
You can define include-exclude statements for your installation. Users can add
these statements in their client options file (dsm.sys). You can also enter the
statements in a set of options and assign that set to client nodes when you register
or update the nodes. For details about the DEFINE CLOPTSET and DEFINE
CLIENTOPT commands, see Administrator’s Guide and Administrator’s Reference.
52
IBM Tivoli Storage Manager for Linux: Quick Start
Here are a few examples of include-exclude statements:
v A user wants all *.sct and *.drw files in the /eng/spec/ directory included for
backup but all other files in that directory excluded. The user adds the following
include-exclude statements:
exclude /eng/spec/*.*
include /engspec/*.drw
include /eng/spec/*.sct
Tivoli Storage Manager reads the statements from the bottom up until a
match is found. In the preceding example, no match would be found on the
include statements for the file /eng/spec/proto.obj. Tivoli Storage Manager
reads the exclude statement, finds a match, and excludes the file.
v For a file or group of files, the user can also override the default management
class:
exclude /eng/spec/*.*
include /eng/spec/*.drw monthly
include /eng/spec/*.sct
In this example,
– *.sct files are bound to the default management class.
– *.drw files are bound to the management class monthly.
– All other files in the spec directory are excluded from backup or archive.
Automating Client Operations
You can schedule most client operations, such as backup, to begin automatically.
You can schedule the following on most clients:
v Tivoli Storage Manager backup, archive, restore, and retrieve operations
v Operating system commands
v Macros (files that can contain operating system and Tivoli Storage Manager
commands)
This section guides you through scheduling client backups for three registered
client nodes assigned to the STANDARD policy domain: bill, mark, and mercedes.
1. Schedule an incremental backup and associate the schedule with the clients.
The schedule, named DAILY_INCR, is for the Tivoli Storage Manager default
policy domain, named STANDARD. The default specifies backup to the disk
storage pool BACKUPPOOL. This schedule calls for a schedule window that:
v Begins on the date the schedule is defined (the default) at 11:00 p.m.
v Lasts for 1 hour (the default)
v Is repeated daily (the default)
v Stays in effect indefinitely (the default)
define schedule standard daily_incr action=incremental starttime=23:00
define association standard daily_incr bill,mark,mercedes
OR
a. Expand Automation.
Chapter 4. Customizing Your IBM Tivoli Storage Manager System
53
b.
c.
d.
e.
f.
Select Client Schedules.
From Operations, select Define Schedule.
Enter the schedule information and Finish.
Return to Client Schedules.
Select the desired schedule.
g. From Operations, select Define Associations.
h. Enter the association information and Finish.
2. Start the client scheduler. For the schedules to become active for a workstation,
a user must start the scheduler from the node.
dsmc schedule
To help ensure that the scheduler is running on the clients, start the client
acceptor daemon (CAD) or client acceptor service.
The include-exclude list (file on UNIX clients) on each client also affects
which files are backed up or archived by the two schedules defined in the
preceding steps. For example, if a file is excluded from backup with an
EXCLUDE statement, the file will not be backed up when the DAILY_INCR
schedule runs.
3. Because the DAILY_INCR schedule is to run daily, you can verify that it is
working as it should on the day after you define the schedule and associate it
with clients. If the schedule has run successfully, the status will be Completed.
query event standard daily_incr begindate=today-1
OR
a. Expand Automation.
b. Select Client Schedules.
c. Select the desired schedule name.
d. From Operations, select Query Client Events.
e. Enter the required information and Finish.
You can limit the query of events to display only schedules that did not run
as expected. For example, you can use the following command daily to see
which clients did not run the DAILY_INCR schedule the previous day:
query event standard daily_incr begindate=today-1 exceptionsonly=yes
Schedules that did not complete successfully have a status of Failed, Missed,
or Severed.
4. Check the results of the schedule DAILY_INCR on one of the clients that was
associated with that schedule. For most clients, information about what
happens when a schedule runs is stored in the file dsmsched.log. See the
Clients book.
54
IBM Tivoli Storage Manager for Linux: Quick Start
Automating Administrative Commands
You can automate Tivoli Storage Manager administrative tasks by scheduling
administrative commands. For example, you can automate commands that need to
be run regularly or that require significant processing or other system resources. In
this section, you define a schedule to run expiration processing.
1. Define a schedule named EXPPROC that invokes expiration processing every
night at 2:00 a.m.
This schedule calls for a schedule window that:
v Begins on the date the schedule is defined (the default) at 2:00 a.m.
v Lasts for 1 hour (the default)
v Is repeated every day
v Takes effect immediately
v Stays in effect indefinitely (the default)
define schedule expproc type=administrative cmd=’expire inventory’ active=yes starttime=02:00
OR
a. Select Automation.
b. Select Administrative Command Schedules.
c. From Operations, select Define Schedule.
d. Enter the schedule information and Finish.
2. Because the EXPPROC schedule is to run daily, you can verify that the
automation is working as it should on the day after you define the schedule. If
the schedule has run successfully, the status will be Completed.
query event expproc type=administrative begindate=today-1
OR
a.
b.
c.
d.
Select Automation.
Expand Administrative Command Schedules.
Select Query Administrative Events.
Enter the required information and Finish.
Protecting IBM Tivoli Storage Manager and Client Data
The database, recovery log, and storage pools are critical to the operation of the
server. If the database or recovery log is unusable, the entire server is unavailable.
If a database is lost and cannot be recovered, the backup, archive, and
space-managed data for that server is lost. If a storage pool volume is lost and
cannot be recovered, the data on the volume is also lost.
IBM Tivoli Storage Manager provides a number of ways to protect your data,
including backing up your storage pools and database. For example, you can
define schedules so that the following operations occur:
Chapter 4. Customizing Your IBM Tivoli Storage Manager System
55
v After the initial full backup of your storage pools, incremental storage pool
backups are done nightly.
v Full database backups are done weekly.
v Incremental database backups are done nightly.
56
IBM Tivoli Storage Manager for Linux: Quick Start
Appendix A. Using Administrative Interfaces
This appendix contains the following sections that describe how to use the IBM
Tivoli Storage Manager administrative interfaces:
v “Using the Administrative Web Interface”
v “Using the Administrative Client Command-Line Interface” on page 62
Using the Administrative Web Interface
You can enter IBM Tivoli Storage Manager commands, view server administration
data, and perform all administrative tasks directly from the Web interface. For
details about starting the Web interface, see “Starting and Stopping an
Administrative Client or the Web Interface” on page 26. To end a Web interface
session, select Log Off, from the Options pull down menu.
Note: To use the administrative Web interface, your browser must have Java
support. See “System Requirements” on page 18 for a list of supported
browsers.
IBM Tivoli Storage Manager Server Administration has four major views:
“Operation View” on page 58
“Network View” on page 60
“Configuration View” on page 60
“Object View” on page 60
The following sections contain details about each view.
Figure 3 on page 58 shows the four major views of the Web interface with the
Operation view partially expanded.
© Copyright IBM Corp. 2002, 2003
57
Figure 3. Administrative Web Interface Tree
By default, the time-out interval for an administrative Web interface session
is 10 minutes. After the interval elapses, you must reenter your
administrator name and password. To change the interval, do the following
from the Web interface:
1. Expand the Operation View.
2. Expand Manage Security.
3. Click Set web authentication time out.
Specify an interval from 0 to 9999 minutes. A value of 0 means that the
session is never timed out.
Operation View
Work with
administrators
Add, update, or delete administrators
Grant or revoke administrative privileges
Grant or revoke administrator authority to access and manage client nodes
Work with client
nodes
Add, update, or delete client nodes
Lock or unlock client nodes
Move node data
Automate client
operations
Define, update, or delete client schedules
Associate client nodes with a schedule
Remove client nodes from a schedule
Report on scheduled events
Tune scheduling settings
58
IBM Tivoli Storage Manager for Linux: Quick Start
Manage the database
and recovery log
View database details
Add or remove database volumes
Extend or reduce database size
Add a copy volume to the database
Work with the database space trigger
Work with the database backup trigger
Back up a database
View recovery log details
Add or remove recovery log volumes
Extend or reduce recovery log size
Add a copy volume to the recovery log
Work with the recovery log space trigger
Set the recovery log mode
Manage server storage
Query storage pools
Query storage pool volumes
Work with disk storage pools:
View disk storage pools
Define, update, or delete disk storage pools
Backup or restore storage pools
Define, update, or delete disk storage pool volumes
Move data on a storage pool volume
Vary a disk volume online or offline
Restore a disk storage pool volume
Work with sequential access storage pools:
View all sequential storage pools
Define, update, or delete sequential access storage pools
Backup or restore sequential access storage pools
Define, update, or delete sequential access volumes
Move data on a storage pool volume
Restore sequential access storage pool volume
Work with copy storage pools:
View all copy storage pools
Define, update, or delete copy storage pools
Define, update, or delete sequential access volumes
Move data on a storage pool volume
Automate operations
Define, update, activate, deactivate, and delete administrative command schedules
View events for administrative schedules
Define, update, rename, copy, delete, and run command scripts
Monitor operations
Query the server activity log
Query client schedule event records
View database details
View commands issued by administrators
View sessions currently accessing the server
View processes running on the server
Manage security
Set server authentication
Modify client registration settings
Enable client sessions
Disable client sessions
Set password expiration, invalid sign-on limit, and minimum password length
Set web authentication time out
Lock or unlock a node from server access
Lock or unlock administrators
Performance tuning
Tune client files sent by transaction
Tune files or bytes moved by transaction
Tune the database buffer pool
Appendix A. Using Administrative Interfaces
59
Central Configuration
Define or update settings for this server
Perform configuration manager operations:
Establish this server as a configuration manager
Work with configuration profiles
Notify subscribers of changes
Perform managed server operations:
Define the configuration manager server
Set configuration refresh frequency
View profiles available for subscription
Prepare to subscribe to server information
Prepare to subscribe to policy information
Work with profile subscriptions
Network View
Other servers
Define, update, delete, export, or import other servers
Client Nodes
Register, update, delete, export, or import client nodes
Server groups
Define, update, delete, or rename server groups
Define, delete, or move server group members
Route commands to multiple servers
Route a command to
multiple servers
Route commands to multiple servers
Configuration View
Define/update settings
for this server
Define or update server settings (for example, name, password, or address)
Configuration
manager operations
Establish this server as a configuration manager
Work with configuration profiles
Notify subscribers of changes
Managed server
operations
Define the configuration manager server
Set configuration refresh frequency
View profiles available for subscription
Prepare to subscribe to server information
Prepare to subscribe to policy information
Work with profile subscriptions
Configuration Objects
Work with configuration settings
Work with configuration profiles for the following:
Managed administrators
Managed policy domains
Managed command schedules
Managed scripts
Managed option sets
Managed server definitions
Managed server groups
Subscribers
Work with profile subscriptions
Object View
Administrators
60
Register, update, remove, rename, export, import, lock, or unlock administrators
Grant or revoke administrative privileges
Grant or revoke administrator authority to access and manage client nodes
IBM Tivoli Storage Manager for Linux: Quick Start
Clients
Work with client nodes:
Register, export, or import client nodes
Query occupancy for client nodes
Move node data
Work with file spaces
Work with backup sets
Work with client option sets:
Define client option sets
Define client options
Work with file spaces
Work with backup sets
Server
View server status and modify settings
Work with server options
View license information, audit and register licenses
Query activity log
View or cancel active processes
View or cancel active sessions
View or cancel restartable restore sessions
Query, backup, delete, or update volume history
View or define other servers
View or define server groups:
View or add server group members
Route a command to multiple servers
Database
Define database volumes
Define database copies
Define, update, or delete the database backup trigger
Define, update, or delete the database space trigger
Recovery Log
Work with the recovery log
View, define, or delete recovery log volumes
Define, update, or delete recovery log space trigger
Automation
Define, update, rename, copy, delete, and run server command scripts
Define, update, activate, deactivate, and delete administrative command schedules:
View or delete events for administrative schedules
Define, update, activate, deactivate, and delete client schedules:
Define, update, or delete client/schedule associations
View or delete events for client schedules
Define, update, activate, deactivate, and delete immediate actions schedules (one-time
processing of client tasks):
View or delete events for immediate actions schedules
Policy Domains
Define, update, delete, or copy policy domains
Import or export policy domains
Move client nodes from one domain to another
Define, update, delete, or copy policy sets
Activate or validate policy sets:
Define, update, delete, or copy management classes
Define, update, or delete copy groups
Work with client nodes
Register, export, or import client nodes
Query occupancy for client nodes
Move node data:
Work with file spaces
Work with backup sets
Define, update, activate, deactivate, and delete client schedules:
Define, update, or delete client/schedule associations
View or delete events for client schedules
Appendix A. Using Administrative Interfaces
61
Server Storage
Work with storage pools:
Work with disk storage pools:
View disk storage pools
Define, update, or delete disk storage pools
Backup or restore storage pools
Define, update, or delete disk storage pool volumes
Move data on a storage pool volume
Vary a disk volume online or offline
Restore a disk storage pool volume
Work with sequential access storage pools:
View all sequential storage pools
Define, update, or delete sequential access storage pools
Backup or restore sequential access storage pools
Define, update, or delete sequential access volumes
Move data on a storage pool volume
Restore sequential access storage pool volume
Work with copy storage pools:
View all copy storage pools
Define, update, or delete copy storage pools
Define, update, or delete sequential access volumes
Move data on a storage pool volume
Query storage pools
Query storage pool volumes
Work with device classes:
Define, update, or delete device classes
View defined device classes
Work with libraries and drives:
Define, update, or delete libraries and drives
Check-in or label library volumes
Define, update, or delete NAS data movers
Define, update, or delete SCSI data movers
Define, update, or delete tape paths for drives and libraries
Define, update, or delete disk paths
Define, update, or delete client/disk associations
Using the Administrative Client Command-Line Interface
The administrative client command-line interface lets administrators control and
monitor the server through administrative commands. For more information on
installing and using the command-line interface, see Administrator’s Reference.
Starting and Stopping the Interface
To enter a series of administrative commands, start the administrative client in
interactive mode by entering:
dsmadmc
You are then prompted to enter your user ID and password. If you do not want to
be prompted for that information, you can enter your user ID and password with
the DSMADMC command by using the -ID and -PASSWORD options. For
example, enter: dsmadmc -id=smith -password=secret
To end an administrative client session in interactive mode, use the QUIT
command: quit
62
IBM Tivoli Storage Manager for Linux: Quick Start
Appendix B. National Language Support
This appendix discusses National Language Support for the IBM Tivoli Storage
Manager server. National Language Support allows the server to display messages
and help in languages other than U.S. English. It also allows for the use of locale
conventions for date, time, and number formatting. The languages supported are:
v Brazilian Portuguese (pt_BR)
v Chinese, simplified (zh_CN)
v
v
v
v
v
v
Chinese, Big 5 (zh_TW)
Chinese, (zh_TW.euctw)
Chinese, (zh_CN.GB18030)
English (en_US)
French (fr_FR)
German (de_DE)
v Italian (it_IT)
v Japanese (ja_JP)
v Korean (ko_KR)
v Spanish (es_ES)
To enable support for a given locale, do the following:
v Set the LC_MESSAGES environment variable to match that which is set in the
server options file. For example, to set the environment variable for Italian,
enter:
export LC_MESSAGES=it_IT
v Set the LANGUAGE option in the server options file to the name of the locale to
use. For example, to use the it_IT locale, set the LANGUAGE option to it_IT. If
the locale is successfully initialized, the date, time, and number formatting for
the server will be controlled by the locale. This overrides the server option file
definitions for date, time, and number formatting. If the locale is not successfully
initialized, the server defaults to U.S. English message files, and the date, time,
and number formats are still controlled by the server options file.
The server console uses the locale/language defined by the server options
language variable. However, if an administrative client connects to the server
and specifies a locale that is different from the one specified at the server, the
server tries to initialize the administrative client’s specified locale for returning
messages to the client.
Note: For administrative Web interface users, some characters may not be
displayed properly if the html browser version is not the same language as
the server. If this problem occurs, it is recommended to use a browser
version that uses the same language as the server.
© Copyright IBM Corp. 2002, 2003
63
64
IBM Tivoli Storage Manager for Linux: Quick Start
Appendix C. Applying Updates to Tivoli Storage Manager
|
|
|
To do updates, issue the rpm command, using the -Uv option, instead of the -iv
option. For example,
|
will update whichever server you have installed to the 5.2.0 version.
rpm -Uvh TIVsm-server-5.2.0-0.i386.rpm
© Copyright IBM Corp. 2002, 2003
65
66
IBM Tivoli Storage Manager for Linux: Quick Start
Appendix D. Removing the IBM Tivoli Storage Manager Server
This appendix describes what you need to do before removing the current version
of the Tivoli Storage Manager server.
Before Removing IBM Tivoli Storage Manager
You must do the following:
1. Do a full database backup. For example, if you have a tape device class named
TAPECLASS, do a full backup by issuing the following command:
backup db type=full devclass=tapeclass
2. Save a copy of the volume history and device configuration files that were
defined in the server options file with the VOLHISTORY and DEVCONFIG
options respectively. For example, to save the volume history in a file called
VOLHIST and the device configuration in a file called DEVICES, enter:
backup volumehistory filenames=volhist
backup devconfig filenames=devices
3. Store the output volumes in a safe location.
Use the following command to remove Tivoli Storage Manager after completing
the backup described above:
rpm -e <packagename>
where <packagename> is one of the packages you have installed.
Note: To find out which packages you have installed, use the following command:
rpm -qa | grep TIVsm
© Copyright IBM Corp. 2002, 2003
67
68
IBM Tivoli Storage Manager for Linux: Quick Start
Appendix E. Setting Up the Secure Web Administrator Proxy
The IBM Tivoli Storage Manager Secure Web Administrator Proxy provides a
secure method for the Tivoli Storage Manager administrative Web interface to
retrieve Web pages without affecting the performance of the server. A Web proxy
on a separate Web server machine, not the IBM Tivoli Storage Manager server, fills
requests from the administrative Web interface for images and HTML pages. A
single Web server can handle requests for multiple IBM Tivoli Storage Manager
servers on different platforms as shown in Figure 4.
Tivoli Storage
Manager Servers
Web Server
with
Web Proxy
Administrator's
Workstations
Figure 4. IBM Tivoli Storage Manager and the Web Proxy
The Web proxy connects to IBM Tivoli Storage Manager as a client, secures the
connection, and retrieves Web pages or submits forms. The Tivoli Storage Manager
server responds with the requested HTML pages and redirects the URLs in the
page to the Web proxy. When the Web proxy receives the response, it passes the
information to the Web server. The Web server’s Secure Socket Layer (SSL) package
encrypts the information and returns it to the Web browser.
Prerequisites
To install, configure, and use the Web proxy, you need the following:
v A Web server on one of the following platforms: AIX, HP-UX, Sun Solaris, or
Windows NT and Windows 2000. The Web server can provide services to IBM
Tivoli Storage Manager servers on AIX, HP-UX, Sun Solaris, Linux, Windows NT
and Windows 2000, and MVS™.
© Copyright IBM Corp. 2002, 2003
69
Note: You should not install the Web server and IBM Tivoli Storage Manager
server on the same machine. To do so would be to lose the performance
advantage of using the Web proxy.
v An IBM Tivoli Storage Manager Secure Web Administrator Proxy CD mounted
on your server, or the location of the Web proxy files available via ftp.
v The communication methods set to TCP/IP and HTTP in the IBM Tivoli Storage
Manager server options file for each server that you will access.
Note: The HTTPS communication method, which was required for SSL support
under ADSM Version 3, is not required for the Web proxy and is not
supported by IBM Tivoli Storage Manager.
The Web server must have the following:
v At least 20MB of space to install the base package and the English-language
version of the Web proxy help files. If you install other languages, you will need
more space.
Note: The setup and configuration wizard does not check for available disk
space.
v Secure socket layer (SSL) set up.
v Support for Common Gateway Interface ( NT and Windows 2000) 1.0 or later.
v Support for Java Development Toolkit (JDK) or Java Runtime Environment (JRE)
1.1.6 or later. See “System Requirements” on page 18 for a list of browsers that
provide this support.
After the Web server is installed, note the location of:
v The Web server’s cgi-bin directory.
/opt/webserver/cgibin
v The location of the Web server’s HTML directory:
/opt/webserver/htdocs
v The location of the JRE’s base directory:
opt/java1.2/jre
Installing the Secure Web Administrator Proxy - Overview
To install the Secure Web Administrator’s Proxy, you must:
v Set up the IBM Tivoli Storage Manager Server
v Install the Web Administrator Proxy
v Use the Web Administrator Proxy
Setting Up the IBM Tivoli Storage Manager Server
Do the following on each IBM Tivoli Storage Manager you want to log into with
the Web proxy.
1. Ensure that an administrator ID and password that is dedicated to the Web
proxy is registered with the IBM Tivoli Storage Manager server. For example, to
register administrator PROXY with the password of PROXY, do the following:
register admin proxy proxy
Note: Do not grant any authority to the administrator. If you do, the security
of your IBM Tivoli Storage Manager system could be compromised.
70
IBM Tivoli Storage Manager for Linux: Quick Start
2. Set the TCP/IP address (high level) and TCP port (low level) addresses of the
IBM Tivoli Storage Manager server. For example, to set the TCP/IP address to
9.115.48.123 and the TCP port address to 1500, do the following:
set serverhladdress 9.115.48.123
set serverlladdress 1500
Installing the Secure Web Administrator Proxy
The Web proxy files are on a separate CD-ROM, named IBM Tivoli Storage Manager
Secure Web Administrator Proxy. This CD-ROM is shipped with IBM Tivoli Storage
Manager. The CD-ROM also includes HTML versions of all IBM Tivoli Storage
Manager server and client publications in a self-extracting zip file. You may also
obtain the Web proxy files via the FTP site. The most recent code can be
downloaded from
ftp://service.boulder.ibm.com/storage/tivoli-storage-management/swap/
Look at readme.download to better understand what files you really need to
download. For example, you do not need to download files that will not be
installed (like the German (deu) version of the HTML support files).
Follow this procedure to install the Web proxy:
1. On your Web server machine, download the Web proxy files via FTP or CD.
Put the files in any directory.
2. In the directory where you put these Web proxy files, set a case-sensitive
environment variable which points to the JRE’s base directory. For example:
export JAVA_HOME=/opt/java1.2/jre
3. In the same directory where the Web proxy files are located and where you set
the environment variable, type:
Setup
Note: If you receive the message, Execute permission denied, change the file
permissions.
The Web proxy install wizard appears. Enter the information as requested:
v Enter the Web server cgi-bin path and the Web server HTML path you wrote
down in “Prerequisites” on page 69.
v You will be asked for the ID and password of the IBM Tivoli Storage
Manager administrator that is dedicated to the Web proxy. For security
reasons, you should not grant this administrator any authority. You can
register this administrator before or after you configure the Web proxy. See
“Setting Up the IBM Tivoli Storage Manager Server” on page 70.
v If the Web proxy will be serving only one IBM Tivoli Storage Manager
server, it is recommended that you specify as a default the TCP/IP address
and port number of that server. If the Web proxy will serve an Enterprise
Administration server network, consider specifying the TCP/IP address and
port number of the configuration manager as the default.
v Make note of the CGI url that you enter, or make note of the default that you
take. You will need this later to use the Web proxy. For example:
http://web/cgi-bin/dsmproxy
Appendix E. Setting Up the Secure Web Administrator Proxy
71
Note: The cgi-bin and html directories can be mapped to other locations by
using symbolic links. The Web proxy will resolve the symbolic links.
4. The wizard now installs the Web proxy files and completes.
Using the Secure Web Administrator Proxy
1. These next steps to verify if the web proxy was installed correctly depend on
the web server being started. To start your web server, consult the
documentation that came with the server for more information.
2. Bring up your Web browser.
3. Invoke the proxy by entering the URL that you specified to the wizard. For
example:
http://web/cgi-bin/dsmproxy
If you have set the high and low level server addresses (see step 2 on page 71),
the login screen of the administrative Web interface is displayed. If you have
not specified the addresses, a form is displayed asking for a location.
Note: If you get a Web server error: A network error occurred: unable to connect to
server, one reason may be that your Web server has not been started. Go
to the bin directory of your Web server using the following commands:
On UNIX :
/opt/webserver/bin
then type:
webserverctl start
4. Log into your IBM Tivoli Storage Manager with a regular administrative Web
interface (not the proxy administrative interface).
Moving to Another IBM Tivoli Storage Manager Server While Using the
Web Proxy
1. Make sure the other server is prepared for the Web proxy (see “Setting Up the
IBM Tivoli Storage Manager Server” on page 70.)
2. Add ?jump at the end of the CGI URL.
http://web/cgi-bin/dsmproxy?jump
3. Enter the TCP/IP address and port.
Uninstalling the Secure Web Administrator Proxy
The Web proxy installation puts the uninstall wizard in the same directory as the
support file.
To start the uninstall wizard, enter the following case-sensitive command:
Uninstall
If you issue this command from the tivoli/tsm/swap/ directory, the wizard begins
removing the files. If you issue this command from any other directory, the wizard
72
IBM Tivoli Storage Manager for Linux: Quick Start
prompts you for the location of your HTML directory. The wizard then determines
what files were installed and how the Web proxy should be removed.
Troubleshooting the Secure Web Administrator Proxy
v Broken images appear, or requests for help files return a page that states that
the page was not found.
1. Check the permission of the files. The default permission on UNIX is 644,
which gives to the owner read-write authority and to all others read-only
authority. Your file permissions should be set at the default 644.
2. Check the Web server error log and verify that the file location is correct. If
the file is not at that location, consider adding an Alias to your Web server
configuration file. For example, on the Web server the tivoli/tsm/swap/
directory is in /www/tivoli/tsm/swap/. You could fix the problem by adding the
following line to httpd.conf:
Alias /StorageFiles "/www/StorageFiles"
v An initial request returns two errors stating that the Web proxy had an error
while connecting to xxx: On your IBM Tivoli Storage Manager console set the
server high level and low level addresses. See step 2 on page 71.
v The Web proxy states that the password or ID is invalid: Verify that the Web
proxy administrator’s ID and password have been set on the server. You can
update the password on the Web proxy using the ?configure option. To use this
option, append ?configure to the end of the dsmproxy URL. For example:
http://webserver.tucson.ibm.com/cgi-bin/dsmproxy?configure
v ?configure or the Web administrative interface links do not work: Set the
proxy’s CGI URL to your Web server’s CGI URL. For example:
dsmproxy -cgiURL=http://webserver.tucson.ibm.com/cgi-bin
v To get to a server other than the default server: Append ?jump to the URL. For
example:
http://webserver.tucson.ibm.com/cgi-bin/dsmproxy?jump
v The Web proxy states that the administrator ID is locked: Unlock the
administrator’s ID using the UNLOCK ADMIN command.
v The Web proxy reports an internal error: To turn on tracing on the Web proxy,
do one of the following:
– Append the FORCETRACE option to the Web request. For example, here is a
sample Web request:
http://webserver.tucson.ibm.com/cgi-bin/dsmproxy?SERVER=tsm:1500&URL=1500
To turn tracing on for this request enter FORCETRACE before the server:
http://webserver.tucson.ibm.com/cgi-bin/dsmproxy?FORCETRACE&SERVER=tsm:1500&URL=1500
The trace information will be placed into a file named proxytrace.txt, which is
located in cgi-bin directory of the Web server.
– From the command line, issue the following command in the Web server
cgi-bin directory where the dsmproxy was installed:
dsmproxy -trace=proxytrc.txt
The proxy would then append trace information to the proxytrc.txt file. The
trace file name can be any name you choose.
v ?configure reports an error when updating the configuration through the Web:
This problem typically occurs on UNIX systems due to file permission errors. On
Appendix E. Setting Up the Secure Web Administrator Proxy
73
UNIX , update the permissions of the file, /etc/dsmproxy.cfg. On Windows NT® or
Windows 2000, the options are stored in the registry.
74
IBM Tivoli Storage Manager for Linux: Quick Start
Appendix F. Where to Look for Information
This appendix describes the service that IBM® provides for IBM Tivoli Storage
Manager and tells you where to look for more information about IBM Tivoli
Storage Manager.
Contacting Customer Support
|
|
For support for this or any Tivoli product, you can contact IBM Customer Support
in one of the following ways:
v Visit the Tivoli Storage Manager technical support Web site at
www.ibm.com/software/sysmgmt/products/
support/IBMTivoliStorageManager.html.
v Submit a problem management record (PMR) electronically at
IBMSERV/IBMLINK. You can access IBMLINK at www.ibm.com/ibmlink/.
v Submit a problem management record (PMR) electronically at
www.ibm.com/software/support/probsub.html.
Customers in the United States can also call 1-800-IBM-SERV (1-800-426-7378).
International customers should consult the Web site for customer support
telephone numbers.
Hearing-impaired customers should visit the TDD/TTY Voice Relay Services and
Accessiblity Center Web site at www.ibm.com/able/voicerelay.html.
You can also review the IBM Software Support Guide, which is available on our Web
site at techsupport.services.ibm.com/guides/handbook.html.
When you contact IBM Software Support, be prepared to provide identification
information for your company so that support personnel can readily assist you.
Company identification information is needed to register for online support
available on the Web site.
The support Web site offers extensive information, including a guide to support
services (IBM Software Support Guide); frequently asked questions (FAQs); and
documentation for all IBM Software products, including Release Notes,
Redbooks™, and white papers, defects (APARs), and solutions. The documentation
for some product releases is available in both PDF and HTML formats. Translated
documents are also available for some product releases.
All Tivoli publications are available for electronic download or order from the IBM
Publications Center:www.ibm.com/shop/publications/order/
We are very interested in hearing about your experience with Tivoli products and
documentation. We also welcome your suggestions for improvements. If you have
comments or suggestions about our documentation, please complete our customer
feedback survey at www.ibm.com/software/sysmgmt/products/
support/IBMTivoliStorageManager.html by selecting the Feedback link in the left
navigation bar.
© Copyright IBM Corp. 2002, 2003
75
Reporting a Problem
Please have the following information ready when you report a problem:
v The Tivoli Storage Manager server version, release, modification, and service
level number. You can get this information by entering the QUERY STATUS
command at the Tivoli Storage Manager command line.
v The Tivoli Storage Manager client version, release, modification, and service
level number. You can get this information by entering dsmc at the command
line.
v The communication protocol (for example, TCP/IP), version, and release number
you are using.
v The activity you were doing when the problem occurred, listing the steps you
followed before the problem occurred.
v The exact text of any error messages.
Internet
You can get additional information through an anonymous FTP server,
ftp://ftp.software.ibm.com. IBM Tivoli Storage Manager information is in the
/storage/tivoli-storage-management directory.
A newsgroup, listserv@marist.edu, is implemented by a third party. IBM supports
this newsgroup on a best-effort basis only.
IBM Tivoli Storage Manager Publications
The following table lists Tivoli Storage Manager server publications.
Publication Title
Order Number
IBM Tivoli Storage Management Products License Information
GH09-4572
IBM Tivoli Storage Manager Messages
GC32-0767
IBM Tivoli Storage Manager for Linux Administrator’s Guide
GC23-4690
IBM Tivoli Storage Manager for Linux Administrator’s Reference
GC23-4691
IBM Tivoli Storage Manager for Linux Quick Start
GC23-4692
The following table lists Tivoli Storage Manager storage agent publications.
Publication Title
Order Number
IBM Tivoli Storage Manager for AIX Storage Agent User’s Guide
GC32-0771
IBM Tivoli Storage Manager for HP-UX Storage Agent User’s Guide
GC32-0727
IBM Tivoli Storage Manager for Linux Storage Agent User’s Guide
GC23-4693
IBM Tivoli Storage Manager for Sun Solaris Storage Agent User’s Guide
GC32-0781
IBM Tivoli Storage Manager for Windows Storage Agent User’s Guide
GC32-0785
The following table lists Tivoli Storage Manager client publications.
Publication Title
Order Number
IBM Tivoli Storage Manager for Space Management for UNIX: Using the GC32-0794
Hierarchical Storage Management Clients
76
IBM Tivoli Storage Manager for Linux: Quick Start
Publication Title
Order Number
IBM Tivoli Storage Manager for Macintosh: Backup-Archive Clients
Installation and User’s Guide
GC32-0787
IBM Tivoli Storage Manager for NetWare: Backup-Archive Clients
Installation and User’s Guide
GC32-0786
IBM Tivoli Storage Manager for UNIX: Backup-Archive Clients
Installation and User’s Guide
GC32-0789
IBM Tivoli Storage Manager for Windows: Backup-Archive Clients
Installation and User’s Guide
GC32-0788
IBM Tivoli Storage Manager Using the Application Program Interface
GC32-0793
The following table lists publications for application protection products.
Order
Number
Publication Title
IBM Tivoli Storage Manager for Application Servers: Data Protection for
WebSphere Application Server Installation and User’s Guide
SC32-9075
IBM Tivoli Storage Manager for Databases: Data Protection for Microsoft SQL
Server Installation and User’s Guide
SC32-9059
IBM Tivoli Storage Manager for Databases: Data Protection for Oracle for UNIX
Installation and User’s Guide
SC32-9064
IBM Tivoli Storage Manager for Databases: Data Protection for Oracle for
Windows Installation and User’s Guide
SC32-9065
IBM Tivoli Storage Manager for Databases: Data Protection for Informix
Installation and User’s Guide
SH26-4095
IBM Tivoli Storage Manager for Enterprise Resource Planning: Data Protection for SC33-6341
R/3 Installation and User’s Guide for DB2 UDB
IBM Tivoli Storage Manager for Enterprise Resource Planning: Data Protection for SC33-6340
R/3 Installation and User’s Guide for Oracle
IBM Tivoli Storage Manager for Hardware: Data Protection for EMC Symmetrix
for R/3 Installation and User’s Guide
SC33-6386
IBM Tivoli Storage Manager for Hardware: Data Protection for Enterprise Storage
Server Databases (DB2 UDB) Installation and User’s Guide
SC32-9060
IBM Tivoli Storage Manager for Hardware: Data Protection for Enterprise Storage
Server Databases (Oracle) Installation and User’s Guide
SC32-9061
IBM Tivoli Storage Manager for Hardware: Data Protection for IBM ESS for R/3
Installation and User’s Guide for DB2 UDB
SC33-8204
IBM Tivoli Storage Manager for Hardware: Data Protection for IBM ESS for R/3
Installation and User’s Guide for Oracle
SC33-8205
IBM Tivoli Storage Manager for Mail: Data Protection for Lotus Domino for
UNIX and OS/400 Installation and User’s Guide
SC32-9056
IBM Tivoli Storage Manager for Mail: Data Protection for Lotus Domino for
Windows Installation
SC32-9057
IBM Tivoli Storage Manager for Mail: Data Protection for Lotus Domino, S/390
Edition Licensed Program Specifications
GC26-7305
IBM Tivoli Storage Manager for Mail: Data Protection for Microsoft Exchange
Server Installation and User’s Guide
SC32-9058
Appendix F. Where to Look for Information
77
IBM Redbooks
The International Technical Support Center (ITSC) publishes redbooks, which are
books on specialized topics, such as Using Tivoli Storage Manager to Back Up
Databases. You can order publications through your IBM representative or the IBM
branch office serving your locality. You can also search for and order books of
interest to you by visiting the IBM Redbooks home page on the World Wide Web
at this address: http://www.redbooks.ibm.com.
Translations
Selected Tivoli Storage Manager publications have been translated into languages
other than American English. Contact your IBM representative for more
information about the translated publications and the availability of these
translations in your country.
78
IBM Tivoli Storage Manager for Linux: Quick Start
Appendix G. Notices
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in
other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user’s responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not give you
any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM
Intellectual Property Department in your country or send inquiries, in writing, to:
IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan
The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or
implied warranties in certain transactions, therefore, this statement may not apply
to you.
This information could include technical inaccuracies or typographical errors.
Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those Web
sites. The materials at those Web sites are not part of the materials for this IBM
product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.
© Copyright IBM Corp. 2002, 2003
79
Licensees of this program who wish to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact:
IBM Corporation
Information Enabling Requests
Dept. M13
5600 Cottle Road
San Jose CA 95193-0001
U.S.A.
Such information may be available, subject to appropriate terms and conditions,
including in some cases, payment of a fee.
The licensed program described in this information and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Program License Agreement, or any equivalent agreement
between us.
Information concerning non-IBM products was obtained from the suppliers of
those products, their published announcements or other publicly available sources.
IBM has not tested those products and cannot confirm the accuracy of
performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products.
This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include the
names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.
If you are viewing this information softcopy, the photographs and color
illustrations may not appear.
80
IBM Tivoli Storage Manager for Linux: Quick Start
Trademarks
The following terms are trademarks of the International Business Machines
Corporation in the United States, other countries, or both:
Advanced Peer-to-Peer Networking
AIX
Application System/400
APPN
DB2
DFDSM
DFS
DFSMS/MVS
DFSMShsm
DFSMSrmm
DPI
Enterprise Storage Server
ESCON
Extended Services
FlashCopy
IBM
IBMLink
iSeries
Magstar
MVS
MVS/ESA
MVS/SP
NetView
OpenEdition
Operating System/2
Operating System/400
OS/2
OS/390
OS/400
POWERparallel
PowerPC
pSeries
RACF
Redbooks
RISC System/6000
RS/6000
SAA
SANergy
SP
System/370
System/390
SystemView
Tivoli
Tivoli Enterprise Console
Tivoli Management Environment
TotalStorage
TME
VTAM
xSeries
z/OS
zSeries
Lotus, Lotus 1–2–3, Lotus Approach®, Lotus Domino™ and Lotus Notes™ are
trademarks of Lotus Development Corporation in the United States, other
countries, or both.
Microsoft®, Windows, Windows NT, and the Windows logo are registered
trademarks of Microsoft Corporation in the United States, other countries, or both.
UNIX is a registered trademark of the Open Group in the United States, other
countries, or both.
Java and all Java-based trademarks and logos are trademarks of Sun Microsystems,
Inc. in the United States, other countries, or both.
Intel is a registered trademark of the Intel Corporation in the United States, other
countries, or both.
Other company, product, or service names may be trademarks or service marks of
others.
Appendix G. Notices
81
82
IBM Tivoli Storage Manager for Linux: Quick Start
Glossary
The terms in this glossary are defined as they
pertain to the IBM Tivoli Storage Manager library.
If you do not find the term you need, refer to the
IBM Software Glossary on the Web at this
address: www.ibm.com/ibm/terminology/. You
can also refer to IBM Dictionary of Computing,
New York: McGraw-Hill, 1994.
This glossary may include terms and definitions
from:
v The American National Standard Dictionary for
Information Systems, ANSI X3.172-1990,
copyright (ANSI). Copies may be purchased
from the American National Standards
Institute, 11 West 42nd Street, New York 10036.
v The Information Technology Vocabulary,
developed by Subcommittee 1, Joint Technical
Committee 1, of the International Organization
for Standardization and the International
Electrotechnical Commission (ISO/IEC
JTC2/SC1).
A
absolute mode. A backup copy group mode that
specifies that a file is considered for incremental
backup even if the file has not changed since the last
backup. See also mode. Contrast with modified mode.
access mode. An attribute of a storage pool or a
storage volume that specifies whether the server can
write to or read from the storage pool or storage
volume. The access mode can be read/write, read-only,
or unavailable. Volumes in primary storage pools can
also have an access mode of destroyed. Volumes in
copy storage pools can also have an access mode of
offsite.
activate. To validate the contents of a policy set and
make it the active policy set.
active policy set. The activated policy set that contains
the policy rules currently in use by all client nodes
assigned to the policy domain. See also policy domain
and policy set.
active version. The most recent backup copy of a file
stored by IBM Tivoli Storage Manager. The active
version of a file cannot be deleted until a backup
process detects that the user has either replaced the file
with a newer version or has deleted the file from the
workstation. Contrast with inactive version.
© Copyright IBM Corp. 2002, 2003
activity log. A log that records normal activity
messages generated by the server. These messages
include information about server and client operations,
such as the start time of sessions or device I/O errors.
Each message includes a message ID, date and time
stamp, and a text description. The number of days to
retain messages in the activity log can be specified.
administrative client. A program that runs on a file
server, workstation, or mainframe that administrators
use to control and monitor the IBM Tivoli Storage
Manager server. Contrast with backup-archive client.
administrative command schedule. A database record
that describes the planned processing of an
administrative command during a specific time period.
See also client schedule.
administrative privilege class. See privilege class.
administrative session. A period of time in which an
administrator user ID communicates with a server to
perform administrative tasks. Contrast with client node
session.
administrator. A user who has been registered to the
server. Administrators can be authorized to one or
more of the following administrative privilege classes:
system, policy, storage, operator, or analyst.
Administrators can use the administrative commands
and queries allowed by their privileges.
aggregate file. A file, stored in one or more storage
pools, consisting of a group of logical files packaged
together. See logical file and physical file.
analyst privilege class. A privilege class that allows
an administrator to reset statistics. See also privilege
class.
application client. One of the IBM Tivoli Storage
Manager data protection programs installed on a
system to protect an application. The IBM Tivoli
Storage Manager server provides backup services to an
application client.
archive. To copy one or more files to a storage pool
for long-term storage. Archived files can include
descriptive information and can be retrieved by archive
date, by file name, or by description. Contrast with
retrieve.
archive copy. A file that has been archived to server
storage.
archive copy group. A policy object containing
attributes that control the generation, destination, and
83
expiration of archived files. An archive copy group
belongs to a management class.
archive retention grace period. The number of days
that IBM Tivoli Storage Manager retains an archived
file when the server is unable to rebind the file to an
appropriate management class.
assigned capacity. The portion of available space that
can be used to store database or recovery log
information. See also available space.
association. (1) The defined relationship between a
client node and a client schedule. An association
identifies the name of a schedule, the name of the
policy domain to which the schedule belongs, and the
name of a client node that performs scheduled
operations. (2) On a configuration manager, the defined
relationship between a profile and an object such as a
policy domain. Profile associations define the
configuration information that will be distributed to a
managed server when it subscribes to the profile.
audit. To check for logical inconsistencies between
information that the server has and the actual condition
of the system. IBM Tivoli Storage Manager can audit
volumes, the database, libraries, and licenses. For
example, when IBM Tivoli Storage Manager audits a
volume, the server checks for inconsistencies between
information about backed-up or archived files stored in
the database and the actual data associated with each
backup version or archive copy in server storage.
authentication. The process of checking a user’s
password before allowing that user access to the server.
Authentication can be turned on or off by an
administrator with system privilege.
authority. The right granted to a user to perform tasks
with IBM Tivoli Storage Manager servers and clients.
See also privilege class.
autochanger. A small, multislot tape device that
automatically puts tape cartridges into tape drives. See
also library.
available space. The amount of space, in megabytes,
that is available to the database or the recovery log.
This space can be used to extend the capacity of the
database or the recovery log, or to provide sufficient
free space before a volume is deleted from the database
or the recovery log.
B
back up. To copy information to another location to
ensure against loss of data. In IBM Tivoli Storage
Manager, you can back up user files, the IBM Tivoli
Storage Manager database, and storage pools. Contrast
with restore. See also database backup series and
incremental backup.
84
IBM Tivoli Storage Manager for Linux: Quick Start
backup-archive client. A program that runs on a
workstation or file server and provides a means for
users to back up, archive, restore, and retrieve files.
Contrast with administrative client.
backup copy group. A policy object containing
attributes that control the generation, destination, and
expiration of backup versions of files. A backup copy
group belongs to a management class.
backup retention grace period. The number of days
that IBM Tivoli Storage Manager retains a backup
version after the server is unable to rebind the file to an
appropriate management class.
backup set. A portable, consolidated group of active
backup versions of files, generated for a backup-archive
client.
backup version. A file that a user backed up to server
storage. More than one backup version of a file can
exist in server storage, but only one backup version is
the active version. See also active version and inactive
version.
binding. The process of associating a file with a
management class name. See rebinding.
buffer pool. Temporary space used by the server to
hold database or recovery log pages. See database buffer
pool and recovery log buffer pool.
C
cache. The process of leaving a duplicate copy on
random access media when the server migrates a file to
another storage pool in the hierarchy.
central scheduler. A function that allows an
administrator to schedule client operations and
administrative commands. The operations can be
scheduled to occur periodically or on a specific date.
See client schedule and administrative command schedule.
client. A program running on a PC, workstation, file
server, LAN server, or mainframe that requests services
of another program, called the server. The following
types of clients can obtain services from an IBM Tivoli
Storage Manager server: administrative client,
application client, API client, backup-archive client, and
HSM client (also known as Tivoli Storage Manager for
Space Management).
client domain. The set of drives, file systems, or
volumes that the user selects to back up or archive
using the backup-archive client.
client migration. The process of copying a file from a
client node to server storage and replacing the file with
a stub file on the client node. The space management
attributes in the management class control this
migration. See also space management.
client node. A file server or workstation on which the
backup-archive client program has been installed, and
which has been registered to the server.
client node session. A period of time in which a client
node communicates with a server to perform backup,
restore, archive, retrieve, migrate, or recall requests.
Contrast with administrative session.
client options file. A file that a client can change,
containing a set of processing options that identify the
server, communication method, and options for backup,
archive, hierarchical storage management, and
scheduling. Also called the dsm.opt file.
client-polling scheduling mode. A client/server
communication technique where the client queries the
server for work. Contrast with server-prompted
scheduling mode.
client schedule. A database record that describes the
planned processing of a client operation during a
specific time period. The client operation can be a
backup, archive, restore, or retrieve operation, a client
operating system command, or a macro. See also
administrative command schedule.
client system options file. A file, used on UNIX
clients, containing a set of processing options that
identify the IBM Tivoli Storage Manager servers to be
contacted for services. This file also specifies
communication methods and options for backup,
archive, hierarchical storage management, and
scheduling. Also called the dsm.sys file. See also client
user options file.
client user options file. A user-created file, used on
UNIX clients, containing a set of processing options
that identify the server, communication method,
backup and archive options, space management
options, and scheduling options. Also called the dsm.opt
file. See also client system options file.
closed registration. A registration process in which
only an administrator can register workstations as
client nodes with the server. Contrast with open
registration.
collocation. The process of keeping all data belonging
to a single client node or a single client file space on a
minimal number of sequential-access volumes within a
storage pool. Collocation can reduce the number of
volumes that must be accessed when a large amount of
data must be restored.
compression. The process of saving storage space by
eliminating empty fields or unnecessary data in a file.
In IBM Tivoli Storage Manager, compression can occur
at a workstation before files are backed up or archived
to server storage. On some types of tape drives,
hardware compression can be used.
configuration manager. One IBM Tivoli Storage
Manager server that distributes configuration
information to other IBM Tivoli Storage Manager
servers (called managed servers) via profiles.
Configuration information can include policy and
schedules. See managed server and profile.
copy group. A policy object whose attributes control
how backup versions or archive copies are generated,
where backup versions or archive copies are initially
located, and when backup versions or archive copies
expire. A copy group belongs to a management class.
See also archive copy group, backup copy group, backup
version, and management class.
copy storage pool. A named set of volumes that
contains copies of files that reside in primary storage
pools. Copy storage pools are used only to back up the
data stored in primary storage pools. A copy storage
pool cannot be a destination for a backup copy group,
an archive copy group, or a management class (for
space-managed files). See primary storage pool and
destination.
D
damaged file. A physical file for which IBM Tivoli
Storage Manager has detected read errors.
database. A collection of information about all objects
managed by the server, including policy management
objects, users and administrators, and client nodes.
database backup series. One full backup of the
database, plus up to 32 incremental backups made
since that full backup. Each full backup that is run
starts a new database backup series. A backup series is
identified with a number.
database backup trigger. A set of criteria that defines
when and how database backups are run automatically.
The criteria determine how often the backup is run,
whether the backup is a full or incremental backup,
and where the backup is stored.
database buffer pool. Storage that is used as a cache
to allow database pages to remain in memory for long
periods of time, so that the server can make continuous
updates to pages without requiring input or output
(I/O) operations from external storage.
database snapshot. A complete backup of the entire
IBM Tivoli Storage Manager database to media that can
be taken off-site. When a database snapshot is created,
the current database backup series is not interrupted. A
database snapshot cannot have incremental database
backups associated with it. See also database backup
series. Contrast with full backup.
data mover. A device, defined to IBM Tivoli Storage
Manager, that moves data on behalf of the server. A
NAS file server can be a data mover.
Glossary
85
default management class. A management class
assigned to a policy set that the server uses to manage
backed-up or archived files when a user does not
specify a management class for a file.
E
desktop client. The group of backup-archive clients
supported by IBM Tivoli Storage Manager that includes
clients on Windows, Apple, and Novell NetWare
operating systems.
enterprise configuration. A method of setting up IBM
Tivoli Storage Manager servers so that the
administrator can distribute the configuration of one of
the servers to the other servers, using server-to-server
communication. See configuration manager, managed
server, profile, and subscription.
destination. A copy group or management class
attribute that specifies the primary storage pool to
which a client file will be backed up, archived, or
migrated.
enterprise logging. The sending of events from IBM
Tivoli Storage Manager servers to a designated event
server. The event server routes the events to designated
receivers, such as to a user exit. See also event.
device class. A named set of characteristics applied to
a group of storage devices. Each device class has a
unique name and represents a device type of disk, file,
optical disk, or tape.
estimated capacity. The available space, in megabytes,
of a storage pool.
device configuration file. A file that contains
information about defined device classes, and, on some
IBM Tivoli Storage Manager servers, defined libraries
and drives. The file can be created by using an IBM
Tivoli Storage Manager administrative command or by
using an option in the server options file. The
information is a copy of the device configuration
information in the IBM Tivoli Storage Manager
database.
disaster recovery manager (DRM). A function in IBM
Tivoli Storage Manager that assists in preparing and
later using a disaster recovery plan file for the IBM
Tivoli Storage Manager server.
disaster recovery plan. A file created by disaster
recovery manager (DRM) that contains information
about how to recover computer systems if a disaster
occurs and scripts that can be run to perform some
recovery tasks. The file includes information about the
software and hardware used by the IBM Tivoli Storage
Manager server, and the location of recovery media.
domain. See policy domain or client domain.
DRM. A short name for disaster recovery manager.
dsm.opt file. See client options file and client user
options file.
dsmserv.opt. See server options file.
dsm.sys file. See client system options file.
dynamic. A value for serialization that specifies that
IBM Tivoli Storage Manager accepts the first attempt to
back up or archive a file regardless of whether the file
is modified during the backup or archive process. See
also serialization. Contrast with shared dynamic, shared
static, and static.
event. (1) An administrative command or a client
operation that is scheduled to be run using IBM Tivoli
Storage Manager scheduling. (2) A message that an
IBM Tivoli Storage Manager server or client issues.
Messages can be logged using IBM Tivoli Storage
Manager event logging.
event record. A database record that describes actual
status and results for events.
event server. A server to which other servers can send
events for logging. The event server routes the events
to any receivers that are enabled for the sending
server’s events.
exclude. To identify files that you do not want to
include in a specific client operation, such as backup or
archive. You identify the files in an include-exclude list.
exclude-include list. See include-exclude list.
expiration. The process by which files are identified
for deletion because their expiration date or retention
period has passed. Backed-up or archived files are
marked expired by IBM Tivoli Storage Manager based
on the criteria defined in the backup or archive copy
group.
expiration date. On some IBM Tivoli Storage Manager
servers, a device class attribute used to notify tape
management systems of the date when IBM Tivoli
Storage Manager no longer needs a tape volume. The
date is placed in the tape label so that the tape
management system does not overwrite the
information on the tape volume before the expiration
date.
export. To copy administrator definitions, client node
definitions, policy definitions, server control
information, or file data to external media, or directly
to another server. Used to move or copy information
between servers.
extend. To increase the portion of available space that
can be used to store database or recovery log
information. Contrast with reduce.
86
IBM Tivoli Storage Manager for Linux: Quick Start
F
file space. A logical space in IBM Tivoli Storage
Manager server storage that contains a group of files.
For clients on Windows systems, a file space is a logical
partition that is identified by a volume label. For clients
on UNIX systems, a file space is a logical space that
contains a group of files backed up or archived from
the same file system, or part of a file system that stems
from a virtual mount point. Clients can restore, retrieve,
or delete their file spaces from IBM Tivoli Storage
Manager server storage. IBM Tivoli Storage Manager
does not necessarily store all the files from a single file
space together, but can identify all the files in server
storage that came from a single file space.
file space ID (FSID). A unique numeric identifier that
the server assigns to a file space when it is stored in
server storage.
frequency. A copy group attribute that specifies the
minimum interval, in days, between incremental
backups.
FSID. See file space ID.
full backup. The process of backing up the entire
server database. A full backup begins a new database
backup series. See also database backup series and
incremental backup. Contrast with database snapshot.
fuzzy copy. A backup version or archive copy of a file
that might not accurately reflect the original content of
the file because IBM Tivoli Storage Manager backed up
or archived the file while the file was being modified.
H
hierarchical storage management (HSM) client. The
Tivoli Storage Manager for Space Management program
that runs on workstations to allow users to maintain
free space on their workstations by migrating and
recalling files to and from IBM Tivoli Storage Manager
storage. Synonymous with space manager client.
high migration threshold. A percentage of the storage
pool capacity that identifies when the server can start
migrating files to the next available storage pool in the
hierarchy. Contrast with low migration threshold. See
server migration.
HSM client. Hierarchical storage management client.
Also known as the space manager client.
I
IBM Tivoli Storage Manager command script. A
sequence of IBM Tivoli Storage Manager administrative
commands that are stored in the database of the IBM
Tivoli Storage Manager server. You can run the script
from any interface to the server. The script can include
substitution for command parameters and conditional
logic.
image backup. A backup of a full file system or raw
logical volume as a single object.
import. The process of copying exported administrator
definitions, client node definitions, policy definitions,
server control information or file data from external
media to a target server. A subset of information can be
imported to a target server from the external media.
Used to move or copy information between servers. See
export.
inactive version. A backup version of a file that is
either not the most recent backup version or that is a
backup version of a file that no longer exists on the
client system. Inactive backup versions are eligible for
expiration processing according to the management
class assigned to the file. Contrast with active version.
include-exclude file. A file containing statements that
IBM Tivoli Storage Manager uses to determine whether
to include certain files in specific client operations, and
to determine the associated management classes to use
for backup, archive, and space management. See
include-exclude list.
include-exclude list. A group of include and exclude
option statements that IBM Tivoli Storage Manager
uses. The exclude options identify files that are not to
be included in specific client operations such as backup
or space management. The include options identify files
that are exempt from the exclusion rules. The include
options can also assign a management class to a file or
group of files for backup, archive, or space
management services. The include-exclude list for a
client may include option statements from the client
options file, from separate include-exclude files, and
from a client option set on the server.
incremental backup. (1) The process of backing up
files or directories that are new or have changed since
the last incremental backup. See also selective backup. (2)
The process of copying only the pages in the database
that are new or changed since the last full or
incremental backup of the database. Contrast with full
backup. See also database backup series.
L
LAN-free data transfer. The movement of client data
directly between a client and a storage device over a
SAN, rather than over the LAN.
library. (1) A repository for demountable recorded
media, such as magnetic tapes. (2) For IBM Tivoli
Storage Manager, a collection of one or more drives,
and possibly robotic devices (depending on the library
type), which can be used to access storage volumes. (3)
In the AS/400® system, a system object that serves as a
Glossary
87
directory to other objects. A library groups related
objects, and allows the user to find objects by name.
definitions of objects such as policy and schedules. See
configuration manager, subscription, and profile.
library client. An IBM Tivoli Storage Manager server
that uses server-to-server communication to access a
library that is managed by another IBM Tivoli Storage
Manager server. See also library manager.
managed system. A client or server that requests
services from the IBM Tivoli Storage Manager server.
library manager. An IBM Tivoli Storage Manager
server that controls device operations when multiple
IBM Tivoli Storage Manager servers share a storage
device. The device operations include mount,
dismount, volume ownership, and library inventory.
See also library client.
logical file. A file stored in one or more server storage
pools, either by itself or as part of an aggregate file. See
also aggregate file and physical file.
logical occupancy. The amount of space used by
logical files in a storage pool. This space does not
include the unused space created when logical files are
deleted from aggregate files, so it might be less than
the physical occupancy. See also physical occupancy,
physical file, and logical file.
management class. A policy object that users can bind
to each file to specify how the server manages the file.
The management class can contain a backup copy
group, an archive copy group, and space management
attributes. The copy groups determine how the server
manages backup versions or archive copies of the file.
The space management attributes determine whether
the file is eligible to be migrated by the space manager
client to server storage and under what conditions the
file is migrated. See also copy group, space manager client,
binding, and rebinding.
maximum extension. Specifies the maximum amount
of storage space, in megabytes, that you can extend the
database or the recovery log.
maximum reduction. Specifies the maximum amount
of storage space, in megabytes, that you can reduce the
database or the recovery log.
logical volume. (1) A portion of a physical volume
that contains a file system. (2) For the IBM Tivoli
Storage Manager server, the combined space on all
volumes for either the database or the recovery log.
The database is one logical volume, and the recovery
log is one logical volume.
maximum utilization. The highest percentage of
assigned capacity used by the database or the recovery
log.
low migration threshold. A percentage of the storage
pool capacity that specifies when the server can stop
the migration of files to the next storage pool. Contrast
with high migration threshold. See server migration.
mirroring. The process of writing the same data to
multiple disks at the same time. Mirroring data protects
against data loss within the database or the recovery
log.
M
macro file. A file that contains one or more IBM Tivoli
Storage Manager administrative commands, which can
be run only from an administrative client by using the
MACRO command. Contrast with IBM Tivoli Storage
Manager command script.
managed object. A definition in the database of a
managed server that was distributed to the managed
server by a configuration manager. When a managed
server subscribes to a profile, all objects associated with
that profile become managed objects in the database of
the managed server. In general, a managed object
cannot be modified locally on the managed server.
Objects can include policy, schedules, client options
sets, server scripts, administrator registrations, and
server and server group definitions.
managed server. An IBM Tivoli Storage Manager
server that receives configuration information from a
configuration manager via subscription to one or more
profiles. Configuration information can include
88
IBM Tivoli Storage Manager for Linux: Quick Start
migrate. To move data from one storage location to
another. See also client migration and server migration.
mode. A copy group attribute that specifies whether
to back up a file that has not been modified since the
last time the file was backed up. See modified and
absolute.
modified mode. A backup copy group mode that
specifies that a file is considered for incremental
backup only if it has changed since the last backup. A
file is considered changed if the date, size, owner, or
permissions have changed. See also mode. Contrast with
absolute mode.
mount. To place a data medium (such as a tape
cartridge) on a drive in a position to operate.
mount limit. A device class attribute that specifies the
maximum number of volumes that can be
simultaneously accessed from the same device class.
The mount limit determines the maximum number of
mount points. See mount point.
mount point. A logical drive through which the server
accesses volumes in a sequential access device class.
For a removable media device such as tape, a mount
point is a logical drive associated with a physical drive.
For a device class with the device type of FILE, a
mount point is a logical drive associated with an I/O
stream. The number of mount points for a device class
is determined by the mount limit for that class. See
mount limit.
mount retention period. A device class attribute that
specifies the maximum number of minutes that the
server retains a mounted sequential access media
volume that is not being used before it dismounts the
sequential access media volume.
mount wait period. A device class attribute that
specifies the maximum number of minutes that the
server waits for a sequential access volume mount
request to be satisfied before canceling the request.
N
NAS. Network-attached storage.
NAS node. An IBM Tivoli Storage Manager node that
is a NAS file server. Data for the NAS node is
transferred by the NAS file server itself at the direction
of an IBM Tivoli Storage Manager server that uses
NDMP. The data is not transferred by the IBM Tivoli
Storage Manager client. Also called NAS file server
node.
native format. A format of data that is written to a
storage pool directly by the IBM Tivoli Storage
Manager server. Contrast with non-native data format.
NDMP. Network Data Management Protocol.
network-attached storage (NAS) file server. A
dedicated storage device with an operating system that
is optimized for file-serving functions. In IBM Tivoli
Storage Manager, a NAS file server can have the
characteristics of both a node and a data mover. See
also data mover and NAS node.
Network Data Management Protocol (NDMP). An
industry-standard protocol that allows a network
storage-management application (such as IBM Tivoli
Storage Manager) to control the backup and recovery of
an NDMP-compliant file server, without installing
third-party software on that file server.
node. (1) A workstation or file server that is registered
with an IBM Tivoli Storage Manager server to receive
its services. See also client node and NAS node. (2) In a
Microsoft cluster configuration, one of the computer
systems that make up the cluster.
node privilege class. A privilege class that allows an
administrator to remotely access backup-archive clients
for a specific client node or for all clients in a policy
domain. See also privilege class.
server uses for basic LAN-based operations. The data is
written by a data mover instead of the server. Storage
pools with data written in a non-native format may not
support some server operations, such as audit of a
volume. The NETAPPDUMP data format for NAS node
backups is an example of a non-native data format.
O
open registration. A registration process in which any
users can register their own workstations as client
nodes with the server. Contrast with closed registration.
operator privilege class. A privilege class that allows
an administrator to issue commands that disable or halt
the server, enable the server, cancel server processes,
and manage removable media. See also privilege class.
P
page. A unit of space allocation within IBM Tivoli
Storage Manager database volumes.
path. An IBM Tivoli Storage Manager object that
defines a one-to-one relationship between a source and
a destination. Using the path, the source accesses the
destination. Data may flow from the source to the
destination, and back. An example of a source is a data
mover (such as a NAS file server), and an example of a
destination is a tape drive.
physical file. A file stored in one or more storage
pools, consisting of either a single logical file, or a
group of logical files packaged together (an aggregate
file). See also aggregate file and logical file.
physical occupancy. The amount of space used by
physical files in a storage pool. This space includes the
unused space created when logical files are deleted
from aggregates. See also physical file, logical file, and
logical occupancy.
policy domain. A policy object that contains policy
sets, management classes, and copy groups that are
used by a group of client nodes. See policy set,
management class, and copy group.
policy privilege class. A privilege class that allows an
administrator to manage policy objects, register client
nodes, and schedule client operations for client nodes.
Authority can be restricted to certain policy domains.
See also privilege class.
policy set. A policy object that contains a group of
management classes that exist for a policy domain.
Several policy sets can exist within a policy domain but
only one policy set is active at one time. See
management class and active policy set.
non-native data format. A format of data written to a
storage pool that is different from the format that the
Glossary
89
premigration. For a space manager client, the process
of copying files that are eligible for migration to server
storage, while leaving the original file intact on the
local system.
primary storage pool. A named set of volumes that
the server uses to store backup versions of files, archive
copies of files, and files migrated from HSM client
nodes. You can back up a primary storage pool to a
copy storage pool. See destination and copy storage pool.
privilege class. A level of authority granted to an
administrator. The privilege class determines which
administrative tasks the administrator can perform. For
example, an administrator with system privilege class
can perform any administrative task. Also called
administrative privilege class. See also system privilege
class, policy privilege class, storage privilege class, operator
privilege class, analyst privilege class, and node privilege
class.
profile. A named group of configuration information
that can be distributed from a configuration manager
when a managed server subscribes. Configuration
information can include registered administrators,
policy, client schedules, client option sets,
administrative schedules, IBM Tivoli Storage Manager
command scripts, server definitions, and server group
definitions. See configuration manager and managed
server.
R
randomization. The process of distributing schedule
start times for different clients within a specified
percentage of the schedule’s startup window.
rebinding. The process of associating a backed-up file
with a new management class name. For example,
rebinding occurs when the management class
associated with a file is deleted. See binding.
recall. To access files that have been migrated from
workstations to server storage by using the space
manager client. Contrast with migrate.
receiver. A server repository that contains a log of
server messages and client messages as events. For
example, a receiver can be a file exit, a user exit, or the
IBM Tivoli Storage Manager server console and activity
log. See also event.
reclamation. A process of consolidating the remaining
data from many sequential access volumes onto fewer
new sequential access volumes.
reclamation threshold. The percentage of reclaimable
space that a sequential access media volume must have
before the server can reclaim the volume. Space
becomes reclaimable when files are expired or are
deleted. The percentage is set for a storage pool.
90
IBM Tivoli Storage Manager for Linux: Quick Start
recovery log. A log of updates that are about to be
written to the database. The log can be used to recover
from system and media failures.
recovery log buffer pool. Storage that the server uses
to hold new transaction records until they can be
written to the recovery log.
reduce. To free up space from the database or the
recovery log, to allow you to delete a volume. Contrast
with extend.
register. (1) To define a client node or administrator
who can access the server. See registration. (2) To specify
licenses that have been purchased for the server.
registration. The process of identifying a client node
or administrator to the server.
restore. To copy information from its backup location
to the active storage location for use. In IBM Tivoli
Storage Manager, you can restore the server database,
storage pools, storage pool volumes, and users’
backed-up files. The backup version of a file in the
storage pool is not affected by the restore operation.
Contrast with backup.
retention. The amount of time, in days, that inactive
backed-up or archived files are kept in the storage pool
before they are deleted. Copy group attributes and
default retention grace periods for the domain define
retention.
retention period. On an MVS server, a device class
attribute that specifies how long files are retained on
sequential access media. When used, IBM Tivoli
Storage Manager passes this information to the MVS
operating system to ensure that other tape management
systems do not overwrite tape volumes that contain
retained data.
retrieve. To copy archived information from the
storage pool to the workstation for use. The archive
copy in the storage pool is not affected by the retrieve
operation. Contrast with archive.
rollback. To remove changes that were made to
database files since the last commit point.
S
schedule. A database record that describes scheduled
client operations or administrative commands. See
administrative command schedule and client schedule.
scheduling mode. The method of interaction between
a server and a client for running scheduled operations
on the client. IBM Tivoli Storage Manager supports two
scheduling modes for client operations: client-polling
and server-prompted.
scratch volume. A labeled volume that is either blank
or contains no valid data, that is not currently defined
to IBM Tivoli Storage Manager, and that is available for
use.
script. See IBM Tivoli Storage Manager command script.
selective backup. The process of backing up selected
files or directories from a client domain. incremental
backup. See also incremental backup.
serialization. The process of handling files that are
modified during backup or archive processing. See
static, dynamic, shared static, and shared dynamic.
server migration. The process of moving data from
one storage pool to the next storage pool defined in the
hierarchy, based on the migration thresholds defined
for the storage pools. See also high migration threshold
and low migration threshold.
server options file. A file that contains settings that
control various server operations. These settings, or
options, affect such things as communications, devices,
and performance.
server-prompted scheduling mode. A client/server
communication technique where the server contacts the
client when a scheduled operation needs to be done.
Contrast with client-polling scheduling mode.
server storage. The primary and copy storage pools
used by the server to store users’ files: backup versions,
archive copies, and files migrated from space manager
client nodes (space-managed files). See primary storage
pool, copy storage pool, storage pool volume, and volume.
session resource usage. The amount of wait time,
CPU time, and space used or retrieved during a client
session.
shared dynamic. A value for serialization that
specifies that a file must not be backed up or archived
if it is being modified during the operation. IBM Tivoli
Storage Manager retries the backup or archive
operation a number of times; if the file is being
modified during each attempt, IBM Tivoli Storage
Manager will back up or archive the file on its last try.
See also serialization. Contrast with dynamic, shared
static, and static.
shared library. A library device that is shared among
multiple IBM Tivoli Storage Manager servers.
shared static. A value for serialization that specifies
that a file must not be backed up or archived if it is
being modified during the operation. IBM Tivoli
Storage Manager retries the backup or archive
operation a number of times; if the file is being
modified during each attempt, IBM Tivoli Storage
Manager will not back up or archive the file. See also
serialization. Contrast with dynamic, shared dynamic, and
static.
snapshot. See database snapshot.
source server. A server that can send data, in the form
of virtual volumes, to another server. Contrast with target
server.
space-managed file. A file that is migrated from a
client node by the space manager client (HSM client).
The space manager client recalls the file to the client
node on demand.
space management. The process of keeping sufficient
free storage space available on a client node by
migrating files to server storage. The files are migrated
based on criteria defined in management classes to
which the files are bound, and the include-exclude list.
Synonymous with hierarchical storage management. See
also migration.
space manager client. The Tivoli Storage Manager for
Space Management program that enables users to
maintain free space on their workstations by migrating
and recalling files to and from server storage. Also
called hierarchical storage management (HSM) client.
startup window. A time period during which a
schedule must be initiated.
static. A value for serialization that specifies that a file
must not be backed up or archived if it is being
modified during the operation. IBM Tivoli Storage
Manager does not retry the operation. See also
serialization. Contrast with dynamic, shared dynamic, and
shared static.
storage agent. A program that enables IBM Tivoli
Storage Manager to back up and restore client data
directly to and from SAN-attached storage.
storage hierarchy. A logical ordering of primary
storage pools, as defined by an administrator. The
ordering is usually based on the speed and capacity of
the devices that the storage pools use. In IBM Tivoli
Storage Manager, the storage hierarchy is defined by
identifying the next storage pool in a storage pool
definition. See storage pool.
storage pool. A named set of storage volumes that is
the destination that the IBM Tivoli Storage Manager
server uses to store client data. The client data consists
of backup versions, archive copies, and migrated files.
You can back up a primary storage pool to a copy
storage pool. See primary storage pool and copy storage
pool.
storage pool volume. A volume that has been
assigned to a storage pool. See volume, copy storage pool,
and primary storage pool.
storage privilege class. A privilege class that allows
an administrator to control how storage resources for
the server are allocated and used, such as monitoring
Glossary
91
the database, the recovery log, and server storage.
Authority can be restricted to certain storage pools. See
also privilege class.
policy set. For example, the validation process checks
whether the policy set contains a default management
class.
stub file. A file that replaces the original file on a
client node when the file is migrated from the client
node to server storage by Tivoli Storage Manager for
Space Management.
version. A backup copy of a file stored in server
storage. The most recent backup copy of a file is the
active version. Earlier copies of the same file are
inactive versions. The number of versions retained by
the server is determined by the copy group attributes
in the management class.
subscription. The method by which a managed server
requests that it receive configuration information
associated with a particular profile on a configuration
manager. See managed server, configuration manager, and
profile.
system privilege class. A privilege class that allows an
administrator to issue all server commands. See also
privilege class.
T
tape library. A term used to refer to a collection of
drives and tape cartridges. The tape library may be an
automated device that performs tape cartridge mounts
and demounts without operator intervention.
tape volume prefix. A device class attribute that is the
high-level-qualifier of the file name or the data set
name in the standard tape label.
target server. A server that can receive data sent from
another server. Contrast with source server. See also
virtual volumes.
U
UCS-2. An ISO/IEC 10646 encoding form, Universal
Character Set coded in 2 octets. The IBM Tivoli Storage
Manager client on Windows NT and Windows 2000
uses the UCS-2 code page when the client is enabled
for Unicode.
Unicode Standard. 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. It can also support many classical
and historical texts and is continually being expanded.
The Unicode Standard is compatible with ISO/IEC
10646. For more information, see
http://www.unicode.org.
UTF-8. Unicode transformation format - 8. A
byte-oriented encoding form specified by the Unicode
Standard.
V
validate. To check a policy set for conditions that can
cause problems if that policy set becomes the active
92
IBM Tivoli Storage Manager for Linux: Quick Start
virtual volume. An archive file on a target server that
represents a sequential media volume to a source server.
volume. The basic unit of storage for the IBM Tivoli
Storage Manager database, recovery log, and storage
pools. A volume can be an LVM logical volume, a
standard file system file, a tape cartridge, or an optical
cartridge. Each volume is identified by a unique
volume identifier. See database volume, scratch volume,
and storage pool volume.
volume history file. A file that contains information
about: volumes used for database backups and
database dumps; volumes used for export of
administrator, node, policy, or server data; and
sequential access storage pool volumes that have been
added, reused, or deleted. The information is a copy of
the same types of volume information in the IBM Tivoli
Storage Manager database.
Index
A
B
accessibility ix
ACTIVATE POLICYSET command 51
activating
policy set 51
server 25
add a library to the system 43, 44, 45
administrative client
description 4
ending 27
name and password 26
starting 26
Web interface 27, 57
administrative command-line
interface 57
administrative commands
ACTIVATE POLICYSET 51
COPY DOMAIN 50
DEFINE ASSOCIATION 53
DEFINE DEVCLASS 44, 46
DEFINE DRIVE 44, 45
DEFINE LIBRARY 44, 45
DEFINE SCHEDULE 53, 55
DEFINE STGPOOL 44, 46
DEFINE VOLUME 36
EXPIRE INVENTORY 52, 55
HALT 25
QUERY EVENT 54, 55
QUERY STGPOOL 46
REGISTER LICENSE 27
REGISTER NODE 37
UPDATE COPYGROUP 51
UPDATE STGPOOL 49
VALIDATE POLICYSET 51
administrator
granting authority to 37
registering 37
advanced tasks xii
architecture, Tivoli Storage Manager 2
archive
description xi, 1, 25
pool size 36
to tape 38, 49, 50
archive copy group xi, 50
associating
clients with policy domains 50
clients with schedules 53
Atape device driver 41
atldd device driver 41
authority level, administrative
granting 37
autochangers 41
automated tape drive, configuring 39
automating
administrative commands 55
client operations 53
backup
copy group xi, 8, 50, 51
description xi, 1, 7, 10, 25
pool size 36
progressive 7
selective 23
to tape 38, 49, 50
backup-archive client
overview 4
register 37
C
client node, Tivoli Storage Manager
description 4, 25
registration 37
command-line interface, administrative
interactive mode 62
password 26
quitting 62
starting 62
using 62
commands
DSMSERV RUNFILE 27
commands, administrative
ACTIVATE POLICYSET 51
COPY DOMAIN 50
DEFINE ASSOCIATION 53
DEFINE DEVCLASS 44, 46
DEFINE DRIVE 44, 45
DEFINE LIBRARY 44, 45
DEFINE SCHEDULE 53, 55
DEFINE STGPOOL 44, 46
DEFINE VOLUME 36
EXPIRE INVENTORY 52, 55
HALT 25
QUERY EVENT 54, 55
QUERY STGPOOL 46
REGISTER LICENSE 27
REGISTER NODE 37
UPDATE COPYGROUP 51
UPDATE STGPOOL 49
VALIDATE POLICYSET 51
commands, client
QUIT 27
SELECTIVE 23
communication methods
HTTP 32
TCP/IP 31
conventions used in this book ix
COPY DOMAIN command 50
D
data management, overview 6
database
defining 35
overview 2
size 35
© Copyright IBM Corp. 2002, 2003
database (continued)
volumes 35
database volume, defining 35
default
disk storage pool volume 36
management class 50
policy (standard) xi
default installation directories 19
DEFINE ASSOCIATION command 53
DEFINE DEVCLASS command 44, 46
DEFINE DRIVE command 44, 45
DEFINE LIBRARY command 44, 45
define path 43, 45
DEFINE SCHEDULE command 53, 55
DEFINE STGPOOL command 44, 46
DEFINE VOLUME command 36, 47
defining
administrator 37
archive copy group 50
backup copy group 50
client node 37
database volume 35
device class 43, 45
disk storage pool volume 36
drive 43, 44, 45
library 44, 45
management class 50
policy 50
policy domain 50
policy set 50
recovery log volume 35
storage pool 44, 46
storage pool volume 36
device
attach 39
names 41
device configuration
automated libraries 37, 39
device drivers 39, 40
for IBM 3490, 3570, and 3590 tape
drives 42
installing 39, 40
manual tape devices 40
mapping IBM Tivoli Storage Manager
devices to 41
SCSI 40
device name 41
directories, default installation 19
disability ix
disaster, protecting against 55
disk storage pool volumes, creating 36
disk storage pools
default volume size 36
defining initial volume 36
initializing 36
documentation, Tivoli Storage
Manager 75
drivers, device
for IBM 3490, 3570, and 3590 tape
drives 42
installing 39, 40
93
drivers, device (continued)
manual tape devices 40
mapping IBM Tivoli Storage Manager
devices to 41
SCSI 40
drives 39, 40, 41, 43, 45
dsmsched.log 54
DSMSERV_DIR environment variable 24
installing (continued)
over a previous version
space requirements for 20
verification 23
interfaces, administrative
administrative Web interface 57
command line 62
K
E
keyboard ix
enabling communications 31
ending the administrative client 27
environment variables 24
expiration
interval (server option) 52
processing 55
server option 25, 52
EXPIRE INVENTORY command 52, 55
F
file names (special) for devices 41
files
dsmserv runfile 27
dsmserv.opt.smp 31
firewall 32
L
label, tape 47
LANGUAGE option 63
language, install from SMIT 63
library, Tivoli Storage Manager
configuration example 39
manual 37
license, Tivoli Storage Manager 27
log file
database recovery 2
M
GRANT AUTHORITY command 37
granting authority to administrators 37
graphical user interface
client 26
maintenance updates 65
management class 10
default 51, 53
mapping devices to device drivers 41
migrating to tape 38, 49, 50
migration
hierarchy 38, 49
thresholds 49
H
N
HALT command 25
halting the server 25
hierarchy, storage pool 11
how Tivoli Storage Manager works 5
HTTP communication method 32
national language support 63
national language version features 63
NLS (national language support) 63
I
online books 18
options
initializing Tivoli Storage Manager
server 35
starting the server 25
options file
editing 31
options, client
TCPADMINPORT 33
TCPPORT 31
TCPWINDOWSIZE 31
options, server
communications 31
OS/2
starting the administrative client 26
overview
data management policy 8
G
IBM Redbooks 78
IBM Tivoli Storage Manager
architecture 2
base functions 1
client overview 4
data management overview 6
how it works 5
server overview 2
storage device and media
management overview 10
IBM Tivoli Storage Manager device
driver 41
IBMtape device driver 41
include-exclude list 52
initializing
server 35
tape volumes 47
installing
device drivers 39, 40
minimum requirements for 20
94
policy
standard (default) xi
using 50, 51
policy domain
associating a client with 50
defining 50
policy set
activating 44, 45, 51
validating 51
program temporary fixes (PTFs) 65
progressive backup methodology 7
protecting data 55
PTFs (program temporary fixes) 65
O
P
password, administrative client
IBM Tivoli Storage Manager for Linux: Quick Start
26
Q
QUERY EVENT command 54, 55
QUERY STGPOOL command 46
querying
events 54, 55
storage pool volumes 46
R
recovery log
creating 35
size 35
volume 35
redbooks 78
REGISTER LICENSE command 27
REGISTER NODE command 37
registering
administrator 37
client node 37
reinstalling an earlier version of the Tivoli
Storage Manager server 65
removing the Tivoli Storage Manager
server 65
S
scheduling
administrative commands 55
client operations 53
overview 14
scratch volumes
description 38
Secure Web Administrator Proxy
CD-ROM 71
description 69
FTP site 71
installing and configuring 71
prerequisites 69
troubleshooting 73
uninstalling 72
selective backup 23, 25
SELECTIVE command 23
server license 27
server options
dsmserv.opt.smp 31
tailoring 31
server options file
setting 31
server, Tivoli Storage Manager
activating 25
authority 37
server, Tivoli Storage Manager (continued)
changing options 52
creating initial storage pool
volume 36
halting 25
initializing 35
options 31, 52
overview 2
setting up 25
starting 25
stopping 25
storage migration 10, 38, 49
verifying configuration 23
size
archive pool 36
backup pool 36
database 35
recovery log, initial 35
space management pool 36
space management (HSM)
client overview 5
storage pool size 36
standard label 47
standard policy xi
starting
administrative client 26
client scheduler 54
server 25
stopping
client 27
server 25
storage pool
archive pool size 36
ARCHIVEPOOL 36, 38, 49, 50
backup pool size 36
BACKUPPOOL 36, 38, 49, 50
default 50
description 10, 25
disk 36
space management pool size 36
SPACEMGPOOL 36, 38, 49, 50
U
UPDATE COPYGROUP command 51
UPDATE STGPOOL command 36, 49
updating
copy group 51
installation 65
storage pool 44, 46
V
VALIDATE POLICYSET command 51
validating a policy set 51
volume
recovery log 2
W
web interface, how to connect server 27
web server 69
T
tape
backup to 37
devices 37, 43, 45
volumes, initializing 47
volumes, labeling 47
tape management system 37
TCP/IP
setting options 31
TCPADMINPORT option 33
TCPNODELAY option 32
TCPPORT option 31
TCPWINDOWSIZE option 31
threshold, migration 49
Tivoli Storage Manager Console
adding tape drives 43, 45
creating disk storage pool
volumes 36
Tivoli Storage Manager, setting up 25
Index
95
96
IBM Tivoli Storage Manager for Linux: Quick Start
Part Number: CT1ZBNA
Program Number: 5698–ISM
5698–ISX
5698–SAN
5698–HSM
GC23-4692-01
(1P) P/N: CT1ZBNA
Printed in U.S.A.
Spine information:
IBM Tivoli Storage Manager
for Linux
Quick Start
Version 5
Release 2