The information contained in this book is subject to change without notice.
Reproduction, adaptation or translation without prior written permission is prohibited,
except as allowed under the copyright laws.
APTARE® and StorageConsole® are registered trademarks of APTARE, Inc. and/or its
affiliates in the U.S. and certain other countries.
Hitachi is a trademark of Hitachi Data Systems.
Acrobat and the Acrobat logo are trademarks of Adobe Systems Incorporated.
Microsoft, Microsoft Windows and Microsoft Internet Explorer are registered
trademarks of Microsoft Corporation in the United States and/or other countries.
Macintosh, Mac, Apple, Safari, and Mac OS are trademarks of Apple Computer, Inc.,
registered in the U.S. and other countries.
EMC Legato NetWorker is a registered trademark of EMC Corporation.
NetBackup and Backup Exec are registered trademarks of Symantec Corporation.
Other company and product names mentioned herein can be trademarks or registered
trademarks of their respective companies.
Publication Change Record
The following table records all revisions to this publication. This first entry is always
the publication’s initial release. Each entry indicates the date of the release and the
number of the system release to which the revision corresponds.
Appendix B - Data Collector Pre-Installation Worksheet39
v v
vi APTARE StorageConsole Data Collector Installation Guide for IBM Tivoli Storage Manager
About This Book
This document provides detailed step-by-step instructions for the installation of the
APTARE Data Collector for IBM Tivoli Storage Manager. This install guide is valid for
Portal version 6.5 onward.
This document assumes either:
• The Portal has already been successfully installed in your enterprise, and that the reader of
this document is aware of the password for the StorageConsole admin user (e.g.
admin@
• The Portal, hosted by APTARE or a third-party service provider, will serve as your portal.
This option typically applies only to evaluation or hosted customers and is referred to as a
HOSTED installation.
yourdomain.com). This is referred to as an IN-HOUSE installation. Or,
Separate instructions are provided as necessary for Windows and UNIX.
Contacting APTARE
If at any time during the install you encounter a problem, or if you simply want to verify
a step or have a question about the installation, please contact the APTARE Customer
Care Group which will be happy to assist you:
Chapter 0
Preface
Technical Support:
Customer Care Group
• support@aptare.com or
• 1-408-871-9848
• 1-866-9-APTARE, Option #1, 6:00am - 5:30pm
Pacific Time
Sales:
• sales@aptare.com or
• 1 866-9-APTARE, Option
#2
About This Book 1
2 APTARE StorageConsole Data Collector Installation Guide for IBM Tivoli Storage Manager
Application Administrator’s Guide
This chapter covers the following topics:
• Data Collection Overview
• Architecture Overview
Data Collection Overview
The Data Collector is a centralized and remotely managed data collection mechanism.
This Java application is responsible for interfacing with backup servers and storage
arrays, gathering information related to storage backup and recovery, and capacity
management.
The Data Collector continuously collects data and sends this data, using an http or https
connection, to another Java application, the Data Receiver. The Data Receiver runs on
the Portal Server and stores the data that it receives in the Reporting Database. When
you use the Portal to generate a report, the Portal requests this information from the
Reporting Database, then returns the results in one of the many available reports.
1
Chapter 0
Introduction to Data Collection
The Data Collector obtains all of its monitoring rules from a Data Collector
Configuration File. This file resides in the Reporting Database in XML format. When
the Data Collector first starts, it downloads this file from the Reporting Database. The
Data Collector uses this file to determine the list of backup servers, hosts, or storage
arrays that are to be monitored and included in its data collection process. For details on
how host names are processed, see “Host Name Processing - Filters and Aliases” in
Application Administrator’s Guide.
Data Collector Terminology
Data Collector - This software component interfaces with each of the supported
backup and recovery software systems to extract meta-data about the underlying
backup and recovery environment. For example, data can include backup job details
and tape inventory information. In the case of Capacity Manager, the Data Collector
communicates with the storage arrays in your SAN (Storage Area Network).
Data Collection by Backup Product
The following collection mechanisms are used for the particular backup products:
• EMC Legato NetWorker - The Data Collector uses the Legato administration commandline utilities, such as mminfo, nsradmin, and nsrinfo.
• IBM Tivoli Storage Manager - The Data Collector interfaces with TSM using the TSM
utility, dsmadmc, collecting data from the underlying TSM databases, including TSM
Archives for LAN-free backups.
Data Collection Overview 3
• Symantec Backup Exec - The Data Collector uses database commands to obtain
information from each Backup Exec server.
Note: Veritas NetBackup is the only backup product that does not require a Data Collector
because an agent is used to obtain information from NetBackup.
Data Collection by Storage Array
• Capacity Manager - The Data Collector communicates with the storage array’s system
service processor (SSP) and hosts to gather storage capacity data.
Data Collector Server - This is the physical server on which the Data Collector is
installed. It can be any server within your network that is Java 1.5 compatible.
For Backup Manager, where you install the Data Collector depends on your backup
solution. NetBackup is the only backup solution that requires that the Data Collector
reside on each Master Server. For all other backup solutions, the Data Collector can run
on a standalone server, the Portal Server, or any Backup Server.
In the case of Capacity Manager, the Data Collector can run on a stand-alone server or
the Portal server. In some cases—such as EMC Symmetrix arrays—the Data Collector
must reside on the system that is running the SAN management software.
A single installation of the Data Collector supports any number of servers. The only real
limitation is the memory and CPU processing power of the server on which the Data
Collector resides.
Planning Data Collector Deployment
In most cases, a single instance of the Data Collector can support any number of backup
servers or storage arrays. However, each environment has its own unique deployment
configuration requirements, so it is important to understand where the Data Collector
software must be installed so that you can determine how many Data Collectors must be
installed and which servers are best suited for the deployment.
Use the following guidelines to plan the installation of Data Collectors.
Backup Manager:
• One Data Collector for each backup product—EMC Legato NetWorker, Tivoli Storage
Manager, VERITAS Backup Exec, and HP Data Protector.
Capacity Manager:
• One Data Collector for each storage array type—EMC or Hitachi
• Host Resources do not require a dedicated Data Collector for each resource. If you have a
Storage Array Data Collector, the Host Resources collector is inherently part of that Data
Collector. However, if for some reason you do not have a Storage Array Data Collector, you
can install a Host Resources Data Collector.
Refer to the Pre-Installation Setup chapter for specific requirements and a worksheet
for assembling the details needed for Data Collector installation.
4 APTARE StorageConsole Data Collector Installation Guide for IBM Tivoli Storage Manager
Architecture Overview
The following diagram provides an example of how the IBM Tivoli Storage Manager
Data Collector could be deployed in your environment.
Figure 1.1 Data Collector in an IBM Tivoli Storage Manager Environment
For each TSM Instance, the Data Collector will establish connections to the database
using the command, dsmadmc. The Data Collector Configuration file contains all the
connection information for each TSM Instance including such parameters as the TSM
user name and password for login, the TSM Instance name, IP address of the TSM Host
Server, and the TSM Port.
The Data Collector will use various QUERY and SELECT commands via dsmadmc to
obtain its information from each separate TSM Instance. The information is then sent
via http(s) to the Portal. A user can then launch a web-browser to use the Portal to see a
global view of all of their TSM Host Servers and TSM Instances.
IBM Tivoli Storage Manager Terminology
TSM Host Server - The TSM Host Server is the physical system that is running the
IBM Tivoli Storage Manager server software. This system will be known by its
hostname or IP address.
TSM Instance- The TSM Instance is a separate instance of the TSM server software
that is running on a TSM Host Server. A single TSM Host Server can run multiple TSM
Instances. This is normally implemented by setting up a separate set of client and
administration ports for each TSM Instance. In the architecture example in Figure 1.1,
there are two TSM Host Servers—one has a single TSM Instance running on it and the
other Host Server has two TSM Instances running on it.
Architecture Overview 5
6 APTARE StorageConsole Data Collector Installation Guide for IBM Tivoli Storage Manager
Application Administrator’s Guide
This chapter covers the following topics:
• Before You Install the Data Collector
• Updating the Local Hosts File
• Adding TSM Host Servers to StorageConsole
• Configuring Data Collector Policies in the Portal
Before You Install the Data Collector
In preparation for Data Collector installation, take the steps described in this chapter.
Note: These steps apply only if you are performing an IN-HOUSE installation. If a third-party
service provider is hosting your Portal—that is, a HOSTED installation (perhaps for a product
evaluation)—skip this section and contact your hosting organization’s representative to
configure the hosted portal for your Data Collector.
2
Chapter 1
Pre-Installation Setup
Requirement: Data Collector Server
The Data Collector Server is the physical server on which the Data Collector is
installed. It can be any server within your network that is Java 1.5 compatible and with
dsmadmc installed.
Updating the Local Hosts File
1. Add the Portal IP Address to the Local Hosts file on the Data Collector Server or on any
available client with web-browsing capabilities.
Note: Only edit the local hosts file if a DNS entry hasn’t already been set up in your
enterprise to resolve both http://aptareportal.yourdomain.com and http://
aptareagent.yourdomain.com to the Portal IP address.
a. Login to the Data Collector Server.
b. On a UNIX server:
edit /etc/hosts
Add entries for aptareportal.yourdomain.com and aptareagent.yourdomain.com,
both resolving to the Portal server IP address.
On a Windows server:
edit C:\WINNT\System32\drivers\etc\hosts
Before You Install the Data Collector 7
Add entries for aptareportal.yourdomain.com and aptareagent.yourdomain.com,
both resolving to the Portal server IP address.
8 APTARE StorageConsole Data Collector Installation Guide for IBM Tivoli Storage Manager
Loading...
+ 32 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.