veritas™ operations manager 4.1 installation guide - storage

Veritas™ Operations ManagerInstallation Guide

4.1

January 2013

Veritas™ Operations Manager Installation GuideThe software described in this book is furnished under a license agreement and may be usedonly in accordance with the terms of the agreement.

Product version: 4.1

Documentation version: 4.1.1

Legal NoticeCopyright © 2011 Symantec Corporation. All rights reserved.

Symantec, the Symantec logo, Veritas, and Veritas Storage Foundation are trademarks orregistered trademarks of Symantec Corporation or its affiliates in the U.S. and othercountries. Other names may be trademarks of their respective owners.

This Symantec product may contain third party software for which Symantec is requiredto provide attribution to the third party (“Third Party Programs”). Some of the Third PartyPrograms are available under open source or free software licenses. The License Agreementaccompanying the Software does not alter any rights or obligations you may have underthose open source or free software licenses. Please see the Third Party Legal Notice Appendixto this Documentation or TPIP ReadMe File accompanying this Symantec product for moreinformation on the Third Party Programs.

The product described in this document is distributed under licenses restricting its use,copying, distribution, and decompilation/reverse engineering. No part of this documentmay be reproduced in any form by any means without prior written authorization ofSymantec Corporation and its licensors, if any.

THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS,REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT,ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TOBE LEGALLY INVALID. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTALOR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING,PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINEDIN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.

The Licensed Software and Documentation are deemed to be commercial computer softwareas defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19"Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "Rights inCommercial Computer Software or Commercial Computer Software Documentation", asapplicable, and any successor regulations. Any use, modification, reproduction release,performance, display or disclosure of the Licensed Software and Documentation by the U.S.Government shall be solely in accordance with the terms of this Agreement.

Symantec Corporation350 Ellis StreetMountain View, CA 94043

http://www.symantec.com

http://www.symantec.com

Technical SupportSymantec Technical Support maintains support centers globally. TechnicalSupport’s primary role is to respond to specific queries about product featuresand functionality. The Technical Support group also creates content for our onlineKnowledge Base. The Technical Support group works collaboratively with theother functional areas within Symantec to answer your questions in a timelyfashion. For example, the Technical Support group works with Product Engineeringand Symantec Security Response to provide alerting services and virus definitionupdates.

Symantec’s support offerings include the following:

■ A range of support options that give you the flexibility to select the rightamount of service for any size organization

■ Telephone and/or Web-based support that provides rapid response andup-to-the-minute information

■ Upgrade assurance that delivers software upgrades

■ Global support purchased on a regional business hours or 24 hours a day, 7days a week basis

■ Premium service offerings that include Account Management Services

For information about Symantec’s support offerings, you can visit our Web siteat the following URL:

www.symantec.com/business/support/

All support services will be delivered in accordance with your support agreementand the then-current enterprise technical support policy.

Contacting Technical SupportCustomers with a current support agreement may access Technical Supportinformation at the following URL:


Before contacting Technical Support, make sure you have satisfied the systemrequirements that are listed in your product documentation. Also, you should beat the computer on which the problem occurred, in case it is necessary to replicatethe problem.

When you contact Technical Support, please have the following informationavailable:

■ Product release level



■ Hardware information

■ Available memory, disk space, and NIC information

■ Operating system

■ Version and patch level

■ Network topology

■ Router, gateway, and IP address information

■ Problem description:

■ Error messages and log files

■ Troubleshooting that was performed before contacting Symantec

■ Recent software configuration changes and network changes

Licensing and registrationIf your Symantec product requires registration or a license key, access our technicalsupport Web page at the following URL:


Customer serviceCustomer service information is available at the following URL:


Customer Service is available to assist with non-technical questions, such as thefollowing types of issues:

■ Questions regarding product licensing or serialization

■ Product registration updates, such as address or name changes

■ General product information (features, language availability, local dealers)

■ Latest information about product updates and upgrades

■ Information about upgrade assurance and support contracts

■ Information about the Symantec Buying Programs

■ Advice about Symantec's technical support options

■ Nontechnical presales questions

■ Issues that are related to CD-ROMs or manuals



Support agreement resourcesIf you want to contact Symantec regarding an existing support agreement, pleasecontact the support agreement administration team for your region as follows:

[email protected] and Japan

[email protected], Middle-East, and Africa

[email protected] America and Latin America

About Symantec ConnectSymantec Connect is the peer-to-peer technical community site for Symantec’senterprise customers. Participants can connect and share information with otherproduct users, including creating forum posts, articles, videos, downloads, blogsand suggesting ideas, as well as interact with Symantec product teams andTechnical Support. Content is rated by the community, and members receivereward points for their contributions.

http://www.symantec.com/connect/storage-management

mailto:[email protected]



http://www.symantec.com/connect/storage-management

Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Chapter 1 Planning your Veritas Operations Managerinstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

About Veritas Operations Manager ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11About Management Server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12About the managed host ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12About standalone (unmanaged) host ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Downloading Veritas Operations Manager 4.1 ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Downloading Management Server files ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Downloading managed host files ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Using the product documentation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Host considerations for installing Veritas Operations Manager ... . . . . . . . . . 16Typical Veritas Operations Manager 4.1 deployment

configurations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Centralized management of Storage Foundation and High

Availability 5.x and 4.x hosts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Centralized management of only Storage Foundation and High

Availability 5.x hosts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Standalone management of Storage Foundation 5.x and 4.x

hosts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Centralized management of hosts not having Storage Foundation

and High Availability products ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Veritas Operations Manager 4.1 installation overview .... . . . . . . . . . . . . . . . . . . . . 18Choosing a Management Server host ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Choosing managed hosts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Coexistence of Veritas Operations Manager and Veritas Operations

Manager Advanced .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Chapter 2 System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Operating system requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Third-party required libraries ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

32-bit SNIA Common HBA API required on Windows hosts ... . . . . . . . . . 26System resource requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Contents

About the frequency of managed host informationdiscovery .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Supported hardware .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Web browser requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Network and firewall requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Chapter 3 Installing, upgrading, and uninstalling VeritasOperations Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Packages included in Veritas Operations Manager ... . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Installing Veritas Operations Manager 4.1 Management Server ... . . . . . . . . . 34

Installing Management Server on UNIX .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Installing Management Server on Windows .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Verifying Management Server installation on UNIX .... . . . . . . . . . . . . . . . . . . . . . . . 37Verifying Management Server installation on Windows .... . . . . . . . . . . . . . . . . . . 37Configuring Veritas Operations Manager 4.1 on UNIX and

Windows .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Setting up the Web browser for Veritas Operations Manager ... . . . . . . . . . . . . . 40Installing Veritas Operations Manager 4.1 host management ... . . . . . . . . . . . . 41

Installing host management on UNIX .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Installing host management on Windows .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43About cloning virtual machines ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44About migrating virtual machines ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Installing Veritas Operations Manager 4.1 host management throughSolaris JumpStart ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Verifying host management installation on UNIX .... . . . . . . . . . . . . . . . . . . . . . . . . . . 45Verifying host management installation on Windows .... . . . . . . . . . . . . . . . . . . . . . 46About installing or upgrading Veritas Operations Manager 4.1

Add-ons .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Upgrading Management Server to Veritas Operations Manager

4.1 ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Upgrading Management Server on UNIX .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Upgrading Management Server on Windows .... . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Backing up Veritas Operations Manager 4.1 data on UNIX .... . . . . . . . . . . . . . . . 50Backing up Veritas Operations Manager 4.1 data on Windows .... . . . . . . . . . . 51Upgrading host management to Veritas Operations Manager 4.1 ... . . . . . . . 53

Upgrading managed hosts using the Veritas Operations Managerconsole ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Upgrading host management on UNIX using operating systemcommands .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Upgrading host management on Windows using the installerpackage .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Verifying the version of Management Server in the console ... . . . . . . . . . . . . . . 56

Contents8

Verifying the version of a Veritas Operations Manager managed hostin the console ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Uninstalling Management Server on UNIX .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Uninstalling Management Server on Windows .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Uninstalling host management on UNIX .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Uninstalling host management on Windows .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Chapter 4 Using Veritas Operations Manager in highavailability environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

About configuring Veritas Operations Manager in high availabilityenvironment .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Configuring a new Veritas Operations Manager 4.1 installation inhigh availability environment .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Sample configuration: After you create the base service groups inVeritas Operations Manager ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Sample configuration: After you configure Veritas OperationsManager in high availability environment .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Configuring an existing Veritas Operations Manager 4.1 installationin high availability environment .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

About configuring Veritas Operations Managerin high availabilityenvironment for disaster recovery .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Prerequisites for configuring Veritas Operations Managerin the highavailability environment for disaster recovery .... . . . . . . . . . . . . . . . . . . . . . . . . . 82

Configuring Veritas Operations Manager 4.1 in high availabilityenvironment for disaster recovery .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Sample configuration: After you configure Veritas OperationsManager in high availability environment for disasterrecovery .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

About upgrading the high availability and the disaster recoveryconfigurations to Veritas Operations Manager 4.1 ... . . . . . . . . . . . . . . . . . . . . 93

Upgrading Management Server in high availabilityenvironment .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Removing the high availability configuration .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

9Contents

Contents10

Planning your VeritasOperations Managerinstallation

This chapter includes the following topics:

■ About Veritas Operations Manager

■ Downloading Veritas Operations Manager 4.1

■ Using the product documentation

■ Host considerations for installing Veritas Operations Manager

■ Typical Veritas Operations Manager 4.1 deployment configurations

■ Veritas Operations Manager 4.1 installation overview

■ Choosing a Management Server host

■ Choosing managed hosts

■ Coexistence of Veritas Operations Manager and Veritas Operations ManagerAdvanced

About Veritas Operations ManagerVeritas Operations Manager by Symantec gives you a single, centralizedmanagement console for the Veritas Storage Foundation and High Availabilityproducts. You can use it to monitor, visualize, and manage storage and clusterresources, and generate reports about them. Veritas Operations Manager letsadministrators centrally manage diverse datacenter environments.

1Chapter

You can also use Veritas Operations Manager to manage the hosts, which do nothave Storage Foundation and High Availability products installed on them.

In Veritas Operations Manager, you can establish user credentials such thatauthorized users can access the product to perform sensitive management tasks,and other users can perform only a basic set of functions.

A typical Veritas Operations Manager deployment consists of the following:

■ Management ServerSee “About Management Server” on page 12.

■ Managed hostsSee “About the managed host” on page 12.

For more information on managing security roles and users accounts, see theVeritas Operations Manager Administrator's Guide.

About Management ServerIn a centrally managed deployment, you must configure one host as ManagementServer. Management Server receives information about all the resources in itsdomain. When you log on to Management Server, you can gain access to theresources on different hosts within the centrally-managed deployment.

When you install Management Server, the Web server component is installedautomatically.

