veritas operations manager enterprise server 5.0 ...€¦ · all support services will be delivered...

Veritas™ Operations ManagerEnterprise Server 5.0Administrator's Guide

September 2012

Veritas™ Operations Manager Enterprise ServerAdministrator's Guide

The 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: 5.0

Document version: 5.0 Rev 1

Legal NoticeCopyright © 2012 Symantec Corporation. All rights reserved.

Symantec, the Symantec logo, Veritas, Veritas Storage Foundation, CommandCentral,NetBackup, Enterprise Vault, and LiveUpdate are trademarks or registered trademarks ofSymantec corporation or its affiliates in the U.S. and other countries. Other names may betrademarks 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. See the Third-party Legal Notices documentfor this product, which is available online or included in the base release media.

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/index.jsp

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:

www.symantec.com/business/support/contact_techsupp_static.jsp

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

http://www.symantec.com/business/support/index.jsp

http://www.symantec.com/business/support/contact_techsupp_static.jsp

■ 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:

www.symantec.com/business/support/

Customer serviceCustomer service information is available at the following URL:

www.symantec.com/business/support/

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

http://www.symantec.com/business/support/

http://www.symantec.com/business/support/

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

DocumentationYour feedback on product documentation is important to us. Send suggestionsfor improvements and reports on errors or omissions. Include the title anddocument version (located on the second page), and chapter and section titles ofthe text on which you are reporting. Send feedback to:

[email protected]

For information regarding the latest HOWTO articles, documentation updates,or to ask a question regarding product documentation, visit the Storage andClustering Documentation forum on Symantec Connect.

https://www-secure.symantec.com/connect/storage-management/forums/storage-and-clustering-documentation

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 Introducing Veritas Operations Manager EnterpriseServer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

About Veritas Operations Manager Advanced .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11About Veritas Operations Manager Enterprise Server ... . . . . . . . . . . . . . . . . . . . . . . 12About Veritas Operations Manager Advanced components ... . . . . . . . . . . . . . . . 13

Chapter 2 Configuring data rollup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

About data rollup .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15About data sources ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16About the objects that roll up to the Enterprise Server ... . . . . . . . . . . . . . . . . . . . . . 16Managing data sources ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Adding a data source to the Enterprise Server ... . . . . . . . . . . . . . . . . . . . . . . . . . . 17Modifying a data source ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Enabling data sources for data rollup .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Disabling data sources for data rollup .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Deleting a data source ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Using extended attributes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19About including extended attributes in your data source ... . . . . . . . . . . . . 19Including storage objects' extended attributes in data

rollup .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Removing storage objects' extended attributes from data

rollup .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Managing the data rollup schedule ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Setting data rollup frequency for a data source ... . . . . . . . . . . . . . . . . . . . . . . . . . 21Running an immediate data rollup .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Viewing data rollup status ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Troubleshooting Veritas Operations Manager Enterprise Server when

data rollup does not start ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Troubleshooting Veritas Operations Manager Enterprise Server when

data rollup fails ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Data rollup options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Contents

Chapter 3 Configuring business views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

About business views .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29About business view hierarchies ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Ways to build business views .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Adding and modifying business views in the console ... . . . . . . . . . . . . . . . . . . . . . . . 32Deleting business views in the console ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Adding, modifying, or deleting business view instances ... . . . . . . . . . . . . . . . . . . . . 34Assigning objects to a business view in the console ... . . . . . . . . . . . . . . . . . . . . . . . . . . 35

About business view rules ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Creating rules for assigning objects to a business view .... . . . . . . . . . . . . . . 36Business view rule options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Viewing, modifying, or deleting rules for assigning objects to a

business view .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Running rules for assigning objects to a business view .... . . . . . . . . . . . . . . 39Enabling or disabling business view rules ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Manually assigning objects to a business view in the

console ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Manually unassigning objects from a business view in the

console ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Object type namespaces and view names for business view

reports ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Transferring business view objects between Enterprise Servers ... . . . . . . . . . 43

Chapter 4 Configuring storage tiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

About storage tiers ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Adding storage tiers ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Storage tiers dialog options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Modifying storage tiers ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Managing storage tier rules ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

About storage tier rules ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48About storage tier rule syntax .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Storage tier rule attributes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Using the Basic Rule Builder to create and modify rules ... . . . . . . . . . . . . . 61Using the Advanced Rule Builder to create and modify

rules ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Adjusting storage tier rankings .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Deleting storage tiers ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Storage tiers options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Contents8

Chapter 5 Managing licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Viewing the Veritas Operations Manager Advanced licenseentitlement reports ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

About the Storage Array Capacity License Entitlement Report ... . . . . . . . . . . . 76About the Host Count and NAS Capacity License Entitlement

Report ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77About Veritas Operations Manager license deployment

management ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78About Symantec licensing and pricing .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Chapter 6 Configuring authentication and authorization . . . . . . . . . . . . . 81

About authentication and authorization .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Configuring authentication brokers ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Adding and removing secondary brokers ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Configuring AD or LDAP authentication .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Removing AD or LDAP authentication .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Enabling and disabling domains .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Configuring user authorization .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Adding and removing security groups .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Editing security groups .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Chapter 7 Managing the Enterprise Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Stopping and starting the Enterprise Server components ... . . . . . . . . . . . . . . . . . 95Configuring Enterprise Server settings ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Backing up and restoring Veritas Operations Manager Enterprise

Server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Gathering troubleshooting information .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Appendix A Creating and managing business views with thecommand line interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Creating and managing business views using the command lineinterface ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

About the business view files ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102About the .view structure file ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Sample .view structure file ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103About the CSV object files ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Adding business views using the command line interface ... . . . . . . . . . . . . . . . . 108Updating business views using the command line interface ... . . . . . . . . . . . . . 109Importing business views using the command line interface ... . . . . . . . . . . . . 110

Before you import a business view .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

9Contents

Importing the business view files ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110Associating undefined objects to business views .... . . . . . . . . . . . . . . . . . . . . 113Setting business view import options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Deleting business views using the command line interface ... . . . . . . . . . . . . . . 116Exporting business views using the command line interface ... . . . . . . . . . . . . 117

Appendix B Command and configuration file reference forbusiness views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

bv_create.bat ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120bv_describe_views.bat ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121bv_export_csv.bat ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122bv_import_csv.bat ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Appendix C Log file reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Default business view import and export log files ... . . . . . . . . . . . . . . . . . . . . . . . . . . 127Default Cognos log files ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128Default console log files ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129Default data rollup log files ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Contents10

Introducing VeritasOperations ManagerEnterprise Server

This chapter includes the following topics:

■ About Veritas Operations Manager Advanced

■ About Veritas Operations Manager Enterprise Server

■ About Veritas Operations Manager Advanced components

About Veritas Operations Manager AdvancedVeritas Operations Manager Advanced includes Enterprise Server and ManagementServer packages. A Veritas Operations Manager Advanced deployment consistsof an Enterprise Server and one or more Management Servers. Veritas OperationsManager Management Server is also available as a separate product withoutEnterprise Server.

Management Server provides reporting for a single datacenter and is used at anoperational level. Enterprise Server lets you aggregate storage information frommultiple datacenters and view storage assets by a variety of business dimensions.For example, business information executive can use an Enterprise Server toidentify the trend of unclaimed tier 1 storage in your New York and Zurichdatacenters. Storage administrators at each site can use Management Servers tofind out which arrays or LUNs are unclaimed.

This document describes Veritas Operations Manager Enterprise Server. Forinformation about Management Server, refer to the Veritas Operations ManagerManagement Server documentation.

1Chapter

About VeritasOperationsManager Enterprise ServerVeritas Operations Manager Enterprise Server is provided as part of VeritasOperations Manager Advanced.

Veritas Operations Manager Enterprise Server improves storage servicemanagement by aligning IT to business objectives. Veritas Operations ManagerEnterprise Server offers business information executives and storageadministrators the following:

■ Global views of the storage that are assets mapped to your organization

■ Business insights into inventory utilization

■ On-demand customized reporting

■ Personalized Home pages for multiple users

The central reporting interface on Veritas Operations Manager Enterprise Serverunifies storage information from multiple datacenters. It organizes the informationalong the lines of your business. If you are a business information executive, youcan use Enterprise Server to view your storage environment at the enterpriselevel. You can then drill down into your organization's hierarchy, which you canorganize by location, departments, or any other logical business unit. Thissummarized information enables you to assess trends in your storage environment,which you can then analyze to assign responsibility.

If you are a storage administrator, you can use Enterprise Server to identifycapacity trends and review storage inventory. You can also determine your storagecosts per business unit. With this information, you can promote storageaccountability and decrease costs.

Table 1-1 On demand reporting in Veritas Operations Manager EnterpriseServer

Choose any scopeChoose any report type

■ Enterprise

■ Geography

■ Application

■ Business unit

■ Storage tier

■ Vendor

■ Array

■ Unclaimed storage

■ Capacity trending

■ Database, file system, or volume managerutilization

■ Burn rate

■ Billing detail

■ Inventory report

Use Veritas Operations Manager Enterprise Server to answer questions like thefollowing:

Introducing Veritas Operations Manager Enterprise ServerAbout Veritas Operations Manager Enterprise Server

12

■ Which hosts and file systems can I reclaim storage from?

■ How much free storage is there across the enterprise?

■ How much storage should I charge each department for?

■ Which databases grow out of control?

■ What will my tier 1 storage growth look like next year?

■ How is capacity trending in North America versus Europe?

■ How is storage allocated in the finance department?

■ How many expired Storage Foundation licenses need to be renewed across theenterprise?

About Veritas Operations Manager Advancedcomponents

Veritas Operations Manager Advanced consists of the following components:

■ Data sources: One or more Veritas Operations Manager Management Servers.

■ Kettle: A software tool that aggregates storage network information from oneor more datacenters . It extracts, transforms, and loads the data from VeritasOperations Manager Management Server databases into the Enterprise ServerSybase ASA database. Veritas Operations Manager Enterprise Server usesKettle in the data rollup process.

■ Embedded Sybase ASA database: A repository for storage data that derivesfrom Veritas Operations Manager Management Servers. The Sybase ASAdatabase can be on the Enterprise Server host or another host.

■ Cognos: A reporting engine that lets you create customized reports based onthe data that is rolled up from multiple data sources. Cognos also lets youcustomize your own product dashboards.Cognos includes many options, including the following:

■ Cognos Connection: Lets you manage the reports that are created in QueryStudio or Report Studio

■ Query Studio: Lets you create ad hoc reports quickly

■ Report Studio: Lets you create advanced reports

■ Veritas Operations Manager Enterprise Server console: A browser-basedconsole that lets you do the following:

■ Access Cognos Connection.

13Introducing Veritas Operations Manager Enterprise ServerAbout Veritas Operations Manager Advanced components

■ Create ad hoc reports.

■ Create advanced reports.

■ Set configuration options.

■ Display reports.

Introducing Veritas Operations Manager Enterprise ServerAbout Veritas Operations Manager Advanced components

14

Configuring data rollup


■ About data rollup

■ About data sources

■ About the objects that roll up to the Enterprise Server

■ Managing data sources

■ Using extended attributes

■ Managing the data rollup schedule

■ Viewing data rollup status

■ Troubleshooting Veritas Operations Manager Enterprise Server when datarollup does not start

■ Troubleshooting Veritas Operations Manager Enterprise Server when datarollup fails

■ Data rollup options

About data rollupData rollup is the process that rolls up data from your Veritas Operations ManagerManagement Servers into an Enterprise Server. To perform data rollup, VeritasOperations Manager Enterprise Server uses Kettle. Kettle is a software tool thatperforms the extract, transform, and load (ETL) process. The ETL process extractsdata from your Veritas Operations Manager Management Servers databases. Then,ETL transforms the data so Veritas Operations Manager Enterprise Server canuse it, and then loads the data into an ASA database.

2Chapter

About data sourcesA data source is a Veritas Operations Manager Management Server that sendsdata to the Enterprise Server. You manage your data sources in the VeritasOperations Manager Enterprise Server console.

About the objects that roll up to the Enterprise ServerData rollup is when a Veritas Operations Manager Management Server sends datato a Veritas Operations Manager Enterprise Server.

When you perform data rollup from your data sources, information about objectsand their attributes and extended attributes rolls up to Veritas Operations ManagerEnterprise Server.

Storage objects that roll up to Veritas Operations Manager Enterprise Serverinclude the following:

■ Arrays

■ Databases

■ File systems

■ Hosts

■ LUNs

■ Disk Groups

■ Clusters

■ Business Entities

■ Product licenses

Information about using extended attributes is covered in the following topic:

See “Using extended attributes” on page 19.

Managing data sourcesData sources are Veritas Operations Manager Management Servers that send datato the Enterprise Server. You can add, modify, and remove data sources in theVeritas Operations Manager Enterprise Server console.

Configuring data rollupAbout data sources

16

Adding a data source to the Enterprise ServerYou add a data source (VOM Management Server) to the Enterprise Server so thatyou can roll up information from that data source.

To add a data source to Veritas Operations Manager Enterprise Server

1 In the Veritas Operations Manager Enterprise Server console, click DataRollup > Data Sources.

2 Click the Add Data Source icon.

See “Data rollup options” on page 27.

3 In the Add New Data Source dialog, enter the VOM Management Server IPaddress or fully qualified host name (FQHN).

4 Enter the user name and password for the VOM Management Server.

5 Click OK.

The new data source appears in the Data Sources table. If you enabled thedata source for data rollup, data rollup runs at the set schedule. You can alsoperform an immediate data rollup.

See “Managing the data rollup schedule” on page 21.

Modifying a data sourceAfter you add a data source for the Enterprise Server, you may need to modifyinformation about that data source. For example, you might want to change thetime of day that data rollup runs for the data source. Or, you might want to changethe name of the data source.

To modify a data source


2 In the Data Sources table, select the data source that you want to modify.

3 In the Data Sources dialog box, make one or more modifications.

You can enable or disable the data source, set the rollup start time, and selectserver time or data source time.

4 Click Save Changes.

The data sources are changed immediately.

17Configuring data rollupManaging data sources

Enabling data sources for data rollupIf you disabled a data source for data rollup to an Enterprise Server, you can turnon data rollup for that data source. When you turn on data rollup for a data source,data rollup runs at the set schedule. You can perform immediate data rollups fromthat data source.

To enable a data source for data rollup


2 In the DataSources table, select the data source for which you want to enabledata rollup.

3 In the Data Source panel, select (check) the Enabled checkbox.


Veritas Operations Manager Enterprise Server enables the data source fordata rollup.

Disabling data sources for data rollupAfter you add a data source to an Enterprise Server, you can disable data rollupfor the data source. When you disable data rollup for a data source, data rollupdoes not run at the set schedule. So, you cannot perform immediate data rollupsfrom that data source.

To disable a data source for data rollup


2 In the Data Sources table, select the data source for which you want to disabledata rollup.

3 In the Data Source panel, select (uncheck) the Enabled checkbox.


Data rollup does not run for the data source at the set schedule and you cannotperform an immediate data rollup.

Veritas Operations Manager Enterprise Server disables the data source fordata rollup.

Deleting a data sourceIf you no longer need to roll up data from a data source, you can delete the datasource from the Enterprise Server.

Configuring data rollupManaging data sources

18

To delete a data source


2 In the Data Sources table, select the data source that you want to delete.

3 Click the Delete Data Source icon.


4 Click OK to confirm the delete.

The deleted data source no longer appears in the Data Source table. Historicdata from this data source remains in the Veritas Operations ManagerEnterprise Server database. You can still use the data in reports.

Using extended attributesAn attribute is the information that pertains to a storage object type. All storageobjects have a standard set of attributes. Extended attributes are the user-createdattributes that convey the information that is meaningful to you. But thisinformation is not part of the object’s physical or software makeup. Theseattributes are not discovered automatically in Veritas Operations Manager. Instead,storage administrators use Veritas Operations Manager to add them to storageobjects.

Veritas Operations Manager Enterprise Server supports extended attributes forall storage objects. You can use extended attributes in the reports that includethese storage objects.

Examples of extended attributes include:

■ Physical location of the object

■ Warranty date for the object

■ Date of purchase

About including extended attributes in your data sourceYou can create extended attributes in Veritas Operations Manager ManagementServer and then roll them up to Veritas Operations Manager Enterprise Server.Because extended attributes are included during the data rollup process, you'llwant to perform an initial data rollup to discover extended attributes. After youselect the extended attributes that you want to include, perform an additionalrollup so that you can use these extended attributes in reports. You add or removea data source’s extended attributes using the Veritas Operations ManagerEnterprise Server console.

19Configuring data rollupUsing extended attributes

When you edit extended attributes, be aware of the following:

■ If you perform data rollup while a user edits extended attributes, the datarollup may not include extended attribute changes. The extended attributesare reflected in the next data rollup.

■ Only one user can edit extended attributes at a time. If you attempt to editextended attributes while another user edits them, you receive a message totry again later.

If you delete an object’s extended attribute in Veritas Operations Manager, thenext time you rollup that storage object, the object’s extended attribute will haveno value. To prevent the blank value, remove the deleted extended attribute fromthe Veritas Operations Manager Enterprise Server Attributes list for the affectedstorage object type. Likewise, when you add an extended attribute to a storageobject in Veritas Operations Manager, add the new extended attribute in thestorage object type’s Veritas Operations Manager Enterprise Server Attributeslist for that attribute to show in your reports.

