The IBM® Tivoli® Storage Manager Server
Fix Pack 7.1.1.000 is available. The following sections provide information
about system requirements, installation, and other resources for the
server.
Description
The Tivoli Storage
Manager server provides
backup, archive, and space management services to clients. You can
set up multiple servers in your enterprise network to balance storage,
processor, and network resources.
To view APARs that were resolved
in Fix Pack 7.1.1.000, see Server APARs resolved in Fix Pack 7.1.1.000.
Installing and upgrading Tivoli Storage
Manager
Before you apply Fix Pack 7.1.1.000, take the
following actions:
- Verify the setting for the ALLOWREORGINDEX server
option, which specifies whether server-initiated index reorganization
is enabled. You can verify the setting in the dsmserv.opt file.
The process of index reorganization might change after the upgrade,
depending on the setting:
- If no value is specified for the ALLOWREORGINDEX server
option, index reorganization did not occur before the upgrade. After
the upgrade, all indexes will be reorganized. For any tables that
are specified with the DISABLEREORGINDEX option,
indexes will be reorganized offline. For all other tables, indexes will be reorganized
online.
- If a value of YES is specified for the ALLOWREORGINDEX server
option, all indexes were reorganized before the upgrade. After the
upgrade, for any tables that are specified with the DISABLEREORGINDEX option,
indexes will be reorganized offline. For all other tables, indexes will be reorganized
online.
- If a value of NO is specified for the ALLOWREORGINDEX server
option, index reorganization did not occur before the upgrade and
will not occur after the upgrade.
If the
Tivoli Storage
Manager system
includes storage pool volumes in deduplicated storage pools, and the
ACCESS=DESTROYED parameter
is set for the volumes, consider updating the volumes by issuing the
UPDATE
VOLUME command and specifying the
ACCESS=UNAVAILABLE parameter.
If you do not specify the
ACCESS=UNAVAILABLE parameter,
and the storage pools include many objects, you might experience delays
during the upgrade. To avoid delays, complete the following steps:
- For affected storage pool volumes for which the ACCESS=DESTROYED parameter
is set, run the UPDATE VOLUME command, and specify
the ACCESS=UNAVAILABLE parameter.
- Upgrade the server.
- Run the UPDATE VOLUME command again. For storage
pools volumes for which the ACCESS=UNAVAILABLE parameter was
previously set, specify the ACCESS=DESTROYED parameter. Consider
updating one volume at a time so that you can monitor the use of system
and IBM DB2® resources and ensure that the
update process does not affect production workloads.
During the upgrade, if the server detects volumes for
which the
ACCESS=DESTROYED parameter is set, the
feature for recovering damaged files from a target replication server
is disabled. If you intend to use the feature, wait until the upgrade
is complete and the use of server resources is at a minimum. Then, issue
the following command:
set replrecoverdamaged on
When
you issue this command, the system initiates a scan of database tables
for damaged objects that can be recovered. If many damaged files are
detected, the scan can take a considerable amount of time. During
subsequent node replication processes, replicated files that are damaged
on the source replication server can be replaced with undamaged files
from the target replication server.
Updates, limitations, and known problems
Updates,
limitations, and known problems are documented in the form of technotes
in the Support knowledge base at http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager. As problems are discovered and resolved, IBM Software Support updates the
knowledge base. By searching the knowledge base, you can find workarounds
or solutions to problems.
Updates
For
a list of new features in Fix Pack 7.1.1.000, see Updates for the Tivoli Storage
Manager server component.
- Managing replicated data with policies that are defined on the
target replication server
To manage replicated data with policies that are defined on
the target replication server, enable the feature by running the SET
DISSIMILARPOLICIES command.
If the feature is enabled,
the best practice is to run the EXPIRE INVENTORY command
immediately after completion of the REPLICATE NODE command. If
a file belongs to a node that is configured for replication, and the
file is scheduled for expiration, that file cannot be expired and
deleted unless it is first replicated. By running the expiration process
immediately after the replication process, you can ensure that expired
files are deleted without delay. In this way, you can avoid issues
such as unexpected database growth and storage pool growth.
To search for the latest information about updates, see Updates for Tivoli Storage
Manager Fix Pack
7.1.1.000.
Limitations and known problems
At
the time of publication, the following limitations and problems were
known:
- Tivoli Storage
Manager Console
is not available
- The Tivoli Storage
Manager Management
Console, which is a Microsoft Management
Console (MMC) snap-in, is no longer delivered with Tivoli Storage
Manager. If you
are configuring or upgrading a Tivoli Storage
Manager server that
is installed on a Microsoft Windows operating system, the
preferred methods are to use the configuration and upgrade wizards.
You can use the wizards to complete several server configuration tasks.
However, you cannot use the wizards to extend the Active Directory
schema so that clients can automatically discover servers.
- Unexpected database growth and degraded performance
- In some circumstances, unexpected database growth and degraded
performance can occur with a Tivoli Storage
Manager server.
For details about this issue and how to resolve it, see Techdoc 1452156.
- Issues with the AUDIT LIBVOLUME command
- You can use the AUDIT LIBVOLUME command on
some operating systems to determine whether a tape volume is intact
and to audit data on the tape volume. Do not run the AUDIT
LIBVOLUME command if the Tivoli Storage
Manager server is
installed on a Solaris operating system. Before you run the AUDIT
LIBVOLUME command, review the following information:
- If Tivoli Storage
Manager is
installed on an AIX, HP-UX, Linux, or Windows operating system, issue the AUDIT
LIBVOLUME command from a tape volume that is checked in
to a library. After you issue the command, the entire physical tape
volume is audited. If errors are detected, you can use the AUDIT
VOLUME command to fix storage pool volumes on the tape if
all of the tape volume data still exists in the storage pool.
- If Tivoli Storage
Manager is
installed on a Windows operating
system, and you issue the AUDIT LIBVOLUME command
for a tape volume in an IBM 03584L22
tape library (firmware level C460), the volume is audited. However,
the tape volume will not be ejected and moved automatically from the
drive to the home slot. You must manually check out the tape volume
after the audit and move it to the home slot.
- If Tivoli Storage
Manager is
installed on a Solaris operating system, and you issue the AUDIT
LIBVOLUME command, and then issue the HALT command
after the audit, the host system where Tivoli Storage
Manager is installed
might fail unexpectedly.
To search for the latest information about limitations
and known problems, which might include additional items, see Limitations and known problems for Tivoli Storage
Manager Fix Pack
7.1.1.000.
Copyright and trademark information
http://www.ibm.com/legal/copytrade.shtml
Notices
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 jurisdictions 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.
Trademarks
IBM, the IBM logo, and ibm.com® are
trademarks or registered trademarks of International Business Machines
Corp., registered in many jurisdictions worldwide. Other product and
service names might be trademarks of IBM or
other companies. A current list of IBM trademarks
is available on the Web at "Copyright and trademark information" at http://www.ibm.com/legal/copytrade.shtml.
Linux is
a registered trademark of Linus Torvalds in the United States, other
countries, or both.
Microsoft and Windows are 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 and other countries.
Other company, product,
or service names may be trademarks or service marks of others.
THIRD-PARTY
LICENSE TERMS AND CONDITIONS, NOTICES AND INFORMATION
The
license agreement for this product refers you to this file for details concerning
terms and conditions applicable to third party software code included
in this product, and for certain notices and other information IBM must provide to you under its
license to certain software code. The relevant terms and conditions, notices and
other information are provided or referenced below. Please note that
any non-English version of the licenses below is unofficial and is
provided to you for your convenience only. The English version of
the licenses below, provided as part of the English version of this
file, is the official version.
Notwithstanding the terms and conditions of any other agreement
you may have with IBM or any
of its related or affiliated entities (collectively "IBM"), the third party software code identified below
are "Excluded Components" and are subject to the following terms and conditions:
- the Excluded Components are provided on an "AS IS" basis
- IBM DISCLAIMS ANY AND ALL
EXPRESS AND IMPLIED WARRANTIES AND CONDITIONS WITH RESPECT TO THE
EXCLUDED COMPONENTS, INCLUDING, BUT NOT LIMITED TO, THE WARRANTY OF
NON-INFRINGEMENT OR INTERFERENCE AND THE IMPLIED WARRANTIES AND CONDITIONS
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
- IBM will not be liable to
you or indemnify you for any claims related to the Excluded Components
- IBM will not be liable for
any direct, indirect, incidental, special, exemplary, punitive or
consequential damages with respect to the Excluded Components.