You can use the Web server on Management Server to access the managed hostsin the centrally managed deployment. You log on to the Management Server URLand Web server port 14161 (for example, https://myhost.example.com:14161).

See “About Veritas Operations Manager” on page 11.

About the managed hostA typical Veritas Operations Manager deployment consists of Management Serverand at least one managed host.

Typically, a managed host is a production server on which you install and runStorage Foundation and High Availability product components. A typical site canhave thousands of hosts using some or all of the Storage Foundation and HighAvailability products. You can also use Veritas Operations Manager to managehosts on which Storage Foundation, or Storage Foundation and High Availability,are not installed.

In Veritas Operations Manager, Management Server is also configured as amanaged host. You can manage Management Server itself as part of a centralmanagement domain.

Planning your Veritas Operations Manager installationAbout Veritas Operations Manager

12

In a centrally managed deployment, the managed hosts relay information aboutstorage network resources and applications to Management Server. ManagementServer merges the data it receives from the managed hosts within its database.Using this merged data, the Veritas Operations Manager console can presentcentralized views and reports.


About standalone (unmanaged) hostA standalone (unmanaged) host is a Storage Foundation host that has beenconfigured so it does not belong to a central management domain.

To manage individual Storage Foundation hosts, you can install and use theJava-based Veritas Enterprise Administrator. This console lets you manage hostsusing the Storage Foundation products installed on them.

If you want a standalone host to participate in the central management domain,you must update it by installing the Veritas Operations Manager host managementpackage.

Note: You can convert any standalone host to a managed host. However, becauseManagement Server is also a managed host, you cannot configure it to be astandalone host.


Downloading Veritas Operations Manager 4.1See “Downloading Management Server files” on page 13.

See “Downloading managed host files” on page 14.

Downloading Management Server filesTo install or upgrade Veritas Operations Manager Management Server, you needto download a .zip file. The .zip file contains the file that you can run to installManagement Server.

The names of the .zip file and the installer file for each platform are as follows:

■ Linux:

■ Download file name -Veritas_Operations_Manager_Management_Server_4.1_Linux.zip

13Planning your Veritas Operations Manager installationDownloading Veritas Operations Manager 4.1

■ Installer file name - Veritas_Operations_Manager_CMS_4.1_Linux.bin

■ Solaris:

■ Download file name -Veritas_Operations_Manager_Management_Server_4.1_SolSparc.zip

■ Installer file name -Veritas_Operations_Manager_CMS_4.1_SolSparc.bin

■ Windows:

■ Download file name -Veritas_Operations_Manager_Management_Server_4.1_Win.zip

■ Installer file name - Veritas_Operations_Manager_CMS_4.1_Win.exe

See “Installing Veritas Operations Manager 4.1 Management Server” on page 34.

See “Upgrading Management Server to Veritas Operations Manager 4.1”on page 47.

Downloading managed host filesTo install or upgrade host management, you need to download theVeritas_Operations_Manager_Managed_Host_Bundle_4.1.zip file that containsthe packages for all the supported operating systems for managed hosts. You canunzip the file and install the package on the host.

Note:To upgrade a managed host to version Veritas Operations Manager 4.1, youcan choose to use the Deployment Management feature. For more informationon deploying packages, see theVeritasOperationsManagerAdministrator'sGuide.

Table 1-1 provides information on the file that you can use to install the managedhost for each operating system.

Table 1-1 Managed host installation and upgrade files

Installer file name

(xxxx is the build number for the release)

Operatingsystem

VRTSsfmh_4.1.xxxx.0_AIX.bff.ZAIX

■ For HP-UX 11.23 and HP-UX 11.31:VRTSsfmh_4.1.xxxx.0_HP-UX.tar.gz

■ For HP-UX 11.11 with Storage Foundation 3.5:VRTSsfmh_4.1.xxxx.0_HP-UX_osr_B.11.11.tar.gz

HP-UX

Planning your Veritas Operations Manager installationDownloading Veritas Operations Manager 4.1

14

Table 1-1 Managed host installation and upgrade files (continued)

Installer file name

(xxxx is the build number for the release)

Operatingsystem

VRTSsfmh_4.1.xxxx.0_Linux.rpmLinux onx86 orXeon

VRTSsfmh_4.1.xxxx.0_Linux_arch_ppc64.rpmLinux onPowerPC

VRTSsfmh_4.1.xxxx.0_SunOS_arch_sparc.pkgSolaris onSPARC

VRTSsfmh_4.1.xxxx.0_SunOS_arch_i386.pkgSolaris onx86

VRTSsfmh_4.10.xxxx_Windows_arch_x86.msiWindows32-bit

VRTSsfmh_4.10.xxxx_Windows_arch_x64.msiWindows64-bit

VRTSsfmh_4.10.xxxx_Windows_arch_IA64.msiWindowsIA64

See “Installing Veritas Operations Manager 4.1 host management” on page 41.

See “Upgrading host management to Veritas Operations Manager 4.1” on page 53.

Using the product documentationThe following guides provide information about Veritas Operations Manager:

■ Veritas Operations Manager Administrator's Guide

■ Veritas Operations Manager Getting Started Guide

■ Veritas Operations Manager Installation Guide

For complete host operating system and system resource specifications, as wellas any known limitations or issues in this release, see the Veritas OperationsManager Release Notes.

For information about the third-party software that is used in this product, seethe Veritas Operations Manager Third-Party License Agreements.

The latest version of the product documentation is available on the SORT Website at the following URL:

15Planning your Veritas Operations Manager installationUsing the product documentation

https://sort.symantec.com/documents

For the late breaking news that is related to this release, use the followingTechNote:

http://www.symantec.com/docs/TECH157641

Host considerations for installing VeritasOperationsManager

Host considerations for installing and configuring Veritas Operations Managerinclude the following:

■ Before you begin the Veritas Operations Manager installation, ensure that youhave the following information:

■ Administrator accounts and passwords for all target hosts

■ A diagram of your storage network (suggested for your reference)

■ The managed hosts within a central management domain must reportsynchronized universal time clock time (UC/UTC).

■ You must have at least one valid support contract for Storage Foundation andHigh Availability to gain support for Veritas Operations Manager.

Typical Veritas Operations Manager 4.1 deploymentconfigurations

You have several options for deploying Veritas Operations Manager.

If you implement centralized management, a typical full installation of VeritasOperations Manager consists of a single Management Server, multiple managedhosts, and any number of Web consoles. We recommend this form of managementbecause of the advantages you gain from being able to perform managementoperations on multiple hosts across the datacenter.

If you implement traditional, single-host management, you have the followingoptions:

■ Install a "thick" client, the Java-based VEA console.

■ Install a light-weight Web Server that relies on a standard Web browser client.

Only the Java console supports single-host management of both 5.x and 4.xhosts.Only 5.x hosts support the light-weight Web Server.

Typical deployment scenarios include the following:

Planning your Veritas Operations Manager installationHost considerations for installing Veritas Operations Manager

16

https://sort.symantec.com/documents


■ Centralized management of Storage Foundation and High Availability 5.x and4.x hostsSee “Centralized management of Storage Foundation and High Availability5.x and 4.x hosts” on page 17.

■ Centralized management of Storage Foundation and High Availability 5.x hostsonlySee “Centralized management of only Storage Foundation and High Availability5.x hosts” on page 17.

■ Standalone management of Storage Foundation 5.x and 4.x hostsSee “Standalone management of Storage Foundation 5.x and 4.x hosts”on page 18.

■ Centralized management of hosts not having Storage Foundation and HighAvailability productsSee “Centralized management of hosts not having Storage Foundation andHigh Availability products” on page 18.

Centralized management of Storage Foundation and High Availability5.x and 4.x hosts

In this deployment scenario, you centrally manage your Storage Foundation andHigh Availability 5.x and your legacy (4.x) hosts. We recommend this deploymentbecause centralized management offers you the flexibility of performing operationson multiple Storage Foundation and High Availability hosts.

Advantages also include the following:

■ Aggregated information for reporting

■ Performance management across the datacenter

■ Monitoring storage utilization across the datacenter

■ Administration and analysis of all clusters in an enterprise

See “Typical Veritas Operations Manager 4.1 deployment configurations”on page 16.

Centralized management of only Storage Foundation and HighAvailability 5.x hosts

In this deployment scenario, you centrally manage only your Storage Foundationand High Availability 5.x products. You manage your Storage Foundation 4.xhostsindividually using the Java-based Veritas Enterprise Administrator (VEA) console.

17Planning your Veritas Operations Manager installationTypical Veritas Operations Manager 4.1 deployment configurations

Programmatically-aggregated information from multiple hosts is available in theVeritas Operations Manager console, from 5.x managed hosts only.


Standalone management of Storage Foundation 5.x and 4.x hostsIn this deployment scenario, you use the Java-based Veritas EnterpriseAdministrator console to perform traditional, single-host management for StorageFoundation 5.x and any 4.x hosts. Unlike centralized management options,connections to multiple hosts are not concurrent and are independent of eachother. In this scenario, you cannot easily aggregate information from multiplehosts across the datacenter .


Centralized management of hosts not having Storage Foundation andHigh Availability products

In this deployment scenario, you centrally manage those hosts, which do not haveStorage Foundation and High Availability products installed on them.

VeritasOperationsManager 4.1 installation overviewInstalling Veritas Operations Manager involves the following:

■ Reviewing the Veritas Operations Manager architecture and typical deploymentconfigurationsSee “Typical Veritas Operations Manager 4.1 deployment configurations”on page 16.

■ Verifying that you have met system requirementsSee “Operating system requirements” on page 23.See “System resource requirements” on page 27.See “Supported hardware” on page 29.See “Web browser requirements” on page 30.See “Network and firewall requirements” on page 31.

■ Installing and configuring the Veritas Operations Manager Management ServerSee “Installing Veritas Operations Manager 4.1 Management Server”on page 34.

Planning your Veritas Operations Manager installationVeritas Operations Manager 4.1 installation overview

18

See “Configuring Veritas Operations Manager 4.1 on UNIX and Windows”on page 38.

■ Installing Veritas Operations Manager host management on the hosts thatwill be centrally managedSee “Installing Veritas Operations Manager 4.1 host management” on page 41.

Choosing a Management Server hostManagement Server is the central point for collecting and managing theinformation that managed hosts relay back to it.

To identify a host that is appropriate as Management Server, use the followingcriteria:

■ The host should meet or exceed recommended system requirements.See “Operating system requirements” on page 23.See “32-bit SNIA Common HBA API required on Windows hosts” on page 26.See “System resource requirements” on page 27.See “Supported hardware” on page 29.See “Web browser requirements” on page 30.See “Network and firewall requirements” on page 31.

■ The host should provide data security and space for a growing database asManagement Server discovers new managed hosts and monitors networkevents. Ideally, the host should have RAID-protected storage and the capacityto grow its file systems.

■ Clients that connect to Management Server using the Veritas OperationsManager console (Web browser) must be able to access the host.

Choosing managed hostsA typical Veritas Operations Manager deployment consists of a ManagementServer and at least one managed host. The managed host has a Veritas OperationsManager agent that collects component-pertinent status information from networkresources, such as hardware and applications, and relays that information toManagement Server.

For managed hosts not having Storage Foundation or Storage Foundation HighAvailability, the server information may be discovered in two ways:

■ By installing an agent on the managed host

■ By agentless discovery using SSH (for UNIX hosts) or WMI (for Windows hosts)

19Planning your Veritas Operations Manager installationChoosing a Management Server host

Note:Agentless discovery is not supported on hosts that have Storage Foundationor Storage Foundation High Availability installed.

The types of managed hosts are the following:

■ Hosts with Storage Foundation 4.x, or later, on all supported platforms

■ Hosts with Storage Foundation and High Availability 3.5 on HP-UX

■ Hosts with Storage Foundation and High Availability 4.x, or later, on allsupported platforms

■ Hosts that do not have Storage Foundation, or Storage Foundation and HighAvailability installed on the supported platforms

For more information on agent and agentless hosts, see the Veritas OperationsManager Administrator's Guide.

Before you install a managed host, make sure that it meets or exceeds therecommended system requirements.

See “Operating system requirements” on page 23.

Coexistence of Veritas Operations Manager andVeritas Operations Manager Advanced

If you plan to install both Veritas Operations Manager and Veritas OperationsManager Advanced on a single host, you need to check the support for coexistenceof both the products. Only certain versions of Veritas Operations Manager can beinstalled with certain versions of Veritas Operations Manager Advanced. Thecoexistence support also depends on the sequence in which the products areinstalled.

Table 1-2 describes the coexistence support when Veritas Operations Manager isinstalled before Veritas Operations Manager Advanced:

Table 1-2 Coexistence support when Veritas Operations Manager is installedfirst

Supported Veritas Operations ManagerAdvanced version

VeritasOperationsManager version onthe host

None4.0, or lower versions

4.04.0 RU1

4.0 RU14.1

Planning your Veritas Operations Manager installationCoexistence of Veritas Operations Manager and Veritas Operations Manager Advanced

20

Table 1-3 describes the coexistence support when Veritas Operations ManagerAdvanced is installed before Veritas Operations Manager:

Table 1-3 Coexistence support when Veritas Operations Manager Advancedis installed first

Supported Veritas Operations Managerversion

Veritas Operations Manager Advancedversion on the host

4.0 RU1, or later versions4.0

4.14.0 RU1

21Planning your Veritas Operations Manager installationCoexistence of Veritas Operations Manager and Veritas Operations Manager Advanced

Planning your Veritas Operations Manager installationCoexistence of Veritas Operations Manager and Veritas Operations Manager Advanced

22

System requirements


■ Operating system requirements

■ Third-party required libraries

■ System resource requirements

■ Supported hardware

■ Web browser requirements

■ Network and firewall requirements

Operating system requirementsTable 2-1 provides an overview of Veritas Operations Manager operating systemrequirements for Management Server:

2Chapter

Table 2-1 Veritas Operations Manager operating system requirements forManagement Server

NotesOperating system supported

x86 64-bit is the supported architecture.

For RHEL 6.0 on x86 64-bit, and RHEL 6.1on x86 64-bit, the 32-bit glibc packagemust be installed.

Red Hat Enterprise Linux 4.0 Update 3

Red Hat Enterprise Linux 5.0

Red Hat Enterprise Linux 5.1 Update 1





Red Hat Enterprise Linux 6


x86 64-bit is the supported architecture.SUSE Linux Enterprise Server 9

SUSE Linux Enterprise Server 10

SPARC is the supported architecture.Solaris 10

x86 64-bit is the supported architecture.Windows 2003

Windows 2008

Windows 2008 R2

Table 2-2 provides an overview of Veritas Operations Manager operating systemrequirements for managed hosts:

Table 2-2 Veritas Operations Manager operating system requirements formanaged hosts having Storage Foundation or Storage Foundationand High Availability products


On AIX hosts, the xlC runtime environmentmust be version 8.0, or later. Use the lslpp-lc | grep xlC.rte command to verifythe version of the xlC runtime environment.

AIX 5.2

AIX 5.3

AIX 6.1 (only for hosts with StorageFoundation 5.0 MP3, or later)

AIX 7.1 (only for Storage Foundation 5.1 SP1PR1 hosts)

PA RISC is the supported architecture.HP-UX 11.11 (only for Storage Foundation3.5 hosts)

System requirementsOperating system requirements

24

Table 2-2 Veritas Operations Manager operating system requirements formanaged hosts having Storage Foundation or Storage Foundationand High Availability products (continued)


HP-UX 11.23

HP-UX 11.31

On Red Hat Enterprise Linux 4.0, StorageFoundation 5.0 is supported on 64-bit Xeon,x86, and PowerPC; Storage Foundation 4.1is supported on x86 and Xeon (32- and64-bit).

For RHEL 6.0 on x86 64-bit, and RHEL 6.1on x86 64-bit, the 32-bit glibc packagemust be installed.


Red Hat Enterprise Linux 5.0 Update 2 (onlyfor hosts with Storage Foundation 5.0 MP3,or later)

Red Hat Enterprise Linux 6


On SUSE Linux Enterprise Server 9, StorageFoundation 5.0 is supported on 64-bit Xeon,x86, and PowerPC; Storage Foundation 4.1is supported on x86 and Xeon (32- and64-bit).

SUSE Linux Enterprise Server 9

SUSE Linux Enterprise Server 10 (only forhosts with Storage Foundation 5.0 MP3, orlater)

SUSE Linux Enterprise Server 11 (only forhosts with Storage Foundation 5.0 MP3, orlater)

Solaris 8

Solaris 9

Solaris 10 SPARC

Solaris 10 x86

Supported on x86, x64, and IA64.Windows Server 2003

Windows Server 2008

Windows 2008 R2

Veritas Operations Manager operating system requirements for managed hoststhat do not have Storage Foundation or Storage Foundation and High Availabilityproducts:

■ AIX 5.2, or later

■ HP-UX 11.23, or later

■ Red Hat Enterprise Linux 4.x, or later

25System requirementsOperating system requirements

■ SUSE Linux Enterprise Server 9, or later

■ Solaris 9

■ Solaris 10 SPARC

■ Solaris 10 x86

■ Windows Server 2003

■ Windows Server 2008

■ Windows Server 2008 R2

For the most complete, up-to-date platform support documentation for StorageFoundation (UNIX) and Storage Foundation HA for Windows, visit the SymantecTechnical Support Web site :

www.symantec.com/techsupp/

Third-party required librariesThis section lists third-party libraries required to run Veritas Operations Manager:

■ 32-bit SNIA Common HBA API required on Windows hosts

32-bit SNIA Common HBA API required on Windows hostsFor proper discovery of Fibre Channel attached devices—including discovery ofHBA and its target ports—Veritas Operations Manager requires installation of the32-bit SNIA Common HBA API on all Windows managed hosts running HBAcontrollers.

The Common HBA API is typically available as part of your HBA vendor’s driverkit, or you can download it from your HBA vendor’s site.

Follow these steps to determine if the SNIA Common HBA API is already presenton your Windows host.

To verify that the 32-bit SNIA Common HBA API is installed on a Windows host

1 Open the registry editor on the managed host using the regedit command.

2 Check the following location to get the SNIA library information:

HKEY_LOCAL_MACHINE\SOFTWARE\SNIA\HBA\hba_model

On 64-bit platforms, Veritas Operations Manager requires 32-bit libraries installedas a pre-requisite. For more information, see your HBA vendor documentation.

System requirementsThird-party required libraries

26

www.symantec.com/techsupp/

System resource requirementsThe amount of memory and disk space that Veritas Operations Manager requiresare listed in this section. The requirements are in addition to the resources thatare already consumed by other software applications running on the host.

For Management Server:

■ CPU required: Dual processor for every 1000 managed hosts.

■ Memory required:

■ 4GB for every 1000 managed hosts.

■ Add 4GB of memory if Management Server is used for the deep discoveryof enclosures using the Storage Insight Add-on.

■ Add 4GB of memory if Management Server is used for the discovery ofVMware virtualization infrastructure.

■ Disk space required: 15GB of disk space for every 1000 managed hosts.

For a managed host:

■ CPU required: See Veritas Storage Foundation documentation.

■ Memory required: See Veritas Storage Foundation documentation.

■ Disk space required:

■ On UNIX hosts: 50MB to 200MB in/var/opt for discovery state files; 100MBin /opt.

■ On Windows hosts: 50MB to 200MB in Install_path\Veritas\VRTSsfmh;100MB in %COMMONAPPDATAFOLDER%\Symantec.

Read the following Symantec Technical Support TechNotes for the latestinformation on updates, patches, and software issues regarding this release:


See “About the frequency of managed host information discovery” on page 27.

About the frequency of managed host information discoveryThe following table describes the frequency of the managed host informationupdates in the Management Server database. The discovery on each managedhost is divided into families to focus on a particular functional area:

27System requirementsSystem resource requirements


Discovered informationFrequencyin minutes

Family

The operating system, packages, and networking for the host.

Typically, most of the information that is related to this familydoes not change frequently.

1440Host

Volume Manager, File Systems, and the related storagenetwork.

30SF

Veritas Cluster Server and the related information.60VCS

Oracle, DB2, MSSQL, and Sybase databases and their storagedependencies.

60DB

The licenses that are installed on the hosts.1440LDR

Configuration status and external faults.5NR

Third-party volume management information.360Native

Oracle Solaris zones and their storage dependencies.120Zones

Oracle Solaris LDoms, and related CPU and memoryinformation.

120LDoms

ESX servers, virtual machines, and their storage dependencies.

Note:This information is discovered only when Control HostAdd-on is installed on a managed host that is designated asthe control host.

360VMware

System requirementsSystem resource requirements

28

Discovered informationFrequencyin minutes

Family

The following information on the hosts that are configuredon the control host for agentless:

■ The IP addresses, operating system, and the usage of theCPU and memory

■ The host bus adapters (HBAs) on the host

■ The disks on the hosts and their correlation with the arrayLUNs and multipathing

■ The volumes and the volume groups on the native VolumeManager

■ The mount points of the file systems and the correlationof the file systems with the disks

■ In a VMware guest environment, the correlation of theguest with the virtual machine and the correlation of thestorage in the guest with the storage exported from theESX server.

Note:This information is discovered only when Control HostAdd-on is installed on a managed host that is designated asthe control host.

360Agentless

Note:The discovery for the Storage Foundation and Veritas Cluster Server familiesis event driven and scheduled. This means that the discovery is triggered whenconfiguration changes occur on the managed hosts. As a result, this informationmust be updated in the Veritas Operations Manager database in the followingupdate. If configuration changes are not detected on the managed hosts, thecommunication between the managed host and Management Server is restrictedto the heartbeat communication that occurs every five minutes. You can connecta managed host to multiple Management Servers. The performance of a managedhost is not affected in this scenario because the discovery happens only once.Reporting of the state as per the host configuration is done based on the numberof Management Servers to which the managed host reports.

Supported hardwareThe following TechNotes contain the Hardware Compatibility List (HCL) for VeritasOperations Manager 4.1 and Storage Foundation products on UNIX:

■ Storage Foundation 5.0 for UNIX:http://www.symantec.com/business/support/index?page=content&id=TECH47620

29System requirementsSupported hardware

http://www.symantec.com/business/support/index?page=content&id=TECH47620

■ Storage Foundation 5.1 for UNIX:http://www.symantec.com/business/support/index?page=content&id=TECH74012

The following TechNotes contain the Hardware Compatibility List (HCL) for VeritasOperations Manager 4.1 and Storage Foundation products on Windows:

■ Storage Foundation 5.0 for Windows:http://www.symantec.com/business/support/index?page=content&id=TECH50141

■ Storage Foundation 5.1 for Windows:http://www.symantec.com/business/support/index?page=content&id=TECH59118

Web browser requirementsThe Veritas Operations Manager console is a graphical user interface that displaysreports and other information for users of the Storage Foundation productsthrough a standard Web browser.

The Web browsers that the Veritas Operations Manager console supports are:

■ Internet Explorer versions 6.x to 9.x

■ Firefox 3.x, or later

Additional considerations for supported Web browsers:

■ Your browser must support JavaScript 1.2, or later.

■ If you use pop-up blockers (including Yahoo Toolbar or Google Toolbar), eitherdisable them or configure them to accept pop-ups from the Veritas OperationsManager Web server to which you connect.

■ For Internet Explorer 6.0 on Windows 2003 (Server and Advanced Server), setthe default intranet zone security level to Medium, or lower.

■ For Internet Explorer, when popup-blocker is turned on, make sure that thefilter level is set to Medium or lower.

■ For Internet Explorer, ensure that the site is incuded in the list of trusted sites.If you cannot add the site to the list of trusted sites, enable the Binary andscript Behaviors option in security settings.

■ You must install Adobe Flash plug-in version 10, or later.

Use the following criteria to identify the kind of system you need to run the Webconsole:

■ The Web console host must be able to access Veritas Operations ManagerManagement Server.

■ Veritas Operations Manager must support the Web browser.

System requirementsWeb browser requirements

30




Network and firewall requirementsIf you plan to manage hosts within multiple domains, update the network settingsto resolve the host from all domains.

You need to ensure that the localhost can be resolved from the host.

If localhost cannot be resolved from the host, update your network settings toenable it.

Veritas Operations Manager uses the default ports as shown in Table 2-3 to transferinformation.

Table 2-3 Default ports in an Veritas Operations Manager installation

Effect if blockedPurposeInitiatorProtocolPort

ManagementServer cannot beconfigured.

ManagementServerconfiguration

ManagementServer

TCP5634

Managed hostcannot be addedto theManagementServer domain.

ManagementServercommunicationswith the managedhosts

Managed hostcannot be addedto theManagementServer domain.

Managed host tosend heartbeats;also used toupload the datafrom the managedhost toManagementServer

Note: Werecommend thatyou keep port5634 openbetween managedhosts forscalability andperformanceoptimization.

managed hosts

31System requirementsNetwork and firewall requirements

Table 2-3 Default ports in an Veritas Operations Manager installation(continued)

Effect if blockedPurposeInitiatorProtocolPort

Users cannotaccess theManagementServer console.

Run theManagementServer console

Web consoleTCP14161

System requirementsNetwork and firewall requirements

32

Installing, upgrading, anduninstalling VeritasOperations Manager


■ Packages included in Veritas Operations Manager

■ Installing Veritas Operations Manager 4.1 Management Server

■ Verifying Management Server installation on UNIX

■ Verifying Management Server installation on Windows

■ Configuring Veritas Operations Manager 4.1 on UNIX and Windows

■ Setting up the Web browser for Veritas Operations Manager

■ Installing Veritas Operations Manager 4.1 host management

■ Installing Veritas Operations Manager 4.1 host management through SolarisJumpStart

■ Verifying host management installation on UNIX

■ Verifying host management installation on Windows

■ About installing or upgrading Veritas Operations Manager 4.1 Add-ons

■ Upgrading Management Server to Veritas Operations Manager 4.1

■ Backing up Veritas Operations Manager 4.1 data on UNIX

■ Backing up Veritas Operations Manager 4.1 data on Windows

3Chapter

■ Upgrading host management to Veritas Operations Manager 4.1

■ Verifying the version of Management Server in the console

■ Verifying the version of a Veritas Operations Manager managed host in theconsole

■ Uninstalling Management Server on UNIX

■ Uninstalling Management Server on Windows

■ Uninstalling host management on UNIX

■ Uninstalling host management on Windows

Packages included in Veritas Operations ManagerTable 3-1 lists the software packages that are included in Veritas OperationsManager.

Table 3-1 Software packages

DescriptionPackage name

Veritas Operations Manager package that is required onManagement Server

VRTSsfmcs

Veritas Operations Manager package that is required on themanaged host

VRTSsfmh

See “Downloading Veritas Operations Manager 4.1” on page 13.

Installing Veritas Operations Manager 4.1Management Server

You can install Management Server on any one of the following hosts:

■ A Linux host

■ A Solaris host

■ A Windows host

After you install Management Server, you have to configure Veritas OperationsManager before you can use it.

For information on system requirements, see the Veritas Operations ManagerRelease Notes.

Installing, upgrading, and uninstalling Veritas Operations ManagerPackages included in Veritas Operations Manager

34

See “Installing Management Server on UNIX” on page 35.

See “Installing Management Server on Windows” on page 36.

Installing Management Server on UNIXYou can install the Veritas Operations Manager Management Server on a Linuxhost or a Solaris host using a .bin file. The .bin file installs the VRTSsfmcs andthe VRTSsfmh packages on the target host.

Note: On a Solaris host, you can install Management Server on both global andnon-global zones.

To install Veritas Operations Manager Management Server on UNIX

1 Make sure that the host where you plan to install Management Server meetsor exceeds system and operating system requirements.

For information on system requirements, see theVeritasOperationsManager4.1 Release Notes.

See “Choosing a Management Server host” on page 19.

2 Download and unzip the installation file.


3 Open an operating system console.

4 On the host where you plan to install Management Server, log on as root.

5 Change directory to the location where you unzipped the .bin file.

6 At the command prompt, enter one of the following:

■ On a Linux host:./Veritas_Operations_Manager_CMS_4.1_Linux.bin

■ On a Solaris host:./Veritas_Operations_Manager_CMS_4.1_SolSparc.bin

If you see the error Permission Denied, change the permissions for the .binfile so that it can be run. Enter one of the following:

■ On a Linux host:chmod +x Veritas_Operations_Manager_CMS_4.1_Linux.bin

■ On a Solaris host:chmod +x Veritas_Operations_Manager_CMS_4.1_SolSparc.bin

35Installing, upgrading, and uninstalling Veritas Operations ManagerInstalling Veritas Operations Manager 4.1 Management Server

7 To accept the End User License Agreement and proceed with installation,type y.

The installation is complete when you see messages similar to the following:

Installation is complete. You will need to configure Veritas

Operations Manager Management Server.

Please open your browser and type the following URL to configure:

https://myhost.example.com:5634/

Please skip this step if you intend to use this host as a standby

node for Veritas Operations Manager Management Server HA.

8 Verify that the packages are installed and the processes are started.

See “Verifying Management Server installation on UNIX” on page 37.

9 Configure Veritas Operations Manager.


Installing Management Server on WindowsYou can install the Veritas Operations Manager Management Server on a Windowshost using the Veritas_Operations_Manager_CMS_4.1_Win.exe file.

To install Veritas Operations Manager Management Server on Windows

1 Make sure that the host where you plan to install Management Server meetsor exceeds system and operating system requirements.

For information on system requirements, see theVeritasOperationsManagerRelease Notes.

See “Choosing a Management Server host” on page 19.

2 On the host where you plan to install Management Server, log on as a userwith administrator privileges.



4 Turn off the Windows firewall, or, open ports 5634 and 14161 for TCP/IPcommunication.

5 Ensure that there is no pending restart from Windows Update. If there is,restart the host before launching the installer.

6 To launch the installer, run theVeritas_Operations_Manager_CMS_4.1_Win.exe file.

Installing, upgrading, and uninstalling Veritas Operations ManagerInstalling Veritas Operations Manager 4.1 Management Server

36

7 To proceed with the Management Server installation, accept the End UserLicense Agreement.

8 Click Install and follow through the installation process.

9 After the installation is complete, click Finish.

The Web browser is launched to configure Veritas Operations Manager.

10 Configure Veritas Operations Manager.


11 Verify that Management Server is installed and the required services arestarted.

See “Verifying Management Server installation on Windows” on page 37.

Verifying Management Server installation on UNIXYou can verify the Management Server installation by making sure that thepackages are installed and the required processes are started.

To verify Management Server installation on UNIX

1 On the host where you installed Management Server, check whether theVRTSsfmcs package is installed. Enter one of the following:

■ On a Linux host: rpm -q VRTSsfmcs

■ On a Solaris host: pkginfo -l VRTSsfmcs

2 Check whether the VRTSsfmh package is installed. Enter one of the following:

■ On a Linux host: rpm -q VRTSsfmh

■ On a Solaris host: pkginfo -l VRTSsfmh

3 Check whether the xprtld process is started. Enter the following:

ps -ef | grep xprtld

See “Verifying the version of Management Server in the console” on page 56.

VerifyingManagementServer installationonWindowsYou can verify the Management Server installation by making sure that the VeritasOperations Manager for Windows program is installed, and the Veritas StorageFoundation Messaging Service is started.

37Installing, upgrading, and uninstalling Veritas Operations ManagerVerifying Management Server installation on UNIX

To verify Management Server installation on Windows

1 On the host where you installed host management, on the Windows ControlPanel, click Add or Remove Programs.

2 Check whether VeritasOperationsManagerforWindows appears in the listof installed programs.

3 On the Windows Services panel, check whether the Veritas StorageFoundation Messaging Service has started.


Configuring Veritas OperationsManager 4.1 on UNIXand Windows

If you are installing Management Server on a UNIX host, messages similar to thefollowing are displayed after successful installation of Management Server:

Installation is complete. You will need to configure Veritas

Operations Manager.

Please open your browser and type the following URL to configure:

https://myhost.example.com:5634/

Use the URL displayed in the message to configure Veritas Operations Manager.

Note: You may configure the networking on Management Server in either theIPv4 mode, or in the mixed mode (IPv4 and IPv6). For Management Server thatruns in the mixed mode, use only the IPv4 address during the installation andconfiguration process and not the IPv6 address.

If you are installing Management Server on a Windows host, the Web browser isautomatically launched with the URL to configure Veritas Operations Manager.For Internet Explorer 7.0, or later, on Windows Server 2008, or Firefox 3.0, orlater, if the Web page does not get displayed, you have to set up the Web browser.

See “Setting up the Web browser for Veritas Operations Manager” on page 40.

During the configuration, you are prompted to specify a location to store theVeritas Operations Manager database. You can accept the default location orspecify your own.

Installing, upgrading, and uninstalling Veritas Operations ManagerConfiguring Veritas Operations Manager 4.1 on UNIX and Windows

38

Note: For Management Server configuration with IPv6 address, the localhost,127.0.0.1, ::1 should be bound to a network interface (for example, lo0 on Solarisand Linux), and lo0 is up and running.

To configure Veritas Operations Manager on UNIX and Windows

1 Do the following tasks to launch the Web browser. If you are configuringVeritas Operations Manager on a Windows host, skip this step.

■ On a host that has a network connection to the Management Server host,open a Web browser.

■ In the Web browser’s address field, type the following URL and pressEnter:https://hostname:5634/where hostname is the Management Server's host name, fully-qualifiedhost name, or IP address. This is applicable for IPv4 mode. For dual mode(IPv4 and IPv6 mode) configuration, you can give only the host name. Forexample: https://myhost.example.com:5634/For the dual mode of Management Server, the IPv6 address and thehostname entries of the managed hosts should be present in ManagementServer's /etc/hosts file. Also, all the managed hosts should have an entryof the IPv6 address and the host name of Management Server in theirrespective /etc/hosts file.

2 In the AuthenticationRequired dialog, enter Management Server host's rootuser name and password.

3 In the Server Setting page, check and modify the Server Name, if required.

4 Check and modify the Server Address, if required.

5 In the DatabaseSetting page, check the default Databaselocation and modifyit, if required.

The default database directory is /var/opt/VRTSsfmcs/db on UNIX,%ALLUSERSPROFILE%\Application Data\Symantec\VRTSsfmcs\dbon Windows2003, and %ALLUSERSPROFILE%\Symantec\VRTSsfmcs\db on Windows2008/2008 R2.

6 Click Next.

7 In the Analytics Setting page, select Enable Analytics Gathering to allowSymantec to gather data on your Veritas Operations Manager usage.

8 Do one of the following:

■ To change settings, click Back,

39Installing, upgrading, and uninstalling Veritas Operations ManagerConfiguring Veritas Operations Manager 4.1 on UNIX and Windows

■ To start the configuration, click Finish.

At the end of the Veritas Operations Manager configuration, messages similarto the following are displayed:

Configuration successful

Click the Launch Web Console button to login.

9 Click Launch Web Console to log on to Veritas Operations Manager on theconfigured Management Server host.



See “About configuring Veritas Operations Manager in high availabilityenvironment” on page 62.

Setting up the Web browser for Veritas OperationsManager

If you use Internet Explorer 7.0, or later, on Windows Server 2008, or Firefox 3.0,or later, the Web pages for configuring and launching Veritas Operations Managerare not displayed. You need to set up the Web browser to display the Web pages.For Internet Explorer 7.0, or later, on Windows Server 2008, if the Web pages arenot automatically displayed, add each Web site to the TrustedSites list. On Firefox3.0, or later, if a security exception is displayed, add the exception to the Webbrowser to override how Firefox identifies the sites.

To set up Internet Explorer 7.0, or later, on Windows Server 2008 for VeritasOperations Manager

1 In Internet Explorer, select Tools > Internet Options.

2 Select the Security tab.

3 Click Sites to add the following Web sites:

■ https://hostname:5634/—URL to configure Veritas Operations Manager

■ https://hostname:14161/—URL to launch Veritas Operations Manager

where, hostname is the name of the Management Server host.

Installing, upgrading, and uninstalling Veritas Operations ManagerSetting up the Web browser for Veritas Operations Manager

40

To set up Firefox 3.0, or later, for Veritas Operations Manager

1 On the security exception page that is displayed when you attempt to openan Veritas Operations Manager Web page, click the Or you can add anexception link.

2 Click Add Exception.

For Firefox 3.6.x, or later, the users should first click the I Understand theRisks button before they click the Add Exception button.

3 In the Add Security Exception dialog, verify that the location is one of thefollowing:

■ https://hostname:5634/—URL to configure Veritas Operations Manager

■ https://hostname:14161/—URL to launch Veritas Operations Manager

where, hostname is the name of the Management Server host.

4 Click Get Certificate.

5 Select the Permanently store this exception check box.

6 Click Confirm Security Exception.

The Web page is now displayed.


Installing Veritas Operations Manager 4.1 hostmanagement

You must install the VRTSsfmh package on a host so you can manage it usingVeritas Operations Manager Management Server.

Three varieties of managed hosts are supported in Veritas Operations Manager:a Storage Foundation 5.x managed host, a Storage Foundation 4.xmanaged host,or a Storage Foundation 3.5 managed host on HP-UX.

After you install the VRTSsfmh package on the host, you need to add the host tothe Management Server domain. You can add the host using the Veritas OperationsManager console, or the gendeploy.pl script.

For more information on adding hosts to a Management Server domain, see theVeritas Operations Manager Administrator's Guide.

For information on system requirements, see the Veritas Operations ManagerRelease Notes.

41Installing, upgrading, and uninstalling Veritas Operations ManagerInstalling Veritas Operations Manager 4.1 host management

See “Installing host management on UNIX” on page 42.

See “Installing host management on Windows” on page 43.

See “About cloning virtual machines” on page 44.

See “About migrating virtual machines” on page 44.

Installing host management on UNIXYou can install Veritas Operations Manager host management on a UNIX host byinstalling the VRTSsfmh package on it.

Note: By default, the VRTSsfmh package is installed in the /opt directory. Youcannot specify a different location to install the package.

To install Veritas Operations Manager host management on a UNIX host

1 Make sure that the host where you plan to install host management meetsor exceeds system and operating system requirements.


2 Download the managed host installation files bundle, and unzip it.



4 On the host where you plan to install host management, log on as root.

5 Change directory to the location where you unzipped the installation filesbundle.

If the host is an AIX host, or an HP-UX host, decompress the downloaded file.


6 At the command prompt, enter one of the following commands to install thepackage:

■ For AIX, enter the following:installp -ac -d VRTSsfmh_4.1.xxxx.0_AIX.bff VRTSsfmh

where, xxxx is the build number for the release.

■ For HP-UX, enter the following:swinstall -s $PWD VRTSsfmh

■ For Linux on x86 or Xeon, enter the following:rpm -ivh VRTSsfmh_4.1.xxxx.0_Linux.rpm


Installing, upgrading, and uninstalling Veritas Operations ManagerInstalling Veritas Operations Manager 4.1 host management

42

■ For Linux on PowerPC, enter the following:rpm -ivh VRTSsfmh_4.1.xxxx.0_Linux_arch_ppc64.rpm


■ For Solaris on SPARC, enter the following:pkgadd -d VRTSsfmh_4.1.xxxx.0_SunOS_arch_sparc.pkg


■ For Solaris on x86, enter the following:pkgadd -d VRTSsfmh_4.1.xxxx.0_SunOS_arch_i386.pkg


7 Verify that the VRTSsfmhpackage is installed and the required processes havestarted.

See “Verifying host management installation on UNIX” on page 45.

Installing host management on WindowsYou can install Veritas Operations Manager host management on a Windows hostby running a .msi file on it.

To install Veritas Operations Manager host management on a Windows host

1 Log on to the target host as a user with administrator privileges.

2 Make sure that the host where you plan to install host management meetsor exceeds system and operating system requirements.




4 From the directory to which you unzipped the installation files bundle, doone of the following:

■ On a 32-bit host, run VRTSsfmh_4.10.xxxx_Windows_arch_x86.msi


■ On a IA64 host, run VRTSsfmh_4.10.xxxx_Windows_arch_IA64.msi



5 On the Welcome screen of the InstallShield Wizard, click Next.

6 On the Ready to Install the Program screen, click Install to start theinstallation.

43Installing, upgrading, and uninstalling Veritas Operations ManagerInstalling Veritas Operations Manager 4.1 host management

7 Click Finish to exit the InstallShield Wizard.

8 Verify that the host management program is installed and the required servicehas started.

See “Verifying host management installation on Windows” on page 46.

About cloning virtual machinesVRTSsfmh package generates a globally unique identifier for the host usingparameters such as host id and MAC address of the host. Veritas OperationsManager Management Server identifies a managed host using this identifier.

Some virtualization technologies such as VMware create a new BIOS UUID for aVirtual Machine when it is cloned. The Veritas Operations Manager Agent(VRTSsfmh package) uses this UUID to know if the host has been cloned.

On other virtualization technologies, you need to reset the host id of the clone isreset. If host id is not reset, both the clone and the cloned hosts are recognizedas the same, which can cause data corruption in the Veritas Operations Managerdatabase. After you reset the host id of the clone, Veritas Operations Managerremoves any managed host-related configuration from the clone that gets copiedover from the cloned host. The clone is treated as a new host and has to be addedas a managed host to the Management Server domain.

About migrating virtual machinesWhen the VRTSsfmh package is installed on a host, it generates a globally uniqueidentifier for the host. Veritas Operations Manager Management Server identifiesa managed host using this identifier. Veritas Operations Manager generates thisunique identifier using parameters such as host id and MAC address of the host.

Veritas Operations Manager tries to maintain the same identifier for the host incase the host is migrated.

On some virtualization technologies such as LPAR or LDOM, the MAC address ofthe host changes when it is migrated. You need to ensure that Veritas OperationsManager uses the same identifier for a managed host even when it is migrated.For this purpose, you need to ensure that the host id of the virtual machine doesnot change after migration. In most of the virtualization technologies, host id ofthe virtual machine remains the same after migration.

Exception to this is LDOM, where, if host id is not explicitly set for an LDOM guest(using the command ldm set-domain), then the host id changes after migrationof the Virtual Machine. It causes VRTSsfmh package to regenerate the uniquehost identifier and the current configuration of the managed host is lost. In such

Installing, upgrading, and uninstalling Veritas Operations ManagerInstalling Veritas Operations Manager 4.1 host management

44

cases, the managed host can no longer actively report data to the VeritasOperations Manager Management Server.

Installing Veritas Operations Manager 4.1 hostmanagement through Solaris JumpStart

You can install host management and add a managed host to the domain throughSolaris JumpStart installation without any user interaction. You can use thegendeploy.pl script to create a script that adds the host to the ManagementServer domain. The script that is generated by gendeploy.pl can be included inthe finalized stages of the Solaris JumpStart installation process.

The following are the highlights of installing Veritas Operations Manager hostmanagement as a part of the Solaris JumpStart installation:

■ Use the gendeploy.pl script to create a script that adds the host to theManagement Server domain.

■ In the finalized stages of the Solaris JumpStart installation, run the script thatis created through gendeploy.pl.

To create the script to be used for adding the hosts in Solaris JumpStart installation

1 Log on as root on Management Server.

2 Run gendeploy.pl to create the script file:

/opt/VRTSsfmh/bin/gendeploy.pl --out scriptfilename

where, scriptfilename is the name of the script file that has to be copied tothe managed host, and then run to add the host to the Management Serverdomain.

See the Veritas OperationsManager Administrator's Guide for more informationon adding hosts to a Management Server domain.

Verifying host management installation on UNIXYou can verify host management installation on UNIX by making sure that theVRTSsfmh package is installed, and the required processes are started.

To verify host management installation on UNIX

1 On the host where you installed host management, enter one of the followingat the command prompt to verify that the package is installed:

■ On AIX, enter the following:lslpp -l VRTSsfmh

45Installing, upgrading, and uninstalling Veritas Operations ManagerInstalling Veritas Operations Manager 4.1 host management through Solaris JumpStart

■ On HP-UX, enter the following:swlist VRTSsfmh

■ On Linux, enter the following:rpm -q VRTSsfmh

■ On Solaris, enter the following:pkginfo -l VRTSsfmh

2 Check whether the xprtld process is started. Enter the following:

ps -ef | grep xprtld

3 Check whether the vxdclid process is started. Enter the following:

ps -ef | grep vxdclid

See “Verifying the version of a Veritas Operations Manager managed host in theconsole” on page 57.

See “Installing host management on UNIX” on page 42.

Verifying host management installation onWindowsYou can verify host management installation on Windows by making sure thatthe Veritas Operations Manager for Windows program is installed, and the StorageFoundation Messaging Service is started.

To verify host management installation on Windows

1 On the host where you installed host management, launch the WindowsControl Panel, and click Add or Remove Programs.

2 Check whether Veritas Operations Manager (Host Component) appears inthe list of installed programs.

3 On the Windows Services panel, check whether the Veritas StorageFoundation Messaging Service has started.


See “Installing host management on Windows” on page 43.

Installing, upgrading, and uninstalling Veritas Operations ManagerVerifying host management installation on Windows

46

About installing or upgrading Veritas OperationsManager 4.1 Add-ons

Veritas Operations Manager Add-ons are independent optional feature packs thatyou can deploy on managed hosts. Add-ons are independent of each other, andthey can be installed or uninstalled based on your business requirements.

Add-ons are installed on Management Server and are deployed from there on themanaged hosts. Some add-ons are installed on Management Server duringManagement Server installation.

If you have upgraded to Veritas Operations Manager 4.1 from a previous versionof Veritas Operations Manager, you may need to upgrade the add-ons. The previousversion of the add-on may not be supported with Veritas Operations Manager 4.1.

For more information on the versions of the add-ons that are supported in VeritasOperations Manager 4.1, see the Veritas Operations Manager Hardware andSoftware Compatibility List(HSCL).

You can download the latest available add-ons to Management Server from thefollowing URL:

http://www.symantec.com/sfm_addons

For more information on deploying add-ons, see the Veritas OperationsManagerAdministrator's Guide.

UpgradingManagement Server to VeritasOperationsManager 4.1

To upgrade your existing Management Server installation to Veritas OperationsManager 4.1, you have to download and install the required packages. You canupgrade to Veritas Operations Manager 4.1 from version 3.x, and from version4.x.

Note: To upgrade to Veritas Operations Manager 4.1 from version 2.x, you needto first upgrade to version 3.x, or 4.x. Then, you can upgrade to version 4.1.

You can upgrade Management Server on Linux, Solaris, and Windows hosts.


See “Upgrading Management Server on UNIX” on page 48.

See “Upgrading Management Server on Windows” on page 49.

47Installing, upgrading, and uninstalling Veritas Operations ManagerAbout installing or upgrading Veritas Operations Manager 4.1 Add-ons

http://www.symantec.com/sfm_addons

See “Backing up Veritas Operations Manager 4.1 data on UNIX” on page 50.

See “Backing up Veritas Operations Manager 4.1 data on Windows” on page 51.

Upgrading Management Server on UNIXYou can upgrade an existing Management Server on a Linux host or a Solaris hostto Veritas Operations Manager 4.1 using a .bin file. When you run the .bin file,the installer first attempts to upgrade the Veritas Operations Manager databaseto a temporary location. If the database upgrade is successful, the remaining stepsin the upgrade process are carried out. If the database upgrade fails, the previousversion of Veritas Operations Manager is restored.

Before you upgrade Management Server, Symantec recommends that you take abackup of the Management Server data.

See “Backing up Veritas Operations Manager 4.1 data on UNIX” on page 50.

To upgrade Management Server to Veritas Operations Manager 4.1 on UNIX

1 Make sure that the host where you plan to upgrade Management Server meetsor exceeds system and operating system requirements.


See “System resource requirements” on page 27.




4 On the host where you plan to upgrade Management Server, log on as root.

5 Change directory to the location where you unzipped the .bin file.

6 At the command prompt, enter one of the following:

■ On a Linux host:./Veritas_Operations_Manager_CMS_4.1_Linux.bin

■ On a Solaris host:./Veritas_Operations_Manager_CMS_4.1_SolSparc.bin

If you see the error Permission Denied, change the permissions for the .binfile so that it can be run. Enter one of the following:

■ On a Linux host:chmod +x Veritas_Operations_Manager_CMS_4.1_Linux.bin

■ On a Solaris host:chmod +x Veritas_Operations_Manager_CMS_4.1_SolSparc.bin

Installing, upgrading, and uninstalling Veritas Operations ManagerUpgrading Management Server to Veritas Operations Manager 4.1

48

7 To accept the End User License Agreement and proceed with the upgrade,type y.

The upgrade is complete when you see messages similar to the following:

Veritas Operations Manager is upgraded successfully.

8 To verify the upgrade, enter one of the following:

■ On a Linux host:rpm -q VRTSsfmcs

■ On a Solaris host:pkginfo -l VRTSsfmcs

Verify that the version for the VRTSsfmcs package is displayed as 4.1.


Upgrading Management Server on WindowsYou can upgrade an existing Management Server on a Windows host to VeritasOperations Manager 4.1 using theVeritas_Operations_Manager_CMS_4.1_Win.exe file. When you run the .exe

file, the installer first attempts to upgrade the Veritas Operations Managerdatabase to a temporary location. If the database upgrade is successful, theremaining steps in the upgrade process are carried out. If the database upgradefails, the previous version of Veritas Operations Manager is restored.

Before you upgrade Management Server, Symantec recommends that you take abackup of the Management Server data.

See “Backing up Veritas Operations Manager 4.1 data on Windows” on page 51.

To upgrade Management Server to Veritas Operations Manager 4.1 on Windows

1 Make sure that the host where you plan to upgrade Management Server meetsor exceeds system and operating system requirements.



2 On the host where you plan to upgrade Management Server, log on as a userwith administrator privileges.



4 Turn off the Windows firewall, or, open ports 5634 and 14161 for TCP/IPcommunication.

49Installing, upgrading, and uninstalling Veritas Operations ManagerUpgrading Management Server to Veritas Operations Manager 4.1

5 Ensure that there is no pending restart from Windows Update. If there is,restart the host before launching the installer.

6 To launch the installer, run theVeritas_Operations_Manager_CMS_4.1_Win.exe file.

7 In the message window that recommends that you back up data before theupgrade, do one of the following:

■ Click Yes to continue with the upgrade.

■ Click No to stop the upgrade. You can choose this option to stop theupgrade and back up data for the previous version of Veritas OperationsManager.See “Backing up Veritas Operations Manager 4.1 data on Windows”on page 51.

8 To upgrade Management Server, click Upgrade.

After the upgrade is complete, you will see the message UpgradeCompletedSuccessfully.

9 Click Finish to close the installer.

10 To verify the upgrade, open the Add or Remove Programs panel.

11 To verify that the version has changed to 4.1, click the support informationlink under the Veritas Operations Manager for Windows program in thecurrently installed programs list.


Backing up Veritas Operations Manager 4.1 data onUNIX

You can regularly back up the Veritas Operations Manager Management Serverdata to prevent data loss in the event of a failure. Veritas Operations Manager 4.1provides a script that you can use to back up and restore data.

Before you upgrade Veritas Operations Manager Management Server, Symantecrecommends that you back up the data. To take a backup of the existingconfiguration, you need to first extract a backup script, and then, run the backupscript.

On UNIX, the backup script can back up an existing Management Server inhigh-availability configuration.

Note: The backup script does not back up the data that is related to the add-ons.

Installing, upgrading, and uninstalling Veritas Operations ManagerBacking up Veritas Operations Manager 4.1 data on UNIX

50

You can use the .bin file that you downloaded for installing the version 4.1Management Server to extract the backup script. You need to perform the extractstep only once to obtain the backup script.

To extract the backup script, run the following command:

■ On Linux:./Veritas_Operations_Manager_CMS_4.1_Linux.bin --x-backup

■ On Solaris:./Veritas_Operations_Manager_CMS_4.1_SolSparc.bin --x-backup

The command extracts a Perl script named vom_bkup.pl.

To take the backup, run the extracted Perl script:

./vom_bkup.pl --backup dir

where, dir is the location that you specify for creating the backup. You can specifyany location except /var/opt/VRTSsfmh, /opt/VRTSsfmh, /var/opt/VRTSsfmcs,or /opt/VRTSsfmcs.

The backup script can also be used to restore the backup. To restore the data usingthe backup script, the backup must be taken using the backup script for version4.1.

See “Upgrading Management Server on UNIX” on page 48.

Backing up Veritas Operations Manager 4.1 data onWindows

You can regularly back up the Veritas Operations Manager Management Serverdata to prevent data loss in the event of a failure. Veritas Operations Manager 4.1provides a script that you can use to back up and restore data.

Before you upgrade Veritas Operations Manager Management Server, Symantecrecommends that you back up the data. To take a backup of the existingconfiguration, you need to first run the installation file that you downloaded toperform the upgrade to version 4.1. When you run the installation file, the backupscript is copied to the installdir\VRTSsfmcs\config\adm\ folder.

On Windows, the backup script can back up an existing Management Server inhigh-availability configuration. However, you cannot use the backup script torestore the high-availability configuration. This feature is currently not supported.

Note: The backup script does not back up the data that is related to the add-ons.

51Installing, upgrading, and uninstalling Veritas Operations ManagerBacking up Veritas Operations Manager 4.1 data on Windows

To back up Veritas Operations Manager on Windows

1 On the host where you plan to back up Management Server, log on as a userwith administrator privileges.

2 To back up data before upgrading to Veritas Operations Manager 4.1, do thefollowing:

■ Download and unzip the installation file.See “Downloading Veritas Operations Manager 4.1” on page 13.

■ To launch the installer, run theVeritas_Operations_Manager_CMS_4.1_Win.exe file.

■ In the message window that recommends that you back up data beforethe upgrade, click No to stop the upgrade.

You need to perform this step only when you are taking backup for the firsttime. You do not need to launch the installer again after you have extractedthe vom_bkup.pl script.

3 To take the backup, run the following command at the command prompt:

"installdir\VRTSsfmh\bin\perl" ./vom_bkup.pl --backup "dir"

where, installdir is the installation directory and dir is the location thatyou specify for creating the backup. Make sure that the location that youspecify has adequate disk space to store the backup. You can specify anylocation except the following:

■ C:\Program Files\Veritas\VRTSsfmcs

■ C:\Program Files\Veritas\VRTSsfmh

■ C:\Documents and Settings\All Users\Application

Data\Symantec\VRTSsfmcs

■ C:\Documents and Settings\All Users\Application

Data\Symantec\VRTSsfmh

The backup script can also be used to restore the backup. To restore the data usingthe backup script, the backup must be taken using the backup script for version4.1.

See “Upgrading Management Server on Windows” on page 49.

Installing, upgrading, and uninstalling Veritas Operations ManagerBacking up Veritas Operations Manager 4.1 data on Windows

52

Upgrading host management to Veritas OperationsManager 4.1

You can upgrade managed hosts in your Management Server domain to VeritasOperations Manager 4.1 to make them compatible with the 4.1 ManagementServer. You can upgrade both the UNIX-based and the Windows-based managedhosts. You can upgrade to Veritas Operations Manager 4.1 from the following:

■ SF Manager 2.1.x managed host

■ Veritas Operations Manager 3.x managed host

■ Veritas Operations Manager 4.0 managed host

Note: You must upgrade Management Server to 4.1 before you upgrade themanaged hosts in its domain to 4.1.

You can do one of the following tasks to upgrade a managed host to VeritasOperations Manager 4.1:

■ Upgrade the managed host using the Settings > Deployment Managementtab in the Veritas Operations Manager console.See “Upgrading managed hosts using the Veritas Operations Manager console” on page 53.For more information on deploying packages, see the Veritas OperationsManager Administrator's Guide.

■ Upgrade the managed host using operating system commands.See “Upgrading host management on UNIX using operating system commands”on page 54.See “Upgrading host management on Windows using the installer package”on page 56.

Upgrading managed hosts using the Veritas Operations Managerconsole

You can upgrade multiple managed hosts using the Veritas Operations Managerconsole. This method is an efficient method to upgrade the VRTSsfmh packageremotely on the managed hosts, instead of upgrading it individually. To upgradethe managed hosts, ensure that theVRTSsfmhpackage is uploaded to the repository.You need not remove any hot fix that is installed on the host for the VRTSsfmh

package before the upgrade.

53Installing, upgrading, and uninstalling Veritas Operations ManagerUpgrading host management to Veritas Operations Manager 4.1

For more information on uploading packages to the repository, see the VeritasOperations Manager Administrator's Guide.

To upgrade managed hosts using the Veritas Operations Manager console

1 In the Veritas Operations Manager console, click Settings > DeploymentManagement.

2 In the Deployment Management view, do one of the following:

■ Select the VRTSsfmh package, and click Actions > Install.

■ Right-click on the VRTSsfmh package. From the submenu, select Install.

3 In the Install Solution panel, click Hosts option, and select the desiredmanaged hosts. To upgrade all the managed hosts that use a specific platform,use the Platforms option.

4 Click Install.

5 Verify the managed host version in the console.

See “Verifying the version of a Veritas Operations Manager managed host inthe console” on page 57.

Upgrading host management on UNIX using operating systemcommands

You can upgrade an existing managed host on UNIX to Veritas Operations Manager4.1 by upgrading the VRTSsfmh package on it.

To upgrade managed host to Veritas Operations Manager 4.1 on UNIX

1 Make sure that the host where you plan to upgrade host management meetsor exceeds system and operating system requirements.






4 On the host where you plan to upgrade host management, log on as root.

5 Change directory to the location where you unzipped the installation filesbundle.

If the host is an AIX or an HP-UX host, decompress the downloaded file.


Installing, upgrading, and uninstalling Veritas Operations ManagerUpgrading host management to Veritas Operations Manager 4.1

54

6 At the command prompt, enter one of the following commands to upgradethe package:

■ For AIX, enter the following:installp -ad VRTSsfmh_4.1.xxxx.0_AIX.bff VRTSsfmh


■ For HP-UX, enter the following:swinstall -s $PWD VRTSsfmh

■ For Linux on x86 or Xeon, enter the following:rpm -U VRTSsfmh_4.1.xxxx.0_Linux.rpm


■ For Linux on PowerPC, enter the following:rpm -U VRTSsfmh_4.1.xxxx.0_Linux_arch_ppc64.rpm


■ For Solaris on SPARC, enter the following:pkgadd -d VRTSsfmh_4.1.xxxx.0_SunOS_arch_sparc.pkg -a

/opt/VRTSsfmh/etc/VRTSsfmhadmin VRTSsfmh


■ For Solaris on x86, enter the following:pkgadd -d VRTSsfmh_4.1.xxxx.0_SunOS_arch_i386.pkg -a

/opt/VRTSsfmh/etc/VRTSsfmhadmin VRTSsfmh


7 To verify that the package has been upgraded and the version has changedto 4.1, enter one of the following at the command prompt:

■ On AIX, enter the following:lslpp -l VRTSsfmh

■ On HP-UX, enter the following:swlist VRTSsfmh

■ On Linux, enter the following:rpm -q VRTSsfmh

■ On Solaris, enter the following:pkginfo -l VRTSsfmh


55Installing, upgrading, and uninstalling Veritas Operations ManagerUpgrading host management to Veritas Operations Manager 4.1

Upgrading host management on Windows using the installer packageYou can upgrade an existing managed host on Windows to Veritas OperationsManager 4.1 by upgrading the .msi package on it.

To upgrade managed host to Veritas Operations Manager 4.1 on Windows




3 From the directory to which you unzipped the installation files bundle, doone of the following:



■ On a IA64 host, run VRTSsfmh_4.10.xxxx_Windows_arch_IA64.msi



4 On the Welcome screen of the InstallShield Wizard, click Next.

5 On the Ready to Install the Program screen, click Install to start the upgrade.

6 Click Finish to exit the InstallShield Wizard.

7 To verify the upgrade, open the Add or Remove Programs panel.

8 To verify that the version has changed to 4.1, click the support informationlink under the VeritasOperationsManagerforWindows(HostComponent)program in the currently installed programs list.


Verifying the version of Management Server in theconsole

After you have installed or upgraded Management Server, you can verify itsversion in the Management Server console.

Installing, upgrading, and uninstalling Veritas Operations ManagerVerifying the version of Management Server in the console

56

To verify the version of Management Server in the console

1 In the header, at the top of the Management Server console, click About.

The Management Server version is displayed.

2 To close the window, click OK.

See “Verifying Management Server installation on UNIX” on page 37.

See “Verifying Management Server installation on Windows” on page 37.

Verifying the version of a VeritasOperationsManagermanaged host in the console

After you have installed or upgraded a managed host, you can verify its versionin the Veritas Operations Manager console.

To verify the version of a managed host in the console

1 In the Veritas Operations Manager console, click Settings > HostManagement.

2 In the Host Management view that is displayed, verify the managed hostversion in the MH Version column.


Uninstalling Management Server on UNIXYou can uninstall Veritas Operations Manager Management Server by removingthe VRTSsfmcs and VRTSsfmh packages from the Management Server host. Whenyou uninstall Management Server, all data on managed hosts is also removed. Ifyou reinstall Management Server on the host, you have to add the hosts again tothe Management Server domain.

Note: You must remove the VRTSsfmcs package before you remove the VRTSsfmh

package.

To uninstall Veritas Operations Manager Management Server on UNIX


2 On the Management Server host, log on as root.

3 To remove the VRTSsfmcs package, enter one of the following:

■ On a Linux host: rpm -e VRTSsfmcs

57Installing, upgrading, and uninstalling Veritas Operations ManagerVerifying the version of a Veritas Operations Manager managed host in the console

■ On a Solaris host: pkgrm VRTSsfmcs

4 To remove the VRTSsfmh package, enter one of the following:

■ On a Linux host: rpm -e VRTSsfmh

■ On a Solaris host: pkgrm VRTSsfmh

Uninstalling Management Server on WindowsYou can uninstall Veritas Operations Manager Management Server from aWindows host. When you uninstall Management Server, all data on managedhosts is also removed. If you reinstall Management Server on the host, you haveto add the hosts again to the Management Server domain.

To uninstall Veritas Operations Manager Management Server on Windows


2 On the Windows Control Panel, click Add or Remove Programs.

3 From the list of installed programs, select Veritas Operations Manager forWindows.

4 Click Remove.

5 In the dialog box, do one of the following:

■ To confirm that you want to uninstall Management Server, click Yes.

■ To exit without uninstalling Management Server, click No and skip step6.

6 On the message window that indicates that the uninstall was successful, clickOK.

Uninstalling host management on UNIXYou can use an operating system command to remove the VRTSsfmhpackage froma UNIX managed host. When you remove the package, Veritas Operations Managerhost management is uninstalled from the managed host.

Note: Before you uninstall the host, remove it from the Management Serverdomain. In the Management Server console, select Settings > HostManagement.Select a host and right-click on it to display the shortcut menu. From the shortcutmenu, select Remove Host(s).

Installing, upgrading, and uninstalling Veritas Operations ManagerUninstalling Management Server on Windows

58

To uninstall Veritas Operations Manager host management on UNIX


2 On the managed host where you plan to uninstall host management, log onas root.

3 At the command prompt, enter one of the following commands to uninstallthe package:

■ On AIX, enter the following:installp -u VRTSsfmh

■ On HP-UX, enter the following:swremove VRTSsfmh

■ On Linux, enter the following:rpm -e VRTSsfmh

■ On Solaris, enter the following:pkgrm VRTSsfmh

Uninstalling host management on WindowsYou can uninstall Veritas Operations Manager host management on a Windowsmanaged host.

Note: Before you uninstall the host, remove it from the Management Serverdomain. In the Management Server console, select Settings > HostManagement.Select a host and right-click on it to display the shortcut menu. From the shortcutmenu, select Remove Host(s).

To uninstall Veritas Operations Manager host management on Windows


2 On the Windows Control Panel, click Add or Remove Programs.

3 From the list of installed programs, select VeritasOperationsManager(HostComponent).

4 Click Remove.

5 In the dialog box, do one of the following:

■ To confirm that you want to uninstall host management, click Yes.

■ To exit without uninstalling host management, click No.

59Installing, upgrading, and uninstalling Veritas Operations ManagerUninstalling host management on Windows

Installing, upgrading, and uninstalling Veritas Operations ManagerUninstalling host management on Windows

60

Using Veritas OperationsManager in high availabilityenvironment


■ About configuring Veritas Operations Manager in high availability environment

■ Configuring a new Veritas Operations Manager 4.1 installation in highavailability environment

■ Sample configuration: After you create the base service groups in VeritasOperations Manager

■ Sample configuration: After you configure Veritas Operations Manager in highavailability environment

■ Configuring an existing Veritas Operations Manager 4.1 installation in highavailability environment

■ About configuring Veritas Operations Managerin high availability environmentfor disaster recovery

■ Prerequisites for configuring Veritas Operations Managerin the highavailability environment for disaster recovery

■ Configuring Veritas Operations Manager 4.1 in high availability environmentfor disaster recovery

■ Sample configuration: After you configure Veritas Operations Manager in highavailability environment for disaster recovery

4Chapter

■ About upgrading the high availability and the disaster recovery configurationsto Veritas Operations Manager 4.1

■ Upgrading Management Server in high availability environment

■ Removing the high availability configuration

About configuringVeritasOperationsManager in highavailability environment

Configuring Veritas Operations Manager in high availability environment enhancesthe efficiency of Veritas Operations Manager as an operational tool for storageadministrators. This configuration improves the availability of the applicationsand the services that Veritas Operations Manager provides.

Note: You can configure Veritas Operations Manager in high availabilityenvironment only in the failover mode.

For the Veritas Operations Manager HA configuration, you must use a two-nodeVCS cluster in which Storage Foundation HA 5.x, or later, is installed. Before youconfigure Veritas Operations Manager in high availability environment, you mustensure that Node1 that you configure as Management Server and Node2 that youadd as managed host to Node1 are part of the same domain.

After you configure Veritas Operations Manager in high availability environment,you can enable the disaster recovery feature on the Veritas Operations Manager-HAsetup.

See “Removing the high availability configuration” on page 94.

Configuring a new Veritas Operations Manager 4.1installation in high availability environment

You can configure Veritas Operations Manager in high availability environmentimmediately after the initial configuration of Management Server. In this method,you do not have to change the host name and the IP address of the host.

Note:To avoid losing the data, do not use this method to configure high availabilityenvironment on an existing Management Server.

Using Veritas Operations Manager in high availability environmentAbout configuring Veritas Operations Manager in high availability environment

62

In Veritas Operations Manager, you can configure both UNIX and WindowsManagement Servers in the high availability environment.

Note: You can configure Windows Management Server with versions Windows2008 (64-bit) and Windows 2008 R2 (64-bit) in the high availability environment.

Configuring Veritas Operations Manager in high availability environment withoutchanging the host name and the IP address of the host involves the followingsteps:

■ Installing Storage Foundation HA 5.x on Node1 and Node2 as part of preparingManagement Server for high availability configuration.

■ Installing Veritas Operations Manager Management Server on the hosts thatyou want to designate as Node1 and Node2.

■ Creating the base service groups in VCS to ensure failover as part of preparingManagement Server for high availability configuration.

■ Configuring Veritas Operations Manager in the high availability environment.

To prepare Management Server for high availability configuration, you mustcreate the following base service groups in VCS:

■ SFM_SStore

■ SFM_Services

Note:You must ensure that the SFM_SStore and the SFM_Services service groupsare in the failover mode.

Table 4-1 displays the details of the resources that you can create on theSFM_SStore service group:

Table 4-1 Resources on the SFM_SStore service group

NotesResource typeResource name

Disk group that is specifiedfor the failover.

Note: For configuringWindows ManagementServer in the highavailability environment, youmust create a clustered diskgroup.

Disk groupSFM_SStore_DG

63Using Veritas Operations Manager in high availability environmentConfiguring a new Veritas Operations Manager 4.1 installation in high availability environment

Table 4-2 displays the details of the resources that you can create on theSFM_Services service group:

Table 4-2 Resources on the SFM_Services service group for UNIX cluster


Virtual IP address, which youhave configured along withthe virtual host name.

The IP resource type dependson the NIC resource type.

IPSFM_Services_IP

Name of NIC.

In the procedure in this topic,we use the following:

■ eth0 as NIC for LinuxManagement Server.

■ hme0 as NIC for SolarisManagement Server.

NICSFM_Services_NIC

■ Mount point name of thefile system that isspecified for failover.

■ Complete path of thestorage device that isspecified for failover.

■ Type of file system thatis specified for failover.In Veritas OperationsManager, you can specifyonly the Veritas filesystem (VxFS).

■ File check option (fsckpt= -n or -y)

MountSFM_Services_Mount

Table 4-3 Resources on the SFM_Services service group for Windows cluster




IPSFM_Services_IP

Using Veritas Operations Manager in high availability environmentConfiguring a new Veritas Operations Manager 4.1 installation in high availability environment

64

Table 4-3 Resources on the SFM_Services service group for Windows cluster(continued)


Name of NIC.




NICSFM_Services_NIC

■ The drive letter that willbe assigned to the volumebeing mounted.

■ Complete path of thestorage device that isspecified for failover.

■ Type of file system thatis specified for failover.In Veritas OperationsManager, you can specifyonly the Veritas filesystem (VxFS).

■ File check option (fsckpt= -n or -y)

MountvSFM_Services_Mountv

LanmanLanman

Note: The SFM_Services service group creates a link to the SFM_SStore servicegroup.

The SFM_Services_IP resource creates a link to the SFM_Services_NIC resource.

In the following procedure, we use the following names for the hosts:

My_host_1Host name of Node1


My_virtual-hostVirtual host name


Note:Before you configure a new Veritas Operations Manager installation in highavailability environment, you must install Storage Foundation HA 5.x on the hoststhat you want to designate as Node1 and Node2.

Note: You must create the SFM_Services_IP resource before you proceed withconfiguring Windows Management Server in the high availability environment.The SFM_Services_IP resource brings up the virtual host name and virtual IPaddress that you can use in configuring Windows Management Server in the highavailability environment. After you get the virtual host name and the virtual IPaddress for Node1, you can proceed with configuring Windows ManagementServer on Node1. (To configure Veritas Operations Manager Management Serveron Node1)

As a best practice, you can create all the base service groups in VCS to ensurefailover before you proceed with configuring Windows Management Server onNode1 in the high availability environment. (To create the base service groups inVCS to ensure failover)

To retrieve the virtual host name and the virtual IP address on Node1 (for UNIXManagement Server only)

◆ To retrieve the virtual host name and the virtual IP address on Node1 onwhich you have installed VCS cluster with Storage Foundation HA 5.x, runthe following command:

■ For the node on Linux:ifconfig eth0:0 My_host_1's virtual IP Address netmask subnet

mask up

■ For the node on Solaris:ifconfig hme0:1 plumb

ifconfig hme0:1 My_host_1's virtual IP Address netmask subnet

mask up


66

To configure Veritas Operations Manager Management Server on Node1

1 On Node1 and Node2, install Veritas Operations Manager Management Serverbits.



2 To configure Node1 as Management Server in standalone mode, click thehttps://My_host_1:5634 URL that displays after you install the ManagementServer bits on Node1.

where, My_host_1 is Node1’s host name. Alternatively, you can use the IPaddress of Node1.

You must ensure that you have appropriate privileges to log in to this host.

3 In the Server Setting page, do the following:

■ In the Server Name field, enter the virtual host name of Node1.

■ In the Server Address field, enter the virtual IP address of Node1.

4 In the Database Setting page, specify the database location.

This field displays the default database path. If required, you can specifyanother database path in this field. If you specify a database path other thanthe default path that is displayed in the field, you must ensure the availabilityof enough database space.

When specifying a database path other than the default database path, youmust not enter the clustered disk group path that you have created for theSFM_SStore_DG resource.

5 In the Analytics Setting page, select the checkbox Enable AnalyticsGathering and click Start.

6 In the next panel for configuring Veritas Operations Manager ManagementServer, view the status of the tasks that are performed as part of VeritasOperations Manager Management Server configuration and click the linkthat is displayed on the panel to log in to Management Server on Node1.

To add Node2 as a managed host to the configured Management Server

◆ Use the Veritas Operations Manager Web console to add Node2 (My_host_2)as a managed host to the configured Management Server. Make sure that thestorage objects that are associated with Node2 are accessible after you addit as managed host.


To create the base service groups in VCS to ensure failover

◆ In VCS, create the base service groups that are named as SFM_SStore andSFM_Services with the appropriate resource types. Also, link the base servicegroups and the resource types.

To view the details of the resources that you can create on the SFM_SStoreservice group, refer to Table 4-1

To view the details of the resources that you can create on the SFM_Servicesservice group, refer to Table 4-2

To configure a new Veritas Operations Manager installation in high availabilityenvironment

1 To configure a new Veritas Operations Manager installation in highavailability environment, open a Web browser, type the following URL in theWeb browser’s address field, and press Enter:

https://My_virtual-host:5634

where, My_virtual-host is the virtual host name of Node1.


2 In the panel that displays the message that Click Next to configure CS as aCluster Node, click Next.

3 In the next panel, which displays the steps that you must do to configureManagement Server as a cluster node, click Start.

4 In the next panel, which displays the steps that you must do to configureManagement Server in high availability environment, click Next.

5 In the next panel, which displays the details of the service group for the HAconfiguration for your review, click Next.

6 In the next panel, view the status of the tasks that are performed as part ofVeritas Operations Manager HA configuration and do the following:

■ Click the link that is displayed on the panel to log in to Veritas OperationsManager that is configured in high availability environment.

■ Click Quit to quit the configuration dialog.


See “Prerequisites for configuring Veritas Operations Managerin the highavailability environment for disaster recovery” on page 82.

See “Configuring an existing Veritas Operations Manager 4.1 installation in highavailability environment” on page 74.


68

See “About upgrading the high availability and the disaster recovery configurationsto Veritas Operations Manager 4.1 ” on page 93.


Sample configuration: After you create the baseservice groups in Veritas Operations Manager

The following is an example of Veritas Operations Manager configuration afteryou create the base service groups (SFM_Services and SFM_SStore):

Note: The following example uses the names London for Node1 and Paris forNode2.

group SFM_SStore (

SystemList = { London = 0, Paris = 1 }

AutoStartList = { London, Paris }

)

DiskGroup SFM_SStore_DG (

DiskGroup = hadg

)

// resource dependency tree

//

// group SFM_SStore

// {

// DiskGroup SFM_SStore_DG

// }

group SFM_Services (



)

IP SFM_Services_IP (

Device @London = eth0

Device @Paris = eth0

Address = "IP_Address"

NetMask = "Netmask"

)

69Using Veritas Operations Manager in high availability environmentSample configuration: After you create the base service groups in Veritas Operations Manager

Mount SFM_Services_MOUNT (

MountPoint = "/hafs"

BlockDevice = "/dev/vx/dsk/hadg/havol"

FSType = vxfs

FsckOpt = "-n"

)

NIC SFM_Services_NIC (



)

requires group SFM_SStore online local hard

SFM_Services_IP requires SFM_Services_NIC


//

// group SFM_Services

// {

// IP SFM_Services_IP

// {

// NIC SFM_Services_NIC

// }

// Mount SFM_Services_MOUNT

// {

// }

See “Sample configuration: After you configure Veritas Operations Manager inhigh availability environment” on page 70.

Sample configuration: After you configure VeritasOperationsManager in high availability environment

The following is an example of Veritas Operations Manager configuration afteryou configure it in high availability environment:

Note: The following example uses the names London for Node1 and Paris forNode2.

Using Veritas Operations Manager in high availability environmentSample configuration: After you configure Veritas Operations Manager in high availability environment

70

group SFM_SStore (



)


DiskGroup = hadg

)