Including storage objects' extended attributes in data rollupYou can add a storage object's extended attributes to your data rollup to anEnterprise Server. A small delay exists between the time you edit a storage object'sextended attributes and the time they become available for use in reports. Youcan expedite the process by performing an immediate data rollup.

See “Running an immediate data rollup” on page 22.

To include a storage object's extended attribute in your data rollup

1 In the Veritas Operations Manager Enterprise Server console, click Manage> Extended Attributes.

2 In the Object type drop-down list, select a storage object.

All attributes that were discovered during a previous rollup for a storageobject type appear in the Available Attributes list. To make extendedattributes available for reporting in Veritas Operations Manager EnterpriseServer, you must select extended attributes for inclusion.

3 In the Available Attributes list, do one of the following and click SaveChanges.

■ To add an individual attribute, select the attribute and click >

■ To add all attributes in the list, click >>

Configuring data rollupUsing extended attributes

20

Removing storage objects' extended attributes from data rollupYou can remove an object's extended attributes from your data rollup to anEnterprise Server. A small delay exists between the time you edit a storage object'sextended attributes the time they become available for use in reports.

To remove a storage object's extended attributes from your data rollup

1 In the Veritas Operations Manager Enterprise Server console, click Manage> Extended Attributes.

2 In the Object type drop-down list, select a storage object.

3 In the list of selected attributes, do the following and click Save Changes:

■ To remove an individual attribute, select the attribute and click <

■ To remove all attributes in the list, click <<

Managing the data rollup scheduleYou can start the data rollup process for your Veritas Operations ManagerEnterprise Server data sources in the following ways:

■ You can set schedules for Veritas Operations Manager Enterprise Server tostart the data rollup process at the specified time.

■ You can start the data rollup process immediately.

Setting data rollup frequency for a data sourceYou roll up data sources daily, and schedule the time of day for each individualdata source (for example, 2:00 A.M.).

To schedule the time of day that data rollup runs for each individual data source,you must add or modify a data source.

The schedule can be based on either the Enterprise Server time or the data sourcetime.

See “Adding a data source to the Enterprise Server” on page 17.

See “Modifying a data source” on page 17.

To set the rollup time for a data source


2 Select the data source.

3 In the Schedule area, select a schedule and click Update Settings.

21Configuring data rollupManaging the data rollup schedule

Running an immediate data rollupYou do not have to wait for Veritas Operations Manager Enterprise Server datarollup to run at the scheduled time for a data source. If you want, you can run animmediate data rollup.

If you run data rollup from a data source more than once a day, Veritas OperationsManager Enterprise Server only saves data from the last successful rollup of theday. The new data overwrites the data from the previous data rollup.

To run an immediate data rollup


2 In the Data Sources table, select the data source that you want to roll up.

3 Click the Rollup Data Source Now icon.


4 To confirm data rollup, click OK.

The data rollup process starts immediately. During and after the process,you can view the status of data rollup.

See “Viewing data rollup status” on page 22.

Viewing data rollup statusYou can view the status of data rollup for each of your data sources in the VeritasOperations Manager Enterprise Server console. When you view the status, youcan see the current state of data rollup for each data source.

The following table details the different processing states in the data rollupprocess.

Table 2-1 Data rollup processing states

DescriptionStatus

The data rollup process has started. The data source’s databaseschema is updated.

Initializing

Data is processed remotely before it is transferred to VeritasOperations Manager Enterprise Server.

Remote Processing

Data is transferred across the network from the data source toVeritas Operations Manager Enterprise Server.

Uploading

Configuring data rollupViewing data rollup status

22

Table 2-1 Data rollup processing states (continued)

DescriptionStatus

Data is loaded into a temporary area of the Veritas OperationsManager Enterprise Server database before further processing.

Staging

Data undergoes final processing. It is loaded from a temporaryarea of the Veritas Operations Manager Enterprise Serverdatabase into the production area.

Loading

Data rollup has succeeded with no errors or warnings. The datais available for reporting.

Succeeded

Data rollup has succeeded with warnings. The data is availablefor reporting.

Succeeded withWarnings

Data rollup failed. No data from the rollup batch is available forreporting. Review the status message for details about why datarollup failed.

See “Troubleshooting Veritas Operations Manager EnterpriseServer when data rollup does not start” on page 24.

See “Troubleshooting Veritas Operations Manager EnterpriseServer when data rollup fails” on page 25.

Failed

Veritas Operations Manager Enterprise Server replaced the datarollup batch with a newer data rollup batch. The newer datarollup batch rolled up successfully from the same data source onthe same day.

Note: Veritas Operations Manager Enterprise Server retainsonly one batch of data for a data source per day.

Overwritten

In the console, you can view the status of the last data rollup for all data sources.You can also view a report that details the status of past data rollups for all datasources.

To view the status of the last data rollup for all data sources

◆ In the Veritas Operations Manager Enterprise Server console, in the Homepane, or in the Data Rollup > Data Sources panes, at the bottom right of thepane, click See details.

A panel displays the details of the last data rollup for all data sources.

23Configuring data rollupViewing data rollup status

To view a report that details the status of past data rollups for all data sources

◆ In the Veritas Operations Manager Enterprise Server console, click DataRollup > Status.

The Rollup Status report displays.

Troubleshooting Veritas Operations ManagerEnterprise Server when data rollup does not start

If data rollup to an Enterprise Server does not start, do the following:

■ Verify that the data source’s database is running.

■ Verify that the extract, transform, and load (ETL) scheduler is configured torun every minute.

■ Check the ETL execute log file for errors.

After you perform these steps, start the data rollup process for the data source.


To verify that the ETL scheduler is configured to run every minute

1 Open an operating system console and log in to the Veritas OperationsManager Enterprise Server host as a user with administrator-level privileges.

2 Type the following command: schtasks.

An entry similar to the following should display:

TaskName Next Run Time Status

==================== ====================== =======

VOM Adv Rollup Task 09:47:00 AM, 7/6/2011

3 If the entry shown in step 2 does not display, to configure the ETL schedulerto run every minute, do the following:

■ Change to the Veritas Operations Manager Enterprise Server bin directory.By default, the directory is:\Program Files\Veritas\VRTSvomer\bin

■ Type the following command:etl_scheduler.bat --setup

Configuring data rollupTroubleshooting Veritas Operations Manager Enterprise Server when data rollup does not start

24

To check the ETL execute log file for errors

1 Open the ETL execute log file (etl_execute.log)

By default, etl_execute.log is in:

\ProgramData\VERITAS\VRTSvomer\logs

2 Search for the following text string: error.

3 If the text strings are present, use the accompanying information to correctthe error.

Troubleshooting Veritas Operations ManagerEnterprise Server when data rollup fails

If data rollup to an Enterprise Server fails, in the Rollup Status report, review thestatus message for details about why data rollup failed.

To troubleshoot a failed data rollup, do the following:

■ Check your network connection to the data source.

■ Verify that the data source’s database is running.

■ Verify data source information.

■ Check the data source’s data rollup log file for errors.

■ Check the data source’s staging log file for errors.

After you perform these steps, start the data rollup process for the data source.


To verify data source information


2 In the Data Sources table, select the data source that failed data rollup.

3 Verify that the information for the data source is correct.

4 If any information is not correct, make the required change.

25Configuring data rollupTroubleshooting Veritas Operations Manager Enterprise Server when data rollup fails

To check the data source’s data rollup log file for errors

1 Open the data rollup log file (rollup_mgmt_datasourcename.log).

By default, rollup_mgmt_datasourcename.log is in:

\ProgramData\VERITAS\VRTSvomer\logs\etl\

rollup_process\datasourcename

or registry key VOM_ER_VAR_DIR:

%VOM_ER_VAR_DIR%\logs\etl\rollup_process\datasourcename

where datasourcename is the name of the data source, as displayed in theVeritas Operations Manager Enterprise Server console.

2 Search for the keyword ERROR

3 If the keyword is found, correct the error.

The error contains a description that you can use to correct the error.

To check the data source’s staging log file for errors

1 Open the staging log file (staging_timestamp*.log).

By default, staging_timestamp*.log is in:


rollup_process\datasourcename



where:

is the name of the data source, as displayed in the VeritasOperations Manager Enterprise Server console.

datasourcename

is the time that the staging process took place for the data source.timestamp

2 Search for the keyword stderr

3 If you find the keyword, make a note of the object log file that the errorreferences.

Configuring data rollupTroubleshooting Veritas Operations Manager Enterprise Server when data rollup fails

26

4 Open the object log file (objectname.log).

By default, objectname.log is in:


rollup_process\datasourcename\import_to_staging



where:

is the name of the file you found in step 3.objectname

is the name of the data source, as displayed in the VeritasOperations Manager Enterprise Server console.

datasourcename

5 Search for the keyword ERROR

6 If you find the keyword, use the error description to correct the error.

Data rollup optionsYou can use several options to manage the process of rolling up data from VOMManagement Servers to Veritas Operations Manager Enterprise Server. Thefollowing table describes those options.

Table 2-2 Data rollup options

DescriptionIconOption

Loads the data source dialog boxes, which youcan use to create a new data source.

Add Data Source

Deletes the selected data source.Delete Data Source

Initiates the data rollup for the selected datasource.

Rollup Data SourceNow

27Configuring data rollupData rollup options

Configuring data rollupData rollup options

28

Configuring business views


■ About business views

■ Adding and modifying business views in the console

■ Deleting business views in the console

■ Adding, modifying, or deleting business view instances

■ Assigning objects to a business view in the console

■ Object type namespaces and view names for business view reports

■ Transferring business view objects between Enterprise Servers

About business viewsThe business view feature of Veritas Operations Manager Enterprise Server letsyou gather information about storage objects and relate the information to yourbusiness. Business views organize data according to your business units,geography, or software applications. For example, you can construct a businessview to show available physical capacity across your global business units.

Business views can help you answer the following questions:

■ Where are my assets located throughout the world?

■ How much physical storage capacity is available at each of these locations?

■ How much of this capacity is currently used? How much remains?

■ Are there any critical business applications running on the servers that havebecome low on capacity?

3Chapter

You can include your business views in the ad hoc reports that show storage dataacross your lines of business, geographic business units, or applications.

Additionally, you can use business views to perform chargeback analysis.

See Veritas Operations Manager Enterprise Server User's Guide.

The following are some examples of object types that you can include in businessviews:

■ Array

■ File System

■ Host

■ Volume

■ NAS File System

■ NAS Share

■ Cluster

■ Service Group

About business view hierarchiesIn preparation for adding a business view, think about the questions that youwant to answer about storage objects in your environment. With those questionsin mind, sketch out the hierarchy you want to display your data in. Depending onthe hierarchy you choose, Veritas Operations Manager Enterprise Server canreport on your data by business unit, geographic location, application, or anyother structure you choose.

Configuring business viewsAbout business views

30

Figure 3-1 Example business view hierarchies

Example Business View Hierarchies

Business Viewnames

Business Viewlevels

BusinessView

Instances

Support

Beijing

Shanghai

Guangzhou

Sales

IT

Group

Company

Business Unit

Continent

Country

City

Organization Geography

Ways to build business viewsYou can build Veritas Operations Manager Enterprise Server business views inthe following ways:

■ You can add business views in the Enterprise Server console, or you can usescripts to create business views and import them into the Enterprise Server.After you add business views, you see them in the console.

■ As you develop business views, you assign storage or cluster objects to themin the console or using the command line interface. You can define rules inthe console to assign objects dynamically as the objects roll up.See “Assigning objects to a business view in the console” on page 35.

31Configuring business viewsAbout business views

■ You can transfer business view information from one Enterprise Server toanother.

Adding and modifying business views in the consoleYou can add and modify business views in the Veritas Operations ManagerEnterprise Server console.

Note: Updating a business view may take some time. The update process alsoupdates Cognos.

Note: Although you can delete business views, it is not recommended. When youdelete a business view, you can no longer use it in reports. As a result, all existingreports that use the business view no longer work properly.

To add a business view

1 In the Veritas Operations Manager Enterprise Server console, click Manage> Business Views > Hierarchies.

2 Click the Add icon at the top of the table.

3 In the Description area, enter a name and description.

For example, you might name the business view "Geographies" and describeit as "Tracks storage usage in North America, Europe, and Asia."

4 In the Object Types area, select the types of objects you want to include inthe business view.

5 Before adding levels, have your hierarchy planned. After levels are added,you can delete levels from the bottom up, but you cannot change the orderor name of a level.

In the Levels area, click the Add icon. In the Add Level dialog box, providea name and description for the level, and click Add.

For example, you might define level 1 as "Continent," level 2 as "Country,"and level 3 as "City."

6 Click the Add button in the lower-right corner to add the business view.

7 After adding a business view you can create instances for each level andassign objects.

See “Adding, modifying, or deleting business view instances” on page 34.

See “Assigning objects to a business view in the console” on page 35.

Configuring business viewsAdding and modifying business views in the console

32

To modify a business view


2 From the table, select the business view that you want to modify.

3 To add or remove object types, select or deselect items in the Object Typesscrolling list.

4 To edit the business view levels, do one or more of the following:

■ Add a level. In the Levels area, create one or more levels by clicking theAdd icon. In the Add Level dialog box, provide a name and description,and click Add.The new level is added at the lowest level in the hierarchy. For example,if you have two levels, where level 1 is Continent and level 2 is Country,clicking Add adds a third level to the hierarchy for City.

■ Edit the description of a level. In the Levels area, select a level and clickthe Edit icon.

■ Delete a level. In the Levels area, select a level and click the Delete icon.Veritas Operations Manager Enterprise Server deletes the lowest level inthe hierarchy. For example, if you have three levels where level 1 isContinent, level 2 is Country, and level 3 is City, then clicking Deletedeletes level 3.

5 Click Update to update the business view with the changes.

Deleting business views in the consoleYou can delete business views in the Veritas Operations Manager Enterprise Serverconsole.

Warning: When you delete a business view, you can no longer use it in reports. Asa result, all existing reports that use the business view no longer work properly.Because of this issue, we recommend that you do not delete business views.

Note:Deleting a business view may take some time. The delete process also updatesCognos.

33Configuring business viewsDeleting business views in the console

To delete a business view


2 In the table, select the business view that you want to delete.

3 Click the Delete icon at the top of the table.

Adding, modifying, or deleting business viewinstances

Business view instances in Veritas Operations Manager Enterprise Server providethe specifics behind the business view hierarchical levels. For example, "NorthAmerica" is an instance of the "Continent" level and "Canada" is an instance ofthe "Country" level.

Add instances for each level that is defined for a business view. You can also editthe name or description of an existing instance or delete instances that you nolonger need.

To add a business view instance

1 In the Veritas Operations Manager Enterprise Server console, click Manage> Business Views > Assignments.

Alternatively, you can add instances with the Create Instances icon onBusiness View Hierarchies.

2 From the Business Views drop-down list, select the business view to whichyou want to add an instance.

3 In the Instances pane, select the node to which you want to add a child orsibling instance.

When first creating instances for the business view, follow these guidelines:

■ The top-level node is the business view. Select the top-level node to addchild instances for Level 1 of the hierarchy.

■ After adding an instance, either add sibling instances for the same levelor add child instances for the next level.For example, if Level 1 is Continent, and Level 2 is Country, add an instancefor North America. Then select North America and add Level 2 instances,such as Canada.

■ At the lowest level instances, you can add children only by first adding anew level on the Hierarchies page.

Configuring business viewsAdding, modifying, or deleting business view instances

34

4 To add the instance, click the Add Child Instance or Add Sibling Instanceicon.

Or, right-click the node and select Add Child Instance or Add SiblingInstance.

5 Type a name and description for the instance, and click Add.

To delete a business view instance


2 From theBusinessViews drop-down list, select the business view from whichyou want to delete an instance.

3 In the Instances pane, select the instance you want to delete. If you deletean instance, any associated child instances are also deleted. If you assignedobjects to the instances, the objects become unassigned.

4 Click the Delete Instance icon. (Or, right-click the instance and select DeleteInstance.)

5 Confirm the deletion.

To edit an instance name or description


2 From the Business Views drop-down list, select the business view for whichyou want to edit an instance.

3 In the Instances pane, select the instance you want to edit.

4 Click the Edit Instance icon. (Or, right-click the instance and select EditInstance.)

5 In the EditInstance dialog box, edit the name and description and click Save.

Assigning objects to a business view in the consoleIn Veritas Operations Manager Enterprise Server, business view objects are theentities you seek information about. For example, objects can be arrays, filesystems, or hosts. You assign objects to business view instances.

To assign objects most efficiently, use the Veritas Operations Manager EnterpriseServer console to create rules for object assignment.You can also assign objectsmanually.

See “About business view rules” on page 36.

35Configuring business viewsAssigning objects to a business view in the console

See “Creating rules for assigning objects to a business view” on page 36.

See “Viewing, modifying, or deleting rules for assigning objects to a business view”on page 38.

See “Running rules for assigning objects to a business view” on page 39.

See “Enabling or disabling business view rules” on page 40.

See “Manually assigning objects to a business view in the console” on page 41.

See “Manually unassigning objects from a business view in the console” on page 42.

See “About data rollup” on page 15.

You can also assign objects using the command line interface.

See “Creating and managing business views using the command line interface”on page 101.

