Redpaper
Alex Osuna
Helvio Homem
Jim Lanson
IBM System Storage N series
Operations Manager Sizing and
Installation Guide
Purpose
The purpose of this IBM® Redpaper is to provide the necessary information to
allow Operations Manager Administrators to effectively choose the correct
system for hosting the Operations Manager server. This Redpaper also tells
them how to install or upgrade it on a Linux® or Windows® system. It is
important to note that the information about sizing are guidelines only and many
environmental factors may influence the choice. Operations Manager was
previously named DataFabric® Manager.
Introduction
In growing IBM environments there is an increased need to ensure that as the
infrastructure grows, the Operations Manager (OM) server can scale to meet
these needs. Specific resource requirements are outlined in the Installation
Guide for each release of OM; however, these are minimum configurations.
Customers implementing these configurations need to know how many more
storage systems, volumes, relationships, and so on, can be added before a
© Copyright IBM Corp. 2007. All rights reserved.
ibm.com/redbooks
1
system upgrade becomes necessary. First we will look at some of the factors
that affect the OM server. Then, we will cover the IT installation and upgrading
procedures for Windows and Linux.
Sizing factors
The following items are the variables considered for an OM sizing:
򐂰 Number of devices monitored: This is the total number of N series devices
being monitored by OM.
򐂰 Monitoring intervals: It is recommended that at least initially all monitoring
intervals be left at their factory defaults. Adjustments to intervals may
adversely affect OM server performance.
򐂰 SnapVault® Relationships: While the number of relationships has minimal
effect on server sizing, large quantities must be considered.
򐂰 SnapMirror® Relationships: While the number of relationships has minimal
effect on server sizing, large quantities must be considered.
򐂰 Qtrees: The total number of Qtrees being monitored by OM must be
considered.
򐂰 Quotas: The total number of quotas being monitored by OM must be
considered.
򐂰 Host agents: Host agents pose little burden on the OM server when used for
SAN data monitoring purposes. When used for the optional SRM data
classification, there is a load imposed, and thus it is recommended that SRM
jobs be run consecutively during non-production hours. For this reason it is
not factored into server sizing.
Test results
Figure 1 on page 3 and Figure 2 on page 3, and Figure 3 on page 4, depict the
results of sizing tests. These tests were performed on various platforms using
Operations Manager 3.2. With each platform, variations in number of CPUs and
memory were used to gauge effects on performance. These tests were
performed with all settings set to factory defaults. The access time referred to on
the vertical axis is the time it takes to get the desired OM page to display. Each
line represents an OM page and the horizontal axis has the number of devices
added to OM. It is important to note the comparisons in vertical scaling between
Solaris™ and the Windows and Linux platforms.
2
IBM System Storage N series Operations Manager Sizing and Installation Guide
Figure 1 Windows summary page
Figure 2 Solaris summary page
IBM System Storage N series Operations Manager Sizing and Installation Guide
3
Figure 3 Linux summary page
Conclusion
As previously stated, these results are based on the use of version 3.2 of
Operations Manager. Results may be different on previous or subsequent
releases. When subsequent releases substantially alter these results, this
document will be updated accordingly.
Database growth
Space in the OM database is dominated by history tables. A rough breakdown is
that 75% of the file are history tables, and about 25% are free pages and
overhead. The remaining OM tables tend to only use a small percentage of the
file. This includes qtree and quota histories.
From a regression analysis of history table contents, there is a formula to
estimate the space consumed as a function of the number of hosts, aggregates,
and volumes:
(#hosts * 2.25 MB) + (#vols * 98 KB) – (#aggrs * 270 KB) = bytes/table
For example: a customer has 250 hosts, 1587 volumes, and 1587 aggregates.
The customer expects that its number of hosts will grow to 350. In order to
accommodate this growth, we should plan for 2200 volumes and 2200
aggregates.
4
IBM System Storage N series Operations Manager Sizing and Installation Guide
(350 * 2.25 MB) + (2200 * 98 KB) – (2200 * 270 KB) = 409 Mbytes/table
OM keeps two each of daily, weekly, monthly, and quarterly tables, plus an
open-ended number of yearly tables. At the end of the year, there will be nine
filled history tables, and OM will add a new yearly table each year. If we add the
25% overhead (free pages and internal bookkeeping), that means each table will
use about 509MB. Nine tables mean 4.58GB, plus a new 509MB yearly table
each year.
Bottom line: after a year, the OM database will be about 4.6GB, and it will grow
by about 509MB/year.
It is important to note that additional space will be consumed by the OM server if
the Performance Advisor is used. This space is not directly part of the OM
database but stored by default under the OM installation directory on a folder
named perfdata. In order to check where Performance Advisor data is currently
stored, enter the command in Example 1.
Example 1 dfm option command
dfm option list perfArchiveDir
You will see an output similar to Example 2 for Windows OM Servers.
Example 2 dfm option output
option
Value
--------------- -----------------------------perfArchiveDir C:/Program Files/IBM/DataFabric/DFM/perfdata
Or like this for Linux OM Servers:
Option
Value
--------------- -----------------------------perfArchiveDir /opt/NTAPdfm/perfdata
In some situations, where the OM Server is monitoring several Storage Systems
and the OM Server C: drive is going out of space due to the large amount of data
generated by Performance Advisor, the data path can be changed to another
volume with the command in Example 3.
Example 3 dfm option set command
dfm option set perfArchiveDir=newperfdatadirectory
IBM System Storage N series Operations Manager Sizing and Installation Guide
5
To apply the path change, it is necessary to restart OM server service. This can
be done by using the commands in Example 4.
Example 4 dfm service command
dfm service stop server
dfm service start server
Note: You must move all of the old perfdata to the new directory after the
server stops; otherwise, the perf data will be lost.
Choosing a configuration
Choosing a configuration is based on the total number of devices monitored and
managed by Operations Manager. In order to factor in the effect of other
operations such as SnapVault, SnapMirror, and SRM Data classification jobs,
use the following:
򐂰
򐂰
򐂰
򐂰
1 device = 50 SnapVault Relationships
1 device = 50 SnapMirror Relationships
1 device = 25 Qtrees
1 device = 100 Quotas
Example
A customer has 35 appliances with a total of 50 SnapVault relationships, two
SnapMirror relationships, 25 Qtrees, and 100 quotas. So in choosing one of the
configurations below, we add the following:
35 appliances + 1(for SnapVault Relationships) + 1 (qtrees) +
1 (quotas) = 38 devices
This would mean the medium configuration is appropriate.
In calculating the above it is important to take anticipated growth into
consideration.
6
IBM System Storage N series Operations Manager Sizing and Installation Guide
Table 1 Small Configuration
1-25 Devices
WINDOWS 2000, 2003
Hardware requirements
򐂰
򐂰
򐂰
PC based on Intel® with single 2-GHz CPU
(Xeon® or Pentium® 4)
4 GB of free disk space, 8 GB recommended
1 GB of memory minimum
Software requirements
򐂰
򐂰
Windows 2000 server (Service Pack 2 or later)
Windows 2003 server
SOLARIS 8, 9
Hardware requirements
򐂰
򐂰
򐂰
Single UltraSPARC IIIi processor at 1 GHz
(such as Sun™ Fire™ V120 or V240)
4 GB of free disk space minimum, 8 GB
recommended
1 GB of memory minimum
Software requirements
򐂰
򐂰
򐂰
򐂰
Solaris 8 (Patch 108827 or later)
Minimum of 4,096 file descriptors
If the hard limit is less than 4,096, DataFabric
Manager sets its limit to be the current hard
limit and generates a warning in the log
Solaris 9
LINUX workstation or server
Hardware requirements
򐂰
򐂰
򐂰
PC based on Intel with single 2-GHz CPU
(Xeon or Pentium 4)
4 GB of free disk space minimum, 8 GB
recommended
1 GB of memory minimum
Software requirements
򐂰
򐂰
Red Hat Enterprise Linux ES for x86, version 3
(update 3 or later)
Other Linux versions and distributions are not
supported
IBM System Storage N series Operations Manager Sizing and Installation Guide
7
Table 2 Medium configuration
26-100 DEVICES
WINDOWS 2000, 2003
Hardware requirements
򐂰
򐂰
򐂰
򐂰
PC based on Intel with single 2-GHz CPU
(Xeon or Pentium 4)
6 GB of free disk space, 12 GB recommended
ISCSI, FC LUN, or internal RAID disk
2 GB of memory minimum
Software requirements
򐂰
򐂰
Windows 2000 server (Service Pack 2 or later)
Windows 2003 server
SOLARIS 8, 9
Hardware requirements
򐂰
򐂰
򐂰
Dual UltraSPARC IIIi processor at 1 GHz or
greater
6 GB of free disk space minimum, 12 GB
recommended
1 GB of memory minimum
Software requirements
򐂰
򐂰
򐂰
򐂰
Solaris 8 (Patch 108827 or later)
Minimum of 4,096 file descriptors
If the hard limit is less than 4,096, DataFabric
Manager sets its limit to be the current hard
limit and generates a warning in the log
Solaris 9
LINUX workstation or server
Hardware requirements
򐂰
򐂰
򐂰
򐂰
8
PC based on Intel with single 2-GHz CPU
(Xeon or Pentium 4)
6 GB of free disk space minimum, 12 GB
recommended
ISCSI, FC LUN, or internal RAID disk
2 GB of memory minimum
Software requirements
򐂰
򐂰
Red Hat Enterprise Linux ES for x86, version 3
(update 3 or later)
Other Linux versions and distributions are not
supported
IBM System Storage N series Operations Manager Sizing and Installation Guide
Table 3 Large configuration
101- 250 Devices
WINDOWS 2000, 2003
Hardware requirements
򐂰
򐂰
򐂰
򐂰
PC based on Intel with Dual 2-GHz CPU (Xeon
or Pentium 4)
8 GB of free disk space, 20 GB recommended
ISCSI, FC LUN, or internal RAID disk
4 GB of memory minimum
Software requirements
򐂰
򐂰
Windows 2000 server (Service Pack 2 or later)
Windows 2003 server
LINUX workstation or server
Hardware requirements
򐂰
򐂰
򐂰
򐂰
PC based on Intel with single 2-GHz CPU
(Xeon or Pentium 4)
8 GB of free disk space minimum, 20 GB
recommended
ISCSI, FC LUN, or internal RAID disk
4 GB of memory minimum
Software requirements
򐂰
򐂰
Red Hat Enterprise Linux ES for x86, version 3
(update 3 or later)
Other Linux versions and distributions are not
supported
Operations Manager 3.4.1 is not supported on Windows NT® 4.0 or Windows
XP.
These requirements are for a Operations Manager installation with only basic
monitoring of IBM N series. If you enable additional features and monitor
additional objects, a more powerful platform will probably be required.
Operations Manager install and upgrade
Prior to installing or upgrading Operations Manager, ensure that you meet
requirements in the following areas:
򐂰 Hardware and software requirements
򐂰 License requirements
򐂰 Data ONTAP® requirements
Review “Choosing a configuration” on page 6 to select the best configuration for
your environment.
Windows Server 2003
In order to install Operations Manager on a Windows Server® 2003, complete
the following steps.
IBM System Storage N series Operations Manager Sizing and Installation Guide
9
Note: The installation software automatically detects and stops any OM
services that are running on the system. Therefore, you do not need to
manually stop OM services before starting the upgrade process to OM 3.4.1.
Also, you need to have Local Administrator login permission on the server you
are installing OM.
Upgrading
1. Insert the OM 3.4.1 CD into the CD-ROM drive of your DataFabric Manager
server, or browse to the folder where the installation file is located.
2. Run dfmsetup-3.4.1-win32.exe to start OM setup.
3. Windows Server 2003 usually shows you a warning regarding security when
executing executable files (Figure 4). If this occurs, click Run.
Figure 4 Windows 2003 Security Warning
4. Wait while setup is started up.
5. On IBM DataFabric Manager - Install shield Wizard (Figure 5 on page 11),
click Next.
10
IBM System Storage N series Operations Manager Sizing and Installation Guide
Figure 5 IBM DataFabric Manager - Install Shield Wizard welcome window
6. Choose a name or accept the default for the OM backup file that is
automatically created by the setup wizard. You can add a string
“before_upgrade” at the end of the suggested file name (Figure 6 on
page 12). Click Next.
IBM System Storage N series Operations Manager Sizing and Installation Guide
11
Figure 6 Back up OM current database
7. Click OK to agree with the warning about backing up large databases.
8. Click Install to start the OM upgrade, or click Back to change any installation
settings (Figure 7 on page 13).
12
IBM System Storage N series Operations Manager Sizing and Installation Guide
Figure 7 Start OM upgrade
9. Wait while new files are copied and OM upgrade is performed. It usually takes
several minutes.
10.Click Finish when installation completes (Figure 8 on page 14).
IBM System Storage N series Operations Manager Sizing and Installation Guide
13
Figure 8 OM Upgrade completed
New Installation
1. Insert the OM 3.4.1 CD into the CD-ROM drive of your DataFabric Manager
server, or browse to the folder where the installation file is located.
2. Run dfmsetup-3.4.1-win32.exe to start OM setup.
3. Windows Server 2003 usually shows you a warning regarding security when
executing .exe files (Figure 9 on page 15). If this occurs, click Run.
14
IBM System Storage N series Operations Manager Sizing and Installation Guide
Figure 9 Windows 2003 Security Warning
4. Wait while setup starts up.
5. On IBM DataFabric Manager - Install shield Wizard (Figure 10), click Next.
Figure 10 IBM DataFabric Manager - Install Shield Wizard - welcome window
IBM System Storage N series Operations Manager Sizing and Installation Guide
15
6. Read the explanation of AutoSupport, and then select your decision. If you
select I do not accept, installation cannot continue. After accepting the
agreement, click Next (Figure 11).
Figure 11 Windows Installation AutoSupport Notice
7. Complete the User Name and Organization information (Figure 12 on
page 17), and then click Next.
16
IBM System Storage N series Operations Manager Sizing and Installation Guide
Figure 12 Customer information
8. Type the license key for OM Core, and click Next (Figure 13 on page 18).
IBM System Storage N series Operations Manager Sizing and Installation Guide
17
Figure 13 License Key for OM Core
9. Choose the destination folder for OM, or accept the default (Figure 14). Click
Next.
Figure 14 Choose the destination folder
18
IBM System Storage N series Operations Manager Sizing and Installation Guide
10.Click Install to start the OM installation, or click Back to change any
installation settings (Figure 15).
Figure 15 Starting OM installation
11.Wait while new files are copied and OM installation is performed. It usually
takes several minutes.
12.Click Finish when installation completes (Figure 16 on page 20).
IBM System Storage N series Operations Manager Sizing and Installation Guide
19
Figure 16 OM Installation completed
Linux
In order to have Operations Manager (OM) installed on a Linux system, complete
the following steps.
Note: Make sure you have root user login permissions for the Operations
Manager server.
New Installation
1. Log on to the Linux machine where Operations Manager will be installed.
2. Get root access by entering the command in Example 5. You will be asked for
root password.
Example 5 root password
su root
3. Launch dfmsetup-3.4.1-linux.sh, previously downloaded by using the
command in Example 6 on page 21.
20
IBM System Storage N series Operations Manager Sizing and Installation Guide
Example 6 dfmsetup
./dfmsetup-3.4.1-linux.sh
By default, Operations Manager installs itself in the /opt directory. To change the
installation directory, use the -d new directory command line option.
4. Setup begins and displays an AutoSupport notice. Agree with the conditions
to proceed with the installation; otherwise, it is skipped (Figure 17). Type y,
and press Enter.
Figure 17 Linux Installation Autosupport notice
5. Enter your OM core license key, and press Enter.
6. Wait while OM 3.4.1 is installed (Figure 18 on page 22).
IBM System Storage N series Operations Manager Sizing and Installation Guide
21
Figure 18 Linux OM 3.4.1 installation
7. When installation finishes, a message appears prompting you to access OM
(Figure 19 on page 23).
8. Access Operations Manager through your browser by typing the following:
http://servername:8080
22
IBM System Storage N series Operations Manager Sizing and Installation Guide
Figure 19 Linux OM Installation completed
The Operations Manager 3.4.1 installation and upgrade process automatically
installs the autosupport feature with autosupport enabled and displays a
message about how to disable the feature. To disable AutoSupport, use the
following command:
dfm option set autosupportEnabled=no
Uninstallation
To uninstall Operations Manager, complete the following steps.
Note: Make sure you have root user login permissions for the Operations
Manager server.
1. Get root access by entering the command in Example 7. You will be asked for
root password.
Example 7 root password
su root
IBM System Storage N series Operations Manager Sizing and Installation Guide
23
2. Use one of the following Red Hat Linux commands.
Example 8 rpm command
rpm -e NTAPdfm
rpm --erase NTAPdfm
Figure 20 Linux OM uninstall
3. Uninstallation is completed!
24
IBM System Storage N series Operations Manager Sizing and Installation Guide
During the uninstallation process, Operations Manager saves the log files and
the database file to a temporary directory named NTAPdfm- year, month, day,
hour, minute, second, if it has permissions to create the directory. If Operations
Manager does not have sufficient permissions, the database file and the log files
are left in place.
The team that wrote this Redpaper
This Redpaper was produced by a team of specialists from around the world
working at the International Technical Support Organization, Poughkeepsie
Center.
Alex Osuna is a Project Leader at the International Technical Support
Organization, Tucson Center. He writes extensively and teaches IBM classes
worldwide on all areas of IBM storage. Before joining the ITSO two years ago,
Alex Osuna worked in Tivoli® Sales as a Systems Engineer. He has over 29
years experience in the IT industry with 20 of them focused mainly on data
storage. He holds over 10 certifications from IBM, Microsoft®, and Redhat.
Helvio Homem is an IT Specialist in IBM Global Services in Brazil. He has six
years of experience in the IT Infra-Structure field. He holds a degree in
Information Systems from Universidade Paulista and holds several product
certifications from Microsoft. His areas of expertise include Microsoft
infra-structure environments and NAS support.
Jim Lanson works for the Network Appliance™ corporation.
IBM System Storage N series Operations Manager Sizing and Installation Guide
25
26
IBM System Storage N series Operations Manager Sizing and Installation Guide
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.
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.
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.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which illustrates programming
techniques on various operating platforms. You may copy, modify, and distribute these sample programs in
any form without payment to IBM, for the purposes of developing, using, marketing or distributing application
programs conforming to the application programming interface for the operating platform for which the
sample programs are written. These examples have not been thoroughly tested under all conditions. IBM,
therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy,
modify, and distribute these sample programs in any form without payment to IBM for the purposes of
developing, using, marketing, or distributing application programs conforming to IBM's application
programming interfaces.
© Copyright International Business Machines Corporation 2007. All rights reserved.
Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by
GSA ADP Schedule Contract with IBM Corp.
27
Send us your comments in one of the following ways:
򐂰 Use the online Contact us review IBM Redbook form found at:
ibm.com/redbooks
򐂰 Send your comments in an email to:
redbook@us.ibm.com
򐂰 Mail your comments to:
IBM Corporation, International Technical Support Organization
Dept. HYTD Mail Station P099, 2455 South Road
Poughkeepsie, NY 12601-5400 U.S.A.
®
Redpaper
Trademarks
The following terms are trademarks of the International Business Machines Corporation in the United States,
other countries, or both:
Redbooks (logo)
IBM®
™
System Storage™
Tivoli®
The following terms are trademarks of other companies:
Network Appliance, SnapVault, SnapMirror, DataFabric, Data ONTAP, and the Network Appliance logo are
trademarks or registered trademarks of Network Appliance, Inc. in the U.S. and other countries.
Solaris, Sun, Sun Fire, and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the
United States, other countries, or both.
Microsoft, Windows NT, Windows Server, Windows, and the Windows logo are trademarks of Microsoft
Corporation in the United States, other countries, or both.
Intel, Pentium, Xeon, Intel logo, Intel Inside logo, and Intel Centrino logo are trademarks or registered
trademarks of Intel Corporation or its subsidiaries in the United States, other countries, or both.
Linux is a trademark of Linus Torvalds in the United States, other countries, or both.
Other company, product, or service names may be trademarks or service marks of others.
28
IBM System Storage N series Operations Manager Sizing Guide