//

// group SFM_SStore

// {


// }




)

Application SFM_Services_DB (

User = root

StartProgram = "/opt/VRTSsfmcs/config/vcs/db/online"

StopProgram = "/opt/VRTSsfmcs/config/vcs/db/offline"

MonitorProgram = "/opt/VRTSsfmcs/config/vcs/db/monitor"

)

Application SFM_Services_SECD (

User = root

StartProgram = "/opt/VRTSsfmcs/config/vcs/secd/online.sh"

StopProgram = "/opt/VRTSsfmcs/config/vcs/secd/offline.sh"

CleanProgram = "/opt/VRTSsfmcs/config/vcs/secd/clean.sh"

MonitorProgram = "/opt/VRTSsfmcs/config/vcs/secd/monitor.sh"

)

Application SFM_Services_WEB (

User = root

StartProgram = "/opt/VRTSsfmcs/config/vcs/gui/online.sh"

StopProgram = "/opt/VRTSsfmcs/config/vcs/gui/offline.sh"

71Using Veritas Operations Manager in high availability environmentSample configuration: After you configure Veritas Operations Manager in high availability environment

CleanProgram = "/opt/VRTSsfmcs/config/vcs/gui/clean.sh"

MonitorProgram = "/opt/VRTSsfmcs/config/vcs/gui/monitor.sh"

)