About business view rulesBusiness view rules in Veritas Operations Manager Enterprise Server determinehow objects are assigned to business view instances. You can create rules to assignlarge numbers of objects during initial configuration. The same rules candynamically assign new objects as they are rolled up.

Modifying a rule reassigns any objects according to the changes in the rule.Deleting a rule moves all objects assigned by the rule back to an unassigned state.

Creating rules for assigning objects to a business viewUse the Veritas Operations Manager Enterprise Server console to create rules forassigning objects to instances of a business view.

Each rule defines the conditions for assigning one object type to one instance.Objects are assigned to the instances at the lowest level of the hierarchy (leafinstance). You create one rule per leaf instance for each type of object. You selectfrom predefined attributes and operators when defining rule conditions.

To create a rule for assigning objects to a business view


2 From the Business Views drop-down list, select the business view to whichyou want to assign objects.

3 In the Instances pane, select the instance to which you want to assign objects.

4 On the Manage Rules tab, under Rules for Instances, select the object typeand click the Add Rule icon.

Configuring business viewsAssigning objects to a business view in the console

36

5 In the Add Rule dialog box, define the rule. Assign a name and descriptionand specify the rule conditions.

See “Business view rule options” on page 37.

6 Optionally click Test Rule to verify the rule syntax. The Test Rule Resultsdialog box displays a list of all objects to be assigned by the rule. Afterreviewing the results, click OK.

7 Click Save. The rule is added to the rules table for that object type.

Warning: If the Automaticassignment check box is selected for the businessview, all rules for the business view are run automatically whenever objectsare rolled up, except for any rules that are set as disabled. To disable or enablerules after saving, use the Disablerules or Enablerules icons above the tableof rules.

Business view rule optionsUse the Veritas Operations Manager Enterprise Server console to create rules forassigning objects to instances of a business view.

Specify the following information when adding the rule:

Selected by default. Disable a rule if you do not want it tobe run. You can also enable or disable rules later using theicons above the table of rules on the Manage Rules tab.

Enabled

The rule name must be unique within the business view.Rule name and description

Select from available object types. The types availabledepend on how the business view is set up.

If you are modifying an existing rule, this selection isdisabled.

Object type

Shows the selected instance.Instance


Create conditions for the rule. A condition consists of anattribute, an operator, and a value. The predefined attributeschange depending on the selected object type.

Select the attribute, the operator, and specify a value. Valuestrings are case sensitive.

You can create up to five conditions for a rule.

To add another condition click the Add icon on the right.Choose whether to use an AND or OR operator in thedrop-down selection on the left. The TextView box displaysthe conditions as you create them. Conditions are appliedin order of precedence.

Conditions

Viewing, modifying, or deleting rules for assigning objects to a businessview

In the Veritas Operations Manager Enterprise Server console, use the followingprocedures to view, modify, or delete rules for assigning objects to a businessview.

Warning: Modifying a rule reassigns objects according to the changes in the rule.Deleting a rule moves all objects previously assigned by the rule back to anunassigned state.

To view rules for assigning objects to a business view


2 From the Business Views drop-down list, select the business view to whichthe rule is applied.

3 In the Instances pane, select the business view if you want to see all rules.To see rules for a specific instance, select the node in the tree.

4 On the Manage Rules tab, click the tab for the type of object that is assignedby the rule. For example, click the Host tab.

To modify rules for assigning objects to a business view




38

3 In the Instances pane, select the bottom-level instance to which the rule isapplied. Or, if you want to modify rules for more than one instance, select anode above that level in the tree.


5 Select the row containing the rule and click the Modify rule icon above thetable.

You can modify only one rule at a time.

6 Make the desired changes.

See “Business view rule options” on page 37.

7 Optionally, test the rule before saving. The results dialog box shows anyobjects that were not previously assigned by the rule but that now satisfy themodified rule conditions.

To delete rules for assigning objects to a business view



3 In the Instances pane, select the bottom-level instance to which the rule isapplied. Or, if you want to delete rules for more than one instance, select anode above that level in the tree.


5 Select the row containing the rule and click the Remove selected rule iconabove the table. The Delete Rule dialog box lists the objects to be moved toan unassigned state.

You can delete only one rule at a time.

Running rules for assigning objects to a business viewThe Veritas Operations Manager Enterprise Server console lets you run businessview rules on demand. You can also enable running rules dynamically wheneverobjects are rolled up.


To run rules on demand for assigning objects to a business view


2 From the Business Views drop-down list, select the business view.

3 Click Run all rules. A dialog box lists all rules that are currently enabled forthe selected business view. Confirm running the rules.

To enable running rules dynamically whenever objects are rolled up


2 From the Business Views drop-down list, select the business view.

3 Select the Automatic assignment checkbox. A message box prompts you toconfirm the automatic assignment. All rules that are enabled for the selectedbusiness view are e run when objects are rolled up.

Enabling or disabling business view rulesThe Veritas Operations Manager Enterprise Server console lets you enable ordisable business view rules at any time. When business view rules are run, onlythe rules that are currently enabled are run. You can enable or disable multiplerules at one time.

To enable or disable business view rules


2 From the Business Views drop-down list, select the business view to whichthe rules are applied.

3 In the Instances pane, select the business view if you want to see all rules.To see rules for a specific instance, select the node in the tree.

4 On the Manage Rules tab, click the tab for the type of object that is assignedby the rules that you want to enable or disable. For example, click the Hosttab.

5 Select one or more rules.

6 Click the Enable rules or Disable rules icon above the table. The Enabledcolumn shows No or Yes depending on the icon you clicked.


40

Manually assigning objects to a business view in the consoleThe Veritas Operations Manager Enterprise Server console lets you manuallyassign objects to instances within a business view.

If you manually assign objects in the console, the number of unassigned objectsin the UnassignedObjects pane is per business view, not per instance. If you havea large number of objects, you can filter them.

Note: The Unassigned Objects table displays the first 1000 rows only. To movethrough the objects, click the Next and Previous icons.

To filter objects


2 On the Objects tab, go to the object pane in which you want to filter objects(the Objects Assigned to Instance pane or the Unassigned Objects pane).

3 Click the tab corresponding to the type of object you want to filter. Forexample, click the Array tab.

4 Click the Filter icon, to the right of the table.

5 Check the boxes of the criteria by which you want to filter the objects. Typea value in each Value textbox you want to filter on. Veritas OperationsManager Enterprise Server retrieves all of the object names that contain thefilter string.

To manually assign objects to a business view


2 From the Business Views drop-down list, select the business view to whichyou want to assign objects.

3 In the Instancespane, select the instance to which you want to assign objects.

4 On the Objects tab, in the Unassigned Objects pane, click the tabcorresponding to the type of object you want to assign. For example, click theArray, File System, or Host tab.

5 Select the checkboxes for the objects you want to assign to the instance.

6 Click the Assign link.


Manually unassigning objects from a business view in the consoleYou can unassign objects from instances within a business view on theAssignments page in the Veritas Operations Manager Enterprise Server console.

Note: If objects were previously assigned using rules, you can modify assignmentsor unassign objects by modifying or deleting rules.

See “Viewing, modifying, or deleting rules for assigning objects to a business view”on page 38.

To unassign objects from a business view


2 From theBusinessViews drop-down list, select the business view from whichyou want to unassign objects.

3 In the Instances pane, select the instance from which you want to unassignobjects.

4 On the Objects tab, select the objects you want to unassign. The objects arein the Objects Assigned to Instance_Name pane under the tab for the objecttype (such as Array or Host).

5 Click the Unassign link.

Object type namespaces and viewnames for businessview reports

You can include Veritas Operations Manager Enterprise Server business views inreports to show object data across your lines of business, geographic businessunits, or applications.

Use Cognos Query Studio to create ad hoc reports for business view information,or use Report Studio to create advanced reports.

See Veritas Operations Manager Enterprise Server User's Guide.

When you create business views, Enterprise Server updates Query Studio andReport Studio with the hierarchies and levels from your business views. Whenyou launch Query Studio or Report Studio, to see the information from yourbusiness views, expand the Cognos namespaces and view names.

Configuring business viewsObject type namespaces and view names for business view reports

42

Table 3-1 lists some examples of Cognos namespaces and view names (by object)that contain information from the business views you create. For a complete listof object types, see the namespaces in Query Studio and Report Studio.

Table 3-1 Example object types and their associated namespace and viewname

View nameCognos namespaceSupported object type

Array Analysis ViewsArray AnalysisArray

Storage Allocation Views

Chargeback Analysis ViewsChargeback AnalysisArray

Tiered Storage AnalysisViews

Tiered Storage AnalysisArray

File System Analysis ViewsFile System AnalysisFile System

Chargeback Analysis ViewsChargeback AnalysisFile System

Database Analysis ViewsDatabase AnalysisHost

File System Analysis ViewsFile System Analysis

Host Consumption ViewsHost ConsumptionHost

Storage Allocation ViewsStorage Allocation

Volume Analysis ViewsVolume AnalysisHost

Chargeback Analysis ViewsChargeback AnalysisHost

Chargeback Analysis ViewsChargeback AnalysisVolume

Volume Analysis ViewsVolume AnalysisVolume

Transferring business view objects betweenEnterprise Servers

You can use the Veritas Operations Manager Enterprise Server console to createa zip file containing CSV files for objects that are unassigned. One CSV file iscreated for each type of object for which there are unassigned objects. You canthen transfer these files to another Enterprise Server and import them for use ina business view on that server.

43Configuring business viewsTransferring business view objects between Enterprise Servers

To export and import a complete business view, you can use the command lineinterface.

See “Creating and managing business views using the command line interface”on page 101.

The procedure covers how to export and import the unassigned object files usingthe Veritas Operations Manager Enterprise Server console.

To transfer business view objects between Enterprise Servers

1 In the Veritas Operations Manager Enterprise Server console for theEnterprise Server that contains the business views, click Manage>BusinessViews > Hierarchies.

2 In the table, select the business view.

3 Click the Get unassigned objects for a business view icon above the table.

Veritas Operations Manager Enterprise Server creates a zip file containinga CSV file for each unassigned object type. You are prompted to open or savethe zip file.

4 Review the CSV files that contain the exported object data.

If Veritas Operations Manager Enterprise Servercannot determine the levelto which an object belongs, it labels the object as "generic object" in the CSVfile . If this labeling happens, manually edit the CSV files to add a level namefor objects at this level.

5 Transfer the exported files to the Veritas Operations Manager EnterpriseServer host that you want to import the objects into.

6 In the Veritas Operations Manager Enterprise Server console for theEnterprise Server where you are importing the objects, on the BusinessViewHierarchies page, select the business view and click the Assign objects toBusiness View icon above the table.

7 In the ImportBusinessView dialog box, browse to the CSV file for each objecttype.

8 Click Submit.

Configuring business viewsTransferring business view objects between Enterprise Servers

44

Configuring storage tiers


■ About storage tiers

■ Adding storage tiers

■ Modifying storage tiers

■ Managing storage tier rules

■ Adjusting storage tier rankings

■ Deleting storage tiers

■ Storage tiers options

About storage tiersSome data is mission-critical and must be stored so that you can quickly retrieveand update it. Because the data is essential to your business, it must be secure aswell. Many organizations respond to these business needs by establishing storagetiers. Storage tiers are often organized to provide varying degrees of availabilityand performance.

With Veritas Operations Manager Enterprise Server, you can create storage tiersthat mirror how your business categorizes storage. In the Enterprise Serverconsole, you create rules and adjust tier rankings to manage the assignment ofstorage to specific tiers. You can view and create reports about your network’sstorage tiers.

Veritas Operations Manager Enterprise Server includes the following sample tiers.

Storage that is fault tolerant, is highly available, and achieves a highperformance rating. Best for mission critical applications.

Tier 1

4Chapter

Storage that is fault tolerant, has medium availability, and operatesat a medium performance rating.

Tier 2

Storage that is not fault tolerant and operates at a mediumperformance rating.

Tier 3

Storage that is unprotected.Tier 4

You can use these sample tiers or modify them so that they align better with yourbusiness needs.

Adding storage tiersYou can use the sample storage tiers provided with Veritas Operations ManagerEnterprise Server or you can add your own.

To add a storage tier

1 In the Veritas Operations Manager Enterprise Server console, click Manage> Storage Tiers.

2 Click the Add Tier icon.

See “Storage tiers options” on page 74.

3 In the Description panel, enter the required information and click SaveChanges.

See “Storage tiers dialog options” on page 46.

4 To confirm creating a storage tier without a rule, click OK.

The new storage tier appears in the Storage Tiers table.

5 (Optional) Create a rule for the storage tier and define the tier as the defaultstorage tier.

See “Managing storage tier rules” on page 47.

Storage tiers dialog optionsUse the StorageTiers pane to define a new storage tier or modify a current storagetier.

Configuring storage tiersAdding storage tiers

46

Table 4-1 Options

DescriptionField

Enter a name for the storage tier; for example, Tier 1 or Gold.

The name of the storage tier displays in the Storage Tiers tableand reports.

Storage tier name

Enter a description for the storage tier.

The description of the storage tier displays in the Storage Tierstable and reports.

Description

Enter the cost per gigabyte associated with the tier.

Note: The costs default to the value that you set for WINDOWSserver. Reports show data in that currency.

Cost

Modifying storage tiersAfter you create a storage tier, you may need to modify its information. Forexample, you might want to change its description or its cost.

To modify a storage tier


2 In the Storage Tiers table, select the storage tier that you want to modify.

3 In the Description panel, make one or more modifications and click SaveChanges.

See “Storage tiers dialog options” on page 46.

The modifications to the storage tier appear in the Storage Tiers table.

4 (Optional) Create or modify a rule for the storage tier and define the tier asthe default storage tier.


Managing storage tier rulesVeritas Operations Manager Enterprise Server storage tier rules determine howstorage is assigned to specific storage tiers. You can create rules for each of yourstorage tiers using one of the following:

47Configuring storage tiersModifying storage tiers

■ The Basic Rule Builder, which uses forms to guide you through the process ofconstructing a rule with the proper syntax.See “Using the Basic Rule Builder to create and modify rules” on page 61.

■ The Advanced Rule Builder, which lets you type the complete rule, but requiresyou to form the correct syntax yourself.See “Using the Advanced Rule Builder to create and modify rules” on page 69.

About storage tier rulesYou can create rules for each of your storage tiers to govern the assignment ofstorage to specific storage tiers. During data rollup, Veritas Operations ManagerEnterprise Server evaluates storage tier rules against each LUN that rolls up. Theprocess of evaluating storage tier rules against each LUN is as follows:

■ Veritas Operations Manager Enterprise Server evaluates the rule of the storagetier with the highest ranking first (rank 1).See “Adjusting storage tier rankings” on page 73.

■ If a rule evaluates to true, Veritas Operations Manager Enterprise Serverassigns the LUN to that storage tier.

■ If a rule does not evaluate to true, then Veritas Operations Manager EnterpriseServer checks the storage tier of the next highest ranking.

■ If there are no rules that evaluate to true for a LUN, then Veritas OperationsManager Enterprise Server assigns the LUN to the default storage tier.

■ Some attributes that are available for tier creation allow null values. Null is aspecial value that indicates that the information is otherwise unknown orunavailable. When you use an attribute that allows a null value in a rule, donot create a rule that evaluates to unknown. When you use comparisonoperators other than is null or is not null, a null value causes unknownresults.For example, if the attribute [Array].[Vendor] is null, the rules[Array].[Vendor] = 'HITACHI' and [Array].[Vendor] <> 'HITACHI'

evaluate to unknown. If you want to assign LUNs to a tier when the attributevalue is null, use the is null or is not null operators. For example, the rule[Array].[Vendor] <> 'HITACHI' OR [Array].[Vendor] IS NULL evaluatesto true for LUNs of an array vendor that is not Hitachi or is null.See “About storage tier rule syntax” on page 49.See “Storage tier rule attributes” on page 51.

For example, you may have three storage tiers and each has a rule. The tiers aredefined as follows:

Configuring storage tiersManaging storage tier rules

48

Has a rank of 1, its rule is for all EMC arrays, and it is the default tierTier A

Has a rank of 2 and its rule is for all Hitachi arrays.Tier B

Has a rank of 3 and its rule is for all IBM arrays.Tier C

When a LUN rolls up and its array vendor is IBM, Veritas Operations ManagerEnterprise Server evaluates that LUN against the highest ranking storage tierfirst, which, in this case is Tier A. The rule for Tier A evaluates to false, so VeritasOperations Manager Enterprise Server checks the storage tier of the next highestranking. The tier of the next highest ranking is Tier B, which also evaluates tofalse. Veritas Operations Manager Enterprise Server checks the final tier, Tier C,which evaluates to true. Veritas Operations Manager Enterprise Server assignsthe LUN to Tier C.

About storage tier rule syntaxWhen you create Veritas Operations Manager Enterprise Server rules for storagetiers, you need to use valid syntax. Otherwise, the rule builders do not save therule. In the Basic Rule Builder, you only need to type values using a valid syntax.In the Advanced Rule Builder, you type the complete rule yourself, which requiresan understanding of rule syntax.

Storage tier rules consist of one or more conditions. A condition consists of thefollowing:

■ A LUN or array attributeSee “Storage tier rule attributes” on page 51.

■ A value

The syntax of a condition must be in the following format: [Object].[Attribute]operator value

For example: [Array].[Vendor] = 'EMC'