Application SFM_Services_XPRTLDD (

User = root

StartProgram = "/opt/VRTSsfmcs/config/vcs/xprtld_domain/online.sh"

StopProgram = "/opt/VRTSsfmcs/config/vcs/xprtld_domain/offline.sh"

MonitorProgram = "/opt/VRTSsfmcs/config/vcs/xprtld_domain/monitor.sh"

)





NetMask = "Netmask"

)

Mount SFM_Services_MOUNT (



FSType = vxfs

FsckOpt = "-n"

)




)


SFM_Services_DB requires SFM_Services_IP

SFM_Services_DB requires SFM_Services_MOUNT

SFM_Services_SECD requires SFM_Services_DB

SFM_Services_WEB requires SFM_Services_SECD

SFM_Services_XPRTLDD requires SFM_Services_DB



//


Using Veritas Operations Manager in high availability environmentSample configuration: After you configure Veritas Operations Manager in high availability environment

72

// {

// Application SFM_Services_WEB

// {

// Application SFM_Services_SECD

// {

// Application SFM_Services_DB

// {


// {


// }


// }

// }

// }

// Application SFM_Services_XPRTLDD

// {


// {


// {


// }


// }

// }

// }

group SFM_Xprtld (


Parallel = 1


)

Application SFM_Services_XPRTLDS (

User = root

StartProgram = "/opt/VRTSsfmcs/config/vcs/xprtld_standalone/online.sh"

StopProgram = "/opt/VRTSsfmcs/config/vcs/xprtld_standalone/offline.sh"

MonitorProgram = "/opt/VRTSsfmcs/config/vcs/xprtld_standalone/monitor.sh"

)


73Using Veritas Operations Manager in high availability environmentSample configuration: After you configure Veritas Operations Manager in high availability environment

//

// group SFM_Xprtld

// {

// Application SFM_Services_XPRTLDS

// }

See “Sample configuration: After you create the base service groups in VeritasOperations Manager ” on page 69.

Configuring an existing Veritas Operations Manager4.1 installation in high availability environment

In Veritas Operations Manager, you can configure the existing UNIX or WindowsManagement Servers in the high availability environment.

Configuring Veritas Operations Manager in high availability environment on anexisting UNIX or Windows Management Server involves the following steps:

■ Modifying the default host names and the IP addresses of the nodes.

■ Installing VCS on the hosts that you want to designate as Node1 and Node2as part of preparing an existing Management Server for high availabilityconfiguration. Node1 is the host on which Veritas Operations ManagerManagement Server is already installed.

■ Configuring Veritas Operations Manager on Node1 in standalone mode as partof preparing an existing Management Server for high availability configuration.

■ Installing Veritas Operations Manager Management Server on Node2 as partof preparing an existing Management Server for high availability configuration.You must not configure Veritas Operations Manager on Node2.

■ Creating the base service groups in VCS to ensure failover.

■ Configuring the existing Veritas Operations Manager installation in the highavailability environment.