You can combine multiple conditions using the AND or OR operators. For example:[Array].[Vendor] = 'EMC' AND [Array].[Model] = 'Cx700'

The following table describes common operators and functions.

49Configuring storage tiersManaging storage tier rules

Table 4-2 Commonly used operators and functions

SyntaxDescriptionOperators andfunctions

[Object].[Attribute] = 'value'Use to match an object’s attribute with avalue. If the attribute equals the value,the rule is true.

=

[Object].[Attribute] = 'value'AND [Object].[Attribute] ='value'

When using more than one condition, useto return a value of true only if allconditions are met.

AND

[Object].[Attribute] = 'value'OR [Object].[Attribute] ='value'

When using more than one condition, useto return a value of true if one or moreconditions are met.

OR

[Object].[Attribute] LIKE'value%'

Use to match an object’s attribute with avalue by pattern matching with wildcards.An underscore (_) matches one characterin the value and a percent (%) matcheszero or more characters.

LIKE

[Object].[Attribute] IN('value1', 'value2')

Use to match an object’s attribute with alist of values.

IN

[Object].[Attribute] NOT IN('value')

Use to match an object’s attribute withall values that do not match the given listof values.

NOT IN

[Object].[Attribute] < valueUse to match an object’s attribute with avalue that is less than the defined value.

<

[Object].[Attribute] > valueUse to match an object’s attribute with avalue that is greater than the definedvalue.

>

[Object].[Attribute] ISNULL

Use to match an object’s attribute with avalue that is null.

IS NULL

[Object].[Attribute] IS NOTNULL

Use to match an object’s attribute with avalue that is not null.

IS NOT NULL

lower([Object].[Attribute])operator 'value'

Use to match an object’s attribute with avalue that contains mixed characters.This function is only available when youuse the Advanced Rule Builder.

lower( )


50

When you use comparison operators, you assign a value to an attribute. Forexample, if you type the rule [Array].[Vendor] = 'EMC' you assign EMC as thevalue for the attribute (the array vendor). You must type values in a specific format.

Note: To find the exact value of an attribute, see your data source.

Table 4-3 Format for values

FormatValue type

'value'String

valueNumeric

Storage tier rule attributesThe following tables describe the array and LUN attributes that you can choosefrom when defining storage tier rules.

Table 4-4 Array attributes

Attribute syntaxDescriptionDisplay name

[ARRAY].[ARRAY OBJECTIDENTIFIER]

Unique identifier for thisobject in the VeritasOperations Managerdatabase.

Array Object Identifier

[ARRAY].[DISPLAY NAME]Array display name.Display Name

[ARRAY].[VENDOR]The array vendor name. Thismay be null.

Vendor

[ARRAY].[FAMILY]Indicates the storage arrayfamily. Values include:

Symmetrix (Symm and DMX)

CLARiiON

Thunder Series

Lightning Series

Enterprise Virtual Array

Enterprise Storage Server

IBM DS Array

Family


Table 4-4 Array attributes (continued)


[ARRAY].[TYPE]Array type. This can be:

Filer

Enclosure

Unenclosed Device

Type

[ARRAY].[FIRMWAREVERSION]

The array firmware ormicrocode version. This maybe null.

Firmware Version

[ARRAY].[MODEL]The array vendor model. Thismay be null.

Model

[ARRAY].[SERIAL NUMBER]The array serial numberassigned by the vendor. Thismay be null.

Serial Number

[ARRAY].[SNMP IPADDRESS(ES)]

One or more IP addresses ofthe SNMP agent providingarray information. Multipleaddresses are stored as acomma separated list. Thismay be null.

SNMP IP Address(es)

[ARRAY].[IS AUTODISCOVERED]

A boolean flag that indicatesif the array has beendiscovered by VeritasOperations Manager agents.Possible values:

'T' - the array has beendiscovered

'F' - the array has not beendiscovered

Is Auto Discovered


52



[ARRAY].[IS VIRTUALIZER]A boolean flag that indicatesif the array is a virtualizer.Virtualizer arrays presentexternal disks as LUNs tohosts. HDS Tagma and USParrays are examples ofvirtualizers. Possible values:

'T' - the array is a virtualizer

'F '- the array is not avirtualizer

Is Virtualizer

[ARRAY].[VOM DISCOVERTYPE]

Veritas Operations Managerdiscover type.

VOM Discover type

[ARRAY].[APPLICATIONBUSINESS ENTITY]

Application business entityto which this array belongs.This may be null.

Application Business Entity

[ARRAY].[COMPOSITEAPPLICATION BUSINESSENTITY]

Composite organizationbusiness entity to which thisarray belongs. This may benull.

Composite ApplicationBusiness Entity

[ARRAY].[ORGANIZATIONBUSINESS ENTITY]

Organization business entityto which this array belongs.This may be null.

Organization Business Entity

[ARRAY].[COMPOSITEORGANIZATION BUSINESSENTITY]

Composite organizationbusiness entity to which thisarray belongs. This may benull.

Composite OrganizationBusiness Entity

[ARRAY].[SUB TYPE]Sub-type of array. Example:PFiler, Vfiler, PDM, VDM etc.

Sub Type

[ARRAY].[IP ADDRESSES]IP addresses.IP Addresses

[ARRAY].[CLUSTER ARRAYNAME]

Cluster array name.Cluster Array Name




[ARRAY].[CLUSTER ARRAYOBJECT IDENTIFIER]

The unique identifier of thehost pfiler array in VeritasOperations Managerfor aNetApp vfiler. This will benull for all other arrays andNetApp filers.

Cluster Array ObjectIdentifier

[ARRAY].[FILER TYPE]Type of Filer: Physical Filer,Virtual Filer, PDM, VDM

Filer Type

Table 4-5 LUN attributes


[LUN].[LUN OBJECTIDENTIFIER]

Unique identifier for thisobject in Veritas OperationsManager database.

LUN Object Identifier

[LUN].[DISPLAY NAME]LUN display name.Display Name

[LUN].[ADVISORY DISPLAYNAME]

The array name discoveredby Veritas OperationsManager. This may be null.

Advisory Display Name


54

Table 4-5 LUN attributes (continued)


[LUN].[RAID LEVEL]The RAID level of the LUN.Possible values:

- RAID0

- RAID1

- RAID3

- RAID4

- RAID4

- RAID5

- RAID6

- RAID7

- RAID10

- RAID0+1

- RAID053

- Unknown.

This may be null.

RAID Level

[LUN].[MASKING STATUS]Indicates whether the virtualdisk is masked, unmasked orcannot be masked. This maybe null.

Masking Status

[LUN].[CLAIMED STATUS]Unknown, unclaimed,claimed.

Claimed Status

[LUN].[RESOURCE TYPE]Indicates the resource typeof the addressable unit. Validstates include: Data Device,System Device, Virtual Copy,and Spare.

Resource Type

[LUN].[SERIAL NUMBER]Vendor assigned serialnumber This may be null.

Serial Number




[LUN].[VENDOR NAME]The name of the companythat manufactured thephysical device. In the caseof a virtual object, such as avolume, this is the name ofthe company thatmanufactured the physicaldevice upon which thevolume resides. This may benull.

Vendor Name

[LUN].[COLUMNS]Number of data columnsused for striping. A value of1 indicates striping is notused. This may be null.

Columns

[LUN].[IS PRIMARY]A boolean flag that indicatesthat this is a primary virtualdisk from which snapshotscan be made. This is onlyapplicable to arrays that useprimary/secondary model.Possible values:

'T' - the LUN is a primaryvirtual disk

'F' - the LUN is not a primaryvirtual disk

Is Primary

[LUN].[IS SECONDARY]A boolean flag that indicatesthat this is a secondaryvirtual disk. This is onlyapplicable to arrays that usethe primary/secondarymodel. Possible values:

'T' - the LUN is a secondaryvirtual disk

'F' - the LUN is not asecondary virtual disk

Is Secondary


56



[LUN].[IS SEGMENT]A boolean flag that indicatesthat the virtual disk is asegment of a larger virtualdisk. Possible values:

'T' - the LUN is a segment ofa larger virtual disk

'F' - the LUN is not a segmentof a larger virtual disk

Is Segment

[LUN].[IS AGGREGATE]A boolean flag that indicatesthat the virtual disk is acombination of other virtualdisks. A virtual disk can beboth a segment and anaggregate if the virtual diskis in a middle layer with anaggregate virtual disk aboveand the segment virtual disksbelow. In such a case, bothsegment and aggregate aretrue. Possible values:

'T' - the LUN is an aggregate

'F' - the LUN is not anaggregate

Is Aggregate

[LUN].[IS CONTROL DEVICE]A boolean flag that indicatesif the device is used only forsending control commandsto the array. This tellsapplications to ignore thedevice. Possible values:

'T' - the LUN is a controldevice

'F' - the LUN is not a controldevice

Is Control Device




[LUN].[IS FAULTTOLERANT]

A boolean flag that indicateswhether the virtual disklayout is fault tolerant.Possible values:

'T' - the LUN is fault tolerant

'F' - the LUN is not faulttolerant

Is Fault Tolerant

[LUN].[IS ADMINISTRATIVE]A boolean flag that indicatesa LUN set aside for a BCV,shadow image, controldevice, and otheradministrative tasks.Possible values:

'T' - the LUN isadministrative

'F' - the LUN is notadministrative

Is Administrative

[LUN].[IS USED INSNAPSHOT]

A boolean flag that indicatesthat the LUN is secondaryand used in a snapshot.Possible values:

'T'- the LUN is secondary andis used in a snapshot

'F' - the LUN is not secondaryand/or is not used in asnapshot

Is Used In Snapshot

[LUN].[IS VIRTUALIZERSOURCE]

A boolean flag that indicatesthat a LUN is a virtualizersource. A virtualizer sourceis allocated to a virtualizerarray such as Tagma or IBMSAN Volume Controller(SVC). Possible values:

'T'- the LUN is a virtualizersource

'F' - the LUN is not avirtualizer source

Is Virtualizer Source


58



[LUN].[IS DIRECTATTACHED]

A boolean flag that indicatesif the device is directattached. Possible values:

'T'- the LUN is directattached

'F' - the LUN is not directattached

Is Direct Attached

[LUN].[IS BASEDONEXTERNAL]

A boolean flag that indicatesif the device is based onexternal. Possible values:

'T'- the LUN is based onexternal

'F' - the LUN is not based onexternal

Is Basedon External

[LUN].[ARRAY PORTS]The number of array portsthe device is connected to.

Array Ports

[LUN].[DISK VENDOR]The name of the companythat manufactured thephysical disk from which thisLUN is made. This may benull.

Disk Vendor

[LUN].[DISK CAPACITY]Total capacity of the physicaldisk from which this LUN ismade.

Disk Capacity

[LUN].[VENDOR LAYOUT]Vendor name for the storagelayout used by this device.This may be null.

Vendor Layout

[LUN].[THIN STATUS]Thin provisioning specificstate of the LUN.

This attribute tells whetherthe object is thin or thin poolsource. For non-thin LUNsthis attribute is notapplicable. This may be null.

Thin Status




[LUN].[VOM DISCOVERTYPE]

VOM Discover type

[LUN].[IS ASSIGNED]A boolean flag that indicatesthat the virtual disk isassigned. Possible values:

'T' - the LUN is assigned

'F' - the LUN is not assigned

Is Assigned

[LUN].[IS EXPORTED]A boolean flag that indicatesif the device is exported.Possible values:

'T' - the device is exported

'F' - the device is notexported

Is Exported

[LUN].[APPLICATIONBUSINESS ENTITY]

Application business entityto which this object belongs.This may be null.

Application Business Entity

[LUN].[COMPOSITEAPPLICATION BUSINESSENTITY]

Composite applicationbusiness entity to which thisobject belongs. This may benull.

Composite ApplicationBusiness Entity

[LUN].[ORGANIZATIONBUSINESS ENTITY]

Organization business entityto which this object belongs.This may be null.

Organization Business Entity

[LUN].[COMPOSITEORGANIZATION BUSINESSENTITY]

Composite organizationbusiness entity to which thisobject belongs. This may benull.

Composite OrganizationBusiness Entity

[LUN].[TYPE]This attribute differentiatesbetween VMDK and Disk.

Type

[LUN].[SUB TYPE]For VMDK, this differentiatesbetween RDM, Sparse andFlat VMDKs.

Sub Type


60



[LUN].[STORAGETECHNOLOGY]

This attribute represents thestorage technology used.Possible values are SAN, DASand NAS.

Storage Technology

[LUN].[STORAGE POOLNAME]

This attribute represents thename of the data storeassociated to a VMwareVMDK

Storage Pool Name

[LUN].[STORAGE POOLNAME]

This attribute represents thename of the data storeassociated to a VMwareVMDK

Storage Pool Name


Using the Basic Rule Builder to create and modify rulesYou can use the Basic Rule Builder to create or modify rules for storage tiers. TheBasic Rule Builder guides you through the process of creating a rule. You do nothave to type the entire rule syntax. For example, you use icons to add, delete, andgroup conditions and drop-down lists to select attributes and operators.

You can view examples of how to use the Basic Rule Builder.

See “Using Basic Rule Builder examples” on page 64.

You can also use the Advanced Rule Builder to create and modify rules.

See “Using the Advanced Rule Builder to create and modify rules” on page 69.

Review details about the icons and fields that you can use with storage tiers andwith the Basic Rule Builder.


See “Basic Rule Builder dialog options” on page 62.

To create or modify a rule using the Basic Rule Builder


2 In the Storage Tiers table, select the storage tier for which you want to createor modify a rule.


3 In the Rule panel, click the Edit Rule icon.

If the Advanced Rule Builder displays, you cannot use the Basic Rule Builderto modify a rule for this storage tier.

See “Using the Advanced Rule Builder to create and modify rules” on page 69.

4 In the Basic Rule Builder, enter the required information and click OK.

5 (Optional) In the Rule panel, check Set asdefault to designate the tier as thedefault storage tier.

During data rollup, Veritas Operations Manager Enterprise Server assignsLUNs to storage tiers based on rules. If there are no rules that evaluate totrue for a LUN, then Veritas Operations Manager Enterprise Server assignsthe LUN to the default storage tier.


The rule applies to the next data rollup.

Basic Rule Builder dialog optionsUse the Basic Rule Builder dialog to add or modify rules for storage tiers.

Table 4-6 shows the options that are available in the Basic Rule Builder dialog.

Table 4-6 Basic Rule Builder Options


Click to add a new condition to the rule.Add Condition

If you added conditions or groupedconditions, click to undo the adding orgrouping of conditions.

You can undo up to the last saved operation.

Undo

Click to validate the rule syntax.Validate Rule

Click to open help for the Basic Rule Builder.Open Rule Help

Click to switch to the Advanced Rule Builder.

After you save a rule that you define in theAdvanced Rule Builder, you cannot edit therule in the Basic Rule Builder.

Switch to AdvancedMode

Click to view or hide a panel that displaysthe syntax for your rule.

View or Hide Rule Text


62

Table 4-6 Basic Rule Builder Options (continued)


Click to ungroup the selected conditions.Ungroup fromFollowing Condition

Click to group the selected condition withthe condition that precedes it.

Grouping conditions is useful when you havethree or more conditions. When you groupconditions, you nest the conditions together.Nesting makes sure that all conditions thatare part of the group must evaluate to truefor the group to evaluate to true. If you havethree conditions, you can group two of theconditions to create a rule in the format (xor (y and z)). Both y and z must evaluate totrue.

Group with PrecedingCondition

Click to group the selected condition withthe condition that follows it.

Grouping conditions is useful when you havethree or more conditions. When you groupconditions, you nest the conditions together.Nesting makes sure that all conditions thatare part of the group must evaluate to truefor the group to evaluate to true. If you havethree conditions, you can group two of theconditions to create a rule in the format (xor (y and z)). Both y and z must evaluate totrue.

Group with FollowingCondition

Click to delete the selected condition.Delete Condition

Click to display a panel that describes theselected attribute.

Show Description

Select an object’s attribute.N/AObject attributedrop-down list

Select an operator.N/AOperator drop-down list


Table 4-6 Basic Rule Builder Options (continued)


Type a value.

You must type values in a specific format,depending on the type of value that you wantto use. The format for values is as follows:

■ Strings: 'value'

For example: 'EMC' or 'Cx700'

■ Numeric: value

For example: 500 or 8000

N/AText box

If you have more than one condition, selectthis option to return a value of true only ifall conditions are met.

N/AAND

If you have more than one condition, selectthis option to return a value of true if one ormore conditions are met.

When you add a new condition, OR isselected by default.

N/AOR

Click to move a condition up.

Moving conditions is useful when you wantto group conditions. For example, if you havethree conditions and want to group the firstand last conditions together, you can movethe last condition up.

Move Condition Up

Click to move a condition down.

Moving conditions is useful when you wantto group conditions. For example, if you havethree conditions and want to group the firstand last conditions together, you can movethe first condition down.

Move Condition Down

Using Basic Rule Builder examplesYou can use the Veritas Operations Manager Enterprise Server Basic Rule Builderin the Enterprise Server console to create rules for storage tiers. Use the proceduresin this section as examples of how you can use the Basic Rule Builder. With thefollowing procedures you can create rules to:

■ Assign EMC storage arrays to a storage tier.


64

■ Assign EMC Symmetrix VMAX storage arrays to a storage tier.