As part of preparing Veritas Operations Manager Management Server for highavailability configuration, you must create the following base service groups inVCS:

■ SFM_SStore

■ SFM_Services

Note:You must ensure that the SFM_SStore and the SFM_Services service groupsare in the failover mode.

Using Veritas Operations Manager in high availability environmentConfiguring an existing Veritas Operations Manager 4.1 installation in high availability environment

74

Table 4-4 displays the details of the resources that you can create on theSFM_SStore service group:


NotesResource typeResource Name



Table 4-5 displays the details of the resources that you can create on theSFM_Services service group:

Table 4-5 Resources on the SFM_Services service group




IPSFM_Services_IP

Name of NIC.




NICSFM_Services_NIC

Mount point name of the FileSystem that is specified forfailover.

Complete path of the storagedevice that is specified forfailover.

Type of File System that isspecified for failover.

File check option (fsckpt = -nor -y)


After you log in to the Veritas Operations Manager that is configured in highavailability environment, in the Host view, you can view the list of hosts in the

75Using Veritas Operations Manager in high availability environmentConfiguring an existing Veritas Operations Manager 4.1 installation in high availability environment

Veritas Operations Manager HA setup. In this list of hosts, the active node isspecified as follows:

Hostname[active]

Note: In the following procedure, we use eth0 as NIC for Linux Management Server.

For Solaris Management Server, we use hme0 as NIC.

In the following procedure, we use the following host names:



My_virtual_hostVirtual host name

Note: Before you configure an existing Veritas Operations Manager installationin high availability environment, you must install VCS cluster with StorageFoundation HA 5.x on the hosts that you want to designate as Node1 and Node2.

To modify the default IP address of Node1 (for Windows Management Server)

1 On the Windows 2008 or the Windows 2008R2 server, navigate to the windowthat displays the active network adapters. Right-click the active networkadapter. From the submenu, select Properties.

2 In the Local Area Connection Properties dialog box, select the Networkingtab. In the This connection uses the following items field, select the optionInternet Protocol Version 4 (TCP/IPv4). Ensure that the check box on theleft-side of the Internet Protocol Version 4 (TCP/IPv4) option is selected.

3 At the bottom of the This connection uses the following items field, clickProperties.

4 In the InternetProtocolVersion4 (TCP/IPv4)Properties dialog box, ensurethat the Use the following IP address option is selected. In the IP addressfield, replace the original IP address of Node1 with the virtual IP address thatyou want to use for configuring Veritas Operations Manager in highavailability environment.

5 In the Internet Protocol Version 4 (TCP/IPv4) Properties dialog box, clickAdvanced.

6 In the AdvancedTCP/IPSettings dialog box, select the IPSettings tab. Insidethe IP address field, click Add.


76

7 In the TCP/IPAddress dialog box, enter the virtual IP address that you haveassigned to Node1 and click Add.

8 In the TCP/IP Address dialog box, in the IP address field, move the virtualIP address to the top of the list and click OK.

9 In the Internet Protocol Version 4 (TCP/IPv4) Properties dialog box, clickOK

To modify the default host name of Node1 (for Windows Management Server)

1 On the desktop of the Windows 2008 or the Windows 2008R2 server,right-click My Computer. From the submenu, select Properties.

2 In the System window, on the left-side, click the link Advanced SystemSettings.

3 In the SystemProperties dialog box, select the tab ComputerName and clickChange.

4 In the dialog box, enter the virtual host name for Node1 and enter thecredentials for the domain to which the virtual host name is associated.

The virtual host name and the original host name of Node1 belong to thesame domain.

5 Restart the computer.

Tomodify the default host nameand the IP address ofNode1 (for UNIXManagementServer)

1 To change the original host name of Node1 (My_host_1) to virtual host name(My_virtual_host), execute the hostname virtual_hostname command. Forexample, use hostname My_virtual_host

This procedure demonstrates an example of changing the default host nameand IP address.

2 To bring up the virtual host name and the virtual IP address on Node1 onwhich you have installed VCS cluster with Storage Foundation HA 5.x, executethe following command:

■ For the node on Linux:ifconfig eth0:0 My_host_1's virtual IP Address netmask subnet

mask up

■ For the node on Solaris:ifconfig hme0:1 plumb

ifconfig hme0:1 My_host_1's virtual IP Address netmask subnet

mask up


To modify the default host names and the IP addresses in the files (for both UNIXand Windows Management Servers)

1 Execute the following commands to change the host name and the IP addressof Node1 to virtual host name and virtual IP address in the following files:

On Linux Management Server, use the following commands:

Modifies Node1's host name(My_host_1) to virtual hostname (My_virtual_host).

vi /etc/sysconfig/network

Modifies the IP address tovirtual IP address .

vi

/etc/sysconfig/network-scripts/ifconfig-eth0

On Solaris Management Server, use the following commands:

Modifies Node1's host name(My_host_1) to virtual hostname (My_virtual_host).

vi /etc/nodename

vi /etc/hostname.hme0

Modifies the IP address tovirtual IP address .

vi /etc/inet/hosts

2 To stop all the VCS processes, execute the following command on both thenodes:

/opt/VRTSvcs/bin/hastop -all

On Windows Management Server, do the following

■ Select Start > Run. In the Run dialog box, type services.msc.

■ In the Services window, stop the Veritas high availability engine serviceYou must perform this task on both Node1 and Node2.


78

3 To change all occurrences of the original host names (My_host_1) to thevirtual host names (My_virtual_host) in the following files of Node1, executethe commands that are mentioned against each file:

vi /etc/llttabllttab

vi /etc/llthostsllthosts

vi /etc/VRTSvcs/conf/sysnamesysname

vi

/etc/VRTSvcs/conf/config/main.cf

main.cf

On Windows Management Server, modify the required entries in the followingfiles from the locations that are mentioned against each of them:

C:\Program Files\Veritas\comms\llt\llttab.txt

C:\Program Files\Veritas\comms\llt\llthosts.txt

C:\Program Files\Veritas\clusterserver\conf

sysname

C:\Program Files\Veritas\clusterserver\conf\config\

main.cf

4 Log in to Node2. To change all occurrences of Node1 host names to the virtualhost names in the following files, execute the commands that are mentionedagainst each file:

vi /etc/llthostsllthosts

vi

/etc/VRTSvcs/conf/config/main.cf

main.cf

On Windows Management Server, modify the required entries in the followingfiles from the locations that are mentioned against each of them:

C:\Program Files\Veritas\comms\llt\llthosts.txt

C:\Program Files\Veritas\clusterserver\conf\config\

main.cf

5 To start the VCS processes, execute the following command on both the nodes:

/opt/VRTSvcs/bin/hastart


On Windows Management Server, do the following

■ Select Start > Run. In the Run dialog box, type services.msc.

■ In the Services window, start the Veritas high availability engine service.

You must perform this task on both Node1 and Node2.

6 Restart Node1 or execute the following command:

service network restart

7 Log in to Node1 using the virtual host name (My_virtual_host).

To prepare an existing Management Server for high availability configuration

1 On Node1, configure Veritas Operations Manager Management Server innon-HA mode.

2 On Node2, install Veritas Operations Manager Management Server withoutconfiguring it.

3 To Node1 on which you have configured the Veritas Operations ManagerManagement Server in non-high availability mode, add Node2 as a managedhost. You can use the Veritas Operations Manager Web GUI to add Node2 asmanaged host to Node1. Make sure that the storage objects that are associatedwith Node2 are accessible after you add it as managed host to Node1.


◆ In VCS, create the base service groups that are named as SFM_SStore andSFM_Services with the appropriate resource types. Also, link the base servicegroups and the resource types.



To configure an existing Veritas OperationsManager installation in high availabilityenvironment

1 To configure an existing Veritas Operations Manager installation in highavailability environment, open a Web browser, type the following URL in theWeb browser’s address field, and press Enter:

https://My_virtual-host:5634

where, My_virtual-host is the virtual host name of Node1.


2 In the panel that displays the message that Click Next to configure CS as aCluster Node, click Next.


80

3 In the next panel, which displays the steps that you must do to configureManagement Server as a cluster node, click Start.

4 In the next panel, which displays the steps that you must do to configureManagement Server in high availability environment, click Next.

5 In the next panel, which displays the details of the service group for the HAconfiguration for your review, click Next.

6 In the next panel, view the status of the tasks that are performed as part ofVeritas Operations Manager HA configuration and do the following:

■ Click the link that is displayed on the dialog to log in to Veritas OperationsManager that is configured in high availability environment.



See “Prerequisites for configuring Veritas Operations Managerin the highavailability environment for disaster recovery” on page 82.

See “Configuring a new Veritas Operations Manager 4.1 installation in highavailability environment” on page 62.



About configuringVeritasOperationsManagerin highavailability environment for disaster recovery

You can configure the disaster recovery feature on Veritas Operations ManagerManagement Server that is configured in high availability environment. In yourglobally distributed datacenter, the Veritas Operations Manager HA setup that isenabled with disaster recovery enhances the failover support.

Before you configure the disaster recovery feature on an Veritas OperationsManager-HA setup, you must create the following two base service groups as partof the Veritas Operations Manager-HA configuration:

■ SFM_Services

■ SFM_SStore

You must replicate the Veritas Operations Manager database and the VeritasOperations Manager domain-wide information that is stored in the shared storage

81Using Veritas Operations Manager in high availability environmentAbout configuring Veritas Operations Managerin high availability environment for disaster recovery

to the second site. You must make sure that SFM_Services_IP andSFM_Services_Mount on the second site is not online while you do this migration.

Prerequisites for configuring Veritas OperationsManagerin the high availability environment fordisaster recovery

Before you configure Veritas Operations Manager in the high availabilityenvironment, ensure the following:

■ Storage Foundation and VCS are installed on both the nodes on which youwant to configure Veritas Operations Manager in the high availabilityenvironment.

■ Veritas Operations Manager Management Server bits are installed on both thenodes.

■ Both the nodes on which you want to configure Veritas Operations Managerin the high availability environment must report synchronized Universal TimeClock (UTC/UC) time.

■ You must specify the database location.You can either use the default database location /var/opt/VTRSsfmcs/db orspecify another location. If you specify the location other than the defaultdatabase location, you must make sure that it is not part of the shared filesystem that is used for failover. Later, the Veritas Operations Manager HAscript moves the database to the shared file system.

■ If you do not use DNS Agent, you must add the host names to the /etc/hostsfile.

■ Global Cluster Option (GCO) is enabled in VCS in Site A and Site B.

■ Veritas Volume Replicator (VVR) is configured in Site A and Site B.

■ The SFM_Services and the SFM_SStore base service groups that are createdon Site A and Site B are the same. The SFM_Services base service group mustbe configured as Global Service group between the two clusters.

■ On Site A and Site B, on both the domains, use the same virtual host name.

■ Use different virtual IP addresses for GCO IP, SFM_Services_IP, andSFM_SStore_IP.

■ SFM_SStore service is online on any of the node on Site B before you executethe disaster recovery script.

Using Veritas Operations Manager in high availability environmentPrerequisites for configuring Veritas Operations Managerin the high availability environment for disaster recovery

82


Configuring Veritas Operations Manager 4.1 in highavailability environment for disaster recovery

In configuring Veritas Operations Manager in high availability environment fordisaster recovery, you configure a Veritas Operations Manager HA setup in aremote site along with the Veritas Operations Manager HA setup in your localsite and make them act as two nodes. Configuring Veritas Operations Manager inhigh availability environment for disaster recovery helps you enhance the failoversupport.

This topic considers the local Veritas Operations Manager-HA setup as Site A andthe remote Veritas Operations Manager- HA setup as Site B.

You can use the SFM_Services and the SFM_SStore service groups to configurethe disaster recovery feature on Veritas Operations Manager that is configuredin high availability environment. You must create the SFM_SStore and theSFM_Services service groups on both Site A and Site B.

Table 4-6 displays the details of the resources that you can create on theSFM_SStore service group to configure the disaster recovery feature on VeritasOperations Manager that is configured in high availability environment:




Note: For configuringWindows ManagementServer in the highavailability environment, youmust create the clustereddisk group.


Virtual IP, which is used toconfigure Node1 in Site A.

IPSFM_SStore_IP

83Using Veritas Operations Manager in high availability environmentConfiguring Veritas Operations Manager 4.1 in high availability environment for disaster recovery

Table 4-6 Resources on the SFM_SStore service group (continued)


Resource that is created onan interface on whichoriginal IP address andvirtual IP address areconfigured.

NICSFM_SStore_NIC

Replicated volume group(RVG) that is configured forreplication of volumes, whichis subset of the disk groupthat is used to failover.

RVGSFM_SStore_RVG

Table 4-7 displays the details of the resources that you can create on theSFM_Services service group to configure the disaster recovery feature on VeritasOperations Manager that is configured in high availability environment:

Note: On Site B, ensure that the SFM_Services_NIC resource is online. You canmake the other resources on Site B offline.

Table 4-7 Resources on the SFM_Services service group


Virtual IP address , whichyou have configured alongwith the virtual host name.


IPSFM_Services_IP

Name of NIC.




NICSFM_Services_NIC

Using Veritas Operations Manager in high availability environmentConfiguring Veritas Operations Manager 4.1 in high availability environment for disaster recovery

84

Table 4-7 Resources on the SFM_Services service group (continued)


Mount point name of the FileSystem that is specified forfailover.

Complete path of the storagedevice that is specified forfailover.

Type of File System that isspecified for failover. InVeritas Operations Manager,you can specify the VxFS FileSystem only.

File check option (fsckpt = -nor -y)


Contains the RVG resourcename that is to be used forreplication.

RVG PrimarySFM_Services_RVGPrimary

Note:You need to create the SFM_SStore_RVG resource and the SFM_SStore_NICresource manually. The SFM_SStore_RVG resource creates a link to theSFM_SStore_IP and the SFM_SStore_DG resources. The SFM_SStore_IP resourcecreates a link to the SFM_SStore_NIC resource.

The SFM_Services_Mount resource creates a link to the SFM_Services_RVGPrimaryresource.

Note: Before you enable the disaster recovery feature on a Veritas OperationsManager-HA setup, which is configured on an existing Veritas Operations Managerinstallation, you must ensure that the virtual host name that is used on all domainsin Site A and Site B are the same.

Note:Before you configure a Veritas Operations Manager-HA-DR setup, you mustinstall VCS cluster with Storage Foundation HA 5.x on the hosts that you want todesignate as Node1 and Node2 in Site A and Node3 and Node4 in Site B. Also,Node1 in Site A and Node3 in Site B are considered as primary nodes.

Note: You must configure SFM_Services as Global Cluster Option (GCO).

85Using Veritas Operations Manager in high availability environmentConfiguring Veritas Operations Manager 4.1 in high availability environment for disaster recovery

To configure Veritas Operations Manager in high availability environment fordisaster recovery

1 Install the Veritas Operations Manager Management Server bits on the nodesNode1 and Node2 in Site A and Node3 and Node4 in Site B.

2 On Node1, configure Veritas Operations Manager Management Server in highavailability environment using the virtual host and virtual IP.

3 Add Node2 in Site A and Node3 and Node4 in Site B as managed host to VeritasOperations Manager Management Server.

4 Add the virtual host name and the virtual IP addresses of Node1 in the/etc/hosts file of Node3. Similarly, add the virtual host name and the virtualIP addresses of Node3 in the /etc/hosts file of Node1.