■ Assign EMC storage arrays that are models DMX800 and DMX4-6 and LUNsthat have RAID levels of RAID1, RAID0/1, or RAID1/0 to a storage tier.

Review details about the icons and fields that you can use with storage tiers andwith the Basic Rule Builder.


See “Basic Rule Builder dialog options” on page 62.

To create a rule to assign EMC storage arrays to a storage tier


2 In the Storage Tiers table, select the storage tier for which you want to createa rule.


4 In the Basic Rule Builder, in Condition 1, do the following:

■ In the object attribute drop-down list, click Array.Vendor.

■ In the text box, type 'EMC'.Condition 1 displays as follows:

5 Click OK.

To create a rule to assign EMC Symmetrix VMAX storage arrays to a storage tier






■ In the text box, type 'EMC'.


5 Click the Add Condition icon.

6 In Condition 2, do the following:

■ In the object attribute drop-down list, click Array.Family

■ In the text box, type 'Symmetrix'

7 Between condition 1 and condition 2, click AND.

8 Click the Add Condition icon.

9 In Condition 3, do the following:

■ In the object attribute drop-down list, click Array.Model

■ In the operator drop-down list, select like.

■ In the text box, type '%VMAX' .

10 Between condition 2 and condition 3, click AND.

Conditions 1, 2, and 3 display as follows:

11 Click OK.


66

To create a rule to assign EMC storage arrays that aremodels DMX800 andDMX4-6and LUNs that have RAID levels of RAID1, RAID0/1, or RAID1/0 to a storage tier





■ In the object attribute drop-down list, click Array.Model.


■ In the text box, type '%DMX800'.

5 Click the Add Condition icon and in Condition 2, do the following:

■ Click the Group with Preceding Condition icon.

■ In the object attribute drop-down list, click Array.Model.


■ In the text box, type '%DMX4-6'.



■ In the text box, type 'EMC'.


7 Between Condition 2 and Condition 3, click AND.



■ In the object attribute drop-down list, click LUN.RAID Level.

■ In the text box, type 'RAID1'.




■ In the text box, type 'RAID0/1'.




■ In the text box, type 'RAID1/0'.


68


11 Click OK.

Using the Advanced Rule Builder to create and modify rulesYou can use the Advanced Rule Builder in the Veritas Operations ManagerEnterprise Server console to create or modify rules for storage tiers. In theAdvanced Rule Builder, you must type a rule using valid rule syntax.

See “About storage tier rule syntax” on page 49.

After you save a rule using the Advanced Rule Builder, you cannot edit the ruleusing the Basic Rule Builder.

See “Using the Basic Rule Builder to create and modify rules” on page 61.

Review details about the icons that you can use with storage tiers.



To create a rule using the Advanced Rule Builder




4 In the Basic Rule Builder, click the Switch to Advanced Mode icon.

5 In the Advanced Rule Builder, do the following to add a condition:

■ Expand the Array and LUN trees to display attributes for each object.

■ In the Array or LUN tree, select an attribute and click Insert.

■ In the rule text box, type an operator and a value using valid syntax.See “About storage tier rule syntax” on page 49.

6 (Optional) To add more conditions to the rule, repeat step 5.

7 Click OK.

8 (Optional) In the Rule panel, check Set asdefault to designate the tier as thedefault storage tier.

During data rollup, Veritas Operations Manager Enterprise Server assignsLUNs to storage tiers based on rules. If there are no rules that evaluate totrue for a LUN, then Veritas Operations Manager Enterprise Server assignsthe LUN to the default storage tier.



To modify a rule using the Advanced Rule Builder


2 In the Storage Tiers table, select the storage tier for which you want to modifya rule.


4 In the Advanced Rule Builder, do one or more of the following:

■ To display attributes for each object, expand the Array and LUN trees.

■ In the Array or LUN tree, select an attribute and click Insert.

■ In the rule text box, retype the rule using valid syntax.See “About storage tier rule syntax” on page 49.


70

5 Click OK.

6 (Optional) To designate the tier as the default storage tier, in the Rule panel,check Set as default.

During data rollup, Veritas Operations Manager Enterprise Server assignsobjects to storage tiers based on rules. Veritas Operations Manager EnterpriseServer designates unassigned objects to the default tier.



Using Advanced Rule Builder examplesYou can use the Veritas Operations Manager Enterprise Server Advanced RuleBuilder to create rules for storage tiers. You must create rules using valid rulesyntax.

Table 4-7 describes common scenarios and provides examples of rule syntax.

Table 4-7 Storage tier rule scenarios and examples

Rule exampleScenario

To assign EMC arrays, use the following rule:

[Array].[Vendor] = 'EMC'

You want to assign LUNs from aspecific array vendor.

To assign EMC, Hitachi, and HDS storage arrays,use the following rule:

[Array].[Vendor] in ('EMC', 'Hitachi',

'HDS')

You want to assign LUNs frommultiple array vendors.

To assign storage arrays that match the vendornames EMC, EMC Corp, and EMC Corporation, usethe following rule:

[Array].[Vendor] LIKE 'EMC%'

You want to assign LUNs from anarray vendor whose name may vary.

To assign storage arrays that match the vendorname Hitachi or hitachi, use the following rule:

lower([Array]).[Vendor]) = 'hitachi'

You want to assign LUNs from anarray vendor whose name may varybetween upper and lowercase.

To assign CX300, CX400, and CX500 EMC storagearrays, use the following rule:


AND [Array].[Model] LIKE 'CX%'

You want to assign LUNs from anarray vendor and array model.


Table 4-7 Storage tier rule scenarios and examples (continued)

Rule exampleScenario

To assign CX300, CX400, and CX500 EMC storagearrays with specific firmware versions, use thefollowing rule:


AND [Array].[Model] LIKE 'CX%'

AND [Array].[Firmware Version] IN

('2.19.400.5.007', '2.16.500.5.010')

You want to assign LUNs from anarray vendor and array model withspecific firmware versions.

To assign virtualized Hitachi storage arrays, usethe following rule:

[Array].[Vendor] = 'HITACHI'

AND [Array].[Is Virtualizer] = 'T'

You want to assign virtualized arrays.

To assign RAID1 Hitachi storage arrays, use thefollowing rule:

[Array].[Vendor] = 'HITACHI'

AND [LUN].[RAID Level] = 'RAID1'

You want to assign LUNs from anarray vendor with a specific RAIDlevel.

To assign RAID5 and RAID10 EMC storage arrays,use the following rule:


AND [LUN].[RAID Level] IN ('RAID5',

'RAID10')

You want to assign LUNs from anarray vendor with multiple RAIDlevels.

To assign EMC storage arrays that are not controldevices, use the following rule:


AND [LUN].[Is Control Device] = 'F'

You want to assign LUNs from anarray vendor that are not controldevices.

To assign non-Hitachi and non- IBM storage arraysthat have a resource type of data and have two ormore mirror copies, use the following rule:

[Array].[Vendor] NOT IN ('HITACHI',

'IBM')

AND [LUN].[Resource Type] = 'Data'

AND [LUN].[Number of Copies] > 2

You want to assign LUNs that are notfrom a specific array vendor, have aresource type of data, and havemirror copies.


72

Adjusting storage tier rankingsStorage tier rankings work with storage tier rules to assign storage to specifictiers. When two or more storage tiers have some rules that evaluate to true for aLUN, Veritas Operations Manager Enterprise Server assigns the LUN to thelowest-ranked tier. For example, Tier X and Tier Y have some rules that evaluateto true for an EMC storage array. If Tier X has a rank of 1 and Tier Y has a rankof 2, Veritas Operations Manager Enterprise Server assigns the array to Tier X.

To adjust storage tier rankings


2 In the Storage Tiers table, select the storage tier for which you want to adjustthe ranking.

3 To adjust the rank, select one of the following icons:

■ Promote tier to a higher rank

■ Demote tier to a lower rank


The change in rank appears in the Storage Tiers table. The new rankingsapply to the next data rollup.

Deleting storage tiersYou can delete storage tiers that you no longer need.

Note: If you delete the default storage tier, Veritas Operations Manager EnterpriseServer assigns the tier with the highest ranking as the default tier.

To delete a storage tier


2 In the Storage Tiers table, select the storage tier that you want to delete.

3 Click the Delete Tier icon.


4 Click OK to confirm deletion.

The storage tier no longer appears in the Storage Tiers table.

73Configuring storage tiersAdjusting storage tier rankings

Storage tiers optionsTable 4-8 describes the options for managing storage tiers.

Table 4-8 Storage tiers options


Loads the storage tiers dialog box which youcan use to create a new storage tier.

Add Tier

Deletes the selected storage tier.Delete Tier

Moves the selected storage tier to a higher rank.Promote tier to ahigher rank

Moves the selected storage tier to a lower rank.Demote tier to alower rank

Loads the Basic Rule Builder or, if youpreviously saved the rule with the AdvancedRule Builder, loads the Advanced Rule Builder.

Edit Rule

Configuring storage tiersStorage tiers options

74

Managing licenses


■ Viewing the Veritas Operations Manager Advanced license entitlement reports

■ About the Storage Array Capacity License Entitlement Report

■ About the Host Count and NAS Capacity License Entitlement Report

■ About Veritas Operations Manager license deployment management

Viewing the Veritas Operations Manager Advancedlicense entitlement reports

Veritas Operations Manager Enterprise Server provides license entitlement reportsthat show information on the required licenses for Veritas Operations ManagerAdvanced.

Symantec determines Veritas Operations Manager Advanced licensing chargesbased on the following factors:

■ The number of managed hosts that are not running the Enterprise version ofStorage Foundation (or related Symantec storage and server managementproducts)

■ The array storage capacity

To view a Veritas Operations Manager Advanced license entitlement report

◆ In the Veritas Operations Manager Enterprise Server console, select Settings> License Entitlement and choose one of the reports listed.

The following reports are provided.

5Chapter

Shows information about the following:

■ The physical array capacity managed by theVeritas Operations Manager Enterprise Server

■ The amount of logical storage used bymanaged hosts with the Storage FoundationEnterprise edition software

■ The storage subject to licensing, calculated bysubtracting the logical storage of the abovehosts from the total physical capacity

Storage Array Capacity LicenseReport

Shows information about the following:

■ The number of managed hosts that requireVeritas Operations Manager Advanced licenses

■ The NAS physical capacity that is subject toVeritas Operations Manager Advancedlicensing requirements

Host Count and NAS CapacityLicense Report

About theStorageArrayCapacity LicenseEntitlementReport

The Storage Array Capacity License Entitlement Report shows the physical arraycapacity (in terabytes) managed by the Veritas Operations Manager EnterpriseServer and calculates the amount subject to Veritas Operations Manager Advancedlicensing charges.

The top of the report shows the following information:

■ Number of arrays

■ Physical capacity

■ Number of managed hosts covered by an Enterprise license

■ Logical capacity allocated to such managed hosts

■ The storage capacity that is subject to licensing, calculated by subtracting thelogical capacity from the physical capacity

The rest of the report shows details on the hosts and arrays.

Managing licensesAbout the Storage Array Capacity License Entitlement Report

76

About the Host Count and NAS Capacity LicenseEntitlement Report

The Host Count and NAS Capacity License Entitlement Report shows the numberof managed hosts requiring licensing for Veritas Operations Manager Advanced.Licenses are required for managed hosts that do not run the Enterprise editionof Storage Foundation.

The report also shows any NAS array physical capacity managed by the EnterpriseServer. NAS array physical capacity is also subject to licensing.

The summary section at the top of the report shows the following information:

■ The total number of hosts that report to the Veritas Operations ManagerEnterprise Server.

■ The total number of hosts that run Storage Foundation.

■ The number of hosts that run Storage Foundation Enterprise, out of the numberof hosts that run Storage Foundation.

■ The number of hosts that require the Veritas Operations Manager Advancedlicense, out of the total number of hosts. This number is equal to the numberof hosts that either:

■ Do not run Storage Foundation.

■ Run Storage Foundation Standard or Storage Foundation Basic.

In addition, the top of the report shows the number of NAS storage arrays andtheir physical capacity, in terabytes.

The rest of the report provides details about the managed hosts and the arrays.

In the Hosts section, you can filter the selection of hosts in the table based onwhether Storage Foundation is installed, and whether they need licenses. Thetable shows the following information:

The name of the host.Host Name

Operating system on which the host runs.Host Platform

Indicates if Storage Foundation is installed on thehost.

Has SF

The Storage Foundation edition (Standard, Basic,or Enterprise)

Edition

Indicates if the host is a virtualization server.Is Virtual

77Managing licensesAbout the Host Count and NAS Capacity License Entitlement Report

About Veritas Operations Manager licensedeployment management

Veritas Operations Manager provides licensing details for the Storage Foundationand related Symantec storage and server management and high availabilityproducts on the managed hosts. The Veritas Operations Manager licensedeployment summary identifies the types of licenses a host has (for example,keyless, expired, needs attention) and helps you avoid wasted licenses. Thedeployment summary also provides details on Symantec software editions.

The license deployment summary includes a product inventory for each host andtiering information for the SPVU, Server, Processor, NProcessors, and OS pricetiers.

For more information about Symantec licensing and price tiers, see the following:

See “About Symantec licensing and pricing” on page 78.

For a full description of license management in Veritas Operations ManagerManagement Server, see the Veritas Operations Manager Management ServerAdministrator's Guide.

About Symantec licensing and pricingThe storage and server management high availability products which operate onUNIX (Solaris, HP-UX, AIX), Linux and Windows must be certified to work onservers. The product certification differs from platform to platform. Certificationis how storage and server management high availability products are licensed byplatform. The price tier information is available on the Symantec OperationsReadiness Tools (SORT) Web site. You can configure Management Server to updatethe price tier information automatically according to a schedule, whenManagement Server is connected to the Internet. When Management Server isnot connected to the Internet, you can set up a proxy server to update the pricetier information automatically. You can download a script file from ManagementServer and run it on a Windows system that is connected to the Internet to extractthe text file that contains the price tier information. You can upload the text fileto Management Server to update the price tier information.

The following table describes the various types of Symantec price tiers:

Managing licensesAbout Veritas Operations Manager license deployment management

78

Table 5-1 Types of Symantec price tiers

DescriptionPlatformssupported

Tier Type

The Veritas storage and servermanagement, high availability products onUNIX are generally licensed and priced perserver. The pricing depends on the serverprice tier to which a server is assigned. Aserver can be assigned to 14 differentserver tiers from Tier A through Tier N.Customers must pay the per-server pricefor each server that runs storage and servermanagement, high availability products.This pricing meter applies to all versionsof Veritas storage and server management,high availability products on UNIX (Solaris,HP-UX, AIX).

The available price tiers for the server tierare A, B, C, D, E, F, G, H, I, J, K, L, M, N

UNIX: Solaris,HP-UX, and IBMAIX

Server Tier

The Veritas storage and servermanagement, high availability products onUNIX can be licensed and priced per tieredprocessor. The price depends on the tier towhich a processor is assigned. A processorcan be assigned to three different processortiers from Processor Tier 1 throughProcessor Tier 3. Customers must pay theper-tiered-processor price for everyprocessor that runs storage and servermanagement, high availability products.

The available price tiers for the processortier are Tier 1, Tier 2, and Tier 3.

All platformsProcessor Tier

Storage Foundation and high availability5.0 for Linux is licensed on a per-processorbasis regardless of the number of cores onthe processor. A multi-core chip with “n”cores counts as one processor. For example,each dual-core AMD Opteron processor thatruns Storage Foundation for Linux requiresone processor license.

The available price tiers for the NProcessortier are 1, 2, 3, 4, 5, 6, 7, 8 Processors.

Linux: Red Hat andNovell SUSE

NProcessor Tier

79Managing licensesAbout Veritas Operations Manager license deployment management

Table 5-1 Types of Symantec price tiers (continued)

DescriptionPlatformssupported

Tier Type

The Veritas storage and server automation,high availability products which operateon the Microsoft Windows operatingsystem are priced per server. The price alsodepends on the edition of Windows that isinstalled; for example, NT or 2000. TheStorage Foundation and high availabilityproducts on Windows do not follow aper-processor pricing meter.

The available price tiers for the operatingsystem tier are Level 1, Level 2, and Level3.

Microsoft WindowsOperation System Tier

The following are considered forcalculating SPVU for the Veritas storageand server management, high availabilityproducts on a host:

■ The operating system on the host

■ The make and the model of theprocessor

■ Number of cores per processor

All platformsSymantec PerformanceValue Unit (SPVU)

Managing licensesAbout Veritas Operations Manager license deployment management

80

Configuring authenticationand authorization


■ About authentication and authorization

■ Configuring authentication brokers

■ Configuring user authorization

About authentication and authorizationVeritas Operations Manager Enterprise Server authenticates a user's identity,and allows access to various product features based on the privileges you grantto that user's security group.

Veritas Operations Manager Enterprise Server supports LDAP and AD-basedauthentication. Veritas Operations Manager Enterprise Server also supports OSauthentication mechanisms, that include Pluggable Authentication Modules(PAM), Network Information Service (NIS), and NIS+, but not multi-factorauthentication mechanisms.

To set up authentication in Veritas Operations Manager Enterprise Server

◆ Configure Veritas Operations Manager Enterprise Server to discover yourauthentication domains.

See “Configuring authentication brokers” on page 82.

To set up authorization in Veritas Operations Manager Enterprise Server

◆ Define security groups to set the level of privileges for different types of usersin your authentication domains.