◆ In VCS, create the following base service groups that are named as SFM_SStoreand SFM_Services with the appropriate resource types. Also, link the baseservice groups and the resource types.



On Site B, ensure that the SFM_Services_NIC resource is online. You can makethe other resources on Site B offline. Also, You must configure SFM_Servicesas Global Cluster Option (GCO).

To enable Veritas Operations Manager HA-DR configuration

◆ Run the following script on Site A to configure Site B as part of the VeritasOperations Manager HA-DR configuration:

opt/VRTSsfmh/bin/xprtlc \

-u vxss://Virtual hostname of Site A:14545/sfm_admin/sfm_domain/vx\

-d debug=1 \

-d setup=1 \

-d mh=site B Node_1,site B Node_2 \

-l https://Virtual hostname of Site A:5634/admin/cgi-bin/cs_hadr_config.pl

See “About configuring Veritas Operations Managerin high availabilityenvironment for disaster recovery” on page 81.


Using Veritas Operations Manager in high availability environmentConfiguring Veritas Operations Manager 4.1 in high availability environment for disaster recovery

86

Sample configuration: After you configure VeritasOperationsManager in high availability environmentfor disaster recovery

The following is an example of Veritas Operations Manager configuration afteryou configure it in high availability environment for disaster recovery:

include "types.cf"

include "VVRTypes.cf"

cluster USA_gco_cluster (

UserNames = { admin = IppJ }

ClusterAddress = "IP_Address"

Administrators = { admin }

HacliUserLevel = COMMANDROOT

)

cluster India_gco_cluster (

ClusterAddress = "IP_Address"

)

heartbeat Icmp (

ClusterList = { rhel5_cmsha }

Arguments @rhel5_cmsha = { "IP_Address" }

)

system Chicago (

)

system Washington (

)

group ClusterService (

SystemList = { Chicago = 0, Washington = 1 }

AutoStartList = { Chicago, Washington }

OnlineRetryLimit = 3

OnlineRetryInterval = 120

)

Application wac (

StartProgram = "/opt/VRTSvcs/bin/wacstart"

StopProgram = "/opt/VRTSvcs/bin/wacstop"

87Using Veritas Operations Manager in high availability environmentSample configuration: After you configure Veritas Operations Manager in high availability environment for disaster

recovery

MonitorProcesses = { "/opt/VRTSvcs/bin/wac" }

RestartLimit = 3

)

IP gcoip (

Device @Chicago = eth0

Device @Washington = eth2


NetMask = "Netmask"

)

NIC csgnic (



)

gcoip requires csgnic

wac requires gcoip


//

// group ClusterService

// {

// Application wac

// {

// IP gcoip

// {

// NIC csgnic

// }

// }

// }

group SFM_SStore (

SystemList = { Washington = 0, Chicago = 1 }

AutoStartList = { Washington }

)


Critical = 0

DiskGroup = hadg

)

Using Veritas Operations Manager in high availability environmentSample configuration: After you configure Veritas Operations Manager in high availability environment for disasterrecovery

88

IP SFM_SStore_IP (

Critical = 0




)

Proxy SFM_SStore_PROXY (

TargetResName = csgnic

)

RVG SFM_SStore_RVG (

RVG = rvg

DiskGroup = hadg

)

SFM_SStore_IP requires SFM_SStore_PROXY

SFM_SStore_RVG requires SFM_SStore_DG

SFM_SStore_RVG requires SFM_SStore_IP


//

// group SFM_SStore

// {

// RVG SFM_SStore_RVG

// {


// IP SFM_SStore_IP

// {

// Proxy SFM_SStore_PROXY

// }

// }

// }



ClusterList = { suse_cmsha_dr = 0, rhel5_cmsha = 1 }

Authority = 1

AutoStartList = { Washington }

ClusterFailOverPolicy = Auto


recovery

)

Application SFM_Services_DB (

User = root

StartProgram = "/opt/VRTSsfmcs/config/vcs/db/online"

StopProgram = "/opt/VRTSsfmcs/config/vcs/db/offline"

MonitorProgram = "/opt/VRTSsfmcs/config/vcs/db/monitor"

)

Application SFM_Services_SECD (

User = root

StartProgram = "/opt/VRTSsfmcs/config/vcs/secd/online.sh"

StopProgram = "/opt/VRTSsfmcs/config/vcs/secd/offline.sh"

CleanProgram = "/opt/VRTSsfmcs/config/vcs/secd/clean.sh"

MonitorProgram = "/opt/VRTSsfmcs/config/vcs/secd/monitor.sh"

)

Application SFM_Services_WEB (

User = root

StartProgram = "/opt/VRTSsfmcs/config/vcs/gui/online.sh"

StopProgram = "/opt/VRTSsfmcs/config/vcs/gui/offline.sh"

CleanProgram = "/opt/VRTSsfmcs/config/vcs/gui/clean.sh"

MonitorProgram = "/opt/VRTSsfmcs/config/vcs/gui/monitor.sh"

)

Application SFM_Services_XPRTLDD (

User = root

StartProgram = "/opt/VRTSsfmcs/config/vcs/xprtld_domain/online.sh"

StopProgram = "/opt/VRTSsfmcs/config/vcs/xprtld_domain/offline.sh"

MonitorProgram = "/opt/VRTSsfmcs/config/vcs/xprtld_domain/monitor.sh"

)


Critical = 0




)

Mount SFM_Services_Mount (

Critical = 0




90

FSType = vxfs

FsckOpt = "-y"

)


Critical = 0



)

RVGPrimary SFM_Services_RVGPRIMARY (

RvgResourceName = rvg

)


SFM_Services_DB requires SFM_Services_IP

SFM_Services_DB requires SFM_Services_Mount


SFM_Services_Mount requires SFM_Services_RVGPRIMARY

SFM_Services_SECD requires SFM_Services_DB

SFM_Services_WEB requires SFM_Services_SECD

SFM_Services_XPRTLDD requires SFM_Services_DB


//


// {

// Application SFM_Services_WEB

// {

// Application SFM_Services_SECD

// {


// {


// {


// }

// Mount SFM_Services_Mount

// {

// RVGPrimary SFM_Services_RVGPRIMARY

// }

// }


recovery

// }

// }

// Application SFM_Services_XPRTLDD

// {


// {


// {


// }

// Mount SFM_Services_Mount

// {

// RVGPrimary SFM_Services_RVGPRIMARY

// }

// }

// }

// }

group SFM_Xprtld (


Parallel = 1

AutoStartList = { Washington, Chicago }

)

Application SFM_Services_XPRTLDS (

User = root

StartProgram = "/opt/VRTSsfmcs/config/vcs/xprtld_standalone/online.sh"

StopProgram = "/opt/VRTSsfmcs/config/vcs/xprtld_standalone/offline.sh"

MonitorProgram = "/opt/VRTSsfmcs/config/vcs/xprtld_standalone/monitor.sh"

)


//

// group SFM_Xprtld

// {

// Application SFM_Services_XPRTLDS

// }

See “Sample configuration: After you configure Veritas Operations Manager inhigh availability environment” on page 70.


92

About upgrading the high availability and the disasterrecovery configurations to Veritas OperationsManager 4.1

You can upgrade Veritas Operations Manager 3.x, or 4.x, UNIX-based ManagementServer that is configured in the high availability (HA) or in the disaster recovery(HA-DR) environment to version 4.1. To upgrade, you can download and use theinstaller for Management Server.


After the upgrade, you can use the HA or the HA-DR environments on the upgradedVeritas Operations Manager 4.1 Management Server.

Note: In the HA configuration for the Windows environment, it is mandatory touse VCS private NT domain to log in to Veritas Operations Manager.

See “Upgrading Management Server in high availability environment” on page 93.


See “Configuring a new Veritas Operations Manager 4.1 installation in highavailability environment” on page 62.


See “Configuring Veritas Operations Manager 4.1 in high availability environmentfor disaster recovery” on page 83.

Upgrading Management Server in high availabilityenvironment

Before you upgrade Veritas Operations Manager in the high availabilityenvironment, keep in mind the following:

■ The SFM_Services, the SFM_SStore, and the SFM_Xprtld service groups shouldbe online on one of the nodes of Veritas Operations Manager in the highavailability environment, which is the active node.

■ Symantec recommends that you take a backup of the Management Server data.

93Using Veritas Operations Manager in high availability environmentAbout upgrading the high availability and the disaster recovery configurations to Veritas Operations Manager 4.1

Note: You must upgrade the active node before you upgrade the slave nodes.

To upgrade Management Server in high availability environment to 4.1

1 Follow the steps to upgrade Management Server on the active node, and then,on the slave nodes.

After the upgrade on the active node, the SFM_Services service group, andthe SFM_SStore service group, are in a frozen state.

2 To unfreeze the service groups on the active node, run the following command:

■ On a UNIX host:/opt/VRTSsfmcs/config/vcs/sfmha start

■ On a Windows host:"installdir\VRTSsfmh\bin\perl.exe"

"installdir\VRTSsfmcs\config\vcs\sfmha" start

where, installdir is the installation directory of Management Server.

You must upgrade all the slave nodes before you unfreeze the service groupson the active node to prevent issues during failover.

3 In the console, verify that the SFM_Services, the SFM_SStore, and theSFM_Xprtld service groups are online on the active node.

Removing the high availability configurationTo remove the high availability configuration from Veritas Operations Manager,you need to launch the https://hostname:5634 URL.

Note: In Veritas Operations Manager 4.1, you cannot remove the Veritas OperationsManager HA-DR environment that is configured in the remote site.

The procedure uses the following host names:

My_virtual-host_1Name of the Management Server host that is configuredin a high availability environment

Using Veritas Operations Manager in high availability environmentRemoving the high availability configuration

94

To remove the high availability configuration from Veritas Operations Manager

1 Launch the following URL from a Web browser:

https://My_Virtual-host_1:5634

where, My_Virtual-host_1 is the virtual host name of the Management Serverhost that is configured in a high availability environment.

2 In the configuration dialog, select Reconfigure as a NON HA CMS and clickNext.

3 In the panel that lists the tasks that are to be performed to remove the VeritasOperations Manager HA configuration, click Rollover.

You must perform the rollover task on Node1 when you remove the highavailability configuration from Veritas Operations Manager.

After the rollover task, you remove the high availability configuration fromVeritas Operations Manager and move back to standalone mode. After youperform the rollover task, you do the following:

■ On Node1and Node2, remove thesfm_hadirectory from the mount locationof the file system.

■ On both the nodes, check for the VRTSsfmcs.pre_clus file on the locationvar/opt/.VRTSsfmcs.pre_clus/. If the VRTSsfmcs.pre_clus file exist onany of the nodes, remove the file.

4 In the next panel, view the status of the tasks that are performed as part ofremoving the Veritas Operations Manager HA configuration and do thefollowing:

■ Click the link that is displayed on the panel to log on to ManagementServer from which the HA configuration is removed.



95Using Veritas Operations Manager in high availability environmentRemoving the high availability configuration

Using Veritas Operations Manager in high availability environmentRemoving the high availability configuration

96

AActiveX 30

Bbacking up Veritas Operations Manager

on UNIX 50on Windows 51

browsers 30

Ccentralized management

Storage Foundation and High Availability 4.xand 5.x 17

Storage Foundation and High Availability 5.x 17configuring

existing Management Server installation in HAenvironment 74

Firefox 40Internet Explorer 40Management Server 38Web browsers 40

Ddeploying

Veritas Operations Manager 16domains

multiple 31downloading

Veritas Operations Manager 13

Ffirewalls

ports 31

Ggendeploy.pl 45

Iinstallation resources

Veritas Operations Manager 16installing

managed host 41UNIX 42Windows 43

Management Server 34UNIX 35Windows 36

Intranet zone security level 30

JJavaScript 30JScript 30

Mmanaged host

installing 41UNIX 42Windows 43

package 34types 12uninstalling on UNIX 58uninstalling on Windows 59upgrading 53

UNIX 54Windows 56

verifying installation on UNIX 45verifying installation on Windows 46verifying version using the console 57

Management Serverconfiguring 38configuring an existing installation in HA

environment 74installing 34

UNIX 35Windows 36

package 34uninstalling on UNIX 57

Index

Management Server (continued)uninstalling on Windows 58upgrading 47

UNIX 48Windows 49

upgrading in HA environment 93verifying installation on UNIX 37verifying installation on Windows 37verifying version using the console 56

Management Server HA-DRconfiguration prerequisites 82

Nnetwork requirements 31new Veritas Operations Manager installation in high

availability environmentconfiguring 62

Ppop-up blockers 30ports

firewalls 31

Rresolv.conf 31resources

installationVeritas Operations Manager 16

Ssecurity level 30SFM_HA setup

configure disaster recovery 81Solaris JumpStart installation 45SSL 30standalone management

defined 13SF 4.x and 5.x 18

TTCP 31toolbars 30

UUC 16UDP 31

uninstallingmanaged host on UNIX 58managed host on Windows 59Management Server on UNIX 57Management Server on Windows 58

upgradedisaster recovery 93HA 93HA-DR 93high availability 93managed host 53

upgradingmanaged host 53

UNIX 54Windows 56

Management Server 47UNIX 48Windows 49

Management Server in HA environment 93Veritas Operations Manager Add-ons 47

UTC 16

VVEA

deploymentstandalone management 18

verifyingmanaged host installation on UNIX 45managed host installation on Windows 46managed host version using the console 57Management Server installation on UNIX 37Management Server installation on Windows 37Management Server version using console 56

Veritas Enterprise Administrator.. See VEAVeritas Operations Manager

about 11backing up

on UNIX 50on Windows 51

choosing managed hosts 19choosing Management Server hosts 19choosing Web console hosts 30configuring Management Server 38deployment

centralized management 17deployment configurations 16downloading 13

managed host files 14Management Server files 13

Index98

Veritas Operations Manager (continued)installation resources 16installing

managed host on UNIX 42managed host on Windows 43Management Server on UNIX 35Management Server on Windows 36

managed host component 12Management Server component 12packages 34uninstalling UNIX managed host 58upgrading

managed host on UNIX 54managed host on Windows 56Management Server on UNIX 48Management Server on Windows 49

upgrading Management Server in HAenvironment 93

URL 13Web server component 12

Veritas Operations Manager Add-onsdownloading 47installing 47upgrading 47

Veritas Operations Manager deploymentcentralized management of Non-SF hosts 18

Veritas Operations Manager HAconfiguring an existing installation 74disaster recovery 81removing configuration 94

Veritas Operations Manager in HA environment 62configure for DR 81

Veritas Operations Manager in high availabilityenvironment for disaster recovery

configuring 83Veritas_Operations_Manager_CMS_4.1_Linux.bin 13,

35Veritas_Operations_Manager_CMS_4.1_SolSparc.bin 13,

35Veritas_Operations_Manager_CMS_4.1_Win.exe 13,

36virtual machines

cloning 44migrating 44

VRTSsfmcs package 34VRTSsfmh package 34, 41–42, 54VRTSsfmh_4.10.0xxx_Windows_arch_IA64.msi 43,

56

VRTSsfmh_4.10.0xxx_Windows_arch_x64.msi 43, 56

VRTSsfmh_4.10.0xxx_Windows_arch_x86.msi 43, 56

WWeb browsers

About 30configuring 40

Web console 30Web server

overview 12

99Index