See “Configuring user authorization” on page 90.

6Chapter

Configuring authentication brokersVeritas Operations Manager Enterprise Server uses authentication brokers todiscover authentication domains, such as LDAP or AD domains. Veritas OperationsManager Enterprise Server uses the following types of authentication brokers:

■ A primary broker that gets installed on the Enterprise Server when you installand configure Veritas Operations Manager Enterprise Server.

■ The optional secondary brokers that you add after installing and configuringVeritas Operations Manager Enterprise Server. Secondary authenticationbrokers allow users in other domains to access your resources without yourhaving to associate those outside domains with the primary broker.

Note: On the Authentication Brokers page, you see your primary broker, anysecondary brokers you have configured, and the domains associated with thosebrokers. As administrators add and remove domains (either on the EnterpriseServer, or directly on the brokers), the domains list does not automatically refresh.To see the most current list of domains, click Refresh Broker.

You configure authentication on the primary broker by doing one of the following:

■ Configure the primary broker to discover your AD or LDAP domain.See “Configuring AD or LDAP authentication” on page 83.

■ Associate the primary broker with a domain for which a NIS or NIS+authentication mechanism is configured. You associate the primary brokerwith a domain by enabling the domain for that broker.See “Enabling and disabling domains” on page 89.

Note: The primary broker does not discover unixpwd domains at this time.

To configure a secondary broker, add the broker and enable a domain for whichan authentication mechanism (LDAP, AD, NIS, NIS+, or unixpwd) is configured.

See “Adding and removing secondary brokers” on page 82.

Adding and removing secondary brokersUsers with the Domain Admin role can use the Veritas Operations ManagerEnterprise Server console to add and remove secondary authentication brokerswithin the Veritas Operations Manager Enterprise Server domain.

Configuring authentication and authorizationConfiguring authentication brokers

82

To add a secondary authentication broker

1 Select Settings > Authentication Brokers.

2 In the Authentication Brokers area, click Add.

3 In the Add New Broker dialog box enter the fully-qualified host name or IPaddress of the authentication broker host that you want to add to the domain.

4 In the AddNewBroker dialog box enter the port number on which you wantto run the authentication broker. Then click OK.

5 Click OK again to exit the Result dialog box.

To remove a secondary authentication broker


2 In the Authentication Brokers area, select the broker you want to removeand click Remove Broker.

3 In the Remove Broker dialog box, click Yes.

4 Click OK to exit the Result dialog box.

Configuring AD or LDAP authenticationYou can use the Veritas Operations Manager Enterprise Server console to configureActive Directory (AD), or Lightweight Directory Access Protocol (LDAP)-basedauthentication on the primary authentication broker.

To configure AD or LDAP-based authentication


2 In Domains area, click Configure LDAP/AD.

3 In the LDAP/ADSettings-discoverattributesandconfigurationinformationwizard panel, enter the details and click Next.

4 In the LDAP/AD Settings - configure LDAP/AD wizard panel, specify thesearch base and click Finish.

5 Click OK to exit the Results panel.

LDAP/AD Settings - discover attributes and configurationinformation panel optionsUse the LDAP/ADSettings -discoverattributesandconfiguration informationpanel options panel to configure Lightweight Directory Access Protocol(LDAP)-based authentication on the primary authentication broker.

83Configuring authentication and authorizationConfiguring authentication brokers

Table 6-1 LDAP/AD Settings - discover attributes and configurationinformation panel options

DescriptionField

Server Information

Fully-qualified host name or IP address ofthe LDAP server.

If a secure session is configured with theLDAP server using SSL certificates, enter thefully-qualified hostname that matches withthe fully-qualified hostname in the LDAPserver certificate.

Server Name (Mandatory)

Number of the port on which the LDAPserver is configured to run.

By default, this field displays the portnumber as 389. You can edit this portnumber, if required.

Port (Mandatory)

Check this check box if the anonymousoperations are disabled on the LDAP serverand a bind user ID is required to proceedwith configuring the LDAP-basedauthentication.

Thisserverrequiresmetologon (Optional)


84

Table 6-1 LDAP/AD Settings - discover attributes and configurationinformation panel options (continued)

DescriptionField

The complete Distinguished Name (DN) ofthe user that is used to bind to the LDAPserver.

If the LDAP server being used is ActiveDirectory (AD), you can provide the DN inany of the following formats:

■ [email protected]

■ domainname\username

For example, You can provide the DN [email protected]\Administrator

For RFC 2307 compliant LDAP servers,specify complete bind DN.

For example,cn=Manager,dc=vss,dc=symantec,dc=com

The LDAP or the AD administrator canprovide you the bind user name that you canuse.

Bind User Name/DN

Password that is assigned to the bind username that you use.

Password

Check this checkbox to use the SecureSockets Layer (SSL) certificates to establisha secure channel between the authenticationbroker and the LDAP server.

Use Secure Sockets Layer

Location of the trusted root CA certificate ofthe vendor that issued the LDAP servercertificate.

Certificate location

Query Information


Table 6-1 LDAP/AD Settings - discover attributes and configurationinformation panel options (continued)

DescriptionField

User name that the system use to detect theLDAP server-related settings.

Note: Make sure that the user name thatyou enter does not contain any specialcharacters. For example, do not enter thespecial character '(' in this field.

The system determines the search basebased on the user name that you specify inthis field.

User Name (Mandatory)

Name of the user group that the system useto detect the LDAP server-related settings.

Veritas Operations Manager displays thisfield if the user does not belong to any usergroups.

Note: Make sure that the group name thatyou enter does not contain any specialcharacters. For example, do not enter thespecial character '(' in this field.

The system determines the search basebased on the group name along with the username that you have specified.

Group Name

LDAP/AD Settings - configure LDAP based authenticationoptionsUse the LDAP/AD Settings - configure LDAP based authentication optionswizard panel to specify the Domain Name and the Search Base to configureLightweight Directory Access Protocol (LDAP) based authentication on the primaryauthentication broker.


86

Table 6-2 LDAP/AD Settings - configure LDAP based authentication options

DescriptionField

Displays the fully-qualified host name or IPAddress of the LDAP server that you havespecified in the LDAP/AD Settings -discover attributes and configurationinformation wizard panel.

You cannot edit this field.

Server Name

Unique name to identify the LDAP basedauthentication that you configure on theprimary authetication broker.

Note: In the Domain Name field, you canenter up to 32 characters.

Domain Name

Search Base

Select this option if you want to use thedefault search base that the sytem hasdetected using the information that you havespecified on the LDAP/AD Settings -discover attributes and configurationinformation wizard panel.

Use Default


Table 6-2 LDAP/AD Settings - configure LDAP based authentication options(continued)

DescriptionField

Select this option to specify the search baseother than the default search base.

For example, you can customize the searchbase as follows to authenticate the user(sampleuser) who belongs to theorganization (ou=HR), which is anorganization unit under ou=user:

The organization structure is given below:

ou=HR,ou=People,dc=veritas,dc=com

|-sampleuser

ou=Engg,ou=People,dc=veritas,dc=com

|-Eng1

The default search base isou=HR,ou=People,dc=veritas,dc=com

To authenticate users under ou=HR andou=Engg, set custom search base to a levelup:

ou=People,dc=symantec,dc=com

Custom

See “Configuring AD or LDAP authentication” on page 83.

Removing AD or LDAP authenticationIf you no longer want to use AD or LDAP-based authentication with a particularVeritas Operations Manager Enterprise Server domain on the primaryauthentication broker, you can use the Veritas Operations Manager EnterpriseServer console to remove the LDAP or AD configuration from that domain.

To remove an LDAP or AD configuration from a domain


2 Select the primary authentication broker.

3 In the Domains area, select the domain for which you want to remove AD orLDAP-based authentication.

4 click Unconfigure LDAP/AD.


88

5 Click Yes to confirm the removal.



Enabling and disabling domainsUse the Veritas Operations Manager Enterprise Server console to enable anauthentication domain on a Veritas Operations Manager Enterprise Server brokerso that you can do the following:

■ Display the domain on the Veritas Operations Manager Enterprise ServerLogin page.

■ Associate the domain with a security group. (A security group is a group ofusers to whom you grant privileges to use features).

Note:Domains get added and removed as administrators make changes to a broker.To see the most current list of domains on a broker, click Refresh Broker.

To enable authentication domains on a broker


2 In the Domains area, select the domains you want to enable.

3 Click Enable Domains.

4 In the Enable Domains dialog box, review the details and click OK.


Disable an authentication domain on a broker if you no longer want users fromthat domain to access your resources.

To disable authentication domains on a broker


2 In the Domains area, select the domains you want to disable.

3 Click Disable Domains.

4 In the Disable Domains dialog box, review the details and click OK.



Configuring user authorizationConfigure authorization to specify roles and privileges for groups of users in yourVeritas Operations Manager Enterprise Server authentication domains. Youconfigure authorization by adding security groups.

Note: Before you add security groups, be sure that you have configured VeritasOperations Manager Enterprise Server to discover your authentication domains.

Table 6-3 shows the roles that an administrator can assign to a security group,and the privileges that are associated with those roles.

Table 6-3 Security group privileges

PrivilegesRole

View all reports in the entire domain.Guest

Everything a Guest can do, plus:

■ Create reports

■ Access Veritas Operations ManagerManaged Hosts

You can optionally give Report Admins oneor more of the following privileges:

■ Add, delete, and modify business views.

■ Add and remove extended attributes.

■ Add, delete, and modify storage tiers,definitions, and rules for assignments.

Report Admin

Everything a Report Admin can do, plus:

■ Add, delete, and modify data sources forrollup.

■ Schedule data sources for rollup

■ Configure authentication andauthorization.

■ Manage product licenses

■ Set log levels

■ Configure Cognos.

Admin

Configuring authentication and authorizationConfiguring user authorization

90

Adding and removing security groupsUsing the Veritas Operations Manager Enterprise Server console, you can addsecurity groups to authorize groups of users in an authentication domain to accessVeritas Operations Manager Enterprise Server. When you add a security group,you specify which product features that group can access.


To add security groups

1 Select Settings > Security Groups.

2 Click New Security Group.

3 In the New Security Group dialog box, enter the name of the group as itappears in the OS, LDAP, or AD authentication domain. (The name mustmatch the name of the authentication group in the domain).

See “New Security Group options” on page 92.

4 Optionally click Check to make sure that the name you specify matches thename in the authentication domain.

5 Select a role for the security group.

See “Configuring user authorization” on page 90.

6 If you configure Report Admin-level privileges, specify the product featuresyou want the Report Admins to access.


Remove security groups if you no longer want users in a particular authenticationdomain to access Veritas Operations Manager Enterprise Server.

Note: You cannot remove the root security group for the primary authenticationbroker.

To remove security groups


2 Select one or more security groups that you want to remove and click RemoveSecurity Group.

3 In the RemoveSecurityGroup dialog box, click Yes to confirm the removal.


91Configuring authentication and authorizationConfiguring user authorization

New Security Group optionsUse the New Security Group dialog when you add a new security group to yourVeritas Operations Manager Enterprise Server configuration. The New SecurityGroup dialog is where you define the security group's attributes.

Table 6-4 New Security Group panel options

DescriptionField

The name of the security group that youwant to create.

The authentication group name and thesecurity group name must be the same. ClickCheck to verify that they are an exact match.The authentication group can be an OS groupor a LDAP/Authentication Domain group.

Note: The name of the security group for anNT domain must include the domain nameon which the group is configured, and thegroup name. The security group name mustbe entered in the domain name\groupnameformat. Example:Machinename\Administrator

Name

The name of the authentication domain thatyou want to associate with the securitygroup.

You can choose the domain names from thedrop-down list. The drop-down list containsall the authentication domains that are inthe enabled state.

Domain

Choose any of the following roles that youwant to associate with the security group:

■ Admin■ Report Admin■ Guest

See “Configuring user authorization”on page 90.

Role

Editing security groupsUse the Veritas Operations Manager Enterprise Server console to change a securitygroup's role or privileges.


92

To edit a security group


2 Select the security group that you want to modify and click Edit AccessControl.

3 In the EditAccessControl dialog, change the role, or add or remove privileges.

4 Click OK to submit the changes.

5 Click OK again to exit the Results panel.

93Configuring authentication and authorizationConfiguring user authorization


94

Managing the EnterpriseServer


■ Stopping and starting the Enterprise Server components

■ Configuring Enterprise Server settings

■ Backing up and restoring Veritas Operations Manager Enterprise Server

■ Gathering troubleshooting information

Stopping and starting the Enterprise Servercomponents

By default, the Veritas Operations Manager Enterprise Server starts after youinstall the product. You can, however, manually stop and restart the EnterpriseServer, and its components.

To stop and start the Veritas Operations Manager Enterprise Server components

1 On the Enterprise Server, open an operating system console and log in as auser with administrator-level privileges.

2 Change to the following directory:

C:\Program Files\Veritas\VRTSsfmh\bin>

3 Run the following script for stopping and starting components:

"C:\Program Files\Veritas\VRTSsfmh\bin\perl.exe" vomadm vomessc

--help

4 Do one of the following:

7Chapter

■ To start all of the services that are installed with Veritas OperationsManager Enterprise Server, enter the following command:vomadm vomessc [--force] --start component name

■ To stop all of the services that are installed with Veritas OperationsManager Enterprise Server, enter the following command:vomadm vomessc [--force] --stop component name

■ To get the status of all the services associated with a component:vomadm vomessc --status component name

Note: Use the --force option to start all of the components, but only for stoppingthe SFMS component.

You can stop and start the components all together, or separately. Table 7-1 showsthe component names.

Table 7-1 Enterprise Server component names

Component name for the scriptVeritas Operations Manager EnterpriseServer Component

ABrkrVOM Enterprise Server AuthenticationService

ApacheVOM Enterprise Server Apache Service

DatabaseSQLANYWHERE_VOMER_<ServerName>

GUIVeritas Enterprise Server Service

CognosCognos10

SFMSVeritas Storage Foundation MessagingService

AllAll components

Configuring Enterprise Server settingsYou can configure the following Veritas Operations Manager Enterprise Serversettings.

Managing the Enterprise ServerConfiguring Enterprise Server settings

96

Table 7-2 Enterprise Server settings

DescriptionType of setting

Enable or disable analytics gathering.

Optionally specify a proxy server for analyticsgathering. For the server name, specify either fullyqualified domain name (FQDN) or IP address.

Analytics Gathering settings

Trend data is maintained at daily granularity for thefirst 360 days. Any data older than 360 days isautomatically summarized by week, month, quarter,and year. Daily samples older than 360 days are purged.By default all trend data older than 3 years isautomatically purged.

You can change the default setting to a value between3 years and 10 years, specified in months.

Data Retention settings

Enable allowing partial data loads to succeed if an erroroccurs during rollup. Enabled by default.

Specify the number of roll-up archives to retain foreach roll-up source. The default is 10.

Roll-up settings

To change settings for the Veritas Operations Manager Enterprise Server

1 In the Veritas Operations Manager Enterprise Server console, select Settings> Enterprise Server.

2 In the EnterpriseServerSettings view, click the tab for the settings you wantto change, make the changes, and click Save Settings.

Backing up and restoringVeritasOperationsManagerEnterprise Server

You can use the Veritas Operations Manager Enterprise Server backup script toback up your database files, important configuration files, and Cognos reportdefinitions.

97Managing the Enterprise ServerBacking up and restoring Veritas Operations Manager Enterprise Server

To back up the Veritas Operations Manager Enterprise Server




3 Run the following script for backing up your configuration:

# perl.exe vomadm vomesbackup [--validate] --backup directoryname

where

--validate validates the database backup files, and directoryname is thename of the directory you want to store the backup files in.

For example: perl.exe vomadm vomesbackup --backup C:\vomesbackup

Restoring the Veritas Operations Manager Enterprise Server involves the following:

■ Restoring the database backup

■ Restoring the report definitions

To restore the database backup




3 Stop the database service. Enter the following:

# perl.exe vomadm vomessc --stop Database

4 Go to the the database directory. For example, enter the following:

# cd C:\ProgramData\Symantec\VRTSvomer\db

5 Back up the database file. Enter the following commands:

# move vomer.db vomer.db.old

# move vomer_data vomer_data.old

# move vomer_index vomer_index.old

# move vomer.log vomer.log.old

Managing the Enterprise ServerBacking up and restoring Veritas Operations Manager Enterprise Server

98

6 Copy the database files from the backup directory to database directory. Forexample, enter the following:

# cd C:\ProgramData\Symantec\VRTSvomer\db

# copy backup_directory\db\vomer

7 Start the database service. Enter the following:

cd C:\Program Files\Veritas\VRTSsfmh\bin>

# perl.exe vomadm vomessc --start Database

To restore the report definition

1 Locate the zip file from the backup directory. Make sure the extension is .zip.

2 Import the zip file into the installdir/Cognos/deployment directory. Enterthe following:

# copy backup_directory\cognos\er-5.0-reportsbkp.zip

installdir\Cognos\deployment

3 In the target environment, open IBM Cognos Connection by clicking theManage Reports icon on the Veritas Operations Manager Enterprise ServerHome page.

4 In the upper-right corner, click Launch IBM Cognos Administration.

5 On the Configuration tab, click Content Administration.

6 On the toolbar, click the NewImport button. You see the New Import wizard.

7 In the Deployment archive box, click the deployment archive that you wantto import.

8 Click Next.

9 Type a unique name, an optional description, and a screen tip for thedeployment specification.

10 Select the folder where you want to save the deployment specification, andclick Next.

11 Review the summary information and click Next.

12 Do one of the following:

■ To run the report once (now or later), click Save and run once and clickFinish. Specify the time and date for the run, and click Run. Review therun time and click OK.

■ To schedule a recurring time, click Save and schedule and then clickFinish. Then, select frequency and start and end dates, and click OK.

99Managing the Enterprise ServerBacking up and restoring Veritas Operations Manager Enterprise Server

When you run the import, you have the option of upgrading the deploymentspecification. If you choose not to upgrade the deployment specification at thistime, you can upgrade it later.

Gathering troubleshooting informationYou can run the vomesgather script to gather logs and other information you mayneed to debug problems with your Veritas Operations Manager Enterprise Server.

To gather troubleshooting information




3 Run the following script for troubleshooting your configuration:

# vomadm vomesgather --gt directoryname [--s sourcename]

where

directoryname is the name of the directory you want to store thetroubleshooting files in. Veritas Operations Manager Enterprise Servercontacts the rollup source (VOM Management Server) only if you include the--s sourcename option.

For example: perl.exe vomadm vomesgather --gt C:\vomadebug [--s

VOMServer00001]

Managing the Enterprise ServerGathering troubleshooting information

100

Creating and managingbusiness views with thecommand line interface

This appendix includes the following topics:

■ Creating and managing business views using the command line interface

■ About the business view files

■ Adding business views using the command line interface

■ Updating business views using the command line interface

■ Importing business views using the command line interface

■ Deleting business views using the command line interface

■ Exporting business views using the command line interface

Creating and managing business views using thecommand line interface

The business view feature of Veritas Operations Manager Enterprise Server letsyou gather information about storage objects and relate the information to yourbusiness. Business views organize data according to your business units,geography, or software applications. For example, you can construct a businessview to show available physical capacity across your global business units.

The Veritas Operations Manager Enterprise Server command line interfaceprovides similar functionality to the console for creating and managing business

AAppendix

views. It does not include the console business view rules feature for creatingrules to assign objects dynamically.

About the business view filesYou must know about the Veritas Operations Manager Enterprise Server businessview files if you update business views using the command line interface.

See “About the .view structure file” on page 102.

See “Sample .view structure file” on page 103.

See “About the CSV object files” on page 105.

About the .view structure fileIf you update business views using the command line interface, you update thestructure of a business view by modifying the .view structure file.

The .view structure file defines the structure of your business view. It specifiesthe name of your business view and the name of each level in the business viewhierarchy. It also specifies the object types that the view supports. It uses the .inifile format. Comment lines start with either the ‘;’ or ‘#’ characters.

The business .view file requires the following sections:

The [Business View] section specifies the name and description forthe business view. The section requires the following parameters:

■ Name

■ Description

[Business View]section

The .view file includes a series of required [Level#] sections. A uniquesection in the business view definition file represents each level inthe hierarchy. [Level1] defines the top level. [Level2] defines the nextlevel in the hierarchy, and so on. Level numbers must be consecutive.

Each Level section requires the following parameters:

■ Name

■ Description

[Level] sections

Creating and managing business views with the command line interfaceAbout the business view files

102

The [Object types] section is required and a single required parameternamed "Types." This parameter is a comma-separated list of the objecttypes that the view supports. You can only import the following typesof objects; all others are ignored.

■ Array

■ Cluster

■ File System

■ Host

■ NAS File System

■ NAS Share

■ Service Group

■ Volume

[Object types]section

Sample .view structure fileWhen you add a business view, Veritas Operations Manager Enterprise Servercreates a .view file to define the structure of your business view. You can add abusiness view using the Veritas Operations Manager Enterprise Server console,or using the command line interface.

When you add a business view using the command line interface, you define abase name for the .view file based on the questions you want to answer aboutobjects in your environment. The following shows a sample .view file using"GEOGRAPHY" as the base name.

; This definition file defines the overall structure of a business view.

; Section names are enclosed in square brackets ( [ ] ).

; Parameter values should not be quoted. Multi-line parameters are

; supported by ending each line with the backslash character.

;

; [Business View] section

; The Business View section defines the view name and description.

; A business view defines the logical structure used to organize

; objects into different business categories.

;

; This section has the following required parameters:

; Name - the name of the business view

; Description - a description for the business view

;

[Business View]

Name=Global

Description=Assets organized by location globally.

103Creating and managing business views with the command line interfaceAbout the business view files

; [Level] Sections

;

; The hierarchy defines a data dimension that allows the user to create

; drill-down reports. This hierarchy is defined by specifying a collection

; of one or more [Level] sections.

;

; Each level in the view hierarchy is defined by one of these sections.

; The level highest in the view is [Level1], the next level in the

; hierarchy is [Level2], etc.

;

; Each [Level] section has the following required parameters:

; Name - the name for the level

; Description - the description of the level

;

[Level1]

Name=Continent

Description= Major land masses that contain one or more countries.

[Level2]

Name=Country

Description=A defined expanse of sovereign land.

[Level3]

Name=State/Province

Description=A geographic sub-region of a Country.

[Level4]

Name=City

Description=A population center within a State or Province.

[Level5]

Name=Data Center

Description=A single data center within a city.

; [Object Types] section

;

; Each business view can support one or more object types. The Object

; Types section has a single parameter, containing a comma separated

; list of supported object types.

;

; The support types are:

; Host - a host object identified by name, ip, or unique id

; Array - an array object identified by name, ip, or unique id


104

;

;

[Object Types]

Types=Host


About the CSV object filesEach .csv file represents one of the object types that are defined in the .view filefor this business view. These files, collectively, are called the business viewassignment CSV files.

Each file should have the same base name as the name of the .view file. Businessview .csv files use the following naming convention. All files that make up anindividual view must use the same prefix. While the business view definition filehas a ‘.view’ extension, the CSV files have the extensions that map directly totheir associated object type. For example, a "foo_Host.csv" extension defines thebusiness view assignment for hosts.

If you used "GEOGRAPHY" as a base name, the .view and CSV files would be namedas follows:

■ GEOGRAPHY.view

■ GEOGRAPHY_Array.csv

■ GEOGRAPHY_Cluster.csv

■ GEOGRAPHY_Filesystem.csv

■ GEOGRAPHY_Host.csv

■ GEOGRAPHY_NAS_Filesystem.csv

■ GEOGRAPHY_NAS_Share.csv

■ GEOGRAPHY_Servicegroup.csv

■ GEOGRAPHY_Volume.csv

Each object type has a set of columns that uniquely identify the object. Thesecolumns are required in each object .csv assignment file. They are in addition tothe required hierarchy level columns that are defined in the .view file. Recordsthat do not have the required number of columns are rejected.

Each object type requires the following columns.


Table A-1 Object types and their required columns

Required object identifier columnsObject type

Define one or more of the following:

■ Name: The name of the array

■ IP: The SNMP IP address for the array. If the array has multipleIPs, you can specify the IPs by enclosing this column in doublequotes and separating addresses with a comma. For example,“127.0.0.1,192.168.1.1”.

■ unique_id

Array

Either define both the host and file system name, or specify theunique ID, as follows:

■ Host name: The name of the host to which the file systembelongs

■ File system name: The name of the file system

■ object_unique_id: A unique identifier that Veritas OperationsManager generates

Filesystem


■ Name: The name of the host

■ IP: The IP address for the host. If the host has multiple IPs,you can specify the IPs by enclosing this column in doublequotes and separating addresses with a comma. For example,“127.0.0.1,192.168.1.1”.


Host

Either define both the host and volume name, or specify theunique ID, as follows:

■ Host name: The name of host to which the file system belongs

■ Volume name: The name of the volume


Volume

Either define both the filer and NAS file system name, or specifythe unique ID, as follows:

■ Filer name: The name of the filer

■ File system name: The name of the NAS file system


NAS_Filesystem


106

Table A-1 Object types and their required columns (continued)

Required object identifier columnsObject type

Either define both the filer and path of the share, or specify theunique ID, as follows:

■ Filer name: The name of the filer

■ Path: The complete path of the share on the NAS volume


NAS_Share


■ Name: The name of the cluster


Cluster

Either define both the cluster and service group name, or specifythe unique ID, as follows:

■ Cluster name: The name of the cluster

■ Service group name: The name of the service group


Service Group

The columns in the CSV file start with all of the levels in the branch, in order,separated by commas. There must be a column for each of the levels that aredefined in the business view definition file. In addition to the level columns, youmust define all the columns required for the object type. The unique identifiercolumns for the object type follow the levels.

Each non-comment, non-blank line defines a node or object in the business view.If the view defines a tree branch but no object assignment, use empty commas asplaceholders for the object columns. If a leaf node misses its parent nodes, useempty commas as place holders.

Example:

#Continent, Country, State or Province, City, Data Center, name, IP,

unique id

Europe,France,Paris,,,,10.68.8.15,

Comment lines start with "#". Comments and blank lines are ignored. Do not placeany characters before the #. For example, if you include double quotes (") beforethe #, then the business view import process fails because the comment lines areconsidered assignment rows.



Adding business views using the command lineinterface

Veritas Operations Manager Enterprise Server includes a script that helps youcreate business views. This script prompts you with a series of questions aboutyour business views. The script includes questions such as the name of the businessview and how many levels it contains. This script creates a .view file (which definesthe data structure) and CSV files (one file for each object type).

To create business views using the command line interface

1 Open an operating system console and log in to the Enterprise Server as auser with administrator-level privileges.

2 Change to the Veritas Operations Manager Enterprise Server bin directory.By default, this directory is located as follows:

\Program Files\Veritas\VRTSvomer\bin

3 To create a business view, type the following command:

bv_create.bat -d directory

where directory is the directory where you want to save the business view.view and CSV files.

The script connects to the Veritas Operations Manager Enterprise Serverdatabase.

4 At the prompt, enter a name for your business view.

5 At the prompt, enter the number of levels in your business view.

6 At the prompt, enter the names and descriptions of each level.

7 At the prompt, enter "Y" or "N" to indicate whether the business view supportsspecific object types.

8 At the prompt, enter the base name of the view, which is used to create the.view file and the unique CSV files that are associated with each object.

For example, if you use "GEOGRAPHY" as a base name, the .view and CSVfiles are named as follows. They must use the same prefix:

■ GEOGRAPHY.view

■ GEOGRAPHY_Host.csv

■ GEOGRAPHY_Array.csv

■ GEOGRAPHY_Filesystem.csv

■ GEOGRAPHY_Volume.csv

Creating and managing business views with the command line interfaceAdding business views using the command line interface

108

The script creates the files in the directory that you specified with the -doption and finishes.

9 Update business view object files.

Adding a business view creates all of the business view files (the .view fileand the CSV files). Update the business view files to make sure that all of yourobjects are rolled up into the business view. Ensure that your hierarchies arecorrect.

For more information on updating business views:

See “Updating business views using the command line interface” on page 109.

Updating business views using the command lineinterface

When you add a business view, Veritas Operations Manager Enterprise Serversaves a structure (.view) file in the specified directory. You update a businessview's structure by editing the .view file and importing it into Veritas OperationsManager Enterprise Server.

To edit the business view structure

1 Check the required structure for the .view file.


See “Sample .view structure file” on page 103.

2 Copy the .view file to a local drive.

3 Using a text editor, edit your .view file. Make sure that all of your level namesare correct, and that they are in the correct hierarchical order.

4 Import the .view structure file into Veritas Operations Manager EnterpriseServer.

See “Importing business views using the command line interface” on page 110.

When you create a business view, Veritas Operations Manager Enterprise Serveralso saves an object (CSV) file for each object type. The CSV files are saved in thespecified directory. You assign objects to a business view by editing the CSV filesand importing them into Veritas Operations Manager Enterprise Server.

To assign objects to a business view

1 Check the required structure for the CSV files.

See “About the CSV object files” on page 105.

2 Copy the CSV files to a local drive.

109Creating and managing business views with the command line interfaceUpdating business views using the command line interface

3 Use a tool such as a spreadsheet to update the CSV files.

Make sure that the objects are in the appropriate levels in the business viewhierarchy.

4 Import the CSV files into Veritas Operations Manager Enterprise Server.

See “Importing business views using the command line interface” on page 110.

Importing business views using the command lineinterface

Veritas Operations Manager Enterprise Server provides a command line interfacescript for importing business views. The script performs the following actions:

■ Imports the data from the .view and .csv object files into Veritas OperationsManager Enterprise Server

■ Correlates the objects with those in the Veritas Operations Manager EnterpriseServer database

■ Adds the associated business view in the "View" folder for each supportedobject type to use in reports

■ Optionally updates the Cognos data hierarchy

Before you import a business viewIf you try to import the same business view twice, the second import is ignoredas a duplicate. To replace an existing business view, change the default behaviorof this script by setting the Overwrite_Existing_Views option in the import optionsfile.

See “Setting business view import options” on page 115.

Check the list of object types that you can include in business views. Check theCognos namespaces and view names, where the business view resides.

See “Object type namespaces and view names for business view reports”on page 42.

Importing the business view filesWhen you create a business view, Veritas Operations Manager Enterprise Serversaves a structure (.view) file and several object (CSV) files (one CSV file for eachobject type).

Creating and managing business views with the command line interfaceImporting business views using the command line interface

110

You can make changes in your business view files and then run a script to importthe business view files into Veritas Operations Manager Enterprise Server. Howyou run the script depends on the type of changes you make to your businessview. You also use the business view files to transfer business views betweenEnterprise Servers.

Table A-2 Importing business view files

See the following procedureObjective

To import both the structure (.view) andobject (CSV) files

To create a new business view, or to importa business view from one Enterprise Serverto another

To import both the structure (.view) andobject (CSV) files

To make changes that affect the businessview structure, such as adding new objecttypes or modifying hierarchy levels

To import the object (CSV) files onlyTo make changes that do not affect thebusiness view structure, such as movingobjects between tree branches or assigningobjects that were previously unassigned

Note: When you edit a business view, then modify a report in Report Studio, youreceive a warning message regarding updated packages. This message displayswhen the business view or namespace changes. Click OK to continue editing thereport. The message does not display unless you modify another business view.

To import both the structure (.view) and object (CSV) files




111Creating and managing business views with the command line interfaceImporting business views using the command line interface

3 To import the business views, type the following command:

bv_import_csv.bat -d directory -v .business_view_file -o options

file -u

where:

is the directory that contains the CSV files that youwant to import.

directory

is the name of the business view .view file that youwant to import. Unless you specify the -va parameter,all view files are processed. If you specify -v, only theview that is defined by the specified .view file isimported.

business_view_file

is the name of an options file. You can use an importoptions file to override default behaviors during theimport process. By default, the script does not overridean existing business view.

See “Setting business view import options” on page 115.

options file

executes the update_metamodel script, whichupdates the data hierarchy (metamodel) with theimported business view at the conclusion of the import.If you omit this flag, any physical changes to thebusiness view are not reflected in the VeritasOperations Manager Enterprise Server data hierarchyuntil you runupdate_metamodel. Updating the datahierarchy is essential for you to use the business viewstructure in your reports.

-u

4 Review the script-generated report of the import.

The business views import into Veritas Operations Manager Enterprise Server.There, you can create the reports that use the business views.

To import the object (CSV) files only





112

3 To set your environment variables, type the following command:

create_ccer_env.bat

4 To import the business views, type the following command:

bv_import_csv.bat -d directory -v .business_view_file -a

where:

is the directory that contains the CSV files that youwant to import.

directory

is the name of the business view .view file that youwant to import. Unless you specify the -va parameter,all view files are processed. If you specify -v, only theview defined by the .view file specified is imported.

business_view_file

causes the script to perform only the object assignmentphase. Use this option to assign additional objects toan existing Veritas Operations Manager EnterpriseServer view. Using this option does not change theVeritas Operations Manager Enterprise Server datahierarchy or business view structure. If you specify -awith the -u flag, -u is ignored. This option lets youupdate an existing view iteratively without waiting forthe recreation of database tables or updating the datahierarchy. Use this option only when your changes donot alter the underlying structure of the business view.

-a

The business view updates.

Associating undefined objects to business viewsObjects that were imported during the creation of a business view might not beassociated with objects in the business view. You can manually associate theseundefined objects with business views.

The objects might not be associated to business views due to the following reasons:

■ The objects were not found in the database.

■ The CSV object files had too few or too many columns.

■ The objects are not supported.

For any of these cases, Veritas Operations Manager Enterprise Server stores therejected object files in a reject log. Veritas Operations Manager Enterprise Servercreates a log for each rejected object. For more information about the logs, referto the following topics:


See “Default business view import and export log files” on page 127.

To associate undefined objects to business views





create_ccer_env.bat

4 Locate the reject logs in the following directory:

\ProgramData\Symantec\VRTSvomer\logs\business_view

where current working directory is the directory from which you executedthe bv_import_csv script.

5 Identify why the objects were not found in Veritas Operations ManagerEnterprise Server. For example, you might need to define additional datarollup sources or add the object to a Veritas Operations Manager ManagementServer. Your CSV files may also contain errors, which are listed in the importreject logs.

6 If objects are not assigned to any node in the business view, do the following:

■ Export the unassigned objects.

■ Add them to the appropriate CSV object file.

■ Re-import the view using the bv_import_csv script and the -a flag. Theflag tells the script to skip the creation of the view tables and update theobject assignments only. This flag also does not update the Cognos datahierarchy.To re-import the business views, type the following command:bv_import_csv.bat -d directory -v .view file -o options file

-a

Where:

Is the directory that contains the CSV files that youwant to import.

directory


114

Defines the file name of the business view you wantto import. If you don't enter-v, Veritas OperationsManager Enterprise Server processes all the .viewfiles. If you specify-v, Veritas Operations ManagerEnterprise Server imports only the specified viewfile.

view file

Is the name of an options file. You can use animport options file to override default behaviorsduring the import process. By default, the scriptdoes not override an existing business view.

See “Setting business view import options”on page 115.

options file

Causes the script to perform only the objectassignment phase. Use this option to assignadditional objects to a Veritas Operations ManagerEnterprise Server view. This option does notchange the Veritas Operations Manager EnterpriseServer data hierarchy or business view. If youspecify -a with the -u flag, -u is ignored. Thisoption lets you update a view iteratively withoutwaiting for database tables to be recreated or thedata hierarchy to be updated. You should only usethis option when your changes do not alter thebusiness view's of the underlying structure.

-a

Setting business view import optionsYou can change the default behaviors when you import Veritas Operations ManagerEnterprise Server business views (using the bv_import_csv script) by changingsettings in an options file. You pass this file to the bv_import_csv script usingthe -o command line switch. The Veritas Operations Manager Enterprise Serverpackage contains a default options file bv_import_csv.opt.

You can change the following settings:

Table A-3 Business view options

SettingsOption

■ 0 (Default): Display messages on the consoleand write them to the log file.

■ 1: Do not display messages on the console, butwrite them to the log file.

Disable writing messages to the console


Table A-3 Business view options (continued)

SettingsOption

All log files are created in the "log" directory.

See “Default business view import and export logfiles” on page 127.

Specify the location for import log files.

■ 0: Display only status messages.

■ 1 (Default): Enable the standard logging level.

■ 2: Enable verbose debug logging.

Specify the logging level, which addsexpanded logging for troubleshootingproblems.

If you try to import the same business view twiceusing the bv_import_csv script, the secondimport is ignored as a duplicate. To replace anexisting business view, change the defaultbehavior of this script by setting theOverwrite_Existing_Views option.

■ No (Default): Discard duplicate views in theimport set and keep the existing view inVeritas Operations Manager Enterprise Serverintact.

■ Yes: Overwrite any existing duplicateVeritasOperations Manager Enterprise Server views.

Overwrite the existing view, whichdefines what happens if a business viewin an export set already exists inVeritas Operations Manager EnterpriseServer

Deleting business views using the command lineinterface

You can delete a Veritas Operations Manager Enterprise Server business viewusing a command-line script.

Warning: When you delete a business view, you can no longer use it in reports. Asa result, all existing reports that use the business view no longer work properly.Because of this issue, we recommend that you do not delete business views.

To delete a business view using a command-line script




Creating and managing business views with the command line interfaceDeleting business views using the command line interface

116


create_ccer_env.bat

4 To delete a business view, type the following command:

bv_import_csv.bat -x business_view_file

where business_view_file is the file name of the business view that you wantto delete.

Veritas Operations Manager Enterprise Server deletes the business view. Youcan no longer run the reports that use the business view.

Exporting business views using the command lineinterface

You can export business views from a Veritas Operations Manager EnterpriseServer. You might want to do this export to transfer business views from oneVeritas Operations Manager Enterprise Server to another.

To export business views from a Veritas Operations Manager Enterprise Server





create_ccer_env.bat

4 To export business views, type the following command:

bv_export_csv.bat -d directory

where directory is the directory that stores the exported files.

The business views export to the specified directory.

117Creating and managing business views with the command line interfaceExporting business views using the command line interface

Creating and managing business views with the command line interfaceExporting business views using the command line interface

118

Command andconfiguration file referencefor business views


■ bv_create.bat

■ bv_describe_views.bat

■ bv_export_csv.bat

■ bv_import_csv.bat

BAppendix

bv_create.batbv_create.bat – creates a business view .view file and CSV files (one for eachobject type) on a Veritas Operations Manager Enterprise Server

SYNOPSISbv_create.bat -d directory

DESCRIPTIONThe bv_create.bat script creates a business view .view file (which defines thedata structure of the business view) and CSV files (one file for each object type).You can then edit the files in a spreadsheet application and later import theminto Veritas Operations Manager Enterprise Server using the bv_import_csv.batscript. Business views can be used with Veritas Operations Manager EnterpriseServer reports.

OPTIONS-d directory

Required. Directory is the directory where you want to save the business view.view and CSV files.

NOTESBy default, bv_create.bat resides in:


EXAMPLESType the following command to create a .view file and .csv files in a directorycalled "location" that you can later import into Veritas Operations ManagerEnterprise Server:

bv_create.bat -d location

Command and configuration file reference for business viewsbv_create.bat

120

bv_describe_views.batbv_describe_views.bat – displays information about all the business viewsdefined on an Enterprise Server

SYNOPSISbv_describe_views.bat

DESCRIPTIONThe bv_describe_views.bat script displays information about all the businessviews that are defined in Veritas Operations Manager Enterprise Server. Thescript reports the view name, description, levels, and supported object types, aswell as the Cognos packages that the view supports.

NOTESBy default, bv_describe_views.bat resides in:


EXAMPLESTo provide a description of all existing business views in an instance of VeritasOperations Manager Enterprise Server type the following command:

bv_describe_views.bat

121Command and configuration file reference for business viewsbv_describe_views.bat

bv_export_csv.batbv_export_csv.bat – exports business view data to CSV format on an EnterpriseServer

SYNOPSISbv_export_csv.bat -d directory [-u][-v view name]

DESCRIPTIONThe bv_export_csv.bat script exports all Veritas Operations Manager EnterpriseServer business views to CSV format and creates these files in a specified directory.

OPTIONS-d directory

Required. Directory into which the script writes the business view CSV files.

-u

Optional. Only exports the objects that are not assigned to a business view.If this option is combined with the -v option, then the script exports objectsthat are not assigned to the specified view.

-v view name

Optional. Lets you export a specific view by providing the view name. Bydefault, this script exports all existing business views.

-a Optional. Exports all the objects that are found in the Veritas OperationsManager Enterprise Server database that the business views support,regardless of their assignment states.

NOTESBy default, bv_export_csv.bat resides on the Veritas Operations ManagerEnterprise Server host in the following directory: \ProgramFiles\Veritas\VRTSvomer\bin

EXAMPLESThe following command exports the CSV file for the geography view into theC:\Program Files\Veritas\VRTSvomer\views directory:

Command and configuration file reference for business viewsbv_export_csv.bat

122

bv_export_csv.bat -d C:\Program Files\Veritas\VRTSvomer\views - v

geography.view

123Command and configuration file reference for business viewsbv_export_csv.bat

bv_import_csv.batbv_import_csv.bat – updates, imports, and deletes business views on a VeritasOperations Manager Enterprise Server

SYNOPSISbv_import_csv.bat -d directory [-v .view file] [-x display_name] [-o

options_file] [-u] [-a] [-?] [-h]

DESCRIPTIONThe bv_import_csv.bat script imports business views that you created or thatyou exported from Veritas Operations Manager Enterprise Server or VeritasBackup Reporter and from Enterprise Reporter. The script also updates and deletescurrent business views.

OPTIONS-d directory

Required. The directory that contains the business view CSV files that youwant to import.

-v .view file

Optional. Defines the file name of the business view .view file to import.

-o options_file

Optional. The import options file lets you override default behaviors duringimport operations. View an example options file, import.opt, in the followingdirectory: \Program Files\Veritas\VRTSvomer\examples

-u Optional. Executes the update_metamodel.bat script, which updates themetamodel with the imported business view. If this flag is omitted, anyphysical changes to the business view are not reflected in the Cognosmetamodel until update_metamodel.bat is executed.

-a Optional. Causes the script to perform only the object assignment phase. Useto assign additional objects to an existing Veritas Operations ManagerEnterprise Server view. Will not perform changes to the metamodel or thebusiness view structure. If this option is specified with the -u flag, the -u flagis ignored.

-x display_name

Optional. Deletes the specified view.

Command and configuration file reference for business viewsbv_import_csv.bat

124

-? Prints this usage message.

-h Prints this usage message.

NOTESBy default, bv_import_csv.bat resides on the Veritas Operations ManagerEnterprise Server host in the following directory: \ProgramFiles\Veritas\VRTSvomer\bin

EXAMPLESEXAMPLE 1: The following command imports business views that you created orthat were exported from CommandCentral Service or Veritas Backup Reporter:

bv_import_csv.bat -d C:\Program Files\Veritas\VRTSvomer\views

EXAMPLE 2: The following command imports business views that you created orthat were exported from another Veritas Operations Manager Enterprise Server:

bv_import_csv.bat -d C:\Program Files\Veritas\VRTSvomer\views -u

EXAMPLE 3: The following command imports a current business view which wasupdated with the changes that did not affect the business view’s structure:

bv_import_csv.bat -d C:\Program Files\Veritas\VRTSvomer\views -v

mybusinessview.view -a

EXAMPLE 4: The following command imports a current business view which wasupdated with the changes that do affect the business view’s structure:

bv_import_csv.bat -d C:\Program Files\Veritas\VRTSvomer\views -v

mybusinessview.view -o C:\Program

Files\Veritas\VRTSvomer\views\bv_import_csv.opt -u

EXAMPLE 5: The following command deletes a current business view:

bv_import_csv.bat -x mybusinessview.view

125Command and configuration file reference for business viewsbv_import_csv.bat

Command and configuration file reference for business viewsbv_import_csv.bat

126

Log file reference


■ Default business view import and export log files

■ Default Cognos log files

■ Default console log files

■ Default data rollup log files

Default business view import and export log filesVeritas Operations Manager Enterprise Server provides default business viewimport and export related log files for administrator use. The scripts generatethese log files.

Table C-1 describes the log files that each script generates.

CAppendix

Table C-1 Default business view import and export files

Log file detailsScript

■ Log file name: import.log

Location:C:\ProgramData\Symantec\VRTSvomer\logs\business_view

Description: This log file captures all output from the script. The"timestamp" is in MMDDYYYYHHMMSS format.

■ Log file name: "view"_"type".rej


Description: This log file captures all of the rejected "type" records forthe "view", where "type" is one of 'Host', 'Array', 'File system', or'Volume', and "view" is the base name of the view set.

■ Log file name: "view"_"type"_sqlldr.log


Description: This log file contains any messages that the databasecommands generate (which thebv_import_cs.pl script uses to populateimport staging tables).

bv_import_csv.bat

■ Log file name: export.log


Description: This log file captures all output from the script. The"timestamp" is in MMDDYYYYHHMMSS format.

bv_export_csv.bat

■ Log file name: update-metamodel.log


Description: This log file captures all output from the script.

update_metamodel.bat

Default Cognos log filesVeritas Operations Manager Enterprise Server provides default Cognos relatedlog files for administrator use. Cognos is a reporting engine that enablescustomizable reports.

Table C-2 describes the log files that are provided.

Log file referenceDefault Cognos log files

128

Table C-2 Default Cognos log files

DetailsLog type

Log file name: cogserver.log

Location: C:\Program Files\Veritas\VRTSvomer\Cognos\logs

Description: This log file contains all Cognos server errors.

Cognos servererrors

Log file name: tomcat.log


Description: This log file contains the Cognos errors that are related to Apache Tomcat servletcontainers.

Cognos Tomcaterrors

Log file name: cognos_config.log


Description: This log file contains details for troubleshooting the Cognos configuration issuesthat occurred during installation.

Cognosinstallation errors

Log file name: forecasting.log


Description: This log file contains error debug messages related to forecasting.

Forecasting errors

Default console log filesVeritas Operations Manager Enterprise Server provides default console relatedlog files for administrator use.


Table C-3 Default console log files

DetailsLog type

Log file name: WebDebugLog.txt.0

Location: C:\ProgramData\Symantec\VRTSvomer\logs

Description: This log file shows console messages and is useful for debugging console issues.

StorageManagement WebConsole

Log file name: _vrtsweb0.0.log


Description: This log file shows any console errors that are related to the Apache Tomcat servletcontainers.

Tomcat

129Log file referenceDefault console log files

Table C-3 Default console log files (continued)

DetailsLog type

Log file name: \ er_config.log

Location: C:\ProgramData\Symantec\VRTSsfmh\logs

Description: This log file logs the information about the configuration.

Configuration

Log file name: \ vxdeploy.log

Location:C:\ProgramData\Symantec\VRTSsfmh\logs\

Description: This log file contains product upgrade related log information.

Upgrade

Default data rollup log filesVeritas Operations Manager Enterprise Server provides default data rollup relatedlog files for administrator use. A software tool called Kettle performs the extract,transform, and load (ETL) process and generates these log files during that process.


Table C-4 Default data rollup log files

DetailsLog type

Log file name: rollup_process_rollup_source_key.log


Description: This log file includes data rollup logging for archiving and deleting from theprevious batch, starting a new rollup, and creating a new batch.

Rollup process

Log file name: rollup_mgmt_rollup_source_name.log


Description: This log file includes data rollup logging for creating staging area, remoteprocessing, and importing data to an ASA database.

Rollupmanagement

Log file name: staging*.log


Description: This log file provides detailed data rollup logging for the task called Import datato VOM-A database.

Staging

Log file referenceDefault data rollup log files

130

Table C-4 Default data rollup log files (continued)

DetailsLog type

Log file name: object_name.log

Location: AppData\VRTSvomer\conf\db\vomer.log

Description: From the Stage log file with stderr lines, find another log entry for the objectwhere the rollup failed. This log file tells whether an error happened when data was loadedinto the Veritas Operations Manager Enterprise Server database.

Database load

131Log file referenceDefault data rollup log files

Log file referenceDefault data rollup log files

132

Aadding

business views 32, 108data sources 17security groups 91storage tiers 46

Advanced Rule Buildercreating storage tier rules 69examples 71

Analytic Gathering settings for Enterprise Server 96

BBasic Rule Builder

creating storage tier rules 61examples 64

business view rulescreating 36enabling or disabling 40overview 36running 39viewing, modifying, or deleting 38

business viewsadding 108adding instances 34adding or editing 32assigning objects to 35, 41associating undefined objects to 113bv_create.bat 120bv_describe_views.bat 121bv_export_csv.bat 122bv_import_csv.bat 124creating rules for assigning objects 36deleting 33, 116deleting instances 34editing instances 34exporting 43, 117hierarchies 30import options 115importing 43, 110managing using the command line interface 101overview 29, 31

business views (continued)reference 102transferring between Enterprise Servers 43unassigning objects from 42updating 109

bv_create.bat 120bv_describe_views.bat 121bv_export_csv.bat 122bv_import_csv.bat 124

CCognos namespace

business views 42commands

bv_create.bat 120bv_describe_views.bat 121bv_export_csv.bat 122bv_import_csv.bat 124

DData Retention settings for Enterprise Server 96data rollup

disabling data sources 18enabling data sources 18extended attributes 19options 27overview 15running 22scheduling 21storage objects 16troubleshooting 24–25viewing status 22

data sourcesadding 17deleting 18disabling 18enabling 18modifying 17overview 16

Database Message Logging settings for EnterpriseServer 96

Index

debug log messages for Enterprise Server 96deleting

business views 33, 116data sources 18storage tiers 73

EEnterprise Server

settings 96Enterprise Server components

starting 95stopping 95

ETL. See data rollupexporting

business views 43, 117extended attributes

including 20overview 19removing 21storage objects 19using 19

Hhierarchies for business views

defining 32planning 30

Iimport options

setting for business views 115importing

business views 43, 110

KKettle 15

Llicense deployment reports 78Licensing and Pricing

NProcessor tier 78OS tier 78processor tier 78server tier 78UNIX

Solaris, HP-UX, AIX 78log files

default business view 127

log files (continued)default console 129default data rollup 130Windows default Cognos 128

logging settings for Enterprise Server messages 96

Mmodifying

business views 32, 109data sources 17storage tiers 47

Oobjects

assigning to business views 35, 41assigning to business views using rules 36unassigning from business views 42undefined 113

PProxy settings for Enterprise Server 96

Rremoving

business views 33, 116security groups 91

reportsbusiness views

adding 108adding instances 34adding or editing 32assigning objects to 41deleting instances 34editing instances 34importing 110namespaces 42object types 42unassigning objects 42updating 109view names 42

Rollup settings for Enterprise Server 96rules, business view. See business view rulesrules, storage tier. See storage tier rules

Ssecurity groups

adding and removing 91

Index134

storage tier rulescreating

Advanced Rule Builder 69Basic Rule Builder 61

modifyingAdvanced Rule Builder 69Basic Rule Builder 61

overview 48syntax 49

storage tiersadding 46deleting 73modifying 47overview 45rankings

adjusting 73overview 73

rulesAdvanced Rule Builder 69Basic Rule Builder 61overview 48syntax 49

storage tiers optionsicons 74

Ttroubleshooting

data rollup 24–25

Uundefined objects

associating to business views 113

VVeritas Operations Manager Advanced

componentsASA database 13Cognos 13Enterprise Server console 13Kettle 13Management Server 13

135Index

veritas operations manager enterprise server 5.0 ...€¦ · all support services will be delivered...

Documents