symantec opscenter administrator's guide - sort home · symantec opscenter...

Symantec OpsCenterAdministrator's Guide

Windows and UNIX

Release 7.0.1

Symantec OpsCenter Administrator's GuideThe software described in this book is furnished under a license agreement and may be usedonly in accordance with the terms of the agreement.

Documentation version: 7.0.1

Legal NoticeCopyright © 2010 Symantec Corporation. All rights reserved.

Symantec and the Symantec Logo are trademarks or registered trademarks of SymantecCorporation or its affiliates in the U.S. and other countries. Other names may be trademarksof their respective owners.

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

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

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

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

Symantec Corporation350 Ellis StreetMountain View, CA 94043

http://www.symantec.com

http://www.symantec.com

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

Symantec’s support offerings include the following:

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

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

■ Upgrade assurance that delivers software upgrades

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

■ Premium service offerings that include Account Management Services

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

www.symantec.com/business/support/

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

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


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

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

■ Product release level



■ Hardware information

■ Available memory, disk space, and NIC information

■ Operating system

■ Version and patch level

■ Network topology

■ Router, gateway, and IP address information

■ Problem description:

■ Error messages and log files

■ Troubleshooting that was performed before contacting Symantec

■ Recent software configuration changes and network changes

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


Customer serviceCustomer service information is available at the following URL:


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

■ Questions regarding product licensing or serialization

■ Product registration updates, such as address or name changes

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

■ Latest information about product updates and upgrades

■ Information about upgrade assurance and support contracts

■ Information about the Symantec Buying Programs

■ Advice about Symantec's technical support options

■ Nontechnical presales questions

■ Issues that are related to CD-ROMs or manuals



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

[email protected] and Japan

[email protected], Middle-East, and Africa

[email protected] America and Latin America

mailto:[email protected]



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

Chapter 1 Getting started using Symantec OpsCenter . . . . . . . . . . . . . . . . . . 19

About Symantec OpsCenter ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19About Symantec OpsCenter functions .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20About Symantec OpsCenter Analytics functions .... . . . . . . . . . . . . . . . . . . . . . . 20About monitoring and managing NetBackup .... . . . . . . . . . . . . . . . . . . . . . . . . . . . 22About alerting in OpsCenter ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22About reporting in Symantec OpsCenter Analytics ... . . . . . . . . . . . . . . . . . . . . 22

About what's new in Symantec OpsCenter 7.0.1 ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24About OpsCenter components ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

About the OpsCenter Server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27About the OpsCenter Agent ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30About the OpsCenter Java View Builder ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

About using the OpsCenter console ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34About starting the OpsCenter console ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

About Web browser considerations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35About accessing the OpsCenter console ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Logging on to the Symantec OpsCenter console ... . . . . . . . . . . . . . . . . . . . . . . . . 44Logging out of the OpsCenter console ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Configuring the OpsCenter session timeout interval ... . . . . . . . . . . . . . . . . . . 50About possible OpsCenter console issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

About OpsCenter console components ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55About using the links on the title bar ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57About using tabs and subtabs ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58About refreshing the OpsCenter console ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Using the Task pane .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59About the View pane .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59About the Symantec ThreatCon pane .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Using the quick links in the Task pane .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Using the Alert Summary pane .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Using the content pane .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65About the OpsCenter status bar ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68About visual keys in the console ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68About using tables ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

About quickly performing common tasks in OpsCenter ... . . . . . . . . . . . . . . . . . . . . 74

Contents

About using Web browser bookmarks .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75About OpsCenter documentation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Chapter 2 Upgrading to Symantec OpsCenter 7.0.1 . . . . . . . . . . . . . . . . . . . . . 77

Upgrading to Symantec OpsCenter 7.0.1 on Windows and UNIX .... . . . . . . . 77Before you install or upgrade to OpsCenter 7.0.1 ... . . . . . . . . . . . . . . . . . . . . . . . 77About platforms supported by OpsCenter 7.0.1 ... . . . . . . . . . . . . . . . . . . . . . . . . . 78About backup and archiving products supported by OpsCenter

7.0.1 ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Upgrading to Symantec OpsCenter 7.0.1 on Windows .... . . . . . . . . . . . . . . . 83Upgrading to Symantec OpsCenter 7.0.1 on UNIX .... . . . . . . . . . . . . . . . . . . . . 95Installing and uninstalling OpsCenter 7.0.1 on AIX .... . . . . . . . . . . . . . . . . . . . 99

Uninstalling OpsCenter 7.0.1 release update on Windows andUNIX .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103Uninstalling OpsCenter 7.0.1 on Windows .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103Uninstalling OpsCenter 7.0.1 on UNIX .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Chapter 3 Installing Symantec OpsCenter 7.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Planning an OpsCenter installation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109About the software components that OpsCenter uses ... . . . . . . . . . . . . . . . 109About the OpsCenter licensing model ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111About the NetBackup and OpsCenter DVD .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116About platforms supported by OpsCenter ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116About backup and archiving products supported by Symantec

OpsCenter ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119About managed NetBackup master server considerations .... . . . . . . . . 121Design your OpsCenter server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122About supported upgrade paths .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125About OpsCenter Agent deployment ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Before you install or upgrade .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Installing Symantec OpsCenter on Windows and UNIX .... . . . . . . . . . . . . . . . . . . 134Installing Symantec OpsCenter on Windows .... . . . . . . . . . . . . . . . . . . . . . . . . . . 135Installing Symantec OpsCenter on UNIX .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139Installing Symantec OpsCenter silently on Windows .... . . . . . . . . . . . . . . . 144

Upgrading to OpsCenter on Windows and UNIX .... . . . . . . . . . . . . . . . . . . . . . . . . . . . 159Upgrade considerations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159Upgrading from NetBackup Operations Manager to Symantec

OpsCenter on Windows and UNIX .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160Upgrading from Veritas Backup Reporter to OpsCenter Analytics

on Windows and UNIX .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166Monitoring data migration from NOM to Symantec

OpsCenter ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Contents8

Monitoring data migration from VBR to Symantec OpsCenterAnalytics ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

Upgrading to OpsCenter Server on a different UNIX system .... . . . . . 206Post-installation tasks ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

Verifying that Symantec OpsCenter is running properly ... . . . . . . . . . . . 212About starting to use OpsCenter ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212About the start-up tasks that OpsCenter performs .... . . . . . . . . . . . . . . . . . . 213Tuning OpsCenter for more performance .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

Using an earlier NOM or VBR installation after upgrade .... . . . . . . . . . . . . . . . . 231Uninstalling Symantec OpsCenter on Windows and UNIX .... . . . . . . . . . . . . . . 232

Uninstalling Symantec OpsCenter on Windows .... . . . . . . . . . . . . . . . . . . . . . . 233Uninstalling Symantec OpsCenter on UNIX .... . . . . . . . . . . . . . . . . . . . . . . . . . . 233

Clustering Symantec OpsCenter ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235About a Symantec OpsCenter cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235Supported cluster solutions .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235About running commands on the active node .... . . . . . . . . . . . . . . . . . . . . . . . . 236Clustering Symantec OpsCenter on Windows .... . . . . . . . . . . . . . . . . . . . . . . . . . 236Uninstalling Symantec OpsCenter from the Windows

cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243Clustering Symantec OpsCenter Server on Solaris ... . . . . . . . . . . . . . . . . . . . 243Uninstalling OpsCenter Server from the Solaris cluster ... . . . . . . . . . . . . 249Known issue during uninstallation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

Chapter 4 Administering Symantec OpsCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251

About OpsCenter services and processes used by OpsCenter ... . . . . . . . . . . . . 251About services used by OpsCenter on Windows .... . . . . . . . . . . . . . . . . . . . . . . 252About processes used by OpsCenter on UNIX .... . . . . . . . . . . . . . . . . . . . . . . . . . 253

About OpsCenter server scripts on Windows and UNIX .... . . . . . . . . . . . . . . . . . 254Controlling OpsCenter services and processes ... . . . . . . . . . . . . . . . . . . . . . . . . 255About dependency of services ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259About nbproxy processes on NetBackup master servers ... . . . . . . . . . . . . 259

About OpsCenter database administration .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260Running OpsCenter commands .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261Saving the OpsCenter database and database logs on separate

hard disks ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264About database troubleshooting .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268

Configuring remote authentication service in OpsCenter ... . . . . . . . . . . . . . . . . 268About backup and restore of OpsCenter and OpsCenter

Analytics ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270Backing up OpsCenter ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270Restoring OpsCenter ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273

About communication and firewall considerations .... . . . . . . . . . . . . . . . . . . . . . . . 276

9Contents

About ports required to communicate with backupproducts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279

About Web browser to Symantec OpsCenter Web GUIconnection .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280

About Symantec OpsCenter Web GUI to Symantec OpsCenterserver software communication .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281

About Symantec OpsCenter server to NetBackup master server(NBSL) communication .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282

About SNMP traps .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282About Symantec OpsCenter Web GUI/Symantec OpsCenter server

to Sybase database communication .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282About Symantec OpsCenter Web GUI to Symantec OpsCenter

server email communication .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283Gathering troubleshooting data with the support script ... . . . . . . . . . . . . . . . . . . 283About OpsCenter log files ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286

About VxUL log files ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286About OpsCenter log files on Windows servers ... . . . . . . . . . . . . . . . . . . . . . . . . 288About OpsCenter log files on UNIX servers ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291

Chapter 5 Understanding OpsCenter settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293

About the settings in OpsCenter ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294Setting user preferences ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295

Changing your password .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299Managing licenses ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300

Adding license keys ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300Viewing license keys ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301Deleting license keys ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301

Configuring data purge settings ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301About restoring NOM or VBR purge settings after upgrading to

OpsCenter Server 7.0 ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302Configuring SMTP server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303Configuring Symantec ThreatCon feature in OpsCenter ... . . . . . . . . . . . . . . . . . . 304Adding host aliases ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305Merging objects (hosts) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306Modifying Tape Library information .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306Copying user profiles ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307Setting report export location .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308Managing Object Types ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308

Modifying object types ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308Deleting object types ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309Adding attributes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309Deleting attributes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309

Contents10

Managing users ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310About user access rights ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310Viewing the list of existing users ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314Adding new users ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314Editing users ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314Resetting user password .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315Deleting users ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315Viewing user groups .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316Adding user groups .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316Editing user groups .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316Deleting user groups .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317

Managing recipients ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317Viewing email recipients ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317Viewing SNMP trap recipients ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318Creating email recipients ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319Creating SNMP trap recipients ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321Modifying Email or SNMP recipient information .... . . . . . . . . . . . . . . . . . . . . 322Deleting Email or SNMP recipient ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323

Managing cost analysis and chargeback for OpsCenter Analytics ... . . . . . 323Setting a default currency for cost reports ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323Editing currency list ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324Managing Cost Variables ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325Managing cost formulae .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328Managing cost estimation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329

Chapter 6 Understanding data collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333

About data collection in OpsCenter ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333About OpsCenter Agents ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334About Data Collectors ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335About backup and archiving products supported by Symantec

OpsCenter 7.0.1 ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337Managing OpsCenter Agents ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339

Viewing Agent status ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339Configuring an OpsCenter Agent ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340Modifying an Agent ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341Deleting Agents ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342

Managing Data Collectors ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342Viewing Data Collector status ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342Configuring a Data Collector ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343Modifying a Data Collector configuration .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345Deleting Data Collectors ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346

Configuring data collection for NetBackup .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346

11Contents

About the NetBackup data collection view .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347How OpsCenter collects data from NetBackup .... . . . . . . . . . . . . . . . . . . . . . . . . 348About NetBackup versions that OpsCenter 7.0.1 can monitor and

manage .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349Viewing master server details and data collection status ... . . . . . . . . . . . 350Adding a master server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354Editing a master server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362Deleting a master server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362Controlling data collection for a master server ... . . . . . . . . . . . . . . . . . . . . . . . . 363

Collecting data from Backup Exec .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363Collecting data from PureDisk .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364

Setting up a trust between the PureDisk SPA host and OpsCenterAB host ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365

Configuring PureDisk data collector ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366Collecting data from Enterprise Vault ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367

About Enterprise Vault ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368About data collected from Enterprise Vault ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368About versions supported by OpsCenter ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370Planning the Enterprise Vault data collector deployment ... . . . . . . . . . . 370About OpsCenter Agent deployment modes .... . . . . . . . . . . . . . . . . . . . . . . . . . . . 372Accessing MS SQL Server host ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373About creating a user for integrated logon .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373Configuring the OpsCenter Agent properties for integrated

logon .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375Installing MS SQL Server JDBC driver ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376Configuring Enterprise Vault data collector ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377

Collecting data from IBM Tivoli Storage Manager ... . . . . . . . . . . . . . . . . . . . . . . . . . . 378Collecting data from EMC Legato Networker ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380

Chapter 7 Managing OpsCenter views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383

About OpsCenter views .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383About view types ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385About accessing OpsCenter views .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386About view levels ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386About nodes and objects ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386

Managing views .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387Viewing OpsCenter views and their details ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387Creating views .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388Modifying views .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389Deleting views .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390Modifying view level alias ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390

Managing nodes and objects ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391

Contents12

Adding nodes to a view .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391Modifying node details ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392Deleting nodes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392Adding objects to a view node .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392Deleting objects from a view node .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393Working with view filters ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394

Chapter 8 Monitoring NetBackup using SymantecOpsCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399

About the Monitor views .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399Controlling the scope of Monitor views .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400

About timeframe selection .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400Monitoring NetBackup using the Overview subtab .... . . . . . . . . . . . . . . . . . . . . . . . . 401

Viewing the Job Summary by State section .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402Viewing the Media Summary by Status section .... . . . . . . . . . . . . . . . . . . . . . . 402About Top 7 Job Error Log Summary section .... . . . . . . . . . . . . . . . . . . . . . . . . . 403Viewing the Services Summary section .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403Viewing the Master Server Summary section .... . . . . . . . . . . . . . . . . . . . . . . . . . 404Viewing the Job Summary by Exit Status section .... . . . . . . . . . . . . . . . . . . . . 405Viewing the Drive Summary by Status section .... . . . . . . . . . . . . . . . . . . . . . . . 406About Top 7 Policies by Failed Jobs section .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406Viewing the Alert Summary by Severity section .... . . . . . . . . . . . . . . . . . . . . . 407

Monitoring NetBackup jobs ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407Using the List View for monitoring jobs ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408Using the Summary View for monitoring jobs ... . . . . . . . . . . . . . . . . . . . . . . . . . 416Using the Hierarchical View for monitoring jobs ... . . . . . . . . . . . . . . . . . . . . . 421

Monitoring NetBackup services ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426Filtering on NetBackup service type .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427Controlling NetBackup services ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428

Monitoring NetBackup policies ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429Using the List View for monitoring NetBackup policies ... . . . . . . . . . . . . . 430Using the Summary View for monitoring policies ... . . . . . . . . . . . . . . . . . . . . 436

Monitoring NetBackup media ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437Using the List View for monitoring NetBackup media ... . . . . . . . . . . . . . . . 438Using the Summary View for monitoring NetBackup media ... . . . . . . 443Using the Hierarchical View by Volume Pool for monitoring

media ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444Using the Hierarchical View by Volume Group for monitoring

media ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445Monitoring NetBackup devices ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447

Using the List View for monitoring drives ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448Using the Summary view to monitor drives ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452

13Contents

Monitoring NetBackup disk pools ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453Monitoring NetBackup hosts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454

Monitoring NetBackup master servers ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455Monitoring NetBackup media servers ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456Monitoring NetBackup clients ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457

Monitoring NetBackup alerts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458Using the List View for monitoring NetBackup alerts ... . . . . . . . . . . . . . . . 459Using the Summary View for monitoring NetBackup alerts ... . . . . . . . 464

Chapter 9 Managing NetBackup using SymantecOpsCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467

About the Manage views .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467Controlling the scope of Manage views .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468Managing alert policies ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468

About OpsCenter alert policies ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470Viewing the details for a single alert policy ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471Filtering on type of alert policy ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471Creating (or changing) an alert policy ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472Managing an alert policy ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485Viewing the alerts associated with an alert policy ... . . . . . . . . . . . . . . . . . . . . 486

Managing NetBackup storage .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486Managing Storage Units ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486Managing Storage Unit Groups .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488Managing storage lifecycle policy ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489

Managing NetBackup devices ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491Managing drives ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492Managing robots ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495Managing disk pools ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497Managing SAN clients ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499Managing Fibre Transport (FT) servers ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501

Chapter 10 Guided Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503

About Guided Recovery .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503Setting up for cloning .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504Pre-operation checks ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504Performing a cloning operation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505Select Master Server screen .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507Select Source Database screen .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507Select Control File Backup screen .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507Destination host and login screen .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508Destination Parameters screen .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509Selection summary screen .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509

Contents14

Pre-clone check screen .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510Job Details screen .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510Post-clone operations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510Troubleshooting Guided Recovery .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511

Troubleshooting files for metadata collection operations at thetime of the backup .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511

Troubleshooting files for Guided Recovery validationoperations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511

Troubleshooting files for Guided Recovery cloningoperations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512

Chapter 11 Understanding and configuring OpsCenteralerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513

About using SNMP with OpsCenter ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513About SNMP .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513About SNMP versions .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514About SNMP versions supported in OpsCenter ... . . . . . . . . . . . . . . . . . . . . . . . . 514About the Management Information Base (MIB) and OpsCenter

support ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515Configuring the SNMP trap community name for

OpsCenter ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530Configuring the SNMP version for sending SNMP traps .... . . . . . . . . . . . 531About customizing alert settings ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532Frequently asked SNMP questions .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533

About managing OpsCenter alerts using Microsoft System CenterOperations Manager 2007 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533

About managing OpsCenter alerts using HP OpenView Network NodeManager 7.50/7.51 on Windows .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534

Chapter 12 Reporting in OpsCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535

About OpsCenter reports ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535About the OpsCenter reports UI ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536About report creation wizards ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537About Report Templates ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537About changes in the reporting interface in OpsCenter

7.0.1 ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538About custom reports ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548About custom SQL query .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548

Working with Report Templates ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548About report filters ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 550Creating a report using a Report Template ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 550

Managing reports ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 550

15Contents

Saving a report ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551Exporting a report ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553Emailing a report ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554

Creating a custom report ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555About report conditions ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555

Creating a report using SQL query .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556Managing My Reports ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557

Creating a report using My Reports tab .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557Deleting a saved report ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557Viewing a saved report ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557Editing a saved report ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558Export a saved report ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560Email a saved report ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560

Managing My Dashboard .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561Adding reports to a dashboard .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561Modifying a dashboard section .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562Deleting a dashboard section .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562Emailing dashboard sections .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563Refreshing My Dashboard .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563

Managing folders ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563Adding a folder ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563Editing a folder ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564Deleting folders ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565Deleting reports from a folder ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565

About schedules ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565Managing report schedules ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566

Viewing report schedule details ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566Creating a report schedule ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568Editing a report schedule ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571Deleting a report schedule ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571

Managing time schedules ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572Viewing time schedule details ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572Creating a time schedule ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572Editing a time schedule ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573Deleting a time schedule ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574

About Report Templates descriptions .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574About Enterprise Vault Archiving reports ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575About Backup reports ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577About Catalog reports ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592About Chargeback reports ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592About Client reports ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593About Disk and Tape Device Activity reports ... . . . . . . . . . . . . . . . . . . . . . . . . . . 599About Media reports ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 602

Contents16

About Performance reports ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605About Policy reports ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 608About Restore reports ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610

Appendix A Additional information on PureDisk datacollection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613

About AT configuration scenarios specific to PureDisk backupproduct ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613Scenario 1: Common Root Broker ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614Scenario 2: Different Root Brokers ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615

Setting up a trust between the OpsCenter AB host and PureDisk SPAhost ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617

Appendix B Attributes of NetBackup data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619

About backup data attributes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619

Appendix C Man pages for CLIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 651

changedbpassword .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652changeVxATProperties ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654configurePorts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655dbbackup .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 656dbdefrag .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657opsadmin .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 658opsCenterAgentSupport ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660opsCenterSupport ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 661runstoredquery .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 664startagent ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 665startdb .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 666startgui ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 667startserver ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 668stopagent ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669stopdb .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 670stopgui ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671stopserver ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 672

Symantec OpsCenter Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675

17Contents

Contents18

Getting started usingSymantec OpsCenter

This chapter includes the following topics:

■ About Symantec OpsCenter

■ About what's new in Symantec OpsCenter 7.0.1

■ About OpsCenter components

■ About using the OpsCenter console

■ About starting the OpsCenter console

■ About OpsCenter console components

■ About quickly performing common tasks in OpsCenter

■ About using Web browser bookmarks

■ About OpsCenter documentation

About Symantec OpsCenterSymantec OpsCenter is a Web-based software application that helps organizationsby providing visibility into their data protection environment. By using SymantecOpsCenter, you can track the effectiveness of data backup and archive operationsby generating comprehensive reports.

OpsCenter is a convergence of NetBackup Operations Manager (NOM) and VeritasBackup Reporter (VBR) and is available in the following two versions:

1Chapter

This OpsCenter version does not require any license.

Symantec OpsCenter provides single deployment configuration and userinterface for monitoring, alerting, and reporting functionality. Thesefeatures were previously available in NOM and VBR.

SymantecOpsCenter

This is the licensed version of OpsCenter.

In addition to the features available in the unlicensed OpsCenter version,Analytics offers report customization, chargeback reporting and supportfor third-party data protection products. These features were availablein VBR.

SymantecOpsCenterAnalytics

Note: OpsCenter 7.0 supports upgrade from NOM and VBR.

For details on OpsCenter upgrade from NOM and VBR and data migration, referto the Installing Symantec OpsCenter 7.0 chapter.

About Symantec OpsCenter functionsThe unlicensed version of OpsCenter is called Symantec OpsCenter.

Symantec OpsCenter can perform the following functions:

■ Monitor NetBackup setups

■ Manage or administer NetBackup setupsNote that OpsCenter can only monitor and manage NetBackup. It cannotmonitor or manage other products like Symantec NetBackup PureDisk,Symantec Enterprise Vault etc.

■ Generate alerts depending on conditions that you have defined

■ Provide operational reporting on the following Symantec products:

■ Symantec NetBackup

■ Symantec NetBackup PureDisk

■ Symantec Backup Exec

■ Symantec Enterprise Vault

About Symantec OpsCenter Analytics functionsThe licensed version of OpsCenter is called Symantec OpsCenter Analytics.

Symantec OpsCenter Analytics can perform the following functions:

■ Monitor NetBackup setups

Getting started using Symantec OpsCenterAbout Symantec OpsCenter

20

■ Manage or administer NetBackup setupsSee “ About monitoring and managing NetBackup” on page 22.Note that Symantec OpsCenter Analytics can only monitor and manageNetBackup. It cannot monitor or manage other products like SymantecNetBackup PureDisk, Symantec Enterprise Vault, Symantec Backup Exec etc.

■ Generate alerts depending on conditions that you have definedSee “About alerting in OpsCenter” on page 22.

■ Create and customize views using Java View Builder

■ Provide operational and business-level reporting on the following Symantecand third-party products:





■ EMC Legato Networker

■ IBM Tivoli Storage Manager

■ Provide chargeback, custom, and custom SQL reports

Symantec OpsCenter Analytics displays customizable, multi-level views of backupand archive resources and customizable reports for tracking service usage andexpenditures. It also contains tools for defining cost metrics and chargebackformulas or handling alerts.

A wide range of audiences can benefit from the reporting and managementcapabilities of Symantec OpsCenter Analytics. The audiences include IT(Information Technology) managers, application owners, IT finance teams, externalcompliance auditors, legal teams, line-of-business managers, external customers,IT architects, and capacity planning teams.

The primary objectives of Symantec OpsCenter Analytics are as follows:

■ Help organizations assess their compliance with business standards by allowingthem to accomplish the following:

■ Help organizations to establish the service level agreements by reportingon them

■ Report to legal department, auditors, IT managers, and administrators

■ Verify compliance with internal as well as external business-levelregulations

■ Identify risks in terms of shortfall of backup resources

21Getting started using Symantec OpsCenterAbout Symantec OpsCenter

■ Assess recovery of clients and applications

■ Assist organizations in effective business planning by enabling them to do thefollowing:

■ Estimate backup resources required in the future, with the help of backuptrend analysis

■ Calculate the cost of data protection management and chargeback tocustomers and business units

Note: You can generate cost reports only for backup data. Cost reports forarchive data are not available.

About monitoring and managing NetBackupOpsCenter can manage and monitor NetBackup master and media servers, clients,and policies. It can manage up to 100 NetBackup master servers distributed acrossmultiple locations. It does not require you to separately log on to each NetBackupmaster or media server.

OpsCenter lets you view the operational status and health of your distributed dataprotection environment.

OpsCenter focuses on how to maintain your backup environment after youcomplete the NetBackup configuration. You need to use the NetBackupAdministration console and command-line interfaces for core NetBackupadministrative functions such as configuring media, storage units, and policies.

About alerting in OpsCenterOpsCenter provides a policy-based alert system, which monitors and notifies youbefore serious problems happen to your backup environment. You can usepredefined alert conditions to create alert policies to monitor typical issues orthresholds within NetBackup or other products. You can send an email or SNMPnotification in response to an actual alert, which lets administrators focus onother job responsibilities. They no longer need to be logged in to a terminal tomonitor systems continuously.

See “Managing alert policies” on page 468.

About reporting in Symantec OpsCenter AnalyticsThis section states the benefits that you can get from the Symantec OpsCenterAnalytics reports.

Getting started using Symantec OpsCenterAbout Symantec OpsCenter

22

See “About OpsCenter reports” on page 535.

About compliance reportingOpsCenter Analytics helps organizations evaluate their compliance with internaland external business standards by providing accurate and customizable reports.By using internal compliance reports, you can measure performance of the systemagainst service level agreement (SLA). The results are then used to optimize dataprotection management. The reports, such as history or trend analysis, ensureyour compliance with SLA. By using these reports, you can track the usage ofbackup resources and identify the risks involved. For example, you can generatea report that anticipates a shortfall of resources in the future based on the currentbackup trend. This report is then used to determine the time required to purchasenew tape drives, master servers, or media servers.

External compliance reports help you follow the policies laid down by variousregulatory bodies that are related to federal, healthcare, internal processes, andothers. These policies include Sarbanes-Oxley act (SOX) and Health InsurancePortability and Accountability Act (HIPAA).

In addition to tracking the backup or archive information, OpsCenter reportsensure recovery of key information assets. The reports can help you ensure thatthe data recovery meets the recovery-time and recovery-point objectives.

OpsCenter can generate reports filtered by views. A view shows a set of enterpriseassets (hosts or file systems) organized in logical groups. For example, you cancreate views to display assets according to their locations in the organization, theline of business they represent, or the applications that are installed. OpsCentercan generate reports according to views created. These reports help you identifylocations or departments containing assets with critical data. These reports arethen used in resource planning.

About business planningOpsCenter Analytics is a management tool that helps you optimize your dataprotection environment with effective business planning. It delivers backupservices to organizations, which include reporting on backup and recovery trendsand managing data centers. This product supports a wide range of backup andrecovery solutions including Symantec’s NetBackup and BackupExec. It seamlesslyintegrates with Symantec’s as well as third-party backup products and providesconsistent reporting across them. It can collect data from the following targetproducts:


■ Symantec BackupExec

23Getting started using Symantec OpsCenterAbout Symantec OpsCenter





OpsCenter’s ability to forecast backup resource requirements helps data centerexecutives to decide whether to maintain the existing resources or add newcapacity. The detailed, drill-down OpsCenter reports help you determine theapplications, databases, or business departments that are the heaviest consumersof backup resources. For example, in an environment running 20 instances ofOracle applications, you can generate a report showing resource consumption bydepartment, server, or location. Depending on this information, organizationscan provide appropriate resource planning in advance.

Symantec OpsCenter Analytics offers you a set of chargeback reports that detailbackup services expenditures. By using these reports, you can track the backupand recovery usage and the associated cost. By using the chargeback function,you can define pricing models for backup service delivery and allocate costs tocustomers based on these models. For example, you can create a formula thatdetermines charges based on kilobytes of backed up data over a period of time.Using this chargeback data, you can then present itemized invoices to internalcustomers, export chargeback tables to third-party billing systems, or use thedata to analyze and justify expenditures.

Note:You can generate cost reports only for backup data. Cost reports for archivedata are not available.

About reporting on archive dataEnterprise Vault Archiving report category contains a number of reports that aregenerated based on the archive data collected from Enterprise Vault. You canreport on the number of messages that are archived across mailboxes, the size ofthese messages before and after the archive operation.

About what's new in Symantec OpsCenter 7.0.1OpsCenter 7.0.1 offers the following enhancements or new functions, which werenot a part of OpsCenter 7.0.

■ OpsCenter Server 7.0.1 can be installed on AIX 5.3 and 6.1.See “About platforms supported by OpsCenter 7.0.1” on page 78.See “Installing and uninstalling OpsCenter 7.0.1 on AIX” on page 99.

Getting started using Symantec OpsCenterAbout what's new in Symantec OpsCenter 7.0.1

24

■ OpsCenter 7.0.1 can monitor and manage all NetBackup master server versionsbetween 6.0 MP7 and 7.0.1.OpsCenter 7.0.1 also supports data collection from Backup Exec 2010, SymantecNetBackup PureDisk 6.6.0.1, 6.6.0.2, and 6.6.0.3.See “About backup and archiving products supported by OpsCenter 7.0.1”on page 81.

■ A new alert condition that is called Incomplete Job has been introduced inOpsCenter 7.0.1. When you create an alert policy based on the IncompleteJobalert condition, an alert is generated when a job of a specified type of thespecified policy or client moves to an Incomplete state. For example when youcreate the alert policy based on Incomplete Job alert condition, you receivean alert when a backup job moves to an Incomplete state.More details about alert conditions are available.See “Creating (or changing) an alert policy” on page 472.

■ A new Alert Summary pane has been added to the OpsCenter console. TheAlertSummary pane provides a visual summary of the critical, major, warning,and informational alerts for the NetBackup master servers to which you areconnected. This pane is available in the Monitor and Manage views of theOpsCenter console. The number of alerts that are shown in this pane is basedon your selection in the View pane. You can click on the alert counts of thecorresponding alert category to view details about the alerts.More details about using the Alert Summary pane are available.See “Using the Alert Summary pane” on page 64.

■ A new option called Allow Multiple Selection In View Pane (referredhenceforth as multiple selection option) has been added underSettings>UserPreferences > General view in the OpsCenter console. This option is selectedby default. When this option is checked, you can select multiple nodes or viewobjects in the View pane.When you uncheck the multiple-selection option, you can make selections inthe View pane in a similar manner as NetBackup Operations Manager (NOM).This means that you can only select a single node or view object from the Viewpane at a given time. Each node or a view object is displayed as a link in theView pane. You can click a node or a view object to view data for the respectivenode or view object. For example, you can click a master server in the Viewpane to view data for the specific master server. When the multiple selectionoption is unchecked, a Group Component Summary table is displayed whenyou click Monitor > Jobs and select Summary View from the drop-down list.The Group Component Summary table was also displayed in NOM earlier.More details about using the multiple selection option are available.See “About making multiple or single-click selections in the View pane”on page 60.

25Getting started using Symantec OpsCenterAbout what's new in Symantec OpsCenter 7.0.1

See “About the Group Component Summary table” on page 419.

■ Many usability changes have been introduced in OpsCenter 7.0.1 in thereporting user interface.The following section lists the differences between the reporting user interfacesin OpsCenter 7.0 and 7.0.1, such as locations and nomenclature of reports.See “About changes in the reporting interface in OpsCenter 7.0.1” on page 538.

■ Some enhancements have been made to the deduplication reports. Thededuplication reports can be accessed when you click Reports > ReportTemplates > Backup > Deduplication in the OpsCenter console.The following enhancements have been made to the deduplication reports:

This report shows only deduplication jobs.The default Report On parameter for thisreport is MasterServer. This report is nowavailable in a line-chart format.

Deduplication > Deduplication Size Factor> Historical

This report shows only deduplication jobs.The default Report On parameter for thisreport is Master Server.

Deduplication > Deduplication Size Factor> Rankings

This report shows only deduplication jobs.The default Report On parameter for thisreport is All Master Servers.

Deduplication > Pre vs. Post DeduplicationSize


Deduplication > Deduplication SizeSavings > Historical


Deduplication > Deduplication SizeSavings > Rankings

See “About Backup reports” on page 577.

■ A new option that is called 'None’ has been added in the Select View Namedrop-down list of the Report Wizard. You can see this option when you createor edit a report and specify the views that can be associated with the reportfrom the Filters section of the Select Parameters page in the Report Wizard.Select the ‘None’ option from the Select View Name drop-down list if you donot want a specific view to be associated with the report.

■ A few changes have been made to the Monitor>Devices>Drives and Manage> Devices > Drive views in the OpsCenter console. The Monitor > Devices >Drive view shows the current drive status information. For 7.0.1 master servers,the List View and the Summary View (under Monitor > Devices > Drives) donot show a drive that is unreachable or disabled.

Getting started using Symantec OpsCenterAbout what's new in Symantec OpsCenter 7.0.1

26

The Manage > Devices > Drive view, on the other hand, shows informationabout all the drives and also includes disabled or unreachable drives.See “Monitoring NetBackup devices” on page 447.See “Managing drives” on page 492.

■ With OpsCenter 7.0.1, running the Support script to collect troubleshootingdata for the OpsCenter Server does not affect any OpsCenter service or process.You can now use OpsCenter and also run the Support script in the background.See “Gathering troubleshooting data with the support script” on page 283.

About OpsCenter componentsThis section describes the following OpsCenter components:

■ About the OpsCenter Server

■ About the OpsCenter Agent

■ About the OpsCenter Java View Builder

About the OpsCenter ServerOpsCenter Server, the core of the architecture, is a Web application that normalizesbackup / archive data collected from various applications. This normalized datais used for reporting on backup related information.

OpsCenter Server is supported on Windows and UNIX platforms.

Note: You must install OpsCenter Server, Agent, and ViewBuilder of the sameversions. For example, Server 7.0.1 is compatible only with Agent 7.0.1 andViewBuilder 7.0.1.

The OpsCenter Server comprises the following components:

Sybase SA (SQL Anywhere) database management system containing datarelated to backup /archive service usage and expenditure, cost metrics andchargeback formulas, and alerts.

OpsCenter database

A set of common authentication runtime libraries and processes that enableusers to log on once to access multiple products.

AT validates identities based on external name spaces like Active Directoryor other LDAP servers, UNIX identities based on password files, NIS/NISplusrepositories or any identities that can be authenticated through PAM. Italso provides a private user repository for service identities.

Symantec Product AuthenticationService (AT)

27Getting started using Symantec OpsCenterAbout OpsCenter components

Component that provides policy-based alert management, includingnotification, custom actions, and SNMP management capabilities.

Alert Manager

A common Web server (that uses Java Server Pages) and a JRE to serve theOpsCenter console.

Symantec Web Server and JavaRuntime Environment (JRE)

A common Veritas Licensing Module and API used to add, change, andremove Veritas product license keys.

Veritas Licensing Manager

A common component that uses socket passing to reduce the number ofports required to be open across a firewall. Symantec Private BranchExchange uses a paradigm similar to that of a telephone switchboard inwhich calls placed to a switchboard are redirected to a known extension.In the PBX exchange, client connections that are sent to the exchange’sport are redirected to an extension associated with the OpsCenter Server.

Symantec Private Branch Exchange

Figure 1-1 shows the architecture of the OpsCenter Server.

Getting started using Symantec OpsCenterAbout OpsCenter components

28

Figure 1-1 OpsCenter Server architecture

OpsCenter Server

AlertService

ReportingService

View BuilderService

LicensingService

SecurityService

SymantecProduct

AuthenticationService (AT)CORBA

Service

Database Access Layer

OpsCenterDatabase

(Sybase DBMS)Server Communication Layer

SymantecBackup Exec

OpsCenter Agent

Symantec NetBackup

SymantecEnterprise Vault

EMC LegatoNetworker

IBM TSM

View Builder Console OpsCenter Console

OpsCenter Web Server

NBSLCommunication

(CORBA)

CLI

SymantecPureDisk(Web

Services)

About the OpsCenter databaseOpsCenter uses Sybase SQL Anywhere 11 (Sybase 11) database managementsystem as a repository for the backup or archive data, such as backup serviceusage and expenditure reports, cost metrics, chargeback formulae, and alerts.


OpsCenter uses a Sybase SQL Anywhere 11 (Sybase 11) database installation thatis separate from the NetBackup database.

Except for a very small number of system settings, all information that is in theWeb UI is contained in the OpsCenter database, which consists of a singlecross-platform database file.

The OpsCenter database is completely embedded and requires no additionalinstallation steps. The Sybase database is also self tuning and does not require adatabase administrator to maintain it.

OpsCenter 7.0 supports upgrade from NOM and VBR.

About the Symantec Product Authentication ServiceThe OpsCenter Server relies on Symantec Product Authentication Service (AT)for user authentication for connections between, OpsCenter Server, Agent, andJava View Builder.

The Symantec Product Authentication Service is referred to as AT.

Symantec Product Authentication Service is a shared component and is used to:

■ Authenticate users to the OpsCenter console based on external authenticationsystems such as Active Directory, NIS, NIS+, LDAP and even standard unixpassword.

■ Provide for a secure transport of data between OpsCenter Agent's and theOpsCenter server.

■ Enable trust between OpsCenter and other Symantec products that also useAT.

Note: For more details on AT, refer to the ICS documentation that is shipped withthe NetBackup documentation set.

When the Symantec Product Authentication Service library authenticates a userfor OpsCenter, it returns a credential that OpsCenter passes along whencross-linking to other Symantec products such as NetBackup Operations Manager.The Web credential provides a limited form of user authentication so that productsdo not prompt the user to log on again.

About the OpsCenter AgentThe OpsCenter Agent collects data from various Symantec and third-party backup/ archiving products. These products can reside on the OpsCenter Agent host oron remote hosts. The OpsCenter Agent relies on the Java Runtime Environment


30

(JRE) to perform its functions. The OpsCenter Agent also requires embedded AT(Symantec Product Authentication Service) to authenticate itself with theOpsCenter Server. Both JRE and AT libraries are installed automatically with theAgent installation.

OpsCenter Agent is supported on Windows and Solaris platforms.


OpsCenter formats the information collected from the following target productsand displays it through the OpsCenter console:


Note: If you want to collect image, error log, or scheduled job data fromNetBackup master server of versions older than 7.0, you need to have OpsCenterAgent installed and configured.

■ Symantec Backup Exec (Windows only)

■ Symantec Enterprise Vault (Windows only)



OpsCenter server collects NetBackup data using NBSL in the following scenarios:

■ If you want to collect tape drive Information, media, policy and schedule, job,or skipped file data from a NetBackup master server of any supported version

■ If you want to collect any data type from NetBackup 7.0 and later masterservers

The OpsCenter Agent can reside on the same host as the OpsCenter server, or canbe installed on a remote host. All OpsCenter data collectors are configured onevery Agent. Configure and run only these data collectors for the target productthat you want to monitor or report on.

A number of combinations of OpsCenter Agent and Server installations arepossible. For example, you can install an Agent on the OpsCenter Server host andconfigure the NetBackup data collector to collect data from a remote NetBackupmaster server. Alternatively, you can install an agent on the NetBackup masterserver host and configure the NetBackup data collector to collect data from thelocal NetBackup master server.


Note: Legato data collector does not support remote data collection. Therefore,the agent must be installed on the Legato server host.

The core of the OpsCenter Agent is a Java virtual machine (JVM) in which you rundifferent data collectors. The OpsCenter Agent communicates with the Server,schedules backup / archive data collection data types, and receives commandsthrough the CORBA API.

As the OpsCenter Server relies on Symantec Product Authentication Service toauthenticate OpsCenter agent - server connections, the Symantec ProductAuthentication Service client libraries reside on the agent host.

The OpsCenter Agent comprises Scheduler, CORBA Client/Server, and datacollectors that collect backup data from all available backup application. TheScheduler and CORBA form the agent core.

These parts of the agent are described in the following topics:

About the scheduler

About the CORBA Client/Server

About data collectors

About the schedulerThe scheduler performs three basic functions for the OpsCenter Agent:

■ Checks the data collection schedules of all running data collectors and queuesthem.

■ Sends periodic heartbeat messages to the OpsCenter server to ensure thereliability of communications between the agent and the server.

■ Monitors modifications made to the agent configuration using the OpsCenterconsole, which are stored on the OpsCenter server.

About the CORBA Client/ServerThe OpsCenter Agent implements a CORBA server that listens on a configurableport (default 7806) that allows the OpsCenter console to get the runtime statusof the Agent. When you send a request to get the Agent status through theOpsCenter UI, the OpsCenter Server send the request to CORBA Server to receivethe requested information.

The Agent behaves as a CORBA client when sending data or alerts to the OpsCenterServer.


32

About data collectorsThe data collectors convert the data specific to backup or archive products intoa format that can be used by the OpsCenter Server. Each data collector mustconform to an interface that defines its interaction with the OpsCenter Agent.The data collector is implemented in a way that suits the underlying product.

Data collector configurations consist of general parameters (such as logconfigurations and data collection event definitions, which are shared by all datacollectors) and product-specific values.

You need to configure a data collector on the OpsCenter Agent host that collectsdata from a backup or archive product host.

About Agent configuration and loggingAgent configuration settings are stored in the OpsCenter database. The OpsCenterAgent also caches the latest version of the configuration settings in theagent.conffile. The agent compares the local agent.conf file with the one stored in thedatabase when the agent process is started. If the agent process has already started,any changes made to the local agent.conf file do not take place until the agentis restarted.

Note: You should not modify the agent.conf file. You should change the agentconfiguration settings using the OpsCenter Agent Configuration UI.

The changes that you have made to the agent configuration settings using theOpsCenter UI or console are reflected after the next heartbeat.

A heartbeat is a request that the OpsCenter Agent sends to the OpsCenter Serverto check for any new changes in the configuration settings. By default, a heartbeatis sent every minute.

Logging for the agent core and individual data collector is administered in thesame fashion but written to different log files.

About the OpsCenter Java View BuilderThe OpsCenter Java View Builder is an application in which an administratorcreates, modifies, and manages access to the OpsCenter views that users see inthe console.

Note: To create or customize views using Java View Builder, you need to installthe licensed version of OpsCenter called Symantec OpsCenter Analytics.


The Java View Builder relies on the AT client libraries which is installedautomatically to communicate properly with the OpsCenter Server. To use theJava View Builder, you need to provide login credentials as you do while loggingonto the OpsCenter console.

See “Logging on to the Symantec OpsCenter console” on page 44.

When you run the Java View Builder exe, it is directly connected to the OpsCenterServer. The View Builder fetches the existing object view definitions fromOpsCenter database and displays them in the OpsCenter console. Actionsperformed using the View Builder console are then stored in the OpsCenterdatabase.


About using the OpsCenter consoleThe following sections cover the basics of how to access and use OpsCenter. Theyinclude how to log on and log off and how the console works.

For information on how to understand and use the various OpsCenter views andrelated tasks, see the OpsCenter online Help. Context-sensitive help is availablefor all console views, task dialog boxes, and wizard task screens.

To access the online Help , use the help option in most dialog boxes and wizardscreens. You can also use the help option on the title bar of OpsCenter views.

The OpsCenter online documentation assumes that the user has a good workingknowledge of NetBackup and its concepts and components.

Portions of the online Help may refer the user to other NetBackup documentationfor descriptions of NetBackup fields and components.

The following NetBackup documents are referenced in the OpsCenter online Help:

■ NetBackup Administration Console Help

■ NetBackup Administrator’s Guide for Windows, Volume I

■ NetBackup Administrator’s Guide for UNIX and Linux, Volume I

■ NetBackup Troubleshooting Guide for UNIX, Windows, and Linux

Getting started using Symantec OpsCenterAbout using the OpsCenter console

34

About starting the OpsCenter consoleThe OpsCenter server is the focal point for centralized management of theNetBackup servers (release 6.0 MP7 and greater) in your backup environment.

When you install Symantec OpsCenter, you select the computer that serves asthe OpsCenter server. When you start the OpsCenter console to manage andmonitor your NetBackup environment, you open a connection to the OpsCenterWeb GUI.

About Web browser considerationsConsider the following recommendations and requirements for the Web browserto be able to access the OpsCenter console.

The following requirements and recommendations should be considered for theWeb browser:

■ The OpsCenter console uses pop-up menus. If you use pop-up blockers withyour Web browser, some of these menus may not display properly. You mustdisable pop-up blocking or add the OpsCenter Web address to the list ofacceptable sites in your browser.

■ The Web browser should have active scripting (ActiveX and JavaScript) enabled.

■ Ensure that the character encoding for the browser is Unicode (UTF 8) beforeyou access the OpsCenter console.Open the Internet Explorer browser and select View > Encoding > Unicode(UTF-8).Open the Mozilla Firefox browser and select View > Character Encoding >Unicode (UTF 8).

■ On some server systems, you may see a blank page when you try to accessOpsCenter using Internet Explorer 7.0 and above versions. This issue is causeddue to high security level in server systems. If you encounter this issue, openInternet Explorer and click Tools > Internet Options. Click the Security taband select 'Internet' icon as the zone. Click Custom Level.... In the SecuritySettings dialog box, browse to Miscellaneous > Allow META REFRESH andselect Enable. Click Yes to confirm that you want to change the security settingsfor the zone, and then click OK.

Note: In case you do not want to change your security settings, you mustmanually append /opscenter to the OpsCenter URL. This must be done everytime you access OpsCenter and face this issue.

35Getting started using Symantec OpsCenterAbout starting the OpsCenter console

■ On some server-class systems, an enhanced security configuration can causesome pages to not display properly in Internet Explorer. If you encounter thisissue, add the OpsCenter URL to the Trusted-sites list and lower the securitysetting. To resolve this issue, open Internet Explorer and select Tools>InternetOptions > Security to configure the Trusted-sites list and lower the securitylevel.

■ If you use Internet Explorer 8.0 to access the OpsCenter console, securitycertificate warnings appear when you access a pop-up menu. Select Continueto thiswebsite (not recommended) to open the pop-up menu. Once you selectthis option, the security certificate warnings do not appear on the pop-upmenus.

■ The Web browser cache must be cleared.

About Web browsers supported by OpsCenterThe OpsCenter user interface (the OpsCenter console) is supported with thefollowing Web browsers.

Table 1-1 lists the Web browsers that OpsCenter supports.

Table 1-1 Web browsers supported by OpsCenter

NotesSupported VersionsWeb browser

IE 6.0 may display a security alertdialog box when you accessOpsCenter.

See “Disabling the security alertdialog box in IE 6.0” on page 37.

IE 7.0 and later versions maydisplay a security certificatewarning page when you accessOpsCenter.

See “Disabling security certificatewarnings permanently frombrowsers” on page 39.

6.x, 7.x, 8.0Microsoft InternetExplorer

Mozilla Firefox may display anUntrusted Connection page whenyou access OpsCenter.

See “Disabling the UntrustedConnection page in Mozilla Firefox”on page 38.

3.0, 3.5Mozilla Firefox

Getting started using Symantec OpsCenterAbout starting the OpsCenter console

36

About accessing the OpsCenter consoleBefore accessing the OpsCenter console, review the following section thoroughly.

See “About Web browser considerations” on page 35.

On a system that has a network connection to the OpsCenter server, start thesystem's Web browser.

In the Web browser address bar, enter the following:http://<host.domain>/opscenter

host.domain is the fully qualified domain name of the OpsCenter server and canalso be an IP address.

Note: By default, OpsCenter tries to run on port 80 (HTTP). If port 80 is notavailable, OpsCenter can use a different port. To know the HTTP and HTTPS portthat OpsCenter uses, run the configurePorts utility. RunINSTALL_PATH\OpsCenter\gui\bin\goodies\configurePorts.bat -status onWindows hosts or/opt/SYMCOpsCenterWebGUI/bin/goodies/configurePorts.sh-status on UNIX hosts. For example, if OpsCenter uses HTTP port 8181, then usehttp://<host.domain>:8181/opscenter.

You can also use the URL that is presented at the end of the OpsCenter serverinstallation to access OpsCenter.

You must supply logon credentials on the OpsCenter login screen. Foradministrator initial logon, the user name is admin and the password is passwordor any custom password that you chose during the installation. SelectOpsCenterUsers(vx) from the Domain drop-down list and click Log On.

See “Logging on to the Symantec OpsCenter console” on page 44.

Disabling the security alert dialog box in IE 6.0When you access OpsCenter in IE 6.0, you may see the security alert dialog box.

The following dialog box may be displayed when you access OpsCenter:


You can click Yes to proceed further. Use the following procedure to disable thisdialog box permanently.

To disable the security alert dialog box permanently

1 Click Tools > Internet Options.

2 In the Internet Options dialog box, click the Advanced tab.

3 Under Security, uncheck Warn about Invalid site certificates option.

4 Restart your browser for the changes to take effect.

Disabling the Untrusted Connection page in Mozilla FirefoxWhen you access OpsCenter in Mozilla Firefox, you may see the UntrustedConnection page.

The following page may open when you access OpsCenter:

--------------------------------------------------------------

This Connection is Untrusted

You have asked Firefox to connect

securely to <OpsCenterhost.domain>, but we can't confirm

that your connection is secure.


38

Normally, when you try to connect securely,

sites will present trusted identification to prove that you are

going to the right place. However, this site's identity can't be verified.

What Should I do?

If you usually connect to

this site without problems, this error could mean that someone is

trying to impersonate the site, and you shouldn't continue.

Technical Details

I Understand the Risks

--------------------------------------------------------------

Your choice is to either click Get me out of here which takes you to the MozillaFirefox start page, or click Add Exception (when you expand the I Understandthe Risks section) and permanently disable the page.

To disable the Untrusted Connection page permanently

1 On the Untrusted Connection page, expand I Understand the Risks sectionand click Add Exception.

2 In the Add Security Exception dialog box, click Get Certificate.

3 Ensure that the Permanently store this exception option is checked. Thisoption is checked by default.

4 Click Confirm Security Exception.

5 Restart your browser for the changes to take effect.

Disabling security certificate warnings permanently frombrowsersWhen you log on to OpsCenter console, you may see security certificate warningson Mozilla Firefox and Internet Explorer browsers. This is because when youaccess OpsCenter usinghttp://<host.domain>/opscenter, you are automaticallyredirected to HTTPS (hypertext transfer protocol Secure) which is a secure protocoland requires a certificate. In case you do not want to use HTTPS and disable thesecurity certificate warnings while accessing OpsCenter console, you can disablethe automatic redirection to HTTPS. However note that using HTTPS providesencryption and secure identification of the server.


To disable security warnings and HTTPS redirection

1 Open the web.xml configuration file in a text editor from the followinglocations:

INSTALL_PATH\OpsCenter\WebServer\conf\web.xmlFor Windows:

/opt/SYMCOpsCenterWebServer/conf/web.xmlFor UNIX:

Note: Before you proceed with rest of the steps, it is recommended that youtake a backup of the web.xml file.

2 In the web.xml file, locate the security constraint string (located towards theend of the file):

<security-constraint>

<display-name>Security Constraint</display-name>

<web-resource-collection>

<web-resource-name>Protected Area</web-resource-name>

<url-pattern>/*</url-pattern>

</web-resource-collection>

<user-data-constraint>

<transport-guarantee>CONFIDENTIAL</transport-guarantee>

</user-data-constraint>


40

3 Comment this portion from the web.xml file by adding  in the end. You can also add your comments inside. For example:



4 Stop the OpsCenter Web GUI service on Windows.

Select ControlPanel>AdministrativeTools>Services and restart (stop andthen start) the Symantec OpsCenter Web Server Service.

5 Restart the OpsCenter Web GUI service on UNIX. Enter the followingcommand:

/opt/SYMCOpsCenterGUI/bin/stopGUIStop service

/opt/SYMCOpsCenterGUI/bin/startGUIStart service

About possible OpsCenter console access issuesYou may see the following issues when you access the console.

Table 1-2 describes possible OpsCenter console access issues and their solution.

Table 1-2 OpsCenter console access issues, causes, and solution

SolutionCauseIssue

1 Verify that the Symantec OpsCenter Web server Service isrunning.

You can check the status of all OpsCenter processes onUNIX by entering the following command:

/opt/SYMCOpsCenterServer/bin/opsadmin.sh

monitor

2 Verify that a Web browser on the OpsCenter server canconnect to the OpsCenter console by using the followingaddress:

http://localhost:<HTTP port number>/opscenter

Note: To know the HTTP and HTTPS port that OpsCenteruses, run the configurePorts utility. RunINSTALL_PATH\OpsCenter\gui\bin\goodies\configurePorts.bat

-status on Windows hosts or/opt/SYMCOpsCenterWebGUI/bin/goodies/configurePorts.sh

-status on UNIX hosts.

The OpsCenter WebGUI (the OpsCenterconsole) is not runningor is inaccessible on thenetwork.

You cannot connect tothe Web GUI. Your Webbrowser displays thefollowing messages:"page cannot bedisplayed" or"connection wasrefused."


42

Table 1-2 OpsCenter console access issues, causes, and solution (continued)

SolutionCauseIssue

Use the following steps on Windows:

1 Locate the opscenter.war file in the following directoryto verify that the OpsCenter application is installed:

INSTALL_PATH\OpsCenter\WebServer\webapps

2 Verify that all the OpsCenter server services are running.

3 Start all the OpsCenter Server services by using thefollowing command:

INSTALL_PATH\OpsCenter\server\bin\opsadmin.bat

start

Use the following steps on UNIX:

1 Locate the opscenter.war file in the following directoryto verify that the OpsCenter application is installed:

/opt/SYMCOpsCenterGUI

2 Verify that all OpsCenter Server processes are running byusing /opt/SYMCOpsCenterServer/bin/opsadminmonitor command.

3 Start all the OpsCenter Server processes by using thefollowing commands:


start

The OpsCenter consoleapplication is notloaded.

The OpsCenter Web GUIis running, but theOpsCenter console is notavailable. Your Webbrowser displays an"HTTP STATUS 404"error.


Table 1-2 OpsCenter console access issues, causes, and solution (continued)

SolutionCauseIssue

Use the following steps to resolve this issue:

1 Open Internet Explorer . On the Tools menu, click InternetOptions.

2 Click the Security tab.

3 Under Select a Web content zone to specify its securitysettings, click the Internet, icon and then click CustomLevel.

4 In the Security Settings dialog box, browse toMiscellaneous > AllowMETAREFRESH and select Enable.

5 Click Yes to confirm that you want to change the securitysettings for the zone, and then click OK.

Note: In case you do not want to change your security setting,you must manually append/opscenter to the OpsCenter URL.This must be done every time you access OpsCenter and facethis issue.

The security level onthe server system isHigh.

You see a blank pagewhen you try to accessOpsCenter using InternetExplorer 7.0 and aboveversions.

Logging on to the Symantec OpsCenter consoleYou must supply logon credentials on the OpsCenter login screen.


44

To log on to Symantec OpsCenter console

1 Enter a user name and password, and select a domain from the Domaindrop-down list. For administrator initial logon, the user name is admin andthe password is password or any custom password that you chose during theinstallation. Select OpsCenterUsers(vx) from the Domain drop-down list.

The domains that appear in the Domain drop-down list include theOpsCenterUsers(vx) domain, domains that are migrated if you upgrade toOpsCenter from NOM or VBR, and domains of the users that are added to theOpsCenter console.

After the initial log on, you should change the user name and password. Tochange existing passwords, use Settings > User Preferences > My Profileview in the OpsCenter console.

See “Changing your password” on page 299.

2 Click Log On.

Initially, a monitoring overview of the NetBackup master servers appears.When you log off from the console, OpsCenter saves your settings andpreferences and uses these settings when you restart the console again.

Note: The first time you log on, OpsCenter uses the default language of theWeb browser. If OpsCenter does not support this language, it uses English.

After initial logon, you can specify a default language or locale from Settings>UserPreferences>General. If you do not set a default, OpsCenter uses theWeb browser language (or English).

See “Setting user preferences” on page 295.

About possible OpsCenter console logon issuesTable 1-3 describes the issues you may find when you log on to the console andtheir solution.


Table 1-3 OpsCenter console logon issues

SolutionCauseIssue

Enter a valid user name, password, anddomain.

Ensure that the Symantec ProductAuthentication Service is started andrunning properly. You can startauthentication service by running 'net startvrtsat' on Windows and'/opt/VRTSat/bin/vxatd' on UNIX.

The SymantecProductAuthenticationService cannotvalidate theuser name andpassword forthe selecteddomain.

You have a userauthentication error. Thelogin screen displays themessage "Userauthentication failed. Pleaseenter valid user name andpassword. If problem persistscontact your systemadministrator ."

Log on as the OpsCenter admin user andadd the user to the list of OpsCenter users.

The user nameand domainare valid, butthe user wasnot added tothe list of usersfor OpsCenter.

The entered user name is nota registered OpsCenter user.The login screen displays themessage "This user is notauthorized to use OpsCenter.Please contact the OpsCenterAdministrator for adding thisuser."

Start the Symantec OpsCenter ServerService and verify that it is runningproperly.

See 'Controlling OpsCenter services andprocesses' section in the Administrationchapter of Symantec OpsCenterAdministrator's Guide.

Check your network configuration. Verifyif hosts file has the correct IP address tohost name mapping. The hosts file islocated inC:\WINDOWS\system32\drivers\etc

directory on Windows.

The OpsCenterserver is notrunning.

You cannot connect to theOpsCenter server. The loginscreen displays the message"Error occurred whileconnecting to the OpsCenterServer. Please ensure thatthe server is running."


46

Table 1-3 OpsCenter console logon issues (continued)

SolutionCauseIssue

This issue mayoccur due tomany reasons.If this issueoccurs whenyou upgradefromOpsCenter 7.0to OpsCenter7.0.1, apossible reasonis the databasegetting lockedduringupgrade.

After you upgrade toOpsCenter 7.0.1 and accessthe OpsCenter console, nodomains are displayed in theDomains drop-down list. Thelogin screen displays themessage "Error occurredwhile connecting to theOpsCenter Server. Pleaseensure that the server isrunning."



SolutionCauseIssue

Use the following steps to determine if thisissue is due to database locking:

1 Browse to the following location onWindows and UNIX:

INSTALL_PATH\OpsCenter\server\db\log

/opt/SYMCOpsCenterServer/db/log

2 Open the log file nameddbManager_<date>_<hour minutesecond>_.log (likedbManager_2010_05_14_173433_.log).Ensure that you open the latest logfile (from the timestamp).

3 Search the string called "ERROR:Failed to Install database. Exit Codeis : 1" in the log file. If this string ispresent, then the issue is due todatabase locking.

Use the following resolution for Windowsand UNIX once you determine thatdatabase locking is the cause of this issue.

Use the following workaround on Windowsplatforms:

1 Open the command prompt andnavigate to the following directory:

INSTALL_PATH\Symantec\OpsCenter\server\bin

2 Run the following command tomigrate the data from 7.0 to 7.0.1database:

opspostinstall server 7.0

7.0.1 2

The number 2 is used in thiscommand to denote a non-clusteredenvironment.

3 Run the following command to restartall OpsCenter services:


48


SolutionCauseIssue

INSTALL_PATH\Symantec\OpsCenter\

server\bin\opsadmin.bat start

4 Ensure that all the OpsCenter servicesare running from the Services Panel.You can access the Services Panel byselecting Control Panel >Administrative Tools > Services.

Use the following workaround on UNIXplatforms:

1 Navigate to/opt/SYMCOpsCenterServer/bin

2 Run the following command tomigrate the data from 7.0 to 7.0.1database:

./opspostinstall server 7.0

7.0.1 2

The number 2 is used in thiscommand to denote a non-clusteredenvironment.

3 Run the following command to restartall OpsCenter processes:

/opt/SYMCOpsCenterServer/

bin/opsadmin.sh start

4 Ensure that all OpsCenter processesare running. Use the followingcommand to check the status ofOpsCenter processes:


monitor

Enter a valid user name and password.Usernameand/orpassword hasnot beenspecified.

Either the user name orpassword or both have notbeen entered. The loginscreen displays the message"Please enter valid user nameand password. "



SolutionCauseIssue

Verify that Symantec ProductAuthentication Service is running. You canstart authentication service by runningnet start vrtsat on Windows and/opt/VRTSat/bin/vxatd on UNIX.

Authenticationservice is down

Authentication service isdown "Error occurred whileconnecting to the SymantecProduct AuthenticationService (AT). Please ensurethat the AT service isrunning."

Logging out of the OpsCenter consoleWhen you log out from the console, OpsCenter saves most of the settings andchanges you make in an OpsCenter session.

To log out from Symantec OpsCenter

◆ Click Logout located on the right side of the title bar.

Configuring the OpsCenter session timeout intervalWhen left at its default value, users are automatically logged out of the OpsCenterconsole when a session is left inactive for 30 minutes. However, the session timeoutinterval can be reconfigured.

To configure the session timeout interval

1 Open the web.xml configuration file in a text editor from the followinglocations:

INSTALL_PATH\OpsCenter\WebServer\conf\web.xmlFor Windows:

/opt/SYMCOpsCenterWebServer/conf/web.xmlFor UNIX:

2 In the web.xml file, locate the session-timeout parameter:

<session-config>

<session-timeout>30</session-timeout>

</session-config>


50

3 Change the session timeout parameter value to the desired length by changingthe number encapsulated by the XML tags for session-timeout (in the exampleabove, change "30" to the desired value).

This value is set in minutes.

4 Stop the OpsCenter services. Enter the following command:

INSTALL_PATH\OpsCenter\server\bin\opsadmin.bat stopWindows

/opt/SYMCOpsCenterServer/bin/opsadmin.sh stopUNIX

5 Restart the OpsCenter services. Enter the following command:

INSTALL_PATH\OpsCenter\server\bin\opsadmin.bat startWindows

/opt/SYMCOpsCenterServer/bin/opsadmin.sh startUNIX

About possible OpsCenter console issuesTable 1-4 describes the issues you may find when you use the console.

Table 1-4 Issues when you use OpsCenter console

SolutionCauseIssue

Log on again. Aftersuccessful logon, you thenreturn to the OpsCenter viewthat you last visited.

You can also configure thesession timeout interval.

See “Configuring theOpsCenter session timeoutinterval” on page 50.

After 30 minutes ofinactivity, the OpsCenteruser automatically logs outof the console. Any attemptto use OpsCenter, displaysthe OpsCenter login screen.

Your OpsCenter consolesession times out. The loginscreen appears when you tryto change views or refreshthe current view.

Click the link in the messageand try to login again.

This error results from aninternal issue in theOpsCenter consoleapplication.

An internal error occurs inthe OpsCenter console. Anexception error messageappears in the OpsCenterconsole. You receive themessage "An unknown errorhas occurred. Click here tolog on and retry. "


Table 1-4 Issues when you use OpsCenter console (continued)

SolutionCauseIssue

Enable active scripting in theWeb browser. You mustenable it to use OpsCenter.

Active scripting is disabledin the Web browser.

You receive the message"Active scripting is requiredto use this application.Enable active scripting in thebrowser."


52


SolutionCauseIssue

An unresponsive script erroris displayed on MozillaFirefox



SolutionCauseIssue

To tell Firefox to let thescript run longer:

■ In the Location bar, typeabout:config and pressEnter.

The following warningmessage may appear:

"This might void yourwarranty!". Click I'll becareful, I promise!, tocontinue to theabout:config page.

■ In the about:config page,search for the preferencedom.max_script_run_time,and double-click on it.

■ In the Enter integer valueprompt, type 0.

Note: 0 and negativevalues imply infinitetime.

■ Press OK.

The following URLs containmore information:

http://support.mozilla.com/en-US/kb/Warning+Unresponsive+script

http://kb.mozillazine.org/Dom.max_script_run_time

With scripts now allowed torun for longer times, youmay no longer receive theprompt. If you still receivethe prompt (or if you want tosee it again), you should setthat preference back to thedefault value.

■ In the Location bar, typeabout:config and press


54







SolutionCauseIssue

Enter.

■ The about:config"This might void yourwarranty!" warningpage may appear.Click I'll be careful, Ipromise!, to continueto the about:configpage.

■ In the about:config page,search for the preferencedom.max_script_run_time.

■ Right-click on it andchoose Reset.

About OpsCenter console componentsThis section provides information on the panes and navigation features availablein the OpsCenter console. You can view the console by using a Web browser.

When you log on initially, the Monitor > Overview view appears.

The following is an example view that shows the OpsCenter console components.

When you change the settings and preferences they are saved and if you log outand log on again these settings are used.

Figure 1-2 shows the OpsCenter console components.

55Getting started using Symantec OpsCenterAbout OpsCenter console components

Figure 1-2 OpsCenter console components

Details pane

Title bar linksTabs and subtabs

Content pane

Minimizeicons

View Pane

Quick links

SymantecThreatConpane

List ViewChange TableSettings icon

Maximize icon Minimize icon

Task Pane(whole leftpane)

Table page controls

AlertSummaryPane

Table 1-5 lists the topics that describe the main elements of the console in greaterdetail.

Table 1-5 Topics covered in this section

DescriptionTopic

See “About using the links on the titlebar” on page 57.

Use the links (for example, Logout and Help)available from the title bar

See “About using tabs and subtabs”on page 58.

Overview about the tabs and subtabs available inthe console

See “About refreshing the OpsCenterconsole” on page 59.

Control the frequency that the OpsCenter consolerefreshes to reflect changes in your backupenvironment

See “Using the Task pane” on page 59.Overview about the Task pane.

See “About the View pane” on page 59.Overview about the View pane.

Getting started using Symantec OpsCenterAbout OpsCenter console components

56

Table 1-5 Topics covered in this section (continued)

DescriptionTopic

See “Using the quick links in the Taskpane” on page 64.

Overview about quick links in the task panes

See “Using the Alert Summary pane”on page 64.

Use the pane that displays a quick visual summaryof any current alerts.

See “Using the content pane”on page 65.

Use the main data display pane that OpsCenteruses

See “About the OpsCenter status bar”on page 68.

Use the status bar at the bottom of the OpsCenterconsole

See “About visual keys in the console”on page 68.

Use the visual keys that OpsCenter uses to helpyou understand displayed information

See “About using tables” on page 69.Use tables, select rows, and use filters.

About using the links on the title barOn the title bar of the OpsCenter console, the Logged in as value shows the username that is logged on to the OpsCenter server.

To adjust the screen space that is used by the tabs and subtabs, click the CustomizeTabs drop-down list. You can select the following options:

Only the selected tab and subtab are shownin a single row. Clicking the arrow next tothe selected tab displays rest of the tabs ina drop-down list. Similarly clicking the arrownext to the selected subtab displays rest ofthe subtabs in a drop-down list.

Small

The tabs and subtabs appear in two separaterows. The tabs do not have any icons abovethem.

Medium

The tabs and subtabs appear in two separaterows. The tabs have icons placed above them.

Large

Use the links available in the title bar at the top of the console for the followingtasks:

■ To know OpsCenter product version and copyright information (click About).


■ Access Symantec OpsCenter help (click Help). Context-sensitive help for allviews, wizards, and dialog boxes is available using this link.More information about online Help is available.See “About OpsCenter documentation ” on page 75.

■ Disconnect from the OpsCenter server to end your session (click Logout).See “Logging out of the OpsCenter console” on page 50.

About using tabs and subtabsTable 1-6 describes the main tabs that provide access to the major areas of theOpsCenter console.

Table 1-6 Tabs and subtabs in the OpsCenter console

DescriptionTab

Monitor the status of NetBackup jobs, services, policies, media, devices,hosts, and display and respond to any OpsCenter alerts.

Monitor

Manage alert policies, NetBackup job policies, storage units, devices.Using this tab you can also restore data.

Manage

View standard OpsCenter reports, create and run custom reports, andschedule reports.

Note: You can use custom report functionality only with a licensedOpsCenter version (OpsCenter Analytics).

Reports

Customize the OpsCenter server, add OpsCenter users, define userpreferences, add master servers, add and configure views, set up emailand SNMP recipients, view chargeback settings, etc.

Settings

Under each main tab is a series of subtabs. The contents of these subtabs varydepending on the current view and represent the views accessible from each maintab. For example, under the Monitor tab there are subtabs like Overview, Jobs,Services, Policies etc.

The data that is shown in OpsCenter views depends on what you select in the Viewpane.

More information about View pane is available.

See “About the View pane” on page 59.


58

About refreshing the OpsCenter consoleAs you use Symantec OpsCenter, the status of your backup environment is likelyto change. Devices go online and offline, OpsCenter generates alerts, media usagefluctuates, and so on. You can control when the information in the consolerefreshes to reflect the changes in your backup environment.

You can change the refresh setting from Settings > User Preferences > Generalview in the OpsCenter console.


Using the Task paneIn many views in the console, a Task pane is available. The Task pane is locatedon the left side of the console and contains the View pane, Symantec ThreatConpane, and Quick Links at the bottom.

To enlarge the Task pane

◆ Click the icon between the Task pane and the content pane. This icon is calledCollapse Task Panel. Click the icon again to show all panes.

Or

You can also drag the line separating the Task pane and the Content pane toresize the Task pane.

The minimize or maximize settings are applicable only for the current session.Also you cannot resize the Task pane from the Monitor > Overview page.

About the View paneThe View pane is a key navigation and configuration tool in Symantec OpsCenter.This pane lets you select the views to control the scope of your console views. ALLMASTER SERVERS is the default view in the View pane.

Using OpsCenter views, you can view NetBackup information for your entiremanagement domain (in the case of ALL MASTER SERVERS view), a specific viewtype, or an individual server.

You can create views from Settings > Views or by using the Java View Builder.For example, you can create a view like Geography to view details about masterservers in a particular region like Europe. You can also create client or policyviews.

More information about how to create views from Settings > Views is available.

See “About OpsCenter views ” on page 383.


See the online Symantec OpsCenter Java View Builder Help to know how you cancreate views using Java View Builder.

The View pane has the following features:

■ Is available in any OpsCenter view where you can change the view.

■ Uses unique icons and colors to convey operational states.For example, an icon with a red dashed-circle represents a managed serverthat is Not Connected. Similarly a disabled master server is shown as a graycolored icon.See “About visual keys in the console” on page 68.

■ Lets you access and change the views that you monitor or manage.As you navigate within the OpsCenter console, your view selection applies forany subsequent screens until you select a different view.Using the View pane is one of the methods you can use to determine the scopeof information that you view.See “About selecting views from the View pane when the multiple selectionoption is checked” on page 62.

Figure 1-3 shows a sample View pane in which ALL MASTER SERVERS view isselected.

Figure 1-3 View pane description

About making multiple or single-click selections in the ViewpaneYou can either make multiple or single-click selections in the View pane. TheAllow Multiple Selection In View Pane option governs how you can make selectionsin the View pane. You can find the AllowMultipleSelection InViewpane optionwhen you click Settings > User Preferences > General in the OpsCenter console.


60

You can either check or uncheck the Allow Multiple Selection In View Paneoption. You can make selections in the View pane in the following ways based onwhether you check or uncheck the multiple selection option:

When the multiple-selection option is checked, you canselect multiple nodes or view objects from the View paneat a given time. The multiple-selection option is checkedby default.

When the multiple-selection option is checked, you can seea check box next to each master server or node in the Viewpane. To view data for multiple master servers and nodes,you check the corresponding check boxes and then clickApply Selection.

Check Allow MultipleSelection In View Paneoption

When you uncheck the multiple-selection option, you canonly select a single node or view object from the View paneat a given time. You can make selections in the View panein a similar manner as NetBackup Operations Manager(NOM).

Each node or a view object is a link. You can click a node ora view object to view data for the respective node or viewobject. For example, you can click a master server in theView pane to view data for the specific master server.

Note: When you uncheck the multiple-selection option, aGroup Component Summary table is displayed when youclick Monitor > Jobs and select Summary View from thedrop-down list.

See “About the Group Component Summary table”on page 419.

Uncheck Allow MultipleSelection In View Paneoption

Figure 1-4 shows how you can check Allow Multiple Selection In View Paneoption and make multiple selections in the View pane. The Allow MultipleSelection in View Pane option is checked by default.


Figure 1-4 Making multiple selections in the View pane

You can selectmultiple masterservers by selectingthe check-box

Figure 1-5 shows how you can uncheck Allow Multiple Selection in View Paneoption and make single-click selections in the View pane.

Figure 1-5 Making single-click selections in the View pane

You canselect onlyone masterserver. Eachmasterserver is alink

About selecting views from the View pane when the multipleselection option is checkedFrom the View pane, you can select a view and a node that contains a group ofmaster servers and also specific objects. For example, you can select the defaultview ALLMASTERSERVERS. When you select a view like ALLMASTERSERVERSor a node that contains a group of master servers, all the master servers that are


62

currently in the view or node are automatically selected. In addition, the masterservers that you may add later to this view or node are also automatically selected.

You may also select only specific objects of a particular view or node. For example,you may select only a specific master server(s) under the default view ALLMASTER SERVERS. To select a specific master server, first deselect the view ornode that contains the master server and then select the master server.

You may also deselect a specific master server from a view by selecting the viewand then deselecting the specific master server. Consider a scenario where thereare two objects server A and server B in a particular view like ALL MASTERSERVERS. In case, you have selected the ALLMASTERSERVERS view and thenspecifically deselected server B , and in addition if you have selected a node thatalso contains server B, server B is not considered even though it is a part ofthe selected view or node. This is because you have specifically deselected server

B from the ALLMASTERSERVER view. When you specifically deselect a masterserver from a view, which is also part of another selected view, the deselection orexclusion is given a higher priority because of which the master server is notconsidered. For this reason, it is recommended that you do not repeat a masterserver across groups.

About the Symantec ThreatCon paneThe Symantec ThreatCon pane shows the current ThreatCon level in the OpsCenterconsole. This level is same as the ThreatCon level which is shown on the followingWeb site:

http://www.symantec.com/security_response/threatcon

The Symantec ThreatCon pane is available in the OpsCenter console on theleft-hand side.

Figure 1-6 shows the Symantec ThreatCon pane in the OpsCenter console.

Figure 1-6 Symantec ThreatCon pane in the OpsCenter console

Clicking the MoreInfo link in the SymantecThreatCon pane shows details aboutthe ThreatCon level.


http://www.symantec.com/security_response/threatcon

OpsCenter periodically polls the ThreatCon Web service and updates the datawhich is shown in the Symantec ThreatCon pane. You can also configure thispolling interval.

Symantec ThreatCon feature is enabled by default. You can also disable or enablethe Symantec ThreatCon feature.

See “Configuring Symantec ThreatCon feature in OpsCenter” on page 304.

Using the quick links in the Task paneIn many views in the console, a task pane is available. At the bottom of this pane,there are quick links to access to the most-common tasks in OpsCenter.

Table 1-7 shows the quick links available in OpsCenter and where they take youwhen you click these links.

Table 1-7 Quick links and where they point

DestinationQuick Link

Manage > Oracle CloningOracle Cloning

Manage > Alert PoliciesAlert Policies

Settings > Configuration > NetBackupNetBackup Data Collection

Settings > ViewsViews

Settings > Users > UsersUsers

To minimize the quick links

◆ Click the minimize icon (down arrow) located on top of the quick links. Onlythe icons for quick link tasks are visible when the quick links are minimized.

Click the maximize icon (up arrow) again to view the quick links.

Note:The Quick links are shown by default in a maximized state. The minimizeor maximize settings are applicable only for the current session.

Using the Alert Summary paneThe Alert Summary pane provides a visual summary of the critical, major, warning,and informational alerts for the NetBackup master servers to which you areconnected. This pane is available in Monitor and Manage views of the OpsCenter


64

console. The number of alerts that are shown in this pane is based on your selectionin the View pane.

To view outstanding alerts quickly

◆ Click any of the four available alert counts.

A filtered detail view for that alert category appears (this view is a shortcutto Monitor > Alerts).

Using the content paneWhen you initially log on to Symantec OpsCenter, the content pane displays asummary of information for all master servers in the OpsCenter console. Initially,a monitoring overview appears (Monitor > Overview).

Information in the content pane varies and is context sensitive to current selectionsin the View pane, the tabs and subtabs, and the timeframe.

To enlarge the content pane

◆ Click the icon between the task pane and the content pane. This icon is calledCollapse Task Panel. Click the icon again to show all panes.

Note:The CollapseTaskPanel icon is not available in the Monitor>Overviewpage.

Or

You can also drag the line separating the View pane and the Content pane toresize the Content pane.

The minimize or maximize settings are applicable only for the current session.Also you cannot resize the Content pane from the Monitor>Overview page.

Using the List, Summary, Hierarchical, and Details viewsMost of the OpsCenter monitor and manage views present information in threemain viewing modes: List View, Summary View, and Hierarchical View. You canview information about your NetBackup environment in any of the available views.Use the drop-down list on the top-right corner of the OpsCenter console to switchbetween these views.

Note: Not all viewing modes are available for all Monitor and Manage views. Thedrop-down list is available in the applicable views.


List ViewDrop-downlist

The Summary View presents information in a graphical format (pie charts). TheList and Hierarchical views present information in tabular formats.

For example, you can view details about all NetBackup jobs (for a master server)in a tabular format using List View on the Monitor > Jobs page. You can view asummary of all NetBackup jobs (for a master server) in the form of pie charts byusing Summary View on the Monitor > Jobs page. You can view details about allNetBackup jobs and also relationships between jobs (for a master server) in atabular format using Hierarchical View on the Monitor > Jobs page.

In addition to the above views, a Details view is also available. A details view isavailable on some of the Monitor, Manage, and Settings pages. The Details viewis shown in the following figure.


66

Details View Contents of all the columns for thespecific job ID is displayed in theDetails View.

Tabs on the Details View

Minimizeicon

Maximizeicon

The Details view presents detailed information about an entity and shows contentsof all the tabular columns (displayed as well as available) for the specific entity.For example, the Details view on the Monitor > Jobs page (List View) showsdetailed information about a specific job ID. Information in the Details view canbe viewed from tabs available in this view.

To resize the Details view

◆ Click the icon (down arrow) between the Details View and the upper part ofthe Content pane to minimize the Details View.

Click the icon (up arrow) between the Details View and the upper part of theContent pane to maximize the Details View.

Or

You can also drag the line separating the upper part of the Content pane andDetails view to resize the Details View.

The minimize or maximize settings are applicable only for the current session.


About the OpsCenter status barThe status bar at the bottom of the OpsCenter console shows a Page generatedvalue. The Pagegenerated value shows the date and time of the OpsCenter serveryou are logged on to (adjusted to match your time zone). This value updates whenthe view changes or refreshes.

More information on how to specify your time zone is available.


About visual keys in the consoleTo help you understand the information it presents, Symantec OpsCenter usesseveral visual keys. These keys include color, status icons, and tool tips.

About color codingThis topic helps you to identify and understand the colors that are used alongwith status icons.

The following colors are used along with status icons:

■ Red indicates a critical condition that may cause the system to be unable toperform an important function. Investigate critical conditions immediately.A server icon with a red dashed-circle means that the connection to themanaged server is lost (Not Connected). A reattempt to connect happens after10 minutes.

■ Green indicates a normal condition, result, or operation.

■ Blue-gray and gray often indicate enabled and disabled, or assigned andunassigned conditions respectively.

About status iconsStatus icons are also used with color coding. When OpsCenter detects a condition(for example, Connected or Not Connected) for a managed NetBackup server, job,drive, or drive path, the icon contains color coding.

These icon colors represent critical, warning, or informational conditions and letyou quickly determine the status of a particular area in your NetBackupenvironment. For example, the Monitor > Jobs view contains green icons forrunning jobs.

Unique icons also appear in the drive details view for shared drives (the NetBackupSSO option). These icons represent the shared drives that are up on all servers


68

that share the drive. Icons also appear for shared drives where the drive status ismixed (up on some servers and down on other servers that share the drive).

Table 1-8 lists the icons that are used for managed NetBackup master servers inthe View pane.

Table 1-8 Icons used for managed master servers

DescriptionIcon

A normal server icon means that the managed server is Connected.

A server icon with a red dashed-circle means that a connection to themanaged server is lost (Not Connected). A reattempt to connect happensafter 10 minutes.

A managed server icon with a line through it denotes that the server isPartially Connected. For a partially connected master server, OpsCentertries to reconnect to NBSL in every 10 minutes to collect data for thedata types for which Collection Status is Failed.

A gray colored server icon means that data collection for the managedserver was disabled by the user.

About tool tipsTool tips provide brief descriptions of the tool and the status icons that appearin OpsCenter views. A tool tip appears when you place the mouse over an icon.

About using tablesOpsCenter collects information about aspects of your NetBackup environmentand presents much of this information in tables. This section describes how tochange the tables to display the information you want to see. The following is asample table showing task icons.

Figure 1-7 shows the task options for tables.


Figure 1-7 Sample screen with task options for tables

Table page controls

Table Settings iconCreate, Edit, andDelete filter icons

Customizing tables for your needsYou can customize the tables in the following manner.

You can perform the following operations to a table:

See “Specifying which columns appear in atable” on page 71.

Add or remove columns

See “Moving a column” on page 71.Rearrange the order of the columns for yourindividual requirements

See “Choosing the number of rows thatappear per page of a table” on page 71.

Choose the number of rows and columns todisplay

See “Sorting the contents of a table column”on page 72.

Sort columns in ascending or descendingorder

See “Changing the width of a column”on page 72.

Change the widths of columns

See “Accessing multiple pages of data intables” on page 72.

Pagination

See “Selecting rows in tables” on page 72.Select rows in tables


70

The table refreshes after the operation and shows the changes you made.

For these operations, OpsCenter saves and reloads your customized settings whenyou log on to the OpsCenter server again. Each user can have different customizedtable settings.

Specifying which columns appear in a table

Use the following procedure to specify which columns appear in a table.

To specify which columns appear in a table

1 Click the Change Table Settings icon at the top-right corner of the table.

2 Initially, some OpsCenter tables do not show all available columns. To viewany of these columns, you may first have to remove one or more columnsfrom the table and then add the missing columns.

Remove columns you do not want to appear by selecting the column inSelected Columns. Then click Remove.

Add any columns that currently do not appear by selecting the column in theAvailable Columns list. Then click Add. Added columns appear as the lastcolumn in the table.

Moving a column

Use the following procedure to move columns in a table.

To move a column

1 Click the Change Table Settings icon at the top of the table.

2 Select the name of the column in Selected Columns.

3 Click Move Up to move the column to the left in the table.

Click Move Down to move the column to the right in the table.

Choosing the number of rows that appear per page of a table

Use the following procedure to choose the number of rows that appear per pagefor a table.

To choose the number of rows that appear per page for a table

1 Click the Change Table Settings icon at the top of the table.

2 Select a number from the Rows Per Page drop-down list .

3 Select Apply To All Tables if you want the Rows Per Page setting to apply toall tables in OpsCenter (includes reports).


Sorting the contents of a table column

Use the following procedure to sort the contents of a column or multiple columns.

To sort the contents of a column or multiple columns

◆ In a table, click the column name. The column sorts in ascending order bydefault.

To sort in descending order, click the column name again.

Changing the width of a column

Use the following procedure to change the width of a column.

To change the width of a column

1 Select the edge of the column heading and hold down the left mouse button.

2 Drag the edge of the column heading to the right or left.

Accessing multiple pages of data in tables

Much of the monitoring information appears in a table format. OpsCenter tablesdisplay 10 rows at one time by default. You can also change the number of rowsto be displayed in the table from the Change Table Settings icon.

When you have more data to display than can fit in a table, the table containsmultiple pages. Use the table page controls (located below the table) to help younavigate the pages.

To display the next 10 rows or to return to a previous set of rows in large tables,use the table page controls.

To go to a specific page

◆ Click the page number.

To go to the previous or the next page

◆ Click the left arrow or the right arrow.

To go to the first or the last page

◆ Click the double left arrow or the double right arrow.

Selecting rows in tables

For many tables in OpsCenter, you must select a row or rows to enable the tasks.

To select a row in a table

◆ Click the check box for that row. Click the check box again to deselect theselected row.


72

To select all rows on the current page of the table

◆ Click the check box in the header row of the table. Click the check box againto deselect all selected rows.

Using filters to customize your viewsMany tables in OpsCenter let you display a subset of the information available bycreating and using custom filters, or by using the predefined (ready-to-use) filters.A filter screens information that is based on a set of conditions that you define.Once you create a filter, you can save it, edit it, or remove it.

In the views that allow filtering, filtering icons appear above the table.

The following procedures describe how you can create, apply, edit, or remove afilter.

To create a custom filter

1 Select the Create Filter icon.

2 Type a name for the filter in the Name field.

3 For Column, select the column name that you want to filter on from thedrop-down list.

For Operator, select an operator. Use != if you do not want to match a specificvalue.

For Value, enter or select a value.

If you select Start Time or End Time for Column, a calendar icon appears forValue. Click the calendar icon to choose a date and time and then click OK.

4 From the drop-down list, select And or Or to build the filter query.

For Link, click Add to add another clause to the query. If the clause is notwhat you want, click Remove to remove the clause from the query.

5 To continue building the filter, select another column.

Repeat 3 and 4.

6 Click OK when you finish building the filter. Your new filter is available inthe filter drop-down list.

To apply a filter

◆ From the drop-down list, select a custom filter or a OpsCenter built-in filter.

OpsCenter filters the table according to the criteria you specify. The viewremains in effect until you change it by selecting another filter.


To edit a custom filter

1 From the drop-down list, select a custom filter.

Note: You cannot modify the ready-to-use OpsCenter filters. You can onlymodify custom filters.

2 Click the Edit filter icon.

3 See “To create a custom filter” on page 73.

This lists the instructions for using the dialog to edit a filter.

Make your changes and click OK.

To remove a custom filter

1 From the drop-down list, select a custom filter.

Note: You cannot delete the ready-to-use or built-in filters.

2 Click the Delete filter icon.

3 Click OK to remove the filter.

Aboutquickly performing common tasks inOpsCenterTable 1-9 lists the common tasks and the corresponding links to thedocumentation.

Table 1-9 Quick links to the OpsCenter documentation

Go to this topicTo learn how to

See “Adding a master server” on page 354.Add master servers in the OpsCenterconsole

See “Managing users” on page 310.Add authorized OpsCenter users

See “Setting user preferences” on page 295.Set up user preferences

See “Configuring SMTP server” on page 303.Configure the SMTP server andOpsCenter alert retention settings

See “Managing recipients” on page 317.Set up recipients for alert and reportnotification

Getting started using Symantec OpsCenterAbout quickly performing common tasks in OpsCenter

74

Table 1-9 Quick links to the OpsCenter documentation (continued)

Go to this topicTo learn how to

See “Creating views” on page 388.Configuring OpsCenter views

See “Creating (or changing) an alert policy”on page 472.

Create OpsCenter alert policies for yoursite

See “Managing an alert policy ” on page 485.View and respond to OpsCenter alerts

See “Monitoring NetBackup jobs” on page 407.View the details for a NetBackup job

See “Monitoring NetBackup policies” on page 429.View NetBackup job policies

See “Managing a job policy” on page 434.Control NetBackup job policies

See “Exporting NetBackup job logs” on page 415.Export NetBackup job log files

See “Monitoring NetBackup services” on page 426.Control NetBackup services

See “About OpsCenter reports” on page 535.Understand and use OpsCenter reports

See “Creating a custom report” on page 555.Create custom reports for your needs

Note: This feature is available with alicensed version (Symantec OpsCenterAnalytics).

See “Managing report schedules” on page 566.Schedule when you want a report to run

About using Web browser bookmarksBy using your Web browser, you can add a bookmark for any view in the OpsCenterconsole and return to it as needed.

If you log out of the OpsCenter console, you can use the bookmark to return tothe same view after you log onto the console.

About OpsCenter documentationThe Symantec OpsCenter Administrator's Guide(NetBackup_AdminGuide_OpsCenter.pdf) provides information on how to useOpsCenter. It includes information about how to monitor and manage NetBackup,collect data from Symantec as well as third-party products, generate alerts, andcreate various reports. It also provides details on the new enhancements inOpsCenter 7.0.1 and also how you can install the OpsCenter 7.0.1 release update.

75Getting started using Symantec OpsCenterAbout using Web browser bookmarks

Note: For the latest support information, for example, supported products oroperating systems, see the Symantec NetBackup Hardware and SoftwareCompatibility List, which is regularly updated on the Symantec Support Web site.

Access the following URL: http://www.symantec.com/business/support

You can find more information about OpsCenter 7.0.1 in Symantec NetBackup7.0.1ReleaseNotes. Always refer to the OpsCenter sections of the NetBackup 7.0.1Release Notes for any last-minute changes to the information that is presentedin this document. The Release Notes also include any restrictions or limits forOpsCenter 7.0.1. You can access the Release Notes from the following URL:

http://entsupport.symantec.com/docs/347326

In addition to this PDF document, OpsCenter 7.0.1 is also shipped with thefollowing online Help documents:

This WebGUI Help contains all information about theOpsCenter GUI. It provides context-sensitive help pages forall GUI screens.

OpsCenter Context-sensitiveHelp

This Java Help contains information about all informationabout Java View Builder dialog boxes and the proceduresyou carry out. You can access the context-sensitive Help byclicking the ‘Help’ button available on a dialog box in theJava View Builder console.

Java View BuilderContext-sensitive Help

This context-sensitive Help provides troubleshootinginformation about NetBackup status codes.

In the OpsCenter console, click Monitor > Jobs and click astatus code link in the jobs table to view its details.

NetBackup Status Codes Help

This HTML help provides information on how you canchange the settings of a table in the OpsCenter console. Toaccess this Help, click the Help button on the Table Settingspop-up screen.

Table Settings Help

Getting started using Symantec OpsCenterAbout OpsCenter documentation

76

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


Upgrading to SymantecOpsCenter 7.0.1


■ Upgrading to Symantec OpsCenter 7.0.1 on Windows and UNIX

■ Uninstalling OpsCenter 7.0.1 release update on Windows and UNIX

Upgrading to Symantec OpsCenter 7.0.1 onWindowsand UNIX

This section describes the procedures for upgrading to OpsCenter 7.0.1 fromOpsCenter 7.0 on Windows and UNIX hosts.

Before you install or upgrade to OpsCenter 7.0.1Review the following considerations before installing the 7.0.1 GA (GeneralAvailability):

■ Before you install the 7.0.1 release update for a specific OpsCenter component,ensure that the 7.0 version of the OpsCenter component is installed. Forexample, if you want to upgrade the OpsCenter server software to 7.0.1, firstinstall OpsCenter Server 7.0 software.If you need to install OpsCenter 7.0, review the 'Installing Symantec OpsCenter7.0' chapter.

■ If you installed the OpsCenter 7.0.1 Beta, uninstall OpsCenter 7.0.1 Beta beforeinstalling OpsCenter 7.0.1 GA.

2Chapter

■ Install OpsCenter Server, Agent, and ViewBuilder of the same versions. Forexample, Server 7.0.1 is only compatible with Agent 7.0.1 and ViewBuilder7.0.1.

■ Ensure that the system on which the OpsCenter server is installed has validvalues for the following OS parameters:

■ Display language

■ Location

Check your respective OS documentation for more information on theseparameters.

■ Symantec recommends that you do not delete or modify any files from the7.0.1 installable.

Note:You can find more information about OpsCenter 7.0.1 inSymantecNetBackup7.0.1ReleaseNotes. Always refer to the OpsCenter sections of the NetBackup 7.0.1Release Notes for any last-minute changes to the information that is presentedin this document. The Release Notes also include any restrictions or limits forOpsCenter 7.0.1. Access the Release Notes from the following link:


About platforms supported by OpsCenter 7.0.1This section provides information about the platforms that OpsCenter 7.0.1supports. In addition to the platforms supported by OpsCenter 7.0, OpsCenterServer 7.0.1 also supports AIX 5.3 and 6.1.

Note: Refer to the compatibility matrix that is posted on the Symantec SupportWeb site for the latest information on the platforms that OpsCenter supports.This document is posted at the following URL:


Table 2-1 OpsCenter operating system requirements

View BuilderAgentServerPlatform

64-bit32-bit64-bit32-bit64-bit32-bit

Yes*

See Note

YesYes*

SeeNote

YesYesYesWindows 2003SP2

Upgrading to Symantec OpsCenter 7.0.1Upgrading to Symantec OpsCenter 7.0.1 on Windows and UNIX

78



Table 2-1 OpsCenter operating system requirements (continued)


Yes*

See Note

YesYes*

SeeNote

YesYesYesWindows 2003 R2

Yes*

See Note

YesYes*

SeeNote

YesYesYesWindows 2008

Yes*

See Note

NoYes*

SeeNote

NoYesNoWindows 2008 R2

NoNoYesNoNoNoSolaris 9 SPARC

NoNoNoNoYesNoSolaris 10 x64

NoNoYesNoYesNoSolaris 10 SPARC

NoNoNoNoYesNoHP Itanium

11.31

NoNoNoNoYesNoAIX 5.3

NoNoNoNoYesNoAIX 6.1

NoNoNoNoYesNoLinux RedHat 4.0,5.0

NoNoNoNoYesNoLinux SUSE ES 10(SP2) & 11

Note: ‘*’ signifies 32-bit binaries working on 64-bit architecture.

Note:OpsCenter components are not supported if Windows or Linux OS is installedon IA-64 architecture.

79Upgrading to Symantec OpsCenter 7.0.1Upgrading to Symantec OpsCenter 7.0.1 on Windows and UNIX

About operating systems and OpsCenter deploymentlimitationsThis section provides some important notes regarding the supported operatingsystems and a few limitations that you need to take care of during OpsCenterdeployment.

Important notes on operating systems

■ If installing OpsCenter on AIX, ensure that the XLC runtime version is 9.0 orhigher.

■ If installing OpsCenter on AIX 6.1, ensure that you install the applicable patchfor AIX from the IBM site:http://www-01.ibm.com/support/docview.wss?uid=isg1fixinfo105097

■ The OpsCenter Server is not supported on non-global Solaris zones.

■ The OpsCenter Server and Agent are supported in a VMware virtual machineguest operating system environment.



■ Location


OpsCenter deployment limitations:

■ You must install OpsCenter Server, Agent, and ViewBuilder of the sameversions. For example, Server 7.0.1 is only compatible with Agent 7.0.1 andViewBuilder 7.0.1.

■ Only the OpsCenter Server can be installed in a clustered mode on UNIX andWindows, with Veritas Cluster Server (VCS). The OpsCenter Agent and ViewBuilder are not supported on VCS.

■ The OpsCenter installer automatically sets the maximum heap size to 1024MB. Your system may require a lesser max heap size to properly run allapplications.See “Adjusting the heap size for OpsCenter components” on page 222.

■ Ensure that the time on the OpsCenter Server and the backup or archiveproduct host is in sync based on the time zone they are deployed in. A backupor archive product host means a supported product host that is connected toOpsCenter. Examples of a backup or archive product host (product host) arePureDisk host, Backup Exec host, NetBackup master server, Enterprise Vaulthost, and so on.


80

http://www-01.ibm.com/support/docview.wss?uid=isg1fixinfo105097

If the OpsCenter server and the product host are in the same time zone (likeCST), both OpsCenter server and the product host must show the same time.For example, if the OpsCenter server and the product host are in CST timezone, but show different time like 8 pm and 10 pm, then OpsCenter may notdisplay accurate data in the reports and also in the Monitor and Manage tabsof the OpsCenter console.If the OpsCenter server and product host are in different time zones like CSTand PST, then ensure that both the CST and the PST time convert to the sameGMT time. For example, if the OpsCenter server and the managed host show8 pm CST and 9 pm PST respectively, then 8 pm (CST) and 9 pm (PST) musttranslate to the same GMT time.

About backup and archiving products supported by OpsCenter 7.0.1This section lists the backup and archiving products that OpsCenter 7.0.1 supports.Note that with the licensed version of OpsCenter, you can do advanced reportingfrom the data that is collected from all of these products. With the unlicensedversion, you cannot collect data from third-party products like IBMTivoliStorage

Manager (TSM) and EMC Legato NetWorker.

Table 2-2 lists the backup and archiving products that OpsCenter supports.

Table 2-2 Backup and archiving products supported by Symantec OpsCenter7.0.1

Support levelVersionsBackup or Archivingproduct

All supported NetBackup platforms(except 7.0 and greater versions) byremote agent

Note:NBU 7.0 and greater versionsdo not require any Agent.

Native agent for Windows 2003 (SP2& R2), Windows 2008 (SP2 & R2),and Solaris 9, 10

6.0 MP7 and higherversions, 6.5 and higherversions, 7.0, 7.0.1

Symantec NetBackup


Table 2-2 Backup and archiving products supported by Symantec OpsCenter7.0.1 (continued)


PureDisk supported platform(PDOS) by the OpsCenter integratedAgent. You do not need a separateAgent to collect data from PureDisk.You can use the inbuilt Agent of theOpsCenter Server for datacollection. To create or configurethe data collector, select the Agentthat is installed as Integrated Agent.

6.2, 6.2.2, 6.5, 6.5.1, 6.6,6.6.0.1, 6.6.0.2, 6.6.0.3

Symantec NetBackupPureDisk

All supported Symantec BackupExec platforms by remote agent.

Native agent on backup servers onWindows 2003 (SP2 & R2), 2008(SP2 & R2)

10d, 11d, 12.0, 12.5, 2010

Note:OpsCenter does notsupport Symantec BackupExec running on NetWare.In addition, OpsCenterdoes not support datacollection from BackupExec software installed ona 64-bit Windowsmachine.

Symantec Backup Exec

All supported Symantec EnterpriseVault platforms by remote agent

Native agent on Microsoft SQLServer 2005 or 2008 (whereEnterprise Vault database resides)on Windows 2003 (SP2 & R2), 2008(SP2 & R2).

7.5, 8.0Symantec EnterpriseVault

Native agent on backup servers onWindows 2003 (SP2 & R2), 2008(SP2 & R2) and Solaris 9/10

Data collection is possible only witha licensed version of OpsCenter.

7.3EMC Legato NetWorker


82



All supported TSM platforms byremote agent

Native agent for backup server onWindows 2003 (SP2 & R2), 2008(SP2 & R2) and Solaris 9/10


5.3, 5.4, 5.5IBM Tivoli StorageManager (TSM)

Upgrading to Symantec OpsCenter 7.0.1 on WindowsThis section provides you with the procedure to download and install OpsCenter7.0.1 components on a Windows host.

Review the following sections before upgrading to OpsCenter 7.0.1:

See “Before you install or upgrade to OpsCenter 7.0.1” on page 77.

See “About platforms supported by OpsCenter 7.0.1” on page 78.

Downloading OpsCenter 7.0.1 release updateUse the following procedure to download the OpsCenter 7.0.1 release update onWindows.


To download OpsCenter 7.0.1 release update

1 Download the OpsCenter 7.0.1 Release Update from the Symantec SupportWeb site into a temporary directory.

Download the OpsCenter 7.0.1 Release Update from the following URL:http://entsupport.symantec.com/docs/350126

You can download the following files corresponding to the specific OpsCentercomponent that you want to upgrade:

OpsCtr_Server_7.0.1_<platform>.zipOpsCenter Server

OpsCtr_Agent_7.0.1_<platform>.zipOpsCenter Agent

OpsCtr_ViewBuilder_7.0.1_<platform>.zipOpsCenter ViewBuilder

2 Extract the applicable zip file by double-clicking on it. For example, if youwant to install OpsCenter Server software, double-clickOpsCtr_Server_7.0.1_<platform>.zip

This creates a number of files that include Setup.exe.

Upgrading to Symantec OpsCenter 7.0.1 on WindowsUse the following procedure to upgrade OpsCenter 7.0 components to OpsCenter7.0.1 on Windows hosts.

You must not run any other installation while installing OpsCenter 7.0.1components. Additionally after an installation is complete, you should wait forsome time before installing other OpsCenter 7.0.1 components.

Note: In case you try to install OpsCenter 7.0.1 components on a system whereOpsCenter 7.0.1 is already installed, the installer runs in a Maintenance mode andlets you repair or remove the OpsCenter 7.0.1 component that is installed on yoursystem.

To upgrade to OpsCenter Server 7.0.1

1 Log on to the OpsCenter system as Administrator.

2 Navigate to the temporary location where you extracted the zip file.

3 RunSetup.exeby double-clicking on the icon from File Manager or WindowsExplorer. Setup.exe can alternatively be run from the command prompt.


84


4 The Welcome Page of the Installation Wizard appears. The Installation Wizarddetects an existing installation of OpsCenter Server 7.0 on the system. Thefollowing message is displayed on the Welcome screen:

The Installation has detected that the following software is already installedon your system: Symantec OpsCenter Server: Version 7.0

Click Next to continue.

5 Read the license agreement, check ‘I accept the terms of the license agreement’and click Next.

6 The installer shows the summary of the installation settings. Check Savesummary to option to save the installation summary. Click Browse to savethe installation summary in your preferred location.

Click Install to begin the installation. The installer installs OpsCenter Server7.0.1 software.

7 After successful installation, you can view the installation logs or view theReadme.

Click Finish.

The installation logs are generated in the following location:

%ALLUSERSPROFILE%\Symantec\OpsCenter\

INSTALLLOGS\OpsCenterMaintPackInstallLog.htm

Symantec recommends that you save theOpsCenterMaintPackInstallLog.htm file before installing any otherOpsCenter component. This is because this file gets overwritten when youinstall another OpsCenter component.

To upgrade to OpsCenter Agent 7.0.1




4 The Welcome Page of the Installation Wizard appears. The Installation Wizarddetects an existing installation of OpsCenter Agent 7.0 on the system. Thefollowing message is displayed on the Welcome screen:

The Installation has detected that the following software is already installedon your system: Symantec OpsCenter Agent: Version 7.0





Click Install to begin the installation. The installer installs OpsCenter Agent7.0.1 software.


Click Finish.


%ALLUSERSPROFILE%\Symantec\OpsCenter\INSTALLLOGS\OpsCenterMaintPackInstallLog.htm


To upgrade to OpsCenter ViewBuilder 7.0.1




4 The Welcome Page of the Installation Wizard appears. The Installation Wizarddetects an existing installation of OpsCenter ViewBuilder 7.0 on the system.The following message is displayed on the Welcome screen:

The Installation has detected that the following software is already installedon your system: Symantec OpsCenter ViewBuilder: Version 7.0




86


Click Install to begin the installation. The installer installs OpsCenterViewBuilder 7.0.1 software.


Click Finish.


%ALLUSERSPROFILE%\Symantec\OpsCenter\

INSTALLLOGS\OpsCenterMaintPackInstallLog.htm


Upgrading to Symantec OpsCenter 7.0.1 silently on WindowsUse the following procedure to upgrade OpsCenter 7.0 components to OpsCenter7.0.1 silently on Windows hosts.

A silent installation avoids the need for interactive input. A silent installationuses a response file to automate OpsCenter installation. Use a silent installationwhen you need to perform an identical installation on several servers.

You must create a response file first and then use the file to perform a silentinstallation. The procedure for creating a response file requires that you runthrough the Installation Wizard. The values that you specify in the Wizard pagesare saved to the response file.

You can also edit the response file if required.

See “About editing the OpsCenter 7.0.1 response file” on page 93.

Note the following points about silent installation:

■ Silent installation of OpsCenter is only supported on Windows platforms.

■ Silent installation of OpsCenter is not supported on clusters.


To upgrade silently to OpsCenter Server

1 Log on as administrator to the system where you want to upgrade OpsCenter7.0 server software to 7.0.1.

2 Open the command prompt on your system. Navigate to the temporarylocation where you extracted the zip file.

3 Enter the following command:

SETUP.EXE -NoInstall

Note that the switch -NoInstall is case sensitive.

This command starts the Installation Wizard where you can specify yourpreferences. Note that the Installation Wizard creates the response file basedon your inputs and does not install the product.

4 The Symantec OpsCenter Installation Wizard appears. The Installation Wizarddetects an existing installation of OpsCenter Server 7.0 on the system. Thefollowing message is displayed on the Welcome screen:

The Installation has detected that the following software is already installedon your system: Symantec OpsCenter Server: Version 7.0




Click Install. Note that clicking Install does not install the product.

7 The Installation Status screen is displayed. Click Finish.

8 A response file namedLangMaintPack-<DD-MM-YY-HH-MIN-SS>.XML is createdat the following location:

%TEMP%\Symantec\OpsCenter

This XML file can be used to install OpsCenter Server software on multiplemachines.

Note: If you have generated the response file on a 32-bit machine, use thisresponse file to install OpsCenter Server software on 32-bit machines only.Similarly if you have generated the response file on a 64-bit machine, usethis response file to install OpsCenter Server software on 64-bit machinesonly.


88

9 On the command prompt, ensure that you are in the directory whereSETUP.EXE is located.

10 Enter the following command to run the silent installation:

SETUP -Silent -RespFile <path of the response file for OpsCenter Server>

Example: Setup -Silent -RespFile C:\LangMaintPack-19-04-10-06-11-31.xml

Note that the switches -Silent and -RespFile are case sensitive.

11 The installation logs are generated at the following location:

%ALLUSERSPROFILE%\SYMANTEC\OPSCENTER\INSTALLLOGS\OpsCenterMaintPackInstallLog.htm

Symantec recommends that you save theOpsCenterMaintPackInstallLog.htm file after you have installed OpsCenterServer 7.0.1. This is because this file gets overwritten when you install anotherOpsCenter component.

See the following section to track the progress of the installation.

See “About tracking the progress of silent installation and troubleshootingtips” on page 93.

After successful installation, you can see Symantec OpsCenter Server 7.0.1Release Update in Add/Remove Programs.

To upgrade silently to OpsCenter Agent

1 Log on as administrator to the system where you want to upgrade OpsCenter7.0 Agent software to 7.0.1.






4 The Symantec OpsCenter Installation Wizard appears. The Installation Wizarddetects an existing installation of OpsCenter Agent on the system. Thefollowing message is displayed on the Welcome screen:

‘The Installation has detected that the following software is already installedon your system: Symantec OpsCenter Agent: Version 7.0’



5 Read the license agreement, check ‘I accept the terms of the licenseagreement’ and click Next.

6 The installer shows the summary of the installation settings. Check Savesummary to option to save the installation summary. Click Browseto savethe installation summary in your preferred location.





This XML file can be used to install OpsCenter Agent software on multiplemachines.

Note: If you have generated the response file on a 32-bit machine, use thisresponse file to install OpsCenter Agent software on 32-bit machines only.Similarly if you have generated the response file on a 64-bit machine, usethis response file to install OpsCenter Agent software on 64-bit machinesonly.



90


SETUP -Silent -RespFile <path of the response file for OpsCenter Agent>





Symantec recommends that you save theOpsCenterMaintPackInstallLog.htm file after you have installed OpsCenterAgent 7.0.1. This is because this file gets overwritten when you install anotherOpsCenter component.



After successful installation, you can see Symantec OpsCenter Agent 7.0.1Release Update in Add/Remove Programs.

To upgrade silently to OpsCenter ViewBuilder 7.0.1

1 Log on as administrator to the system where you want to upgrade OpsCenter7.0 ViewBuilder software to 7.0.1.






4 The Welcome Page of the Installation Wizard appears. The Installation Wizarddetects an existing installation of OpsCenter ViewBuilder 7.0 on the system.The following message is displayed on the Welcome screen:

The Installation has detected that the following software is already installedon your system: Symantec OpsCenter ViewBuilder: Version 7.0




6 The installer shows the summary of the installation settings. Check Savesummary to option to save the installation summary. Click Browseto savethe installation summary in your preferred location.





This XML file can be used to install OpsCenter ViewBuilder software onmultiple machines.

Note: If you have generated the response file on a 32-bit machine, use thisresponse file to install OpsCenter ViewBuilder software on 32-bit machinesonly. Similarly if you have generated the response file on a 64-bit machine,use this response file to install OpsCenter ViewBuilder software on 64-bitmachines only.



SETUP -Silent -RespFile <path of the response file for OpsCenterViewBuilder>





Symantec recommends that you save theOpsCenterMaintPackInstallLog.htm file after you have installed OpsCenterViewBuilder 7.0.1. This is because this file gets overwritten when you installanother OpsCenter component.



After successful installation, you can see SymantecOpsCenterViewBuilder7.0.1 Release Update in Add/Remove Programs.


92

About editing the OpsCenter 7.0.1 response file

You can edit the response file to change any inputs that you provided to theInstallation Wizard. The silent installation is based on these inputs. To edit theresponse file, open it and modify the Value field for the applicable install property.

The following are the contents of a sample response file:

<?xml version="1.0" encoding="UTF-8" standalone="no" ?>

- <XML_Install>

- <OpsCenter_MaintPack>

<InstallProperty Name="RAN_SETUP" Value="1" />

<InstallProperty Name="INSTALLDIR" Value="C:\Program Files\Symantec" />

</OpsCenter_MaintPack>

</XML_Install>

For example, you can modify the OpsCenter installation location in this responsefile by changing the value of INSTALLDIR property from C:\ProgramFiles\Symantec to D:\Symantec.

Note that the text that you enter or modify in the response file is case sensitive.You must save the response file after you modify it.

Note: Symantec recommends that you do not change the value of RAN_SETUP.

About tracking the progress of silent installation and troubleshooting tips

When a silent installation is in progress, you can see SETUP.EXE process runningin the Processes tab of the Windows Task Manager. In addition, you will also findmultiple msiexec.exe processes running in the Task Manager.

You can also track if a silent installation is in progress by checking the size ofVxinst.log file. The size of Vxinst.log file increases as silent installationprogresses. The Vxinst.log file is generated in%ALLUSERSPROFILE%\SYMANTEC\OPSCENTER\INSTALLLOGS.

Upgrading to OpsCenter 7.0.1 on a clusterUse the following procedure to install OpsCenter 7.0.1 release update on anOpsCenter 7.0 cluster.

To upgrade to OpsCenter Server 7.0.1 on a cluster

1 Before you install the OpsCenter 7.0.1 Release Update, ensure that SymantecOpsCenter is at release level 7.0 and configured to run in a cluster. Log on tothe OpsCenter 7.0 cluster as a user with administrator privileges.

2 Ensure that the OpsCenter group is online.


3 Take the VCS OpsCenter resource offline. Use the following command:

hares -offline <oc_resource> -sys <system>

where <oc_resource> is the name of OpsCenter resource and <system> is thenode name on which the resource is currently online. Note that the OpsCenterresource is only a part of the resource group.

4 Make VCS configuration editable. Use the following command:

haconf -makerw

5 Freeze the OpsCenter group. Use the following command to freeze theOpsCenter group:

hagrp -freeze <oc_group> -persistent

where <oc_group> is the name of the OpsCenter group.

6 Stop the OpsCenter cluster agent on all nodes of the OpsCenter group byusing the following command:

haagent -stop NetBackupOpsCenterVCS -sys <node>

where NetBackupOpsCenterVCS is the name of the OpsCenter cluster agent.This command must be repeated for all nodes of the OpsCenter group.

7 Install OpsCenter Server 7.0.1 on all the inactive nodes of the cluster.

See “Upgrading to Symantec OpsCenter 7.0.1 on Windows” on page 84.

8 Install OpsCenter Server 7.0.1 on the active node of the cluster.

See “Upgrading to Symantec OpsCenter 7.0.1 on Windows” on page 84.

9 Start the OpsCenter cluster agent on all nodes of the OpsCenter group. Usethe following command:

haagent -start NetBackupOpsCenterVCS -sys <node>

This command must be repeated for all nodes of the OpsCenter group.

10 Unfreeze the OpsCenter group. Use the following command:

hagrp -unfreeze <oc_group> -persistent


11 Make VCS configuration read only. Use the following command:

haconf -dump -makero

12 If the cluster is in a faulted state, clear the fault.


94

13 Take the OpsCenter resource group offline.

See the cluster documentation for more information.

14 Bring the OpsCenter resource group online. Also verify that OpsCenter canfailover properly in the cluster.


Upgrading to Symantec OpsCenter 7.0.1 on UNIXThis section provides you with the procedure to download and upgrade toOpsCenter 7.0.1 components on UNIX platforms (except AIX).

For AIX platform, you need to do a fresh installation of OpsCenter 7.0.1.

See “Installing and uninstalling OpsCenter 7.0.1 on AIX” on page 99.

Review the following sections before upgrading to OpsCenter 7.0.1 on UNIXplatforms:



Downloading OpsCenter 7.0.1 release updateUse the following procedure to download the OpsCenter 7.0.1 release update onUNIX platforms (except AIX).


To download OpsCenter 7.0.1 release update

1 Download the OpsCenter 7.0.1 release update from the Symantec SupportWeb site into the /tmp directory.

Download the OpsCenter 7.0.1 release update from the following URL:http://entsupport.symantec.com/docs/350126

Download the following files corresponding to the specific OpsCentercomponent that you want to upgrade:

OpsCtr_<Server>_7.0.1_<platform>.tar.gzOpsCenter Server

OpsCtr_<Agent>_7.0.1_<platform>.tar.gzOpsCenter Agent

2 Extract the OpsCtr_<OpsCenter_Component>_7.0.1_<platform>.tar.gz

file.

Note: <OpsCenter_Component> is Server or Agent.

This creates the following directory which contain installation scripts:OpsCtr_<OpsCenter_Component>_7.0.1_<platform>

Upgrading to Symantec OpsCenter 7.0.1This section provides you with the procedure to upgrade to OpsCenter 7.0.1components on UNIX platforms (except AIX).

For AIX platform, you need to do a fresh installation of OpsCenter 7.0.1.

See “Installing and uninstalling OpsCenter 7.0.1 on AIX” on page 99.

To upgrade to OpsCenter Server 7.0.1 on UNIX platforms (except AIX)

1 Open a UNIX console and log on as root on the target host.

2 Navigate to the directory in which you extracted the Release Update installable(/tmp) by using the following command:

cd /tmp/OpsCtr_Server_7.0.1_<platform>/ServerPatch

3 Type the following command: ./installOpsCenterServerPatch. Press Enter.

4 The Welcome message is displayed. Press Enter to continue.


96


5 The installer examines the system for existing packages. The installer checksif OpsCenter Server 7.0 is installed on the system and then displays thefollowing message:

The following OpsCenterServer Patch packages will be installed:

Symantec OpsCenter Patch 7.0.1SYMCOpsCenterPatch 701

Press Enter to continue.

6 The OpsCenter Server is upgraded to 7.0.1 and configuration changes aremade to the system. When the installation is complete, it displays a summaryof the install, including the location of the installation log files.

To upgrade to OpsCenter Agent 7.0.1 on UNIX platforms (except AIX)


2 Navigate to the directory in which you extracted the Release Update installable(/tmp) by using the following command:

cd /tmp/OpsCtr_Agent_7.0.1_<platform>/AgentPatch

3 Type the following command: ./installOpsCenterAgentPatch. Press Enter.


5 The installer examines the system for existing packages. The installer checksif OpsCenter Agent 7.0 is installed on the system and then displays thefollowing message:

The following OpsCenter Agent Patch packages will be installed:

Symantec WebGUI Agent PatchSYMCOpsCenterAgentPatch 701


6 The OpsCenter Agent is upgraded to 7.0.1 and configuration changes aremade to the system. When the installation is complete, it displays a summaryof the install, including the location of the installation log files.

Upgrading to OpsCenter 7.0.1 on a Solaris clusterUse the following procedure to install OpsCenter 7.0.1 release update on anOpsCenter 7.0 cluster.


To upgrade to OpsCenter Server 7.0.1 on a Solaris cluster

1 Before you install the OpsCenter 7.0.1 Release Update, ensure that SymantecOpsCenter is at release level 7.0 and configured to run in a cluster. Log on tothe OpsCenter 7.0 cluster as root.


3 Take the VCS OpsCenter resource offline.


where <oc_resource> is the name of OpsCenter resource and <system> is thenode name on which the resource is currently online.

Note that the OpsCenter resource is only a part of the resource group.


haconf -makerw

5 Freeze the OpsCenter group. Use the following command to freeze theOpsCenter group:





where NetBackupOpsCenterVCS is the name of the OpsCenter cluster agent.


7 Install OpsCenter Server 7.0.1 on all the inactive nodes of the cluster.

See “Upgrading to Symantec OpsCenter 7.0.1” on page 96.

8 Install OpsCenter Server 7.0.1 on the active node of the cluster.

See “Upgrading to Symantec OpsCenter 7.0.1” on page 96.








98








Installing and uninstalling OpsCenter 7.0.1 on AIXThe following sections describe how you can download, install, or uninstallOpsCenter Server on AIX platform.

Note that you always perform a fresh installation of OpsCenter 7.0.1 on AIX. Thisis because AIX support starts with OpsCenter 7.0.1.

Review the following sections before upgrading to OpsCenter 7.0.1 on AIX:



Downloading OpsCenter 7.0.1 package for AIXUse the following procedure to download the OpsCenter 7.0.1 package for AIX.

To download OpsCenter 7.0.1 for AIX

1 Download the OpsCtr_7.0.1_AIX64.tar.gz file from the Symantec SupportWeb site into the /tmp directory.

You can download this file from the following URL:http://entsupport.symantec.com/docs/350126

2 Extract the OpsCtr_7.0.1_AIX64.tar.gz file.

This creates the following directory which contain installation scripts:OpsCtr_7.0.1_AIX64

Installing OpsCenter 7.0.1 on AIXUse the following steps to perform a fresh installation of OpsCenter 7.0.1 on AIXplatform.

Review the following considerations before installing OpsCenter Server on AIX:



■ Ensure that the XLC runtime version is 9.0 and higher.

■ Ensure that you install the applicable patch for AIX 6.1 from the IBM Web site:http://www-01.ibm.com/support/docview.wss?uid=isg1fixinfo105097

To install OpsCenter Server 7.0.1

1 Log on to the target host as root.

2 Navigate to the directory in which you extracted the 7.0.1 installable (/tmp)by using the following command:

cd /tmp/OpsCtr_7.0.1_AIX64/Server

3 Type the following command: ./installOpsCenterServer. Press Enter.


5 The installer then checks if OpsCenter Server is installed on the system ornot. It prompts you in case OpsCenter is already installed. The installer alsoexamines the system for existing packages.

6 The installer displays a list of components that get installed like PBX, AT,Symantec WebGUI Server, Symantec Database etc. Review this list andpressEnter to continue.

7 The installer prompts you with the following message:

You have selected the following installation options:

Installation directory: /opt

Is the above configuration correct? [y,n,q] y


Note that non-default installation is not supported on AIX platform.


100

http://www-01.ibm.com/support/docview.wss?uid=isg1fixinfo105097

8 OpsCenter server is installed on the system.

Type a directory path under which to install the OpsCenter database andpress Enter.

If you create an alternate database directory, the script creates the folderOpsCenterServer below your directory.

To accept the default database installation directory (/var/Symantec), pressEnter without typing a directory path.

In case the database installation directory (/var/symantec) does not exist onthe host, the following information is displayed:

Directory "/var/symantec" does not exist. Do

you want to create the directory? [y,n,q] y

Type y to confirm and press Enter.

The following information is displayed:

The OpsCenter database server may require up to

1 GB of temporary space at runtime. By default, temporary files

will be created in the database installation directory

/var/Symantec/OpsCenterServer

9 You are prompted with the following message:

Would you like to use an alternate directory for

database server temporary space? [y,n,q] (n)

To use the database installation directory for database server temporaryspace, press Enter without typing a directory path.

To specify an alternate directory, type y and press Enter.

Type a directory path for the database server temporary space and pressEnter.

10 Review the installation options you selected. The location of database directoryand the database temp directory is also displayed.

11 Type y and press Enter to confirm the selection and continue.

Type n and press Enter to repeat the configuration steps and revise yourselection.


12 Configuration changes are made to the system.

You are prompted with the following question:

Do you want to restore data that has been backed

up manually [y,n,q] <n>

You can ignore this message as this is a completely fresh installation. Typen and then press Enter.

13 You are prompted for license information. The installer prompts you withthe following:

Please enter a Symantec OpsCenter Analytics license key

or press <Return>:

Enter a valid demo or permanent key that you have received with the purchaseof OpsCenter 7.0.1 and press Enter.

If you do not enter a key, you get an unlicensed version. With the unlicensedversion (Symantec OpsCenter), you cannot access the licensed features.

See “About the license keys” on page 112.

You can also add the license keys later from the OpsCenter console.

See “Managing licenses” on page 300.

Uninstalling OpsCenter Server 7.0.1 on AIXUse the following procedure to uninstall OpsCenter Server 7.0.1 on AIX. Thisremoves OpsCenter Server from the AIX host.

To uninstall OpsCenter Server 7.0.1 on AIX

1 Log on to the target host as root.

2 Change to the following directory:

/opt/VRTS/install

3 Type the following command and press Enter:

./uninstallOpsCenterServer

The Uninstall Script checks the components installed on the system.

4 When asked to confirm if you want to uninstall OpsCenter Server, do one ofthe following:

■ Type y and press Enter to start the uninstall process.


102

The Uninstall Script stops all processes and then uninstalls the componentpackages. When the uninstall is complete, it displays a summary of theuninstall, including the location of the uninstall log files.

■ Type n and press Enter to cancel the uninstall procedure.

Uninstalling OpsCenter 7.0.1 release update onWindows and UNIX

This section describes procedures for uninstalling OpsCenter 7.0.1 on Windowsand UNIX (except AIX). This will only uninstall the 7.0.1 release update from yoursystem.

Note: In case you have installed OpsCenter 7.0.1 and want to uninstall OpsCenterfrom your system, Symantec recommends that you first uninstall OpsCenter 7.0.1release update and then OpsCenter 7.0.

Uninstalling OpsCenter 7.0.1 on WindowsUse the Windows Add/Remove Programs utility to uninstall OpsCenter 7.0.1components on a Windows host.

Note:Before uninstalling OpsCenter components, ensure that NetBackup-WindowsGUI is not running. Close any NetBackup-Windows GUI consoles that are openbefore uninstalling OpsCenter components.

Uninstalling OpsCenter 7.0.1Use the following procedure to uninstall OpsCenter 7.0.1.

To uninstall Symantec OpsCenter Server 7.0.1 on Windows

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

2 In the Windows Control Panel, click Add/Remove Programs.

3 Click Symantec OpsCenter Server 7.0.1 Release Update and click Remove.

4 Click Yes to confirm the uninstallation and remove Symantec OpsCenterServer 7.0.1 from your computer.

To uninstall Symantec OpsCenter Agent 7.0.1 on Windows



103Upgrading to Symantec OpsCenter 7.0.1Uninstalling OpsCenter 7.0.1 release update on Windows and UNIX

3 Click Symantec OpsCenter Agent 7.0.1 Release Update and click Remove.

4 Click Yes to confirm the uninstallation and remove Symantec OpsCenterAgent 7.0.1 from your computer.

To uninstall Symantec OpsCenter View Builder 7.0.1 on Windows



3 Click Symantec OpsCenter ViewBuilder 7.0.1 Release Update and clickRemove.

4 Click Next to continue and remove Symantec OpsCenter View Builder 7.0.1from your computer.

Uninstalling OpsCenter 7.0.1 from a Windows clusterUse the following procedure to uninstall OpsCenter 7.0.1 from a Windows cluster.

To uninstall OpsCenter 7.0.1 from a Windows cluster

1 Log on to the 7.0.1 cluster as a user with administrator privileges.




where <oc_resource> is the name of OpsCenter resource and <system> is thenode name on which the resource is currently online. Note that the OpsCenterresource is only a part of the resource group.


haconf -makerw

5 Freeze the OpsCenter group to prevent failover during the uninstall. Use thefollowing command:







Upgrading to Symantec OpsCenter 7.0.1Uninstalling OpsCenter 7.0.1 release update on Windows and UNIX

104

7 Uninstall OpsCenter Server 7.0.1 from all the inactive nodes of the cluster.

See “Uninstalling OpsCenter 7.0.1” on page 103.

8 Uninstall OpsCenter Server 7.0.1 from the active node of the cluster.















Uninstalling OpsCenter 7.0.1 on UNIXUse the Uninstall Script to uninstall OpsCenter components on UNIX platforms(except AIX). The uninstall script is a part of the 7.0.1 Release Update pack andalso resides in the following directories for the specific OpsCenter component:

/opt/VRTS/install/Ops701 directoryServer

/opt/VRTS/install/OpsAgent701 directoryAgent

Uninstalling OpsCenter 7.0.1Use the following procedure to uninstall OpsCenter 7.0.1 components. Thisprocedure uninstalls only the 7.0.1 Release Update.


To uninstall OpsCenter Server on UNIX


2 Navigate to the following directory:

/opt/VRTS/install/Ops701


./uninstallOpsCenterServerPatch

4 The Uninstall Script checks the components that are installed on the systemand prompts the following question:

Are you sure you want to uninstall OpsCenterServer Patch?

Type y and press Enter to start the uninstall process.

The Uninstall Script stops all processes and then uninstalls OpsCenter Server7.0.1 packages. When the uninstall is complete, it displays a summary of theuninstall, including the location of the uninstall log files.

To uninstall OpsCenter Agent on UNIX


2 Navigate to the following directory:

/opt/VRTS/install/OpsAgent701


./uninstallOpsCenterAgentPatch

4 The Uninstall Script checks the components that are installed on the systemand prompts the following question:

Are you sure you want to uninstall OpsCenter Agent Patch?

Type y and press Enter to start the uninstall process.

The Uninstall Script stops all processes and then uninstalls OpsCenter Agent7.0.1 packages. When the uninstall is complete, it displays a summary of theuninstall, including the location of the uninstall log files.

Uninstalling OpsCenter 7.0.1 from a clusterUse the following procedure to uninstall OpsCenter 7.0.1 from a cluster.

To uninstall OpsCenter 7.0.1 from a cluster

1 Log on to the OpsCenter 7.0.1 cluster as root.



106



where <oc_resource> is the name of OpsCenter resource and <system> is thenode name on which the resource is currently online.

Note that the OpsCenter resource is only a part of the resource group.


haconf -makerw

5 Freeze the OpsCenter group to prevent failover during the uninstall. Use thefollowing command:






7 Uninstall OpsCenter Server 7.0.1 from all the inactive nodes of the cluster.


8 Uninstall OpsCenter Server 7.0.1 from the active node of the cluster.

















108

Installing SymantecOpsCenter 7.0


■ Planning an OpsCenter installation

■ Installing Symantec OpsCenter on Windows and UNIX

■ Upgrading to OpsCenter on Windows and UNIX

■ Post-installation tasks

■ Using an earlier NOM or VBR installation after upgrade

■ Uninstalling Symantec OpsCenter on Windows and UNIX

■ Clustering Symantec OpsCenter

Planning an OpsCenter installationThis section provides information on what all you need to take care of, before youproceed to OpsCenter 7.0 installation or upgrade.

About the software components that OpsCenter usesAlong with OpsCenter specific components, OpsCenter uses some commonSymantec components that are shared.

About components shared with other Symantec applicationsThe following components are used by OpsCenter and are also shared with otherSymantec applications:

3Chapter

■ Symantec Private Branch Exchange (PBX)Symantec Private Branch Exchange lets Symantec applications share a commonTCP/IP port, which reduces the number of ports in the firewalls that must beopen to operate products. PBX also integrates with the Symantec ProductAuthentication Service to allow for authenticated connections in addition tonon-authenticated connections.Since it is an independent component, the PBX port number can be changedusing PBX configuration files. Changing the PBX port number on the serverwhere OpsCenter is installed may cause OpsCenter to fail.

■ Symantec Product Authentication Service (AT)This service is primarily used for user logon authentication and is requiredfor secure communication between OpsCenter Agent, OpsCenter GUI, ViewBuilder, and the OpsCenter server software. AT is also used for securecommunication between NetBackup master servers and the OpsCenter serversoftware. The OpsCenter server needs to be a legitimate server that is allowedto talk to NBU, wherein, the OpsCenter server must appear in the server list.Note that there is no requirement for Symantec Product Authorization Serviceto be installed. Also, there is no requirement for NetBackup Service Layer(NBAC) to be configured on your managed NetBackup master servers.See the files in the docs directory of the NetBackup DVD for information onauthentication services.See Security and Encryption Guide in the NetBackup DVD for informationabout NBAC.

■ JRE (Java Runtime Environment )The Symantec OpsCenter Web server and the OpsCenter application requirethis component.

About Symantec OpsCenter specific componentsThe following components are used only by OpsCenter and are not shared withother Symantec applications:

■ Symantec Java Web serverThe OpsCenter Web GUI and the reporting service runs under Symantec JavaWeb server .

■ Veritas Unified Logging (VxUL)This logging component is installed with OpsCenter Server and Agent and isused to configure and view OpsCenter logs.See the NetBackup Troubleshooting Guide for more information about VxULlogs.

Installing Symantec OpsCenter 7.0Planning an OpsCenter installation

110

■ Sybase database - OpsCenter uses a Sybase SQL Anywhere 11 (Sybase 11)database installation that is separate from the NetBackup database.More information about the Sybase component is available.See http://www.sybase.com/support/manuals.

About the OpsCenter licensing modelOpsCenter requires no license. If you wish to enable additional functionality, adda license key to enable OpsCenter Analytics.

The licensed version of OpsCenter is called Symantec OpsCenter Analytics. Theunlicensed version of OpsCenter is called Symantec OpsCenter. This is visiblefrom the title bar and logon page of the OpsCenter console.

The Symantec OpsCenter Analytics licenses are charged depending on thefollowing considerations:

■ The number of backup clients that OpsCenter reports on (for backupenvironments)

■ The number of mailboxes that OpsCenter reports on (for Symantec EnterpriseVault environments)

Note: If you want to enable custom reporting on Enterprise Vault data, you mustadd the appropriate license key.

For example: You have an OpsCenter - NetBackup set up with 100 backup clientsand OpsCenter - Enterprise Vault set up with 500 mailboxes to report on. Youneed to purchase a license that enables you to report on 100 backup clients and500 mailboxes.

While installing OpsCenter, if you install Symantec Enterprise Vault enabledlicensing key, the license option called Archive Mailbox is added. The licenseoption is visible in the OpsCenter console, on the Settings > Configuration >License page.

If you have a license for 1000 mailboxes, it is added as 'Archive Mailbox' as shownin the figure.

111Installing Symantec OpsCenter 7.0Planning an OpsCenter installation

These entries show that thelicense to back up 1000clients and the license tocollect archive data of 1000mailboxes from EnterpriseVault is installed.

These entries show that the actualusage of Archive mailbox licenseoption is 0 while the licensed value is1000.

It may be possible that the number of mailboxes that you have configured exceedsthe license limit or the number of backup clients that you have exceeds the licenselimit. To know this compare the Value and the Usage column from the Settings> Configuration > License page in the OpsCenter console.

About the license keysOpsCenter has two types of license keys:

This is valid for 60 days from the day the keyis generated. The purpose of the demo keyis to enable you to try the product before youpurchase it.

Demo key

A permanent key does not have an expirydate.

Permanent key

You can access the licensed features with both demo and permanent keys. Witha licensed version, you can do advanced reporting, create custom reports, collectdata from third-party products like IBM Tivoli Storage Manager (TSM) and EMCLegato NetWorker etc.


112

See “About the OpsCenter Analytics licensed features” on page 114.

You can also add, delete, or view license keys after installation from the OpsCenterconsole.


AboutSymantecOpsCenter andSymantecOpsCenterAnalyticsTable 3-1 lists the differences between Symantec OpsCenter and SymantecOpsCenter Analytics.

Table 3-1 Difference between Symantec OpsCenter and Symantec OpsCenterAnalytics

Symantec OpsCenter AnalyticsSymantec OpsCenter

The licensed version of OpsCenter is calledSymantec OpsCenter Analytics.

Symantec OpsCenter Analytics is visiblefrom the title bar and logon page of theOpsCenter console.

The unlicensed version of OpsCenter iscalled Symantec OpsCenter

Symantec OpsCenter is visible from the titlebar and logon page of the OpsCenter console.

Symantec OpsCenter Analytics lets you doadvanced business-level reporting. WithSymantec OpsCenter Analytics, you haveadditional reporting functionality likecreating custom reports, creating reportsusing SQL queries, NetWorker, running orconfiguring chargeback reports, viewingreport data for any previous date etc. . Youcan also collecting data from third-partyproducts like:

■ IBM

■ TSM

■ EMC Legato

More information about the licensed featuresis available.

See “About the OpsCenter Analytics licensedfeatures” on page 114.

Symantec OpsCenter lets you do operationalreporting.

Symantec OpsCenter Analytics lets youcreate and customize multi-level views usingJava View Builder.

You cannot create or customize views usingJava View Builder.


About the OpsCenter Analytics licensed featuresTable 3-2 shows the list of licensed features, where they are located in theOpsCenter console, and how they appear in the unlicensed version.

Table 3-2 Licensed features in OpsCenter Analytics

What is shown in theunlicensed OpsCenterversion

From where you canaccess this feature on theOpsCenter Analyticsconsole

Licensed Feature

Create a custom reportoption is disabled.

Reports>ReportTemplates> Create a New Report >Create a Custom Report

Reports > My Reports >Create a New Report >Create a Custom Report

Create a Custom Report

Create a report using SQLquery option is disabled.

Reports>ReportTemplates> Create a New Report >Create a report using SQLquery

Reports > My Reports >Create a New Report >Create a report using SQLquery

Create a report using SQLquery

Chargeback reports aredisabled.

Report > Report Templates> Chargeback Reports

Run or view chargebackreports

Chargeback settings aredisabled.

Settings > ChargebackControl chargeback settings

You cannot create or editdata collectors forthird-party products like IBMTivoli Storage Manager

(TSM) and EMC LegatoNetWorker.

Settings > Configuration >Agent > Create DataCollector

In the Data Collector Wizard,in the Select Productdrop-down list, TSM andEMC Legato NetWorkeroptions are disabled.

Settings > Configuration >Agent > Edit Data Collector

Create or edit data collectorsfor IBM TSM, EMC LegatoNetWorker


114

Table 3-2 Licensed features in OpsCenter Analytics (continued)

What is shown in theunlicensed OpsCenterversion

From where you canaccess this feature on theOpsCenter Analyticsconsole

Licensed Feature

You can view data older than60 days only with a licensedversion of OpsCenter(OpsCenter Analytics).Upgrade to a valid licenseand select the desiredtimeframe.

Report > Report Templates> Create New Report(Relative and AbsoluteTimeframe window on theSelect Parameters page)

Reports > My Reports >CreateNewReport (Relativeand Absolute Timeframewindow on the SelectParameters page)

Report > Report templates(Run a report, click EditReport and then Relative andAbsolute Timeframewindow.)

Reports > My Reports (Run areport, click EditReport andthen Relative and AbsoluteTimeframe window.)

Full control over reporttimeframe selection. You canview report data for anyprevious date.

The Reconcile option isdisabled.

Monitor > Jobs. TheReconcile option under theMore drop-down list isdisabled.

Reconcile Task

The EditViewlevelAlias tabis disabled.

Settings > Edit View levelAlias

Edit View level Alias tab

The Object Types tab isdisabled.

Settings > Configuration >Object Types

Object Types

You cannot log on to theView Builder. Access to theView Builder is denied if nolicense is there.

View Builder


About the NetBackup and OpsCenter DVDSymantec OpsCenter is shipped with the NetBackup media kit and also as aseparate OpsCenter DVD.

About the NetBackup media kitThe NetBackup Enterprise Server media kit organizes the DVDs by operatingsystem platform. The NetBackup media kit includes a separate DVD for eachplatform. Each NetBackup DVD also lets you install Symantec OpsCenter for thespecific platform. You can use the appropriate DVD to install Symantec OpsCenterand required components. See the NetBackup Installation Guide for more detailsabout the contents of this media kit.

You can either install an unlicensed version (Symantec OpsCenter), a demo version,or purchase a Symantec OpsCenter Analytics license key and install the licensedversion. With the unlicensed version (Symantec OpsCenter), you cannot accessthe licensed features. With the demo version, you can access the licensedOpsCenter features for 60 days (starting from the day you install the demo key).

See “About the OpsCenter licensing model” on page 111.

About the Symantec OpsCenter DVDA separate DVD that contains OpsCenter software is also available. This DVDcontains OpsCenter software for all supported platforms.

You can either install an unlicensed version (Symantec OpsCenter), a demo version,or purchase a Symantec OpsCenter Analytics license key and install the licensedversion. With the unlicensed version (Symantec OpsCenter), you cannot accessthe licensed features. With the demo version, you can access the licensedOpsCenter Analytics features for 60 days (starting from the day you install thedemo key).


About platforms supported by OpsCenterThis section provides information about the platforms that OpsCenter supports.

Note: Refer to the compatibility matrix that is posted on the Symantec SupportWeb site for the latest information on the platforms that OpsCenter supports.This document is posted at the following URL:



116


Table 3-3 OpsCenter operating system requirements


64-bit32-bit64-bit32-bit64-bit32-bit

Yes*

See Note

YesYes*

SeeNote

YesYesYesWindows 2003SP2

Yes*

See Note

YesYes*

SeeNote

YesYesYesWindows 2003 R2

Yes*

See Note

YesYes*

SeeNote

YesYesYesWindows 2008

Yes*

See Note

NoYes*

SeeNote

NoYesNoWindows 2008 R2

NoNoYesNoNoNoSolaris 9 SPARC

NoNoNoNoYesNoSolaris 10 x64

NoNoYesNoYesNoSolaris 10 SPARC

NoNoNoNoYesNoHP Itanium

11.31

NoNoNoNoYesNoLinux RedHat 4.0,5.0

NoNoNoNoYesNoLinux SUSE ES 10(SP2) & 11

Note: ‘*’ signifies 32-bit binaries working on 64-bit architecture.

Note:OpsCenter components are not supported if Windows or Linux OS is installedon IA-64 architecture.


Note: OpsCenter 7.0.1 Server can also be installed on AIX 5.3, 6.1 (64-bit only).


About important notes on operating systems and OpsCenterdeployment limitationsThis section provides a few important notes regarding the supported operatingsystems and a few limitations that you need to take care of during OpsCenterdeployment.

Important notes on operating systems:

■ The OpsCenter Server is not supported on non-global Solaris zones.

■ The OpsCenter Server and Agent are supported in a VMware virtual machineguest operating system environment.



■ Location


OpsCenter deployment limitations:

■ You must install OpsCenter Server, Agent, and ViewBuilder of the sameversions. For example, Server 7.0.1 is only compatible with Agent 7.0.1 andViewBuilder 7.0.1.

■ Only the OpsCenter Server can be installed in a clustered mode on UNIX andWindows, with Veritas Cluster Server (VCS).

■ The OpsCenter installer automatically sets the maximum heap size to 1024MB. Your system may require a lesser max heap size to properly run allapplications.See “Adjusting the heap size for OpsCenter components” on page 222.

■ Ensure that the time on the OpsCenter Server and the backup or archiveproduct host is in sync based on the time zone they are deployed in. A backupor archive product host means a supported product host that is connected toOpsCenter. Examples of a backup or archive product host (product host) arePureDisk host, Backup Exec host, NetBackup master server, Enterprise Vaulthost etc.If the OpsCenter server and the product host are in the same time zone (likeCST), both OpsCenter server and the product host must show the same time.


118

For example, if the OpsCenter server and the product host are in CST timezone, but show different time like 8 pm and 10 pm, then OpsCenter may notdisplay accurate data in the reports and also Monitor and Manage tabs of theOpsCenter console.If the OpsCenter server and product host are in different time zones like CSTand PST, then ensure that both the CST and the PST time convert to the sameGMT time. For example if the OpsCenter server and the managed host show8 pm CST and 9 pm PST respectively, then 8 pm (CST) and 9 pm (PST) musttranslate to the same GMT time.

About backup and archiving products supported by SymantecOpsCenter

This section lists the backup and archiving products that OpsCenter supports.Note that with the licensed version of OpsCenter, you can do advanced reportingfrom the data that is collected from all of these products. With the unlicensedversion, you cannot collect data from third-party products like IBMTivoliStorage



Table 3-4 Backup and archiving products supported by Symantec OpsCenter


All supported NetBackupplatforms (except 7.0 and greaterversions) by remote agent

Note: NBU 7.0 and greaterversions do not require anyAgent.

Native agent for Windows 2003(SP2 & R2), Windows 2008 (SP2& R2), and Solaris 9, 10

6.0 MP7 and higher versions,6.5 and higher versions, 7.0

Note: OpsCenter 7.0.1 canalso monitor NetBackup 7.0.1in addition to all theNetBackup versions listedabove.

Symantec NetBackup


Table 3-4 Backup and archiving products supported by Symantec OpsCenter(continued)


PureDisk supported platform(PDOS) by the OpsCenterintegrated Agent. You do not needa separate Agent to collect datafrom PureDisk. You can use theinbuilt Agent of the OpsCenterServer for data collection. Tocreate or configure the datacollector, select the Agent that isinstalled as Integrated Agent.

6.2, 6.2.2, 6.5, 6.5.1, 6.6Symantec NetBackupPureDisk


Native agent on backup serverson Windows 2003 (SP2 & R2),2008 (SP2 & R2)

10d, 11d, 12.0, 12.5

Note: OpsCenter does notsupport Symantec BackupExec running on NetWare. Inaddition, OpsCenter does notsupport data collection fromBackup Exec softwareinstalled on a 64-bitWindows system.

Note: OpsCenter 7.0.1 canalso monitor Backup Exec2010 in addition to all theBackup Exec versions listedabove.


All supported SymantecEnterprise Vault platforms byremote agent

Native agent on Microsoft SQLServer 2005 or 2008 (whereEnterprise Vault database resides)on Windows 2003 (SP2 & R2),2008 (SP2 & R2).



120

Table 3-4 Backup and archiving products supported by Symantec OpsCenter(continued)


Native agent on backup serverson Windows 2003 (SP2 & R2),2008 (SP2 & R2) and Solaris 9/10

Data collection is possible onlywith a licensed version ofOpsCenter.




Data collection is possible onlywith a licensed version ofOpsCenter.


About managed NetBackup master server considerationsConsider the following recommendations and requirements for your managedNetBackup master servers.

The following recommendations and requirements should be considered for yourmanaged master servers:

■ Installation of OpsCenter server software on a NetBackup master or mediaserver is possible if you want to monitor only one master server (i.e. the masterserver on which the OpsCenter server software is installed).To monitor more than one master server, Symantec recommends that youinstall the OpsCenter server software on a separate standalone server.More information on sizing guidelines is available.See “About OpsCenter sizing guidelines” on page 124..

■ OpsCenter does not collect data from the managed servers that are configuredwithin a network address translation (NAT) network.

■ The OpsCenter server should be configured as a fixed host with a static IPaddress.

■ Symantec recommends that any NetBackup master server be monitored byonly one OpsCenter server.


■ OpsCenter 7.0 can monitor all NetBackup master server versions between 6.0MP7 and 7.0.

Note: OpsCenter 7.0.1 can monitor all NetBackup master server versionsbetween 6.0 MP7 and 7.0.1.

■ OpsCenter can be used to monitor a NetBackup cluster.See NetBackup High Availability Administrator's Guide for more details onsetting up a NetBackup cluster environment.

More information about adding managed NetBackup servers in OpsCenter isavailable.

See “Adding a master server in the OpsCenter console” on page 358.

About using NBSL to collect data from NetBackup masterserversA NetBackup master server with version 7.0 and above does not require any Agentor data collector for data collection. The data is collected automatically by theOpsCenter server from an NBU 7.0 (or greater) master server using NetBackupService Layer (NBSL).

However for a master server whose version is less than 7.0, an Agent must beinstalled only if you want to collect specific data (image, error log, and scheduledjobs data). In case you do not want to collect such data, you do not need to installan Agent. OpsCenter collects all the other data automatically from the masterserver using NBSL

Starting with the 6.0 release of NetBackup, NBSL components are included as apart of NetBackup on master and media servers.

OpsCenter requires NBSL for all NetBackup monitoring, managing, and controlfunctions. OpsCenter is affected if NBSL stops running on a managed NetBackupserver.

If NBSL stops, OpsCenter may not capture any changes that were made to theNetBackup configuration. When NBSL restarts, OpsCenter correctly recapturesthe latest state.

Design your OpsCenter serverBefore setting up a Symantec OpsCenter (OpsCenter) server, review therecommendations and requirements that are listed in the earlier sections.

See “About managed NetBackup master server considerations” on page 121.


122

Sizing considerationsThe size of your OpsCenter server depends largely on the number of NetBackupobjects that OpsCenter manages.

The NetBackup objects that determine the OpsCenter server size are the following:

■ Number of master servers to manage

■ Number of policies

■ Number of the jobs that are run per day

■ Total number of jobs

■ Number of media

Based on these factors, the following OpsCenter server components should besized accordingly:

■ Disk space (for installed OpsCenter binary + OpsCenter database)

■ Type and number of CPUs

■ RAM

The next section describes the OpsCenter database and how it affects disk spacerequirements, followed by a link to the sizing guidelines for OpsCenter.

About the OpsCenter databaseThe Sybase database that OpsCenter uses is similar to the database that NetBackupuses. The database is installed as part of the OpsCenter server installation.

Note the following:

■ After you configure OpsCenter, OpsCenter disk space depends on the volumeof data initially loaded on the OpsCenter server from the managed NetBackupservers.The initial data load on the OpsCenter server is in turn dependent on thefollowing data present in the managed master servers:

■ Number of policy data records

■ Number of job data records

■ Number of media data records

■ The rate of OpsCenter database growth depends on the quantity of manageddata. This data can be policy data, job data, or media data.

Information is available on how to adjust database values for better OpsCenterperformance.


See “Tuning OpsCenter for more performance” on page 213.

About OpsCenter sizing guidelinesTable 3-5 lists the minimum hardware requirements and recommended settingsfor installing OpsCenter server software.

Table 3-5 OpsCenter server sizing guidelines

Number ofjobs per day

Number ofmedia

Number ofjob policies

Number ofalerts

Number ofNetBackupmasterservers tobemonitored

SystemConfiguration

0 – 20,0000 – 10000 – 20000 - 10,0000-202 Processors,8 GB RAM

20,000 –40,000

1000 – 10,0002000 – 400010,000 -40,000

20-404 Processors,8 GB RAM

40,000 –60,000

10,000 –50,000

4000 – 600040,000 -60,000

40-608 LogicalProcessors, 8GB RAM

60,000 –1,50,000

50,000 –1,00,000

6000 – 10,00060,000 -1,00,000

60-10016 LogicalProcessors,16 GB RAM

Note: Some of the data in this table has been interpolated.

Symantec recommends that the memory of the system where you install OpsCenterserver is 8 GB or more.

Installation of OpsCenter server software on a NetBackup master or media serveris possible if you want to monitor only one master server (i.e. the master serveron which the OpsCenter server software is installed).

If NetBackup and OpsCenter server are installed on the same system, Symantecrecommends that the maximum number of NetBackup jobs that run daily is 5000.If the number of NetBackup jobs that run daily on the master server is more than5000, Symantec recommends that you install OpsCenter server software on aseparate stand-alone system.

Information is available on how you can tune OpsCenter for better OpsCenterperformance.


124

See “Tuning OpsCenter for more performance” on page 213.

About supported upgrade pathsOpsCenter supports direct upgrades from the following versions:

■ VBR 6.5 GA -> OpsCenter 7.0

■ VBR 6.5.1 -> OpsCenter 7.0

■ VBR 6.5.1.1 -> OpsCenter 7.0

■ VBR 6.6 GA -> OpsCenter 7.0

■ VBR 6.6.1 -> OpsCenter 7.0

■ NOM 6.0 MP7 -> OpsCenter 7.0

■ NOM 6.5 and higher versions -> OpsCenter 7.0

Note: In case you have a lower version of NOM or VBR, first upgrade to thesupported version. See the product documentation for details on how to upgrade.

About OpsCenter Agent deploymentThis section describes the deployment scenarios of OpsCenter Agent. It helps youdecide the Agent deployment in your environment.

Note: You must install OpsCenter Server, Agent, and ViewBuilder of the sameversions. For example, Server 7.0.1 is only compatible with Agent 7.0.1 andViewBuilder 7.0.1.

OpsCenter Agent can either be deployed on the OpsCenter Server host, producthost (for example, a NetBackup master server whose version is less than 7.0, aBackup Exec host, an Enterprise Vault host etc.), or a separate host (Remote Agent). A Remote Agent is an Agent that is deployed on a host other than the OpsCenterhost. This depends on the product that you want to collect data from and itsoperating system. The prerequisites for collecting data from each product varyand are described in their respective data collection sections.


Note:A NetBackup master server with version 7.0 and above does not require anyAgent for data collection. The data is collected automatically by the OpsCenterserver from an NBU 7.0 (or greater) master server using NBSL.

However for a master server whose version is less than 7.0, an Agent must beinstalled only if you want to collect specific data (image, error log, and scheduledjobs data). In case you do not want to collect such data, you do not need to installan Agent. OpsCenter collects all the other data automatically from the masterserver using NBSL.

Note:You do not require an OpsCenter Agent to collect data from PureDisk. If youhave installed the VBR Agent only for PureDisk data collection, you must manuallyuninstall the VBR Agent.

See “About backup and archiving products supported by Symantec OpsCenter”on page 119.

A single Agent can have multiple data collectors configured which collect datafrom the respective product host.

Note: In case of a NetBackup and EMC Legato Networker host, you need separateOpsCenter Agents to collect data from servers with different versions.

See “About data collection in OpsCenter” on page 333.

Only one Agent can be installed on a single host, which can have multiple datacollectors (were called 'Agent Modules' previously) configured.

See “Installing Symantec OpsCenter on Windows and UNIX” on page 134.

About Agent deployment in case of different product versionsThe following section describes what should be the Agent deployment if you wantto collect data from different product versions.


126

You need separate Agents to collect data from differentversions of NetBackup master server . NetBackup binaries(Remote Admin Console for Windows and master or mediaserver for UNIX) installed on the Agent host should matchthe version of the NetBackup master server .

Note: A NetBackup master server with version 7.0 or laterdoes not require any Agent for data collection. However fora master server whose version is less than 7.0, an Agentmust be installed if you want to collect specific data(scheduled jobs, image, and error logs).

NetBackup

You don't need a separate Agent to collect data fromPureDisk. You can use theinbuiltAgent of the OpsCenterServer for data collection. To create or configure the datacollector, select the Agent that is installed as IntegratedAgent.

Note: You do not require an OpsCenterAgent to collect datafrom PureDisk. If you have installed the VBR Agent only forPureDisk data collection, you must manually uninstall theVBR Agent.

See “Configuring PureDisk data collector” on page 366.

PureDisk

You can use same Agent to collect data from Backup ExecServers with different versions.

Note: To collect data from Backup Exec Server host, youneed to install the Agent on a Windows host, as Backup Execsupports only Windows platform.

Backup Exec

You can use same OpsCenter Agent to collect data from TSMservers with different versions.

IBM TSM

You need separate OpsCenter Agents for Legato serverswith different versions. Agent needs to be installed on theLegato server host.

EMC Legato Networker

You can use the same OpsCenter Agent to collect EnterpriseVault data from Microsoft SQL Servers with differentversions.

Note: To collect Enterprise Vault / archive data, you needto install the OpsCenter Agent on a Windows host, asEnterprise Vault supports only Windows platform.

Enterprise Vault


About installing Agent on a product hostOpsCenter Agent can be installed on a product host.

The following products support local Agent installation:




■ IBM TSM


Note: EMC Legato Networker does not support remote OpsCenter Agentinstallation. You must install the Agent on the EMC Legato Networker host.

Installing Agent in this fashion has a very low effect on the backup environmentby adding agent. The OpsCenter Agent must support the operating system of thebackup application host.

Installing the Agent on a remote backup application host has the followingadvantages:

■ Ease of maintenance to upgrade agent; you only service one host.

■ Minimal intrusion on backup hosts; one agent that is installed on a backuphost.

A disadvantage of installing the OpsCenter Agent on a remote backup applicationhost is that the Agent may use significant system resources, which can affect thebackup application host’s performance.

About installing the Agent on a host different than a producthostOpsCenter Agent can be installed on a host different than the product host. Thedifferent host may be the OpsCenter Server host or a separate host.

You should deploy Remote Agent in the following situations:

■ When OpsCenter Agent does not support the operating system of the product,for example HP-UX.

■ When host system has insufficient resources to support colocation of agentand backup application.

In such situations, the Agent should remotely communicate with backup products.


128

The following products support Remote Agent installation:




Note: PureDisk does not support local Agent installation, because OpsCenterdoes not support PDOS (PureDisk Operation System). Therefore PureDiskServer and OpsCenter Agent cannot reside on the same host.


■ IBM TSM

Note: Make sure that the Remote Agent host has Remote Admin Console (RAC)or Master or media server installed, to collect data from another master serverthat you want to monitor / report on.

UNIX platforms do not support RAC.

For back up products (except Backup Exec), you need to have backup applicationclient (.exe) on the Agent host to collect data remotely.

See “Collecting data from Enterprise Vault” on page 367.

Advantages of installing the Agent on the OpsCenter Server host or a separatehost include the following:

■ You do not have to install additional software on backup application hosts asthe backup data is gathered remotely.

■ You need to maintain only one machine for both OpsCenter Server and agent,which avoids the maintenance that might otherwise be involved in upgradingthe agent.

Disadvantages of installing the Agent on the OpsCenter Server host include thefollowing:

■ You must install a component of the backup application on the OpsCenterServer host.For example, you need separate OpsCenter Agents to collect data from differentversions of NetBackup Master Server. NetBackup binaries (Remote AdminConsole for Windows and Master or Media Server for Solaris) installed on theAgent host should match the version of the NetBackup Master Server.


■ In some situations, a backup application license key is required for thecomponent that is installed on the OpsCenter Server host.

Examples of Agent deployment in a NetBackup setupIn a NetBackup setup, the following OpsCenter deployment scenarios are valid:

■ OpsCenter Server is installed on OpsCenterHost 1, Agent is installed onAgentHost 1, and NetBackup 6.5 master server is installed on ProdHost 1You need to install NetBackup 6.5 Remote Admin Console or NetBackup masterserver on AgentHost 1 and configure a data collector to collect data fromProdHost 1.

■ OpsCenter Server and Agent are installed onOpsCenterHost 1 and NetBackupmaster server is installed on ProdHost 1You need to install NetBackup 6.5 Remote Admin Console or NetBackup masterserver on OpsCenterHost 1 and configure a data collector to collect data fromProdHost 1.

■ OpsCenter Server is installed onOpsCenterHost1 and NetBackup master serverand Agent are installed on ProdHost 1You need to configure a data collector onOpsCenterHost 1 to collect data fromProdHost 1.

■ OpsCenter Server and Agent are installed on OpsCenterHost 1, NetBackup 6.5master server is installed on , and ProdHost 1 another NetBackup 6.5 masterserver is installed on ProdHost 2.You need to install NetBackup 6.5 Remote Admin Console or master server onOpsCenterHost 1 and configure two data collectors, one to collect data fromProdHost 1 and another to collect data from ProdHost 2.

■ OpsCenter Server is installed on OpsCenterHost 1, Agent A1 is installed onAgentHost 1, and Agent A2 is installed on AgentHost 2. NetBackup 6.0 masterserver is installed on ProdHost 1 and NetBackup 6.5 master server is installedon ProdHost 2.You need to install NetBackup 6.0 Remote Admin Console or master server onAgentHost 1 and configure a data collector to collect data from ProdHost 1 andinstall NetBackup 6.5 Remote Admin Console or master server on theAgentHost2 and configure a data collector to collect data from ProdHost 2

Before you install or upgradeReview the following checklists before installing Symantec OpsCenter 7.0(OpsCenter) and before upgrading from NetBackup Operations Manager (NOM)or Veritas Backup Reporter (VBR) to Symantec OpsCenter.


130

Table 3-6 lists the things you must check before installing OpsCenter or beforeupgrading from NOM or VBR to OpsCenter on a Windows server.

Table 3-6 OpsCenter install and upgrade checklist for Windows

ChecklistSerial No.

Ensure that you install OpsCenter software on a supported platform.

See “About platforms supported by OpsCenter” on page 116.

1.

Ensure that no other installation is in progress while installing OpsCenter.2.

Ensure that the antivirus software is disabled before installing OpsCenter.3.

Ensure that your OpsCenter server is configured as a fixed host with a staticIP address.

4.

Ensure that the fully qualified domain name (FQDN) of your OpsCenter serverhas maximum 44 characters.

5.

For fresh OpsCenter installation, ensure that the database directory has atleast 20 MB of available space. Note that once you install and start usingOpsCenter, the database grows in size, and requires more space.

See “Design your OpsCenter server” on page 122.

6.

Ensure that the necessary ports are opened before installing OpsCenter ona hardened server.

See “About communication and firewall considerations” on page 276.

7.

Ensure that the name of the folder in which you are installing OpsCenterdoes not contain any special characters like %, ~, !, @, $, &, ^, #.

8.

If a file called 'program' exists in the C: folder of your OpsCenter server,rename, or delete the file before installing OpsCenter.

9.

If you need to monitor a single master server, install OpsCenter on theNetBackup master or media server (recommended).

10.

If you are upgrading from NOM to OpsCenter , ensure that you have one ofthe following NOM versions installed:

■ Latest Maintenance Pack of NOM 6.0

■ NOM 6.5 and higher versions

If you are upgrading from a NOM version not listed above, first upgrade toone of the supported versions. See the NOM documentation for details onhow to perform this upgrade.

11.


Table 3-6 OpsCenter install and upgrade checklist for Windows (continued)

ChecklistSerial No.

If you are upgrading from VBR to OpsCenter Analytics, ensure that you haveone of the following VBR versions installed:

■ VBR 6.5, VBR 6.5.1, VBR 6.5.1.1

■ VBR 6.6, VBR 6.6.1

If you are upgrading from a VBR version not listed above, first upgrade toone of the supported versions. See the VBR documentation for details onhow to perform this upgrade.

12.

If upgrading from VBR or NOM, ensure that the OpsCenter database directoryhas thrice as much space (3x) as that taken by your NOM database or VBRdatabase (x). For example, if your NOM database or VBR database is 1 GB,then the OpsCenter database directory must have at least 3 GB of availablespace.

Note that once you install and start using OpsCenter, the database grows insize, and requires more space.


13.

Table 3-7 lists the things you must check before installing OpsCenter or beforeupgrading from NOM or VBR to OpsCenter on a UNIX server.

Table 3-7 OpsCenter install and upgrade checklist for UNIX

ChecklistSerial No.

Ensure that you install OpsCenter software on a supported platform.


1.

Ensure that no other installation is in progress while installing OpsCenter.2.

Ensure that your OpsCenter server is configured as a fixed host with a staticIP address.

3.

Ensure that the OpsCenter server does not have a symbolic link to the /optdirectory.

4.

Ensure that the fully qualified domain name (FQDN) of your OpsCenter serverhas maximum 44 characters.

5.

For fresh OpsCenter installation, ensure that the database directory has atleast 20 MB of available space. Note that once you install and start usingOpsCenter, the database grows in size, and requires more space.


6.


132

Table 3-7 OpsCenter install and upgrade checklist for UNIX (continued)

ChecklistSerial No.

Ensure that the necessary ports are opened before installing OpsCenter ona hardened server.

See “About communication and firewall considerations” on page 276.

7.

If you need to monitor a single master server, install OpsCenter on theNetBackup master or media server (recommended).

8.

If you upgrade from NOM to OpsCenter , ensure that you have one of thefollowing NOM versions installed:

■ Latest Maintenance Pack of NOM 6.0 MP7

■ NOM 6.5 and higher versions

If you are upgrading from a NOM version not listed above, first upgrade toone of the supported versions. See the NOM documentation for details onhow to perform this upgrade.

9.

If you are upgrading from VBR to OpsCenter Analytics, ensure that you haveone of the following VBR versions installed:

■ VBR 6.5, VBR 6.5.1, VBR 6.5.1.1

■ VBR 6.6, VBR 6.6.1

If you are upgrading from a VBR version not listed above, first upgrade toone of the supported versions. See the VBR documentation for details onhow to perform this upgrade.

10.

If you are upgrading from VBR or NOM, ensure that the OpsCenter databasedirectory has thrice as much space as that taken by your NOM database orVBR database. For example, if your NOM database or VBR database is 1 GB,then the OpsCenter database directory must have at least 3 GB of availablespace.

Note that once you install and start using OpsCenter, the database grows insize, and requires more space.


11.

If you are upgrading from NOM or VBR to OpsCenter on a different system(such as when upgrading from a platform not supported in OpsCenter likeSolaris 8 or 9), run the Backup.sh script from the Server directory of theOpsCenter DVD to back up the necessary data.

This backed up data can then be restored on the supported OpsCenterplatform during installation.


12.


Installing SymantecOpsCenter onWindows andUNIXThis section describes the procedures for fresh installation of OpsCenter 7.0 onWindows and UNIX hosts.

You can also upgrade from an earlier NOM or VBR installation.

See “Upgrading to OpsCenter on Windows and UNIX” on page 159.

You can install OpsCenter in a clustered mode.

See “Clustering Symantec OpsCenter” on page 235.

Table 3-8 provides steps to install OpsCenter components. You can use this tableas a checklist while installing Symantec OpsCenter.

Table 3-8 Steps to install / upgrade / cluster Symantec OpsCenter

Reference topicStepStep number

See “Planning an OpsCenter installation”on page 109.

Review the hardware / software requirements forOpsCenter Server and Agent hosts, carefully.

Make sure that you satisfy the operating systemrequirements.

See “About platforms supported by OpsCenter”on page 116.

Go through the firewall settings and port numberinformation.

See “About communication and firewall considerations”on page 276.

Go through the Agent deployment section.

See “About OpsCenter Agent deployment” on page 125.

Review the Install/Upgrade checklists before installingOpsCenter.

See “Before you install or upgrade” on page 130.

1

See “Installing Symantec OpsCenter onWindows” on page 135.

See “Installing Symantec OpsCenter onUNIX” on page 139.

See “Upgrading to OpsCenter on Windowsand UNIX” on page 159.

See “Clustering Symantec OpsCenter”on page 235.

Go through the appropriate installation section.

Different sections are available for fresh installation,upgrade, and clustering.

Note: After installation, verify if OpsCenter is runningproperly.

2

Installing Symantec OpsCenter 7.0Installing Symantec OpsCenter on Windows and UNIX

134

Installing Symantec OpsCenter on WindowsUse the Installation Wizard to install OpsCenter on a Windows host.

You may install OpsCenter 7.0 from the OpsCenter DVD or from the NetBackupmedia kit. The OpsCenter DVD contains OpsCenter software for all availableplatforms. The NetBackup media kit contains a separate DVD for each platform.

Note: You must not run any other installation while installing OpsCentercomponents. Additionally after an installation is complete, you should wait forsome time before installing other OpsCenter components.

Installing Symantec OpsCenter Server on WindowsUse the following procedure to install Symantec OpsCenter server on Windowshosts.

Note: In case you try to install OpsCenter components on a system where OpsCenteris already installed, the installer runs in a Maintenance mode and lets you repairor remove the OpsCenter component that is installed on your system.

To install OpsCenter Server on Windows

1 On a Windows host where you want to install OpsCenter server, insert theappropriate OpsCenter product DVD in the DVD drive.

You may install OpsCenter from the OpsCenter DVD or from the NetBackupmedia kit. The OpsCenter DVD contains OpsCenter software for all availableplatforms. The NetBackup media kit contains a separate DVD for eachplatform.

2 If autorun is enabled, the Symantec DVD Browser appears.■

■ If autorun is not enabled, click Start >Run. On the Run dialog box, in theOpen text box, type ‘D:\Browser.exe’ and press Enter:

Where D is the DVD drive.The Symantec DVD Browser appears.

3 On the Symantec DVD browser, click the Installation link.

4 If you use the NetBackup media kit to install OpsCenter, click OpsCenterSoftwareInstallation. Ignore this step if you install OpsCenter server softwarefrom the OpsCenter DVD.

5 Click the OpsCenter Server Installation link to install Symantec OpsCenterserver.

135Installing Symantec OpsCenter 7.0Installing Symantec OpsCenter on Windows and UNIX

6 The Symantec OpsCenter Installation Wizard appears. Click Next.


8 The following options are displayed:

Select this option to install OpsCenter Server on thishost.

Install to this computer only

Select this option to install OpsCenter Server on allselected nodes, in a clustered mode. You need to installOpsCenter Server manually on each node of thecluster.

This option is enabled if you have Veritas ClusterServer (VCS) installed.

See “Clustering Symantec OpsCenter on Windows”on page 236.

See “Clustering Symantec OpsCenter Server onSolaris” on page 243.

Install a clustered OpsCenterServer

Select Install to this computer only.

9 In the Installation Method section, click Typical to use the default settings,installation location, or port numbers.

Also compare the space that is required by the installation with the actualspace available in the installation directory.

Note: Click Custom if you want to change the default settings, locations, orport numbers.

Click Next.

10 On the License Keys screen, enter your demo or permanent key that you havereceived with the purchase of OpsCenter and click Add Key.






136

11 Click Next. The installer shows the summary of the settings that you haveselected for installation.

Check SaveSummaryto field to save the installation summary. Click Browseto save the installation summary in your preferred location.

12 Click Install.

The installer starts installing the OpsCenter Server software.

Note: The default OpsCenter database location on Windows is:

C:\Program Files\Symantec\OpsCenter\server\db\data

13 After successful installation, you can view the OpsCenter console or viewinstallation logs.

14 Click Finish.

Installing Symantec OpsCenter Agent on WindowsUse the following procedure to install Symantec OpsCenter Agent on a Windowshost.

To install OpsCenter Agent

1 You can install the OpsCenter Agent either on the OpsCenter Server host,product host, or a separate host. To decide where you want to install theOpsCenter Agent, review the information on Agent deployments.

See “About OpsCenter Agent deployment” on page 125.

2 On a Windows host where you want to install OpsCenter Agent, insert theappropriate OpsCenter product DVD in the DVD drive.

You may install OpsCenter Agent from the OpsCenter DVD or from theNetBackup media kit. The OpsCenter DVD contains OpsCenter software forall available platforms. The NetBackup media kit contains a separate DVDfor each platform.




4 On the Symantec DVD Browser, click the Installation link.


5 If you use the NetBackup media kit to install OpsCenter Agent, click OpsCenterSoftwareInstallation. Ignore this step if you install OpsCenter Agent softwarefrom the OpsCenter DVD.

6 Click the OpsCenter Agent Installation link to install OpsCenter Agent.



9 The default installation location is C:\Program Files\Symantec. To installOpsCenter to a different directory, click Browse.

Note: The default installation location on a Windows 64-bit machine isC:\Program Files (x86)\Symantec.

Click Next.

10 The installer shows the summary of the settings that you have selected forAgent installation.


11 Click Install.

The installer starts installation of OpsCenter Agent.

12 After successful installation, you can view Agent installation logs or openthe readme file.

13 Click Finish.

Installing Symantec OpsCenter View Builder on WindowsUse the following procedure to install Symantec OpsCenter View Builder.

To install OpsCenter View Builder

1 On the OpsCenter Server host, insert the appropriate OpsCenter product DVDin the DVD drive.




138




4 If you use the NetBackup media kit to install OpsCenter View Builder, clickOpsCenter Software Installation. Ignore this step if you install OpsCenterView Builder software from the OpsCenter DVD.

5 Click the OpsCenter View Builder Installation link to install SymantecOpsCenter View Builder.



8 On the Installation Location screen, click Browse if you want to change thedefault location for Symantec OpsCenter View Builder installation.


9 Select a new location and click Next.

10 The installer shows the summary of the settings that you have selected forSymantec OpsCenter View Builder installation.


11 Click Install.

The installer starts installation of Symantec OpsCenter View Builder.

12 After successful installation, you can view the installation logs or open thereadme file.

13 Click Finish.

Installing Symantec OpsCenter on UNIXThis section provides you with the procedure to install OpsCenter on a UNIX host.

You may install OpsCenter from the OpsCenter DVD or from the NetBackup mediakit. The OpsCenter DVD contains OpsCenter software for all available platforms.The NetBackup media kit contains a separate DVD for each platform.


Installing Symantec OpsCenter Server on UNIXUse the following procedure to install OpsCenter server software on UNIX hosts.

To install OpsCenter Server on UNIX


2 Mount the OpsCenter product DVD for the appropriate platform on whichyou are installing.


3 Do one of the following:

■ If you use the OpsCenter DVD to install OpsCenter server software,navigate to the appropriate OpsCenter platform directory and then theServer directory on the DVD.

Type the following command:./install. Press Enter.

■ If you use the NetBackup media kit to install OpsCenter, navigate to theServer directory.

cd OpsCenter/Server

Type the following command:./installOpsCenterServer. Press Enter.



For Solaris Sparc, the installer also asks for installing Server or Agent if youare installing from OpsCenter DVD.

6 The installer displays a list of components that get installed like PBX, AT,Symantec WebGUI Server, Symantec Database etc. Review this list and pressEnter to continue.

7 The installer prompts you with the following question:

Where do you want to install Symantec OpsCenter? </opt>

Type a directory path where you want to install the Symantec OpsCenterServer packages and press Enter.

To accept the default path (/opt), press Enter without typing a directorypath.


140

8 Type y to confirm the directory path and press Enter.
























13 Configuration changes are made to the system.

You are prompted with the following question:

Do you want to restore data that has been backed

up manually [y,n,q] <n>

If you have not been using NOM or VBR and are only installing OpsCenterfor the first time, you do not need to restore any data. Type n and then pressEnter.

Use this option if you are upgrading from NOM or VBR to OpsCenter serversoftware on a different UNIX system. An example scenario is when NOM orVBR is running on Solaris 8 and you require the same data with OpsCenteron Solaris 10. To upgrade on a different server or platform, use Backup.sh

script to back up your data on the NOM or VBR server and then copy it to theOpsCenter server. The Backup.sh script is located in the Server directory ofthe OpsCenter DVD.

More information on how to upgrade to OpsCenter server on a differentsystem is available.

See “Upgrading to OpsCenter Server on a different UNIX system” on page 206.

14 You are prompted for license information. The installer prompts you withthe following:


or press <Return>:

Enter a valid demo or permanent key that you have received with the purchaseof OpsCenter and press Enter.





Installing Symantec OpsCenter Agent on UNIXUse the following procedure to install OpsCenter Agent on UNIX.


142

To install OpsCenter Agent on UNIX


2 Mount the appropriate OpsCenter product DVD for the platform on whichyou are installing.



■ If you use the OpsCenter DVD to install OpsCenter Agent, navigate to theappropriate OpsCenter platform directory and then the Agent directoryon the DVD.Type the following command:

./install. Press Enter.

■ If you use the NetBackup media kit to install OpsCenter Agent, navigateto the following location:

cd OpsCenter/Agent

Type the following command:

./installOpsCenterAgent. Press Enter.

4 Type the following command:



6 The installer then checks if OpsCenter Agent is installed on the system ornot. It prompts you in case OpsCenter Agent is already installed.

For Solaris Sparc, the installer also asks for installing Server or Agent if youare installing from OpsCenter DVD.

7 The installer displays a list of components that get installed like PBX,Symantec WebGUI Agent etc. Review this list and press Enter to continue.

8 It is optional to configure the OpsCenter Agent during installation. You maychoose to configure OpsCenter Agent later either manually or by running./opt/VRTS/install/installOpsCenterAgent -configure command.

To configure OpsCenterAgent now, type y and press Enter.


9 Enter the location where you want to install OpsCenter Agent.

Type a directory path where you want to install the Symantec OpsCenterAgent packages and press Enter.


10 Type y and then press Enter to confirm your installation options.

11 The OpsCenter Agent is installed. You can view the installation log files,summary, and response files on the path mentioned.

Installing Symantec OpsCenter silently on WindowsThis section lists the procedure on how you can install the OpsCenter componentssilently on Windows platform. It also lists how you can track the progress of silentinstallation and some troubleshooting tips.

Installing OpsCenter silentlyA silent installation avoids the need for interactive input. A silent installationuses a response file to automate OpsCenter installation. Use a silent installationwhen you need to perform an identical installation on several servers.

You must create a response file first and then use the file to perform a silentinstallation. The procedure for creating a response file requires that you runthrough the Installation Wizard. The values that you specify in the Wizard pagesare saved to the response file.

You can also edit the response file if required.

See “About editing the response file” on page 156.

Note the following points about silent installation:

■ Silent installation of OpsCenter is only supported on Windows platforms.

■ Silent installation of OpsCenter is not supported on clusters.

To install OpsCenter server software silently

1 Log on as administrator to the system where you want to install OpsCenterserver software.

2 Insert the appropriate OpsCenter product DVD in the DVD drive. You mayinstall OpsCenter from the OpsCenter DVD or from the NetBackup media kit.The OpsCenter DVD contains OpsCenter software for all available platforms.The NetBackup media kit contains a separate DVD for each platform.


144

3 Open the command prompt on your system. Use either of the following optionsdepending on whether you are using OpsCenter DVD or NetBackup media kitto install OpsCenter:

■ If you are using the OpsCenter DVD to install OpsCenter, navigate to <DVDDrive>\<Architecture>\Server directory.Example: D:\x86\Server

■ If you are using the NetBackup media kit to install OpsCenter, navigateto <DVD Drive>\Addons\<Architecture>\OpsCenter\Server directory.Example: D:\Addons\x86\OpsCenter\Server





5 The Welcome screen of the Symantec OpsCenter Installation Wizard appears.Click Next.


7 Select Install to this computer only on the Installation Choice screen.

In the Installation Method section, click Typical to use the default settings,installation location, or port numbers. Also compare the space that is requiredby the installation with the actual space available in the installation directory.


Click Next.



See Symantec OpsCenter Administrator's Guide for licensing details.

Click Next.


9 The installer shows the summary of the settings that you have selected forinstallation. Check SaveSummary to field to save the installation summary.Click Browse to save the installation summary in your preferred location.



11 A response file named Server-<DD-MM-YY-HH-MIN-SS>.XML is created atthe following location:

‘%TEMP%\Symantec\OpsCenter

This XML file can be used to install OpsCenter server software on multiplemachines.



SETUP -Silent -RespFile <path of the response file>

Example: Setup -Silent -RespFile C:\Server-07-12-09-06-11-31.xml



%ALLUSERSPROFILE%\SYMANTEC\OPSCENTER\INSTALLLOGS



After successful installation, you can see Symantec OpsCenter Server inAdd/Remove Programs.

To install OpsCenter Agent silently

1 Log on as administrator to the system where you want to install OpsCenterAgent software.

2 Insert the appropriate OpsCenter product DVD in the DVD drive. You mayinstall OpsCenter Agent from the OpsCenter DVD or from the NetBackupmedia kit. The OpsCenter DVD contains OpsCenter software for all availableplatforms. The NetBackup media kit contains a separate DVD for eachplatform.

3 Open the command prompt on your system. Use either of the following optionsdepending on whether you are using OpsCenter DVD or NetBackup media kitto install OpsCenter Agent:


146

■ If you are using the OpsCenter DVD to install OpsCenter, navigate to <DVDDrive>\<Architecture>\Agent directory.Example: D:\x86\Agent

■ If you are using the NetBackup media kit to install OpsCenter, navigateto <DVD Drive>\Addons\<Architecture>\OpsCenter\Agent directory.Example: D:\Addons\x86\OpsCenter\Agent







7 The default installation location is C:\Program Files\Symantec. To installOpsCenter to a different directory, click Browse.


Click Next.

8 The installer shows the summary of the settings that you have selected forAgent installation. Check Save Summary to field to save the installationsummary. Click Browse to save the installation summary in your preferredlocation.

9 Click Install. Note that clicking Install does not install the product.


11 A response file named Agent-<DD-MM-YY-HH-MIN-SS>.XML is created at thefollowing location:







Example: Setup -Silent -RespFile C:\Agent-07-12-09-06-11-31.xml






After successful installation, you can see Symantec OpsCenter Agent inAdd/Remove Programs.

To install ViewBuilder silently

1 Log on as administrator to the system where you want to install OpsCenterViewBuilder software.

2 Insert the appropriate OpsCenter product DVD in the DVD drive. You mayinstall OpsCenter from the OpsCenter DVD or from the NetBackup media kit.The OpsCenter DVD contains OpsCenter software for all available platforms.The NetBackup media kit contains a separate DVD for each platform.

3 Open the command prompt on your system. Use either of the following optionsdepending on whether you are using OpsCenter DVD or NetBackup media kitto install OpsCenter:

■ If you are using the OpsCenter DVD to install OpsCenter, navigate to <DVDDrive>\<Architecture>\ViewBuilder directory.Example: D:\x86\ViewBuilder

■ If you are using the NetBackup media kit to install OpsCenter, navigateto <DVD Drive>\Addons\<Architecture>\OpsCenter\ViewBuilder directory.Example: D:\Addons\x86\OpsCenter\ViewBuilder



Note that the -NoInstall switch is case sensitive.




148


7 The default installation location is C:\Program Files\Symantec. To installOpsCenter View Builder to a different directory, click Browse.


Click Next.

8 The installer shows the summary of the settings that you have selected forSymantec OpsCenter View Builder installation.


9 Click Install. Note that clicking Install does not install the product.


11 A response file named ViewBuilder-<DD-MM-YY-HH-MIN-SS>.XML is createdat the following location:

‘%TEMP%\Symantec\OpsCenter





Example: Setup -Silent -RespFile C:\ViewBuilder-07-12-09-06-11-31.xml






After successful installation, you can see Symantec OpsCenter ViewBuilderin Add/Remove Programs.


Upgrading silently to OpsCenter

Use the following procedures to upgrade to OpsCenter components silently.

To upgrade silently from NOM or VBR to OpsCenter server

1 Log on as administrator to the NOM system or VBR system where you wantto install OpsCenter server software.

2 Insert the appropriate OpsCenter product DVD in the DVD drive.


3 Open the command prompt on your system. Use either of the following optionsdepending on whether you are using OpsCenter DVD or NetBackup mediakit:

■ If you are using the OpsCenter DVD to install OpsCenter, navigate to <DVDDrive>\<Architecture>\Server directory.Example: D:\x86\Server

■ If you are using the NetBackup media kit to install OpsCenter, navigateto <DVD Drive>\Addons\<Architecture>\OpsCenter\Server directory.Example: D:\Addons\x86\OpsCenter\Server





5 The Installation Wizard detects an existing installation of NetBackupOperations Manager or Veritas Backup Reporter on the system. For example,the following message may be displayed on the Welcome screen:

‘The Installation has detected that the following software is already installedon your system: NetBackup Operations Manager Server: Version 6.5’

Before you upgrade to Symantec OpsCenter, all existing NOM services arestopped automatically. After you successfully upgrade to Symantec OpsCenter,you can manually uninstall NOM.

Click Next.



150

7 In the Installation Method section, click Typical to use the default settings,installation location, or port numbers. Also compare the space that is requiredfor installing OpsCenter server and the actual space that is available.

Click Next.


8 Specify a location for saving the old NOM or VBR database. The defaultlocation is C:\Program Files\Symantec\OpsCenter\SavedData. Click Browseto specify a different location.

Click Next.

Note:Ensure that the database location has adequate space by going throughthe Diskspacerequirements section on this page. A green checkmark appearsin the Required column if there is adequate disk space.

9 On the Upgrade Settings page, enter a port number on which the old NOMor VBR database can be started. The default port number is 13799. Click Next.

10 On the LicenseKeys screen, enter your demo or permanent key that you havereceived with the purchase of OpsCenter and click Add Key.

If you are upgrading from NOM and you do not enter a key, you get anunlicensed version (Symantec OpsCenter). With an unlicensed version, youcannot access the licensed features.

If you are upgrading from VBR and you do not enter a license key, yourexisting license keys are used. The license keys that are already installed onthe system are displayed in the box that appears on this screen. The licensetype information is also shown along with the key.

See the Symantec OpsCenter Administrator’s Guide for more informationabout licenses.

Click Next.

11 The installer shows a summary of the settings that you have selected forinstallation.

Check SaveSummaryto option to save the installation summary. Click Browseto save the installation summary in your preferred location.




13 A response file named Server-<DD-MM-YY-HH-MIN-SS>.XML is created at thefollowing location:


This XML file can be used to install OpsCenter server software on multiplemachines.




Example: Setup -Silent -RespFile C:\Server-07-12-09-06-11-31.xml






After successful installation, you can see Symantec OpsCenter Server inAdd/Remove Programs.

To upgrade silently from VBR Agent to OpsCenter Agent

1 Log on as administrator to the VBR Agent system that you want to upgradeto OpsCenter server software.




■ If you are using the OpsCenter DVD to install OpsCenter, navigate to <DVDDrive>\<Architecture>\Agent directory.Example: D:\x86\Agent


152

■ If you are using the NetBackup media kit to install OpsCenter, navigateto <DVD Drive>\Addons\<Architecture>\OpsCenter\Agent directory.Example: D:\Addons\x86\OpsCenter\Agent





5 The Symantec OpsCenter Installation Wizard appears. The Installation Wizarddetects an existing installation of Veritas Backup Reporter Agent on thesystem. Based on your installed VBR Agent version, the following messagemay be displayed on the Welcome screen:

‘The Installation has detected that the following software is already installedon your system: Veritas Backup Reporter Agent: <Version>’

Before you upgrade to Symantec OpsCenter Agent, all Veritas Backup Reporterservices are stopped automatically. After you successfully upgrade toSymantec OpsCenter Agent, you must manually uninstall Veritas BackupReporter Agent.



7 On the Installation Location screen, click Browse if you want to change thedefault location for Symantec OpsCenter Agent installation.

Ensure that the installation directory that you specify has adequate space bygoing through the Disk space requirements section on this page. A greencheckmark appears in the Required column if there is adequate disk space.

Select a new location and click Next.

8 The installer shows a summary of the settings that you have selected forSymantec OpsCenter Agent installation. Check Save Summary to field tosave the installation summary. Click Browse to save the installation summaryin your preferred location.




10 A response file named Agent-<DD-MM-YY-HH-MIN-SS>.XML is created at thefollowing location:

%TEMP%\Symantec\OpsCenter\





Example: Setup -Silent -RespFile C:\Agent-07-12-09-06-11-31.xml






After successful installation, you can see Symantec OpsCenter Agent inAdd/Remove Programs.

To upgrade silently from VBR View Builder to OpsCenter View Builder

1 Log on as administrator to the VBR ViewBuilder system that you want toupgrade to OpsCenter ViewBuilder software.


You may install OpsCenter ViewBuilder from the OpsCenter DVD or from theNetBackup media kit. The OpsCenter DVD contains OpsCenter software forall available platforms. The NetBackup media kit contains a separate DVDfor each platform.


■ If you are using the OpsCenter DVD to install OpsCenter, navigate to <DVDDrive>\<Architecture>\ViewBuilder directory.Example: D:\x86\ViewBuilder

■ If you are using the NetBackup media kit to install OpsCenter, navigateto <DVD Drive>\Addons\<Architecture>\OpsCenter\ViewBuilder directory.


154

Example: D:\Addons\x86\OpsCenter\ViewBuilder





5 The Symantec OpsCenter Installation Wizard appears. The Installation Wizarddetects an existing Veritas Backup Reporter View Builder and shows thefollowing message on the Welcome page:

‘The Installation has detected that the following software is already installedon your system:

Veritas Backup Reporter View Builder: <version>.

In order to upgrade to a newer version, the existing Veritas Backup ReporterView Builder will be removed.'




Ensure that the installation directory that you specify has adequate space bygoing through the Disk space requirements section on this page. A greencheckmark appears in the Required column if there is adequate disk space.

Select a new location and click Next.

8 The installer shows a summary of the settings that you have selected forSymantec OpsCenter View Builder installation. Check SaveSummaryto fieldto save the installation summary. Click Browse to save the installationsummary in your preferred location.

Click Install.

9 A response file named ViewBuilder-<DD-MM-YY-HH-MIN-SS>.XML is createdat the following location:

%TEMP%\Symantec\OpsCenter\




11 Enter the following command to run silent installation:

Setup -Silent -RespFile <path of the response file>

Example: Setup -Silent -RespFile

C:\ViewBuilder-07-12-10-06-11-31.xml






After successful installation, you can see Symantec OpsCenter ViewBuilderin Add/Remove Programs.

About editing the response fileYou can edit the response file to change any inputs that you provided to theInstallation Wizard . The silent installation is based on these inputs. To edit theresponse file, open it and modify the Value field for the applicable install property.For example, you can modify the OpsCenter installation location, license keyinformation, or database directory in the response file.

The following are the contents of a sample response file:

<?xml version="1.0" encoding="UTF-8" standalone="no" ?>

- <XML_Install>

- <OpsCenter_Server>

<InstallProperty Name="RAN_SETUP" Value="1" />

<InstallProperty Name="INSTALLDIR" Value="C:\Program Files\Symantec" />

<InstallProperty Name="BUSINESS_REP_LIC_KEYS">

<TagValue><License Key></TagValue>

</InstallProperty>

<Installproperty Name="SCMSTARTTYPE" Value="auto" />

<Installproperty Name="INSTALLPBX" Value="YES" />

<Installproperty Name="STARTSERVICE" Value="YES" />

<Installproperty Name="DATABASE_DATA_DIR" Value="C:\Program Files\Symantec\OpsCenter\DB\Data" />

</OpsCenter_Server>

</XML_Install>


156

For example, you can modify the OpsCenter installation location in this responsefile by changing the value of INSTALLDIR property from C:\ProgramFiles\Symantec to D:\Symantec. You can also modify the database directory bymodifying the value of the DATABASE_DATA_DIR property.

Similarly you can edit the license key by changing the value ofBUSINESS_REP_LIC_KEYS property. You can also add a new license key by adding<TagValue>License key </TagValue> under <InstallPropertyName="BUSINESS_REP_LIC_KEYS" >.

Note that the text that you enter or modify in the response file is case sensitive.You must save the response file after you modify it.

Note: Symantec recommends that you do not change the value of RAN_SETUP,SCMSTARTTYPE, INSTALLPBX, and STARTSERVICE properties.

About tracking the progress of silent installation andtroubleshooting tipsWhen a silent installation is in progress, you can see SETUP.EXE process runningin the Processes tab of the Windows Task Manager. In addition, you will also findmultiple msiexec.exe processes running in the Task Manager.

You can also track if a silent installation is in progress by checking the size ofVxinst.log file. The size of Vxinst.log file increases as silent installationprogresses. The Vxinst.log file is generated in%ALLUSERSPROFILE%\SYMANTEC\OPSCENTER\INSTALLLOGS.

About troubleshooting silent installation issues

Use the following procedure to troubleshoot silent installation issues. Thisprocedure must be performed after the silent installation ends.

To troubleshoot silent installation issues

1 After the silent installation ends, navigate to the following location:

%ALLUSERSPROFILE%\SYMANTEC\OPSCENTER\INSTALLLOGS.

2 Check if a file named OpsCenterInstallLog.htm is present. IfOpsCenterInstallLog.htm is not present, see 7.


3 OpenOpsCenterInstallLog.htm and check the timestamp and the OpsCentercomponent it is for to ensure that it is the appropriate log file.

You must check the timestamp because OpsCenterInstallLog.htmmay havebeen generated as a result of previous silent installations.

In addition, the same OpsCenterInstallLog.htm file is generated when youinstall OpsCenter server, Agent, or View Builder. Hence you must check thespecific OpsCenter component that is associated withOpsCenterInstallLog.htm.

4 You can check the timestamp by opening OpsCenterInstallLog.htm andseeing the first line in the file. For example, the following is the first line froma sample OpsCenterInstallLog.htm file:

01-19-2010,13:35:30: -Silent _RespFile "C:\Documents and

Settings\Administrator\Agent-19-01-10-13-04-21.xml"

In this example, the timestamp is 01-19-2010, 13:35:30.

5 To know the OpsCenter component the log file is associated with, search forthe following keywords in the OpsCenterInstallLog.htm file:

You will find matches when you searchfor OpsCenter Server in the file. Thismeans that the log file is for OpsCenterserver.

OpsCenter Server

You will find matches when you searchfor OpsCenter Agent in the file. Thismeans that the log file is for OpsCenterAgent.

OpsCenter Agent

You will find matches when you searchfor OpsCenter ViewBuilder in the file.This means that the log file is forOpsCenter ViewBuilder.

OpsCenter ViewBuilder

Note: In case you have checked the timestamp and the OpsCenter componentassociated with all OpsCenterInstallLog.htm files that are present and donot find a valid OpsCenterInstallLog.htm file, see 7.


158

6 Use the OpsCenterInstallLog.htm file to troubleshoot silent installationissues. Open the OpsCenterInstallLog.htm file to see if the installation wassuccessful or to understand why the installation failed. This file shows theinstallation status at the end. Installation errors are flagged in this file in redcolor. You may also see a description about why the error occurred andtroubleshoot accordingly.

Ignore the subsequent steps of this procedure.

7 If OpsCenterInstallLog.htm is not present or you cannot find a validOpsCenterInstallLog.htmfile, check ifOpsCenter<Product>InstallLog.htmfile is present. In OpsCenter<Product>InstallLog.htm, <Product> can beServer, Agent, or ViewBuilder depending on the OpsCenter component thatyou are installing.

8 Always ensure that the OpsCenter<Product>InstallLog.htm file isappropriate by checking the timestamp. You can check the timestamp byopening the OpsCenter<Product>InstallLog.htm file and seeing the firstline of the file. For example, the following is the first line from a sampleOpsCenter<Product>InstallLog.htm file:

01-19-2010,13:35:30: -Silent _RespFile "C:\Documents and

Settings\Administrator\Agent-19-01-10-13-04-21.xml"

In this example, the timestamp is 01-19-2010, 13:35:30.

9 Use the OpsCenter<Product>InstallLog.htm file to troubleshoot silentinstallation issues. You can open the OpsCenter<Product>InstallLog.htm fileto see if the installation was successful or to understand why the installationfailed. This file shows the installation status at the end. Installation errorsare flagged in this file in red color. You may also see a description about whythe error occurred and troubleshoot accordingly.

Upgrading to OpsCenter on Windows and UNIXThis section describes how you can upgrade from NOM or VBR to OpsCenter 7.0on Windows and UNIX platforms.

Upgrade considerationsWhen you upgrade from Veritas Backup Reporter to OpsCenter Server and accessthe OpsCenter console, you may not see data for some columns in the followingviews:

159Installing Symantec OpsCenter 7.0Upgrading to OpsCenter on Windows and UNIX

No data is shown for Available Columns(columns that are not displayed) like PID,Owner, Parent, Data Movement etc.

Monitor > Jobs

No data is shown in this viewMonitor > Services

No data is shown for some columnsMonitor > Policies

No data is shown for some columnsMonitor > Media

No data is shown for some columnsMonitor > Devices

No data is shown for some columnsManage > Storage

No data is shown for some columnsManage > Devices

This data is not shown because VBR does not collect this data and hence this datais not available in the VBR database. The data for all these columns is shown afterdata collection for the master server is enabled during data migration. Once thedata collection is enabled, this data is collected from the master server and shownon the OpsCenter console.

Note: For most of the entities like policies, media, devices etc., all previous datais also collected once data collection is enabled. However for jobs and image,previous data is not collected from the master server.

Upgrading from NetBackup Operations Manager to SymantecOpsCenter on Windows and UNIX

The OpsCenter Installation Wizard automatically detects an older NOMinstallation. The OpsCenter installer only stops the existing NOM services. It doesnot uninstall your existing NOM installation. You can manually uninstall NOMafter successfully migrating data and using Symantec OpsCenter for some time.During upgrade, OpsCenter server is installed, the older NOM database is savedand started. Note that a saved copy of the NOM database is used for upgrade. Datamigration from the older NOM database to the new OpsCenter database startsonce the Symantec OpsCenter Server Service is started while installing OpsCenterserver.

You can access the data migration status page from the OpsCenter logon page.The data migration process may take time depending on the volume of data thathas to be migrated.

Installing Symantec OpsCenter 7.0Upgrading to OpsCenter on Windows and UNIX

160

Upgrading from NetBackup Operations Manager to SymantecOpsCenter on WindowsUse the following procedure to upgrade to OpsCenter server on Windows.


To upgrade from NOM to Symantec OpsCenter on Windows









6 The Symantec OpsCenter Installation Wizard appears. The Installation Wizarddetects an existing installation of NetBackup Operations Manager on thesystem. For example, the following message may be displayed on the Welcomescreen:

The Installation has detected that the following software

is already installed on your system:

NetBackup Operations Manager Server: Version 6.5

Before you upgrade to Symantec OpsCenter, all existing NOM services arestopped automatically. After you successfully upgrade to Symantec OpsCenter,you can manually uninstall NOM.


7 Click Next.


9 On the Installation Choice section, click Typical to use the default settings,installation location, or port numbers.

Also compare the space that is required for installing OpsCenter server andthe actual space that is available.


Click Next.

10 Specify a location for saving the old NOM database. The default location isC:\Program Files\Symantec\OpsCenter\SavedData. Click Browse to specifya different location.


11 On the Upgrade Settings page, enter a port number on which the old NOMdatabase can be started. The default port number is 13799.

Click Next.


If you do not enter a key, you get an unlicensed version (Symantec OpsCenter).With an unlicensed version, you cannot access the licensed features.



Check SaveSummaryto option to save the installation summary. Click Browseto save the installation summary in your preferred location.

14 Click Install.

The installer installs OpsCenter Server software.


162


Data migration from the old NOM database to the OpsCenter database startsonce the Symantec OpsCenter Server service is started while installingOpsCenter server. You can also access the data migration status from theOpsCenter console.

See “Monitoring data migration from NOM to Symantec OpsCenter”on page 177.

16 Click Finish.

Upgrading fromNetBackupOperationsManager to OpsCenteron UNIXUse the following procedure to upgrade from NOM to OpsCenter on UNIX.

To install OpsCenter Server on UNIX





■ If you use the OpsCenter DVD to install OpsCenter, go to the appropriateOpsCenter platform directory and then the Server directory.

■ If using the NetBackup media kit, go to the following directory:

cd OpsCenter/Server

4 Type the following command:./installOpsCenterServer. Press Enter.


6 The installer then checks for an existing NOM installation. It displays thefollowing message when NOM is installed:

NetBackup Operations Manager (NOM) <version> is installed

on <hostname>. Do you want to upgrade from NOM <version> to

Symantec OpsCenter [y,n,q] y

To upgrade to Symantec OpsCenter, type y and then press Enter.


7 The following message is displayed:

The existing NOM database and configuration files must

be backed up before upgrading to Symantec OpsCenter.

Where should the NOM database and configuration

files be backed up? An OpsCenter_save directory will be

created within the directory that you specify to store

these files. (/var/symantec)

Type the directory name in which the NOM database and configuration filescan be saved and then press Enter.

To accept the default directory path (/var/symantec), press Enter.


9 Type a directory path where you want to install the Symantec OpsCenterServer packages and press Enter.








The OpsCenter database server may require up to 1 GB of temporary

space at runtime.

By default, temporary files will be created in the database

installation directory,



164


Would you like to use an alternate directory for database server

temporary space? [y,n,q] (n)






15 Configuration changes are performed. You are prompted with the followingmessage:

The old database will be started separately to migrate its data

to the OpsCenter database. Specify a port number on which the old

database can be started (13799)

Type a port number on which the old NOM database can be started and pressEnter.

To accept the default port number (13799), press Enter only.

Note: Ensure that the port number that you enter is free and not used by anyapplication.



or press <Return>:

To use a permanent key or a demo key, type the license key and press Enter.

If you do not enter any key and press Enter, you get an unlicensed version(Symantec OpsCenter). You cannot access the licensed features by using theunlicensed version.

17 All the OpsCenter services are started.

The following information is also displayed:

■ Web URL to access OpsCenter console.


■ Location of install log, summary, and response files.

■ Link on the OpsCenter logon page from where you can access the datamigration status

Upgrading from Veritas Backup Reporter to OpsCenter Analytics onWindows and UNIX

The OpsCenter Installation Wizard automatically detects an older VBR installation.The OpsCenter installer only stops the existing VBR services. It does not uninstallyour existing VBR installation. You can manually uninstall VBR after successfullymigrating data and using Symantec OpsCenter for some time. However, do notuninstall VBR server after upgrading successfully to Symantec OpsCenter serversoftware on a Windows platform. Read the following TechAlert if you want touninstall VBR on Windows:


During upgrade, OpsCenter is installed and the older VBR database is saved andstarted. Note that a saved copy of the VBR database is used for upgrade. The datamigration from the older VBR database to the new OpsCenter database starts afteryou successfully upgrade to OpsCenter. The data migration process happens foreach master server. You can also view the data migration process from theOpsCenter logon page. The data migration process may take time depending onthe data that has to be migrated.

Upgrading from Veritas Backup Reporter to OpsCenterAnalytics on WindowsUse the following procedure to upgrade from Veritas Backup Reporter Server,Agent, and View Builder to Symantec OpsCenter Server, Agent, and View Builderrespectively.


Upgrading from Veritas Backup Reporter Server to OpsCenter Server onWindows

Use the following procedure to upgrade from Veritas Backup Reporter Server toSymantec OpsCenter Server on Windows.


166


To upgrade to OpsCenter Server on Windows








5 Click the OpsCenter Server Installation link to install Symantec OpsCenterServer.

6 The Symantec OpsCenter Installation Wizard appears. The Installation Wizarddetects an existing installation of Veritas Backup Reporter on the system.Based on your installed VBR version, the following message may be displayedon the Welcome screen:



Veritas Backup Reporter Server: <Version>

Before you upgrade to Symantec OpsCenter, all existing VBR server services

are stopped automatically.

After you successfully upgrade to Symantec OpsCenter, you must manually

uninstall VBR server software.

Note that you should not uninstall VBR server after upgrading successfullyto Symantec OpsCenter server software. Read the following TechAlert if youwant to uninstall VBR after upgrading to OpsCenter server:


7 Click Next to continue.




9 On the Installation Choice section, click Typical to use the default settings,installation location, or port numbers.

Also compare the space that is required for upgrading to OpsCenter and theactual space that is available.


Click Next.

10 Specify a location for saving the old VBR database. The default location isC:\Program Files\Symantec\OpsCenter\SavedData. Click Browse to specifya different location.



12 On the Upgrade Settings page, enter a port number on which the old VBRdatabase can be started. The default port number is 13799.

Note: Ensure that the port number that you enter is free and not used by anyother application.

Click Next.

13 On the License Keys screen, enter the demo or permanent key that you havereceived with the purchase of OpsCenter and click Add Key.

The license keys that are already installed on the system are also displayedin the box that is shown on this screen. The license type is also shown alongwith the key. If you do not enter a license key, your existing license keys areused.





168

15 Click Install.

The installer upgrades VBR server to OpsCenter Server software.


Data migration from the old VBR database to the OpsCenter database startsonce the Symantec OpsCenter Server service is started while installingOpsCenter server. You can also access the data migration status from theOpsCenter console.

See “Monitoring data migration from VBR to Symantec OpsCenter Analytics”on page 192.

17 Click Finish.

Upgrading from Veritas Backup Reporter Agent to OpsCenter Agent onWindows

Use the following procedure to upgrade from Veritas Backup Reporter Agent toSymantec OpsCenter Agent.

You do not require an OpsCenterAgent to collect data from NetBackup 7.0 orPureDisk. However, you must install OpsCenter Agent if you want to collect datafrom other backup products.

Note:Once you upgrade your VBR Agent to the OpsCenter Agent, the port numberthat the VBR Agent uses is not required in OpsCenter. By default, the VBR Agentuses port number 7806.

To upgrade to OpsCenter Agent on Windows

1 On a Windows host where you want to install OpsCenter Agent, insert theappropriate OpsCenter product DVD in the DVD drive.







4 If you use the NetBackup media kit to install OpsCenter Agent, click OpsCenterSoftwareInstallation. Ignore this step if you install OpsCenter Agent softwarefrom the OpsCenter DVD.

5 Click the OpsCenter Agent Installation link to install Symantec OpsCenterAgent.

6 The Symantec OpsCenter Installation Wizard appears. The Installation Wizarddetects an existing installation of Veritas Backup Reporter Agent on thesystem. Based on your installed VBR Agent version, the following messagemay be displayed on the Welcome screen:



Veritas Backup Reporter Agent: <Version>

Before you upgrade to Symantec OpsCenter Agent, all Veritas Backup Reporterservices are stopped automatically. After you successfully upgrade toSymantec OpsCenter Agent, you must manually uninstall Veritas BackupReporter Agent.



9 On the Installation Location screen, click Browse if you want to change thedefault location for Symantec OpsCenter Agent installation.

Note: Ensure that the installation directory that you specify has adequatespace by going through the Disk space requirements section on this page.A green checkmark appears in the Required column if there is adequate diskspace.


11 The installer shows a summary of the settings that you have selected forSymantec OpsCenter Agent installation.


12 Click Install.

The installer starts installation of Symantec OpsCenter Agent.


170


14 Click Finish.

Upgrading from Veritas Backup Reporter View Builder to OpsCenter ViewBuilder on Windows

Use the following procedure to upgrade from Veritas Backup Reporter View Builderto Symantec OpsCenter View Builder

To upgrade from Veritas Backup Reporter View Builder to Symantec OpsCenterView Builder

1 On the OpsCenter View Builder host, insert the appropriate OpsCenter productDVD in the DVD drive.






4 If you use the NetBackup media kit to install OpsCenter View Builder, clickOpsCenter Software Installation. Ignore this step if you install OpsCenterView Builder software from the OpsCenter DVD.

5 Click the OpsCenter View Builder Installation link to install SymantecOpsCenter View Builder.

6 The Symantec OpsCenter Installation Wizard appears. The Installation Wizarddetects an existing Veritas Backup Reporter View Builder and shows thefollowing message on the Welcome page:

The Installation has detected that the following

software is already installed

on your system.

Veritas Backup Reporter: <version>

In order to upgrade to a newer version, the existing Veritas

Backup Reporter View Builder will be removed.





Note: Ensure that the installation directory that you specify has adequatespace by going through the Disk space requirements section on this page.A green checkmark appears in the Required column if there is adequate diskspace.


10 The installer shows a summary of the settings that you have selected forSymantec OpsCenter View Builder installation.


11 Click Install.

The installer starts installation of Symantec OpsCenter View Builder.


13 Click Finish.

Upgrading fromVeritas BackupReporter toOpsCenter onUNIXUse the following procedure to upgrade from Veritas Backup Reporter Server andAgent to Symantec OpsCenter Server and Agent respectively.

Upgrading from Veritas Backup Reporter to OpsCenter Server on UNIX

Use the following procedure to upgrade from Veritas Backup Reporter Server toSymantec OpsCenter Server on UNIX.

To upgrade from VBR Server to OpsCenter Server on UNIX





172


■ If you use the OpsCenter DVD to install OpsCenter, go to the appropriateOpsCenter platform directory and then the Server directory.


cd OpsCenter/Server



6 The installer then checks for an existing VBR installation. It displays thefollowing message when VBR is installed:

Veritas Backup Reporter (VBR) <version>

is installed on <hostname>. Do you want to upgrade

from VBR <version> to Symantec OpsCenter [y,n,q] y

To upgrade to Symantec OpsCenter, type y and then press Enter.

7 The following message is displayed:

The existing VBR database and configuration files must

be backed up before upgrading to Symantec OpsCenter.

Where should the VBR database and configuration files be

backed up? An OpsCenter_save directory will be created

within the directory that you specify to store these

files. (/var/symantec)

Type the directory name in which you want to save the VBR database andconfiguration files and then press Enter.

To save the VBR database and configuration files in the default directorypath (/var/symantec), press Enter only.


9 Type a directory path where you want to install the Symantec OpsCenterServer packages and press Enter.


10 Type y to confirm the installation directory path and press Enter.

If any older version of packages like VRTSpbx is detected, it is automaticallyuninstalled and the required version is installed.




The script creates the folder OpsCenterServer below the directory that youspecify.



The OpsCenter database server may require

up to 1 GB of temporary space at runtime.

By default, temporary files will be created in the

database installation directory,/var/Symantec/OpsCenterServer


Would you like to use an alternate directory

for database server temporary space? [y,n,q] (n)

Type y and press Enter to specify an alternate directory for the databaseserver temporary space. Specify the directory location when prompted. Reviewthe installation options that you selected (database and database tempdirectory locations). Type y and then press Enter.


Review the installation options that you selected (database and database tempdirectory locations). Type y and then press Enter.

13 Configuration changes are performed. You are prompted with the followingmessage:

The old database will be started separately

to migrate its data to the OpsCenter database. Specify

a port number on which the old database can be started (13799)

Type a port number on which the old VBR database can be started and pressEnter.

To accept the default port number (13799), press Enter only.

Note: Ensure that the port number that you enter is free and not used by anyapplication.


174


An older license key has been detected. Press

<Return> to use the existing key. Do you want to enter

a new key?<Enter one key at a time

if there are multiple keys:

To use a new key, type the license key and press Enter.

To use the existing key, press Enter only.

15 All the OpsCenter processes are started.

The following information is also displayed:

■ Web URL to access OpsCenter console.

■ Location of install log, summary, and response files.

■ Link on the OpsCenter logon page from where you can access the datamigration status

Upgrading from Veritas Backup Reporter Agent to OpsCenter Agent onUNIX

Use the following procedure to upgrade a VBR agent to an OpsCenter agent onUNIX.

You do not require an OpsCenterAgent to collect data from NetBackup 7.0 orPureDisk. However, you must install OpsCenter Agent if you want to collect datafrom other backup products.

Note: Once you upgrade your VBR Agent to the OpsCenter Agent, the port thatthe VBR Agent uses is not required in OpsCenter. The default port that the VBRAgent uses is 7806.

To upgrade a VBR Agent to OpsCenter Agent on UNIX


2 Mount the appropriate OpsCenter product DVD for the platform on whichyou are installing OpsCenter software.




■ If you use the OpsCenter DVD to install OpsCenter, go to the appropriateOpsCenter platform directory and then the Agent directory.


cd OpsCenter/Agent

4 Type the following command:



6 The installer displays a list of components that get installed like PBX,Symantec WebGUI Agent etc. Review this list and press Enter to continue.

7 It is optional to configure OpsCenter Agent during installation. You maychoose to configure OpsCenter Agent later either manually or by running./opt/VRTS/install/installOpsCenterAgent -configurecommand.

To configure OpsCenterAgent now, type y and press Enter.

8 Enter the location where you want to install OpsCenter Agent.

Type a directory path where you want to install the Symantec OpsCenterAgent packages and press Enter.


9 Type y and then press Enter to confirm your installation options.

10 The OpsCenter Agent is installed. You can view the installation log files,summary, and response files on the path mentioned.

About VBR upgrade considerationsAfter upgrading from VBR to OpsCenter server, data is not displayed underMonitor > Devices, Manage > Storage, and Manage > Devices. After a VBRupgrade, data is not displayed under the Storage and Devices tabs in Monitoring.(Storage units, Robots, Drives, and so forth.)

The data is not displayed as VBR does not collect any monitoring data, only thenames are provided from the job records. This data is collected from the masterserver after the upgrade as part of the regular data collection.

Troubleshootingdatabase inconsistency issuesduringupgradeThe upgrade process may fail due to database inconsistency when you upgradefrom VBR to OpsCenter server. Additional information may be displayed in the


176

ServerService_<timestamp>.log file. This file is located in<INSTALL_PATH>\OpsCenter\server\logs directory on Windows and/<INSTALL_PATH>/SYMCOpsCenterServer/logsdirectory on Solaris. For example,the log file may display the following message:

"Database schema is inconsistent with released schema <reason>"

This message generally appears when you have modified the VBR database schemalike added, modified, or removed columns or constraints from the VBR databasetables. To resolve this issue, you must manually undo the modifications that youhave made to the database so that the database schema is similar to the releasedversion.

To resolve database inconsistency errors

1 Modify the database as per the message in the ServerService_<timestamp>.logfile. This file is located in<INSTALL_PATH>\OpsCenter\server\logsdirectoryon Windows and /<INSTALL_PATH>/SYMCOpsCenterServer/logs directoryon Solaris.

2 Copy the modified ccsvc.db and ccsvc.log files from VBR database to thefollowing directory on the OpsCenter server:

For Windows: <INSTALL_PATH>\server\db\upgrade\data

For Solaris: <INSTALL_PATH>/SYMCOpsCenterServer/db/upgrade/data

3 Upgrade to OpsCenter server again.

See “Upgrading from Veritas Backup Reporter to OpsCenter Analytics onWindows and UNIX” on page 166.

Monitoring data migration from NOM to Symantec OpsCenterWhen you upgrade from NOM to OpsCenter server, the OpsCenter InstallationWizard automatically detects an older NOM installation. The OpsCenter installeronly stops the existing NOM services. It does not uninstall your existing NOMinstallation. You can manually uninstall NOM after successfully migrating dataand using Symantec OpsCenter for some time. During upgrade, the OpsCenterserver is installed, the older NOM database is saved and started. Data migrationfrom the older NOM database to the new OpsCenter database starts once theSymantec OpsCenter Server Service is started while installing OpsCenter server.

The data migration process may take time depending on the volume of data thathas to be migrated. The following sections describe the data migration processfrom NOM to Symantec OpsCenter in detail.


About upgrading the NOM database to Symantec OpsCenterThe data migration from the NOM database to the Symantec OpsCenter databasestarts once the Symantec OpsCenter Server Service is started while installingOpsCenter server.

Review the following considerations for data migration to Symantec OpsCenter:

■ For NOM versions less than 6.5.4, the database is first upgraded to NOM 6.5.4database. The NOM 6.5.4 database is then upgraded to the OpsCenter database.

■ For NOM 6.5.4 and later versions, the database is upgraded directly to theOpsCenter database.

The data migration from NOM 6.5.4 to the OpsCenter database occurs in threestages. In the first stage, data that is specific to NOM is migrated to the OpsCenterdatabase. The NOM data comprises of alerts, alert policies, users, domains, servergroups etc.

Note: You must create new alert policies in OpsCenter only after alert migrationis complete.

Table 3-9 gives details about the NOM data that is migrated and how it appearsin OpsCenter.

Table 3-9 NOM data migration

Data in OpsCenterNOM data that is migrated

Metadata about the managed master serversfrom NOM is migrated to OpsCenter.

Once this data has been migrated toOpsCenter, you can view this data fromSettings>Configuration>NetBackup pagein the OpsCenter console.

Master server metadata


178

Table 3-9 NOM data migration (continued)


The NOM users take the following user rolesin OpsCenter:

■ The admin user in NOM is the SecurityAdministrator in Symantec OpsCenter.

■ A normal NOM user is the Administratorin OpsCenter.

■ A read-only NOM user is the Operator inOpsCenter.

The NOM admin user ofNOM_BuiltIn@hostname domain must logon to OpsCenter using theOpsCenterUsers(vx) domain. Users ofother NOM domains can continue using theirrespective domains in OpsCenter.

Once this data has been migrated toOpsCenter, you can view this data from theSettings > Users page in the OpsCenterconsole.

User information and domains

All recipients and recipient groups aremigrated from NOM to OpsCenter.

Once the recipients have been migrated toOpsCenter, you can view this data from theSettings > Recipients page (both Email andSNMP subtabs) in the OpsCenter console.

Note: Recipient groups are not supportedin OpsCenter. Even though recipient groupsare migrated to the OpsCenter database, theOpsCenter console does not display recipientgroups.

Email and trap recipients




The main (root) server, policy, or client nodeis mapped to the ALL MASTER SERVERSview. For each NOM user, three trees arecreated - PrivateTree_Server,PrivateTree_Client, and PrivateTree_Policytrees.

The OpsCenter console displays all views inthe drop-down list of the View Pane.

Public and Private groups are migrated asnodes. A small group of master servers,policies, or clients are nodes in OpsCenter.

A single host, policy, or client is an object inthe View Pane.

Public and Private Groups


180



Saved Reports




The following reports (and the schedulesthat are created for these reports) from NOMare not migrated to OpsCenter:

■ Jobs Scheduled to Run

■ Drive Usage

■ Cycle Dashboard

■ Cycle Dashboard by Job Type

■ Cycle Dashboard by media server

■ Running versus Queued Jobs

■ Job Summary by Client

■ Rolling 8 day summary

■ Rolling 8 day summary by media server

■ Window Utilization by Policy

User-created composite reports in NOM aremigrated as dashboard reports. Once thesereports have been migrated, you can viewthem from Reports > My Dashboard in theOpsCenter console.

User-created reports in NOM (both Publicand Private) are migrated as custom SQLqueries. If you edit these reports inOpsCenter, you can directly edit SQL queriesfor these reports.

Note: To edit custom SQL reports inOpsCenter, you must have a licensed versionof OpsCenter (OpsCenter Analytics).

All private graphical reports in NOM becometabular in OpsCenter.

The concept of saving a report in NOM isdifferent than OpsCenter. User must providevalues for all the filters like Client Name,Policy Name etc. before you save a report inOpsCenter. In NOM, a user provides valuesfor filters while running a report. Henceafter migration is complete, these reportsget default values for filters in OpsCenter.For example if you migrate a Skipped Filesdetails for client report for a specific clientlike nom-ut6 from NOM, then in OpsCenter


182



the report is configured to run on all theclients (instead of only nom-ut6). TheWHERE clause of the OpsCenter SQL queryhas "IS NOT NULL" value.

Shortcuts to reports are not migrated.Shortcuts to reports are not supported inOpsCenter.

You need to manually configure My Portalagain using OpsCenter reports.

All alert policies and alerts are migratedfrom NOM to OpsCenter.

You must create new alert policies inOpsCenter only after alert migration iscomplete.

To see if alert policies have been migrated,see the Data Migration Status page.

Alert Policies and alerts

After the NOM data has been migrated, the second stage of data migration begins.Note that in the second stage of data migration, data is migrated per master server.

In the second stage, the following data is migrated for each master server:

■ Media server

■ Client

■ Storage Unit

■ Volume group

■ Volume Pool

■ Robot

■ Drives

■ Services

■ Catalog

■ License

■ Storage Service

■ FSM


■ DSM

■ FT

■ Policy (includes policy versions)

■ Media

■ Jobs (last 30 days)

Once all this data for each master servers (including jobs data for the last 30 days)has been migrated to the OpsCenter database, data collection for each masterserver is enabled automatically. The status for the specific master server is shownas Last 30 Days Jobs Migrated on the Data Migration status page. At this point,fresh data collection from the master server begins and you can start using theMonitor and Manage tabs of the OpsCenter console.

Note: If data collection for a master server was disabled in NOM, then datacollection for the specific master server remains disabled after you upgrade toOpsCenter. In such a case, data collection is not enabled automatically aftermigration.

In the third stage of data migration, the following data is migrated:

Jobs data older than 30 days is migrated foreach master server.

Jobs older than 30 days


184

The concept of report schedules is differentin NOM and OpsCenter. While creatingschedule for a report in OpsCenter, you onlyneed to specify the schedule details like timeetc. However when you create a schedule inNOM, you provide the schedule details aswell as filter values.

The following steps are performed in thespecified sequence to migrate scheduledreports from NOM to OpsCenter:

■ The schedule is saved separately in theOpsCenter database

■ The report filter values are inserted inthe report definition

■ The report is saved again.

In case a standard report is scheduled inNOM, the report is first saved under Reports> My Reports and then the schedule isattached to it. For example, if a standardreport like Available Media is scheduled inNOM, then the standard report is saved inOpsCenter under Reports>MyReports viewand the schedule is then attached to thisreport.

Note: Reports that come with NOM and arecomposite reports (containing more thanone report). Schedules for composite reportsare not migrated. Example, Full MediaCapacity, Restore Job Summary etc.

Report Schedules

You can work in the OpsCenter console while this data is migrated in thebackground.

Note: All NOM user preferences like column settings, SORD value etc. are notmigrated to OpsCenter.

What happens when data migration is interruptedData migration can be interrupted due to many reasons, like network issues,stopping services on the OpsCenter server etc.

We can have the following upgrade scenarios:


■ For NOM versions less than 6.5.4, the database is first upgraded to NOM 6.5.4database. The NOM 6.5.4 database is then upgraded to the OpsCenter database.

■ For NOM 6.5.4 and later versions, the database is upgraded directly to theOpsCenter database.

Based on the upgrade scenarios, the data migration process can either beinterrupted when upgrade to NOM 6.5.4 database is in progress (this happenswhen a NOM version less than 6.5.4 is being upgraded to OpsCenter) or whenupgrade from NOM 6.5.4 database to the OpsCenter database is in progress.

Table 3-10 explains the specific scenarios and what happens when data migrationis interrupted in these scenarios.

Table 3-10 What happens when data migration is interrupted

Migration statusScenario

In this case, data migration automaticallyrestarts from the beginning.

Data migration is interrupted when a NOMdatabase (NOM version lower than 6.5.4) isbeing upgraded to the NOM 6.5.4 database.

In this case, data migration resumes fromthe last checkpoint automatically. The datathat had already been migrated does notneed to be migrated again.

Note: The data migration for the followingentities does not resume from the lastcheckpoint and needs to be migrated again- Recipient, User, Reports, Groups, Robot,Services, DSM, License feature history,report schedules, and alert policy.

Data migration is interrupted when data ismigrated from NOM 6.5.4 to the OpsCenterdatabase.

Viewing the data migration statusYou can also view the data migration status using the OpsCenter console.

To view the data migration status

1 Access the data migration status page by doing any of the following:

■ In the Web browser address bar, enter the following:http://<host.domain>/opscenter/dbUpgradeStatus.do<host.domain> is the FQDN (Fully Qualified Domain Name) or IP addressof the OpsCenter Server host.


186

Note: By default, OpsCenter tries to run on port 80 (HTTP). If port 80 isnot available, OpsCenter can use a different port. To know the HTTP andHTTPS port that OpsCenter uses, run the configurePorts utility. RunINSTALL_PATH\OpsCenter\gui\bin\goodies\configurePorts.bat

-status on Windows hosts or/opt/SYMCOpsCenterWebGUI/bin/goodies/configurePorts.sh -status

on UNIX hosts. For example, if OpsCenter uses HTTP port 8181, then usehttp://<server-host>:8181/opscenter/dbUpgradeStatus.do.

You can also use the URL that is presented at the end of the OpsCenterserver installation and append /dbUpgradeStatus.do after the URL toaccess the data migration page at any point in time.

■ On the OpsCenter logon page, use the Click here to see migration statuslink as shown in the following figure. The link is located at the bottom ofthe logon page on the right-hand side.This link automatically disappears when the data migration is complete.

The data migration status is displayed as shown in the following figure:


The data migration status comprises Entity Migration Status and MasterServer Entity Migration Status.

The Entity Migration Status tab shows the following columns (along withthe migration summary):

Displays the name of the database entity,like master server , Alert Policy, Policy data(number of records) that are being migratedto OpsCenter.

Entity

The total number of records of an entity thatneed to be migrated from NOM to SymantecOpsCenter.

Total Records


188

Number of records of an entity that havebeen migrated to Symantec OpsCenter, as ofnow

Note: Migrated records are the number ofrows in tables. This does not necessarilymean that these many records for thespecific entity will be shown on theOpsCenter console.

For example, the migrated records forpolicies include policies as well as policyversions that are associated with it. Also thenumber of migrated recipients includesrecipients as well as recipient groups.However, recipient groups are not shown onthe OpsCenter console as they are notsupported by OpsCenter.

Migrated Records

The number of records that were skippedduring data migration because of thefollowing possible reasons:

■ The data was in an inconsistent stateduring upgrade. Such records arecollected once the OpsCenter serverstarts.

■ NOM data that is not migrated is alsoshown as Skipped Records. For example,NOM standard reports like CycleDashboard and also schedules for suchstandard reports (if any) are shown asskipped records.

Skipped Records

2 Click the Master Server Entity Migration Status tab to view the details ofentities that are migrated per master server. This is shown in the followingfigure:


This page shows the number of records that have been migrated for eachmaster server. It also shows the time that is required for migrating thosemany records.

The Entity Migration Status tab shows the following columns (in additionto the migration summary):

Displays the name of the master server thatis being migrated to OpsCenter.

Server Name


190

The migration status for the respectivemaster server.

The following migration status is possiblefor a master server:

NotStarted: Data Migration has not startedfor this master server

In Progress:: Entities for this master serverare being migrated from NOM to OpsCenter

Last30DaysJobsMigrated: This means thatthe second stage of data migration iscomplete for the specific master server. Thisstatus indicates that entities like policies,media, and jobs for the last 30 days havebeen migrated to OpsCenter and datacollection in OpsCenter has been enabled forthe selected master server. Because datacollection has been enabled, the OpsCenterserver starts collecting fresh data from thespecific master server. You can start usingthe Monitor and Manage views of theOpsCenter console at this point.

Note: If data collection for a master serverwas disabled in NOM, then data collectionfor the specific master server remainsdisabled after migration.

Completed: Entities for this master serverhave been migrated from NOM to OpsCenter

Failed: Entities for this master server cannotbe migrated from NOM to OpsCenter.

Status

The total number of records for each masterserver that need to be migrated from NOMto Symantec OpsCenter.

Total Records


Number of records for each master serverthat have been migrated to SymantecOpsCenter, as of now


For example, the migrated records forpolicies include policies as well as policyversions that are associated with it. Also thenumber of migrated recipients includesrecipients as well as recipient groups.However, recipient groups are not shown onthe OpsCenter console as OpsCenter doesnot support recipient groups.

Migrated Records

Number of records for each master serverthat were skipped during data migrationbecause of the following possible reasons:

■ The data was in an inconsistent stateduring upgrade. Such records arecollected once the OpsCenter serverstarts.

■ NOM data that is not migrated is alsoshown as Skipped Records. For example,NOM standard reports like CycleDashboard and also schedules for suchstandard reports (if any) are shown asskipped records.

Skipped Records

Monitoring data migration from VBR to Symantec OpsCenter AnalyticsWhen you upgrade from VBR to OpsCenter Analytics, the OpsCenter InstallationWizard automatically detects an older VBR installation. The OpsCenter installeronly stops the existing VBR services. It does not uninstall your existing VBRinstallation. You can manually uninstall VBR after successfully migrating dataand using Symantec OpsCenter for some time. However, do not uninstall VBRserver after upgrading to OpsCenter server software on a Windows platform. Readthe following TechAlert if you want to uninstall VBR on Windows:



192


During upgrade, the OpsCenter server is installed and the older VBR database issaved and started. The data migration from the older VBR database to the newOpsCenter database starts once the Symantec OpsCenter Server Service is startedwhile installing OpsCenter server.

The data migration process may take time depending on the amount of data thathas to be migrated. The following sections describe the data migration processfrom VBR to OpsCenter Analytics.

About upgrading the VBR database to Symantec OpsCenterAnalyticsThe data migration from the VBR database to the Symantec OpsCenter databasestarts once the Symantec OpsCenter Server Service is started while installingOpsCenter server.

Review the following considerations for data migration:

■ For VBR 6.5, 6.5.1, and 6.5.1.1 versions, the database is first upgraded to theVBR 6.6 database. The VBR 6.6 database is then upgraded to the OpsCenterdatabase.

■ For VBR 6.6 and later versions, the database is upgraded directly to theOpsCenter database.

The data migration from VBR 6.6 to the OpsCenter database occurs in the followingstages:

■ First stage in which VBR metadata and backup data is migrated from VBR tothe OpsCenter database.The VBR metadata comprises of data related to alert policies, users, domains,views, SMTP server, and data purge settings etc. The backup data consists ofentities like policy, media, devices etc. For entities like jobs, media history,scheduled jobs, and images, data for the last 30 days is migrated in this stage.

■ Second stage in which Symantec Enterprise Vault archive data and report datais migrated.

■ Third stage in which backup data older than 30 days (for NetBackup, BackupExec, PureDisk, TSM, Legato Networker) is migrated from VBR to OpsCenterfor each master server.

Table 3-11 gives details about the VBR metadata that is migrated in the first stageand how it appears in OpsCenter.


Table 3-11 VBR metadata migration in the first stage

Data in OpsCenterVBR data that is migrated

The Agents and data collectors that you haveconfigured in VBR are migrated toOpsCenter.

Once this data has been migrated toOpsCenter, the NetBackup agents andNetBackup data collectors can be viewedfrom Settings>Configuration>NetBackupin the OpsCenter console. The agents anddata collectors for all products other thanNetBackup can be viewed from Settings >Configuration > Agents in the OpsCenterconsole.

Agent and Data Collectors

Data related to master servers, mediaservers, clients, file systems, and EVarchive-related information like vault server, Exchange Server is migrated to OpsCenter.

Note: Only those master servers, mediaservers, and clients that have job data aremigrated to OpsCenter.

Objects


194

Table 3-11 VBR metadata migration in the first stage (continued)


The VBR users take the following user rolesin OpsCenter:

■ The Administrator in VBR is the SecurityAdministrator in Symantec OpsCenter.

■ A read-only VBR Administrator is theAnalyst in OpsCenter.

■ A normal VBR user is the Reporter inOpsCenter.

The users on the cc_users@hostnamedomaincan continue using the same domain inOpsCenter. Users of other domains can alsocontinue using their respective domains.

Note: Only the VBR default user(admin@cc_users) must log on usingOpsCenterUsers (vx) domain. All settings ofthe default admin user are now associatedwith the admin user of OpsCenterUsers(vx)domain.

Once this data has been migrated toOpsCenter, you can view this data from theSettings > Users page in the OpsCenterconsole.

User information and domains

All recipients and recipient groups aremigrated from VBR to OpsCenter.

Once this data has been migrated toOpsCenter, you can view this data from theSettings > Recipients page (both Email andSNMP subtabs) in the OpsCenter console.

Note: Recipient groups are not supportedin OpsCenter. Even though recipient groupsare migrated to the OpsCenter database, therecipient groups are not displayed in theOpsCenter console.

Email and trap recipients

All views from VBR are migrated toOpsCenter as client-type views.

Once this data has been migrated toOpsCenter, you can see these views in theView Pane of the OpsCenter console.

Views


Table 3-11 VBR metadata migration in the first stage (continued)


You must create new alert policies inOpsCenter only after alert policy migrationis complete.

To see if alert policies have been migrated,see the Data Migration Status page.

See “Viewing the data migration status”on page 200.

Note: Alerts from VBR are not migrated toOpsCenter.

Alert Policies

After the VBR metadata is migrated, backup data (for NetBackup, Backup Exec,PureDisk, IBM TSM, EMC Legato Networker) is migrated per master server.

The following data is migrated as a part of backup data for each master server:

■ Policy

■ Devices (tape libraries , Tape drives, Disk pools etc.)

■ Data Classification

■ MediaMedia History (Last 30 days)

■ Jobs (Last 30 days)

■ Scheduled jobs (Last 30 days)

■ Images (Last 30 days)

Once all this data (including jobs data for the last 30 days) has been migrated tothe OpsCenter database for each master server, data collection for each masterserver is enabled automatically. The status for the specific master server is shownas Last 30 Days Jobs Migrated on the Data Migration status page.

At this point, fresh data collection from the master server begins and you canstart using the Monitor,Manage, and Reports tabs of the OpsCenter console.

Note: If data collection for a master server was disabled in VBR, then data collectionfor the specific master server remains disabled after upgrading to OpsCenterAnalytics. In such a case, data collection is not enabled automatically aftermigration.


196

After the first stage of data migration is complete, the second stage of datamigration begins. In the second stage of data migration, Symantec EnterpriseVault archive data is migrated followed by report data.

The following data is migrated as Symantec Enterprise Vault archive data in thesecond stage:

■ Archive policy (migrated per site)

■ Exchange server (migrated per site)

■ Vault server (migrated per site)

■ Retention category

■ Provisioning Group

■ Vault Store

■ Vault partition

■ Vault and Savesets

After the archive data migration is complete, report data is migrated in the secondstage.

Table 3-12 gives details about the report data that is migrated and how it appearsin OpsCenter.


Table 3-12 VBR report data migration in the second stage

Data in OpsCenter AnalyticsVBR data that is migrated

After migration is complete, you can viewthe My Backup Reports folder under PrivateReports tree. Earlier in VBR, the My BackupReports folder was under My Saved Reportsfolder.

Custom SQL and Stored Custom SQL reportsare not migrated to Symantec OpsCenter.

Custom chargeback reports that you havecreated in VBR are not migrated toOpsCenter.

The following VBR reports are not migratedto OpsCenter:

■ Master Server Count

■ NetBackup Storage Lifecycle Map

■ Success Rate vs. Amount Backed Up

■ Success Rate vs. Client Count

■ Success Rate vs. Job Count

■ Success Rate vs. File Count

■ Active Job Count

■ Tape Used Capacity By Retention Level

■ Tape Count Trends by Retention Level

■ Tape Count Trends by Volume Pool

■ Recovery Reports

■ Asset Reports

Reports

All VBR chargeback variables and formulaeare migrated to OpsCenter.

Once this data has been migrated, thechargeback variables and formulae can beviewed from Settings >Chargeback view inthe OpsCenter console.

Chargeback variables and formulas

All report schedules are migrated from VBRto OpsCenter.

Report schedules

After the second stage of data migration is complete, the third stage of datamigration begins. In the third stage of data migration, the backup data that remainsto be migrated in the first stage (data older than 30 days) is migrated for eachmaster server.


198

The following data is migrated in the third stage for each master server:

■ Media History (Older than 30 days)

■ Disk Pool history (Older than 30 days)

■ Jobs (Older than 30 days)

■ Scheduled jobs (Older than 30 days)

■ Images (Older than 30 days)

If you upgrade from VBR versions lower than 6.6 to OpsCenter Analytics, youneed to configure the following after data migration is complete:

■ SMTP server settings. The VBR SMTP server settings are not migrated toOpsCenter.

What happens when data migration is interruptedData migration can be interrupted due to many reasons, like network issues,accidental shutdown of OpsCenter server, stopping services on the OpsCenterserver etc.

We can have the following upgrade scenarios:

■ For VBR 6.5, 6.5.1, and 6.5.1.1 versions, the database is first upgraded to theVBR 6.6 database. The VBR 6.6 database is then upgraded to the OpsCenterdatabase.

■ For VBR 6.6 and later versions, the database is upgraded directly to theOpsCenter database.

Based on the upgrade scenarios, the data migration process can either beinterrupted when upgrade to VBR 6.6 database is in progress (this happens whena VBR version less than 6.6 is upgraded to OpsCenter Analytics) or when upgradefrom VBR 6.6 database to the OpsCenter database is in progress.

Table 3-10 explains the specific scenarios and what happens when data migrationis interrupted in these scenarios.

Table 3-13 What happens when data migration is interrupted


In this case, data migration automaticallyrestarts from the beginning.

Data migration is interrupted when a VBRdatabase (VBR version lower than 6.6) isbeing upgraded to the VBR 6.6 database.


Table 3-13 What happens when data migration is interrupted (continued)


In this case, data migration resumes fromthe last checkpoint automatically. The datathat had already been migrated does notneed to be migrated again.

Note: The data migration for the followingentities does not resume from the lastcheckpoint and is migrated again - list ofclients and file systems, reports.

Data migration is interrupted when data isbeing migrated from VBR 6.6 to theOpsCenter database.

Viewing the data migration statusYou can also view the data migration status using the OpsCenter console.

To view the data migration status

1 Access the data migration status page by doing any of the following:

■ In the Web browser address bar, enter the following:http://<host.domain>/opscenter/dbUpgradeStatus.do<host.domain> is the FQDN (Fully Qualified Domain Name) or IP addressof the OpsCenter Server host.

Note: By default, OpsCenter tries to run on port 80 (HTTP). If port 80 isnot available, OpsCenter can use a different port. To know the HTTP andHTTPS port that OpsCenter uses, run the configurePorts utility. RunINSTALL_PATH\OpsCenter\gui\bin\goodies\configurePorts.bat

-status on Windows hosts or/opt/SYMCOpsCenterWebGUI/bin/goodies/configurePorts.sh -status

on UNIX hosts. For example, if OpsCenter uses HTTP port 8181, then usehttp://<host.domain>:8181/opscenter/dbUpgradeStatus.do to accessthe data migration page at any point in time.

You can also use the URL that is presented at the end of the OpsCenterserver installation and append /dbUpgradeStatus.do after the URL toaccess the data migration page at any point in time.

■ On the OpsCenter logon page, use the Click here to see migration statuslink as shown in the following figure. The link is located at the bottom ofthe logon page on the right-hand side.This link automatically disappears when the data migration is complete.


200

The data migration status is displayed as shown in the following figure:


The data migration status contains Entity Migration Status and MasterServer Entity Migration Status tabs.

The Entity Migration Status tab shows the following columns (along withthe migration summary):

Displays the name of the database entity,such as Alert Policy, Policy, Disk Pool, Jobsetc. that is being migrated to OpsCenterAnalytics.

Entity

The total number of records of an entity thatneed to be migrated from VBR to SymantecOpsCenter Analytics.

Total Records


202

Number of records of an entity that havebeen migrated to Symantec OpsCenter, as ofnow


For example, the migrated records forpolicies include policies as well as policyversions that are associated with it. Also thenumber of migrated recipients includesrecipients as well as recipient groups.However, recipient groups are not shown onthe OpsCenter console as they are notsupported in OpsCenter.

Migrated Records

Number of the records that were skippedduring data migration because of thefollowing possible reason:

■ The data was in an inconsistent stateduring upgrade. Such records arecollected once the OpsCenter serverstarts (if they are present in theNetBackup host) .

■ VBR data that is not migrated is alsoshown as Skipped Records. For example,VBR alerts are shown as skipped records.

Skipped Records

2 Click the Master Server Entity Migration Status tab to view the details ofentities that are migrated for each master server. The following figure showsa sample view of the Master Server Entity Migration Status tab:


This page shows the number of records that have been migrated for eachmaster server. It also shows the time that is required for migrating thosemany records.

The Entity Migration Status tab shows the following columns (along withmigration summary):

Displays the name of the database entity,such as master server , Alert Policy, Policydata (number of records) that has beenmigrated to OpsCenter.

Server Name


204

The migration status for the respectivemaster server.

The following migration status are possiblefor a master server:

NotStarted: The data migration process forthe master server has not started.

In Progress: Entities for this master serverare being migrated from VBR to OpsCenterAnalytics.

Last30DaysJobsMigrated: This means thatthe first stage of data migration is completefor the specific master server. This statusindicates that entities like policies, media,and jobs for the last 30 days have beenmigrated to OpsCenter Analytics and datacollection in OpsCenter Analytics has beenenabled for the selected master server.Because data collection has been enabled,the OpsCenter server starts collecting freshdata from the specific master server. Youcan start using the Monitor and Manageviews of the OpsCenter Analytics console atthis point.

Note: If data collection for a master serverwas disabled in VBR, then data collection forthe specific master server remains disabledafter migration.

Completed: Entities for this master serverhave been migrated from VBR to OpsCenterAnalytics

Failed: Entities for this master server cannotbe migrated from VBR to OpsCenterAnalytics.

Status

The total number of records for each masterserver that need to be migrated to SymantecOpsCenter Analytics from VBR.

Total Records


Number of records for each master serverthat have been migrated to SymantecOpsCenter, as of now


For example, the migrated records forpolicies include policies as well as policyversions associated with it. Also the numberof migrated recipients includes recipients aswell as recipient groups. However, recipientgroups are not shown on the OpsCenterconsole as OpsCenter does not supportrecipient groups.

Migrated Records

Number of records for each master serverthat were skipped during data migrationbecause of the following possible reasons:

■ The data was in an inconsistent stateduring upgrade. Such records arecollected once the OpsCenter serverstarts (if they are present in theNetBackup host).

■ VBR data that is not migrated is alsoshown as Skipped Records. For example,VBR alerts are shown as skipped records.

Skipped Records

Upgrading to OpsCenter Server on a different UNIX systemThis section explains how you can upgrade from NOM or VBR to OpsCenter serversoftware on a different UNIX system. An example scenario is when NOM or VBRis running on Solaris 8 and you require the same data with OpsCenter on Solaris10.

Note: Manual upgrades are not supported for Windows platforms.

Note the following points before you upgrade from NOM or VBR to Opscenterserver software on a different UNIX system:


206

■ Manual upgrades are supported only within the UNIX family. For example,you can upgrade from Solaris 8 to Solaris 10 but you cannot upgrade from aWindows platform to Solaris 10.

■ Manual upgrades are supported only within a particular OS family. For example,you can upgrade from Solaris 8 to Solaris 10 but you cannot upgrade fromRHEL 4.0 to Solaris 10.

■ Manual upgrade from NOM to OpsCenter server is supported from specificNOM platforms. Ensure that NOM is running on the following platforms:

■ Linux RHEL 4.0, 5.0, 64-bit

■ Solaris SPARC 9.0, 10.0, 64-bit

■ Solaris x86 10.0, 64-bit

For example, you can upgrade from NOM running on Solaris SPARC 9 (64-bit)to OpsCenter server running on Solaris SPARC 10 (64-bit).

■ Manual upgrade from VBR to OpsCenter server is supported on Solarisplatforms. For example, you can upgrade from VBR running on Solaris 8 toOpsCenter server running on Solaris 10.

Use the following procedure to upgrade to OpsCenter server software on a differentUNIX system.

The procedure basically involves the following steps:

■ Back up your NOM or VBR database and configuration files using Backup.sh

utility on your old NOM or VBR server.See “Backing up your data on the NOM or VBR server” on page 207.

■ Copy this data from the old server to the server where you plan to installOpsCenter server.Install the OpsCenter server software and restore the NOM or VBR data usingthe OpsCenter installer.See “Upgrading to OpsCenter server on the new system” on page 208.

Backing up your data on the NOM or VBR serverUse the following procedure to back up your database and configuration files onthe NOM or VBR server.


To back up the NOM or VBR database

1 Go to the NOM or VBR server and log on as root.

2 Mount the appropriate OpsCenter product DVD for the platform on whichyou are installing OpsCenter software.



■ If you use the OpsCenter DVD, go to the appropriate OpsCenter platformdirectory and then the Server directory.

■ If you use the NetBackup media kit, go to the following directory:

cd OpsCenter/Server

4 Run Backup.sh script. This script backs up the NOM or VBR database andconfiguration files on this system.

./Backup.sh

5 The script detects that you have NOM or VBR installed and prompts you forthe backup location:

You have <product> installed.

Please specify the backup location. A directory named

OpsCenter_save will be created within to store the data

[var/symantec]:

To back up the <product> data in a specific location, type a backup locationand press Enter.

To back up the<product>data in the default directory (/var/symantec), pressEnter.

A directory that is named OpsCenter_save is created in the backup locationthat you specify.

Upgrading to OpsCenter server on the new systemUse the following procedure to install OpsCenter server and restore the old VBRor NOM data on the new system.


208

To upgrade to OpsCenter server on the new system

1 Log on as root on the server where you want to install OpsCenter.

2 Copy the backed up NOM or VBR data (OpsCenter_save folder) from the olderNOM or VBR server to this server.




■ If you use the OpsCenter DVD to install OpsCenter server software,navigate to the appropriate OpsCenter platform directory and then theServer directory on the DVD.

■ If you use the NetBackup media kit to install OpsCenter, navigate to theServer directory.

cd OpsCenter/Server






Where do you want to install Symantec

OpsCenter? </opt>




























210

15 Once the configuration changes are completed, you are prompted with thefollowing question:

Do you want to restore data that has been

backed up manually [y,n,q] <n>

Type y and then press Enter.

16 You are prompted for the location of the backed up directory:

Please specify the directory that contains

the backed up data. <var/symantec>

Specify the location where you have copied the backed up data and pressEnter.

17 You are prompted with the following:

The old database will be started separately for

migrating its data to the OpsCenter database. Specify a port

number on which the old database can be started <13799>

To start the old database on port 13799, press Enter. Otherwise enter anyother port that is available and press Enter.

18 You are prompted for license information. Depending on whether older licensekeys are detected or not, the installer may prompt you with the following:


or press <Return>:

Enter a valid demo or permanent key that you have received with the purchaseof OpsCenter Analytics and press Enter.

If you do not enter a key, you get an unlicensed version. With the unlicensedversion, you cannot access the licensed features.




Post-installation tasksThe following sections explain how to start using OpsCenter and includes someperformance tuning tips for OpsCenter.

211Installing Symantec OpsCenter 7.0Post-installation tasks

Verifying that Symantec OpsCenter is running properlyAfter installing Symantec OpsCenter on either Windows or UNIX, perform a checkto verify that OpsCenter is running properly.

To verify that OpsCenter is running properly

1 Use the URL that is presented at the end of the OpsCenter Server installationto access the OpsCenter console.

Alternately type the following in the Web browser address bar:http://<server-host>/opscenter

Note: By default, OpsCenter tries to run on port 80 (HTTP). If port 80 is notavailable, OpsCenter can use a different port. To know the HTTP and HTTPSport that OpsCenter uses, run the configurePorts utility. RunINSTALL_PATH\OpsCenter\gui\bin\goodies\configurePorts.bat -status

on Windows hosts or/opt/SYMCOpsCenterWebGUI/bin/goodies/configurePorts.sh -statusonUNIX hosts. For example, if OpsCenter uses HTTP port 8181, then usehttp://<host.domain>:8181/opscenter.

If the OpsCenter logon screen appears, the OpsCenter Server, the Web server,and the authentication service are running.

The first time you log in, it takes longer than usual time for the GUI to load.

2 Log on as admin (user name) /password (password) on the private domain:

OpsCenterUsers(vx)

About starting to use OpsCenterAfter you complete the OpsCenter installation, you are ready to start using theOpsCenter console.

Table 3-14 lists the common tasks in OpsCenter and contains links to thecorresponding topics and descriptions.

Table 3-14 Links to get you started with OpsCenter

Topic DescriptionTopicTask

This topic provides instructions on how to accessthe console and log on, and provides solutions topossible issues.

See “About accessing theOpsCenter console” on page 37.

To access and log on to theOpsCenter console.

Installing Symantec OpsCenter 7.0Post-installation tasks

212

Table 3-14 Links to get you started with OpsCenter (continued)

Topic DescriptionTopicTask

For administrator initial logon, the user name isadmin and the password is password if you havechosen to keep the default password duringinstallation. After initial logon, it is recommendedthat you change the user name and password.

See “Changing your password”on page 299.

To change the passwordfor the administratorlogon.

This topic provides an overview of the consolecomponents.

See “About OpsCenter consolecomponents” on page 55.

To learn about theOpsCenter consolecomponents.

For instructions on understanding and using thevarious OpsCenter monitoring, managing, reporting,and settings views and related tasks, use theOpsCenter online Help .

See “About using the OpsCenterconsole” on page 34.

To learn more about usingthe OpsCenter console.

About the start-up tasks that OpsCenter performsOpsCenter performs the following tasks when it starts for the first time.

When OpsCenter starts, it performs the following tasks:

■ Creates and initializes the security domain that the authentication brokerrequires. If these security domains are present, OpsCenter uses them. Thefollowing domains namely OpsCenterUsers, OpsCenterServices, andNOM_MACHINES are created when OpsCenter server is installed.

■ Creates the OpsCenter admin user in the OpsCenterUsers domain with thedefault password as 'password'.

Tuning OpsCenter for more performanceThe following settings can be tuned to improve OpsCenter performance.

Note: The information that is published in this section is based on the tests thathave been performed in Symantec Lab in a controlled environment with expertusers. These can be used as guidelines and should not be used as 100% accuratebenchmarks.

About adding master servers to OpsCenterIf you need to add multiple master servers to the OpsCenter console, Symantecrecommends that you add five master servers at one time. For example, if you


have 20 master servers to be added, then you should not add all of them at once.Symantec recommends that you add them in groups of five in the following manner- 5+5+5+5. Once you add the first five master servers, wait until the initial datacollection for these master servers is complete. To view the data collection statusfor a master server, go to Settings>Configuration>NetBackup in the OpsCenterconsole and then click the Data Collection Status tab on the page. The datacollection status for a master server can be viewed from the Collection Statuscolumn.

About using a Web browser to access OpsCenterSymantec recommends that you use Mozilla Firefox to access the OpsCenterconsole. Performance testing indicates that Mozilla Firefox works 1.25 timesfaster than Microsoft Internet Explorer.

About installing OpsCenter on a Windows 64-bit platformSymantec recommends that you install the OpsCenter server software on asupported Windows 64-bit platform for optimum performance. Performancetesting indicates that OpsCenter runs fastest on a Windows 64-bit platform ascompared to other Windows or UNIX platforms.


About bandwidth utilizationThe following table lists the average bandwidth that is consumed when OpsCentercollects data from a master server.

Number of jobs per dayAverage Bandwidth used by OpsCenter

25004.67 Kbps

More than 10,00010.381 Kbps

Note: The system that was used for testing was a NetBackup 7.0 master serverrunning Windows 2003 on a Xeon-64 processor that has 2 GB RAM and 1.0 GbELAN connection.

About performance tuning guidelinesYou may want to tune OpsCenter to obtain incremental performance gains. Thissection describes important tuning parameters and settings that can result inimproved performance.


214

The following guidelines can help improve OpsCenter performance:

■ Install the OpsCenter database on a drive that is different from whereOpsCenter server software and operating system is installed.See “Moving the OpsCenter database to a different hard disk” on page 215.

■ Install the OpsCenter log files on a drive that is different from where OpsCenterserver software and operating system is installed. This should be done only ifthe logging level is greater than 1.See “Saving the OpsCenter log files on a different drive” on page 217.

■ Symantec recommends that you defragment the OpsCenter databaseperiodically. You must perform defragmentation once in a month.See “About OpsCenter database defragmentation” on page 221.

■ Increase the heap size of the OpsCenter Server in accordance with the RAM.See “Adjusting the heap size for OpsCenter components” on page 222.

■ Increase the database cache size in accordance with the RAM and databasesize.See “Adjusting the OpsCenter database cache size” on page 227.

■ Create report schedules such that the email or export happens in system idletime when OpsCenter is not accessed frequently.

■ Purge the OpsCenter data periodically.See “About purging data periodically” on page 229.

Moving the OpsCenter database to a different hard diskUse the following procedure to move the OpsCenter database to a different harddisk.

To move the OpsCenter database to a different hard disk on Windows

1 Stop all OpsCenter server services. Open the command line and enter thefollowing command:

INSTALL_PATH\OpsCenter\server\bin\opsadmin.bat stop

2 Open the databases.conf file with a text editor like notepad from thefollowing directory:

INSTALL_PATH\OpsCenter\server\db\conf

This file has the following contents:

"INSTALL_PATH\OpsCenter\server\db\data\vxpmdb.db"

This path specifies the default location of the OpsCenter database.


3 To move the database to a custom location like E:\Database, replace thecontents of the file with the following:

"E:\Database\vxpmdb.db"

Make sure that you specify the path in double quotes. Also the directories inthe specified path should not contain any special characters like %, ~, !, @, $,&, ^, # etc. For example, do not specify a path like E:\Database%.

Save the databases.conf file.

4 Copy the database file to the new location. Copy vxpmdb.db fromINSTALL_PATH\OpsCenter\server\db\data to a location like E:\Database.

5 Restart all OpsCenter server services.

To restart all OpsCenter services, enter the following command:INSTALL_PATH\OpsCenter\server\bin\opsadmin.bat start

You should run and monitor OpsCenter for a certain period after moving thedatabase. If OpsCenter works as expected, you can delete vxpmdb.db from thedefault location (INSTALL_PATH\OpsCenter\server\db\data).

To move the OpsCenter database to a different hard disk on UNIX

1 Stop all OpsCenter server processes. Enter the following command:

/opt/SYMCOpsCenterServer/bin/opsadmin.sh stop

2 The default location of the OpsCenter database is/opt/SYMCOpsCenterServer/db/data.

Back up the OpsCenter database (/opt/SYMCOpsCenterServer/db/data) tosome other location. Enter the following command:

cp –R /opt/SYMCOpsCenterServer/db/data /backup/data

3 To move the database to a custom location like /usr/mydata, first create thenew directory by entering the following command:

mkdir -p /usr/mydata

4 To move the database to a custom location like /usr/mydata,enter thefollowing command:

mv /opt/SYMCOpsCenterServer/db/data/* /usr/mydata

5 Remove the symbolic link that exists for the OpsCenter database. Enter thefollowing command:

unlink /opt/SYMCOpsCenterServer/db/data


216

6 Create a symbolic link to /usr/mydata in /opt/SYMCOpsCenterServer/db/data.To create a symbolic link, enter the following command:

ln -s /usr/mydata/data /opt/SYMCOpsCenterServer/db/data

7 Restart all OpsCenter server processes by entering the following command:

/opt/SYMCOpsCenterServer/bin/opsadmin.sh start

You should run and monitor OpsCenter for a certain period after moving thedatabase. If OpsCenter works as expected, you can delete vxpmdb.db from/backup/data.

Saving the OpsCenter log files on a different driveSymantec recommends that you install the OpsCenter log files on a drive that isdifferent from where OpsCenter server software and operating system is installed.This should be done only if the debug level of logs is greater than 1. The defaultdebug level of OpsCenter logs is 1.

To know the debug level of your logs, see the following section.

See “Checking the debug level of logs” on page 217.

You can control how OpsCenter writes log files for OpsCenter Server, OpsCenterAgent, and the OpsCenter Web GUI components.

See “Saving the log files to a different directory on Windows” on page 218.

See “Saving the log files to a different directory on UNIX” on page 220.

Checking the debug level of logs

You can check the debug level of OpsCenter logs by using the following procedure.


To check the debug level of logs

1 Navigate to the following location:

INSTALL_PATH\OpsCenter\server\bin\

or

INSTALL_PATH\OpsCenter\Agent\bin\

Windows

/opt/SYMCOpsCenterServer/bin

or

/opt/SYMCOpsCenterAgent/bin

UNIX


vxlogcfg -l -p 58330 -o <OID> -q

The following OID values must be used for OpsCenter components:

148OpsCenter Server

146OpsCenter Agent

147OpsCenter ViewBuilder

Saving the log files to a different directory on Windows

Use the following procedures to save the log files for OpsCenter components ina different directory.

By default, OpsCenter writes VxUL logs to the following directories:

INSTALL_PATH\OpsCenter\server\logsOpsCenter Server

INSTALL_PATH\OpsCenter\Agent\logsOpsCenter Agent

INSTALL_PATH\OpsCenter\gui\logsOpsCenter ViewBuilder


218

To save the log files for OpsCenter server in a different location

1 Enter the following command to save log files to a different location:

INSTALL_PATH\OpsCenter\server\bin\vxlogcfg -a –p 58330 -o 148 -s

LogDirectory="<New log directory location>"

Note:58330 is the OpsCenter product ID. 148 is the OID for OpsCenter server.

2 Select Control Panel > Administrative Tools > Services and stop theSymantec OpsCenter Server Service.

3 Select Control Panel > Administrative Tools > Services and start theSymantec OpsCenter Server Service.

To save the log files for OpsCenter Agent in a different location


INSTALL_PATH\OpsCenter\Agent\bin\vxlogcfg -a –p 58330 -o 146 -s


Note: 58330 is the OpsCenter product ID. 146 is the OID for OpsCenter Agent.

2 Select Control Panel > Administrative Tools > Services and stop theSymantec OpsCenter Agent Service.

3 Select Control Panel > Administrative Tools > Services and start theSymantec OpsCenter Agent Service.

To save the log files for OpsCenter Web GUI in a different location


INSTALL_PATH\OpsCenter\server\bin\vxlogcfg -a –p 58330 -o 147 -s


Note: 58330 is the OpsCenter product ID. 147 is the OID for OpsCenter WebGUI.

2 Select Control Panel > Administrative Tools > Services and stop theSymantec OpsCenter Web Server Service.

3 Select Control Panel > Administrative Tools > Services and start theSymantec OpsCenter Web Server Service.


Saving the log files to a different directory on UNIX

Use the following procedures to save the log files for OpsCenter components ina different location.

By default, OpsCenter writes VxUL logs to the following directories:

/opt/SYMCOpsCenterServer/logsOpsCenter Server

/opt/SYMCOpsCenterAgent/logsOpsCenter Agent

/opt/SYMCOpsCenterGUI/logsOpsCenter ViewBuilder

To save the log files for OpsCenter server in a different location


/opt/SYMCOpsCenterServer/bin/vxlogcfg -a -p 58330 -o 148 -s


Note:58330 is the OpsCenter product ID. 148 is the OID for OpsCenter server.

2 Enter the following command to stop the OpsCenter server process:

/opt/SYMCOpsCenterServer/bin/stopserver

3 Enter the following command to start the OpsCenter server process:

/opt/SYMCOpsCenterServer/bin/startserver

To save the log files for OpsCenter Agent in a different location


/opt/SYMCOpsCenterAgent/bin/vxlogcfg -a -p 58330 -o 146 -s


Note: 58330 is the OpsCenter product ID. 146 is the OID for OpsCenter Agent.

2 Enter the following command to stop the OpsCenter Agent process:

/opt/SYMCOpsCenterAgent/bin/stopagent

3 Enter the following command to start the OpsCenter server process:

/opt/SYMCOpsCenterAgent/bin/startagent


220

To save the log files for OpsCenter Web GUI in a different location


/opt/SYMCOpsCenterServer/bin/vxlogcfg -a -p 58330 -o 147 -s


Note: 58330 is the OpsCenter product ID. 147 is the OID for OpsCenter WebGUI.

2 Enter the following command to stop the OpsCenter Web server process:

/opt/SYMCOpsCenterAgent/bin/stopgui.sh

3 Enter the following command to start the OpsCenter Web server process:

/opt/SYMCOpsCenterAgent/bin/startgui.sh

About OpsCenter database defragmentationFragmentation occurs naturally as you make changes to your database. Suchchanges may occur due to the deletion of data from the OpsCenter database. Someexamples when data is deleted from the OpsCenter database are the following:

■ When data purging is enabled in OpsCenter. The purge settings can be viewedby clicking Settings > Configuration > Data Purge in the OpsCenter console.Data purging in OpsCenter is enabled by default.

■ When you delete a master server from OpsCenter.

Symantec recommends that you should defragment the OpsCenter database oncein a month. In addition, you should defragment the OpsCenter database if the diskfragment count in the server.log file on Windows or dbserver.log file on UNIXshows a large number.

The following section describes how you can find the disk fragment count.

See “Checking the disk fragment count” on page 221.

Checking the disk fragment count

Use the following procedure to check the disk fragment count in the server.logfile on Windows or dbserver.log file on UNIX.


To check the disk fragment count

1 Open the following files on Windows and UNIX respectively:

INSTALL_PATH\Symantec\OpsCenter\server\db\log\server.logWindows

/opt/SYMCOpsCenterServer/db/log/dbserver.logUNIX

2 Search for the word fragment in the file. For example, when you search forfragment in server.log or dbserver.log, you may find the following line:

Performancewarning:Databasefile"G:\OpsCenter\db\vxpmdb.db"consistsof 2000 disk fragments

Note: You may not find any results when you search for fragment. This iscompletely fine. You may see such performance warnings when the diskfragment count is high.

Defragmenting the OpsCenter database

You can defragment the OpsCenter database using the dbdefrag command.Defragmentation helps to increase data access and retrieval speed. For optimumperformance, defragment the OpsCenter databases periodically and after a purgeoperation.

Note: OpsCenter does not work during the time when the OpsCenter database isdefragmented.

To defragment the OpsCenter database on Windows and UNIX

◆ To defragment the OpsCenter database on Windows, run the followingcommand:

INSTALL_PATH\OpsCenter\server\bin\dbdefrag.bat

To defragment the OpsCenter database on UNIX, run the following command:

/opt/SYMCOpsCenterServer/bin/dbdefrag.sh

Adjusting the heap size for OpsCenter componentsUse the following procedures to adjust the heap size for OpsCenter components.


222

Adjusting the default heap size for the OpsCenter server

If the OpsCenter server processes are consuming a lot of memory (which mayhappen with large OpsCenter configurations), it may be helpful to increase theOpsCenter Server heap size.

The OpsCenter Server default heap size can be increased from 1024 MB up to 1400MB for 32-bit platforms. The OpsCenter Server default heap size can be increasedfrom 2048 MB to a higher value (like 4096 MB) for 64-bit platforms. You candetermine a higher value based on the physical (RAM) and virtual memory thatis available on your system.

To adjust the heap size on Windows servers

1 Open OpsCenterServerService.xml file from the following location on theOpsCenter server:

INSTALL_PATH\OpsCenter\server\bin

2 Modify the Xmx1024M value in the following string.

<CmdArg value="-Xms512M -Xmx1024M

For example, replace -Xmx1024M with -Xmx1400M to increase the maximumheap size from 1024 MB to 1400 MB.

On 64-bit systems, modify the -Xmx2048M value in the following string:

<CmdArg value="-Xrs -Xmx2048M

For example, replace -Xmx2048with -Xmx4096 to increase the maximum heapsize from 2048 MB to 4096 MB.

3 Save the OpsCenterServerService.xml file.

4 You must restart all OpsCenter server services for the changes to be effective.

Enter the following commands to first stop and then start all OpsCenter serverservices as follows:


INSTALL_PATH\OpsCenter\server\bin\opsadmin.bat start


To adjust the heap size on UNIX servers

1 Open startserver file from the following location:

/opt/SYMCOpsCenterServer/bin

2 Modify the -Xmx2048M value in the following string:

MAX_HEAP=-Xmx2048M


3 Save the startserver file.

4 You must restart all OpsCenter server processes for the changes to be effective.

Enter the following commands to first stop and then start all OpsCenter serverprocesses as follows:



Adjusting the default heap size for the Symantec OpsCenter Web server

The OpsCenter Web server default heap size can be increased from 1024 MB upto 1400 MB for 32-bit platforms. The OpsCenter Web server default heap size canbe increased from 1024 MB to a higher value (like 2048 MB) for 64-bit platforms.You can determine a higher value based on the physical (RAM) and virtual memorythat is available on your system.

Note: If you start seeing poor performance in the OpsCenter console every fewdays and restarting the Symantec OpsCenter Web server service fixes the problem,you should increase the Web server default.


224


1 Open OpsCenterGUIService.xml file from the following location on theOpsCenter server:

INSTALL_PATH\OpsCenter\gui\bin\OpsCenterGUIService.xml

2 Modify the Xmx1024m value in the following string.

<EnvVar name="JAVA_OPTS" value="-Xrs -Xms512m -Xmx1024m

For example, replace -Xmx1024m with -Xmx1400m to increase the maximumheap size from 1024 MB to 1400 MB.

Note: This string may be listed twice in the OpsCenterGUIService.xml file.You can change the first occurrence of -Xmx1024m in theOpsCenterGUIService.xml file to adjust the heap size.

3 Save the OpsCenterGUIService.xml file.

4 You must restart all OpsCenter server services for the changes to be effective.

Enter the following commands to first stop and then start all OpsCenter serverservices as follows:




1 Open startGUI file from the following location:

/opt/SYMCOpsCenterGUI/bin


JAVA_OPTS="-Xrs -d64 -Xms512M -Xmx1024m...



3 Save the startGUI file.

4 You must restart all OpsCenter server processes for the changes to be effective.

Enter the following commands to first stop and then start all OpsCenter serverprocesses as follows:



Adjusting the default heap size for the OpsCenter Agent

If the OpsCenter Agent processes are consuming a lot of memory (which mayhappen with large OpsCenter configurations), it may be helpful to increase theOpsCenter Agent heap size. The OpsCenter Agent default heap size can beincreased from 1024 MB up to 1400 MB for 32-bit platforms. The OpsCenter Agentdefault heap size can be increased from 1024 MB to a higher value (like 2048 MB)for 64-bit platforms. You can determine a higher value based on the physical(RAM) and virtual memory that is available on your system.

Note: The OpsCenter Agent runs as a 32-bit application on 64-bit Windowsplatforms. Hence, the OpsCenter Agent default heap size can be increased from1024 MB up to 1400 MB for Windows 64-bit platforms.


1 Open OpsCenterAgentService.xml file from the following location on theOpsCenter server:

INSTALL_PATH\OpsCenter\Agent\bin


<CmdArg value="-Xms512M -Xmx1024M


3 Save the OpsCenterAgentService.xml file.


226

4 You must restart the OpsCenter Agent service for the changes to be effective.To restart the OpsCenter Agent service, first stop and then start the SymantecOpsCenter Agent Service.

Select Control Panel > Administrative Tools > Services and stop theSymantec OpsCenter Agent Service.

5 Select Control Panel > Administrative Tools > Services and start theSymantec OpsCenter Agent Service.


1 Open startagent file from the following location:

/opt/SYMCOpsCenterAgent/bin


MAX_HEAP=-Xmx1024M


3 Save the startagent file.

4 You must restart the OpsCenter Agent process for the changes to be effective.

Enter the following commands to first stop and then start OpsCenter Agentprocess as follows:



Adjusting the OpsCenter database cache sizeThe amount of memory available for database server cache is an important factorin controlling OpsCenter performance. Symantec recommends that you adjustthe Sybase cache size after installing OpsCenter. After you install OpsCenter, thedatabase size can grow rapidly as you add more master servers.

Sybase automatically adjusts the cache size for optimum performance. You canalso set the cache size using the -c server option.


To set the cache size using the -c server option on Windows servers

1 Open the install_path\OpsCenter\server\db\conf\server.conf file.

For example, to increase the cache size to 512 MB, add -c 512M -cs to thecontent of server.conf file:

-n OPSCENTER_<hostname> -x

tcpip(BROADCASTLISTENER=0;DOBROADCAST=NO;ServerPort=13786) -o

"install_path\db\log\server.log" -m

should be changed to

-n OPSCENTER_<hostname> -x

tcpip(BROADCASTLISTENER=0;DOBROADCAST=NO;ServerPort=13786) -o

"install_path\db\log\server.log

" -c 512M -cs -m

The -cs option logs the cache size changes for the database server.

In the same manner, to increase the cache size to 1 GB, you should add -c

1G -cs to the content of the server.conf file.

2 Stop and restart the OpsCenter services, as follows:




228

To set the cache size using the -c server option on UNIX servers

1 Open the/opt/SYMCOpsCenterServer/db/conf/server.conffile and changethe value of the -c option.

For example, you can increase the Sybase cache size to 512 MB by changingthe server.conf file content.

The following:

-n OPSCENTER_<hostname>

-x tcpip(BROADCASTLISTENER=0;DOBROADCAST=NO;ServerPort=13786;)

-gp 8192 -ct+ -gd DBA -gk DBA -gl DBA -ti 60

-c 25M -ch 500M -cl

25M -ud -m

should be changed to:

-n OPSCENTER_<hostname>

-x tcpip(BROADCASTLISTENER=0;DOBROADCAST=NO;ServerPort=13786;)

-gp 8192 -ct+ -gd DBA -gk DBA -gl DBA -ti 60 -c 512M

-cs -ud -m

This example replaced -c 25M -ch 500M -cl 25M with -c 512M -cs in theserver.conf file to increase the cache size to 512 MB. In the same manner, toincrease the cache size to 1 GB, replace -c 25M -ch 500M -cl 25M with -c 1G-cs.

The -ch and -cl server options are used to set the maximum and the minimumcache size respectively. The -cs option logs the cache size changes for thedatabase server.

2 Save the server.conf file.

3 Stop and restart the OpsCenter processes, as follows:



About purging data periodicallyYou should purge the OpsCenter data periodically.

See “Configuring data purge settings” on page 301.

The OpsCenter database should be defragmented after a purge operation.

See “Defragmenting the OpsCenter database” on page 222.


AboutOpsCenter performance and floating-point calculationsSymantec OpsCenter performs certain calculations that require floating-pointmath. If the server's processor does not have a dedicated floating-point unit, thecalculations are handled in floating-point emulation.

Emulation mode slows down OpsCenter's performance. Symantec does notrecommend running OpsCenter on any server that lacks a dedicated floating-pointunit.

Performance issues exist when the OpsCenter server software is installed on aSun T1 server. Symantec recommends that you install OpsCenter server softwareon a Sun T2 server. The issue of limited floating point capability on T1 servershas been resolved with the T2 servers.

About known performance issuesThe following known issues may occur when the database size increases:

■ The performance of OpsCenter reports degrades. Reports are slow and take alonger time to run.

■ If you have configured report schedules, the reports may reach later than thescheduled time.

■ Procedure-based reports may not run before timeout happens (in 30 minutes).Symantec recommends that you schedule procedure-based reports in such ascenario.The following is a list of procedure-based reports:

■ Backup Job Size Variance

■ Throughput Variance

■ File Count Variance

■ Backup Duration Variance

■ BMR Client Configuration Backup Failures

■ Clients Not Backed up

■ Client Summary Dashboard

■ Master Server Job Throughput

■ Media Server Job Throughput

■ Disk Usage

■ Storage Unit Usage

■ Media Summary by Media Server


230

■ Virtual Client Summary

■ Capacity Planning Historical

■ Capacity Planning Forecasted

■ Drive Throughput

■ Drive Utilization

■ Success Rate Line

■ Daily Summary of Backup Activity

■ All Failed Backups

■ Consecutive Failures Report

■ All Jobs

■ Client Risk Analysis

■ Client Coverage

Using an earlier NOM or VBR installation afterupgrade

It is possible to revert back to using your older NOM or VBR software even afteryou have upgraded to OpsCenter 7.0 server.

When you upgrade from NOM or VBR to OpsCenter server, the OpsCenter installeronly stops the existing NOM or VBR services. It does not uninstall your existingNOM or VBR installation. If you have not uninstalled NOM or VBR, you can useyour older installation.

In case you have not uninstalled NOM or VBR and want to use your existing NOMor VBR software, use the following procedure.

To start using NOM or VBR on Windows

1 Log on to the OpsCenter server as an Administrator.

2 Uninstall OpsCenter server software.

See “Uninstalling Symantec OpsCenter on Windows” on page 233.

3 Select ControlPanel>AdministrativeTools>Services and use the WindowsService Control Manager (SCM) to change the startup type of all NOM or VBRservices to Automatic.

231Installing Symantec OpsCenter 7.0Using an earlier NOM or VBR installation after upgrade

4 Start all NOM or VBR services by entering the following command:

<INSTALL_PATH>\NetBackup OperationsManager\bin\admincmd\NOMAdmin -start_service

NOM

<INSTALL_PATH>\Tools\cscript vx_services_start.vbsVBR

5 Log on to the NOM or VBR console.

In case domains are not visible on the logon page and you cannot log on to NOM,you must reinstall Symantec Product Authentication Service that was shippedwith your NOM version. See the NOM documentation for more information.

To start using NOM or VBR on UNIX

1 Log on to the OpsCenter server as root.

2 Uninstall OpsCenter server software.

See “Uninstalling Symantec OpsCenter on UNIX ” on page 233.

3 Enter the following command to start all NOM or VBR processes:

/<INSTALL_PATH>/VRTSnom/bin/NOMAdmin -start_serviceNOM

/<INSTALL_PATH>/VRTSccsvs/bin/vbrserver startVBR

4 Log on to the NOM or VBR console.

In case domains are not visible on the logon page and you cannot log on to NOM,you must reinstall Symantec Product Authentication Service that was shippedwith your NOM version. See the NOM documentation for more information.

Uninstalling Symantec OpsCenter on Windows andUNIX

This section describes uninstallation procedures for OpsCenter on Windows andUNIX.

Note: After a rollback, the keys are not recreated to display an entry in Add orRemove Programs dialog box. If a rollback occurs during an uninstall of OpsCenter,the keys are not removed from Add or Remove Programs dialog box. You mustremove OpsCenter. Usesetup.exe to remove OpsCenter.

Installing Symantec OpsCenter 7.0Uninstalling Symantec OpsCenter on Windows and UNIX

232

Uninstalling Symantec OpsCenter on WindowsUse the Windows Add/Remove Programs utility to uninstall OpsCenter on aWindows host.

Note: Before uninstalling OpsCenter components, ensure that NetBackup-WindowsGUI is not running. Close any NetBackup-Windows GUI consoles that are openbefore uninstalling OpsCenter components.

To uninstall Symantec OpsCenter Server on Windows



3 Click Symantec OpsCenter Server and click Remove.

4 Click Next to continue and remove Symantec OpsCenter Server from yourcomputer.

To uninstall Symantec OpsCenter Agent on Windows



3 Click Symantec OpsCenter Agent and click Remove.

4 Click Next to continue and remove Symantec OpsCenter Agent from yourcomputer.

To uninstall Symantec OpsCenter View Builder on Windows



3 Click Symantec OpsCenter View Builder and click Remove.

4 Click Next to continue and remove Symantec OpsCenter View Builder fromyour computer.

Uninstalling Symantec OpsCenter on UNIXUse the Uninstall Script, which resides in the root directory of the product DVDand also in INSTALL_PATH/VRTS/install directory, to uninstall OpsCenter on aUNIX host.

233Installing Symantec OpsCenter 7.0Uninstalling Symantec OpsCenter on Windows and UNIX

Note: If you want to reinstall OpsCenter components, use the product DVD. Youcannot reinstall OpsCenter components using the install scripts in theINSTALL_PATH/VRTS/install directory.

To uninstall OpsCenter Server on UNIX

1 Open a UNIX console and log in as root on the target host.


INSTALL_PATH/VRTS/install


./uninstallopscenterserver


When you upgrade from VBR server to the OpsCenter server and thenuninstall OpsCenter server, you may be prompted with the following question:

Do you want to uninstall package VRTSccsvs

from <host name> which is dependent on package VRTSpbx?

[y,n,q,?] (n)

If you see this prompt, type n and press Enter. The VBR uninstaller (and notthe OpsCenter uninstaller) must be used to remove the VRTSccsvs package.

4 When asked to confirm if you want to uninstall OpsCenter Server, do one ofthe following:




To uninstall OpsCenter Agent on UNIX

1 Open a UNIX console and log in as root on the target host.


/opt/VRTS/install

Installing Symantec OpsCenter 7.0Uninstalling Symantec OpsCenter on Windows and UNIX

234


./uninstallopscenteragent


4 When asked to confirm if you want to uninstall OpsCenter Agent, do one ofthe following:




Clustering Symantec OpsCenterThe following sections describe how you can cluster OpsCenter 7.0.

About a Symantec OpsCenter clusterClusters provide high availability of applications and data to users. In a cluster,two or more nodes are linked in a network and work collectively as a single system.Each node can access the shared disks with the help of cluster software. All nodesin a cluster are constantly aware of the status of resources on the other nodes. Ifa node becomes unavailable, resources running on that node migrate to an availablenode.

Symantec OpsCenter (OpsCenter) operates in an active or passive failoverconfiguration. OpsCenter Server must be installed on the active node and thepassive (or failover nodes). When a failover occurs in an OpsCenter cluster,OpsCenter is shut down on the active node and starts on one of the failover nodesin the cluster. During failover, users experience only a short interruption in service.This failover provides high availability for OpsCenter. You can cluster only theOpsCenter Server. Installing OpsCenter in a clustered environment makesOpsCenter a highly available application.

Supported cluster solutionsFor Symantec OpsCenter to be clustered, you must have Veritas Cluster Server(VCS) installed. An OpsCenter cluster is supported on Windows and Solarisplatforms.

Table 3-15 lists the supported versions of VCS.

235Installing Symantec OpsCenter 7.0Clustering Symantec OpsCenter

Table 3-15 OpsCenter cluster support matrix

Start of supportLatest supported versionPlatform

4.2 RP25.1VCS Windows

4.35.0VCS Solaris

VCS is a high-availability solution for cluster configurations. With VCS you canmonitor systems and application services, and restart services on a differentsystem when hardware or software fails.

For more information about VCS, see the Veritas Cluster Server User's Guide.

Note: Clustered OpsCenter is not supported on MSCS.

About running commands on the active nodeFor a clustered OpsCenter server, you must run commands on the active node.You may get unexpected results if you run a command on an inactive node. Thecommand may fail to run and may sometimes result in an unexpected behavior.

For example, running the dbbackup command on an inactive node may result inthe following unexpected result:

Command: E:\OpsCenter\server\bin>dbbackup.bat E:\temp

Result: "Could not find Z:\OpsCenter\server\config\db.conf file"

In addition, the OpsCenter service group may failover if the command requiresrestarting the OpsCenter services. Some OpsCenter commands or utilities like thesupport utility require restarting the services.

Clustering Symantec OpsCenter on WindowsThis section provides information about installing Symantec OpsCenter in aclustered mode, on a Windows host.

Table 3-16 provides the Windows clustering steps.

Table 3-16 OpsCenter clustering steps

Reference topicDescriptionStep

See “Limitations of SymantecOpsCenter cluster on Windows”on page 237.

Understand the limitations of anOpsCenter cluster

1

Installing Symantec OpsCenter 7.0Clustering Symantec OpsCenter

236

Table 3-16 OpsCenter clustering steps (continued)


See “Prerequisites for SymantecOpsCenter cluster on Windows”on page 237.

Make sure that you have met allprerequisites.

2

See “Installing Symantec ProductAuthentication Service onWindows” on page 238.

Install OpsCenter 7.0.3

Limitations of Symantec OpsCenter cluster on WindowsAn OpsCenter cluster has the following limitations:

■ Only the OpsCenter Server can be clustered.OpsCenter Agent and the OpsCenterView Builder cannot be clustered.

■ Upgrades from previous versions of NOM or VBR to clustered OpsCenter Serveris not supported.

■ OpsCenter cluster cannot co-exist with any other Symantec product runningin secure mode using the Symantec Product Authentication Service.

■ OpsCenter does not support clustered AT.

Prerequisites for Symantec OpsCenter cluster on WindowsThis section contains information about the requirements that must be met beforeyou install and configure OpsCenter in a clustered mode, on a Windows host.

■ Verify that VCS and OpsCenter support your hardware. For a list of supportedstorage devices, visit the following Web site:http://entsupport.symantec.com

■ Verify that the supported version of VCS is correctly installed and configured.Follow the steps in the Veritas Cluster Server Installation Guide.

■ For VCS Windows 4.2 versions, ensure that the patch available throughTechNote 278307 is installed prior to installing OpsCenter. For OpsCenter, thesupported VCS version starts from 4.2 RP2. The patch is available from thefollowing URL:http://entsupport.symantec.com/docs/278307This TechNote is applicable to OpsCenter.

■ Verify that no VCS resource group and resource exist with the same name asthat which you intend to use for OpsCenter.


http://entsupport.symantec.com


■ The SharedDisk must be configured and accessible to all cluster nodes whereyou want to install OpsCenter.

■ Verify that you have an IP address and host name (virtual name) to be assignedto the OpsCenter resource in VCS. Only use these for the OpsCenter resource.Also, ping the IP address and verify that the IP address is not plumbed.

■ Verify that you can mount the disk.

■ Verify that you have the OpsCenter installation program and a valid licensekey.

■ For a Windows cluster, verify that the cluster disk groups and dynamic volumesfor OpsCenter are created on the shared storage. Refer to theVeritas StorageFoundation Administrator’s Guide for details.

■ Verify that all VCS services are up and running on all the nodes in the cluster.

■ Verify that OpsCenter installation is carried out with the domain adminaccount.

■ Before installing OpsCenter Server, ensure that Symantec authenticationservice (AT) Server is installed separately in a non-clustered mode. AT can beinstalled in Root + AB or AB mode.For more information about installing AT, see the Symanetc InfrastructceCoreServices Installation Guide.

Installing Symantec Product Authentication Service onWindowsOpsCenter Server requires that Symantec Product Authentication Service (AT) isinstalled on a standalone host, before OpsCenter can be clustered. You must installthe version of AT Service that is shipped with OpsCenter 7.0. You can eitherconfigure AT in root + authentication broker (Root + AB) mode or authenticationbroker (AB) mode. Symantec recommends that you configure AT in a 'Root+AB'mode.

Clustered OpsCenter Server uses this authentication broker. To establish aconnection between AT host and OpsCenter Server host, you need to create aprincipal user on the AT host. Use the credentials of this user when installingOpsCenter Server.

Note: Symantec Product Authentication Service is installed when you installVeritas Cluster Server. You must upgrade to the version of authentication servicethat is shipped with OpsCenter 7.0.


238

Note: OpsCenter does not support clustered AT.

Note: In case of updates made to AT for OpsCenter 7.0, see the following technotefor the latest information:


Symantec Product Authentication Service can be installed in the following ways:

To install AT

1 Log on to the host where you want to install AT.

You should not cluster the AT service, as OpsCenter does not support clusteredAT.

2 You may install AT from the OpsCenter DVD or from the NetBackup mediakit.

3 If autorun is enabled, the Symantec OpsCenter Installation Wizard appears.■


Where D is the DVD drive.The Symantec OpsCenter Installation Wizard appears.

4 On the Symantec OpsCenter Installation Wizard, click the Installation link.

5 Click Symantec Product Authentication Service.

6 Click Next. The VxSSVRTSatSetup.exe is executed.

See Symantec Infrstructure Core Services Installation Guide for moreinformation about the VxSSVRTSatSetup.exe.

7 Create a principal user on the AT host using the following command:

AT_INSTALL_DIR/bin/vssat addprpl --prplname <principal name>

--password <principal name password> --pdrtype ab --domain broker

--prpltype service --is_broker_admin --is_domain_admin

AT_INSTALL_DIR is the directory where AT is installed.

The default location on 32-bit Windows platforms is: %ProgramFiles%\VERITAS\Security\Authentication

The default location on 64-bit Windows platforms is:%ProgramFiles(x86)%\VERITAS\Secruity\Authentication



Installing OpsCenter Server on a Windows clusterTo cluster OpsCenter and make it highly available, you must install and configureOpsCenter in a clustered mode.

Note: To install OpsCenter Server in clustered mode, first install the OpsCenterServer on the active node and then on the passive nodes. Also, you need to installOpsCenter Server manually on all the nodes.

Note: Tomcat is not clustered or installed in the shared drive. HenceconfigurePortsutility has to be run on each node.

To install OpsCenter Server in a clustered mode on Windows


You may install OpsCenter Server from the OpsCenter DVD or from theNetBackup media kit. The OpsCenter DVD contains OpsCenter software forall available platforms. The NetBackup media kit contains a separate DVDfor each platform.

2 If autorun is enabled, the Symantec OpsCenter Installation Wizard appears.■


Where D is the DVD drive.The Symantec OpsCenter Installation Wizard appears.

3 On the Symantec OpsCenter Installation Wizard, click the Installation link.

4 If you are using the NetBackup media kit to install OpsCenter, click OpsCenterSoftwareInstallation. Ignore this step if you are installing OpsCenter serversoftware from the OpsCenter DVD.


6 Click Next.



240

8 Select Install a clustered OpsCenter Server to install OpsCenter Server inclustered mode. You need to install OpsCenter Server manually on each nodeof the cluster.

This option is enabled if you have Veritas Cluster Server (VCS) installed.

Select Install to this computer only to install OpsCenter Server innon-clustered mode.

9 In the Installation Method section, click Typical to use the default settingsand installation location.

Also compare the space that is required for installation with the actual spaceavailable in the installation directory.

Note: Click Custom if you want to change the default settings and locations.

Click Next.

10 On the License Keys screen, enter the demo or permanent key that you havereceived with the purchase of OpsCenter and click Add Key.

Note: You can also add the license keys from the OpsCenter console.


The license keys that are already installed on the system are also displayedin the box that is shown on this screen. The license type information is alsoshown along with the key.

More information about licenses is available.


11 Click Next. The Authentication Settings screen is displayed.

12 On the Authentication Settings screen, enter the following details of aprincipal user to connect to the host where AT authentication broker (Root+ AB or AB) is installed:

■ Authentication service host name

■ Authentication service port number (2821 is the default port number)

■ Authentication service user name

■ Authentication service Password

■ Authentication service Domain Name (broker is the default domain name)


Note:You must have this principal user created on the authentication broker(AB) host.

See “Installing Symantec Product Authentication Service on Windows”on page 238.

13 Click Next. The Cluster Settings screen is displayed.

14 On the Cluster Settings screen, enter the following information:

Enter the name for the OpsCenter cluster. Forexample: OpsCenter_Server

Cluster Group Name

Enter the virtual host name that is assigned to theOpsCenter cluster. For example: OpsCenter_Cluster-1

Virtual host Name

Enter the IP address that assigned to the OpsCentercluster

Virtual IP address

Enter the subnet mask . For example: 255.255.252.0Subnet mask

Select the shared drive path that you have configuredin VxVM. For example, Z:\

Path to Shared data

Select LAN as a public network.

You can select different public network for passivenodes.

Public Network

15 Click Next. The installer shows the summary of the settings that you haveselected for OpsCenter Server installation.


16 Click Install.

The installer starts installing the OpsCenter Server software.

Note: In clustered mode, the default OpsCenter database location on Windowsis the following location on the shared drive:

OpsCenter\Server\db


18 Click Finish.


242

Uninstalling Symantec OpsCenter from the Windows clusterUse the Windows Add/Remove Programs utility to uninstall OpsCenter Serverfrom a cluster node on Windows host.

Note: Uninstall the OpsCenter Server first from the passive nodes and then fromthe active node..

To unistall Symantec OpsCenter Server on Windows



3 Click Symantec OpsCenter Server and click Remove.

4 Click Next to continue and remove Symantec OpsCenter Server from yourcomputer.

Clustering Symantec OpsCenter Server on SolarisThis section provides information about installing OpsCenter Server in a clusteredmode, on a Solaris host.

Table 3-17 provides the Solaris clustering steps.

Table 3-17 OpsCenter Server clustering steps


See “Limitations of SymantecOpsCenter cluster on Solaris”on page 244.

Understand the limitations of anOpsCenter cluster

1

See “Prerequisites for SymantecOpsCenter cluster on Solaris”on page 244.

Make sure that you have met allprerequisites.

2

See “Preinstallation checklist fora Symantec OpsCenter Serverinstallation” on page 245.

Make sure that your preinstallationchecklist is complete.

3

See “Installing SymantecOpsCenter Server in a clusteredmode on Solaris” on page 247.

Install OpsCenter 7.0.4


Limitations of Symantec OpsCenter cluster on SolarisA OpsCenter cluster has the following limitations:

■ Only the OpsCenter Server can be clustered.OpsCenter Agent and OpsCenterView Builder cannot be clustered.

■ Upgrades from previous versions of NOM or VBR to clustered OpsCenter Serveris not supported.

■ OpsCenter cluster cannot co-exist with any other Symantec product runningin secure mode using the Symantec Product Authentication Service.

■ OpsCenter does not support clustered AT.

Prerequisites for Symantec OpsCenter cluster on SolarisThe following requirements must be met before you install and configure aSymantec OpsCenter failover server:

■ Verify that VCS and OpsCenter support your hardware. For a list of supportedstorage devices, visit the following Web site:http://entsupport.symantec.com

■ Verify that the supported version of VCS is correctly installed and configuredon Solaris. Follow the steps in the Veritas Cluster Server Installation Guide.

■ Verify that no VCS resource group and resource exist with the same name asthat which you intend to use for OpsCenter.

■ The SharedDisk must be configured and accessible to all cluster nodes whereyou want to install NetBackup.

■ Verify that you have an IP address and host name (virtual name) to be assignedto the OpsCenter resource in VCS. Only use these for the OpsCenter resource.Also, ping the IP address and verify that the IP address is not plumbed.

■ Verify that you can mount the disk.

■ Verify that you have the OpsCenter installation program and a valid licensekey.

■ Verify that OpsCenter Server installation is carried out with the domain adminaccount.

■ Before installing OpsCenter Server, ensure that Symantec authenticationservice (AT) Server is installed separately in a non-clustered mode. AT can beinstalled in Root + AB or AB mode.For more information about installing AT, see the Symanetc InfrastructceCoreServices Installation Guide.


244

http://entsupport.symantec.com

Installing Symantec Product Authentication Service on SolarisOpsCenter Server requires that Symantec Product Authentication Service (AT) isinstalled on a standalone host, before OpsCenter can be clustered. You must installthe version of AT Service that is shipped with OpsCenter. You can either configureAT in root + authentication broker (Root + AB) mode or authentication broker(AB) mode. Clustered OpsCenter Server uses this authentication broker. Toestablish a connection between AT host and OpsCenter Server host, you need tocreate a principal user on the AT host. Use the credentials of this user wheninstalling OpsCenter Server.

Note: Symantec Product Authentication Service is installed when you installVeritas Cluster Server. You must upgrade to the version of authentication servicethat is shipped with OpsCenter.

Note: OpsCenter does not support clustered AT.

Symantec Product Authentication Service can be installed in the following ways:

To install AT

1 Log on to the host where you want to install AT.

You should not cluster the AT service, as OpsCenter does not support clusteredAT.

2 Mount the NetBackup media kit for the appropriate platform on which youare installing. The NetBackup media kit contains a separate DVD for eachplatform.

3 In the NetBackup media kit product DVD, navigate to the ICS directory:

cd ICS

4 Invoke the ./installics script from the ICS directory.

The installics menu is displayed.

5 Select 1 to install AT.

See Symantec Infrstructure Core Services Installation Guide for more detailson using the installics script.

Preinstallation checklist for a Symantec OpsCenter ServerinstallationThe OpsCenter Server requests certain cluster related information duringinstallation. Fill out the checklist before you begin installation.


Note:The configuration utility unless specified, treats all attribute values globally.

The following information is required for all VCS cluster configurations.

----------------------------------------Virtual Name for NetBackup:

----------------------------------------IP address :

----------------------------------------Subnet mask

Network device name(NIC)

IP addressNode Name

------------------------------------------------------------------------------------------------------------------------

------------------------------------------------------------------------------------------------------------------------

------------------------------------------------------------------------------------------------------------------------

About installation of Symantec OpsCenter with VCS

The following information is required if you use VCS. Review the scenario that isdescribed.

See “Scenario 1 - with VxVM” on page 246.

Scenario 1 - with VxVM

The following information is required if you use VCS with VxVM.

ExampleResource

Disk group resource:

opsdgDisk group : --------------------------------------

0 or 1Start volumes: -----------------------------------

0 or 1Stop volumes: -----------------------------------

Volume resource: (optional)

opsvolVolume: -------------------------------------------

Mount resource:

/opt/VRTSnbuMount point : ------------------------------------

/dev/vx/dsk/opsdg/opsvolBlock device: -----------------------------------

vxfsFS Type: ------------------------------------------


246

(optional)Mount option: ----------------------------------

(if you add other options, -y is also required)Fsck option: -------------------------------------

Installing Symantec OpsCenter Server in a clustered mode onSolarisTo cluster OpsCenter and make it highly available, you must install and configureOpsCenter in a clustered mode.

Note: To install OpsCenter Server in clustered mode, first install the OpsCenterServer on the active node and then on the passive nodes. Also, you need to installOpsCenter Server manually on all the nodes.

Note: Tomcat is not clustered or installed in the shared drive. HenceconfigurePortsutility has to be run on each node.

To install OpsCenter Server in clustered mode on Solaris

1 Fill out the checklist for all configurations and the checklist for your specificenvironment.

See “Preinstallation checklist for a Symantec OpsCenter Server installation”on page 245.

2 Open a Solaris console and log on as root on the target host.


You may install OpsCenter Server from the OpsCenter DVD or from theNetBackup media kit. The OpsCenter DVD contains OpsCenter software forall available platforms. The NetBackup media kit contains a separate DVDfor each platform.

4 Make sure that the shared disk is not mounted on any node in the cluster.

If applicable, unmount the OpsCenter shared mount point. Stop the volumethe mount point is on and deport the disk group for that volume on all nodesof the cluster.


■ If you are using the OpsCenter DVD to install OpsCenter Server software,navigate to the appropriate OpsCenter Server platform directory and thenthe Server directory on the DVD.


■ If you are using the NetBackup media kit to install OpsCenter Server,navigate to the Server directory:cd OpsCenter/Server




9 The installer displays a list of components that are installed like PBX,Symantec WebGUI Server, Symantec Database etc. Review this list and pressEnter to continue.


Where do you want to install Symantec OpsCenter? </opt>




12 When OpsCenter Server is installed on the clustered setup a confirmationprompt is displayed.

■ When installing OpsCenter Server on the first node, you are prompted toconfirm creation of an OpsCenter Server cluster. Type Yes to set upOpsCenter in HA mode.

■ When installing OpsCenter Server on the subsequent nodes, informationof already created NetBackup cluster group is displayed. You are promptedto join the group.


248

13 When you are prompted for cluster specific configuration details, refer tothe checklist and provide details accordingly.

Use the virtual name for the NetBackup server name.

Caution: When you are prompted, you must provide the same virtual clustername that you provided during the installation. This name is case-sensitiveand must be in the same format (FQDN/short) on all the nodes.

14 Allow OpsCenter to be installed in a cluster. The following happens whenOpsCenter Server is installed:

■ On the first node, a single node cluster resource group for OpsCenter iscreated and brought online.

■ On the other nodes, the installed node is added to the cluster resourcegroup.

Uninstalling OpsCenter Server from the Solaris clusterUse the Uninstall Script, which resides in the root directory of the product DVDand also in /opt/VRTS/install directory, to uninstall OpsCenter from a node ona Solaris host.

To unistall OpsCenter Server on Solaris

1 Open a Solaris console and log on as root on the target host.


/opt/VRTS/install


./uninstallopscenterserver

The Uninstall script checks the components that are installed on the system.

4 When you are asked to confirm if you want to uninstall OpsCenter Server,do one of the following:





Known issue during uninstallationYou may get the following error message while uninstalling OpsCenter serversoftware from an OpsCenter cluster:

"Fatal error during installation"

Use the following steps to uninstall OpsCenter server software in such a scenario:

To uninstall OpsCenter server software

1 Delete the OpsCenter resource group from a cluster node.

See “Deleting OpsCenter resource group from the cluster” on page 250.

2 Since the OpsCenter resource group has been deleted, you must uninstall theOpsCenter server software from each node manually.

See “Uninstalling Symantec OpsCenter from the Windows cluster” on page 243.

See “Uninstalling OpsCenter Server from the Solaris cluster” on page 249.

Deleting OpsCenter resource group from the clusterUse the following procedure to delete OpsCenter resource group from the cluster.

To delete OpsCenter resource group from the cluster

1 Log on to the cluster Web GUI.

2 Right-click the selected Cluster Monitor panel and click ExplorerView fromthe menu to access Cluster Explorer.

3 Click the Service Groups tab in the Cluster Explorer configuration tree.

4 Right-click the OpsCenter resource group and select Offline > All Systems.

5 Click Yes to forcefully take the resource group offline.

6 Right-click the OpsCenter resource group and select Delete.

7 Click Yes to delete the OpsCenter resource group.


250

Administering SymantecOpsCenter


■ About OpsCenter services and processes used by OpsCenter

■ About OpsCenter server scripts on Windows and UNIX

■ About OpsCenter database administration

■ Configuring remote authentication service in OpsCenter

■ About backup and restore of OpsCenter and OpsCenter Analytics

■ About communication and firewall considerations

■ Gathering troubleshooting data with the support script

■ About OpsCenter log files

About OpsCenter services and processes used byOpsCenter

This section provides information about OpsCenter services and processes andhow you can control these services.

These topics assume you already installed OpsCenter on a server.

If you have not installed OpsCenter, review the installation chapter.

4Chapter

About services used by OpsCenter on WindowsAfter you install OpsCenter server and Agent on Windows, the following servicesshould be active. OpsCenter depends on these services. If any of these servicesfail to start, OpsCenter does not start.

Table 4-1 contains information about the services that OpsCenter uses on Windows.

Table 4-1 Services used by OpsCenter on Windows

DescriptionProcessService Name

This service is for the Symantec OpsCenter Agent. By default,the OpsCenter Agent Service starts whenever you boot yourAgent host.

java.exeSymantec OpsCenter AgentService

The OpsCenter server interacts with the OpsCenter GUI andprovides the data that is requested by the GUI from theOpsCenter database. It also interacts with NetBackup throughNBSL to get data regularly.

java.exeSymantec OpsCenterServer Service

This service manages the OpsCenter databases. This processmust be running on the OpsCenter server during all normaloperations like viewing reports, running reports and so on.

dbsrv11.exeSymantec OpsCenterDatabase Server

This service is not an OpsCenter service. OpsCenter uses thisservice to host the OpsCenter Console.

java.exeSymantec OpsCenter Webserver Service

This service is not an OpsCenter service, but it is a componentused by OpsCenter. Symantec Private Branch Exchange allowsall socket communication to take place through a single port.

pbx_exchange.exeSymantec Private BranchExchange

This service is not an OpsCenter service. OpsCenter uses thisservice to authenticate users of OpsCenter.

vxatd.exeSymantec ProductAuthentication Service

Note: The processes listed in this table show the actual memory consumed by therespective OpsCenter service.

Controlling the servicesUse the following procedure to verify if these services are running or not.

Administering Symantec OpsCenterAbout OpsCenter services and processes used by OpsCenter

252

To control these services

1 Use Start > Settings > Control Panel > Administrative Tools > Services.

2 Check the Status column for each service. From the Status column, you canverify if a service is running or not.

3 The Services panel can also be used to stop, start, and restart the OpsCenterservices and Symantec shared services.

About processes used by OpsCenter on UNIXAfter you install OpsCenter server and Agent on UNIX, the following processesshould be active.

Table 4-2 describes the processes that OpsCenter uses on UNIX.

Table 4-2 Processes used by OpsCenter on UNIX

Detailed DescriptionProcessProcessDescription

This process is for the Symantec OpsCenterAgent. By default, the OpsCenter Agentprocess starts whenever you boot yourAgent host.

/opt/SYMCOpsCenterAgent/bin/.OpsCenterAgentdSymantecOpsCenter Agent

The OpsCenter server interacts with theOpsCenter GUI and provides the data thatthe GUI requests from the OpsCenterdatabase. It also interacts with NetBackupto get data regularly.

/opt/SYMCOpsCenterServer/bin/.OpsCenterServerdSymantecOpsCenter Server

This process manages the OpsCenterdatabases. This process must be runningon the OpsCenter server during all normaloperations like viewing reports, runningreports and so on.

/opt/SYMCOpsCenterDatabase/bin/OpsCenterDBdSymantecOpsCenter DatabaseServer

This process is not an OpsCenter process.OpsCenter uses this process to host theOpsCenter Console. Many Symantec Webconsoles share this component.

javaSymantecOpsCenter WebServer

This process is not an OpsCenter process.but it is a component used by OpsCenter.PBX allows all socket communication totake place through a single port.

/opt/VRTSpbx/bin/pbx_exchangeSymantec PrivateBranch Exchange

253Administering Symantec OpsCenterAbout OpsCenter services and processes used by OpsCenter

Table 4-2 Processes used by OpsCenter on UNIX (continued)

Detailed DescriptionProcessProcessDescription

This process is not an OpsCenter process.OpsCenter uses this process to authenticateusers of OpsCenter.

/opt/VRTSat/bin/vxatdSymantec ProductAuthenticationService

Note: The processes listed in this table show the actual memory consumed by therespective OpsCenter process.

AboutOpsCenter server scripts onWindowsandUNIXThe following scripts are used within OpsCenter. The OpsCenter administratormay use many of these scripts. Use the -h option for help about these scripts.

Table 4-3 lists the OpsCenter server scripts on Windows.

Table 4-3 OpsCenter server scripts on Windows

Invokes or Is Invokedby

FunctionLocationScript

AdministratorStarts or stops theOpsCenterServerd.

INSTALL_PATH\OpsCenter\server\binstartserver.bat

and

stopserver.bat

OpsCenter AdministratorBacks up the OpsCenterdatabase

INSTALL_PATH\OpsCenter\server\bindbbackup.bat

OpsCenter AdministratorStarts or stops theOpsCenter database

INSTALL_PATH\OpsCenter\server\binstartdb.bat andstopdb.bat

OpsCenter AdministratorStarts and stops allOpsCenter Server services

INSTALL_PATH\OpsCenter\server\binopsadmin.bat

OpsCenter AdministratorDefragments the OpsCenterdatabase

INSTALL_PATH\OpsCenter\server\bindbdefrag.bat

OpsCenter AdministratorChanges the OpsCenterdatabase password

INSTALL_PATH\OpsCenter\server\binchangedbpassword.bat

OpsCenter AdministratorRuns saved custom SQL andgenerates output in thedesired format.

INSTALL_PATH\OpsCenter\server\binrunStoredQuery.bat

Administering Symantec OpsCenterAbout OpsCenter server scripts on Windows and UNIX

254

Table 4-4 lists the OpsCenter server scripts on UNIX.

Table 4-4 OpsCenter server scripts on UNIX

Invokes or Is Invokedby

FunctionLocationScript

OpsCenter

Server

Starts or stops theOpsCenterServerd.

/opt/SYMCOpsCenterServer/binstartserver

and

stopserver

OpsCenter AdministratorStarts or stops the OpsCenterdatabase

/opt/SYMCOpsCenterServer/binstartdb and stopdb

OpsCenter AdministratorStarts, stops, and monitorsall OpsCenter Serverprocesses

/opt/SYMCOpsCenterServer/binopsadmin

OpsCenter

Server

This script is used internallyfor clustering. The scriptstarts, stops, or restarts theOpsCenter database,OpsCenter Server, andOpsCenter Web server(Tomcat).

Solaris: /etc/init.dOpsCenterServers

OpsCenter AdministratorBacks up the OpsCenterdatabase

/opt/SYMCOpsCenterServerdbbackup.sh

OpsCenter AdministratorDefragments the OpsCenterdatabase

/opt/SYMCOpsCenterServerdbdefrag

OpsCenter AdministratorChanges the OpsCenterdatabase password

/opt/SYMCOpsCenterServerchangeDbPassword

OpsCenter AdministratorRuns saved custom SQL andgenerates output in thedesired format.

/opt/SYMCOpsCenterServerrunStoredQuery

Controlling OpsCenter services and processesThis section provides information on how you can control the OpsCenter serverservices and OpsCenter Agent service.

255Administering Symantec OpsCenterAbout OpsCenter server scripts on Windows and UNIX

Controllingall SymantecOpsCenter server servicesonWindowsservers using opsadmin

The following procedure describes how you can start and stop all OpsCenter serverservices using the opsadmin script.

To start all OpsCenter server services

◆ Enter the following command:


To stop all OpsCenter server services



Controlling the Symantec OpsCenter database server serviceon Windows serversThe following procedure describes how you can control the Symantec OpsCenterdatabase server service on Windows servers.

To start or stop the Symantec OpsCenter database server service

◆ Select ControlPanel>AdministrativeTools>Services and start or stop theSymantec OpsCenter Database Server service.

Controlling the Symantec OpsCenter Server Service onWindows serversThe following procedure describes how you can control the Symantec OpsCenterServer service on Windows servers.

To start or stop the Symantec OpsCenter Server service

◆ Select ControlPanel>AdministrativeTools>Services and start or stop theSymantec OpsCenter Server Service.

Controlling the Symantec OpsCenter Web server ServiceThe following procedure describes how you can control the Symantec OpsCenterWeb server service on Windows servers.

To start or stop the Symantec OpsCenter Web server service

◆ Select ControlPanel>AdministrativeTools>Services and start or stop theSymantec OpsCenter Web Server Service.


256

Controlling the Symantec OpsCenter Agent ServiceThe following procedure describes how you can control the Symantec OpsCenterAgent service on Windows servers.

To start or stop the Symantec OpsCenter Agent service

◆ Select ControlPanel>AdministrativeTools>Services and start or stop theSymantec OpsCenter Agent Service.

Controlling all Symantec OpsCenter server processes on UNIXservers using opsadmin.sh script

The following procedure describes how you can start, stop, and monitor allOpsCenter server processes using the opsadmin script.

To start all OpsCenter server processes

◆ Enter the following command to start all OpsCenter server processes:


To stop all OpsCenter server processes

◆ Enter the following command to stop all OpsCenter server processes:


To monitor all OpsCenter server processes

◆ Enter the following command to monitor the status of all OpsCenter serverprocesses:

/opt/SYMCOpsCenterServer/bin/opsadmin.sh monitor

Controlling the Symantec OpsCenter database server processon UNIX serversThe following procedure describes how you can control the OpsCenter databaseserver process on UNIX servers.

To start the database server


/opt/SYMCOpsCenterServer/bin/startdb


To stop the database server


/opt/SYMCOpsCenterServer/bin/stopdb

Controlling the Symantec OpsCenter server process on UNIXserversThe following procedure describes how you can control the OpsCenter serverprocess on UNIX servers.

To start the OpsCenter server



To stop the OpsCenter server



Controlling the Symantec OpsCenter Web server process onUNIX serversThe following procedure describes how you can control the OpsCenter serverprocess on UNIX servers.

To start the OpsCenter Web server


/opt/SYMCOpsCenterGUI/bin/startgui.sh

To stop the OpsCenter Web server


/opt/SYMCOpsCenterGUI/bin/stopgui.sh


258

Controlling the Symantec OpsCenter Agent process on UNIXserversThe following procedure describes how you can control the OpsCenter Agentprocess on UNIX servers.

To start the OpsCenter Agent



To stop the OpsCenter Agent



About dependency of servicesThe Symantec OpsCenter server service requires that the following OpsCenterservices (processes) are running:

■ Symantec OpsCenter Database Server

■ Symantec Product Authentication Service

■ Symantec Private Branch Exchange

If you stop any of these services, then the OpsCenter server also stops.

Note:

After a reboot, the OpsCenter processes do not start automatically on SUSE Linuxsystems. Symantec recommends that you start the OpsCenter processes after youperform a reboot.

Also after you reboot a SUSE 11 Server, and even though OpsCenter Server servicesare running, an attempt to logon may not succeed. Occasionally, OpsCenter servicesmay not start on reboot in case of SUSE 11. This may happen some times becauseof the PBX taking time to start.

About nbproxy processes on NetBackup master serversWhen OpsCenter is connected to a master server, you may find one or morenbproxy processes running on the master server. You may also see nbproxy


processes when NetBackup-Java GUI or NetBackup-Windows GUI request certaindata from NetBackup (like LiveUpdate , storage lifecycle policies).

Most of the nbproxy processes are started, managed, and removed by NBSL. Thissection talks about the nbproxy processes that NBSL manages.

Note: Not all nbproxy processes on the master server are managed by NBSL. Forexample, some of the nbproxy processes are managed by nbjm and nbpem.

An nbproxy process runs to retrieve the following NetBackup data for OpsCenter:

■ Policies

■ Catalogs

■ Storage lifecycle policies

■ LiveUpdate

■ Client details

Note the following points about the NBSL-managed nbproxy processes:

■ If the data collection for a master server is disabled or a master server isremoved from the OpsCenter console, all nbproxy processes are stoppedimmediately.

■ If OpsCenter crashes (or is abruptly closed), the nbproxy process is removedwithin an hour.

■ If NetBackup is stopped (and NBSL is already killed), all nbproxy processes arestopped immediately.

■ If NBSL crashes (or is abruptly closed), all nbproxy processes exit within 10minutes.

About OpsCenter database administrationThe Sybase database that OpsCenter uses is similar to the NetBackup databaseand is installed as part of the OpsCenter installation. The database is located onthe OpsCenter server.

More information about Sybase database is available.

See http://www.sybase.com/support/manuals.

Administering Symantec OpsCenterAbout OpsCenter database administration

260

Running OpsCenter commandsOpsCenter provides some useful commands to help manage the OpsCenterdatabase. In addition, a utility called changeVxATProperties has been includedthat lets you change the authentication server parameters.

Table 4-5 lists some of the commands that are available.

Table 4-5 Commands available with OpsCenter

ReferenceCommand

See “Changing the OpsCenter databaseadministrator password” on page 261.

changeDbPassword

See “Starting and stopping the OpsCenter database”on page 262.

startdb and stopdb

See “Defragmenting the OpsCenter database”on page 263.

dbdefrag

See “Backing up the OpsCenter database ”on page 271.

See “Restoring the OpsCenter database” on page 274.

dbbackup

See “Configuring authentication server parameters”on page 263.

changeVxATProperties

Note: For a clustered OpsCenter server, you must run commands on the activenode.See “About running commands on the active node” on page 236.

Changing the OpsCenter database administrator passwordThechangeDbPasswordutility lets you change the database administrator passwordthat is used for the OpsCenter database.

Note: This utility is not used to change the logon password for OpsCenter. Tochange the existing logon password, you must use the OpsCenter console.


OpsCenter uses the Sybase SA (Server Anywhere) database to store data. Yourequire a user name and a password to access the data that is stored in thedatabase.

261Administering Symantec OpsCenterAbout OpsCenter database administration

The database administrator user ID isDBA and the initial password isSQL (passwordis case sensitive).

Review the rules for forming a new database password.

The OpsCenter database administrator password cannot have the followingcharacteristics:

■ Exceed 30 characters.

■ Contain consecutive black slash characters.

■ Contain any bracket [ ] characters.

■ Contain any of the following characters. These characters have special meaningin Windows or in shell scripts.‘ ! $ % & . ; ^ | < > , { } $ " ~ [ ] \\

■ Contains the ASCII characters that are less than 32 or ASCII characters thatare greater than 127.

■ Begin with White space and a single quote character.

■ End with White space.

Note: Information about role-based access in Symantec OpsCenter is available.

See “About user access rights” on page 310.

To change the database administrator password on Windows and UNIX

1 Enter the following command on Windows:

INSTALL_PATH\OpsCenter\server\bin\changeDbPassword.bat

Enter the following command on UNIX:

/opt/SYMCOpsCenterServer/bin/changeDbPassword.sh

2 You are prompted for the old database administrator password. Enter the olddatabase password.

3 You are prompted for a new database administrator password. Enter the newpassword.

Starting and stopping the OpsCenter databaseThe startdb script is used to start the OpsCenter database. The stopdb script isused to stop the OpsCenter database.


262

To start the database server on Windows and UNIX

◆ To start the OpsCenter database on Windows, run the following command:

INSTALL_PATH\OpsCenter\server\bin\startdb.bat

To start the OpsCenter database on UNIX, run the following command:


To stop the database server on Windows and UNIX

◆ To stop the OpsCenter database on Windows, run the following command:

INSTALL_PATH\OpsCenter\server\bin\stopdb.bat

To stop the OpsCenter database on UNIX, run the following command:


Defragmenting the OpsCenter databaseYou can defragment the OpsCenter database using the dbdefrag command.Defragmentation helps to increase data access and retrieval speed.

For optimum performance, defragment the OpsCenter databases periodically andafter a purge operation.

Note: OpsCenter does not work during the time when the OpsCenter database isdefragmented.

To defragment the OpsCenter database on Windows and UNIX

◆ To defragment the OpsCenter database on Windows, run the followingcommand:


To defragment the OpsCenter database on UNIX, run the following command:


Configuring authentication server parametersThe authentication server parameters can be configured using thechangeVxATProperties utility.


Note: This procedure is applicable only for OpsCenter clusters where theauthentication broker is remote. This procedure is not applicable when SymantecProduct Authentication Service is installed on the local machine.

To configure authentication server parameters

1 Enter the following command on Windows:

INSTALL_PATH\OpsCenter\server\bin\changeVxATProperties.bat

Enter the following command on UNIX:

/opt/SYMCOpsCenterServer/bin/changeVxATProperties.sh

The authentication server parameters appear one by one. The current valuesof the parameters are specified in brackets.

2 Enter the new values next to the respective parameter. If you do not enter anew value for a parameter, the value of the parameter does not change.

3 You must restart the OpsCenter services for these changes to be effective.Answer y to restart the OpsCenter services.

Saving the OpsCenter database and database logs on separate harddisks

To improve OpsCenter performance, OpsCenter database files and the log filesthat are associated with the OpsCenter database should be stored on separatehard disks. You can store the OpsCenter database files on one hard disk and thelog files on another hard disk.

Symantec also recommends that you not store the database files on the hard diskthat contains your operating system files.

You can specify a custom location (non-default location) for the OpsCenter databaseduring OpsCenter installation. The default location for the OpsCenter databasecan also be changed after OpsCenter has been installed.

Use the following procedures to move the OpsCenter database and log files to adifferent hard disk. The first two procedures are for moving the OpsCenterdatabase files on Windows or UNIX. The last two procedures are for moving thedatabase log files.


264

To move the OpsCenter database to a different hard disk on Windows

1 Stop all OpsCenter services. Enter the following command:


2 Open the databases.conf file with a text editor like notepad from thefollowing directory:

INSTALL_PATH\OpsCenter\server\db\conf

This file has the following contents:

"INSTALL_PATH\OpsCenter\server\db\data\vxpmdb.db"

This path specifies the default location of the OpsCenter database.

3 To move the database to a custom location like E:\Database, replace thecontents of the file with the following:

"E:\Database\vxpmdb.db"

Make sure that you specify the path in double quotes. Also the directories inthe specified path should not contain any special characters like %, ~, !, @, $,&, ^, # etc. For example, do not specify a path like E:\Database%.

Save the databases.conf file.

4 Copy the database file to the new location. Copy vxpmdb.db fromINSTALL_PATH\OpsCenter\server\db\data to a location like E:\Database.


To restart all OpsCenter services, enter the following command:


You should run and monitor OpsCenter for a certain period after moving thedatabase. If OpsCenter works as expected, you can delete vxpmdb.db fromthe default location (INSTALL_PATH\OpsCenter\server\db\data).


To move the OpsCenter database to a different hard disk on UNIX

1 Stop all OpsCenter processes. Enter the following command:


2 The default location of the OpsCenter database in UNIX is/opt/SYMCOpsCenterServer/db/data. To move the database to a customlocation like /usr/mydata,enter the following command:

mv /opt/SYMCOpsCenterServer/db/data /usr/mydata

3 Create a symbolic link to /usr/mydata in/opt/SYMCOpsCenterServer/db/data. To create a symbolic link, enter thefollowing command:

ln -s /usr/mydata /opt/SYMCOpsCenterServer/db/data



You should run and monitor OpsCenter for a certain period after moving thedatabase. If OpsCenter works as expected, you can delete vxpmdb.db from/opt/SYMCOpsCenterServer/db/data.


266

To move the database log files to a different hard disk on Windows

1 Stop all OpsCenter server services. Enter the following command:


2 Navigate to the following location for 32-bit and 64-bit systems respectively:

INSTALL_PATH\OpsCenter\server\db\WIN32

INSTALL_PATH\OpsCenter\server\db\WIN64

Enter the following commands:

dblog -t directory_path\vxpmdb.log database_path\vxpmdb.db

where directory_path is the path where you want to store the database logsand database_path is the path where your database is located.

This command moves the log file that is associated with the OpsCenterdatabase to the new directory (directory_path). It is recommended to usevxpmdb.log as the name of the log file.


To restart all OpsCenter services, enter the following command:


To move the database log files to a different hard disk on UNIX



2 Set the path of the LD_LIBRARY_PATH variable in the following manner:

LD_LIBRARY_PATH=/opt/SYMCOpsCenterDatabase/lib:$LD_LIBRARY_PATH

export LD_LIBRARY_PATH


3 Navigate to the following location:

/opt/SYMCOpsCenterDatabase/bin

Enter the following commands:

./dblog -t directory_path/vxpmdb.log database_path/vxpmdb.db

where directory_path is the path where you want to store your database logfile and database_path is the path where the OpsCenter database is located.

This command moves the log file that is associated with the OpsCenterdatabase to the new directory (directory_path). It is recommended to usevxpmdb.log as the name of the log file.



About database troubleshootingSecurity information about the OpsCenter database is available.

See “About Symantec OpsCenter Web GUI/Symantec OpsCenter server to Sybasedatabase communication” on page 282.

Information about the log files on Windows and UNIX servers is available.

See “About OpsCenter log files on Windows servers” on page 288.

See “About OpsCenter log files on UNIX servers” on page 291.

Configuring remote authentication service inOpsCenter

OpsCenter supports using Symantec Product Authentication Service (AT) remotely.When using the Symantec Product Authentication Service remotely, you installthe authentication server component on a remote computer in the network.

If you were using a remote AT configuration in NOM and upgrade to OpsCenter,you can configure the remote AT after upgrading to OpsCenter.

Use the following procedure to use remote AT with OpsCenter.

Administering Symantec OpsCenterConfiguring remote authentication service in OpsCenter

268

To configure remote AT in OpsCenter

1 Enter the following command for Windows and UNIX platforms respectively:

INSTALL_PATH\OpsCenter\server\bin\changeVxATProperties.batWindows

/opt/SYMCOpsCenterServer/bin/changeVxATProperties.shUNIX

2 The authentication server parameters appear one by one. The current valuesof the parameters are specified in brackets.

The following authentication service parameters are displayed:

The fully qualified host name (FQHN) ofthe server on which the authenticationservice server component is running.

The default value is localhost if theauthentication service is installed on theOpsCenter server.

Authentication Service Host Name

The port number of the server on whichthe authentication service servercomponent is running.

The default value is 2821.

Authentication Service Port Number

The domain name of the broker.

The default value is broker.

Authentication Service Domain Name

The name of the broker user used forinitial authentication.

The default value is admin.

Authentication Service User Name

The password of the broker user used forinitial authentication.

The default value is Vxadmin.

Authentication Service Password

269Administering Symantec OpsCenterConfiguring remote authentication service in OpsCenter

3 To use a remote AT configuration, enter the new values next to the respectiveparameter. If you do not enter a new value for a parameter, the value of theparameter does not change.

Enter the FQHN of the remote server onwhich the authentication service servercomponent is running.

Authentication Service Host Name

Enter the port number of the remoteserver on which the authentication serviceserver component is running.

Authentication Service Port Number

Enter the domain name of the broker.Authentication Service Domain Name

Enter the name of the broker user usedfor initial authentication.

Authentication Service User Name

Enter the password of the broker userused for initial authentication.

Authentication Service Password

4 You must restart the OpsCenter services for these changes to be effective.

Answer y to restart the OpsCenter services.

About backup and restore of OpsCenter andOpsCenter Analytics

The procedures in this section explain how you can back up and restore OpsCenterand OpsCenter Analytics in case of a disaster.

Backing up OpsCenterThe sequence of steps gives an overview about the steps that need to be followedto back up OpsCenter.

Administering Symantec OpsCenterAbout backup and restore of OpsCenter and OpsCenter Analytics

270

To back up OpsCenter in case of a disaster

1 Take a hot backup of the OpsCenter database (vxpmdb) using the dbbackup

script. This script can be run whenever you need to back up your OpsCenterdatabase.

See “Backing up the OpsCenter database ” on page 271.

2 Along with the OpsCenter database, the user information that SymantecProduct Authentication Service manages must be saved in a directory or byusing a NetBackup backup policy.

See “Saving the OpsCenter user profiles managed by Symantec ProductAuthentication Service” on page 272.

Note: You can also create schedules for taking regular database andauthentication profile backups. In this case, NetBackup policies can be createdto back up the specified directories that contain OpsCenter database snapshotsand the authentication service user configuration files.

See theNetBackupAdministrator’s Guide, Volume I for more information onhow to configure a policy and schedule.

3 If you want to change the OpsCenter database password, you also need toback up the database password file.

See “Backing up the OpsCenter database password file” on page 273.

Backing up the OpsCenter databaseOpsCenter is shipped with a database backup script that performs backup of thedatabase without interrupting its operations, which is referred to as hot backup.On UNIX as well as Windows platforms, the script overwrites existing database(db) files before backing up or restoring the database. The database files are asfollows: vxpmdb.db and vxpmdb.log. The script backs up or restores the vxpmdb.dband vxpmdb.log file (if it exists).

Note:Regular file system backups are not sufficient for backing up the OpsCenterdatabase. You must schedule periodic hot backups for the OpsCenter database toavoid losing any important data.

271Administering Symantec OpsCenterAbout backup and restore of OpsCenter and OpsCenter Analytics

To back up the OpsCenter database

1 Log on to the OpsCenter database server host in one of the following ways:

As an administrator or user in the Administrator groupWindows

rootUNIX

2 Open the Windows command prompt or the UNIX console.

3 Run the backup script that is appropriate for your platform. Specify one ofthe following backup directories depending on your platform:

INSTALL_PATH\OpsCenter\server\bin\dbbackup.bat

C:\MyDbBackupFolder

Windows

/opt/SYMCOpsCenterServer/bin/dbbackup.sh

/my_db_backup_dir

UNIX

The backup script creates vxpmdb.db and vxpmdb.log (if it exists) in thebackup directory that you specified.

Saving the OpsCenter user profiles managed by SymantecProduct Authentication ServiceUse the following procedures to save the authentication service profiles onWindows and UNIX servers.

To save authentication service profiles on Windows servers

◆ Do one of the following to save the user profiles:

■ Copy the folderINSTALL_PATH\VERITAS\Security\Authentication\systemprofile toanother folder.

■ Create a NetBackup job policy to back up the authentication servicesystemprofile folder.

To save authentication service profiles on UNIX servers

◆ Do one of the following to save the user profiles:

■ Copy the folder /var/VRTSat to another folder.

■ Create a NetBackup job policy to back up the authentication service profilefolder.


272

Backing up the OpsCenter database password fileIf you want to change the OpsCenter database password you also need to back upthe following password file (along with the backup of the OpsCenter database filesand authentication service profile folders that are mentioned previously).

To back up the OpsCenter database password file on Windows

◆ Back up the db.conf file that is located inINSTALL_PATH/OpsCenter/server/config directory.

To back up the OpsCenter database password file on UNIX

◆ Back up thedb.conf file that is located in/opt/SYMCOpsCenterServer/config

directory.

Restoring OpsCenterA restore of OpsCenter requires that the new OpsCenter server has the same hostname and IP address of the old server that crashed. This limitation involvesauthentication service credentials (host name and IP address) which are storedon the server.

Note: The following procedures assume that you have OpsCenter databasesnapshots and the authentication service user profiles saved in folders.

The sequence of steps gives an overview about the steps that need to be followedto restore OpsCenter.

To restore OpsCenter in case of a disaster

1 Install OpsCenter on a server with the same name as the server whereproblems happened.

2 Stop all OpsCenter server services.

3 Restore the OpsCenter database snapshot files and authentication serviceuser profiles from the backup image.

See “Restoring the OpsCenter database” on page 274.

See “Restoring the OpsCenter user profiles managed by Symantec ProductAuthentication Service” on page 276.

4 If you saved a copy of the OpsCenter database password file, copy the file tothe corresponding location on the newly installed OpsCenter server. Copythe db.conf file to INSTALL_PATH/OpsCenter/server/config directory onWindows or /opt/SYMCOpsCenterServer/config directory on UNIX.



Restoring the OpsCenter databaseAfter you back up the database, you can restore it. On Windows and UNIX hosts,the restore operation automatically stops the database, restores the backupdatabase files, and restarts the database. The dbbackup script overwrites existingdatabase (db) files before backing up or restoring the database. The database filesare as follows: vxpmdb.db and vxpmdb.log. The script backs up or restores thevxpmdb.db and vxpmdb.log file (if it exists).


274

To restore a backed up OpsCenter database

1 On the OpsCenter server whose backup data you want to restore, open a UNIXconsole or a Windows command prompt and log on as root (on UNIX) or asan administrator or user in the Administrators group (on Windows).

Open a Windows command prompt and log on as an administratoror user in the Administrators group.

Windows

Open a UNIX console and then log on as root.UNIX

All the paths that are shown in the steps that follow are the default databaseinstall paths. These paths may different for your site if the database wasinstalled anywhere other than the default location.

2 To restore the backed up database, do one of the following:

Type the following command and press Enter.

INSTALL_PATH\OpsCenter\server\bin\dbbackup.bat<backupDir> -restore <restoreDir>

Windows

Type the following command and press Enter.

/opt/SYMCOpsCenterServer/bin/dbbackup.sh<backupDir> -restore <restoreDir>

UNIX

where backupDir is the directory where the backed up database resides, and<restoreDir> is the location of the current OpsCenter database.

restoreDir is optional.

If not used, the dbbackup script restores to the default database directory:

INSTALL_PATH\OpsCenter\server\db\dataWindows

/opt/SYMCOpsCenterServer/db/dataUNIX

If you specified a non-default directory location, you must specify therestoreDir option.

The script prompts you with a message similar to the following:

WARNING: this operation will overwrite the active

OpsCenter data on this host.

Do you wish to continue ? [y/n] (n)


3 To continue with the restore, press Enter on Windows hosts.

To continue with the restore, type y on UNIX hosts.

The dbbackup script automatically stops and restarts the database.

Restoring the OpsCenter user profiles managed by SymantecProduct Authentication ServiceUse the following procedures to save the authentication service profiles onWindows and UNIX servers.

To restore the authentication user profiles on Windows

1 Stop all OpsCenter server services. Enter the following command:


2 Copy or overwrite the folder containing the authentication service userprofiles to INSTALL_PATH\VERITAS\Security\Authentication\systemprofile.

3 Start all OpsCenter server services. Enter the following command:


To restore the authentication user profiles on UNIX



2 Copy or overwrite the folder containing the authentication service userprofiles to /var/VRTSat

3 Start all OpsCenter server processes. Enter the following command:


About communication and firewall considerationsFigure 4-1 shows the key Symantec OpsCenter components and how theycommunicate.

Administering Symantec OpsCenterAbout communication and firewall considerations

276

Figure 4-1 Key Symantec OpsCenter components and how they communicate

OpsCenter Server

OpsCenter WebGUI

Web Browser

Hosts where backupproducts like Backup

Exec, PureDisk etc. areinstalled

NetBackup MasterServer without NBAC

Hosts where backupproducts like BackupExec, PureDisk etc..are

installed

OpsCenter Database

SNMPtraps

Port 162

DefaultPort 13786

PBXdefault port

1556SMTPemail

PossibleFirewall

PossibleFirewall

PossibleFirewall NetBackup Master

Server with NBAC

PBXdefault port

1556

The following HTTP and HTTPS port combinations arechecked for availability in the specified sequence and the

first available port combination is used as the default HTTPand HTTPS port respectively - Port 80 and Port 443, Port

8181 and Port 8443, and, Port 8282 and Port 8553.

ViewBuilderConsole

Table 4-6 shows the default port settings for Symantec OpsCenter.

SMTP recipient ports can be configured from the Symantec OpsCenter console(using Settings > Configuration > SMTP Server). The SNMP trap recipient portscan also be configured from the Symantec OpsCenter console (using Settings >Recipients > SNMP).

If these ports are changed then the appropriate hardware ports have to be opened.

Table 4-6 shows the key Symantec OpsCenter components and the communicationports that are used.

277Administering Symantec OpsCenterAbout communication and firewall considerations

Table 4-6 Communication ports used by key Symantec OpsCenter components

Port ConfigurationUsage (ProcessName)

Port NumberDestinationHost

SourceHost

Allow from source to destination.SMTP25Mail ServerSymantecOpsCenterServer

Allow from source to destination.SNMP traprecipient

162SNMP ServerSymantecOpsCenterServer

Allow between source and destination(bi-directional).

PBX port number configuration is supported.

PBX(pbx_exchange)

1556NetBackupMasterServer(s)

SymantecOpsCenterServer

Allow between source and destination.

Some hardened servers and firewallconfigurations may block this port.

PBX port number configuration is not supported.

PBX(pbx_exchange)

1556SymantecOpsCenterServer

SymantecOpsCenterClient

Allow from all hosts on network.HTTP andHTTPS

The followingHTTP and HTTPSports are checkedfor availability inthe specifiedsequence and thefirst availableport combinationis used by default:

1 80 (HTTP)and 443(HTTPS)




WebBrowser

Allow between source and destination.

Some hardened servers and firewallconfigurations may block this port.

Sybase database(dbsrv11)

13786SymantecOpsCenterServer



278

Table 4-6 Communication ports used by key Symantec OpsCenter components(continued)

Port ConfigurationUsage (ProcessName)

Port NumberDestinationHost

SourceHost

Allow between source and destination in caseNBAC is enabled on NetBackup master server.

SymantecProductAuthenticationService (vxatd)

2821Host whereSymantecProductAuthenticationService (AT)Server isinstalled


About ports required to communicate with backup productsThis section provides information about the ports that Symantec OpsCenter Agentuses to communicate with backup products like NetBackup, Backup Exec, PureDisk,and TSM.

Table 4-7 lists the ports that must be opened on Symantec OpsCenter Agent tocollect data from various backup products.

Table 4-7 Ports required to communicate with other backup product

Port numberCommunicationBackup product

13782 & 13724Symantec OpsCenter (NetBackupdata collector) communicates withthe NetBackup master server.

13782 port should be used toconnect to the NetBackup masterserver and 13724 port should beused to respond to the Agent host.The response is sent on a port inthe reserved port range 512-1023if not configured to use vnetd

The following processes are usedfor NetBackup data collection:

■ bperror.exe

■ bpretlevel.exe

■ bpimagelist.exe

NetBackup


Table 4-7 Ports required to communicate with other backup product(continued)

Port numberCommunicationBackup product

6106Symantec OpsCenter (Backup Execdata collector) communicates withBackup Exec Server using BackupExec API

Backup Exec

443 (HTTPS)

2821 (AT)

Symantec OpsCenter (PureDiskdata collector) communicates withPureDisk SPA by atssl

PureDisk

1500Symantec OpsCenter (TSM datacollector) communicates with TSMServer using TSM CLI dsmadmc

TSM

This is a local hostcommunication

Symantec OpsCenter (Legato datacollector) communicates withLegato Server locally

EMC LegatoNetworker

About Web browser to Symantec OpsCenter Web GUI connectionWeb browsers use Insecure hypertext transfer protocol (HTTP) and Securehypertext transfer protocol (HTTPS) to communicate with the Symantec OpsCenterWeb GUI. These protocols use TCP/IP.

For HTTP, specific ports are checked for availability in a particular sequence andthe first available port is used by default.

Table 4-8 lists how the default HTTP and HTTPS ports are selected.


280

Table 4-8 Default HTTP and HTTPS ports

DescriptionHTTPS portnumber

HTTP portnumber

Sr.No.

Port 80 and Port 443 are checked foravailability.

■ If port 80 and port 443 are available, port80 is used as the default HTTP port andport 443 is used as the default HTTPSport.

■ In case, one or both ports are used bysome other application like a Web server, then the next port combination ischecked for availability.

443801.


■ If port 8181and port 8443 are available,port 8181 is used as the default HTTPport and port 8443 is used as the defaultHTTPS port.

■ In case, one or both ports are used bysome other application like VRTSWebinstalled with VCS or any other product,then the next port combination ischecked for availability.

844381812.


855382823.

These HTTP and HTTPS ports are opened only for input and are configurableusing the command lines.

to configure these ports.

About Symantec OpsCenter Web GUI to Symantec OpsCenter serversoftware communication

The Symantec OpsCenter Web GUI uses Symantec Private Branch Exchange (PBX)to communicate with the Symantec OpsCenter server software. The default portis 1556. The PBX port is opened for input and output traffic.

The PBX port number can be changed while adding or editing a master server.


About Symantec OpsCenter server to NetBackup master server (NBSL)communication

Symantec OpsCenter requires the NetBackup Service Layer (NBSL) to be presenton all managed master servers.

The Symantec OpsCenter server software collects data from NBSL in the followingways:

■ Initial data load

■ Listening for change notifications or events.

Whenever Symantec OpsCenter server software starts or when a master serveris added to Symantec OpsCenter, Symantec OpsCenter collects all the data fromthe master server during the initial data load. As soon as the initial data load isdone, the Symantec OpsCenter server software listens to notifications or eventssent by NBSL for any change in NetBackup data and updates the SymantecOpsCenter database. This applies to the data collection related to NetBackuppolicies, jobs, media, and devices. This does not apply to catalog data and datarelated to NetBackup logs.

Symantec Private Branch Exchange is used for communication and requires aport opened for input and output. The default PBX port used is 1556.

The PBX port number can be changed while adding or editing a master server.

Information on PBX is available.

See About Symantec OpsCenter Web GUI to Symantec OpsCenter server softwarecommunication in the OpsCenter Guide.

Information on how to use NBAC with NetBackup servers is available.

About SNMP trapsSNMP trap protocol is used for outbound UDP traffic and requires a port thatopens for output. The port number is 162.

About Symantec OpsCenter Web GUI/Symantec OpsCenter server toSybase database communication

The Symantec OpsCenter Web GUI communicates with the Symantec OpsCenterSybase SQL Anywhere database server by using the default port 13786.

The Sybase database server port is closed to all inbound connections. The databaseis available only to resident Symantec OpsCenter components on the SymantecOpsCenter server.


282

About Symantec OpsCenter Web GUI to Symantec OpsCenter serveremail communication

SMTP email server protocol is used for outgoing mail. The port number is definedwhen the SMTP server port is specified by the user (see Settings>Configuration>SMTPServer in the Symantec OpsCenter console to specify this port). The portis opened for output only.

Gathering troubleshooting data with the supportscript

If you are running OpsCenter on UNIX or Windows, you can use the support scriptto gather troubleshooting information for OpsCenter Server and OpsCenter Agent.The script collects Server and Agent logs, collects information about any datacollection problems, captures the current Agent configuration, and compressesthe results into a zip file. This file can serve as a first-level information for theSupport team in case of an issue with OpsCenter.

283Administering Symantec OpsCenterGathering troubleshooting data with the support script

To gather troubleshooting data for OpsCenter Server on Windows

1 Run the following command to execute the support script for OpsCenterServer:

INSTALL_PATH\OpsCenter\server\bin\opsCenterSupport.bat

Note: The following is the default directory location on Windows machines.

2 The script then prompts the following questions:

Do you want to collect configuration files? [y/n] y

Do you want to collect application log files? [y/n] y

Do you want to collect OpsCenter GUI <147> log files? [y/n] y

Do you want to collect OpsCenter Server <148> log files? [y/n] y

Do you want to collect db log files? [y/n] y

Do you want to collect WebServer log files? [y/n] y

Do you want to collect setEnv file? [y/n] y

Do you want to collect database files? [y/n] y

If this is an upgrade scenario, do you want to collect old database and logfiles? [y/n] y

If this is an install scenario, do you want to collect installation logs? [y/n]y

Answer y or n based on your preferences.

3 This script collects system information and OpsCenter configurationinformation based on your preferences. It then compresses all this informationin a file that is called Support.zip. You can use OpsCenter and run the supportscript in the background.

Note: Adding log files and OpsCenter database files can increase the file sizeof the resulting Support.zip file.

4 The Support.zip file is stored in the following directory:

INSTALL_PATH\OpsCenter\server\temp\support

Administering Symantec OpsCenterGathering troubleshooting data with the support script

284

To gather troubleshooting data for OpsCenter Agent on Windows

1 Run the following command to execute the support script for OpsCenterAgent:

INSTALL_PATH\OpsCenter\Agent\bin\opsCenterAgentSupport.bat

Note: The following is the default directory location on Windows machines.

2 The script stops the OpsCenter Agent service and then collects the OpsCenterAgent logs. It then collates this information in a Support.zip file.

3 This zip file is stored in the following directory:

INSTALL_PATH\OpsCenter\Agent\temp\support

4 After the Support.zip file is created, the script starts the OpsCenter Agentservice.

To gather troubleshooting data for the OpsCenter Server on UNIX

1 Run the following commands to execute the support scripts for OpsCenterServer:

/opt/SYMCOpsCenterServer/bin/opsCenterSupport.sh

2 The script then prompts the following questions:

Do you want to collect configuration files? [y/n] y

Do you want to collect application log files? [y/n] y

Do you want to collect OpsCenter GUI <147> log files? [y/n] y

Do you want to collect OpsCenter Server <148> log files? [y/n] y

Do you want to collect db log files? [y/n] y

Do you want to collect WebServer log files? [y/n] y

Do you want to collect setEnv file? [y/n] y

Do you want to collect database files? [y/n] y

If this is an upgrade scenario, do you want to collect old database and logfiles? [y/n] y

If this is an install scenario, do you want to collect installation logs? [y/n]y

Answer y or n based on your preferences.

285Administering Symantec OpsCenterGathering troubleshooting data with the support script

3 This script collects system information and OpsCenter configurationinformation based on your preferences. It then collates all this informationin a support.zip file. You can use OpsCenter and run the support script inthe background.

Note: Adding log files and OpsCenter database files can increase the file sizeof the resulting support.zip.

4 The support.zip file is stored in the following directory:

/opt/SYMCOpsCenterServer/temp/support

To gather troubleshooting data for the OpsCenter Agent on UNIX

1 Run the following command to execute the support script for OpsCenterAgent:

/opt/SYMCOpsCenterAgent/bin/opsCenterAgentSupport.sh

Note: The following are the default directory locations on UNIX machines.

2 The script stops the OpsCenter Agent process and then collects the OpsCenterAgent logs. It then collates this information in a support.zip file.

3 The support.zip file is stored in the following directory:

/opt/SYMCOpsCenterAgent/temp/support

4 After the zip file is created, the script automatically starts the OpsCenterAgent process.

About OpsCenter log filesOpsCenter creates log files that you can use to troubleshoot installation,performance, and other issues. OpsCenter writes log files using Veritas UnifiedLogging (VxUL), legacy, and other log file formats.

See “About OpsCenter log files on Windows servers” on page 288.

See “About OpsCenter log files on UNIX servers” on page 291.

About VxUL log filesThe VxUL log file creates log file names and messages in a format that isstandardized across all Symantec components. These messages use VxUL IDs (a

Administering Symantec OpsCenterAbout OpsCenter log files

286

product ID and an originator ID) that identify the component that wrote the logmessage.

OpsCenter components create most log messages in VxUL format.

Table 4-9 shows the originator IDs used by OpsCenter and key shared components.

Table 4-9 VxUL IDs used by OpsCenter components

Originator nameVxUL originator ID

Symantec Private Branch Exchange service (PBX)103

NetBackup Service Layer (NBSL)132

Symantec OpsCenter Agent146

Symantec OpsCenter Web GUI147

Symantec OpsCenter Server148

In Windows, OpsCenter writes VxUL logs to the following directory:

INSTALL_PATH\OpsCenter\server\logs

In UNIX, OpsCenter writes VxUL logs to the following directory:

/opt/SYMCOpsCenterServer/logs

You can control how OpsCenter writes log files for OpsCenter Server, OpsCenterAgent, and the OpsCenter Web GUI.

The following OID values must be used for OpsCenter Server, OpsCenter Agent,and OpsCenter Web GUI.

148OpsCenter Server

146OpsCenter Agent

147OpsCenter Web GUI

Table 4-10 lists the commands by which you can control logging on Windows.

287Administering Symantec OpsCenterAbout OpsCenter log files

Table 4-10 Control logging on Windows

CommandControl Logging

INSTALL_PATH\OpsCenter\server\bin\vxlogcfg.exe-a -p 58330 -o <OID> -s LogDirectory="<New logdirectory location>"

Note: 58330 is the OpsCenter product ID.

To change the log directory destination(default value is

<INSTALL_PATH\OpsCenter\server\logs

INSTALL_PATH\OpsCenter\server\bin\vxlogcfg.exe-a -p 58330 -o <OID> -s DebugLevel=1

To configure the verbosity level (defaultvalue is 1)

INSTALL_PATH\OpsCenter\server\bin\vxlogcfg.exe-a -p 58330 -o <OID> -s DiagnosticLevel=1

To configure the diagnostic level(default value is 1)

INSTALL_PATH\OpsCenter\server\bin\vxlogcfg.exe-a -p 58330 -o <OID> -s NumberOfLogFiles=100

To configure the number of log filesthat are created (default value is 100)

Table 4-11 lists the commands by which you can control logging on UNIX.

Table 4-11 Control logging on UNIX

CommandControl logging

/opt/SYMCOpsCenterServer/bin/vxlogcfg -a -p58330 -o <OID> -s LogDirectory="<New logdirectory location>"

Note: 58330 is the OpsCenter product ID.

To change the log directory destination(default value is<INSTALL_PATH/SYMCOpsCenterServer/logs)

/opt/SYMCOpsCenterServer/bin/vxlogcfg -a -p58330 -o <OID> -s DebugLevel=<New debug level>

To configure the debug level (defaultvalue is 1)

/opt/SYMCOpsCenterServer/bin/vxlogcfg -a -p58330 -o <OID> -s DiagnosticLevel=<Newdiagnostic level>

To configure the diagnostic level(default value is 1)

/opt/SYMCOpsCenterServer/bin/vxlogcfg -a -p58330 -o <OID> -s NumberOfLogFiles=<Newnumber>

To configure the number of log filesthat are created (default value is 100)

About OpsCenter log files on Windows serversOpsCenter creates the following log files using VxUL and legacy formats.


288

About OpsCenter 7.0 installation log filesTable 4-12 shows details about the installation log files for OpsCenter components.These log files can be used to troubleshoot installation issues of the respectiveOpsCenter component.

Table 4-12 OpsCenter 7.0 installation log files

Log fileOpsCentercomponent

%ALLUSERSPROFILE%\Symantec\OpsCenter\INSTALLLOGS\OpsCenterServerInstallLog.html

OpsCenterServer

%ALLUSERSPROFILE%\\Symantec\OpsCenter\INSTALLLOGS\OpsCenterAgentInstallLog.html

OpsCenterAgent

%ALLUSERSPROFILE%\\Symantec\OpsCenter\INSTALLLOGS\OpsCenterViewBuilderInstallLog.html

OpsCenterViewBuilder

For all OpsCenter 7.0.1 components, an installation log file namedOpsCenterMaintPackInstallLog.htm is generated in the following location:

%ALLUSERSPROFILE%\Symantec\OpsCenter\INSTALLLOGS

About OpsCenter log filesTable 4-13 shows details about the OpsCenter log files.

Table 4-13 OpsCenter log files

Troubleshooting purposeLog fileLog file directory

These log files for system.err andsystem.out of OpsCenter serverservice.

ServerService_timestamp.logINSTALL_PATH\OpsCenter\server\logs\

About log files associated with Symantec ProductAuthentication ServiceTable 4-14 lists the log files that are associated with Symantec ProductAuthentication Service.


Table 4-14 Log files for Symantec Product Authentication Service


Authentication activity.vxatd.log

vssconfig.log

On 32-bit Windowsplatforms:%ProgramFiles%\Veritas\Security

\Authentication\bin

On 64-bit Windowsplatforms:%ProgramFiles(x86)%

\Veritas\Security

\Authentication\bin

About OpsCenter database log filesTable 4-15 lists the log files that are associated with the OpsCenter database.

Table 4-15 Log files associated with the OpsCenter database


OpsCenter Sybase databaseactivity.

server.logINSTALL_PATH\OpsCenter\server\db\log\

OpsCenter Sybase databasetransaction files.

Note: Do not change this log file.

vxpmdb.logINSTALL_PATH\OpsCenter\server\db\data\

About OpsCenter Web server log filesThe log files that are associated with the OpsCenter Web server are present in theINSTALL_PATH\OpsCenter\WebServer\logs directory.

About VxUL log files for OpsCenter and the components thatOpsCenter usesTable 4-16 lists the log files that are associated with VxUL and other componentsthat OpsCenter uses.


290

Table 4-16 Log files associated with VxUL and other components

Troubleshootingpurpose

Log fileLog file directory

PBX activity.50936-103-*.logINSTALL_PATH\VERITAS\VxPBX\bin\

NBSL activity.51216-132-*.logINSTALL_PATH\VERITAS\NetBackup\logs\

Agent activity.51216-146-*.logINSTALL_PATH\OpsCenter\Agent\logs

OpsCenter WebGUI activity.

51216-147-*.logINSTALL_PATH\OpsCenter\gui\logs\

OpsCenter serveractivity.

58330-148*.logINSTALL_PATH\OpsCenter\server\logs

About OpsCenter log files on UNIX serversOpsCenter creates the following log files by using VxUL and legacy formats.

About log files associated with OpsCenterTable 4-17 lists the log files for OpsCenter.

Table 4-17 Log files for OpsCenter

Troubleshooting purposeOpsCenter log file

stdout and stderr for the OpsCenterServerdaemon.

/opt/SYMCOpsCenterServer/logs/OpsCenterServer_out.log

Shows the details of purge operations./opt/SYMCOpsCenterServer/logs/purge-status.log

Provides a trace for any installation issues./var/VRTS/install/logs/ (directory)

About log files for Symantec Product Authentication ServiceTable 4-18 lists the log files that are associated with Symantec ProductAuthentication Service.

Table 4-18 Log files for Symantec Product Authentication Service

Troubleshooting purposeLog file

Authentication activity./var/VRTSat/vxatd.log


About log files associated with OpsCenter databaseTable 4-19 lists the log files that are associated with the OpsCenter database.

Table 4-19 Log files associated with OpsCenter database


OpsCenter Sybase database activity./opt/SYMCOpsCenterServer/db/log/dbserver.log

OpsCenter Sybase database transaction files.

Note: Do not change this log file.

/opt/SYMCOpsCenterServer/db/data/vxpmdb.log

About log files associated with OpsCenter Web serverTable 4-20 lists the log files that are associated with the OpsCenter Web server.

Table 4-20 Log files associated with the OpsCenter Web server

Troubleshooting purposeOpsCenter log directory

OpsCenter Web GUI application activity (stdout)./opt/SYMCOpsCenterWebServer/logs

About log files associated with VxUL and other componentsTable 4-21 lists the log files that are associated with VxUL and other components.

Table 4-21 Log files associated with VxUL and other components


PBX activity./opt/VRTSpbx/log/50936-103-*.log

NBSL activity./opt/openv/logs/51216-132-*.log

OpsCenter Agent activity./opt/SYMCOpsCenterAgent/logs/51216-146-*.log

OpsCenter Web GUI activity./opt/SYMCOpsCenterGUI/logs/51216-147-*.log

OpsCenter server activity./opt/SYMCOpsCenterServer/logs/558330-148*.log


292

Understanding OpsCentersettings


■ About the settings in OpsCenter

■ Setting user preferences

■ Managing licenses

■ Configuring data purge settings

■ Configuring SMTP server

■ Configuring Symantec ThreatCon feature in OpsCenter

■ Adding host aliases

■ Merging objects (hosts)

■ Modifying Tape Library information

■ Copying user profiles

■ Setting report export location

■ Managing Object Types

■ Managing users

■ Managing recipients

■ Managing cost analysis and chargeback for OpsCenter Analytics

5Chapter

About the settings in OpsCenterThis section describes the various OpsCenter settings. An OpsCenter Admin canconfigure these settings using the OpsCenter console. The normal users can viewor access the information that is relevant only to their profiles, which theOpsCenter Administrator has set.

Following are the various settings that you can configure in OpsCenter.

Table 5-1 Settings in OpsCenter

Reference topicLets you...Name of thesetting

See “Setting userpreferences” on page 295.

Add user-specific details and create userprofiles.

User Preferences

See “Configuring datacollection for NetBackup”on page 346.

Add NetBackup master servers and theirproperties to collect data from it.

NetBackup

See “Managing OpsCenterAgents” on page 339.

Create Agent and Data Collectors tocollect data from non-NetBackupproducts.

Agent

See “ Adding license keys”on page 300.

Manage permanent or demo license keys.License

See “Configuring data purgesettings” on page 301.

Specify when you want to purge the datathat is collected from various products.

Data Purge

See “Configuring SMTPserver” on page 303.

Configure the SMTP server details thatyou need while sending reports or alertsthrough emails.

SMTP Sever

See “Configuring SymantecThreatCon feature inOpsCenter” on page 304.

Configure Symantec ThreatCon featurein OpsCenter.

The Symantec ThreatCon feature is usedto show how secure or vulnerable yournetwork is.

ThreatCon

See “Adding host aliases”on page 305.

Add aliases for hosts.Host Alias

See “Merging objects (hosts)” on page 306.

Configure OpsCenter to merge the objectsthat represent the same backup client,but registered as separate objects

Object Merger

Understanding OpsCenter settingsAbout the settings in OpsCenter

294

Table 5-1 Settings in OpsCenter (continued)

Reference topicLets you...Name of thesetting

See “Merging objects (hosts)” on page 306.

Modify tape library informationTape Library

See “Copying user profiles”on page 307.

Configure OpsCenter to copy a user'sprofile to another user.

Copy User Profile

See “Setting report exportlocation” on page 308.

Specify the location where the exportedreports are stored.

Report ExportLocation

See “Managing ObjectTypes” on page 308.

Add new object types and attributes.Object Type

See “Managing views”on page 387.

Create and manage OpsCenter views.Views

See “Managing users”on page 310.

Manage users and user groups.Users

See “Managing recipients”on page 317.

Manage Email and SNMP recipients.Recipients

See “Setting a defaultcurrency for cost reports”on page 323.

Manage the currency settings that appearin cost reports. You can select a currencyfrom the global currency list and set it asdefault.

CurrencySettings

See “Managing CostVariables” on page 325.

Create cost variables.Cost Variables

See “Managing costformulae” on page 328.

Create cost formulae.Cost Formulae

See “Managing costestimation” on page 329.

Manage cost estimationCost Estimation

Setting user preferencesIn OpsCenter, you can set your preferences, such as default locale or time zoneand personal details, such as email ID or name. You can also change your passwordusing the User Preferences tab, if your user account belongs to the OpsCenterUsersdomain.

295Understanding OpsCenter settingsSetting user preferences

To set user preferences

1 In the OpsCenter console, click Settings > User Preferences. The userpreferences options are organized in the General and My Profile tabs.

Understanding OpsCenter settingsSetting user preferences

296

2 Click the General tab to set the following user preferences:

Select a locale of your choice from the drop-down list. For example,if you select English as a default locale, all OpsCenter GUI screensuse English as a default language.

Default Locale

Select a preferred time zone - either OpsCenter Server time zoneor any other time zone from the Other drop-down list. OpsCenter

Data DisplayTime Zone

displays time on the GUI screens according to the selected timezone.

Enter the time that is used as the start time of a day in reports.Report data is grouped depending on this start time.

Start 24 HourDay at

Select this check box if you do not want to automatically refreshthe OpsCenter GUI.

Disable AutoRefresh

By default, the auto-refresh option is enabled.

Enter auto-refresh interval in minutes. For example, if you wantto refresh the OpsCenter GUI to show updated data after every 5minutes, enter five in the Auto Refresh Interval text box.

Auto RefreshInterval(Minutes)


Select this check box if you want to select multiple nodes or viewobjects in the View Pane. When you check this option, you can seea check box next to each master server or node in the View Pane.To view data for multiple master servers and nodes, you check thecorresponding check boxes and then click Apply Selection.

By default, the multiple-selection option is enabled.

When you uncheck the multiple-selection option, you can onlyselect a single node or view object from the View Pane at a giventime. You can make selections in the View Pane in a similar manneras NetBackup Operations Manager (NOM). Each node or a viewobject is a link. You can click a node or a view object to view datafor the respective node or view object. For example, you can clicka master server in the View Pane to view data for the specificmaster server.

See “About making multiple or single-click selections in the Viewpane” on page 60.

In addition when you uncheck the multiple-selection option, aGroup Component Summary table is displayed when you clickMonitor > Jobs and select Summary View from the drop-downlist. The Group Component Summary table was also displayed inNOM earlier. The GroupComponentSummary table shown at thebottom of the view displays job summary information about theimmediate NetBackup constituents of the selected view or node(group) in the View pane. For example if you select the ALLMASTER SERVERS view, the Group Component Summary tabledisplays job summary for each master server.

More details about the Group Component Summary table areavailable.

See “About the Group Component Summary table” on page 419.

Allow MultipleSelection in ViewPane

3 Click Save.

Understanding OpsCenter settingsSetting user preferences

298

4 Click the My Profile tab to view the following options:

You can modify some of the options.

Displays the user name.User Name

The OpsCenter security admin sets a default password for eachuser when it creates the profiles.

The users that belong to the “OpsCenterUsers” domain can changetheir passwords after logging on .

To change password, click the Change Password link.


The users from other domains cannot change their passwords usingthis option.

Password

The role of this userUser Role

Name of the domain to which this user belongsDomain Name

The email address of this userEmail Address

In General details, you can see the following information

Displays the first name of the userFirst Name

Displays the last name of the userLast Name

Displays the cost center user belongs toCost Center

Displays the department of the user.Department

Displays the work number of the user.Work Number

Displays the mobile number of the user.Mobile Number

Displays the pager number of the user.Pager Number

5 Click Save.

Changing your passwordIt is recommended that you change the administrator-assigned password the firsttime you logon to Symantec OpsCenter console and then change it at regularintervals thereafter.


To change the password with which you log on to OpsCenter

1 In the OpsCenter console, click Settings > My Profile.

2 In the My Profile dialog box, click Change Password.

3 In the Change Password dialog box, do the following:

■ Type the existing password in the Old Password field.

■ Type the new password in the New Password field.

Passwords are case sensitive and must contain at least five characters.

■ Type your new password again in the Confirm New Password text box.

4 Click Save.

Managing licensesThis section provides procedures to manage license keys from the OpsCenter.

To use the advanced features that are not available in Symantec OpsCenter, youneed to use a license key and enable Symantec OpsCenter Analytics.

See “About Symantec OpsCenter” on page 19.

See “ Adding license keys” on page 300.

See “ Viewing license keys” on page 301.

See “ Deleting license keys” on page 301.

Adding license keysAn OpsCenter administrator can install OpsCenter license keys to activateadditional product features or delete the license keys that are no longer needed.

You can add one or more OpsCenter license keys.

To addOpsCenterlicense keys

1 Logon to the OpsCenter server host as admin.

2 In the console, click Settings > Configuration .

3 Click the License tab.

4 Click Add.

5 On the Add License Key pop-up screen, enter a license key and click OK.

Understanding OpsCenter settingsManaging licenses

300

Viewing license keysYou can view the license keys that are installed on the OpsCenterserver host.

To view OpsCenter license keys

1 Logon to the OpsCenterServer host as admin.

2 In the console, click Settings > Configuration.


Deleting license keysYou can remove one or more Symantec OpsCenter Analytics license keys fromthe OpsCenter Server, on which you are connected as an administrator.

To delete Symantec OpsCenter Analytics license keys

1 Log on to the OpsCenter Server host as admin.

2 In the OpsCenter console, click Settings > Configuration.


4 Select the check box in front of the license key that you want to delete.

5 Click Delete.

Configuring data purge settingsYou can configure the OpsCenterServer retention periods for the data types thatare logged, such as Job, Policy, and Skipped Files.

Note: The details of the purged data are stored in the purge-status.log file,which is located in the OpsCenter server logs directory.

To configure data purge period on the OpsCenterServer

1 Log on to the OpsCenter console as admin.

2 In the OpsCenter click Settings > Configuration.

3 Click the Data Purge tab.

By default, data purge is enabled.

301Understanding OpsCenter settingsConfiguring data purge settings

4 Edit the default data purge settings for the following data:

Set the number of days after which you want to purge the backupjobs.

The number of days set for backup logs should be less than or equalto the number of days set for backup jobs. In other words, logs canbe purged earlier than their respective jobs, or they can be purgedat the same time.

For example,

Note: If logs are purged but the respective jobs are not purged,the corresponding logs are collected again.

For example: The data purge setting for backup jobs is set to 10days and for Backup Logs are five days. The backup logs are purgedafter five days but the related jobs are still present. Because, thebackup jobs are set to be purged after 10 days.

Thus, the logs of such jobs are collected again by the OpsCenterAgent.

Backup Job

Set the number of days after which you want to purge the backuplogs.

Backup Log

To retain Tape Drive History logsTape DriveHistory

To retain Media History logsMedia History

Enter the number of days for which you want to retain the alertdata. Alert data older than this number is purged from theOpsCenter database.

Alert

5 In the TimeofPurge text box, enter the time of day (in 24-hour clock format)when you want to purge the data.

6 Click Save.

About restoring NOM or VBR purge settings after upgrading toOpsCenter Server 7.0

While upgrading from NOM or VBR to OpsCenter Server, the OpsCenter Serverservice and the data migration process start simultaneously. Since the datamigration from NOM or VBR to the OpsCenter database has just started and isnot complete, the purge settings in OpsCenter take default values and not thevalues that you configured in NOM or VBR.

Understanding OpsCenter settingsConfiguring data purge settings

302

To use the purge settings that you configured for NOM or VBR in OpsCenter 7.0,you must restart the OpsCenter Server service after the data migration is complete.Use the following procedure to restart OpsCenter Server service after the datamigration is complete on Windows and UNIX platforms.

To restart the OpsCenter Server service on Windows

1 Select Control Panel > Administrative Tools > Services and stop theSymantec OpsCenter Server Service.

2 Select Control Panel > Administrative Tools > Services and start theSymantec OpsCenter Server Service.

To restart the OpsCenter Server process on UNIX

1 Enter the following command to stop the OpsCenter Server process:


2 Enter the following command to start the OpsCenter Server process:


Configuring SMTP serverThis section provides the procedure to configure the SMTP server that you canuse for sending emails and alerts.

To configure SMTP server settings for OpsCenter

1 Logon to the OpsCenter server as admin.

2 In the OpsCenter console, click Settings > Configuration.

3 Click SMTP Server.

OpsCenter uses these global server settings to send email notifications usingthe SMTP server that you specify..

303Understanding OpsCenter settingsConfiguring SMTP server

4 Enter the following information:

Enter the SMTP (Simple Mail Transfer Protocol) Serverhost name.

Notifications of alerts that are generated in OpsCenterare sent using this SMTP server.

SMTP server Name

Enter the SMTP (Simple Mail Transfer Protocol) Serverport number.

SMTP server port

Enter the name that is associated with the email ID.For example, Backup Reporting Department

Sender Display Name

Specify the email ID to receive any replies to alerts orthe reports that were sent by OpsCenter.

Sender Display EmailAddress

Some SMTP servers may require user name andpassword credentials to send email.

Enter the user name.

Server User Name

Some SMTP servers may require user name andpassword credentials to send email.

Enter the password for this user account.

Server User Password

5 Click Save.

Configuring Symantec ThreatCon feature inOpsCenter

This section provides information on how to configure the Symantec ThreatConfeature in OpsCenter.

The Symantec ThreatCon feature is used to show how secure or vulnerable yournetwork is.See “About the Symantec ThreatCon pane” on page 63.

Use the following procedure to enable or disable the Symantec ThreatCon feature.The ThreatCon feature is enabled by default. To disable ThreatCon, uncheck thebox next to Enable ThreatCon Collection

To configure Symantec ThreatCon feature on Windows for OpsCenter

1 Log on to the OpsCenterServer with administrator privileges.

2 In the OpsCenter, click Settings > Configuration.

3 Click ThreatCon.

Understanding OpsCenter settingsConfiguring Symantec ThreatCon feature in OpsCenter

304

4 Edit the following default information:

Disable or enable the ThreatCon data collection using this checkbox.

EnableThreatConCollection

Set the minutes for Polling Interval.Polling Interval

Note: The proxy server configuration is not mandatory. Enter thefollowing proxy server details if you want to use it for accessing thelatest ThreatCon ratings, if the default network is down.

Enter the proxy server name.

Server Name

Enter the port number to connect to the proxy server.Port

Enter the user name of the proxy server.User Name

Set the password for the user account that you use to connect to theproxy server.

Password

5 Click Save.

Adding host aliasesThis section provides the procedures to add aliases for hosts.

The host’s primary alias is displayed in all console functions and reports. Otherhost aliases are used when you are search in OpsCenter or gather and collate data.

Warning: It is essential that your alias names are compatible with your hosts’ DNSnames or with the names by which they are known to applications such asNetBackup and Backup Exec. For example, if you use an alias that is unknown toOpsCenter, the explorer stops collecting information from the OpsCenter hostand instead attempts to collect data from a host with the alias name.

To add a host alias

1 In the OpsCenter console, click Settings> Configuration > Host Alias.

2 From the drop-down list select a host name or type a host name, and ClickShow Alias.

All the existing aliases are displayed.

3 Click Add Alias.

305Understanding OpsCenter settingsAdding host aliases

4 Enter the alias name for the host that you have selected from the drop-downlist.

5 click Save

Merging objects (hosts)OpsCenter provides a facility to merge objects (hosts) that represent the samemaster server, media server, backup client, but registered as separate objects(hosts). Using the OpsCenter UI, you can merge only one object into other, at atime.

In OpsCenter, you can merge objects (hosts) representing the same backup client.

Caution: Object merging is not reversible.

To merge two objects

1 Logon to the OpsCenter Server host with administrator privileges.

2 In the OpsCenter console, click Settings > Configuration > Object merger.

3 Select the Host Type: Master Server, Media Server, or Client.

4 Select the Source Host from the drop-down list. An auto-suggest feature isavailable.

5 Select the Target Host from the drop-down list. An auto-suggest feature isavailable.

6 Click Validate Object Merging.

7 You can view the snapshot of the selection that you have made earlier. Tomodify the Source Host or Target Host click Back. To begin the merge clickStart Merge

Repeat these steps if you want to merge more objects.

Modifying Tape Library informationOpsCenter provides a facility to monitor all the tapes that the data collector uses.Using the OpsCenter UI, you can edit the serial number, manufacturer, alias, slotcount of the tape drives the data collector uses.

To modify tape library information in OpsCenter

1 Log on to the OpsCenterServer with administrator privileges.

2 In the OpsCenter, click Settings > Configuration.

Understanding OpsCenter settingsMerging objects (hosts)

306

3 Click Tape Library.

4 You can view the list of the tape libraries in OpsCenter. Select the check boxnext to tape library, for which you want to edit the information.

5 Edit the following information:

Select the type of tape library from the drop-down list.Type

Enter the serial number of the tape librarySerial Number

Enter the manufacturer of the tape library.Manufacturer

Enter the alias for the tape library.Alias

Enter the slot count you want for the tape library.Slot Count

6 Click Save.

Copying user profilesMost user-definable content, such as reports, cost variables, and cost formulas,is accessible only by the user who has created it. Using the copy user profilefunctionality, you can copy information from one user account to another.

Copy user profile

1 Logon to the Symantec OpsCenter Server with administrator privileges.

2 In the OpsCenter console, click Settings>Configuration>CopyUserProfile

3 Select the source user account from the From User drop-down list.

4 Select the target user account from the To User drop-down list.

5 In the Copy Items options, select the items you want to copy, for examplereports or cost rates and formulae.

6 Click Next

7 Select reports or cost rates and formulae to be copied to this user profile.

If you copy a cost formula, the associated cost variables are implicitly copied.

If you copy a cost report, the associated cost formula and variables areimplicitly copied.

8 Click Copy

307Understanding OpsCenter settingsCopying user profiles

Setting report export locationIn OpsCenter you can configure exporting of reports to a predefined location.Data from exported reports is stored in a default directory, if you have not definedany location.

To set reports for exporting

1 Log on to the Symantec OpsCenter Server with administrator privileges.

2 In the OpsCenter console, click Settings > Configuration > Report ExportLocation

3 In the ReportExportLocation box type the directory where you want to savethe reports.

4 Click Save.

Managing Object TypesIn OpsCenter you can add or edit attributes of predefined object types. You canalso add new object types and attributes for those new object types.

To add an object type

1 Logon to the Symantec OpsCenter Server with administrator privileges

2 In the OpsCenter console, click Settings > Configuration > Object Types.

3 Click Add.

4 Enter the name in the Add Object Type pop-up screen.

5 Click OK.

See “Modifying object types” on page 308.

See “Deleting object types” on page 309.

See “Adding attributes” on page 309.

See “Deleting attributes” on page 309.

Modifying object typesYou can only modify the name of an object type that you have created. You cannotmodify the name of the predefined objects in the drop-down list.

To modify an object type name

1 Log on to the Symantec OpsCenter Server with administrator privileges.

2 In the OpsCenter console, click Settings > Configuration > Object Type.

Understanding OpsCenter settingsSetting report export location

308

3 Select the object type that you want to modify from the drop-down list.

You can rename the object types that you have created. You cannot renamethe predefined object types.

4 Click Add.

5 Add

Deleting object typesYou can only delete an object type that you have created. You cannot delete thepredefined objects in the drop-down list.

To delete object types

1 Log on to the Symantec OpsCenter Server with administrator privileges


3 Select the object type from the drop-down list. You can delete the object typesthat you have created. You cannot delete predefined object types.

4 Click Delete

Adding attributesYou can add attributes to all object types.

To add attributes



3 Select the object type from the drop-down list and in Attributes section, clickAdd.

4 Enter the name of the attribute and click OK.

Deleting attributesYou can delete attributes that are added to an object type.

To delete attributes



3 Select the object type from the drop-down list. In the Attributes section,select the check box in front of the attribute you want to delete.

4 Click Delete.

309Understanding OpsCenter settingsManaging Object Types

Managing usersAfter you install Symantec OpsCenter, you need to create user accounts. TheSymantec Product Authentication Service validates credentials of OpsCenterusers based on Windows, NIS, or private domains.


See “ Adding new users” on page 314.

See “Resetting user password” on page 315.

See “Adding user groups” on page 316.

About user access rightsThis section provides information on OpsCenter users and the functions that theycan perform in the OpsCenter GUI.

About OpsCenter UI functionsTable 5-2 provides details of the OpsCenter UI functions that you can perform.

Table 5-2 OpsCenter UI functions

TasksOpsCenterfunctions

The User Management function includes the following tasks:

■ Create, update, delete users

■ Create, update, delete user groups

■ Add, remove users from user groups

■ Assign, remove roles to users and user groups

User Management

The OpsCenter Management function includes the following tasks:

■ Add, Update, Delete Master Server

■ Add, Update, Delete OpsCenter Agents

■ Set default currency, SNMP, SMTP server

OpsCenterManagement

The NetBackup Configuration Management function includes thefollowing tasks:

■ Add, update, delete NetBackup entities: Host Properties, Policy,Media and Devices, and others

NetBackupConfigurationManagement

Understanding OpsCenter settingsManaging users

310

Table 5-2 OpsCenter UI functions (continued)


The NetBackup Operations function includes the following tasks:

Change states of the NetBackup entities as follows:

■ Policy (Activate/De-active)

■ Job (Stop/Start/Suspend/Resume)

■ Media (Assign, Freeze, unfreeze )

■ Drives (Up/Down)

■ Others

NetBackup Operations

The Backup and the Recovery function includes the followingtasks:

■ Execute manual backups

■ Search and restore files, folders, application (Oracle, SQLServer, and Exchange Server)

Backup and Recovery

The Views Management function includes the following tasks:

■ Create, update, delete OpsCenter views and nodes

■ Assign Read / Write permissions to users on OpsCenter viewsand nodes

Views Management

The NetBackup Operations function includes the following tasks:

■ View OpsCenter views and nodes

All Views Read

This function includes the following tasks:

■ Execute report templates and public custom reports

■ Schedule canned and public custom reports

■ Create, update Dashboard

Report Execution


■ Create, update, delete custom reports

■ Make custom reports public and/or private

Custom Reports


■ Create, update, delete custom SQL reports

Custom SQL Reports

Monitoring includes the following tasks:

■ View entities ( Dashboards, Summary, Details): Job, Policy,Media, Alerts, Drives, Others

Monitoring

311Understanding OpsCenter settingsManaging users

Table 5-2 OpsCenter UI functions (continued)


The Alert Management function includes the following tasks:

■ Create, update, delete alert policies

■ Assign, acknowledge, clear alerts

Alert Management

About OpsCenter user rolesOpsCenter users are categorized as follows:

This is a super admin user who can perform all OpsCenter functionsincluding user management.

The OpsCenter Security Administrator can create, edit, or delete users.

Note: An Administrator in VBR (Veritas Backup Reporter) or NOM(NetBackup Operations Manager) is a Security Administrator inOpsCenter.

SecurityAdministrator

This user can perform all OpsCenter functions except for usermanagement.

The OpsCenter Administrator cannot create, edit, or delete users.

Note: A NOM user becomes an Administrator in OpsCenter.

Administrator

This user is not involved in activities that are related to managing users,OpsCenter Server, and NetBackup configuration.

Note: A NOM read-only user becomes an Operator in OpsCenter.

Operator

The role of this user is to mainly analyze the operational andbusiness-level reports. This user cannot perform functions, such as usermanagement or backup & recovery.

The Analyst has the Read permission on all views.

Note: A VBR read-only admin becomes an Analyst in OpsCenter.

Analyst

The role of this user is to mainly generate the operational andbusiness-level reports for further analysis.

Note: A VBR user becomes a Reporter in OpsCenter.

Reporter

About OpsCenter user roles and their functionsTable 5-3 lists the OpsCenter user roles and the OpsCenter UI functions that theseusers can perform.


312

Table 5-3 User roles

ReporterAnalystOperatorAdministratorSecurityAdministrator

OpsCenterfunction

NNNNYUserManagement

NNNYYOpsCenterManagement

NNNYYNetBackupConfigurationManagement

NNYYYNetBackupOperations

NNYYYBackup andRecovery

N

(Restricted to onlypermitted entitiesthrough Java View

Builder)

N

(Restricted to onlypermitted entitiesthrough Java View

Builder)

YYYViewsManagement

Restricted to onlypermitted entities

Restricted to onlypermitted entities

YYYAll ViewsRead

YYYYYReportExecution

YYYYYCustomReports

NNYYYCustom SQLReports

YYYYYMonitoring

YYYYYAlertManagement

“Y” represents “Yes”, which means that the users of this role can perform thisparticular OpsCenter function.

“N” represents “No”, which means that the users of this role cannot perform thisparticular OpsCenter function.


Viewing the list of existing usersYou can view a list of OpsCenter users and their information such as, name, username, access level, authentication domain, and so on. The user information isarranged in a tabular format. You can sort the table by user attributes

To view OpsCenter user account information

1 Log on to the Symantec OpsCenter host with administrator privileges.

2 In the Symantec OpsCenter console, click Settings > Users.

3 Click Users to view the list of users.

Adding new usersYou can either add the existing users that are discovered from various domainsto OpsCenter or create users in the private “OpsCenterUsers” domain.

To add a new user to OpsCenter

1 Log on to the OpsCenter host with administrator privileges.

2 In the OpsCenter console, click Settings > Users.

3 On the Users tab, click Add .

4 Select the user creation type: New User or Existing Domain User.

5 Enter the following general and demographic details of the user:

User name, user role, domain name, email ID, first name, last name,department, cost center, work number, mobile number, and contact details.

The following user information is mandatory:

User Name, Password, Confirm Password, and User Role

See “About OpsCenter user roles” on page 312.

If you have selected the Existing Domain User option, you do not have toenter Password and Confirm Password.

If you have selected the New User option, specify the password, and enter itonce again for confirmation.

6 Click Save.

Editing usersYou can edit the existing users.


314

To edit an existing user



3 On the Users tab, click the check box in front of the user that you want toedit.

4 Click Edit.

5 Modify the user information.

You cannot modify the domain of the user.

You can also reset passwords of the OpsCenter users using this page.

See “Resetting user password” on page 315.

6 Click Save.

Resetting user passwordThis section describes how to reset a user password.

The Reset Password functionality is applicable only for OpsCenter users.

To reset a user password



3 On the Users tab, click the check box in front of the user for whom you wantto reset the password.

4 Edit.

5 In the General Details pane, click Reset Password.

6 On the Reset Password page, enter the new password and confirm passwordfor the selected user.

7 Click Save.

Deleting usersYou can delete the user accounts that do not need to be maintained.

Note: The default OpsCenter user admin cannot be deleted.

Warning: Do not inadvertently delete all your administrator accounts.


To delete a OpsCenter user account



3 Click Users.

4 Check the box next to the user account you want to delete.

5 Click Delete.

Viewing user groupsThis section provides the procedure to view the existing user groups.

To view a user group

1 Log on to the Symantec OpsCenter host with administrator privileges.

2 In the Symantec OpsCenter console, click Settings > Users.

3 Click User Groups to view the list of user groups.

Adding user groupsIf you want to give the same privileges to multiple users, add them to a single usergroup. The same access rights on views are attributed to all users in the user group.

To create an OpsCenter user group



3 Click User Groups.

4 Click Add.

5 On the User Groups tab, enter the name of the group and description.

6 In the List of Users pane, click Add to open the Add Users pop-up screen.

7 On the Add Users pop-up screen, select the users that you want to add to thisuser group.

8 Click OK.

9 On the User Group tab, click Save.

Editing user groupsYou can modify an existing user group.


316

To edit a Symantec OpsCenter user group

1 Log on to the OpsCenter Server host with administrator privileges.


3 Click User Groups .

4 Select the check box in front of the user group that you want to edit.

5 Click Edit.

6 Modify the user group name or description.

7 Add or delete the users using the List of Users pane and Add Users pop-upscreen.

8 Click Save.

Deleting user groupsYou can delete a user group that you no longer need.

To delete a Symantec OpsCenter user group



3 Click User Groups.

4 Select the check box next to the user groups that you want to delete.

5 Click Delete.

Managing recipientsYou can specify the recipients to whom you want to send alert notifications oremail reports.

Note: Make sure that the mail server is configured to send emails.

See “Configuring SMTP server” on page 303.

See “Creating email recipients” on page 319.

See “Creating SNMP trap recipients” on page 321.

Viewing email recipientsThis section provides the procedure to view the available email recipients.

317Understanding OpsCenter settingsManaging recipients

To view the email recipients

1 Log on to the OpsCenter Server host.

2 In the OpsCenter console, click Settings > Recipients.

By default, the Email tab is selected. All email recipients are displayed on thistab.

The following email recipient details are displayed in a table:

Name of the email recipientRecipientName

Email ID of the recipientEmailAddress

The status of the email recipient that states whether it is active or not

If a recipient is not active, it is not available for selection on the AddingEmail Recipients pop-up screen, when emails are sent.

Active

Description about the email recipientDescription

Viewing SNMP trap recipientsThis section provides the procedure to view the available SNMP trap recipients.

To view the SNMP trap recipients

1 Log on to the OpsCenter Server host.

2 In the OpsCenter console, click Settings >Recipients.

3 Click SNMP.

The following trap recipient details are displayed in a table:

Name of the SNMP trap recipientRecipientName

Name of the SNMP hostSNMP Host

Port number on the SNMP host where you want to send trapsPort

The status of the trap recipient that states whether it is active or not

If a recipient is not active, it is not available for selection on the AddingTrap Recipients pop-up screen, when alert policies are configured.

Active

Description about the trap recipientDescription

Understanding OpsCenter settingsManaging recipients

318

Creating email recipientsThis section describes how to create email recipients.

To create email recipients



3 In the Email tab, click Add to create new email recipients.


4 Enter the following information:

Enter the name of the official whom you want to notifyabout an alert or send reports.

Email Recipient Name

Enter the email ID of the official, to which alertnotifications or reports are sent.

Email Address

Select this check box if you want the recipient to receivealert notifications and reports by emails.

Active

Enter a short description about the alert or report sothat recipients can understand.

Description

Select this check box to activate the Alert NotificationDelivery Limit settings. If you do not select this checkbox, Maximum Number of Messages, Delivery Time Span,and Reset Message Count After Time are not taken intoaccount when notifications are send.

Activate Delivery Limit

Enter the maximum number of notifications that youwant to receive within the specified Delivery Time Span.

Maximum Number ofMessages

Enter the time duration in hours, minutes, or seconds,during which notifications are sent. Once the messagecount reaches Maximum Number of Messages, theNotification Manager blocks the delivery of any newnotifications to the associated recipient for the timeperiod that is specified for Reset Message Count AfterTime.

Delivery Time Span

Enter the time period in hours, minutes, or seconds,during which notifications are blocked if the messagecount has reached Maximum Number of Messages. Oncethis time period is over, Maximum Number of Messagesis reset and the Notification Manager starts sendingnotifications for the specified Delivery Time Span.

Note: For example, if Maximum Number of Messages =10, Delivery Time Span = 30 Minutes, and Reset MessageCount After Time = 2 Hours, Alert Manager sendsmessages until message count reaches 10 in 30 Minutes.Once it has sent 10 messages, it blocks the delivery ofnew messages for next two Hours. After two hours, AlertManager once again starts sending messages untilmessage count reaches 10.

Reset Message Count AfterTime

5 Click Save.


320

Creating SNMP trap recipientsTraps, (interrupts), are signals sent to inform the programs that an event hasoccurred. In OpsCenter, traps are the notifications that are sent to a specifiedSNMP host or group of hosts when a condition is met.

A trap recipient is a host that receives notifications in the form of SNMP trapswhen an alert condition is met. For example, a trap is sent after an alert wasgenerated as a result of failure of communication between the OpsCenter Agentand Server.

For more details, refer to the About using SNMP with OpsCenter section.

To create SNMP recipients



3 Click SNMP.

4 Click Add

5 In the SNMP Attributes page enter the following information:


6 Enter the name of the SNMP trap recipient.Recipient Name

Enter an SNMP host, to which you want to send traps.SNMP Host

Enter the port number on the SNMP host where you wantto send traps.

SNMP Port

Select this check box if you want the recipient to receivenotifications by SNMP traps.

Active

Enter a short description about the traps.Description

Select this check box to activate the Alert NotificationDelivery Limit settings. If you do not select this check box,Maximum Number of Messages, Delivery Time Span, andReset Message Count After Time are not taken into accountwhen notifications are send. The notifications are sent assoon as alerts are generated.

Activate Delivery Limit

Enter a maximum number of notifications that can be sentwithin the specified Delivery Time Span.

Maximum Number ofMessages

Enter the time duration in hours, minutes, or seconds,during which notifications are sent. Once the message countreaches Maximum Number of Messages, Alert Managerblocks the delivery of any new notifications to the associatedrecipient for the time period that is specified for ResetMessage Count After Time.

Delivery Time Span

Enter the time period in hours, minutes, or seconds, duringwhich notifications are blocked if the message count hasreached Maximum Number of Messages. Once this timeperiod is over, Maximum Number of Messages is reset andAlert Manager starts sending notifications for the specifiedDelivery Time Span.

Reset Message CountAfter Time

7 Click Save.

Modifying Email or SNMP recipient informationOnly OpsCenter administrator can modify email / trap recipient information.


See “Creating SNMP trap recipients” on page 321.


322

To modify Email or SNMP trap recipient information


2 In the Email Recipients tab or SNMP Recipients tab, select email / traprecipient from the table, that you want to edit.

3 On the modify email / trap recipient page, change email / trap recipientattributes and Alert Notification Delivery Limit Settings.

4 Click Save.

Deleting Email or SNMP recipientOnly OpsCenter administrator can delete email or trap recipient.


To delete Email or SNMP trap recipient


2 In the Email Recipients tab or SNMP Recipients tab, select email / traprecipient from the table, that you want to delete.

3 Click Delete.

4 Click Save.

Managing cost analysis and chargeback forOpsCenterAnalytics

This feature is accessible only to Symantec OpsCenter Analytics users.

In OpsCenter Analytics, you can choose the currency that you want to be displayedon cost reports. If you have OpsCenter administrator privilege, you can set multipleglobal currencies, one of which can be set as default currency. You can set thecost variable, cost formulae, and cost estimation that you want to run the costreports.

You cannot access the Settings>Chargeback feature if you do not have SymantecOpsCenter Analytics. This feature is disabled for unlicensed OpsCenter version.

Setting a default currency for cost reportsThis section provides the procedure to set the default currency that you want tobe displayed on OpsCenter cost reports.

323Understanding OpsCenter settingsManaging cost analysis and chargeback for OpsCenter Analytics

Note:Setting the default currency gives you the flexibility of displaying cost reportvalues in the currency of your choice. However, OpsCenter does not supportconversion of currencies.

To set the default currency

1 Log on to the OpsCenter Server with administrator privileges.

2 In the OpsCenter console, click Settings > Chargeback.

You cannot access the Settings > Chargeback feature if you do not haveSymantec OpsCenter Analytics. This feature is disabled for unlicensedOpsCenter version.

3 On the Currency Settings tab, in the Default Currency drop-down list, allglobal currencies that are set by the administrator are available for selection.Select a currency from the drop-down list.

See “Editing currency list” on page 324.

4 Select the Currency Display Mode: Currency Code or Currency Symbol. Forexample, for US dollar currency, you can either select a currency code USDor symbol $, which appears on chargeback reports.

5 Select the Display Currency Option in Cost Reports check box to show thedefault currency on the cost reports.

6 Click Save.

Editing currency listThis section provides the procedure to edit the global currency list, which is madeavailable when a default currency is selected to be displayed on OpsCenter costreports.

To edit currency list



If you have not entered the Symantec OpsCenter Analytics license key, youcannot access the Settings>Chargeback feature. This feature is disabled forunlicensed OpsCenter version.

3 On the Currency Settings tab, click Edit Currency List.

Understanding OpsCenter settingsManaging cost analysis and chargeback for OpsCenter Analytics

324

4 On the Edit Currency List pop-up screen, select currencies from the GlobalCurrency list, which you want to make available for selection in the DefaultCurrency drop-down list on the Currency Settings tab.

See “Setting a default currency for cost reports” on page 323.

5 Click Add to add the selected currencies to the User Currency list.

You can use Add, Remove, Add All, and Remove All options to alter the UserCurrency list.

6 Click OK.

Managing Cost VariablesYou can create cost variables based on various parameters to determine cost ofvarious services.

See “Creating cost variables” on page 325.

See “Modifying cost variables” on page 327.

See “Deleting cost variables” on page 327.

Creating cost variablesCost reports in OpsCenter Analytics are based on the user-defined variables thatdefine the cost of various services.

Typically, each service is represented by one variable that reflects the cost of theservice, for example $1.00 per backup job. However, you can account for ratechanges in one of two ways: by creating two variables for the same service (whichyou can include in a single cost formula later) or by incorporating both rates intoa single variable. For example, a single variable can incorporate the rate of $1.00per backup job until 31 December 2004 and the rate of $1.25 per backup job startingon 1 January 2005.

Note: To generate deduplication savings reports, you must create a cost variablewith the Protected Job Size (GB) metric.

To set up OpsCenter to run cost reports, you need to create the variables thatdefine the cost of various services.

To create a cost variable



Click Cost Variable.


3 On the Cost Variable tab, click Add.

4 Enter the variable name.

5 Select any of the following variable metrics from the drop-down list:

■ Daily Occupancy

■ Job Count

■ Job Size

■ Protected Job Size

6 If necessary, select additional parameters to refine the metric you selected.For Job Count, Job Size, and Protected Job Size select the following:

The following fields are not applicable for the Daily Occupancy variablemetric.

Measure costs for a specific type of job, for example Backup orRestore. The default option is All.

Job Type

Measure costs for the jobs that use a specific policy type. InNetBackup, the policy type determines the type of clients thatcan be part of the policy and, in some cases, the types of backupsthat can be performed on the clients. Examples include DB2,Sybase, and MS-Exchange-Server. The default policy type isAll.

Job Policy Type

Measure cost for a specific transport type for example, LAN(Local Area Network) or SAN (Storage Area Network). Thedefault option is All.

Job Transport Type

Measure cost for a specific storage type for example, tape ordisk. OpsCenter supports NetBackup's disk-based dataprotection feature, which enables you to select disk as a storagetype, when a cost variable is created. The default option is All.

Job Storage Type

7 Add one or more date ranges and associated rates using the drop-down listsfor Month, Day, Year, and Time and by typing a cost per service unit (suchas backup jobs or backed-up GB) in the Rate field.

Add at least one date range.


326

8 Optionally, to add more date ranges, click Add New Range.

This can be useful for defining multiple date ranges to represent historicalor future changes in service costs. You can also modify the variable later toadd or delete date ranges as costs change.

9 Click OK .

You can now use the variable you created to build the formulas that form thebasis for cost reports.

See “Creating cost formulae” on page 328.

Modifying cost variablesYou can update cost variables and formulas without having to recreate the reportsthat rely on them. For example, you can modify the name, date ranges and ratesof a variable to reflect changing conditions in your enterprise.

To modify a cost variable



Click Cost Variables.

3 Select the check box in front of the variable name that you want to modify.

4 Click Edit.

5 Modify the cost variable details.

6 Click OK.

Deleting cost variablesYou can variables you no longer need. Deleting a cost variable removes itpermanently from the database, and you must update any formulas that use thevariable. To restore a deleted variable, you must recreate the variable manually.

To delete a cost variable



3 Click Cost Variables.

4 Select the check box in front of the cost variable that you want to delete.

5 ClickDelete.


Managing cost formulaeBased on cost variables you can create the cost formulas that you can use togenerate cost reports.


See “Modifying cost formulae” on page 328.

See “Deleting a cost formulae” on page 329.

Creating cost formulaeAfter you create cost variables, create the formula that define the cost of variousservices to run cost reports.

To create a cost formula



Click Cost Formulae.

3 On the Cost Formulae tab, click Add.

4 Enter the name of the formula.

5 Select a cost variable from the drop-down list.

You need to select at least one cost variable.

6 Optionally, to define formulae containing more than one variable, click Addnew cost variable. Select a different variable from the nes drop-down list.

You can also modify the formulae later to add or delete variables.

7 Click OK.

You now can use the formula to create cost reports with which you canevaluate the cost of services and make decisions about what to charge forperforming those services.

Modifying cost formulaeYou can modify the name and variables of a cost formula that you have created.

You can update chargeback formulas without having to recreate the reports thatrely on them. For example, you might want to update a formula that is calledRecoveryRate to reflect a change in the hourly rate that is charged for recoveryoperations.


328

To modify a cost formulae




3 On the Cost Formulae tab, select the cost formulae that you want to modify.

4 Click Edit.

5 Modify the details of the cost formula.

6 Click OK.

Deleting a cost formulaeYou can also delete formulae that you no longer need. Deleting a cost formularemoves it permanently from the database.

To delete cost formulae




3 On the Cost Formulae tab, select the cost formulae that you want to delete.

4 Click Delete.

5 On the confirmation dialog box, click OK.

Managing cost estimationThe Formula Modeling Tool offers an easy way to estimate baseline rates for theIT services you provide. Using historical data, it provides you with an estimate ofhow much it costs your organization to provide a specific kind of service.

For example, suppose you anticipate spending $500,000 over the next year toprovide backup services throughout your enterprise. By inserting the metric DailyOccupancy into the tool, along with the amount $500000, you can obtain anestimate per kilobyte that is based on the backup activity you performed last year.

See “Creating cost variables” on page 325.



To estimate baseline (chargeback) costs using the Formula Modeling Tool



Click Cost Estimation.

3 Select a Report Grouping parameter to define the model’s scope.

4 Use the following Metric Selection parameters to specify the metric whoserate you want to estimate:

Select a metric, or category of service.

Example: Daily Occupancy

Metric

Specify the total amount of money, in dollars, you expect tocharge for service within that category in a given time frame.

Examples: $50000, $10000, or $10000.00

Amount

5 Use the following Time Frame parameters to define the time intervals forwhich data is modeled:


330

Defines the beginning and end of the time interval the estimatemust cover. You can choose either absolute dates, meaningthat the estimate’s contents remains static whenever youdisplay it, or relative dates, meaning that the estimate alwaysreflects data that is collected over the most recent time interval.

Select one of the following:

■ Click Absolute to configure an absolute time frame. Thenselect a start time (month, day, year, and time of day) usingthe From drop-down lists, and a stop time using the Todrop-down lists. The estimate reflects data from the timeperiod between the start and the end dates.

Example: From MAR 1 2004 12:00 A.M. to APR 30 200412:00 A.M.

■ Click Relative to configure a relative time frame. Thenselect a time interval using the Last drop-down lists. Theestimate reflects the data that is collected within thespecified time period, up to the current time.

Examples: Last 21 Days or Last two Quarters

The Relative setting is especially useful for the estimatesthat you plan to generate on a regular basis. Such estimatesalways reflect the data that is collected over the most recenttime interval.

Time Frame

6 Click Run Model to input different values into the model, or to run a newmodel.



332

Understanding datacollection


■ About data collection in OpsCenter

■ Managing OpsCenter Agents

■ Managing Data Collectors

■ Configuring data collection for NetBackup

■ Collecting data from Backup Exec

■ Collecting data from PureDisk

■ Collecting data from Enterprise Vault

■ Collecting data from IBM Tivoli Storage Manager

■ Collecting data from EMC Legato Networker

About data collection in OpsCenterOpsCenter provides extensive reporting on the data that is collected from backupand archiving products. An OpsCenter Agent comprises product-specific datacollectors that collect data from point products and return it to the OpsCenterServer.

Note: Only one OpsCenter Agent can be installed on a single host.

6Chapter

An OpsCenter Agent consists of the data collectors that can collect data from thefollowing backup and archiving products:

■ Symantec Backup Exec (Windows only)

Note: To collect data from Backup Exec Server host, you need to install theOpsCenter Agent on a Windows host.


■ Symantec Enterprise Vault (Windows only)

Note: To collect archive data from Enterprise Vault, you need to install theOpsCenter Agent on a Windows host.

■ IBM Tivoli Storage Manager (TSM)


See “Configuring data collection for NetBackup” on page 346.

About OpsCenter AgentsThe OpsCenter Agent collects data from various Symantec and third-party backupand archiving products. These products can reside on the OpsCenter Agent hostor on remote hosts.

For more details on OpsCenter Agent installation and deployment scenarios, referto the Installing Symantec OpsCenter chapter.

Note:When you install the OpsCenter Server, OpsCenter Integrated Agent is alsoinstalled and configured, which you can use to collect only PureDisk data. Tocollect PureDisk data, you do not need to manually install or configure OpsCenterAgent.

You cannot delete the Integrated Agent.

You can collect PureDisk data only through the OpsCenter Integrated Agent.

About OpsCenter Agent logsOpsCenter Agent logs are stored at the following location:

InstallPath\Symantec\OpsCenter\Agent\logs

Understanding data collectionAbout data collection in OpsCenter

334

Where InstallPath is the location where you have installed the OpsCenter Agent.

By default the InstallPath is: C:\Program Files

Naming convention for the OpsCenter Agent log file:

5*-146-*.log

An example of the OpsCenter Agent log file name:

58330-146-2567491850-091129-0000000000.log

About Data CollectorsThe OpsCenter data collectors, collect data from backup and archiving producthosts. Each data collector collects data from a single product host. You canconfigure multiple data collectors on a single OpsCenter Agent host.

You can create data collectors to communicate with the various products, suchas Backup Exec, Enterprise Vault, or EMC Networker. These data collectors collectthe specified data type as specified in the configuration. You can specify to collectall or some of the data types for that product. For example, Backup Exec datacollector can collect Tape Drive Usage, Media, Policy and Schedule, Job, or Image.

Note: Error logs and skipped files are collected as part of job data.

You can enable or disable a data collector.

Table 6-1 lists the data collectors that you can configure in OpsCenter.

Table 6-1 Data collector types

DescriptionData Collector type

Create this data collector to collect data from Backup Exec.

See “Collecting data from Backup Exec” on page 363.

Symantec Backup Exec DataCollector (Windows only)

Create this data collector to collect data from NetBackupPureDisk.

See “Collecting data from PureDisk” on page 364.

Note: You can collect the PureDisk data only through theOpsCenter Integrated Agent that is installed with theOpsCenter server. To collect PureDisk data, you need tocreate a data collector for the Integrated Agent.

NetBackup PureDisk DataCollector

335Understanding data collectionAbout data collection in OpsCenter

Table 6-1 Data collector types (continued)

DescriptionData Collector type

Create this data collector to collect archive data fromSymantec Enterprise Vault database


Symantec Enterprise VaultData Collector (Windowsonly)

Create this data collector to collect data from TSM.

See “Collecting data from IBM Tivoli Storage Manager”on page 378.

TSM Data Collector

Create this data collector to collect data from LegatoNetworker.

See “Collecting data from EMC Legato Networker”on page 380.

Legato Networker DataCollector

Table 6-2 lists the data types that are collected by OpsCenter 7.0.1 from variousbackup and archiving products.

Table 6-2 Data types collected

EMCLegatoNetWorker

IBMTivoliStorageManager

SymantecNetBackupPureDisk

Enterprise VaultBackupExec

NetBackupDataTypes

7.3(5.3, 5.4,5.5)

(6.2.x, 6.5.x,6.6, 6.6.0.1,6.6.0.2,6.6.0.3)

8.07.5(10.x,11.x,12.x,2010)

(6.0MP7,6.5,6.5.2A,6.5.4,6.5.5, 7.0,7.0.1)

YYYNNYYJob

YYYNNYYPolicyandSchedules

YYNNNYYTapeDrive

NNNNNNYImage

NYNNNYYErrorLogs


336

Table 6-2 Data types collected (continued)

EMCLegatoNetWorker

IBMTivoliStorageManager

SymantecNetBackupPureDisk

Enterprise VaultBackupExec

NetBackupDataTypes

NNNNNNYScheduleJobs

YYNNNYYMedia

NYNNNYYSkippedFiles

NNNNYNNTarget

NNNNYNNArchive

NNNYYNNVault

NNNYYNNVaultStore

About backup and archiving products supported by SymantecOpsCenter 7.0.1

This section lists the backup and archiving products that OpsCenter 7.0.1 supports.Note that with the licensed version of OpsCenter, you can do advanced reportingfrom the data that is collected from all of these products. With the unlicensedversion, you cannot collect data from third-party products like IBMTivoliStorage



337Understanding data collectionAbout data collection in OpsCenter

Table 6-3 Backup and archiving products supported by Symantec OpsCenter7.0.1


All supported NetBackup platforms(except 7.0 and greater versions) byremote agent

Note:NBU 7.0 and greater versionsdo not require any Agent.

Native agent for Windows 2003 (SP2& R2), Windows 2008 (SP2 & R2),and Solaris 9, 10

6.0 MP7 and higherversions, 6.5 and higherversions, 7.0, 7.0.1

Symantec NetBackup

PureDisk supported platform(PDOS) by the OpsCenter integratedAgent. You do not need a separateAgent to collect data from PureDisk.You can use the inbuilt Agent of theOpsCenter Server for datacollection. To create or configurethe data collector, select the Agentthat is installed as Integrated Agent.

6.2, 6.2.2, 6.5, 6.5.1, 6.6,6.6.0.1, 6.6.0.2, 6.6.0.3

Symantec NetBackupPureDisk


Native agent on backup servers onWindows 2003 (SP2 & R2), 2008(SP2 & R2)

10d, 11d, 12.0, 12.5, 2010

Note:OpsCenter does notsupport Symantec BackupExec running on NetWare.


All supported Symantec EnterpriseVault platforms by remote agent

Native agent on Microsoft SQLServer 2005 or 2008 (whereEnterprise Vault database resides)on Windows 2003 (SP2 & R2), 2008(SP2 & R2).


Native agent on backup servers onWindows 2003 (SP2 & R2), 2008(SP2 & R2) and Solaris 9/10




338







Note: Ensure that the time on the OpsCenter Server and the backup or archiveproduct host is in sync based on the time zone they are deployed in. A backup orarchive product host means a supported product host that is connected toOpsCenter. Examples of a backup or archive product host (product host) arePureDisk host, Backup Exec host, NetBackup master server, Enterprise Vault hostetc.

If the OpsCenter server and the product host are in the same time zone (like CST),both OpsCenter server and the product host must show the same time. For example,if the OpsCenter server and the product host are in CST time zone, but showdifferent time like 8 pm and 10 pm, then OpsCenter may not display accurate datain the reports and also Monitor and Manage tabs of the OpsCenter console.

If the OpsCenter server and product host are in different time zones like CST andPST, then ensure that both the CST and the PST time convert to the same GMTtime. For example if the OpsCenter server and the managed host show 8 pm CSTand 9 pm PST respectively, then 8 pm (CST) and 9 pm (PST) must translate to thesame GMT time.

Managing OpsCenter AgentsThis section provides procedures to view, modify, create, and delete an OpsCenterAgent configuration.

See “About the OpsCenter Agent” on page 30.

Viewing Agent statusUse this section to view general details and status of an OpsCenter Agent thatyou have configured in OpsCenter.

339Understanding data collectionManaging OpsCenter Agents

To view Agent status

1 In the OpsCenter console, click Settings > Configuration > Agent.

2 On the Agent list, select an Agent to view its status at the bottom of the page.

By default the General tab is selected that displays the following details, whichyou have specified when you created this Agent.

See “Configuring an OpsCenter Agent” on page 340.

Displays the name of the Agent hostAgent Host

Displays the port number that is used to connect to the PBX on theOpsCenter Server

PBX Port

Displays the network address of the OpsCenter ServerOpsCenterServerNetworkAddress

3 Click Agent Summary by Data Collector Status, Agent Summary by Data TypeStatus, or Agent Summary by Data Collector Count tab to view the relevantdetails.

Configuring an OpsCenter AgentThis section provides the procedure to configure an OpsCenter Agent.

Understanding data collectionManaging OpsCenter Agents

340

To configure an OpsCenter Agent


2 Click Create Agent.

Enter the host name where you want toconfigure the OpsCenter Agent

Agent Host

Select the operating system family of thehost where you want to install Agent. Forexample: Solaris Family or WindowsFamily

For Windows hosts, you can configure anAgent for all supported backup andarchiving products. For Solaris hosts, youcan only configure an Agent for IBM TivoliStorage Manager and EMC LegatoNetworker.

Agent Operating System Family

Enter the port number that the OpsCenterAgent requires to connect to the PBX onthe OpsCenter Server

PBX Port

Select the network address from thedrop-down list, using which you want toconnect to the OpsCenter Server

OpsCenter Server Network Address

3 Click Save.

Modifying an AgentThis section provides the procedure to modify an OpsCenter Agent information.

To modify an OpsCenter Agent


2 From the list of agents, select the check box in front of the Agent that youwant to modify.

3 Click Edit Agent.

4 On the Edit Agent page, modify PBX port or OpsCenter Server NetworkAddress.

5 Click Save.

341Understanding data collectionManaging OpsCenter Agents

Deleting AgentsThis section provides the procedure to delete an OpsCenter Agent.

To delete an OpsCenter Agent


2 From the list of agents, select the check box in front of the Agent that youwant to delete.

3 Click Delete.

Managing Data CollectorsThis section provides procedures to view, configure, modify, and delete a datacollector.

Viewing Data Collector statusUse this section to view general details and status of a Data Collector that youhave configured for an Agent.

To view data collector status


2 On the Agent list, expand an Agent to view the Data Collectors that areconfigured for this Agent.

Understanding data collectionManaging Data Collectors

342

3 Select a Data Collector to view its details and status at the bottom of the page.

By default the General tab is selected displaying the following Data Collectordetails, which you have specified when you created this Data Collector.

See “ Configuring a Data Collector” on page 343.

Displays the name of the product type, for which this Data Collector isconfigured

For example: Symantec Backup Exec

Product

Displays the name of the target host, which this Data Collector collectsdata from

ProductHost

Displays the status of the Data Collector as Enabled or Disabled thatyou have set

If the Data Collector status is disabled, the data is not collected fromthe target host.

Status

4 Select the Data Collection Status tab.

The following details are displayed:

List of the data types that this data collector collects from the producthost

Data Type

The time when the full data was successfully collected from the producthost

LastSuccessfulData Load

The time when this schedule was last run to collect data.Last RunTime

The collection status of the data collector for each data type, such asComplete, Failed, or Not Started

CollectionStatus

The message that appeared at the time of the last exceptionLastExceptionMessage

Configuring a Data CollectorOpsCenter is designed to provide extensive reporting on the data that is receivedfrom backup and archiving products. OpsCenter consists of Server, Agent, JavaView Builder, and a console. The OpsCenter Agent contains product-specific data

343Understanding data collectionManaging Data Collectors

collectors collecting data from the products and returning it to the OpsCenterServer. You can generate various business reports on this backup / archiving data.

After you install and configure an OpsCenter Agent, configure the data collectors.

See “Configuring an OpsCenter Agent” on page 340.

To configure a data collector


2 On the Agent list, select a check box in front of the Agent, for which you wantto configure a Data Collector.

3 Click Create Data Collector.

4 On the Create Data Collector: Product Selection page, enter the followinginformation:

Select the name of the product from which you want to collectdata. For example, Symantec Backup Exec.

The options available in the Select Product drop-down listdepends on the Agent operating system family that you haveselected while creating the respective Agent.

Select Product

Enter the name of the product host from which you want tocollect backup or archiving data.

Target host name

5 Click Next.

On the Create Data Collector: Details page, the Target Details, ConfigurationSettings, and Data Collection details are displayed.

6 Verify or modify the default Target Details:

Displays the name of the product from which this datacollector collects data. You need to specify the product namewhen you create the data collector. For example: SymantecBackup Exec

Product

Displays the name of the product host from which this datacollector collects data. You need to specify the product namewhen you create the data collector.

Target host name

By default, the data collector status is Enabled. You candisable the data collection by changing the status.

Data Collector Status

Understanding data collectionManaging Data Collectors

344

7 Enter the data collector configuration settings. These settings vary dependingon the data collector type you configure. For product specific configurationsettings, refer to the respective data collector settings.

See “Collecting data from Backup Exec” on page 363.


See “Collecting data from IBM Tivoli Storage Manager” on page 378.

See “Collecting data from EMC Legato Networker” on page 380.

8 Enter the following data collector settings:

Select the start time of a blackout period. The data is notcollected during the time that is specified in Blackout PeriodStart Time and Blackout Period End Time.

Blackout Period StartTime

Select the end time of a blackout period. The data is notcollected during the time that is specified in Blackout PeriodStart Time and Blackout Period End Time.

Blackout Period EndTime

Select this check box to collect the associated data type.Configuration Status

Lists the data types that can be collected from a product host.The data types vary depending on the product that you arecollect data from.

See “About Data Collectors” on page 335.

Collectible Data Type

Enter the collection interval in minutes, hours, and days.Collection interval is the time interval that you want to setbetween the two consecutive data collections.

For example: You have set the Collection Interval to 15Minutes. The first data collection starts at say 9:00 A.M. tillall archive records are collected and ends at 11:00 A.M. Thenext data collection starts at 11:15 A.M. after 15-minutesinterval .

Collection Interval(sec)

States whether last data load was successful or not.

See “Viewing Agent status” on page 339.

Last Successful DataLoad

9 Click Save.

Modifying a Data Collector configurationThis section provides procedure to modify configuration of a Data Collector.

345Understanding data collectionManaging Data Collectors

To modify a Data Collector configuration

1 Log on to the OpsCenter console.

2 In the OpsCenter console, click Settings > Configuration > Agent..

3 On the Agent list, expand an Agent to view Data Collectors that are configuredfor this Agent.

4 Select a check box in front of the Data Collector that you want to modify.

5 Click Edit Data Collector.

6 On the Edit Data Collector: Details page, modify the Target Details.

7 Modify data collection configuration settings. These settings vary dependingon the product, which this data collector collects data from.

8 Modify blackout period settings.

9 Modify collection interval.

10 Click Save.

Deleting Data CollectorsThis section provides procedure for deleting Data Collector configurations froman Agent.

To delete a Data Collector configuration

1 Log on to the OpsCenter Server.


3 On the Agent list, expand an Agent to view Data Collectors that are configuredfor this Agent.

4 Select check boxes in front of the Data Collectors that you want to delete.

5 Click Delete Data Collector.

Configuring data collection for NetBackupThis section describes how OpsCenter collects data from NetBackup. It alsodescribes how you can add, edit, delete, and control data collection for a masterserver.

The following sections describe the NetBackup data collection in detail:

■ About the NetBackup data collection view

■ How OpsCenter collects data from NetBackup

Understanding data collectionConfiguring data collection for NetBackup

346

■ About NetBackup versions that OpsCenter 7.0.1 can monitor and manage

■ Viewing master server details and data collection status

■ Adding a master server

■ Editing a master server

■ Deleting a master server

■ Controlling data collection for a master server

About the NetBackup data collection viewThis view is displayed when you select Settings > Configuration > NetBackupfrom the OpsCenter console. This view shows details of master servers.

The table that appears in this view shows the following columns:

Name or IP address of the master server thatis configured.

Network Name

The display name that you have chosen forthe master server.

Display Name

Operating system of the master server.Operating system

Backup product and version from where thedata is collected.

Product

The last time that OpsCenter successfullyinitiated contact with the particular masterserver. The Last Contact column does notnecessarily represent the last time thatOpsCenter collected information from themaster server.

Last Contact

The master server can show any of thefollowing states:

■ Connected

■ Partially Connected

■ Not Connected

■ Disabled

See “About the master server state”on page 353.

State

347Understanding data collectionConfiguring data collection for NetBackup

How OpsCenter collects data from NetBackupOpsCenter is used to monitor, manage, and report on NetBackup master and mediaservers, clients, and policies. To perform the monitoring, management, andreporting functions, OpsCenter collects data from the NetBackup master servers.The NetBackup data collection and management logic that OpsCenter uses is builtinto NetBackup master servers. This logic is included in the NetBackup ServiceLayer (NBSL). Starting with the 6.0 release of NetBackup, NetBackup Service Layer(NBSL) components are included as a part of NetBackup on master and mediaservers.

Note:OpsCenter only uses the NBSL on master servers for data collection. ThoughNBSL is also included on media servers, OpsCenter does not use it. You must addonly master servers to the OpsCenter console. You must not add any media serversto the OpsCenter console.

NBSL provides a single point of access to key NetBackup data, objects, and changeevents. The NetBackup UI also uses NBSL. NBSL runs as a service or daemon andhas local configuration information, but no local database.

OpsCenter uses NBSL for all NetBackup monitoring, managing, and controlfunctions. If NBSL service stops running on a managed NetBackup server,OpsCenter gets affected.

If NBSL stops, OpsCenter may not capture any changes that were made to theNetBackup configuration. When NBSL restarts, OpsCenter correctly recapturesthe latest state.

See “About the data collection status of a master server” on page 350.

Note: A NetBackup 7.0 or 7.0.1 master server does not require any OpsCenterAgent or data collector for data collection. However for a master server whoseversion is less than 7.0, an Agent must be installed only if you want to collectspecific data (image, error log, and scheduled jobs data).

In earlier master server versions, the VBR agents collected the data for image,error log, and scheduled jobs. For NetBackup 7.0 and 7.0.1 master servers, thisdata is collected automatically by the OpsCenter Server. OpsCenter Agents do notneed to be installed on the NetBackup 7.0 or 7.0.1 master servers.

The OpsCenter server software collects data from NBSL in the following ways:

■ Initial data load

■ Listening for change notifications


348

Whenever OpsCenter server software starts, when data collection for a masterserver is enabled or when a master server is added to OpsCenter, the OpsCenterserver starts collecting all the available data from NetBackup master server intothe OpsCenter database using NBSL. The initial data load happens serially foreach data type. As soon as the initial data load is complete, OpsCenter serversoftware listens to the notifications from NBSL for any change in NetBackup data,and updates the OpsCenter database.

Note:Consider a scenario when you add a master server or when OpsCenter Serversoftware starts after a long time, or when the data collection for a master serveris enabled after a long time. In this case, it may take some time for the OpsCenterserver to collect all data (such as media, jobs, images, drives etc.) from theNetBackup master server and insert it into the OpsCenter database.

Consider a scenario where a master server is already added on the OpsCenterconsole, and you uninstall and then reinstall NetBackup on the master server. Inthis case, the State of the master server shows as NotConnected in the OpsCenterconsole (State column in Settings > Configuration > NetBackup) and OpsCenterdoes not collect any new data from the specific master server. To begin datacollection from the master server, you must delete the master server from theOpsCenter console and then add the master server again. Once you add the masterserver in the OpsCenter console, the OpsCenter server can start collecting datafrom the master server.


Symantec Private Branch Exchange (PBX) is used for communication and requiresa port to be opened on the OpsCenter server and the NetBackup master server forinput and output. The default PBX port that is used is 1556. If you change the PBXport on the NetBackup master server, you can configure the same in OpsCenterwhile adding or editing a master server.

About NetBackup versions that OpsCenter 7.0.1 can monitor andmanage

OpsCenter 7.0.1 can monitor and manage all NetBackup versions between 6.0MP7 and 7.0.1.

The NetBackup master servers that OpsCenter manages are referred to as managedNetBackup servers. Each managed NetBackup master server that OpsCentermanages must have NBSL present and in operation. Starting with the 6.0 releaseof NetBackup, NetBackup Service Layer (NBSL) components are included as a partof NetBackup on master servers.


These managed NetBackup servers harvest pertinent NetBackup data and storeit in the OpsCenter database.

See “About the OpsCenter database” on page 29.

OpsCenter can also be used to monitor a NetBackup cluster.

SeeNetBackupHighAvailabilityAdministrator'sGuide for more details on settingup a NetBackup cluster environment. Also review the OpsCenter sections of theNetBackup release notes before using OpsCenter for monitoring NetBackupclusters.

Viewing master server details and data collection statusUse the following procedure to view the details for a master server. The detailsfor the master server are shown at the bottom of the Settings > Configuration >NetBackup view under the following tabs:

This tab displays the contents of many ofthe columns that are displayed in the table.

General

This tab displays the collection status foreach of the data types. The Data CollectionStatus tab is shown by default when youselect Settings > Configuration > NetBackup.

It also lists details like the time when thedata load was last successful, when datacollection last happened, and the exceptionmessage if the data collection failed for anyof the data types.

See “About the data collection status of amaster server” on page 350.

Data Collection Status

To view the details and the data collection status for a master server

1 In the OpsCenter console, select Settings > Configurations > NetBackup.

2 Click the name of the master server (link) from the Network Name column.

The details for the master server are shown at the bottom of this view.

About the data collection status of a master serverThis section describes the NetBackup data types that OpsCenter collects and thedifferent states for managed servers.

Figure 6-1 shows a sample data collection status view for a master server.


350

Figure 6-1 Sample Data Collection Status view

Table 6-4 gives a description of the contents in the Data Collection Status tab.

Table 6-4 Data Collection Status view

DescriptionColumn

The type of data that is collected from NetBackup.

See “About NetBackup data types and collection status”on page 351.

Data Type

This column lists the date and time when the last successful dataload happened for the specific data type.

Last Successful DataLoad

This column lists the date and time when data collection wasattempted.

Last Run Time

This column provides the status of each data load activity thatOpsCenter requests.

Collection Status

This column lists the last exception message if data collectionfailed for a data type.

Last ExceptionMessage

About NetBackup data types and collection status

OpsCenter collects data for many NetBackup data types (such as jobs, policy, mediaserver, service, storage unit etc.) by using NBSL.

For most operations and changes in NetBackup, NBSL sends notifications toOpsCenter. For changes such as job, policy, services, and devices, the notificationalso contains the changed data. This data is stored in the OpsCenter database.


The following are the collection status for the different data types and theirdescription:

This status may come when the masterserver version does not support the specificdata type. For example, NetBackup 6.0 doesnot support disk, FT data types.

This status also comes when your masterserver version is lower than 7.0 and you havenot configured data collection for thefollowing data types:

■ Error Logs

■ Scheduled jobs

■ Image

You can enable data collection for these datatypes while adding or editing a master serverunder Advanced Data Collection Propertiessection.

See “Adding a master server in theOpsCenter console” on page 358.

See “Editing a master server” on page 362.

Not Applicable

The data collection for the specific data typehas not started. This may happen when youinitially add a master server or when youstart the OpsCenter server.

Not Started

The data collection for the specific data typeis queued.

Queued

The data collection for the specific data typeis in progress.

Running

The data collection for the specific data typeis complete.

Completed


352

The data collection for the specific data typehas failed. When the data collection fails,you can see the exception message from theLast Exception Message column.

Note:Data collection can fail, and then startafter some time. This is normal behavior. Ifdata collection for a particular data typefails, it should be automatically started againwithin 10 minutes. All the functionalityother than the functionality of the failed datatype can be used normally while collectionfor a data type fails.

Failed

This status is seen when the specific datatype like FT is not licensed in NetBackup.

Not Licensed

About the master server state

This section lists the different states that can exist for a master server and whatthey mean.

The master server can have any of the following states:

The master server is Connected when thedata collection status for all data types is notFailed. This means that the collection statusfor all the data types must be any otherstatus except Failed.

Connected

The master server is Partially Connectedwhen data collection for some data typesfails while data collection has happened oris happening for other data types. Forexample, data collection for catalog data typeis Completed but data collection for client,device, disk etc. fails.

Master servers may show as PartiallyConnected temporarily for some time. Thisis because data collection can fail, and thenstart after some time. This is normalbehavior. If data collection for a particulardata type fails, it should be automaticallystarted again within 10 minutes. All thefunctionality other than the functionality ofthe failed data type can be used normallywhile collection for a data type fails.

Partially Connected


The master server is Not Connected whenthe data collection for all data types fails.This may be when there is a network issuebecause of which OpsCenter is not able toconnect and collect data from NetBackup.

Note:Data collection can fail, and then startafter some time. This is normal behavior. Ifdata collection for a particular data typefails, it should be automatically started againwithin 10 minutes. All the functionalityother than the functionality of the failed datatype can be used normally while collectionfor a data type fails.

Not Connected

The master server is Disabled when the datacollection for the selected master server isdisabled.

Disabled

Adding a master serverTo allow OpsCenter to communicate with a managed NetBackup server and collectdata requires some security configuration. OpsCenter can monitor the masterservers which have NetBackup Access Control (NBAC) configured and also thoseservers that do not have NBAC configured.

Note: Symantec recommends that any NetBackup master server be monitored byonly one OpsCenter server.

Use the following steps to add a master server. Note that you must first configurethe master server to allow server access and data collection by OpsCenter. Afterconfiguring the master server, you must add this server to the OpsCenter consoleso that it can be monitored.

To add a master server

1 Configure your managed master server to allow server access and datacollection by OpsCenter.

See “Configuring a master server for server access and data collection byOpsCenter” on page 356.

2 After configuring the master server, you mustadd the master server to the OpsCenter console so that it can be monitored.



354

Note: You can use an alternate procedure to add a NetBackup 7.0 or later masterserver to OpsCenter. This procedure can be used for both NBAC and non-NBACservers.

See “Adding a NetBackup 7.0 or later master server” on page 355.

Adding a NetBackup 7.0 or later master serverUse the following procedure to add a NetBackup 7.0 or 7.0.1 master server to theOpsCenter console. This procedure can be used for both NBAC and non-NBACservers.

In case of a clustered NetBackup setup, use this procedure for each node of thecluster.

To add a NetBackup 7.0 or later server to the OpsCenter console on Windows andUNIX

1 Log on to the managed master server as Administrator or root for Windowsand UNIX respectively.

2 Browse to the following location:

%Program Files%/NetBackup/bin/admincmdWindows

/usr/openv/netbackup/bin/admincmdUNIX

3 Run the following command on the master server:

nbregopsc -add <Name of the OpsCenter Server>

As a part of usability enhancements, a command that is called nbregopschasbeen added to NetBackup 7.0 and later versions. In addition, a new entry thatis called OPS_CENTER_SERVER_NAME has been added to the bp.conf file. Thenbregopsc command registers OpsCenter with the current master server andadds this master server to OpsCenter. This command also establishes a trustrelationship from the authentication broker of NetBackup master server tothe authentication broker of OpsCenter server.


4 Ignore this step for master servers for which NBAC is not configured.

However if the master server is NBAC-enabled, a trust relationship must beestablished from the authentication broker of the OpsCenter server to theauthentication broker (AB) of the NetBackup master server. OpsCenter cannotmonitor NetBackup servers if the trust relationship has not been set upbetween OpsCenter and NetBackup server.

To establish the trust relationship, log on as Administrator or root on theOpsCenter server host and navigate to the following location:

%Program

Files%\Veritas\Security\Authentication\bin

Windows

/opt/VRTSat/binUNIX

On the OpsCenter server host, run the following command:

vssat setuptrust --broker <MasterServerhost:2821> --securitylevel

high

Note that <MasterServerhost> is the name of the master server.

5 Restart all the NetBackup services (processes).

Once you perform this procedure, the master server is automatically addedto the OpsCenter console.

Note: In case running the nbregopsc command fails, you must manually addthe master server to the OpsCenter console.


Configuring a master server for server access and datacollection by OpsCenterUse the following procedures to configure a master server for data collection byOpsCenter on Windows and UNIX. This procedure applies to both NBAC andnon-NBAC master servers.

In case of a clustered NetBackup setup, use this procedure on each node of thecluster.


356

Note:This procedure applies to all master server versions including 7.0. However,it is recommended that the following procedure be used for NetBackup 7.0 andlater servers.


To configure a master server on Windows and UNIX

1 Log on to the managed master server as Administrator or root on Windowsand UNIX respectively.

2 Start the NetBackup Administration Console.

3 Expand NetBackup Management > Host Properties > Master Servers.

4 Double-click the master server name to view its properties. The MasterServerProperties dialog box appears.

5 From the Master Server Properties dialog box, select the Servers tab todisplay the server list.

6 To add the OpsCenter server to the server list, click Add. The Add a NewServer Entry dialog box appears.

7 Type the OpsCenter server name in the field and click Add to add the serverto the list.

Ensure that the OpsCenter server name that you add is reachable from theNetBackup server.

8 Click Close.

9 In the Master Server Properties dialog box, click OK.


10 Ignore this step for master servers on which NBAC is not configured.

However if the master server is NBAC-enabled, a bi-directional trustrelationship must be established between the authentication broker of theOpsCenter server and the authentication broker(AB) of each managedNetBackup server. OpsCenter cannot monitor NetBackup servers if the trustrelationship has not been set up between OpsCenter and NetBackup server(NBAC enabled).

To set up these trust relationships, use the vssat command in SymantecProduct Authentication Service. Run this command from %Program

Files%\Veritas\Security\Authentication\bin directory in Windows or/opt/VRTSat/bin in UNIX.

On the NetBackup master server host, run the following command:

vssat setuptrust --broker <OpsCenterABhost:2821> --securitylevel

high

where <OpsCenterABhost> is same as the host where OpsCenter server isinstalled. However if OpsCenter is installed in a clustered mode, then<OpscenterAB> is the host name that is provided as the remote authenticationbroker host during the OpsCenter installation.

Similarly, log on as Administrator or root on the OpsCenter server host andrun the following command:

vssat setuptrust --broker <MasterServerhost:2821> --securitylevel

high

where <MasterServerhost> is the name of the master server.

11 Restart all the NetBackup services.

12 Add this master server to the OpsCenter console so that it can be monitored.


Adding a master server in the OpsCenter consoleYou must add a master server to the OpsCenter console so that it can be monitored.Use the following procedure to add a master server.

To add a master server

1 In the OpsCenter console, select Settings > Configurations > NetBackup .

2 Click Add.


358

3 Enter the followingdetailsforthemasterserverunderGeneralPropertiesandAdvancedPropertiessections:

Enter a host name or an IP address. Thisfield is required.

In case the master server is clustered,enter the virtual name of the masterserver.

Network Name

Enter an alternate name for the server.The display name is used for the masterserver on all views of the OpsCenterconsole.

Note that this field is required.

Display Name

The NetBackup PBX port allows all socketcommunication to take place whileconnecting through a single port. Thedefault NetBackup PBX port is 1556.

Note that this field is required.

NetBackup PBX port

The OpsCenter server may have multiplenetwork interface cards (NIC). You canselect a preferred network address fromthe drop-down list. OpsCenter uses theaddress that you select to connect to themaster server.

OpsCenter's Preferred network address

The Advanced Data Collection Properties section is applicable if yourNetBackup master server version is lower than 7.0. In earlier master serverversions, the VBR agents collected the data for image, error log, and scheduledjobs. For NetBackup 7.0 and later master servers, this data is collectedautomatically by NBSL and OpsCenter Agents do not need to be installed onthe master servers.

The data for image, error log, and scheduled jobs is used in OpsCenter reports.

Enter the following details under Advanced Data Collection Propertiessection:


Select an agent from the drop-down list.In case, no agent is configured, clickConfigure Agent.

You can create an OpsCenter Agent fromSettings>Configuration>Agent>CreateAgent.

See “Configuring an OpsCenter Agent”on page 340.

Agent

The directory path on the OpsCenterAgent host where the NetBackupapplication is installed. In case of remotedata collection, this is the path on theOpsCenter Agent host where RAC (RemoteAdmin Console) is installed.

Example of install directory path on aWindows machine: C:\ProgramFiles\VERITAS\NetBackup

Example of install directory path on aSolaris machine:/usr/openv/netbackup

Install Directory

The directory path on the OpsCenterAgent host where the Volume Manager isinstalled.

Example of Volume Manager directory ona Windows machine: C:\ProgramFiles\VERITAS\Volmgr

Example of Volume Manager directory ona Solaris machine:/usr/openv/volmgr

Volume Manager Directory

Click the checkbox if you want to enableimage data collection from the masterserver.

Enable Image Data Collection

Click the checkbox if you want to enableerror log data collection from the masterserver.

Enable Error Log data Collection


360

Click the checkbox if you want to enablescheduled job data collection from themaster server.

Note that you must enter the value inUsername and Password fields so thatscheduled job data can be collected.

Enable Scheduled Job Data Collection

Enter the user name to access theNetBackup master server. A user name isrequired if you enable scheduled job datacollection.

Ignore this field in the followingscenarios:

■ If you have set the Scheduled Jobsoption to Disable

■ If you want to collect the scheduledjobs data from a local NetBackup host.

If you want to collect the scheduled jobsdata remotely, using the nbpemreq CLI,set the Future Scheduled Jobs option toEnable, and specify valid NetBackupadmin credentials.

Note: The Username field is disabled ifEnable Scheduled Job Data checkbox isunchecked.

Note: Username and Password is notneeded if the agent is installed on NBUmaster server.

Username

Enter the password of the NetBackup useraccount. This is required if you enablescheduled job data collection.

Note: The Password field is disabled ifEnable Scheduled Job Data checkbox isunchecked.

Password

4 Click Locate to check if OpsCenter can connect to the master server. An errorappears if OpsCenter cannot connect to the NetBackup master server on thenetwork.

5 Click Save to add the master server.

Alternately, you can click Cancel to exit.


Editing a master serverUse the following procedure to change the configuration information for aNetBackup master server

To edit a master server


2 Use the checkbox to select a master server from the NetworkName column.

3 Click Edit.

4 Edit the information that is displayed on the Edit Master Server page. Youcan change the data that is shown for General Properties, AdvancedProperties, and Advanced Data Collection Properties sections.

A description of the fields present in these sections is available.


Note that you cannot edit the Network Name for the master server. TheNetwork Name field falls under the General Properties section.

5 Click Save.

Deleting a master serverYou can delete one or more master servers using the following procedure. Notethat deleting a master server deletes all the data that is associated with the masterserver.

Note: Deleting a master server may take some time.

To delete a master server


2 Use the checkbox to select one or more master servers from the NetworkName column.

3 Click Delete.

4 The following warning message appears:

Deletion of the selected master server(s)

will delete all related data. Do you want to proceed?

Click OK.


362

Controlling data collection for a master serverYou can disable or enable OpsCenter data collection for a particular managedNetBackup master server depending on your needs.

Note: If you disable data collection it may appear to be a loss of data in OpsCenter.For example, a drive may have the same status until you enable OpsCenter datacollection again.

To disable data collection for a master server



3 Click Disable Data Collection.

To enable data collection for a master server



3 Click Enable Data Collection.

Collecting data from Backup ExecThis section describes data collection from Backup Exec.

Caution: The Backup Exec data collector requires the following component to beinstalled on the OpsCenter Agent host, to collect data properly.

Microsoft Visual C++ 2005 SP1 Redistributable Package (x86) that isvcredist_x86.exe

VC Redistributable Package is available at:

http://www.microsoft.com/downloads/details.aspx?

familyid=200B2FD9-AE1A-4A14-984D-389C36F85647&displaylang=en

Once you install this component on the Agent host, configure the Backup Execdata collector as described in the following section.

363Understanding data collectionCollecting data from Backup Exec

To configure Backup Exec data collector

1 Click Settings > Configuration > Agent .

2 On the Agent list, select a check box in front of the Agent, for which you wantto configure a Data Collector.


4 On the Create Data Collector: Product Selection page, select Symantec BackupExec from the Select Product drop-down list.

5 In the Target Host Name text box, enter the Backup Exec Server host name,from which you want to collect data.

6 Click Next.

7 On the Create Data Collector: Details page, specify the following Backup Execdata collector configuration settings:

Enter the name of the user account that is required toconnect to the Backup Exec Database .

User name

Enter the password of this user account.Password

Select the version of the Symantec Backup Exec server- 10.x, 11.x, or 12.x - from which you want to collectdata.

Version

8 Select blackout period details, data types to be collected, and collectioninterval.

For more details on collection interval, and other data collector settings, referto the following section:


9 Click Save.

Collecting data from PureDiskOpsCenter supports collection of data from Symantec NetBackup PureDisk. Thecollected data is stored in the OpsCenter database, based on which you can generatereports. OpsCenter can collect Policy & Schedule and Job data types from PureDiskStorage Pool Authority (PureDisk SPA).

For more details on PureDisk, refer to the Symantec NetBackup PureDiskdocumentation.

Understanding data collectionCollecting data from PureDisk

364

PureDisk SPA and its components that run on the PureDisk operating system(PDOS). The Single Instance Storage (SIS) or deduplication technology ofNetBackup PureDisk is unique in storage and backup industry. PureDisk identifiesfiles and the data segments that contain identical data and treats them as a singleinstance of a file, which it backs up only once. This lets you save storage space.Attributes of identical files, such as name and date of modification can vary.

While backing up a file, PureDisk determines whether multiple instances of thefile are present on hosts across the network, including remote hosts. By using thededuplication technology, PureDisk stores only one instance of the file.

Table 6-5 describes the steps that you need to carry out to collect data fromPureDisk.

Table 6-5 Steps to collect data from PureDisk


Refer to the “InstallingSymantec OpsCenteron Windows andUNIX” section.

Install OpsCenter server.

Note: When you install OpsCenterserver,OpsCenter Integrated Agent is alsoinstalled and configured, which you can use tocollect only PureDisk data. To collect PureDiskdata, you do not need to manually install orconfigure OpsCenter Agent.

You cannot delete the Integrated Agent.

Note: You can collect PureDisk data only throughthe OpsCenter Integrated Agent.

1

See “Setting up a trustbetween the PureDiskSPA host andOpsCenter AB host”on page 365.

You need to establish trust between theauthentication brokers of OpsCenter and PureDiskSPA for secure communication.

This is a pre-requisite for PureDisk data collectionfrom OpsCenter.

2

See “ConfiguringPureDisk datacollector” on page 366.

Using the OpsCenter console, configure PureDiskdata collector for the Integrated Agent.

3

Setting up a trust between the PureDisk SPA host and OpsCenter ABhost

You need to set up a bi-directional trust between the PureDisk SPA host andOpsCenter AB (authentication broker ) host. This is a pre-requisite for PureDiskdata collection from OpsCenter.

365Understanding data collectionCollecting data from PureDisk

Note: OpsCenter AB host is the host where the OpsCenter server is installed.However, if OpsCenter is installed in a clustered mode, then the OpsCenter ABhost is the host name that was provided as the remote authentication broker hostduring the OpsCenter installation.

The OpsCenter AB hostname is stored in the vxss.hostname parameter in thefollowing file:

On Windows: C:\ProgramFiles\Symantec\OpsCenter\server\config\security.conf

On UNIX: /opt/SYMCOpsCenterServer/config/security.conf

This section provides the manual steps that you need to carry out on the PureDiskSPA host, to setup trust between the PureDisk SPA host and the OpsCenterauthentication broker host.

To set up a trust between PureDisk SPA host and OpsCenter AB host

1 On the PureDisk SPA host, logon as root and run the following command:

su www-data

2 As a “www-data” user, run the following command:

/opt/VRTSat/bin/vssat setuptrust --broker OpsCenterABhost:2821

--securitylevel low

After successfully setting up a trust between the PureDisk SPA host andOpsCenter AB host, the following message is displayed:

setuptrust

----------------------

----------------------

Setup Trust With Broker: OpsCenterABhost

Note: Setting up a trust between the OpsCenter AB host and PureDisk SPA hostfrom the OpsCenter AB host is accomplished automatically after the PureDiskdata collector is configured.

Configuring PureDisk data collectorThis section provides the procedure to configure NetBackup PureDisk data collectoron the OpsCenter UI.

Understanding data collectionCollecting data from PureDisk

366

To configure NetBackup PureDisk data collector

1 Click Settings > Configuration > Agent .

2 On the Agent list, select a check box in front of the Integrated Agent.

When you install OpsCenter server,OpsCenter Integrated Agent is alsoinstalled and configured, which you can use to collect only PureDisk data. Tocollect PureDisk data, you do not need to manually install or configureOpsCenter Agent.

You can collect PureDisk data only through the OpsCenter Integrated Agent.


4 On the Create Data Collector: Product Selection page, select SymantecNetBackup PureDisk from the Select Product drop-down list.

5 In the TargetHostName text box, enter the PureDisk SPA Server host name,from which you want to collect data.

6 Click Next.

7 On the Create Data Collector: Details page, specify the following PureDiskconfiguration settings:

Select any of the following Symantec NetBackupPureDisk versions from the drop-down list: 6.2, 6.2.1,6.2.2, 6.5, 6.5.0.1, 6.5.1, 6.6

Product Version



8 Click Save.

Setting up a trust between the OpsCenter authentication broker host andPureDisk SPA host is accomplished automatically after PureDisk data collectoris configured. If it is not successful, you need to do it manually.

Refer to the "Setting up a trust between the OpsCenter AB host and PureDiskSPA host" in the OpsCenter Administrator's Guide.

Collecting data from Enterprise VaultThis section provides information about Enterprise Vault Data Collectorconfiguration.

367Understanding data collectionCollecting data from Enterprise Vault

About Enterprise VaultSymantec Enterprise Vault software application provides a flexible frameworkfor archiving emails, file systems, and collaborative environments. It is supportedonly on Windows platform.

Enterprise Vault has the following features:

■ Policy-controlled archiving

■ Seamless retrieval of information

■ Powerful search capability

■ Compliance retention

■ Data compression and single instancing

For more details, refer to Enterprise Vault documentation.

About data collected from Enterprise VaultOpsCenter categorizes the data that is collected from Enterprise Vault databaseinto various data types.

Table 6-6 lists the data types in OpsCenter that represent type of data that iscollected from Enterprise Vault.

For example, OpsCenter collects Policy and Retention Category data fromEnterprise Vault database and stores it as Archive Policy data type.

Table 6-6 Enterprise Vault data types

Data in Enterprise VaultData type in OpsCenter

Policy and Retention CategoryArchive Policy

Vault Store and Vault Store PartitionVault Store

Mailbox, Public Folder, and Provisioning GroupTarget

SaveSetArchive

You can select these data types while configuring the Enterprise Vault datacollector. The data collector collects the information from Enterprise Vault thatis associated with the selected data types, , as per the specified schedule.

See “Configuring Enterprise Vault data collector” on page 377.

Figure 6-2 shows the hierarchy of archive data in Enterprise Vault.

Understanding data collectionCollecting data from Enterprise Vault

368

Figure 6-2 Representation of Enterprise Vault data in OpsCenter reports

ExchangeServer

ArchiveSite

EnterpriseVault Server

VaultStore

VaultPartition

ProvisioningGroup

----------------- Archives ----------------- -------------- Archive Storage -------------

An archive site is a logical group of hosts that need to be archived (ExchangeServers, Provisioning Groups), storage media (vault stores, vault partitions), andEnterprise Vault Servers. It is at the highest level in the Enterprise Vault datahierarchy. Using OpsCenter archive reports you can determine the details aboutboth archiving activities and archival storage, depending on which path you followto drill down the site information.

See “About OpsCenter reports” on page 535.

OpsCenter reports present archive data in the following two ways:


A few archive reports show details about archiving activities. Forexample: Details of mailboxes to be archived, original size of datathat has been archived, the number of mailboxes that exceed theirwarning limits per Exchange Server or Provisioning Group, andso on.

These are all archiving activities, which you can view reports for.These archiving activity reports are available in the ‘Exchange’report folder of Archive reports. OpsCenter archive reports showonly Exchange Server data.

Note:Mailboxes are referred to as targets and an individual emailis referred to as an item.

Archiving activities

A few archive reports show details about the storage of archiveddata. For example: details of vault stores and vault partitionswhere the archive data has been stored, or how many emails werearchived per Enterprise Vault Server, and so on.

Storage of archiveddata

About versions supported by OpsCenterOpsCenter supports the following versions of Enterprise Vault. It supports allversions of Microsoft SQL Server that the Enterprise Vault supports.

7.5, 8.0Enterprise Vault

2005, 2008Microsoft SQL Server

Planning the Enterprise Vault data collector deploymentEnterprise Vault stores the archive metadata in the directory and the storagedatabase residing in Microsoft SQL Server. To collect the archive metadata fromMicrosoft SQL Server, you need to configure OpsCenter Agent and data collectorusing the OpsCenter console.

OpsCenter supports local as well as remote archive-data collection. However,Symantec recommends the remote data collection method, in which OpsCenterAgent and MS SQL Server are installed on different hosts.

Table 6-7 lists the steps that you need to carry out before configuring theEnterprise Vault data collector for archive-data collection in the OpsCenter console.


370

Table 6-7 Planning and deployment steps


See “About single-domaindeployment mode”on page 372.

See “About multi-domaindeployment mode”on page 372.

See “About standalonedeployment mode”on page 372.

Deploy OpsCenter Agent in any of the followingways, to collect archive data remotely:

■ Single-domain mode

■ Multi-domain mode

■ Standalone mode

Note: Symantec recommends that to collectEnterprise Vault data, you deploy theOpsCenter Agent in single-domain mode.

1

See “Accessing MS SQLServer host” on page 373.

Make sure that the user whose credentials youuse for the integrated logon has required accessrights on the MS SQL Server, where the archivedata resides.

This can be an existing user, or you can createa new user in MS SQL Server and give requiredaccess rights.

2

See “ About creating auser in single-domaindeployment mode”on page 374.

See “ About creating auser in multi-domaindeployment mode”on page 374.

See “About creating auser in standalonedeployment mode”on page 374.

Depending on the deployment mode of theOpsCenter Agent, add a user in the appropriatedomain or workgroup, which you want to usefor integrated logon between Agent host andMS SQL Server host.

3

See “Installing MS SQLServer JDBC driver”on page 376.

Install MS SQL Server JDBC driver on theOpsCenter Agent host.

4

See “Configuring theOpsCenter Agentproperties for integratedlogon” on page 375.

For integrated logon, configure the OpsCenterAgent to run in the context of the user or groupthat has access to MS SQL Server, where theEnterprise Vault data resides, depending onthe OpsCenter Agent deployment mode.

5


You need to configure the Enterprise Vault data collector using the OpsCenterconsole and schedule data collection.

See “Configuring Enterprise Vault data collector” on page 377.

About OpsCenter Agent deployment modesThis section describes various deployment modes in which you can deployOpsCenter Agent, depending on your setup. This section mainly talks about theremote agent deployment modes. However, Enterprise Vault also supports localAgent deployment. You can deploy the OpsCenter Agent on MS SQL Server hostor OpsCenter Server host.

About single-domain deployment modeSymantec recommends that you deploy the OpsCenter Agent in single-domainmode to collect Enterprise Vault data. In this deployment mode, the OpsCenterAgent host and the MS SQL Server host (Enterprise Vault database instance) sharethe same Windows domain.

About multi-domain deployment modeIn addition to single-domain mode, you can deploy the OpsCenter Agent inmulti-domain mode. In this deployment mode, the OpsCenter Agent host and theMS SQL Server host (Enterprise Vault database instance) do not share the sameWindows domain. The OpsCenter Agent host is in a domain different than theSQL Server domain.

Note: To collect Enterprise Vault data, Symantec does not recommend themulti-domain or standalone deployment of the OpsCenter Agent.

About standalone deployment modeIn this deployment mode, the OpsCenter Agent host and the MS SQL Server host(Enterprise Vault database instance) do not share the same Windows domain. TheOpsCenter Agent host is installed on a standalone host.

Note: To collect Enterprise Vault data, Symantec does not recommend themulti-domain or standalone deployment of the OpsCenter Agent.


372

Accessing MS SQL Server hostThis section describes how to give the required rights to a user to access MS SQLServer.

To give rights to a user to access MS SQL Server

1 Create a Windows domain user on the MS SQL Server host. For example,create a user with credentials ‘localadmin’ and ‘pass’.

2 Open the MS SQL Server admin console, using SQL Server Management StudioExpress or any other MS SQL Server client. Add this Windows domain user(local admin) to the MS SQL Server.

3 Add this user (local admin) to the Enterprise Vault databases, on which youwant the access rights.

Note: To report on Enterprise Vault / archive data, OpsCenter Agent needsaccess to the Enterprise Vault directory and storage databases. You need toadd the user to these databases and give the required access rights on thesedatabases.

4 In the MS SQL Server admin console, in the Object Explorer, expand theSecurity folder.

5 Expand the logons folder.

6 Right-click the user name - for example ‘OpsDomain\localadmin’ with thepassword ‘pass’ - with which you want to perform integrated logon on theAgent host and MS SQL Server host.

7 Click Properties.

8 On the logon Properties screen, in the Selectapage pane, select ServerRoles.

9 In the Server roles pane at the right-hand side, select the ‘public’ check box.

The user local admin in the OpsDomain (OpsDomain\localadmin) now hasthe rights to access MS SQL Server.

10 Additionally, make sure that the user has ‘datareader’ rights to access thedesired database.

About creating a user for integrated logonThis section provides procedures to create a user that is required for integratedlogon between the OpsCenter Agent host and MS SQL Server host, where thearchive data resides.


Depending on the OpsCenter Agent deployment mode, the procedure to create alogon user varies.

About creating a user in single-domain deployment modeMake sure that the user whose credentials (for example, User name: 'localadmin'and Password: 'pass') you use for the integrated logon has required access rightson the MS SQL Server, where the archive data resides.

The user 'localadmin' can be an existing user, or you can create a new user withthese credentials in MS SQL Server and give required access rights.

See “Accessing MS SQL Server host” on page 373.

If you have deployed the OpsCenter Agent in the single-domain mode, create auser, (User name: 'localadmin' and Password: 'pass') in the Agent host domainthat is the Windows domain.

See “About single-domain deployment mode” on page 372.

Use credentials of this user (User name: 'localadmin' and Password: 'pass') whenyou configure the Agent properties for integrated logon.

See “Configuring the OpsCenter Agent properties for integrated logon” on page 375.

About creating a user in multi-domain deployment modeMake sure that the user whose credentials (for example, User name: 'localadmin'and Password: 'pass') you use for the integrated logon has required access rightson the MS SQL Server, where the archive data resides.



If you have deployed the OpsCenter Agent in the multi-domain mode, create auser (User name: 'localadmin' and Password: 'pass') in the Agent host domain.

See “About multi-domain deployment mode” on page 372.



About creating a user in standalone deployment modeMake sure that the user whose credentials (for example, User name: 'localadmin'and Password: 'pass') you use for the integrated logon has required access rightson the MS SQL Server, where the archive data resides.


374



If you have deployed the OpsCenter Agent in the standalone mode, create a userfor example (User name: 'localadmin' and Password: 'pass') in the appropriateworkgroup.

See “About standalone deployment mode” on page 372.



Configuring the OpsCenter Agent properties for integrated logonThe Enterprise Vault data collector that is configured in OpsCenter collects theEnterprise Vault archive data residing on the MS SQL Server. However, the datacollection is not possible if the OpsCenter Agent is not configured to run in thecontext of the user or the group that has access to the SQL Server.

Note: Make sure that this user has required rights to access MS SQL Server


To configure OpsCenter Agent properties

1 On the OpsCenter Agent host (Windows system), click Start > Run.

2 In the Run dialog box, in the Open text box, enter services.msc.

3 Click Enter.

The Windows Services screen is displayed.

4 On the Services screen, on the services list, right-click the Symantec OpsCenterAgent service.

5 On the right-click menu, click Properties.

6 On the Symantec OpsCenter Agent Properties screen, on the Log On tab,select the “This account” option.

7 Enter the credentials of the user - for example 'localadmin' with the password'pass' - who has the rights to access the MS SQL Server, where the EnterpriseVault archive data resides.

Alternatively, click Browse. This opens the Select User dialog box.


8 Enter a user name in the text box. This user should have access rights on MSSQL Server. Click Check Names to check whether the user name that isspecified is present in the Windows domain or not.

9 Click OK.

10 Click OK on the LogOn tab.

Installing MS SQL Server JDBC driverTo collect the Enterprise Vault data residing on Microsoft SQL Server (or MS SQLServer or SQL Server), you require the SQL Server JDBC driver that is installedon the OpsCenter Agent host. The Agent requires the JDBC driver to communicatewith the MS SQL Server.

Microsoft provides a Java Database Connectivity (JDBC) driver for use with SQLServer. The SQL Server JDBC Driver 2.0 is available to all SQL Server users at noadditional charge, and provides access to SQL Server 2000, SQL Server 2005, andSQL Server 2008 from any Java application, application server, or Java-enabledapplet. This is a Type 4 JDBC driver that provides database connectivity throughthe standard JDBC application program interfaces (APIs) available in Java Platform,Enterprise Edition 5.

To install MS SQL Server JDBC driver

1 Click the following link:

Download Microsoft SQL Server JDBC Driver 2.0

2 On the Microsoft SQL Server JDBC Driver 2.0 page, click Download.

3 The File Download dialog box is displayed.

Click Open to access the end-user license agreement.

4 On the MICROSOFT SOFTWARE LICENSE TERMS page, select the following:

I Accept the above agreement and I want to download the MicrosoftWindows version

The File Download dialog box is displayed.

5 Click Save to save the sqljdbc_2.0.1803.100_enu.exe file to a desiredlocation.

6 Unzip the sqljdbc_2.0.1803.100_enu.exe file.


376

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=99b21b65-e98f-4a61-b811-19912601fdc9

7 Copy sqljdbc_2.0\enu\auth\x86\sqljdbc_auth.dll andsqljdbc_2.0\enu\sqljdbc4.jar files to the following location on the Agenthost.

Install Dir\Symantec\OpsCenter\Agent\lib

where Install Dir is the location where you have installed OpsCenter.

Click the following link for more information and frequently asked questionson the JDBC driver.

Microsoft SQL Server JDBC Driver

8 Restart the Agent service.

Configuring Enterprise Vault data collectorThis section provides the procedure to configure the Enterprise Vault data collectorin the OpsCenter console. This data collector collects archive data from MS SQLServer where the Enterprise Vault database resides.

To collect archive data, the Enterprise Vault data collector needs the Agent to beconfigured to run in the context of the user or the group that can access MS SQLServer.


To configure Enterprise Vault data collector

1 In the OpsCenter console, click Settings > Configuration > Agent .

2 On the Agent list, select a check box in front of the Agent for which you wantto configure the Data Collector.


4 On the Create Data Collector: Product Selection page, select SymantecEnterprise Vault from the Select Product drop-down list.

5 Enter the name of the host, from where you want to collect the archive data.

6 Click Next.

7 Enter the following Configuration Settings:

This is the database instance name. By default this field isleft blank.

Database InstanceName

Enter the port number that is used to connect to the MS SQLServer.

The default port number is 1433.

Database port number


http://msdn.microsoft.com/en-us/data/aa937724.aspx

8 Specify blackout period details.

9 Select the data types that you want to collect. You can collect the followingdata types from an Enterprise Vault set up: Target, Vault Store, Archive Policy,and Archive

10 Select collection interval.



11 Click Save.

Enterprise Vault data collection checklistEnsure the following before you start collecting data from Enterprise Vaultdatabase:

■ The SQL Server JDBC driver has been installed on the OpsCenter Agent hostSee “Installing MS SQL Server JDBC driver” on page 376.

■ The OpsCenter Agent has been configured to run in the context of the user oruser group that has access to MS SQL Server database where Enterprise Vaultdata is stored.See “Configuring the OpsCenter Agent properties for integrated logon”on page 375.

■ The OpsCenter Agent service is running.

■ The SQL Server services are running.

■ You have entered the appropriate information for Enterprise Vault datacollector variables.See “Configuring Enterprise Vault data collector” on page 377.

■ You have selected the data types / events to be collected from the EnterpriseVault database, that is the MS SQL Server.

■ You have specified the collection interval within which you want to collect thearchive data.

Collecting data from IBM Tivoli Storage ManagerOpsCenter supports the collection of the following data types from IBM TivoliStorage Manager (TSM):

The variables to configure for the IBM Tivoli Storage Manager data collector areas follows:

Understanding data collectionCollecting data from IBM Tivoli Storage Manager

378

The home directory for the Tivoli Storage Managerinstallation. (This variable can be left blank.)

Home Directory

An administrator-level logon that is used to connect to theTivoli Storage Manager server. (The default is admin.)

TSM ID

The password for the account (specified in tsmId) forconnecting to the TSM server. (The default password isadmin.)

TSM Password

(Windows only) The TCP port on the TSM server throughwhich the data collector establishes a connection.

The TSM Server Port has no effect on Solaris. The Solarisdata collector uses only product host settings.

TSM Server Port

The path to the dsm.opt file.dsmConfig

The path where files to be run dsmadmc reside.dsmDir

The path of TSM administrative client (dsmadmc).dsmadmc Location

Note: The TSM product environment variables DSM_CONFIG and DSM_SYS point tothe dsmadmc required files dsm.opt and dsm.sys (Solaris and AIX). For moreinformation, refer to your TSM documentation.

Specify the TSM server host (also called product host) value for the TSM datacollector in the following manner:

Use the fully qualified host name. In short, product host isthe value that you can use with the dsmadmc-tcpserveraddress option. For example, the followingentries are valid for product host:

Host.sample.domain.com

Host

assuming that Host can be fully qualified.

Windows

379Understanding data collectionCollecting data from IBM Tivoli Storage Manager

The product host must be the value that is specified in thedsm.sys file, for tag SErvername (note the case). In short,product host is the value that you can use with thedsmadmc-se option. The following is a sample dsm.sys file:

*****************************************

SErvername server_a COMMmethod

CoMMmethod TCPip

TCPPort 1500

TCPServeraddress 255.255.255.255

SERVERNAME MYHOST.Veritas.COM

TCPSERVERADDRESS 255.255.255.255

NODENAME myhost.mycompany.com

******************************************

Solaris and AIX

For more details on collection interval, and other data collector settings, refer tothe following section:


Collecting data from EMC Legato NetworkerThe variables to configure for the EMC Legato Networker data collector are asfollows:

The home directory for the EMC Legato Networkerinstallation.

Home Directory

The directory path for the log file containing group-completemessages. This path may be absolute or relative tohomeDirectory. The default file name is messages.

To increase the efficiency of the Networker data collector,configure Networker to create a log that contains only groupcomplete messages, and point messagesFile to this log

Location of messages file

The directory path of the mminfo command-line interface(CLI), absolute, or relative to homeDirectory

Location of mminfo.exe

The directory path of the nsradmin CLI, absolute, or relativeto homeDirectory

Location of nsradmin.exe

Understanding data collectionCollecting data from EMC Legato Networker

380

The Networker resource file to use instead of the defaultfile that is used by nsradmin (Optional)

Location of nsrres file

Output of an nsradmin command (Optional)

The OpsCenter console displays nsrResFile, nsrFile,and mminfoFile even though these variables are optionaland only advanced users must set them.

Location of nsr file

Output of mminfo(Optional)Location of mminfo file

For more details on collection interval, and other data collector settings, refer tothe following section:


381Understanding data collectionCollecting data from EMC Legato Networker

Understanding data collectionCollecting data from EMC Legato Networker

382

Managing OpsCenter views


■ About OpsCenter views

■ Managing views

■ Managing nodes and objects

About OpsCenter viewsSymantec OpsCenter views are logical groups of IT assets (master servers orclients) organized in a hierarchical manner. You can create views in Java ViewBuilder and make them available in the OpsCenter console.

Figure 7-1 shows the details that are displayed on the Views tab in the OpsCenterconsole.

7Chapter

Figure 7-1 The Views tab

Note: If you do not have the admin privileges you can still copy a view object froma read-only view to your view. However, you cannot modify its attributes becauseyou do not have the write permissions for that view.

Note: To manage views, an OpsCenter Analyst and Reporter need to have therequired rights assigned to them through Java View Builder. If they do not havethese rights, they cannot manage - create, edit, or delete - views using theOpsCenter GUI.

An OpsCenter Analyst has the Read permissions on all views.

An OpsCenter Reporter has the Read permissions on the views only if it has therequired permissions.


In a OpsCenter view, IT assets that are scattered across organization can bearranged according to their locations, business units, or applications. You cangenerate various OpsCenter reports that are filtered by views. With these reports,you can identify the locations or departments with hosts storing business criticaldata.

Managing OpsCenter viewsAbout OpsCenter views

384

After you install and run the OpsCenter Server and the OpsCenter Agent,OpsCenter detects theIT assets, which are then stored in the database. The JavaView Builder makes these IT assets available when a view is created.

The hierarchy of an object view based on archive data is as follows:

Abstract objects (Geography > Region > City) > Domain (Site) > Host (ExchangeServer / Enterprise Vault Server) > Target (Mailbox / Journal Mailbox / PublicFolder)


Note: To run the Java View Builder, you need Java Runtime Environment (JRE)installed on the host.

In a view hierarchy, between top and bottom levels you can create a number ofuser-defined levels. An OpsCenter view is a homogeneous one, it cannot havehosts and file systems in the same tree.

About view typesIn OpsCenter, each view is associated with a view type. Depending on the type ofthe view, objects are made available for assigning to that view.

Note:All Veritas Backup Reporter (VBR) views are migrated to OpsCenter as Clientviews. As Media reports run only on 'Master Server view', after upgrade from VBR,you need to once again create the Master Server views to run the Media reportswith views.

You can create views of the following types:

If you create a view of type Client, onlybackup clients are available to be assignedto the view.

Client

If you create a view of type Master Server,only Master Servers are available to beassigned to the view.

Master server

If you create a view of type Policy, onlypolicies are available to be assigned to theview.

Policy

385Managing OpsCenter viewsAbout OpsCenter views

If you create a view of type Enterprise Vaultserver, only EV servers are available to beassigned to the view.

Enterprise Vault server

If you create a view of type Exchange server,only Exchange servers are available to beassigned to the view.

Exchange server

If you create a view of type Vault, only vaultsare available to be assigned to the view.

Vault

If you create a view of type File System, onlyfile systems are available to be assigned tothe view.

File System

About accessing OpsCenter viewsWhile creating an OpsCenter view, you can specify the access rights for that view.A view can either be public or private.

See “Creating views” on page 388.

All OpsCenter users can access public views.Public view

Only view owner and OpsCenter admin can access private views.Private view

About view levelsA newly created view has only one level. You can add multiple nodes to a view atdifferent levels. You can add alias for each of these view levels.

See “Modifying view level alias” on page 390.

Master server hosts, clients, or policies are always at the lowest levels in a view.Between the top level and the bottom level, you can create multiple intermediatelevels to organize view objects into logical groups, to create a hierarchical structurein the view.

About nodes and objectsAn OpsCenter view comprises nodes and view objects. A node is a logical entitythat you add to create a hierarchical structure of a view. Between the first level(the view name itself) and the last level (actual view object), you can add multiplenodes.

Figure 7-2 shows an example of a view comprising multiple nodes and objects.

Managing OpsCenter viewsAbout OpsCenter views

386

Figure 7-2 View nodes and objects

Managing viewsThis section provides procedures to add, edit, or delete OpsCenter views.

Viewing OpsCenter views and their detailsThis section provides the procedure to view OpsCenter views.


To view OpsCenter views

1 In the OpsCenter console, click Settings>Views. A list of views that you havealready created is displayed.

See “Modifying views” on page 389.

See “Creating views” on page 388.

2 To check the details of a view, select the view from the views list. The detailsare displayed in the lower section of the page.

387Managing OpsCenter viewsManaging views

This tab shows the details of view levelaliases of the selected view. Default viewlevel aliases are as follows: Level 1, Level2, and so on.

The Alias View Levels tab does not containany data, if you have not added any nodesor objects to the selected view.

You can modify the view level aliases.

See “Modifying view level alias”on page 390.

Alias View Levels tab

The General tab displays the followingdetails:

■ Name of the selected view

■ Description of the view

■ Date and time when the view wascreated

■ Name of the user who has created thisview

General tab

Creating viewsThis section provides the procedure to create a view using OpsCenter.

To create a view

1 In the OpsCenter console, click Settings > Views.

2 Click Add.

Managing OpsCenter viewsManaging views

388

3 On the Add View dialog box, specify the following view details:

Enter the view nameName

Select the view type: Client, Master Server, Policy,Enterprise Vault Server, or Exchange Server

See “About view types” on page 385.

View type

Enter description about the view.

For example: This is a geographical view that comprisesof master servers located in Asia Pacific, Europe, andNorth America.

Description

Select the check box if you want to make the view public.

All users can access public views.

See “About accessing OpsCenter views” on page 386.

If you do not select this check box, the view becomesprivate. Users other than you and OpsCenter admin cannotaccess this view.

Make the View Public

4 Click OK.

Modifying viewsThis section provides the procedure to modify view details.

To modify views


2 From the list of views, select a view that you want to modify.

3 Click Edit.

389Managing OpsCenter viewsManaging views

4 On the Edit View dialog box, you can modify the following view details:

Modify the view nameName

Modify the view description.Description

Select the check box if you want to makethe view public.

All users can access public views.

See “About accessing OpsCenter views”on page 386.

Make the View Public

5 Click OK.

Deleting viewsThis section provides the procedure to delete views.

Note: Once you have deleted a view, it cannot be recovered. If you delete a view,all its nodes are deleted and the objects are moved to the unassigned tree.

To delete views


2 From the list of views, select a view that you want to delete.

3 Click Delete.

Modifying view level aliasThis section provides the procedure to modify alias of view levels.

See “Adding nodes to a view” on page 391.

To modify alias view levels


2 From the list of views, select a view for which you want to modify view levelalias.

3 Click Edit Alias View Levels.

Managing OpsCenter viewsManaging views

390

4 On the Alias View Levels dialog box, text boxes for entering aliases for allavailable view levels appear. For example, if the selected view has only onelevel, the Alias View Levels dialog box appears as follows:

5 Rename the available levels. For example, if the selected view has three levels,you can rename the levels as follows: rename Alias Level 1 as Geography,Alias Level 2 as Country, and Alias Level 3 as Region.

6 Click OK.

Managing nodes and objectsThis section provides procedures to create, modify, and delete nodes and objectsof a view.

Adding nodes to a viewThis section provides the procedure to add a node to a view.

See “About nodes and objects” on page 386.

To add nodes to a view


2 From the list of views, select a view to which you want to add nodes andobjects.

3 Click Manage Nodes and Objects.

4 On the view tree, select the view to which you want to add a node.

5 Click Add.

6 On the Add dialog box, enter the node name.

7 Click OK.

391Managing OpsCenter viewsManaging nodes and objects

Modifying node detailsThis section provides the procedure to modify the information of a view node.


To modify node information


2 From the list of views, select a view to modify the information of associatednodes.


4 On the view tree, expand the view to see the associated nodes.

5 Select the node that you want to modify.

6 Click Edit.

7 On the Edit dialog box, modify the name of the node.

8 Click OK.

Deleting nodesThis section provides the procedure to delete the nodes from a view.


To delete a node


2 From the list of views, select a view from which you want to delete nodes.


4 On the view tree, expand the view to see the associated nodes.

5 Select the node that you want to delete.

6 Click Delete.


Adding objects to a view nodeThis section provides the procedure to add objects to a view or a node within aview.

Managing OpsCenter viewsManaging nodes and objects

392

To add an object to a view node


2 From the list of views, select the view to which you want to add objects.


4 On the view tree, select the view name or a view node to which you want toadd an object.

5 In the right-hand-side pane, select the Unassigned Objects tab. The availableobjects list varies depending on the view type.

For example: If the view is of type Client, only client hosts are available onthe Unassigned Objects tab for selection.

The Unassigned Objects tab contains all objects that have not yet beenassigned to the selected view or view node.

You can filter the unassigned objects with the help of default filters or youcan create new filters and apply them to view the required objects on the tab.

See “Working with view filters” on page 394.

6 Select the check boxes in front of the view objects that you want to add to theselected view or view node.

7 Click Add to Node.

The added view objects are removed from the Unassigned Objects tab andappear on the Objects on Node tab.

Deleting objects from a view nodeThis section provides the procedure to delete the objects from a view or a viewnode.

To delete an object from a view node


2 From the list of views, select the view from which you want to delete objects.


4 On the view tree, select the view name or a view node from which you wantto delete an object.

The objects that are assigned to this view or the view node are displayed onthe Objects on Node tab.

5 Select the check boxes in front of the view objects that you want to delete.


6 Click Delete from Node.


Working with view filtersOpsCenter provides a set of default filters using which you can filter the viewobjects that you need to add to a view. You can also create your own filters andapply them to view the required list of view objects.

The default set of filters vary depending on the view type.

Table 7-1 lists the default filters available for various view types.

Table 7-1 Default filters

Default filtersView type

All Clients, Windows Clients, Solaris Clients, Linux Clients, OtherClients

Client

All Servers, Connected Servers, Partially Connected Servers, NotConnected Servers, Windows Servers, Solaris Servers, LinuxServers, Other Servers

Master Server

All Policies, Active Policies, Inactive Policies, Windows Policies,Catalog Policies, Standard Policies, Other Policies

Policy

Creating a view object filterThis section provides the procedure to create user-defined view object filters.

See “Working with view filters” on page 394.

To create a view object filter


2 From the list of views, select the view to which you want to assign objects.


4 On the view tree, select the view name or the view node to which you wantto assign view objects.

5 In the right-hand-side pane, select the Unassigned Objects tab. The list ofobjects that is displayed varies depending on the view type.


6 Click the Create Filter icon.


394

7 On the dialog box, specify the following filter details:

Enter the filter name.Name

The filter definition comprises thefollowing components:

■ Column - Select a column of filed namethat you want to filter on.

■ Operator - Select an operator to forma filter criteria.

■ Value - Enter the value for the selectedcolumn, with which you want to filterthe available view objects.

■ And - Select And or Or as appropriate.This lets you specify multiple filtercriteria.

Use the links appearing in the Link asfollows:

■ Click Add to add a new row forspecifying new filter criteria.

■ Click Remove to remove the respectiverow from the filter criteria.

Definition

The following figure shows an example of creating a filter.

8 Click OK.

This user-defiled filter is now added in the Filter drop-down list on theUnassigned Objects tab, which you can modify or delete.

See “Modifying view object filters” on page 396.

See “Deleting view object filters” on page 396.


Modifying view object filtersYou can modify definition of user-defined view object filters. You cannot modifythe default filters.

See “Creating a view object filter” on page 394.

To modify view object filters




4 On the view tree, select the view name or a view node to which you want toassign view objects.



6 From the Filter drop-down list, select the user-defined filter that you wantto modify.

7 Select the Edit Filter icon.

If you have selected a default filter, the Edit Filter icon is disabled.

8 On the dialog box, modify name or definition of the filter.

9 Click OK.

Deleting view object filtersYou can delete user-defined view object filters. You cannot delete the defaultfilters.

See “Creating a view object filter” on page 394.

To delete view object filters




4 On the view tree, select the view name or a view node to which you want toassign view objects.


396


6 From the Filter drop-down list, select the user-defined filter that you wantto delete.

If you have selected a default filter, the Delete Filter icon is disabled.



398

Monitoring NetBackupusing Symantec OpsCenter


■ About the Monitor views

■ Controlling the scope of Monitor views

■ Monitoring NetBackup using the Overview subtab

■ Monitoring NetBackup jobs

■ Monitoring NetBackup services

■ Monitoring NetBackup policies

■ Monitoring NetBackup media

■ Monitoring NetBackup devices

■ Monitoring NetBackup hosts

■ Monitoring NetBackup alerts

About the Monitor viewsFrom the Monitor tab and associated subtabs, you can view detailed informationabout your NetBackup environment including jobs, services, policies, media,devices, hosts, and alerts.

8Chapter

Controlling the scope of Monitor viewsThe content that is shown in the Monitor views is based on your current Viewpane selection.

You can select the following default option from the View pane:

Select ALL MASTER SERVERS to viewinformation for all the NetBackup servers inyour environment.

ALL MASTER SERVERS

In addition to using the default view i.e. ALL MASTER SERVERS, you can alsocreate your own views from Settings > Views or by using Java View Builder. Forexample, you can create a view like Geography to view details about master serversin a particular region like Europe.

More information about how to create views by using the Settings > Views isavailable.



Use the following procedure to view details of all master servers or specific masterservers.

To view details of all master servers

◆ In the OpsCenter console, select ALLMASTERSERVERS from the drop-downlist in the View pane.

To view details of specific master servers

1 In the OpsCenter console, select ALLMASTERSERVERS from the drop-downlist in the View pane.

2 Deselect the checkbox next to ALLMASTERSERVERS and select the specificmaster servers from the list of master servers. Ensure that other masterservers are unchecked.

3 Click Apply Selection.

About timeframe selectionYou can also view data for the last 24, 48, or 72 hours for some of the Monitorviews by clicking Last 24 Hours, Last 48 Hours, or Last 72 Hours respectively.These options are located on the top-right corner of specific Monitor views. Notethat by default, data for the last 24 hours is shown in these views.

Monitoring NetBackup using Symantec OpsCenterControlling the scope of Monitor views

400

You can control timeframe selection for the following Monitor views:

■ Monitor > Overview (Job Summary by State, Job Summary by Exit Status, Top7 Policies by Failed Jobs, Top 7 Job Error Log Summary, and Alert Summaryby Severity sections)

■ Monitor > Jobs

■ Monitor > Alerts

■ Monitor > Policies (Summary View)

In addition, you can also customize the timeframe selection by clicking Customizeand specifying an absolute timeframe or relative timeframe. Using the Customizeoption, you can view data for any timeframe that you want like you can view jobsdata for the previous three weeks. The Customize option is located on the top-rightcorner of specific Monitor views.

You can customize the timeframe selection for the following Monitor views:

■ Monitor > Jobs (List View and Hierarchical View)

■ Monitor > Alerts (List View)

Monitoring NetBackup using the Overview subtabThis view is displayed when you select Monitor > Overview (default view). Thisview gives an overview of your NetBackup environment. This view contains thedifferent sections which display specific information about your NetBackupenvironment.

From this view, you can use links to drill down and access detailed informationabout many aspects of your NetBackup environment. Pie charts for mostmonitoring categories appear. The pie segments are also links to more details forthe monitoring category.

The following sections describe the Overview subtab in detail:

■ Viewing the Job Summary by State section

■ Viewing the Media Summary by Status section

■ About Top 7 Job Error Log Summary section

■ Viewing the Services Summary section

■ Viewing the Master Server Summary section

■ Viewing the Job Summary by Exit Status section

■ Viewing the Drive Summary by Status section

401Monitoring NetBackup using Symantec OpsCenterMonitoring NetBackup using the Overview subtab

■ About Top 7 Policies by Failed Jobs section

■ Viewing the Alert Summary by Severity section

Viewing the Job Summary by State sectionThe Job Summary by State section shows an overall distribution of jobs by jobstate for the current selection in the View pane and timeframe selection. Thisinformation is shown in a pie chart as well as a table. Data for the last 24 hoursis shown by default. You can also view data for the last 48 hours or 72 hours.

See “Controlling the scope of Monitor views” on page 400.

A pie chart with different colors represents the job distribution. Each color of thepie chart represents how jobs are distributed in your environment as per the jobstate in the selected timeframe. You can also view the color code summary in thissection to know the colors that represent different job states. Pointing on the piechart gives the number and percentage of jobs in a particular job state in yourNetBackup environment. For example, pointing on the yellow color in the piechart shows that in the last 24 hours, 22 jobs, or 42% jobs in your environmentare in a queued state.

You can drill down from this section to see details for failed, incomplete, queued,active jobs etc.

To view jobs by job state

1 In the OpsCenter console, select Monitor > Overview.

2 In the Job Summary by State section, do either of the following:

■ Click on the number of jobs (link) for a particular job state from the table.For example, click on the number that is shown for Done jobs.Or

■ Click a colored section of the pie chart that corresponds to a particularjob state. For example, click on the yellow section of the pie chart to viewdetails for Queued jobs.

Viewing the Media Summary by Status sectionThe Media Summary by Status section shows an overall distribution of media bymedia status for the current selection in the View pane. This information is shownin a pie chart as well as a table.

A pie chart with different colors represents media distribution in this section.Each color of the pie chart represents how media are distributed in yourenvironment as per the media status. You can also view the color code summaryin this section to know the colors that represent different media status. Pointing

Monitoring NetBackup using Symantec OpsCenterMonitoring NetBackup using the Overview subtab

402

on the pie chart gives the number and percentage of media with a particular mediastatus in your NetBackup environment. For example, pointing on the red color inthe pie chart shows that four media or 2% media in your environment are frozen.

You can drill down from this section to see details for media with different statuslike details for frozen and active media.

To view media by media status


2 In the Media Summary by Status section, do either of the following:

■ Click the number of media (link) for a particular media status from thetable. For example, click the number for Frozen media.Or

■ Click a colored section of the pie chart that corresponds to a particularmedia status. For example, click on the red section of the pie chart to viewdetails for Frozen media.

About Top 7 Job Error Log Summary sectionTheTop7JobErrorLogSummary section lists seven exit status codes responsiblefor maximum failed jobs in your environment. The content that is shown in thissection is based on the current View pane selection. Data for the last 24 hours isshown by default. You can also view data for the last 48 hours or 72 hours.


The table that appears in the section lists the top seven exit status codesresponsible for maximum job failure and also lists the number of failed jobs foreach exit status in the selected timeframe. Note that the failed jobs that are shownin the Failed Job Count column are arranged in descending order in the table. Byviewing this section, you can quickly analyze the reasons behind maximum jobfailures in your environment.

Viewing the Services Summary sectionThe Services Summary section provides a high-level view that shows the totalnumber of running and stopped NetBackup services for the current View paneselection.

The total number of running and stopped NetBackup services are shown in a table.You can drill down from the links in this table to see details for running or stoppedservices.


To view running or stopped services


2 In the Service Summary section, click the number that is shown in the ServiceCount column of the table. For example, click on the number that is shownfor Running services to view details for the services that are running.

Viewing the Master Server Summary sectionThe MasterServerSummary section provides the specific information about themaster servers based on the current View pane selection.

The following information is shown in the Master Server Summary section:

■ Total number of master servers in your environment

■ Number of the master servers that appear as Connected in the OpsCenterconsole

■ Number of the master servers that appear as Not Connected in the OpsCenterconsole

■ Clients that do not have a backup policy configured for them

You can drill down from this section to see details for all the master servers inyour environment or details for the master servers that appear as connected /not connected. You can also see details of the clients that do not have a backuppolicy configured for them.

To view all master servers


2 In the Master Server Summary section, click the number that is shown inthe Total column.

To view the master servers that are connected


2 In the Master Server Summary section, click the number that is shown inthe Connected column.

To view details of the master servers that are not connected


2 In the Master Server Summary section, click the number that is shown inthe Not Connected column.


404

To view details of the clients that are at risk


2 In the Master Server Summary section, click the number that is shown inthe Clients at Risk column.

Viewing the Job Summary by Exit Status sectionThe Job Summary by Exit Status section shows an overall distribution of jobs byexit status based on the current View pane and timeframe selection. Thisinformation is shown in a pie chart as well as a table. Data for the last 24 hoursis shown by default. You can also view data for the last 48 hours or 72 hours.


A pie chart with different colors represents the job distribution by exit status inthe selected timeframe. Each color of the pie chart represents how jobs aredistributed in your environment as per the exit status. You can also view the colorcode summary in this section to know the colors that represent different exitstatus. Pointing on the pie chart gives the total number and percentage ofsuccessful, partially successful, and failed jobs in your NetBackup environment.For example, pointing on the red color in the pie chart shows that in the last 24hours, 72 jobs, or 42% jobs in your environment failed. This information is alsolisted in a tabular format. In addition, a table also shows the amount of data thathas been backed up for the selected view and timeframe.

You can drill down from this section to see details for failed, successful, or partiallysuccessful jobs.

To view jobs by exit status


2 Select SummaryView from the drop-down list. Note that the drop-down listis located on the top-right corner of the page.

3 In the Job Summary by Exit Status section, do either of the following:

■ Click the number of jobs (link) corresponding to a particular exit statusfrom the table.Or

■ Click a colored section of the pie chart that corresponds to a particularexit status. For example, click on the red section of the pie chart to viewdetails for failed jobs.


Viewing the Drive Summary by Status sectionThe Drive Summary by Status section shows an overall distribution of drives bydrive status for the current View pane selection. This information is shown in apie chart as well as a table.

Note: For 7.0.1 master servers, the Drive Summary by Status section does notshow the drives that are disabled or unreachable.

A pie chart with different colors represents the distribution of drives by drivestatus in the selected timeframe. Each color of the pie chart represents how drivesare distributed in your environment as per the drive status. You can also view thecolor code summary in this section to know the colors that represent differentexit status. Pointing on the pie chart provides the number and percentage of driveswith up or down status in your NetBackup environment. For example, pointingon the green color in the pie chart shows that 5 drives or 100% drives in yourenvironment are up.

You can drill down from this section to see details of all drives including up, down,or mixed drives.

To view drives by drive status


2 In the Drive Summary by Status section, do either of the following:

■ Click the number of drives (link) for a particular drive status from thetable. For example, click the number for Up drivesOr

■ Click a colored section of the pie chart that corresponds to a particulardrive status. For example, click on the green section of the pie chart toview details for the drives that are up.

About Top 7 Policies by Failed Jobs sectionThe Top7PoliciesbyFailedJobs section lists the top five policies which have themaximum failed jobs for the current View pane and timeframe selection. Data forthe last 24 hours is shown by default. You can also view data for the last 48 hoursor 72 hours.


The table that is shown in the section lists the top seven policies which havemaximum failed jobs associated with them. The table also shows the number offailed jobs for each policy. Note that the failed jobs (shown in Total Number of


406

Failed Jobs column) are arranged in descending order in the table. From thissection you can quickly view the policies which have the maximum failed jobsassociated with them.

Viewing the Alert Summary by Severity sectionThe Alert Summary by Severity section shows an overall distribution of alerts byseverity for the current View pane and timeframe selection. This information isshown in a pie chart as well as a table. Data for the last 24 hours is shown bydefault. You can also view data for the last 48 hours or 72 hours.


A pie chart with different colors represents the alert distribution by severity inthis section. Each color of the pie chart represents how alerts are distributed inyour environment as per the alert severity. You can also view the color codesummary in this section to know the colors that represent different severity.

Pointing on the pie chart gives the number and percentage of alerts with aparticular severity in your NetBackup environment. For example, pointing on thegreen color in the pie chart shows that in the last 24 hours, 200 alerts, or 17%alerts in your environment are critical.

You can drill down from this section to see details for alert categories.

To view alerts by severity


2 In the Alert Summary by Severity section, do either of the following:

■ Click the number of alerts (link) for a particular alert severity from thetable. For example, click on the number that is shown for Critical alerts.Or

■ Click a colored section of the pie chart that corresponds to a particularalert severity. For example, click on the red section of the pie chart to viewdetails for critical alerts.

Monitoring NetBackup jobsThe Monitor > Jobs view provides details of NetBackup jobs. You can use thefollowing views to see NetBackup job information:

407Monitoring NetBackup using Symantec OpsCenterMonitoring NetBackup jobs

This view is shown by default when youselect Monitor > Jobs. This view displaysdetailed information about jobs based on thecurrent View pane and timeframe selection.

Note: You can only view jobs data for thelast 30 days from the List View.

See “Using the List View for monitoring jobs”on page 408.

List View

The Summary View contains the differentsections which show the NetBackup jobdistribution by exit status, job state, and jobtype based on the current View pane andtimeframe selection. This information isshown in pie charts and tables.

See “Using the Summary View formonitoring jobs” on page 416.

Summary View

The Hierarchical View shows all parent-childjobs in a hierarchical fashion based on thecurrent View pane and timeframe selection.

Note: You can only view jobs data for thelast 30 days from the Hierarchical View.

See “Using the Hierarchical View formonitoring jobs” on page 421.

Hierarchical View

Note: You can select these views from the drop-down list. The drop-down list islocated at the top-right corner of the page.

Using the List View for monitoring jobsThis view is displayed when you select Monitor> Jobs. The List View is shown bydefault. This view displays detailed information for jobs for the current ViewPaneand timeframe selection. Data for the last 24 hours is shown by default. You canalso view data for the last 48 hours or 72 hours.


Note: You can only view jobs data for the last 30 days from the List View.

The table that appears in this view shows the following columns by default:

Monitoring NetBackup using Symantec OpsCenterMonitoring NetBackup jobs

408

This column shows the unique ID associatedwith the job (link).

Job ID

This column shows the name of the masterserver (link) associated with the job. You canclick on the link to view details for themaster server.

Master Server

This column lists the job type like whetherthe job is a DB Backup or an Image Cleanupjob.

Type

This column lists the current NetBackup jobstate like whether the job is Queued, Waitingfor Retry, Done etc.

State

Exit status of the job. The link providesstatus description and details ontroubleshooting in case it failed.

Status

This column lists the name of the policy thatis associated with the job.

Policy

This column lists the name of the client onwhich the job is run.

Client

This column lists the date, time, and yearwhen the job started.

Start Time

This column lists the time that is taken bythe job. The Elapsed Time is the differencebetween End Time and Start Time values.For a running job, Elapsed Time is thedifference between the current time andStart time.

Note: The contents of the Elapsed Timecolumn cannot be sorted in ascending ordescending order (when you click on thecolumn name.)

Elapsed Time

This column lists the date, time, and yearwhen the job ended.

End Time

This column lists the size of the job.Job Size

This column lists the number of files thathave been backed up by this job.

Files


This column lists the percentage of job thathas been completed.

% Complete

Not all columns are displayed in the table by default. More columns can be addedto your view by clicking the TableSettings icon. The TableSettings icon is locatedon the top-right corner of the table.

The following columns are not displayed in the table by default:.

■ Schedule

■ Source Media Server

■ Destination Media Server

■ Destination Storage Unit

■ Attempt

■ Operation

■ PID

■ Owner

■ Parent

■ KB per sec

■ Session ID

■ Data Movement

■ Backup Type

■ Schedule Type

■ Policy Type

■ Compression

■ Current File

■ Robot

■ Vault

■ Media to Eject

■ Copy

■ Profile

■ Active Start

■ Reconciliation Status


410

■ Reconciliation Reason

■ Data Reduction Savings (%)

■ Priority

■ State Details

See the online NetBackup Administration Console Help for a detailed descriptionof these fields.

More information about how to customize tables and view specific columns isavailable.

See “About using tables” on page 69.

Viewing the details for a single NetBackup jobAll the details that are associated with a job can be viewed from the Details pane.The Details pane is located at the bottom of the Monitor > Jobs view.

The Details pane has the following tabs:

The General tab of the Details pane displaysall information available for the job. It alsoincludes the contents of all the availablecolumns that can be viewed from the table.

General

The Attempts tab shows details of theattempts that have been made to completea job.

Attempts

The File List tab shows the files that havebeen backed up by the job and also theirlocation.

File List

To view details for a single NetBackup job

1 In the OpsCenter console, select Monitor > Jobs.

2 Click the ID (link) for a job from the Job ID column of the table. View the jobdetails in the Details pane

Viewing the details for a master server associated with a jobUse the following procedure to view the details for a master server that isassociated with a job.


To view information for the master server that is associated with a job


2 Click the server name (link) associated with the job in the Master Servercolumn of the table. The details of the master server are shown on a separatepage. You can also enable or disable data collection for the master serverfrom this page.

Viewing policy information for a jobUse the following procedure to view the details for the policy that is associatedwith a job.

To view policy information for a job


2 Click the policy name (link) for the job in the Policy column of the table.

3 A separate page appears that shows policy information on the following tabs:

This tab is shown by default. Most of thepolicy details are listed.

Click on the master server link to viewdetails of the master server that isassociated with the policy.

General

This tab displays the properties ofschedules that are associated with thepolicy.

Schedules

This tab displays the details of clients tobe backed up

Clients

This tab shows the files that are to bebacked up

Selection

Filtering on NetBackup job stateYou can filter by using any of the built-in job filters. These filters are availablefrom the drop-down list which is present on top of the table.

The built-in job filters are the following:

Select this filter to view details of all the jobs.All Jobs (default filter)

Select this filter to view only active jobsActive Jobs


412

Select this filter to view only queued jobs.Queued Jobs

Select this filter to view only Done jobs.Done Jobs

Select this filter to view the jobs that havebeen suspended.

Suspended Jobs

Select this filter to view the jobs that arewaiting for retry.

Waiting for Retry Jobs

Select this filter to view the jobs that areincomplete.

Incomplete Jobs

Select this filter to view the jobs that havebeen canceled.

Canceled Jobs

Select this filter to view the jobs that areundefined.

Undefined Jobs

Select this filter to view the jobs that aresuccessful.

Successful Jobs

Select this filter to view the jobs that arepartially successful.

Partially Successful Jobs

Select this filter to view the jobs that failed.Failed Jobs

In addition to using the built-in filters, you can also create your own custom filters.

See “Using filters to customize your views” on page 73.

To view details by job state

1 Select Monitor > Jobs.

2 Select a filter from the drop-down list. Note that the drop-down list is locatedon top of the table.

Controlling NetBackup jobsUse the following procedure to cancel, suspend, resume, or restart a job. Beforeyou perform these tasks, manually refresh your Web browser to obtain an updatedview for all jobs.

Note: These tasks are not visible if you log on with an Analyst or a Reporter role.


To control a job


2 Ensure that List View is selected in the drop-down list. Note that thedrop-down list is located on the top-right corner of the page.

3 Select a job from the table. You may select one or more jobs.

4 Click Cancel, Restart, Resume, Suspend. These buttons are located on topof the table.

The OpsCenter console may take some time to show the updated status onceyou perform the tasks.

Reconciling NetBackup jobsYou can use the Reconcile option to prevent the jobs that failed due to reasonslike user terminating a job, host cannot be reached etc. from being billed. By usingthe Reconcile option and selecting a reason, you can let your service providerknow not to bill you for these jobs as these jobs failed due to specific issues atyour end.

Note: The Reconcile option is disabled in the unlicensed version (SymantecOpsCenter).

Before you perform this task, manually refresh your Web browser to obtain anupdated view for all jobs

To reconcile NetBackup jobs



3 Select a job from the table. You can select one or more jobs.

4 From the More drop-down list, select Reconcile.

5 In the Reconcile Jobs dialog box, select a reason for reconciling the job fromthe drop-down list.

Note that you can select Un-Reconcile from the drop-down list to undo areconciliation.

6 Click OK.


414

Changing the job priorityYou can change the priority that is associated with a job.

Review the following points before changing the job priority:

■ Priority can be changed only for the jobs that are in Active or Queued state.

■ Priority can be changed only for jobs from the master servers that are runningNetBackup 6.5.2 or higher versions.

To change the job priority



3 Select an active job or a queued job from the table.

4 From the More drop-down list, select Change Job Priority.

5 In the Change Priority dialog box, set the job priority to a particular value.You can also increment or decrement the job priority.

6 Click OK.

7 Click Finish.

The OpsCenter console may take some time to show the updated status onceyou perform this task.

Exporting NetBackup job logsYou can export the log files that are associated with a job. You can view or savethe exported log files in an Excel format.

Note: The Export Job Logs option is not visible if you log on with an Analyst or aReporter role.

Note: Logs are not available for all job types. Before exporting a log file, ensurethat the NetBackup master server is Connected and the selected job logs areenabled.

To export the NetBackup log files for a job




3 Select a job from the table.

You can export only one job log at a time.

4 From the More drop-down list, select Export Job Logs.

5 Click Open or Save from the dialog box to view or save the log file in an Excelformat.

Using the Summary View for monitoring jobsThis view is displayed when you select Monitor > Jobs and then select SummaryView from the drop-down list. The drop-down list is located at the top-right cornerof the page.

The content that is shown in the Summary View is based on the current ViewPane and timeframe selection. Data for the last 24 hours is shown by default. Youcan also view data for the last 48 hours or 72 hours.


The Summary View contains the different sections which display specificinformation about NetBackup jobs. These sections show NetBackup job informationin a table as well as a pie chart. The table and the pie charts include links to filtereddetail views. You can use these links to drill down and access detailed informationabout NetBackup jobs.

Note: If you uncheck the AllowMultiple Selection inViewPane option, a GroupComponent Summary table is displayed when you access the Summary View forMonitor>Jobs. The Group Component Summary table displays information aboutimmediate NetBackup constituents of the view or node (group) that you selectedin the View pane. You can uncheck the Allow Multiple Selection in View Paneoption from Settings > User Preferences > General.

The following sections describe this view in detail:

■ Viewing the Job Summary by Exit Status section

■ Viewing the Job Summary by State section

■ Viewing the Job Summary by Type section

■ About the Group Component Summary table

Viewing the Job Summary by Exit Status sectionThe Job Summary by Exit Status section shows an overall distribution of jobs byexit status. The data that is shown in this view is based on the current View pane


416

and timeframe selection. This information is shown in a pie chart as well as atable. Data for the last 24 hours is shown by default. You can also view data forthe last 48 hours or 72 hours.


A pie chart with different colors represents the job distribution by exit status inthis section. Each color of the pie chart represents how jobs are distributed inyour environment as per the exit status. You can also view the color code summaryin this section to know the colors that represent different exit status. Pointingyour cursor on the pie chart gives the number and percentage of jobs with aparticular exit status in your NetBackup environment. For example, pointing yourcursor on the red color in the pie chart shows that in the last 24 hours, 72 jobs or42% jobs in your environment failed.

You can drill down from this section to see details for successful, partiallysuccessful, and failed jobs.

To view jobs by exit status



3 In the Job Summary by Exit Status section, do either of the following:

■ Click the number of jobs (link) corresponding to a particular exit statusfrom the table.Or

■ Click a colored section of the pie chart that corresponds to a particularexit status. For example, click on the red section of the pie chart to viewdetails for failed jobs.

Viewing the Job Summary by State sectionThe Job Summary by State section shows an overall distribution of jobs by theNetBackup job state based on the current View pane and timeframe selection.This information is shown in a pie chart as well as a table. Data for the last 24hours is shown by default. You can also view data for the last 48 hours or 72 hours.


A pie chart with different colors represents the job distribution by job state. Eachcolor of the pie chart represents how jobs are distributed in your environment asper the job state. You can also view the color code summary in this section to knowthe colors that represent different job states. Pointing your cursor on the pie chartgives the number and percentage of jobs in a particular job state in your NetBackupenvironment. For example, pointing your cursor on the yellow color in the pie


chart shows that in the last 24 hours, 22 jobs, or 42% jobs in your environmentare in a queued state.

You can drill down from this section to see details for the jobs that failed, the jobsthat are waiting for retry, queued or active jobs etc.

To view jobs by job state



3 In the Job Summary by State section, do either of the following:

■ Click the number of jobs (link) in a particular job state from the table. Forexample, click on the number that is shown for Done jobs.Or

■ Click a colored section of the pie chart that corresponds to a particularjob state. For example, click on the yellow section of the pie chart to viewdetails for Queued jobs.

Viewing the Job Summary by Type sectionThe Job Summary by Type section shows an overall distribution of jobs by thejob type based on the current View pane and timeframe selection. This informationis shown in a pie chart as well as a table. Data for the last 24 hours is shown bydefault. You can also view data for the last 48 or 72 hours.


A pie chart with different colors represents the job distribution by job type in thissection. Each color of the pie chart represents how jobs are distributed in yourenvironment as per the job type. You can also view the color code summary inthis section to know the colors that represent different job types. Pointing yourcursor on the pie chart gives the number and percentage of jobs of a particularjob type in your NetBackup environment. For example, pointing your cursor onthe red color in the pie chart shows that in the last 24 hours, 22 jobs or 42% jobsin your environment are DBBackup jobs.

You can drill down from this section to see details for different job types likeDBBackup, Image Cleanup etc.


418

To view jobs by job type



3 In the Job Summary by Type section, do either of the following:

■ Click the number of jobs (link) corresponding to a particular job type fromthe table. For example, click on the number that is shown for DBBackupjobs.Or

■ Click a colored section of the pie chart that corresponds to a particularjob type. For example, click on the red section of the pie chart to viewdetails for DBBackup jobs.

About the Group Component Summary tableWhen you uncheck the option called AllowMultipleSelectionInViewPane underSettings > User Preferences > General view in the OpsCenter console, you canview the Group Component Summary table in the Summary View for Monitor >Jobs. The Group Component Summary table is displayed at the bottom of theSummary View for Monitor > Jobs. The Group Component Summary table wasalso displayed in NOM earlier.

You must select a group (view or node) from the View Pane to see data in the GroupComponent Summary table. You will not see any data in the Group ComponentSummary table if you select a specific view object (master server) in the ViewPane.

More details about nodes and view objects is available.

See “About nodes and objects” on page 386.

The Group Component Summary table displays job summary information aboutthe immediate NetBackup constituents of the selected view or node (group) in theView pane. For example if you select the ALL MASTER SERVERS view, the GroupComponent Summary table displays job summary for each master server. If youselect a view that contains multiple nodes, a job summary of the nodes (and notthe view objects for each node) is displayed.

Note: OpsCenter or OpsCenter Analytics monitors only NetBackup. Hence anyother servers (like BE, PD, or TSM servers) do not appear in the Group ComponentSummary table.


The information that is displayed in the Group Component Summary table isbased on the current View Pane and timeframe selection. Data for the last 24hours is shown by default. You can also view data for the last 48 or 72 hours.


Table 8-1 explains the information that is displayed in the Group ComponentSummary table.

Table 8-1 Columns and descriptions in the Group Component Summary table

DescriptionColumn

Name of the node or view object.Name

Total number of jobs (link) for the specificnode or view object in the selectedtimeframe. Click on the link to view detailedinformation about all the jobs.

Total

Number of successful jobs (link) for thespecific node or view object in the selectedtimeframe. Click the link to view detailedinformation about successful jobs.

Successful

Number of partially successful jobs (link) forthe specific node or view object in theselected timeframe. Click the link to viewdetailed information about the partiallysuccessful jobs.

Partially Successful

Number of failed jobs (link) for the specificnode or view object in the selectedtimeframe. Click the link to view detailedinformation about the failed jobs.

Failed

Data backed up for the specific node or viewobject in the selected timeframe.

Data Backup up

Number of active jobs (link) for the specificnode or view object in the selectedtimeframe. Click the link to view detailedinformation about the active jobs.

Active

Number of queued jobs (link) for the specificnode or view object in the selectedtimeframe. Click the link to view detailedinformation about the queued jobs.

Queued


420

Table 8-1 Columns and descriptions in the Group Component Summary table(continued)

DescriptionColumn

Number of suspended jobs (link) for thespecific node or view object in the selectedtimeframe. Click the link to view detailedinformation about the suspended jobs.

Suspended

Number of incomplete jobs (link) for thespecific node or view object in the selectedtimeframe. Click the link to view detailedinformation about the incomplete jobs.

Incomplete

Number of undefined jobs (link) for thespecific node or view object in the selectedtimeframe. Click the link to view detailedinformation about the undefined jobs.

Undefined

Number of jobs that are waiting for retry(link) for the specific node or view object inthe selected timeframe. Click the link to viewdetailed information about the jobs that arewaiting for retry.

Waiting for Retry

Using the Hierarchical View for monitoring jobsThis view is displayed when you select Monitor>Jobs and then select HierarchicalView from the drop-down list. The data that is shown in this view is based on thecurrent View pane and timeframe selection. Data for the last 24 hours is shownby default. You can also view data for the last 48 or 72 hours.

Note: You can only view jobs data for the last 30 days from the Hierarchical View.


In the Hierarchical View, all related jobs can be grouped and you can see allparent-child jobs in a hierarchical fashion. You can view details of only the toplevel, parent job in this view with the ability to expand and drill into the detailsof child jobs if there are failures.

The Hierarchical View shows details of all jobs and also highlights the parent-childrelationship between jobs wherever applicable. All parent jobs have a +sign beforethe job ID. You can click the + sign to see all child jobs. A child job is indented tothe right-hand side in the Job ID column. If some of the child jobs are parent jobs,


then + sign also appears before the job ID of the child job. However, if a job doesnot have a relationship with any other job (meaning it is neither a parent nor achild job), it is represented only by its job ID in the Job ID column. Neither is therea + sign before the job ID of such a job nor this job is indented to the right-handside.

Note the following things about the related jobs that are shown in the HierarchicalView:

■ The filters are applied only to parent jobs. The filters are not applied to childjobs. For example, if you apply the Partially Successful Jobs filter, child jobsare not considered at all. Only parent jobs or unrelated jobs (jobs that are notrelated to any other job) with partially successful status are considered.

■ The sorting feature in the Hierarchical View applies to both parent jobs andchild jobs. When you expand a parent job, the current selected sort order isapplied to child jobs.

■ All tasks that apply to the parent job are also applicable to its child jobs.

Viewing the details for a single NetBackup jobAll the details that are associated with a job can be viewed from the Details pane.The Details pane is located at the bottom of the Monitor > Jobs view.


The General tab of the Details pane displaysall information available for the job. It alsoincludes the contents of all the availablecolumns that can be viewed from the table.

General

The Attempts tab shows details of theattempts that have been made to completea job.

Attempts

The File List tab shows the files that havebeen backed up by the job and also theirlocation.

File List

To view details for a single NetBackup job


2 Select Hierarchical View from the drop-down list. The drop-down list islocated at the top-right corner of the view.

3 Click the ID (link) for a job from the Job ID column of the table.

4 View the job details in the Details pane.


422

Viewing the details for a master server associated with a jobUse the following procedure to view the details for a master server that isassociated with a job.

To view information for the master server that is associated with a job



3 Click the server name (link) associated with the job in the Master Servercolumn of the table. The details of the master server are shown on a separatepage. You can also enable or disable data collection for the master serverfrom this page.

Viewing policy information for a jobUse the following procedure to view the details for the policy that is associatedwith a job.

Note: You can also view policy information from the List View.

To view policy information for a job



3 Click the policy name (link) for the job in the Policy column of the table.

4 A separate page appears that shows policy information on the following tabs:

This tab shows most of the policy details.General (default tab)

This tab displays the properties of theschedules that are associated with thepolicy.

Schedules

This tab displays the details of clients tobe backed up.

Clients

This tab shows the files that are to bebacked up.

Selection


Filtering on NetBackup job stateYou can filter by using any of the following built-in job filters. These filters areavailable from the drop-down list which is present on top of the table.

The built-in job filters are the following:

Select this filter to view details of all the jobs.All Jobs (default filter)

Select this filter to view only active jobsActive Jobs

Select this filter to view only queued jobs.Queued Jobs

Select this filter to view only Done jobs.Done Jobs

Select this filter to view the jobs that havebeen suspended.

Suspended Jobs

Select this filter to view the jobs that arewaiting for retry.

Waiting for Retry Jobs

Select this filter to view the jobs that areincomplete.

Incomplete Jobs

Select this filter to view the jobs that areundefined.

Undefined Jobs

Select this filter to view the jobs that havebeen canceled.

Canceled Jobs

Select this filter to view the jobs that aresuccessful.

Successful Jobs

Select this filter to view the jobs that arepartially successful.

Partially Successful Jobs

Select this filter to view the jobs that failed.Failed Jobs



To view details by job state





424

Controlling NetBackup jobsUse the following procedure to cancel, suspend, resume, or restart a job. Beforeyou perform these tasks, manually refresh your Web browser to obtain an updatedview for all jobs.


To control a job


2 Select Hierarchical View from the drop-down list. Note that the drop-downlist is located on the top-right corner of the page.

3 Select a job from the table. You may select one or more jobs.

4 Click Cancel, Restart, Resume, Suspend.

The OpsCenter console may take some time to show the updated status onceyou perform these tasks.

Reconciling NetBackup jobsYou can use the Reconcile option to prevent the jobs that failed due to reasonslike user terminating a job, host cannot be reached etc. from being billed. By usingthe Reconcile option and selecting a reason, you can let your service providerknow not to bill you for these jobs as these jobs failed due to specific issues atyour end.

Note: The Reconcile option is disabled in the unlicensed version (SymantecOpsCenter).

The Reconcile option is not visible if you log on with an Analyst or a Reporterrole.

Before you perform this task, manually refresh your Web browser to obtain anupdated view for all jobs

To reconcile NetBackup jobs



3 Select a job from the table. You can select one or more jobs.

4 From the More drop-down list, select Reconcile.


5 In the Reconcile Jobs dialog box, select a reason for reconciling the job fromthe drop-down list.

Note that you can select Un-Reconcile from the drop-down list to undo areconciliation.

6 Click OK.

Changing the job priorityYou can change the priority that is associated with a job.

Review the following points before changing the job priority:

■ Priority can be changed only for the jobs that are in Active or Queued state.

■ Priority can be changed only for jobs from the master servers that are runningNetBackup 6.5.2 or higher versions.

Note: The Change Job Priority option is not visible if you log on with an Analystor a Reporter role.

To change the job priority



3 Select an active job or a queued job from the table.

4 From the More drop-down list, select Change Job Priority.

5 In the Change Priority dialog box, set the job priority to a particular value.You can also increment or decrement the job priority.

6 Click OK.

7 Click Finish.

The OpsCenter console may take some time to show the updated status onceyou perform this task.

Monitoring NetBackup servicesThis view is displayed when you select Monitor > Services. This view containsdetailed information for services. The data that is shown in this view is based onthe current View pane selection.


Monitoring NetBackup using Symantec OpsCenterMonitoring NetBackup services

426

The table that appears in this view has the following columns:

This column lists the name of the service.Name

This column lists the name of the masterserver or media server where the service ordaemon is present.

Host Name

This column lists the NetBackup servicetype.

Example: Vault Manager, Device Manager,or Service Layer

Service Type

The operational status of the service ordaemon. This status can be Stopped,Running, or Other.

Other can be Not Installed, Not Licensed,Start Pending, Stop Pending, RestartPending, Failed, or Unknown.

Note: The status for some services mayshow as Stopped on the Monitor>Servicespage in the OpsCenter console. This may bebecause the license for these services iseither not installed or configured for aspecific media or master server.

Status

You can perform the following tasks from this view:

See “Filtering on NetBackup service type”on page 427.

Use filters to view specific services

See “Controlling NetBackup services”on page 428.

Control NetBackup services

Filtering on NetBackup service typeYou can filter by using any of the four built-in filters. These filters are availablefrom the drop-down list which is present on top of the table.

The built-in filters are the following:

Select this filter to view details of all theservices.

All Services (default filter)

427Monitoring NetBackup using Symantec OpsCenterMonitoring NetBackup services

Select this filter to view details of theservices that have been stopped.

Stopped Services

Select this filter to view details of runningservices.

Running Services

Select this filter to view details of all otherservices like Not Licensed, Unknown (notrecognized by OpsCenter), or Not Applicable(some services may not be applicable toearlier versions).

Other Services



Use the following procedure to view details by type of service.

To view details by type of service

1 In the OpsCenter console, select Monitor > Services.


Controlling NetBackup servicesUnder certain circumstances there may be issues among multiple OpsCenterusers. For instance, one OpsCenter user stops a service while another user triesto start the same service.

Note: NetBackup service layer (nbsl) cannot be controlled from OpsCenter.

To control a service

1 Refresh your Web browser to obtain an updated state for all services.

2 In the OpsCenter console, select Monitor > Services.

Monitoring NetBackup using Symantec OpsCenterMonitoring NetBackup services

428

3 Select a service from the table. You can select one or more services.

4 Click Start, Stop, or Restart. Note that these tasks are located on top of thetable.

Note: These tasks are not visible if you log on with an Analyst or a Reporterrole.

The OpsCenter console may take some time to show the updated status onceyou perform these tasks. Stop, Running, or Restart Pending appears in theStatus column until the selected action completes.

If you start or stop a service that has a dependency on another service,NetBackup ensures that any dependent services are also started or stopped.

Monitoring NetBackup policiesThe Monitor > Policies view provides details of NetBackup policies. You can usethe following views to see NetBackup policy information:

The List View is shown by default when youselect Monitor > Policies. This view showsdetailed information about NetBackuppolicies based on the current View paneselection.

See “Using the List View for monitoringNetBackup policies” on page 430.

List View

The Summary View contains the differentsections that display specific informationabout NetBackup policies based on thecurrent View pane and timeframe selection.These sections show specific policyinformation in a table as well as a pie chart.

See “Using the Summary View formonitoring policies” on page 436.

Summary View


429Monitoring NetBackup using Symantec OpsCenterMonitoring NetBackup policies

Using the List View for monitoring NetBackup policiesThis view is displayed when you select Monitor > Policies. This view containsdetailed information about policies. The data that is shown in this view is basedon the current View pane selection.



Name of the policy. Click the link to viewdetails about the policy.

Name

Name of the master server that is associatedwith the policy. Click the link to view detailsof master server.

Master Server

This column is the policy type. Usually, thePolicy type determines the type of clientsthat can be backed up by this policy.Example: DB2, NBU-Catalog, Oracle, Sybase,Vault etc.

Type

Storage that is associated with the policy.Click the link to view details for storage.

Storage

Volume pool that is associated with thepolicy. Click the link to view details ofvolume pool.

Volume Pool

Interval (in minutes) between twocheckpoints in NetBackup.

CheckPoint Interval

The total number of jobs that are associatedwith the policy.

Jobs/Policy

Priority that you have defined for the policy.Zero means the lowest priority.

Priority

This column determines whether the policyis Active or not.

Active

Not all of the available columns appear initially in this view. The following columnsdo not appear, but can be added to your view by clicking the Table Settings icon:

■ Data Classification

■ Effective Date

■ Compression

Monitoring NetBackup using Symantec OpsCenterMonitoring NetBackup policies

430

■ Encryption

■ Block Level Increments

■ Allow Multiple Data Streams

■ Offhost

■ Follow NFS

■ Cross Mount Points

■ Individual File Restore From Raw

■ True Image Recovery

■ Collect Disaster Recovery Information

■ Collect Bare Metal Restore Information

■ Snapshot Backups

■ Alternate Client

■ Data Mover

■ Virtual Machine Proxy

■ Snapshot Method

■ Keyword Phrase

■ Policy Domain Name





See “Filtering on NetBackup policy type”on page 432.

Use filters to view specific policies

See “Viewing details for a single NetBackuppolicy” on page 433.

View the details for a single NetBackuppolicy

See “Viewing the details for a master serverassociated with a policy” on page 433.

View the details for a master serverassociated with a policy

See “Viewing the details for storageassociated with a policy” on page 434.

View the details for storage that is associatedwith a policy


See “Viewing the details for a volume poolassociated with a policy” on page 434.

View the details for a volume pool that isassociated with a policy

See “Managing a job policy” on page 434.Manage a job policy

See “Starting a manual backup” on page 435.Start a manual backup

See “Viewing the history for a single jobpolicy ” on page 435.

View the history for a job policy

See “Using the Summary View for monitoring policies” on page 436.

Filtering on NetBackup policy typeYou can filter by using any of the seven built-in filters. These filters are availablefrom the drop-down list which is present on top of the table.


Select this filter to view details of allNetBackup policies.

All Policies (default filter)

Select this filter to view details of the policiesthat are active.

Active Policies

Select this filter to view details of the policiesthat are inactive.

Inactive Policies

Select this filter to view details of all policiesthat apply to Windows clients.

Windows Policies

Select this filter to view details of catalogpolicies.

Catalog Policies

Select this filter to view details of Standardpolicies.

Standard Policies

Select this filter to view details of all otherpolicies like DB2 policies, SAP policies, OS2policies etc.

Other Policies



Use the following procedure to view details by type of policy.


432

To view details by type of policy

1 In the OpsCenter console, select Monitor > Policies.


Viewing details for a single NetBackup policyAll the details that are associated with a policy can be viewed from the Detailspane. The Details pane is located at the bottom of the Monitor > Jobs view.


The General tab of the Details pane displaysall information available for the policy. Italso includes contents of all the columns thatcan be viewed from the table.

You can also click the master server name(link) to get details of the master server.

General

The Schedules tab displays details of theschedules that are associated with the policy.

Schedules

The Clients tab shows details of clients to bebacked up by the policy.

Clients

The Selections tab shows the files that havebeen backed up by the policy and also theirlocation.

Selections

To view details for a single NetBackup policy


2 Click the name (link) for a policy from the Name column of the table.

3 View the policy details in the Details pane.

Viewing the details for amaster server associatedwith a policyUse the following procedure to view the details for a master server that isassociated with a policy.


To view information for the master server that is associated with a policy


2 Click the server name (link) associated with the policy from the MasterServercolumn of the table. The details of the master server are shown on a separatepage. You can also enable or disable data collection for the master serverfrom this page.

Viewing the details for storage associated with a policyUse the following procedure to view the details for the storage that is associatedwith a policy.

To view information for the storage that is associated with a policy


2 Click the storage name (link) associated with the policy in the Storage columnof the table. The details of the storage are shown on a separate page. You canalso view details for the master server from this page.

Viewing the details for a volume pool associated with a policyUse the following procedure to view the details for a volume pool that is associatedwith a policy.

To view information for the volume pool that is associated with a policy


2 Click the volume pool name (link) associated with the policy from the VolumePool column in the table. The details of the volume pool are shown on aseparate page.

Managing a job policyUse the following procedure to activate or deactivate a policy. Before you performthese tasks, manually refresh your Web browser to obtain an updated view of allpolicies.



434

To activate or deactivate a policy


2 Select a job policy from the table.

3 Click Activate or Deactivate. Note that these options are located on top ofthe table.


Starting a manual backupUse the following procedure to start a manual backup. Before you perform thistask, manually refresh your Web browser to obtain an updated view of all policies.

The OpsCenter console may take some time to show the updated status once youperform this task.

Note: This task is not visible if you log on with an Analyst or a Reporter role.

To start a manual backup


2 Select a policy from the table. You can select only one policy and it must bean active policy.

3 Click Manual Backup. Note that this option is located on top of the table.

4 You can select a schedule and a client from the drop-down lists for the backup,or only select a schedule or a client.

If you do not select a schedule, NetBackup uses the schedule with the highestretention level.

If you do not select a client, NetBackup backs up all scheduled clients.

Viewing the history for a single job policyUse the following procedure to view the history for a policy.

Note: This task is not visible if you log on with an Analyst or a Reporter role.

To view the history for a policy


2 Select a job policy from the table.


3 Click View History. Note that this option is located on top of the table.

4 The Compare Policies tab displays the policy versions. You must select twoversions from the RetirementDate column to compare versions. The changesare highlighted in red color.

To view only the differences between the versions, click the ViewDifferencestab.

Using the Summary View for monitoring policiesThis view is displayed when you select Monitor > Policies and then selectSummary View from the drop-down list. The drop-down list is located at thetop-right corner of the page. This view contains detailed information about policies.

The content that is shown in the Summary View is based on the current Viewpane and timeframe selection. Data for the last 24 hours is shown by default. Youcan also view data for the last 48 or 72 hours.


The Summary View contains the different sections which display specificinformation about NetBackup policies. These sections show specific policyinformation in a table as well as a pie chart. The table and the pie charts includelinks to filtered detail views. You can use these links to drill down and accessdetailed information about NetBackup policies.

The following sections describe this view in detail

■ About Top 5 Policies by Data Backed up section

■ About Top 7 Policies by Failed Jobs section

■ About Top 7 Policies by No. of Jobs section

About Top 5 Policies by Data Backed up sectionThe Top 5 Policies by Data Backed up section lists the top five policies whichhave the maximum data backed up for the current View pane and timeframeselection. Data for the last 24 hours is shown by default. You can also view datafor the last 48 or 72 hours.


The table that is shown in the section lists the top five policies which havemaximum data backed up. The table also shows the data that is backed up for eachpolicy. Note that the data that is backed up (shown in Volume (Bytes) column) isarranged in descending order in the table. From this section, you can quickly viewthe policies which have the maximum data backed up.


436

About Top 7 Policies by Failed Jobs sectionThe Top 7 Policies by Failed Jobs section lists seven policies which have themaximum failed jobs for the current View pane and timeframe selection. Datafor the last 24 hours is shown by default. You can also view data for the last 48 or72 hours.


The table that is shown in the section lists the top seven policies which havemaximum failed jobs associated with them. The table also shows the total numberof failed jobs for each policy. Note that the failed jobs (shown in Total Number ofJobs column) are arranged in descending order in the table. From this section,you can quickly view the policies which have the maximum failed jobs associatedwith them.

Note: This section can also be viewed from Monitor > Overview.

About Top 7 Policies by No. of Jobs sectionThe Top 7 Policies by No. of Jobs section lists seven policies which have themaximum number of jobs. This data is based on the current View pane andtimeframe selection. Data for the last 24 hours is shown by default. You can alsoview data for the last 48 or 72 hours.


The table that is shown in the section lists the policies which have maximumnumber of jobs. The table also shows the total number of jobs for each policy. Notethat the total number of jobs for each policy (shown in Total Number of Jobscolumn) are arranged in descending order in the table. From this section, you canquickly view the policies which have the maximum number of jobs associatedwith them.

Monitoring NetBackup mediaThe Monitor >Media view provides details of NetBackup media. You can use thefollowing views to see details about NetBackup media:

437Monitoring NetBackup using Symantec OpsCenterMonitoring NetBackup media

The List View is shown by default when youselect Monitor > Media. This view showsdetailed information about NetBackup mediafor the current View pane selection.

See “Using the List View for monitoringNetBackup media” on page 438.

List View

The Summary View displays the volume poolavailable for each master server for thecurrent View pane selection. It also showsother media details that are associated withthe master server like Frozen Media Count,Suspended Media Count etc.

See “Using the Summary View formonitoring NetBackup media” on page 443.

Summary View

The Hierarchical View by Volume Poolshows details of all media and also groupsmedia by volume pool for the current Viewpane selection.

See “Using the Hierarchical View by VolumePool for monitoring media” on page 444.

Hierarchical View by Volume Pool

The Hierarchical View by Volume Groupshows details of all media and also groupsmedia by volume group for the current Viewpane selection.

See “Using the Hierarchical View by VolumeGroup for monitoring media” on page 445.

Hierarchical View by Volume Group


Using the List View for monitoring NetBackup mediaThis view is displayed when you select Monitor > Media. This view containsdetailed information for media. This data is based on the current View paneselection.



Monitoring NetBackup using Symantec OpsCenterMonitoring NetBackup media

438

Unique ID associated with a media. Click thelink to view details about the media.

Media ID

Name of the master server that is associatedwith the media. Click the link to view detailsof master server.

Master Server

Type of media like 8mm, 4mm etc.Media Type

Specifies the robot type of the robot toinventory. Example: tl4, tl8 etc.

Robot Type

Unique, logical identification number for therobot to inventory.

Robot Number

Slot in the robot that contains the volume.Slot

The number of times that the volume hasbeen mounted.

Mounts

The date when the volume was assigned foruse.

Time Assigned

The maximum number of mounts (orcleanings) that are allowed for the volume.Zero (0) indicates unlimited mounts.

Max. Mounts

Date when the images on the volume expire.Data Expiration

The most recent time NetBackup used thevolume for backups.

Last Written

Current media status like Frozen, Active etc.Media Status

Capacity that has been used.Used Capacity


■ Last Write Host

■ Side

■ Partner

■ First Mount

■ Last Mount

■ Cleanings Remaining

■ Created


■ Description

■ Vault Name

■ Date Vaulted

■ Return Date

■ Vault Slot

■ Session ID

■ Vault Container ID

■ Last Read

■ Images

■ Valid Images

■ Number of Restores

■ Conflicts

■ Origin Host

■ Media Owner

■ Cleaning Media

■ Imported

■ Multiplexed

■ Multiretention

■ Last Restore

■ Volume Expiration

■ Retention Level





See “Viewing the details for NetBackupmedia” on page 441.

View the details for a particular NetBackupmedia


440

See “Viewing the details for a master serverassociated with the media” on page 441.

View the details for a master server that isassociated with the media

See “Filtering on NetBackup media type”on page 441.

Use filters to view specific media

See “Controlling media” on page 442.Control media

Viewing the details for NetBackup mediaAll the details that are associated with a media can be viewed from the Detailspane. The Details pane is located at the bottom of the view.

To view the details for a particular media

1 In the OpsCenter console, select Monitor > Media.

2 Click a drilldown link from the Media ID column. View the media propertiesfrom the Details pane. From the Details pane, you can also click the masterserver link to see details about the master server that is associated with themedia.

Viewing the details for a master server associated with themediaUse the following procedure to view the details for a master server that isassociated with a media.

To view the details for a master server associated with a media


2 Click the server name (link) associated with the media in the Master Servercolumn of the table. The details of the master server are shown on a separatepage.

Filtering on NetBackup media typeYou can sort and filter this view to focus on the specific type of media that youwant to see. For example, you can create and apply a filter that displays full mediaonly. You can filter by using any of the built-in filters. These filters are availablefrom the drop-down list which is present on top of the table.


Select this filter to view details of all media.All Media (default filter)


Select this filter to view details of the mediathat have been assigned to an individual forfurther action.

Assigned Media

Select this filter to view details of the mediathat are unassigned.

Unassigned Media

Select this filter to view details of the mediathat are frozen.

Frozen Media

Select this filter to view details of the mediathat are full.

Full Media

Select this filter to view details of the mediathat are suspended.

Suspended Media

Select this filter to view details of all othermedia like Multi Retention Level media, BEmedia etc.

Other Media

Select this filter to view details of media withActive status.

Active Media

Select this filter to view details of cleaningmedia.

Cleaning Media

In addition to the built-in filters, you can create your own custom filters.


Use the following procedure to view details by type of media.

To view details by type of media



Controlling mediaUse the following procedure to freeze, unfreeze, suspend, or unsuspend specificmedia. Note that to perform these tasks the media must be assigned to NetBackup.The media is assigned if there is a date in the Time Assigned column.



442

To perform media tasks


2 Select a media ID from the table (use the check box).

3 Click Freeze, Unfreeze, Suspend, or Unsuspend. Note that these options arepresent on top of the table.


Using the Summary View for monitoring NetBackup mediaThis view is displayed when you select Monitor>Media and then select SummaryView from the drop-down list. The drop-down list is located at the top-right cornerof the page. The data that is shown in this view is based on the current View paneselection.


The table that appears in this view displays the volume pool available for eachmaster server. It also shows other media details that are associated with the masterserver like Frozen Media Count, Suspended Media Count etc.

The following columns are shown in the table:

Name of the master serverMaster Server

Name of the volume pool that is associatedwith the master server

Volume Pool name

Total number of the frozen media that isassociated with the master server.

Frozen Media Count

Total number of the suspended media thatis associated with the master server.

Suspended Media Count

Total number of the full media associatedwith the master server.

Full Media Count

Total number of active media associated withthe master server.

Active Media Count

Total number of all other media like MultiRetention Level media, BE media etc. thatare associated with the master server .

Other Media Count

Total number of the media that are availablefor the master server.

Available Media Count


Using the Hierarchical View by Volume Pool for monitoring mediaThis view is displayed when you select Monitor > Media and then selectHeirarchical View by Volume Pool from the drop-down list. The drop-down listis located at the top-right corner of the page. The data that is shown in this viewis based on the current View pane selection.


The HierarchicalViewbyVolumePool shows details of all media and also groupsmedia by volume pool. Each volume pool that is shown in the Media ID columnhas a +sign before it. You can expand a volume pool to see all media that are apart of this volume pool. Note that the media are indented to the right-hand sidein the Media ID column.

The sorting feature in this view applies only to media in the volume pool. Whenyou expand a volume pool, the current selected sort order is applied to media inthe pool.

The following tasks can be performed from this view:

See “Viewing the details for volume pool”on page 444.

View the details for volume pool

See “Viewing the details for media”on page 444.

View details for the media that are a part ofa specific volume pool


Viewing the details for volume poolUse the following procedure to view the details for a volume pool.

To view details for a volume pool


2 Select Hierarchical View by Volume Pool from the drop-down list. Thedrop-down list is located at the top-right corner of the page.

3 Click a volume pool (link) from the MediaID column. Note that a volume poolhas a + sign on the left side. The details for the volume pool are shown in theGeneral tab at the bottom of this view.

Viewing the details for mediaUse the following procedure to view details for the media that are part of a specificvolume pool.


444

To view the details for media



3 Expand a volume pool from the Media ID column. This shows the media thatare a part of the volume pool. Note that the media are indented to theright-hand side

4 Click the media ID (link). Details for the media are shown in the General tabat the bottom of the view.






3 Expand a volume pool from the Media ID column. This shows the media thatare a part of the volume pool. Note that the media are indented to theright-hand side

4 Select a media ID (use the check box).

5 Click Freeze, Unfreeze, Suspend, or Unsuspend. Note that these tasks arepresent on top of the table.


Using the Hierarchical View by Volume Group for monitoring mediaThis view is displayed when you select Monitor > Media and then selectHeirarchical View by Volume Group from the drop-down list. The drop-downlist is located at the top-right corner of the page. The data that is shown in thisview is based on the current View pane selection.



The Hierarchical View by Volume Group shows details of all media and alsogroups media by volume group. Each volume group shown in the MediaID columnhas a +sign before it. You can expand a volume group to see all media that are apart of this volume group. Note that the media are indented to the right-hand sidein the Media ID column.

The sorting feature in this view applies to media in the volume group. When youexpand a volume group, the current selected sort order is applied to media in thatgroup.


See “Viewing the details for a volume group”on page 446.

View the details for a volume group

See “Viewing the details for media”on page 446.

View details for the media that are part of aspecific volume group


Viewing the details for a volume groupUse the following procedure to view the details for a specific volume group.

To view details for a volume group


2 Select Hierarchical View by Volume Group from the drop-down list. Thedrop-down list is located at the top-right corner of the page.

3 Click a volume group (link) from the Media ID column. Note that a volumegroup has a + sign on the left side. The details for the volume group are shownin the General tab at the bottom of this view.

Viewing the details for mediaUse the following procedure to view details for media that are part of a specificvolume group.

To view the details for media




446

3 Expand a volume group from the Media ID column. This shows the mediathat are a part of the volume group. Note that the media are indented to theright-hand side

4 Click the media ID (link). Details for the media are shown in the General tabat the bottom of the view.






3 Expand a volume group from the Media ID column. This shows the mediathat are a part of the volume group. Note that the media are indented to theright-hand side

4 Select a media ID (use the check box).

5 Click Freeze, Unfreeze, Suspend, or Unsuspend. Note that these options arepresent on top of the table.


Monitoring NetBackup devicesThis view is displayed when you select Monitor > Devices.

This view contains the following two tabs:

447Monitoring NetBackup using Symantec OpsCenterMonitoring NetBackup devices

This tab is shown by default when you selectMonitor > Devices. The contents of theDrives tab are shown by default.

This view displays the current drive statusinformation based on the current View paneselection.

See “Using the List View for monitoringdrives” on page 448.

See “Using the Summary view to monitordrives” on page 452.

Drives

This view displays detailed informationabout the disk pools that are configured foruse by NetBackup based on the current Viewpane selection.

See “Monitoring NetBackup disk pools”on page 453.

Disk Pools

Using the List View for monitoring drivesThis view is displayed when you select Monitor > Devices > Drives. This viewshows the current drive status information. The data that is shown in this viewis based on the current View pane selection.


Note: For 7.0.1 master servers, the List View does not show a drive that isunreachable or disabled. Similarly if one of the paths for a drive is unreachableor disabled, it is not shown in the Paths tab that appears in the List View.

The table that appears in this view shows the following information:

The name that is assigned to the drive whenit was added to NetBackup.

Drive Name

The name of the device host where the driveis connected.

Device Host

Name of the master server that is associatedwith the drive.

Master Server

Type of drive like 4mm, 8mm etc.Drive Type

The type of robot that contains this drive.Robot Type

Monitoring NetBackup using Symantec OpsCenterMonitoring NetBackup devices

448


■ Serial Number

■ Cleaning Frequency

■ Shared

■ Inquiry Information

■ Volume Header Path

■ ACS

■ LSM

■ Panel

■ Drive

■ Vendor Drive Identifier

■ Robot Number

■ Robot Drive Number

■ Recorded Media ID

■ Drive Status

■ Assigned Host

■ Control Host Name

■ Control Mode

■ Evsn

■ Control Up

■ Last Clean Time

■ Local Control

■ Mounted Time

■ NDMP

■ Occupy Index

■ Opr Comment

■ Ready

■ Request ID

■ Scan Host


■ VM Host

■ Write Enabled





See “Viewing the details for a single drive”on page 450.

View the details for a single drive

See “Viewing the details for a master serverassociated with a drive” on page 450.

View the details for a master server that isassociated with a drive

See “Filtering on NetBackup drive category”on page 451.

Use filters to view specific drives

See “Controlling drives” on page 451.Control drives

Viewing the details for a single driveAll the details that are associated with a drive can be viewed from the Detailspane. The Details pane is located at the bottom of the view.

To view the details for a single drive

1 Select Monitor > Devices > Drives. The List View is shown by default.

2 Click the drilldown link from the DriveName column. The drive informationcan be viewed from the General and Paths tab of the Details pane. From theGeneral tab, you can also click the master server link to see details about themaster server that is associated with the drive.

Viewing the details for amaster server associatedwith a driveUse the following procedure to view details for a master server that is associatedwith a drive.

To view the details for a master server associated with a drive

1 Select Monitor > Devices > Drives. The List View is shown by default.

2 Click the drilldown link from the Master Server column. The master serverinformation can be viewed from a separate page.


450

Filtering on NetBackup drive categoryYou can sort and filter this view to focus on the specific type of drives that youwant to see. For example, you can apply a filter that displays only those drivesthat are up. You can filter by using any of the built-in filters. These filters areavailable from the drop-down list which is present on top of the table.

The following built-in filters are available:

The All Drives filter is the default filter.Select this filter to view all drives.

All Drives

Select this filter to view only those drivesthat are up. For up drives, all drive paths areup.

Up Drives

Select this filter to view only those drivesthat are down. For down drives, all drivepaths are down.

Down Drives

Select this filter to view mixed drives. Formixed drives, some drive paths are up andsome drive paths are down.

Mixed Drives



Use the following procedure to view details by type of drives.

To view details by type of drives

1 In the OpsCenter console, select Monitor > Devices > Drives. Ensure thatList View is selected in the drop-down list.


Controlling drivesSee theNetBackupAdministrator'sGuide,Volume I for information on drive statesand how to control drives.

Before you perform these tasks, manually refresh your Web browser to obtain anupdated view of all drives. When you refresh, you also ensure that the drive is notinvolved in any tasks by other users.



To control drives

1 In the OpsCenter console, select Monitor > Devices > Drives. The List Viewis displayed by default.

2 Select a drive from the Drive Name column in the table.

3 Click Up, Down, or Reset. Note that these options are located on top of thedrive details table.


Using the Summary view to monitor drivesThis view is displayed when you select Monitor>Devices>Drives and then selectSummary View from the drop-down list. The drop-down list is located at thetop-right corner of the page.

The Summary view contains the following section:

Viewing the Drive Summary by Status section

Viewing the Drive Summary by Status sectionThe Drive Summary by Status section shows an overall distribution of drives bydrive status for the current View pane selection. This information is shown in apie chart as well as a table.

Note: For 7.0.1 master servers, the Drive Summary by Status section does notshow the drives that are disabled or unreachable.

Each color of the pie chart represents how drives are distributed in yourenvironment as per the drive status. You can also view the color code summaryin this section to know the colors that represent different exit status. Pointing onthe pie chart shows the number and percentage of drives with up or down statusin your NetBackup environment. For example, pointing on the green color in thepie chart shows that 5 drives or 100% drives in your environment are up.

Note: The Drive Summary by Status section can also be viewed from Monitor >Overview.

You can drill down from this section to see details of the drives that are up ordown.


452

To view drives by drive status


2 In the Drive Summary by Status section, do either of the following:

■ Click the number of drives (link) for a particular drive status from thetable. For example, click the number for Up drivesOr

■ Click a colored section of the pie chart that corresponds to a particulardrive status. For example, click on the green section of the pie chart toview details for the drives that are up.

Monitoring NetBackup disk poolsThis view is displayed when you select Monitor>Devices>DiskPools. This viewdisplays detailed information about the disk pools that are configured for use byNetBackup. The data that is shown in this view is based on the current View paneselection.



Name of the disk poolName

The storage server type. For OpenStorage,the server type depends on the vendor name.

Server Type

Number of disk volumes in the disk pool.Number of Volumes

The amount of storage space in use.Used Capacity

The total raw, unformatted size of thestorage in the disk pool.

Raw Size

The estimated amount of disk space availablefor storage after file metadata overhead istaken into account.

Usable Size

The low water mark for the disk pool. (Thedefault is 80%.) When the capacity of thedisk pool returns to the low water mark,NetBackup again assigns jobs to the storageunit.

Low Watermark (%)



■ High Water Mark (%)

■ Master Server

■ State

■ Imported




You can perform the following task from this view:

See “Viewing the details for a single diskpool” on page 454.

View the details for a single disk pool

Viewing the details for a single disk poolAll the details that are associated with a disk pool can be viewed from the Detailspane. The Details pane is located at the bottom of the view.

To view the details for a single disk pool

1 In the OpsCenter console, select Monitor > Devices > Disk Pools.

2 Click the drilldown link from the Name column. The disk pool informationcan be viewed from the General and Disk Volume tab of the Details pane.From the General tab, you can also click the master server link to see detailsabout the master server that is associated with the disk pool.

Monitoring NetBackup hostsThis view is displayed when you select Monitor > Hosts.

This view contains the following subtabs:

This tab is shown by default when you selectMonitor > Hosts.

This view displays detailed informationabout NetBackup master servers based onthe current View pane selection.

See “Monitoring NetBackup master servers”on page 455.

Master Server

Monitoring NetBackup using Symantec OpsCenterMonitoring NetBackup hosts

454

This view displays detailed informationabout NetBackup media servers based on thecurrent View pane selection.

See “Monitoring NetBackup media servers”on page 456.

Media Server

This view displays detailed informationabout NetBackup clients based on thecurrent View pane selection.

See “Monitoring NetBackup clients”on page 457.

Client

Monitoring NetBackup master serversThis view shows details of master servers. The data that is shown in this view isbased on the current View pane selection.



Fully qualified domain name or IP addressof the master server that is configured.

Network Name

The display name that you have chosen forthe master server.

Display Name

Operating system of the master server.Operating System

Back up product from where the data is beingcollected like PureDisk, Backup Exec etc.

Product

The last time when OpsCenter successfullyinitiated contact with the master server. Thisdoes not necessarily represent the last timethat OpsCenter collected information fromthe master server.

Last Contact

Shows the current state of the master serverlike Connected, Not Connected etc.

State


See “Filtering by NetBackup master servertype and status” on page 456.

Use filters to view specific master servers

455Monitoring NetBackup using Symantec OpsCenterMonitoring NetBackup hosts

Filtering by NetBackup master server type and statusYou can sort and filter this view to focus on the specific type of master serversthat you want to see. For example, you can apply a filter that displays Windowsservers only. These filters are available from the drop-down list which is presenton top of the table.


Select this filter to view details of all masterservers.

All Servers (default filter)

Select this filter to view details of thosemaster servers that are connected.

Connected Servers

Select this filter to view details of thosemaster servers that are partially connected.

Partially Connected Servers

Select this filter to view details of thosemaster servers that appear as not connected.

Not Connected Servers

Select this filter to view details of Windowsservers.

Windows Servers

Select this filter to view details of Solarisservers.

Solaris Servers

Select this filter to view details of Linuxservers.

Linux Servers

Select this filter to view details of all otherservers like AIX servers, HP-UX servers etc.

Other Servers



Use the following procedure to view details by type of master server.

To view details by type of master server

1 In the OpsCenter console, select Monitor > Hosts > Master Server.


Monitoring NetBackup media serversThis view shows details of media servers. The data that is shown in this view isbased on the current View pane selection.

Monitoring NetBackup using Symantec OpsCenterMonitoring NetBackup hosts

456



Name of the media server.Name

Name of the master server that is associatedwith the media server.

Master Server


See “Viewing the details of a master serverthat is associated with a media server”on page 457.

View the details of a master server that isassociated with a media server

Viewing the details of a master server that is associated witha media serverUse the following procedure to view the details of a master server that is associatedwith a media server.

To view the details of a master server that is associated with a media server

1 In the OpsCenter console, select Monitor > Hosts > Media Servers.

2 Click the drilldown link from the Master Server column.

Monitoring NetBackup clientsThis view shows details of NetBackup clients. The data that is shown in this viewis based on the current View pane selection.



Name of the client that is to be backed up.Client Name

Name of the master server that is associatedwith the client.

Master Server

Operating system on the client like Linux,HP-UX etc.

OS Type

Hardware of the client machine like PC.Hardware


457Monitoring NetBackup using Symantec OpsCenterMonitoring NetBackup hosts

See “Viewing the details for a single masterserver” on page 458.

View the details for a single master server

Viewing the details for a single master serverAll the details for a master server that is associated with a client can be viewedfrom the General tab.

To view the details for a single master server

1 In the OpsCenter console, select Monitor > Hosts > Client.

2 Click the drilldown link in the Master Server column.

Monitoring NetBackup alertsThe Monitor > Alerts view provides details of NetBackup alerts. The data that isshown in this view is based on the current View pane and timeframe selection.Data for the last 24 hours is shown by default. You can also view data for the last48 hours or 72 hours.


Note:The OpsCenter console displays active alerts by default (these are the alertsthat have not been cleared).

You can use the following views to see NetBackup alert information:

The List View is shown by default when youselect Monitor>Alerts. The List View showsactive alerts by default. This view also letsyou view detailed information about allNetBackup alerts and also filter, respond toalerts.

See “Using the List View for monitoringNetBackup alerts” on page 459.

List View

Monitoring NetBackup using Symantec OpsCenterMonitoring NetBackup alerts

458

The Summary View only displays activealerts (these are the alerts that have not beencleared). The Summary View shows howactive alerts are distributed in yourenvironment as per the alert severity. Thisinformation is shown in a pie chart as wellas a table.

See “Using the Summary View formonitoring NetBackup alerts” on page 464.

Summary View

Using the List View for monitoring NetBackup alertsThe List view is displayed when you select Monitor > Alerts. This view containsdetailed information for alerts. This view provides tools to view and filter alerts,and to track user responses to alerts. The data that is shown in this view is basedon the current View pane and timeframe selection. Data for the last 24 hours isshown by default. You can also view data for the last 48 hours or 72 hours.


Note:The List View displays active alerts by default (these are the alerts that havenot been cleared).


Unique ID associated with each NetBackupalert.

Alert ID

The severity of the alert. The severity typehelps you determine how quickly you wantto respond.

Severity

Name of the policy that is associated withthe alert.

Alert Policy

The alert condition that is used for the alert.Alert Condition

Current status of the alert like Active,Cleared etc.

Status

Name of the individual to whom the alerthas been assigned.

Assigned To

Time, date, and year when the alert wasraised.

Time Raised

459Monitoring NetBackup using Symantec OpsCenterMonitoring NetBackup alerts

Time, date, and year when the alert wasmodified.

Last Update Time

Name of the individual who last modifiedthe alert.

Updated by

Not all of the available columns appear initially in this view. The AssignmentState column does not appear, but can be added to your view by clicking the TableSettings icon.




See “Viewing the details for a single alert”on page 460.

View the details for a single alert

See “Viewing the details of the alert policyassociated with an alert” on page 460.

View the details of an alert policy that isassociated with the alert

See “Filtering by alert type” on page 461.Use filters to view specific alerts

See “Responding to alerts ” on page 462.Respond to alerts

Viewing the details for a single alertAll the details that are associated with an alert can be viewed from the Detailspane. The Details pane is located at the bottom of the view.

To view the details of a single alert

1 In the OpsCenter console, select Monitor > Alerts.

2 Click a drill-down link from the Alert ID column. The alert details are shownunder General and Comments tabs of the Details pane. In addition to theinformation that is shown in the table, the General tab also shows masterserver, policy name, job ID, and exit status information. The Comments tabshows comments on the alert (if any), the time these comments were givenand the individual who last updated the alert.

Viewing the details of the alert policy associated with an alertUse the following procedure to view the details of the alert policy that is associatedwith an alert.


460

To view the details of alert policy associated with the alert


2 Click the drill-down link from the Alert Policy column.

Filtering by alert typeSince the Monitor > Alerts view can include large numbers of alerts, a filter isavailable. You can use this filter to limit the types of alerts that appear.

You can filter on various severity levels or status settings, which lets you focuson only the specific alerts that interest you. For example, you can create and applya filter that only displays the alerts that are acknowledged.

You can filter using any of the following nine built-in alert filters. These filtersare available from the drop-down list which is present on top of the alert detailstable.

Select this filter to view Active alerts. This does not includethe alerts that have been cleared.

Active (default filter)

Select this filter to only view the alerts whose severity isCritical.

Critical

Select this filter to only view the alerts whose severity isMajor.

Major

Select this filter to only view the alerts whose severity isWarning.

Warning

Select this filter to only view the alerts whose severity isInformational.

Informational

Select this filter to only view the alerts that have not beenassigned to anybody.

Unassigned

Select this filter to only view the alerts that have beenassigned to other OpsCenter users.

Assigned

Select this filter to only view the alerts that have beenacknowledged by an OpsCenter user.

Acknowledged

Select this filter to only view the alerts that have beencleared.

More information on cleared alerts is available.

See “Responding to alerts ” on page 462.

Cleared


Select this filter to view the details of all alerts. This includesboth active and cleared alerts.

All Alerts



Use the following procedure to view details by type of alerts.

To view details by type of alert


2 Select a filter using the Filter drop-down list. For example, select All Alertsto view details of both active and cleared alerts.

Responding to alertsYou can manage OpsCenter alerts from the Monitor > Alerts view by addingcomments or by assigning the alert to an individual for further review. You canalso clear or acknowledge an alert. OpsCenter allows multiple users to process ortake action on an alert.

When you acknowledge an alert, you inform other users who see the alert thataction on the alert occurred. If you clear an alert, you cannot perform any furtheractivity on the alert (for example, assign or acknowledge). Cleared alerts do notappear in the alert view by default.

Note:Under certain circumstances there may be issues among multiple OpsCenterusers. For instance, an OpsCenter user comments on an alert while anotherOpsCenter user tries to clear the same alert.

The OpsCenter console displays active alerts by default (these are the alerts thathave not been cleared). Some alerts (for example, Drive is Down) are clearedautomatically when the condition is resolved.

You can view cleared alerts from Monitor > Alerts view (List View) by using theCleared or All Alerts filter.

See “Filtering by alert type” on page 461.

The following alerts are cleared automatically when the condition is resolved:

■ Drive is Down

■ Lost Contact with Media Server

■ Service Stopped

■ Agent Server Communication Break


462

■ Master Server Unreachable

■ Frozen Media

■ Suspended Media

■ Disk Pool Full

■ Disk Volume Down

■ License Capacity

■ Symantec ThreatCon

■ High Down Drives

■ High Frozen Media

■ High Suspended Media

■ Low Available Media

■ No Cleaning Tape

■ Low Disk Volume Capacity

■ Catalog Space Low

■ Catalog not backed up

■ Catalog backup disabled

Note: You can also purge NetBackup alert data from Settings > Configuration >DataPurge in the OpsCenter console based on a retention period that you specify.Any purged data is deleted permanently. This option is useful if you see OpsCenterperformance degrade when there is a high number of alerts in the OpsCenterdatabase.

See “Configuring data purge settings” on page 301.

To acknowledge an alert


2 Select an alert from the table.

3 Click Acknowledge or Clear.


To add a comment for an alert



3 Click AddComment. You can add a comment as a reminder to yourself or forother users.

To clear an alert



3 Click More and then select Clear from the drop-down list.

To assign an alert to an individual



3 Click Assign.

You can assign an alert to a user for their action or information.

4 Select a user to whom you want to assign the alert.

5 Click OK.

To change the policy that is associated with an alert



The Alert Policy Wizard is also used to create a policy.

3 Click More and then select Edit Policy from the drop-down list.

See “Understanding alert counts in the Monitor view” on page 484.

Using the Summary View for monitoring NetBackup alertsThe Summary View gives an overall summary of alerts by severity. It containsthe Alert Summary by Severity section which shows an overall distribution ofalerts by severity for the current View pane and timeframe selection. Thisinformation is shown in a pie chart as well as a table. Data for the last 24 hoursis shown by default. You can also view data for the last 48 hours or 72 hours.


A pie chart with different colors represents the alert distribution by severity inthis section. Each color of the pie chart represents how alerts are distributed in


464

your environment as per the alert severity. You can also view the color codesummary in this section to know the colors that represent different severity.

Note: The Summary View only displays active alerts (these are the alerts thathave not been cleared).

Pointing on the pie chart gives the number and percentage of alerts with aparticular severity in your NetBackup environment. For example, pointing on thegreen color in the pie chart shows that in the last 24 hours, 200 alerts, or 17%alerts in your environment are critical.

Note: The Alert Summary by Severity section can also be viewed from Monitor >Overview.

You can drill down from this section to see details for alert categories.

To view alerts by severity


2 Select SummaryView from the drop-down list. The drop-down list is locatedat the top-right corner of the page.

3 In the Alert Summary by Severity section, do either of the following:

■ Click the number of alerts (link) for a particular alert severity from thetable. For example, click on the number that is shown for Critical alerts.Or

■ Click a colored section of the pie chart that corresponds to a particularalert severity. For example, click on the red section of the pie chart to viewdetails for critical alerts.

See “Understanding alert counts in the Monitor view” on page 484.



466

Managing NetBackup usingSymantec OpsCenter


■ About the Manage views

■ Controlling the scope of Manage views

■ Managing alert policies

■ Managing NetBackup storage

■ Managing NetBackup devices

About the Manage viewsFrom the Manage tab and associated subtabs, you can view and manage yourNetBackup environment, which also include OpsCenter alert policies, storage,and devices.

The OpsCenter server collects data from NetBackup master servers, stores it in adatabase, and displays it on demand. Most of the data is sent by NetBackup andappears almost instantaneously after it changes. (Network, system delays, orbrowser refresh settings can affect how quickly it appears). This data is collectedmainly using notifications. For most operations and changes in NetBackup, NBSLsends a notification to OpsCenter.

See “How OpsCenter collects data from NetBackup” on page 348.

9Chapter

Controlling the scope of Manage viewsThe content that is shown in the Manage views is based on your current Viewpane selection.

You can select the following default option from the View pane:

Select ALL MASTER SERVERS to viewinformation for all the NetBackup servers inyour environment.

ALL MASTER SERVERS

In addition to using the default view i.e. ALL MASTER SERVERS, you can alsocreate your own views from Settings > Views or by using Java View Builder. Forexample, you can create a view like Geography to view details about master serversin a particular region like Europe.

More information about how to create views using Settings > Views is available.



Use the following procedure to view details of all master servers or specific masterservers.

To view details of all master servers

◆ In the OpsCenter console, select ALLMASTERSERVERS from the drop-downlist in the View pane.

To view details of specific master servers

1 In the OpsCenter console, select ALLMASTERSERVERS from the drop-downlist in the View pane.

2 Deselect the checkbox next to ALL MASTER SERVERS and select specificmaster servers from the list of master servers. Ensure that other masterservers are unchecked.

3 Click Apply Selection.

Managing alert policiesThis view is displayed when you select Manage>AlertPolicies. This view displaysdetailed information for OpsCenter alert policies for the current View paneselection.

See “Controlling the scope of Manage views” on page 468.

Managing NetBackup using Symantec OpsCenterControlling the scope of Manage views

468


This column lists the name of the alertpolicy. Click the link to view details aboutthe policy.

Name

This column lists the description for the alertpolicy.

Description

This column lists the alert condition that isused for the alert policy. Example: Hung Job,Job Finalized, High Frozen Media etc.

See “About alert conditions” on page 472.

Alert Condition

This column determines whether the alertpolicy is enabled or not.

Enabled

This column lists the severity that isassociated with the alert policy.

Severity

This column lists the severity of the emailor trap that is sent when the alert is cleared.

Clear Severity

This column lists the date and time whenthe alert policy was created.

Creation Time

This column lists the date and time whenthe alert policy was last modified.

Modification Time

This column lists the OpsCenter user wholast modified the alert policy.

Modified By

Table 9-1 lists the topics that describe how to manage alert policies.

Table 9-1 Topic contents and description

DescriptionTopic

Explains the concept of alert policies. Alsoexplains the License Capacity alert policy.

See “About OpsCenter alert policies”on page 470.

Explains how to view the details for an alertpolicy.

See “Viewing the details for a single alertpolicy” on page 471.

Explains how to filter and view the alertpolicies that are of interest to you.

See “Filtering on type of alert policy”on page 471.

Explains how to create an alert policy usingthe Alert Policy Wizard.

See “Creating (or changing) an alert policy”on page 472.

469Managing NetBackup using Symantec OpsCenterManaging alert policies

Table 9-1 Topic contents and description (continued)

DescriptionTopic

Explains the tasks that are available formanaging a single alert policy. This includestasks like editing, copying, deleting,activating, or deactivating an alert policy.

See “Managing an alert policy ” on page 485.

Explains how you can view the alerts thatare associated with an alert policy.

See “Viewing the alerts associated with analert policy” on page 486.

About OpsCenter alert policiesOpsCenter provides tools to create and manage alert policies and handle anyresulting alerts that the policies generate. Alert policies help you manage yourNetBackup environment by providing constant monitoring of your NetBackupsystems. When certain events or conditions occur in your environment, OpsCenterhelps you manage your NetBackup server network by generating alerts or sendingemail and trap notifications (or both).

When a NetBackup system event triggers an alert (based on your alert policies),the following occurs:

■ OpsCenter sends email or SNMP notices to any recipients that are configuredin the policy.

■ The OpsCenter console displays views to help you track and manage thesealerts.

You can specify email or SNMP notification in response to an alert, which letsadministrators focus on other job responsibilities. Administrators do not need tomonitor a terminal continuously.

Alert policies are defined as informational, warning, major, or critical.

Under certain circumstances there may be issues among multiple OpsCenterusers. For instance, an OpsCenter user changes a policy while another user triesto remove the same policy.

About the License Capacity alert policyOpsCenter contains an internal predefined alert policy that is called the LicenseCapacity Alert. The License Capacity alert is generated for a capacity-based licensedNetBackup feature if the used capacity exceeds the licensed capacity. This alertis automatically cleared for the licensed feature if the used capacity is less thanlicensed capacity. If an alert is generated for a licensed feature and the alert hasnot been cleared for 7 days (i.e. the used capacity is more than the licensed capacity

Managing NetBackup using Symantec OpsCenterManaging alert policies

470

for seven days after the alert is generated), a new alert is generated and the oldalert is cleared automatically.

The License Capacity alert is an informational alert. It is internal to OpsCenterand cannot be modified. However, you can disable (or enable) the License Capacityalert policy if you do not want to receive these alerts.

See “Managing an alert policy ” on page 485.

Note: The License Capacity alert is not generated for the capacity-based licensesfor OpenStorage Disk option, PureDisk Storage option, and Virtual Tape option.All capacity values for this alert are calculated based on the definition that 1terabyte=1,099,511,627,776 bytes.

Viewing the details for a single alert policyAll the details that are associated with an alert policy can be viewed from thebottom of the Manage > Alert Policies view under the General tab. The Generaltab displays all the details that are shown in the table.

To view the details of a single alert

1 In the OpsCenter console, select Manage > Alert Policies.

2 Click a drill-down link from the Name column. The alert policy details areshown at the bottom of this view under the General tab.

Filtering on type of alert policyA filter is available in the Manage > Alert Policies view to limit the types of alertpolicies that appear.

You can filter using any of the following three built-in filters. These filters areavailable from the drop-down list which is present on top of the table.

Select this filter to view all alert policies.All Alert Policies

Select this filter to view the alert policiesthat are enabled.

Enabled Alert Policies

Select this filter to view the alert policiesthat are disabled.

Disabled Alert Policies

You can also create your own filters which let you focus on only the specific alertpolicies that interest you.



To view details by type of alert policy



Creating (or changing) an alert policyYou can create alert policies to detect when something goes wrong with NetBackupand troubleshoot it. You can create policies to automate responses to key eventsin your enterprise. For example, you can create a policy to alert you when a jobfails on a specific master server. You can monitor for frozen media and email theoperator when the number of frozen media exceeds a threshold value. You canthen take corrective action.

OpsCenter periodically retrieves data from NetBackup based on notifications anda wait time (of up to 15 minutes). This time delay between the NetBackup ActivityMonitor and the OpsCenter console can mean that many intermediate job statesmay be lost.

About alert conditionsOpsCenter comes with a set of predefined alert conditions. You can create alertpolicies based on these alert conditions to detect when something goes wrong inyour NetBackup environment and troubleshoot NetBackup. The alerts help youto anticipate and handle problems before they occur. You can receive these alertsby logging on to OpsCenter, and also by email or SNMP traps. You can specifyemail and SNMP recipients while creating an alert policy.

Alert conditions can be divided into the following categories:

For these alert conditions, OpsCenterretrieves data from NetBackup based onnotifications from NBSL.

Event-based alert conditions

For these alert conditions, OpsCenterretrieves data from NetBackup based on await time (of up to 15 minutes).

Periodic alert conditions

Table 9-2 lists the alert conditions, alert category, and descriptions.


472

Table 9-2 Alert conditions in OpsCenter

DescriptionAlertCategory

Alert conditionAlertType

An alert is generated when the job failure ratebecomes more than the specified rate.

Event-basedHigh job failurerate

Job

PeriodicHung job


Table 9-2 Alert conditions in OpsCenter (continued)



An alert is generated when a job hangs (runsfor more than the specified time) for a selectedpolicy or a client for a specified period. TheHung Job condition is checked every 15minutes. Depending upon when a job startswithin a check cycle, an alert may not occur.

For Hung Job alert, you can configureOpsCenter to ignore the time for which a jobis in a queued state. While checking the HungJob condition, OpsCenter considers the starttime of a job by default. This also includes thetime for which a job is in a queued state. A jobmay not always be in an active state after itstarts. Due to unavailability of resources, a jobmay first be in a queued state before it becomesactive.

If you configure OpsCenter to ignore thequeued time for a job, OpsCenter considers thetime when a job becomes active while checkingthe Hung Job condition. Note that the activestart time of the first attempt is considered.

For example, suppose a policy is created witha job threshold of 25 minutes. A job starts 10minutes after a first check cycle and ends 13minutes after the third check cycle is done.This is a total execution of 33 (5 + 15 + 13)minutes, but an alert is not raised.

In this case, the policy is checked four times.The job was not yet started during the firstcheck, was running less than the thresholdduring the second (job duration = 5 minutes)and third checks (job duration = 20 minutes),and the job completes (job duration = 33)before the fourth check.

If a job starts at 4 minutes after a first check,an alert is raised at the third check, since thejob has executed for 26 minutes (11 + 15minutes).

Events-basedJob finalized


474




An alert is generated when a job of specifiedtype, of the specified policy or client ended inthe specified status.

An alert is generated when a job of a specifiedtype of the specified policy/client moves to anIncomplete state.

Events-basedIncomplete Job

An alert is generated when any of the selectedmedia is frozen.

Events-basedFrozen mediaMedia

An alert is generated when any of the selectedmedia is suspended.

Events-basedSuspended media

An alert is generated when a media exceedsthe threshold number of mounts.

Events-basedExceeded maxmedia mounts

An alert is generated when a restore operationrequires media. The restore operation mayrequire a specific media which contains thespecific image to be restored.

Events-basedMedia requiredfor restore

An alert is generated when the number ofavailable media becomes less than thepredefined threshold value.

PeriodicLow availablemedia

An alert is generated when the percentage ofsuspended media exceeds the predefinedthreshold value.

PeriodicHigh suspendedmedia

An alert is generated when the percentage offrozen media exceeds the predefined thresholdvalue.

PeriodicHigh frozenmedia





An alert is generated when space available forcatalogs becomes less than the threshold valueor size. For Catalog Space low condition, youcan specify the threshold value for a particularpolicy in percentage, bytes, kilobytes (KB),megabytes (MB), gigabytes (GB), terabytes (TB)or petabytes (PB) and generate alerts. Thegenerated alert can also show available catalogspace using these units.

PeriodicCatalog Space lowCatalog

An alert is generated when catalog backup doesnot take place for a predefined time period.

This does not necessarily mean that if you donot receive this alert, the catalog backup wassuccessful.

PeriodicCatalog notBacked up

An alert is generated when all the catalogbackup policies are disabled. If the policy hasbeen defined for a server group, an alert isgenerated for every master server within thegroup that satisfies this criteria. The alert isnot generated if no catalog backup policy existsfor a master server.

PeriodicCatalog BackupDisabled

An alert is generated on a media mountrequest.

Events-basedMount RequestTape

An alert is generated when no cleaning tapesare left.

PeriodicNo Cleaning Tape

An alert is generated when a cleaning tape haszero cleaning left.

Events-basedZero CleaningLeft


476




An alert is generated when a disk pool(s)reaches the high water mark. An alert policybased on Disk Pool Full condition generates analert only when the used capacity of the diskpool reaches the high water mark.

Events-basedDisk Pool FullDisk.

An alert is generated when the selected diskvolume(s) is down.

Events-basedDisk VolumeDown

An alert is generated when a disk volumecapacity is running below the threshold limit.

PeriodicLow Disk VolumeCapacity

An alert is generated when a drive in aspecified robot or media server in the selectedserver context goes down.

Events-basedDrive is Down

An alert is generated when the percentage ofdown drives exceeds the predefined thresholdvalue.

PeriodicHigh Down Drives





An alert is generated when the communicationbetween Agent and OpsCenter Server breaks.By default, this alert is automatically clearedwhen the communication is re-established.

PeriodicAgent ServerCommunicationbreak

Host

An alert is generated when OpsCenter losescontact with the master server. This alertcondition means that the connection betweenOpsCenter and the managed NetBackup masterserver is lost. It does not necessarily mean thatNetBackup backups are not working.

Events-basedMaster ServerUnreachable

An alert is generated when OpsCenter losescontact with the media server.

Events-basedLost Contact withMedia Server

An alert is generated when the selected servicestops on any of the selected servers in theselected view.

Events-basedService Stopped

An alert is generated when the SymantecThreatCon level is equal to or more than thethreshold level that you specify. To create thealert policy, select the Symantec ThreatConalert condition and then specify the thresholdThreatCon rating.

The Symantec ThreatCon alerts are clearedautomatically when the ThreatCon levelbecomes less than the threshold level that youhave specified. For example, if you havecreated an alert policy that alerts you whenthe Symantec ThreatCon level becomes 3, thenthe alert is cleared automatically once theThreatCon level becomes 2 or less.

Events-basedSymantecThreatCon

Events-basedJob Policy Change


478




An alert is generated when a policy attributefor a job policy is changed. Multiple alerts aregenerated if multiple attributes are changedfor a job policy

See “Additional information on Job PolicyChange condition” on page 479.

If you select a particular job policy, only theselected job policy is monitored for change. Ifyou do not select any job policy, all the jobpolicies are monitored for changes.

Additional information on Job Policy Change condition

Review the following text for Job Policy Change alert condition.

Only the following policy attributes are monitored for job policies:

Policy client typePolicy name

CheckpointCheckpoint interval

Backup network drivesEffective date

EncryptionCompression

OffhostBlock level incrementals

Snapshot argumentsSnapshot method

Client nameMaster server

Collect true image restore infoCollect bmr info

Ext sec infoFail on error

Keyword phraseFrozen image

Off host backupNumber of copies

CatalogResidence

ClientsSchedules

Volume poolStorage unit


PriorityJobs/Policy

True image recoveryCross mount points

Keyword phraseAllow multiple data streams

Data moverAlternate client

StatusIndividual file restore from raw

Backup copyBlock increment

Disaster recoveryData mover type

Follows nfs mountsFile list

Max jobs per policyMax fragmentation size

Proxy clientPfi enabled

Share groupData classification name

Policy active

Adding an alert policyFollow the screens of the Alert Policy Wizard to define an alert policy. Therequired information and the required number of screens vary depending on thealert condition you choose. For some alert conditions, you can skip the optionalscreens.

Note: The Alert Policy Wizard is also used when you edit an alert policy.

To add an alert policy


2 Click Add. The Alert Policy Wizard appears.


480

3 Enter the following details in the Alert Policy Wizard :

Enter a name for the alert policy. Thename must be unique.

This is a required field.

Name

Enter a description for the alert policy.Description

Select an alert condition from the list ofalert conditions that are available.


Alert Condition

Click Next to continue. You may click Cancel to exit the Wizard at any stage.

4 Specify attributes for the alert condition that you selected. The attributesdiffer for each alert condition. For many alert conditions (for example, forthe Job Finalized condition), you may need to enter threshold attributes andother required or optional attributes. These attributes define and limit thealert.

Click Next.

5 Select the view that should be verified for the alert condition. You can selecta view and a node that contains a group of master servers and also specificobjects. For example, you can select the default view ALLMASTERSERVERSto be checked for the alert condition. When you select a view like ALLMASTERSERVERS or a node that contains a group of master servers, all themaster servers that are currently in the view or node are automaticallyselected. In addition, master servers that you may add later to this view ornode will also be automatically selected and hence verified for the alertcondition.

You may also select only specific objects of a particular view or node to bechecked for the alert condition. For example, you may select only a specificmaster server(s) under the default view ALLMASTERSERVERS to be checkedfor the alert condition. To select a specific master server, first deselect theview or node that contains the master server and then select the masterserver.

You may also deselect a specific master server from a view by selecting theview and then deselecting the specific master server. Consider a scenariowhere there are two objects server A and server B in a particular view likeALL MASTER SERVERS. In case, you have selected the ALL MASTERSERVERS view and then specifically deselected server B , and in additionif you have selected a view or node that also contains server B, server B

will not be verified for the alert condition even though it is a part of the


selected view or node. This is because you have specifically deselected server

B from the ALL MASTER SERVER view. When you specifically deselect amaster server from a view, which is also part of another selected view, thedeselection or exclusion is given a higher priority because of which the masterserver is not verified for the alert condition. For this reason, it is recommendedthat you do not repeat a master server across groups.

Note that you can also view and select additional attributes like policies,clients, media servers etc. on expanding the views and nodes from this page(wherever applicable). These attributes are located under the applicable viewsor nodes for specific alert conditions. For example, for the Job Finalized alertcondition, you can select the view as well as the specific policies and clientsthat should be checked for the alert.

You can view the applicable attributes like policy name, client name, mediaserver name, robot number, drive IDs etc. for the following alert conditions:

■ Job Finalized

■ Drive is Down

■ Media Required for Restore

■ Service Stopped

■ Frozen Media

■ Suspended Media

■ Exceeded Max Media Mounts

■ Disk Group Full

■ Disk Volume Down

■ Job Policy Changed

■ Hung Job

Note: This page is not shown if you have selected the Symantec ThreatConalert condition. This is because the Symantec ThreatCon alert condition doesnot depend on any views or master servers.

You must select at least one object, node, or view from this page. Click Nextto continue.

6 Optionally in the Email Recipients and Trap Recipients sections, you canselect email or SNMP recipients (or both) to receive the alert notification.

See “Adding email recipients” on page 483.


482

See “Adding SNMP trap recipients” on page 484.

Note that if you create an alert policy and do not define any recipients, thealert is still displayed in the Monitor > Alerts view.

In the Severity section, do the following:

■ Select a severity level from the AlertSeverity drop-down list. (If this alertoccurs, the alert is displayed in the Monitor > Alerts view.)

■ Select an appropriate severity level from the Severity of email/trap sentfor cleared alert drop-down list. With Severity of email/trap sent forcleared alert option, you can configure the severity for an email or trapthat is sent when an alert is cleared. The default severity level isInformational.In OpsCenter, an alert is raised with the severity specified in the alertpolicy. Whenever this alert is cleared, an email or trap informing the userthat the alert is cleared is sent with the same severity that is defined inthe alert policy. This is the default behavior. For example, you may havecreated an alert policy for a Hung Job alert condition with a Criticalseverity. As a result, you receive Hung Job alert with Critical severity.When this Hung Job alert gets cleared, you receive an email or trap thatinforms you that the alert has been cleared. This email or trap also has aCritical severity. You can now configure the severity for this email or trapfrom Critical to some other severity like “Informational” while creatingthe alert policy. Note that you can configure the severity only for emailor trap.

■ The ActivateCondition option is checked by default. This means that bydefault, the policy will be active once you create it. Deselect the ActivateCondition option if you want to deactivate the policy.You can always activate or deactivate the policy later from the OpsCenterconsole.See “Managing an alert policy ” on page 485.

7 Click Save to save the alert policy.

8 Click Finish once the policy is successfully created.

Adding email recipients

While creating an alert policy using the Alert Policy Wizard, go to the Actionsscreen. On the Actions screen, click To, Cc, or Bcc from the Email Recipientssection. In the Add Email Recipients dialog box, select the specific recipientsfrom the Recipient Name column and click To, Cc, or Bcc based on yourrequirements. Click OK


Adding SNMP trap recipients

While creating an alert policy using the Alert Policy Wizard, go to the Actionsscreen. On the Actions screen, click To from the Trap Recipients section. In theAddTrapRecipients dialog box, select the specific recipients from the RecipientName column and click To. Click OK

Understanding alert counts in the Monitor viewAlerts apply only to the object (master server) where the corresponding alertpolicy is created. When alerts are raised for that policy they are raised on theselected object. For example, a Frozen Media alert occurs when any of the selectedmedia on the selected master server (object) are frozen. Consider a case whereyou create an alert policy for a selected view that contains two master servers.For creating the policy, you select an alert condition of type of Frozen Media.Since this master server is present in the view, the alert is listed when you selectthe specific server as well as the specific view from the View Pane.

But some types of alerts, for example High Job Failure Rate apply across groups.In this case, jobs from all of the master servers in the selected group are used tocalculate the job failure rate. The alert does not apply to a single master serverin the group but applies to the server group on which the alert policy was created.This means that only one alert is raised for the group if the job failure rate for theservers in the selected group is more than a user-defined threshold. An alert isnot generated for every master server that is a part of the group. Therefore, thealert is listed only when you select the server group on which alert policy is created(or a parent group of that group).

If you create this type of alert policy for a single managed server, the alert is raisedon the server since the server is the selected object. The alert can also be viewedif all the nodes or views that contain the master server are selected.

The following OpsCenter alert policy conditions apply across groups:

■ High Down Drives

■ High Frozen Media

■ High Job Failure Rate

■ High Suspended Media

■ Low Disk Volume Capacity

■ Low Available Media


484

Managing an alert policyUse the following procedure to edit, delete, copy, activate, or deactivate an alertpolicy. You can copy and use an alert policy on another managed master server.The copy of the alert policy is available in the alert policy details table where youcan make changes to it.

To edit an alert policy


2 Select an alert policy from the Name column in the table.

3 Click Edit.

The Alert Policy Wizard is used to create or edit a policy. When you edit analert policy, the alert condition specific to the policy is selected by default inthe Alert Policy Wizard. You cannot select a different alert condition whileediting an alert policy.

See “Adding an alert policy” on page 480.

To delete an alert policy



3 Click Delete.

To copy an alert policy



3 Click More and then click Copy from the drop-down list.

4 In the Copy Alert Policy dialog box, enter the new name for the alert policy.

5 Click OK.

The copy of the alert policy is available in the alert policy details table whereyou can make changes to it.

To enable or disable an alert policy



3 Click More and then click Enable or Disable from the drop-down list.


Viewing the alerts associated with an alert policyUse the following procedure to view the alerts that are associated with an alertpolicy.

To view the alerts associated with an alert policy



3 Click More and then select View Alerts from the drop-down list.

Managing NetBackup storageThis view is displayed when you select Manage > Storage. Included in this vieware subtabs for Storage Unit, Storage Unit Group, and Storage Lifecycle Policy.Using these subtabs you can view detailed information about NetBackup storagefor the current View pane selection.


Table 9-3 lists the topics on how to manage NetBackup storage.

Table 9-3 Topic contents and descriptions

DescriptionTopic

Explains the capabilities that are availableusing the Manage > Storage > Storage Unitview.

See “Managing Storage Units” on page 486.

Explains the capabilities that are availableusing the Manage > Storage > Storage UnitGroup view.

See “Managing Storage Unit Groups”on page 488.

Explains the capabilities that are availableusing the Manage > Storage > StorageLifecycle Policy view.

See “Managing storage lifecycle policy”on page 489.

Managing Storage UnitsThis view is displayed when you select Manage > Storage > Storage Unit. Thisview shows the details for a storage unit for the current View pane selection.There is one row in the table for each storage unit for the current selection in theView pane.


Managing NetBackup using Symantec OpsCenterManaging NetBackup storage

486


This column lists the name of the storageunit. Click the link to view details about thestorage unit.

Name

This column specifies the type of robot (ifany) that the storage unit contains.

Robot Type

This column specifies a unique, logicalidentification number for the robotic library.

Robot Number

This column lists the density of the storageunit.

Density

This column specifies whether the storageunit is available exclusively on demand. Thishappens only when a policy or schedule isexplicitly configured to use this storage unit..

On Demand

This column specifies the absolute path to afile system or a volume available for diskbackups.

Path


■ Storage Unit Type

■ Capacity

■ Free Space

■ High Water Mark

■ Max. Concurrent Jobs

■ Staging

■ Low Water Mark

■ Can Exist On Root

■ NDMP Host

■ Enable Block Sharing

■ Transfer Throttle

■ Master Server

■ Last Seen Time

487Managing NetBackup using Symantec OpsCenterManaging NetBackup storage

■ Host

■ Fragment Size

■ Multiplexing

■ Disk Type

■ Time Last Selected

■ Disk Pool

■ Host List




The following task can be performed from this view:

See “Viewing the details for a single storageunit” on page 488.

View the details for a single storage unit

Viewing the details for a single storage unitUse the following procedure to view the details for a single storage unit.

To view details for a single storage unit

1 In the OpsCenter console, select Manage > Storage > Storage Unit.

2 Click a storage unit name (drilldown link) from the Name column in the table.

The storage unit details are shown at the bottom of this view under theGeneral tab. This tab displays many of the available columns of the table.

Managing Storage Unit GroupsThis view is displayed when you select Manage > Storage > Storage Unit Group.This view shows the details for a storage unit group for the current View paneselection. The table contains one row for each storage unit group for the currentselection in the View pane.




488

This column lists the name of the storageunit group. Click the link to view detailsabout the storage unit group.

Name

This column specifies the order that storageunits are selected when they are included ina group. .

Storage Unit Selection

This column specifies the date and timewhen the storage unit group was last seen.

Last Seen Time


See “Viewing the details for a single storageunit group” on page 489.

View the details for a single storage unitgroup

Viewing the details for a single storage unit groupUse the following procedure to view the details for a storage unit group.

The storage unit group details are shown at the bottom of this view under thefollowing tabs:

This tab shows the details of the storage unitgroup that are also shown in the table.

General

This tab shows the details of the storageunits that are a part of the storage unitgroup.

Storage Unit

To view details for a single storage unit group

1 In the OpsCenter console, select Manage > Storage > Storage Unit Group.

2 Click the name of a storage unit group (drilldown link) from the Name columnin the table.

Managing storage lifecycle policyThis view is displayed when you select Manage > Storage > Storage LifecyclePolicy. This view shows the storage lifecycle policy details for the current Viewpane selection. A storage lifecycle consists of one or more storage units. The tablecontains one row for each Storage lifecycle policy for the current selection in theView pane.


489Managing NetBackup using Symantec OpsCenterManaging NetBackup storage


This column lists the name of the storagelifecycle policy. Click the link to view detailsabout the storage lifecycle Policy.

Name

This column lists the data classification thathas been selected for the storage lifecycle,which applies to all of the storage units inthe lifecycle. For example, the data might beclassified as gold or silver.

Data Classification

This column specifies the priority that apolicy has for backup resources. The defaultfor all policies is 0, the lowest prioritypossible. Any policy with a priority greaterthan zero has priority over the defaultsetting. .

Job Priority

This column lists the master server that isassociated with the storage lifecycle Policy.Click the link to view more details about themaster server.

Master Server


See “Viewing the details for a single storagelifecycle policy ” on page 490.

View the details of a single storage lifecyclepolicy

See “Viewing the details for a master serverassociated with a storage lifecycle policy ”on page 491.

View the details of a master server that isassociated with a storage lifecycle policy

Viewing the details for a single storage lifecycle policyUse the following procedure to view the details for a single storage lifecycle Policy.The details are shown at the bottom of this view under the following tabs:

This tab shows the details of the storage unitgroup that are also shown in the table.

General

This tab shows the details of the storagedestinations that are a part of the storagelifecycle policy.

Storage Destinations


490

To view the details for a storage lifecycle policy

1 In the OpsCenter console, select Manage>Storage>StorageLifecyclePolicy.

2 Click the name of a storage lifecycle policy (drilldown link) from the Namecolumn in the table.

Viewing the details for a master server associated with astorage lifecycle policyUse the following procedure to view the details for a master server that isassociated with a storage lifecycle policy. The details are shown on a separatepage.

To view the details for a master server associated with a storage lifecycle Policy

1 In the OpsCenter console, select Manage>Storage>StorageLifecyclePolicy.

2 Click the name of the master server (drilldown link) from the Master Servercolumn in the table.

Managing NetBackup devicesUnder certain circumstances there may be issues among multiple OpsCenter usersmanaging devices. For instance, a user brings a drive down while another usertries to bring up the same drive.

Table 9-4 lists the topics on how to manage NetBackup devices.

Table 9-4 Topic contents and descriptions

DescriptionTopic

Explains the capabilities that are availableusing the Manage > Devices > Drive view.

See “Managing drives” on page 492.

Explains the capabilities that are availableusing the Manage > Devices > Robot view.

See “Managing robots” on page 495.

Explains the capabilities that are availableusing the Manage > Devices > Disk Pool view.

See “Managing disk pools” on page 497.

Explains the capabilities that are availableusing the Manage > Devices > SAN Clientview.

See “Managing SAN clients” on page 499.

Explains the capabilities that are availableusing the Manage > Devices > FT Serverview.

See “Managing Fibre Transport (FT) servers”on page 501.

491Managing NetBackup using Symantec OpsCenterManaging NetBackup devices

Managing drivesThis view is displayed when you select Manage>Devices>Drive. This view showsdetails for the drives that are configured for use by NetBackup for the currentView pane selection. This view shows information about all the drives and alsoincludes disabled or unreachable drives.



This column lists the configured name of thedrive. Click the link to view details about thedrive.

Drive Name

This column lists the name of the device host(media server) where this drive is attached.If multiple drive paths are configured, thiscolumn contains Multiple. If the drive isconfigured as a shared drive (SSO), thiscolumn contains Multiple.

Device Host

This column lists the name of the masterserver that is associated with the drive.

Master Server

This column specifies the type of drive.

Example: hcart2, hcart3, 4MM.

Drive Type

This column specifies the type of robot thatcontains this drive.

Example: TL4, TLD.

Robot Type

This column contains 'Yes' if the path isenabled. The column contains 'No' if the pathis not enabled. If multiple drive paths areconfigured, this column contains 'Multiple'.

Enabled


■ Serial Number

■ Cleaning Frequency

■ Shared


■ Volume Header Path

Managing NetBackup using Symantec OpsCenterManaging NetBackup devices

492

■ ACS

■ LSM

■ Panel

■ Drive

■ Vendor Drive Identifier

■ Robot Number

■ Robot Drive Number

■ Recorded Media ID

■ Assigned Host

■ Control Host Name

■ Evsn

■ Last Clean Time

■ Local Control

■ Mounted Time

■ NDMP

■ Occupy Index

■ Opr Comment

■ Ready

■ Request ID

■ Scan Host

■ VM Host

■ Write Enabled





See “Viewing the details for a single drive”on page 494.

View the details for a single drive


See “Viewing the details for a master serverassociated with a drive” on page 494.

View the details of a master server that isassociated with a drive

See “Filtering on NetBackup drive category”on page 494.

Use filters to view specific drives

Viewing the details for a single driveUse the following procedure to view the details of a single drive.

To view the details for a single drive

1 In the OpsCenter console, select Manage > Devices > Drive.

2 Click the name of the drive (drilldown link) from the Drive Name column inthe table.

Detailed properties and status for the drive are shown at the bottom of theview under the General tab. The Paths tab shows the paths that wereconfigured for the drive.

Viewing the details for amaster server associatedwith a driveUse the following procedure to view the details of a master server that is associatedwith a drive.

To view the details for a master server


2 Click the name of the drive (drilldown link) from the Master Server columnin the table.

Details for the specific master server are shown on a separate page.

Filtering on NetBackup drive categoryYou can sort and filter this view to focus on the specific type of drives that youwant to see. For example, you can apply a filter that displays only those drivesthat are up. You can filter by using any of the built-in filters. These filters areavailable from the drop-down list which is present on top of the table.

The following built-in filters are available:

All Drives is the default filter. Select thisfilter to view all drives.

All Drives


494

Select this filter to view only those drivesthat are up. For up drives, all drive paths areup.

Up Drives

Select this filter to view only those drivesthat are down. For down drives, all drivepaths are down.

Down Drives

Select this filter to view mixed drives. Formixed drives, some drive paths are up andsome drive paths are down.

Mixed Drives



To view details by type of drive



Managing robotsThis view is displayed when you select Manage > Devices > Robot. This viewshows details for the robots that are configured for use by NetBackup for thecurrent View pane selection.



This column contains the name of the robot.The robot name contains the type andnumber of the robot, for example TLD(3).

Click the link to view details about the robot.

Robot Name

This column lists the name of the device hostwhere this robot is attached.

Device Host

This column contains the robot serialnumber.

Serial Number

If the robot is controlled by a remote host,this column contains the name of the hostthat controls the robot.

Robot Control Host


This column lists the master server that isassociated with the robot.

Click the link to view details about themaster server.

Master Server

This column lists the media server that isassociated with the robot.

Click the link to view details about the mediaserver.

Media Server


■ Robot Type

■ Robot Number


■ Last Seen Time

■ Max Drive

■ Max Slot

■ Remote ID

■ VM Host





See “Viewing the details for a single robot”on page 497.

View the details of a robot

See “Viewing the details for a master serverassociated with a robot” on page 497.

View the details for a master server that isassociated with a robot

See “Viewing the details for a media serverassociated with a robot” on page 497.

View the details for a media server that isassociated with a robot


496

Viewing the details for a single robotUse the following procedure to view the details of a single robot.

To view the details for a single robot

1 In the OpsCenter console, select Manage > Devices > Robot.

2 Click the name of the robot (drilldown link) from the RobotName column inthe table.

Detailed properties for the robot are shown at the bottom of the view underthe General tab. The Paths tab shows the paths that were configured for therobot.

Viewing the details for amaster server associatedwith a robotUse the following procedure to view the details of a master server that is associatedwith a robot.

To view the details for a master server associated with a robot



Detailed properties for the master server are shown on a separate page.

Viewing the details for a media server associated with a robotUse the following procedure to view the details of a media server that is associatedwith a robot.

To view the details for a media server associated with a robot


2 Click the name of the media server (drilldown link) from the Media Servercolumn in the table.

Detailed properties for the media server are shown on a separate page.

Managing disk poolsThis view is displayed when you select Manage > Devices > Disk Pool. This viewshows details for the disk pools that are configured for use by NetBackup in thecurrent View pane selection.




This column lists the name of the disk poolName

This column lists the storage server type.For OpenStorage, the server type dependson the vendor name.

Server Type

This column lists the number of diskvolumes in the disk pool.

Number of Volumes

This column lists the amount of storagespace in use.

Used Capacity

This column lists the total raw, unformattedsize of the storage in the disk pool.

Raw Size

This column lists the estimated amount ofdisk space available for storage after filemetadata overhead is taken into account.

Usable Size

This column lists the low water mark for thedisk pool. (The default is 80%.) When thecapacity of the disk pool returns to the lowwater mark, NetBackup again assigns jobsto the storage unit.

Low Watermark (%)


■ High Water Mark (%)

■ Master Server

■ State

■ Imported





See “Viewing the details for a disk pool”on page 499.

View the details for a disk pool


498

Viewing the details for a disk poolUse the following procedure to view the details for a disk pool. The details for thedisk pool are shown at the bottom of the Manage>Devices>DiskPool view underthe following tabs:

This tab shows the detailed properties for adisk pool. Click the master server link to viewdetails about the master server that isassociated with the disk pool.

General

This tab shows details about the diskvolumes that are associated with the diskpool.

Disk Volume

This tab shows details about the storageservers that are associated with the diskpool.

Storage Server

To view the details for a disk pool

1 In the OpsCenter console, select Manage > Devices > Disk Pool.

2 Click the name of the disk pool (drilldown link) from the Name column in thetable.

The details are shown at the bottom of this view.

Managing SAN clientsThis view is displayed when you select Manage>Devices>SANClient. This viewshows details for the SAN clients that are configured for use by NetBackup in thecurrent View pane selection.



This column lists the name of the SAN client.Name

This column lists the state of the FT deviceon the SAN client.

The different states can be active, disabledetc.

State

This column determines when to use the FTmedia server.

Usage Preference


This column lists the number of NetBackupmedia servers that support FT transport andthat the client can send data to or receivedata from.

No. of FT Media Servers

The number of minutes to wait for an FTmedia server for a backup operation.

Backup Wait Period

The number of minutes to wait for an FTmedia server for a restore operation.

Restore Wait Period

This column lists the master server that isassociated with the SAN client.

Master Server

The Version column does not appear, but can be added to your view by clickingthe Table Settings icon.


See “Viewing the details for a SAN client”on page 500.

View the details of a SAN client

See “Viewing the details for a master serverassociated with a SAN client” on page 501.

View the details of a master server that isassociated with a SAN client

Viewing the details for a SAN clientUse the following procedure to view the details of a SAN client. The details forthe SAN Client are shown at the bottom of Manage > Devices > SAN Client viewunder the following tabs:

This tab shows detailed properties and statusfor the SAN client. Click the master serverlink to view details about the master serverthat is associated with the SAN client.

General

This tab shows the FT target devicesinformation for the selected SAN client.

FT device

To view the details for a SAN client

1 In the OpsCenter console, select Manage > Devices > SAN Client.

2 Click the name of the SAN client (drilldown link) from the Name column inthe table.



500

Viewing the details for a master server associated with a SANclientUse the following procedure to view the details of a master server that is associatedwith a SAN client.

To view the details for a master server associated with a SAN client

1 In the OpsCenter console, select Manage > Devices > SAN Client.



Managing Fibre Transport (FT) serversThis view is displayed when you select Manage > Devices > FT Server. This viewshows details for the FT media servers that are configured for use by NetBackupfor the current View pane selection.



This column contains the name of the FTmedia server.

Click the link to view details about the robot.

Name

This column lists the state of the FT mediaserver.

State

This column lists the master server that isassociated with the FT server.

Master Server

This column specifies the number of FTconnections to allow to a media server.

Max Allowed Connections


See “Viewing the details for an FT server ”on page 502.

View the details of an FT server

See “Viewing the details for a master serverassociated with an FT server” on page 502.

View the details for a master server that isassociated with an FT server


Viewing the details for an FT serverUse the following procedure to view the details for an FT server. The details forthe FT server are shown at the bottom of Manage > Devices > FT Server viewunder the following tabs:

This tab shows detailed properties and statusfor the FT server.

General

This tab shows the FT target devicesinformation for the selected FT server.

FT device

To view the details for an FT server

1 In the OpsCenter console, select Manage > Devices > FT Server.

2 Click the name of the Fibre Transport server (drilldown link) from the Namecolumn in the table.


Viewing the details for a master server associated with an FTserverUse the following procedure to view the details of a master server that is associatedwith an FT server.

To view the details for a master server associated with an FT server

1 In the OpsCenter console, select Manage > Devices > FT Server.




502

Guided Recovery


■ About Guided Recovery

■ Setting up for cloning

■ Pre-operation checks

■ Performing a cloning operation

■ Select Master Server screen

■ Select Source Database screen

■ Select Control File Backup screen

■ Destination host and login screen

■ Destination Parameters screen

■ Selection summary screen

■ Pre-clone check screen

■ Job Details screen

■ Post-clone operations

■ Troubleshooting Guided Recovery

About Guided RecoveryThe use of the OpsCenter Web-based user interface to guide a user through theOracle cloning operation offers several benefits:

■ The process is more automated, making the operation easier to perform.

10Chapter

■ OpsCenter retrieves information for you such as databases and control files,shortening the Oracle clone setup time.

■ A validation process increases the rate of successfully completing the cloningoperation.

■ You do not need access to the original database to perform the cloningoperation.

Setting up for cloningThe following items must be done before you perform a Guided Recovery cloningoperation:

■ Oracle uses metadata cataloging, which enables database information to appearin the OpsCenter interface. Ensure that the Oracle metadata parameter in theclient's bp.conf is set at backup time as follows:

ORACLE_METADATA=YES

Or, use the SEND command to set the metadata parameter:

SEND ORACLE_METADATA=YES

■ Oracle uses metadata cataloging, which enables database information to appearin the OpsCenter interface. Use the bpsetconfig command(install_path\NetBackup\bin\admincmd\bpsetconfig) on the server to seta client's configuration. For example:

# bpsetconfig -h myoracleclient ORACLE_METADATA=YES

■ Set up all destination file paths before you run the cloning operation, becausethe operation does not create new file paths during the process. Ensure thatthe user has write access to these paths.

Pre-operation checksCheck the following items before you begin the cloning process:

■ Ensure that the source and destination systems and the source and destinationdatabases are compatible. Examples are Solaris 9 to Solaris 10 and Oracle 11to Oracle 11.

■ The cloning operation does not support offline tablespaces or raw tablespaces.

Guided RecoverySetting up for cloning

504

■ The cloning operation does not support Oracle Automatic Storage Management(ASM).

■ To use a different user or a different group for the clone, you must changewhat the permissions of the backup image are to be at backup time. Add the'BKUP_IMAGE_PERM=ANY' to the send commands during the backup of thesource database.

■ If the destination client is different than the source client, perform an alternaterestore procedure.

■ If the NetBackup client service runs as the Oracle user, then that user needsto be granted the right to "Replace a process level token".

■ On Oracle 9 for Windows, run the Oracle service under the Oracle user account.By default, it runs under the local system. On Oracle 10G systems and later,you can run under the local system.

■ Shut down the source database to successfully complete the operation.Otherwise, an error indicating the database cannot be mounted in exclusivemode appears.

■ If the cloning user shares an existing Oracle home, the user must have writeaccess to some directories such as DBS.

Performing a cloning operationYou need to log onto OpsCenter, to perform a cloning operation. OpsCenter is theWeb GUI that you use to perform all guided recovery operations.

To perform a cloning operation on an Oracle database in OpsCenter

1 When you log onto OpsCenter, the first screen that appears is the MonitorOverviewscreen. Along the top of the screen, click Manage>OracleCloning.

2 On the Select Master Server screen, use the drop-down menu to select themaster server that you want to work with, then click Go.

See “Select Master Server screen” on page 507.

3 The Select Source Database screen lets you filter the list of databases bydatabase name, host name, database version, platform, and date. The defaultcondition is to display all databases that are backed up in the default daterange. Click Show Databases.

More information is available on this screen.

See “Select Source Database screen” on page 507.

505Guided RecoveryPerforming a cloning operation

4 The databases appear under the filtering part of the same screen. Select thedatabase on which you want to perform a cloning operation by clicking optionat the left side of the desired database entry. Then click Next>.

5 The Select Control File Backup screen shows a timeline view of the controlfile backups. Select the icon for the desired control file backup from thetimeline view. You can hover over the icon to display the control file details.If the icon represents multiple backups, you can hover over the icon to displayall versions of the backup for that time periods.

Additional information is available to verify that you have selected the correctcontrol file. The lower left corner of the screen lists three links. Moreinformation is available about these links.

See “Select Control File Backup screen” on page 507.

Click on the icon of the control file backup you want to restore for the cloneof the selected database. The default is the latest backup selected. Then clickNext>.

6 The Destination Host and Login screen contains parameters for thedestination of the clone to be created. Enter the destination host name in thetext box that is provided or click Browse and select from a list of availablehosts. Note the following prerequisites concerning the destination host:

■ The platform type of the source and destination must be the same.

■ A NetBackup client must be installed.

■ A compatible version of Oracle must be installed.

See “Destination host and login screen” on page 508.

For operating system authentication, enter a user name, password (Windows),and domain (Windows). Then click Next>.

7 The Define Destination Parameters screen appears. The five tabs on thisscreen are used to change database attributes, the destination paths of controlfiles, data files, and redo logs, and restore options. After you have changedthe destination parameters, click Next>.

See “Destination Parameters screen” on page 509.

Guided RecoveryPerforming a cloning operation

506

8 The SelectionSummary screen lets you scan the information you have enteredon the previous screens. Links to the recovery sets and destination databaseattributes let you view and verify any changes you have made. When you aresatisfied with the summary information, click Next>.

See “Selection summary screen” on page 509.

9 The Pre-cloneCheck screen lets you validate the database attributes and thefile paths. To validate, click the underlined word here. If a directory pathdoes not already exist, the validation check flags the error. If a file alreadyexists, the validation check also flags the error, so that the cloning operationdoes not overwrite the file.

See “Pre-clone check screen” on page 510.

When you are ready to launch the cloning operation, click Launch CloningProcess. A display appears that is similar to the NetBackup Activity Monitor.

Select Master Server screenFrom the pulldown menu, select the NetBackup master server that collected thebackup information to be used for the cloning operation.

Select Source Database screenWhen the Select Source Database screen first appears, the lowest portion of thescreen shows a list of the latest backups for all the databases that the masterserver knows about for the default date range.

The upper portion of the screen shows parameters for filtering the list of databases.If the list is long, you can filter what databases appear by database name, hostname, database version, and date range. Multiple filter parameters can be usedat the same time.

For example, to show only the Solaris databases that are backed up between11/05/2009 and 11/12/2009, select Solaris from the Platform: pulldown menu.Then select the dates from the calendar icons. Then click Show Databases todisplay the new filtered list of databases.

Select Control File Backup screenThe Select Control File Backup screen is a timeline view of all the control filesthat are backed up for the selected database. The timeline displays an icon foreach control file that is associated with the backed up database. When you firstenter this screen, the latest backup control file is already selected .

507Guided RecoverySelect Master Server screen

Hover over the icon on the timeline to display a popup that shows informationabout that file: backup name, type of media, the size of the backup, etc.

Multiple control files may be displayed on the timeline. To view all the instancesof control files, you may need to increase the scope of the timeline. You can displaythe timeline in days, weeks, months, or years. If multiple control files were backedup during a single timeline unit, a different icon appears representing more thanone control file (for example, if the database was backed up twice in an hour). Toselect from among these files, hover over the icon. A popup lists each control filein table format. It shows several items including the backup name and the typeof media. Click option next to the desired control file.

You can also click one of the links in the lower left of the screen to verify that youhave selected the proper control file.

■ ViewDatabaseSchema shows the schema of the selected control file. It showshow the database is laid out by listing each data file name, tablespace name,and its size.

■ View Datafiles Recovery Set shows the data file backups to be used for therestore process. It also shows the backup and image information that isdisplayed for each data file. The data file recovery set is generated only forthe files that are backed up as part of an incremental strategy. Even thoughfiles that are backed up as part of a full backup do not appear in this list, theclone still completes successfully.If the image spans media, only the first media is shown in the list.

■ View Archived Log Recovery Set shows the archive log backups that may beused to recover the database to the latest point in time of that control file. Thisset is generated only for the files that are backed up as part of an incrementalstrategy. Even though files that are backed up as part of a full backup do notappear in this list, the clone still completes successfully.

Destination host and login screenThe Select Destination Parameters screen lets you enter the destination host andthe Oracle logon information. For Windows, you are asked for the domain name,user name, and password. For UNIX and Linux, you are asked only for the username.

The following rules apply to the selection of the destination host:

■ The destination must be of the same platform type as the source of the clone.

■ A NetBackup client must be installed.

■ A compatible version of Oracle must be installed.

Guided RecoveryDestination host and login screen

508

Destination Parameters screenGuided Recovery uses many values from the source database as default valuesfor the destination database. You can modify these values if not appropriate forthe destination database.

Note:The Windows information you enter on this screen is case sensitive. Be sureto enter the Windows information appropriately.

The Destination Parameters screen contains the following tabs:

■ Database Attributes. This pane appears when you first enter the DatabaseAttributes screen. Each attribute name has identical source and destinationattributes. You can change the destination attribute of the instance name,database name, and database home. Note that the instance name is casesensitive while the database name is not case sensitive.

■ Control File Paths. This pane displays the source path and the destinationpath for each control file. You can change a control file destination path byclicking in the associated text window and entering the new path. You can alsoclick Browse to navigate to the desired path. When you change a path, ahighlight bar appears around the text window as a visual indicator that thispath has changed.

■ Data File Paths. This pane lets you change the destination path for one ormore data files. Enter the path in the text window provided, then select thedata files on which to apply it, and press the Apply option.

■ Redo Log Paths. This pane displays the source path and the destination pathfor all redo logs. You can type in a new destination path or click Browse tonavigate to the desired path. When you change a path, a highlight bar appearsaround the text window as a visual indicator that this path has changed.

■ Restore Options. This pane displays restore options. The option that isdisplayed on this pane is Numberofparallel streamsforrestoreandrecover.

When you are done making changes on this screen, click Next>. All the informationfrom the previous screen is saved in preparation for the cloning operation. Allthe changes that are made in this screen are temporary and are active only forthe cloning session.

Selection summary screenThe following information appears on this screen:

■ The selected master server and the source database attributes.

509Guided RecoveryDestination Parameters screen

■ The date and time of the selected control file backup, and the backup mediatype.

■ The database recovery set and the archived log recovery set.

■ The destination database attributes selected in the previous screen and thedatabase initialization parameters to be used for the cloning operation.

Pre-clone check screenThe Pre-cloneCheck screen lets you validate the database attributes and the filepaths. To validate, click the underlined word here. If a file path does not alreadyexist, the validation check flags the error. If a file already exists, the validationcheck also flags the error, so that the cloning operation does not overwrite thefile.

You can also specify an email address, so when the cloning process completes, anemail is sent to you that gives you the status of the cloning operation along withother pertinent information.

Job Details screenThe Job Details screen is intended to reflect the NetBackup Activity Monitor. Moreinformation is available on the Activity Monitor.

See the NetBackup Administrator's Guide, Volume I.

Post-clone operationsPerform the following after the cloning operation has completed:

■ On UNIX systems, update the oratab file with the appropriate instanceinformation.

■ If the cloning operation fails, do the following cleanup:

■ If the database is active, shut down the database.

■ Remove init<SID>.ora, spfile<SID>.ora, and any other files associated withthe SID being used, from the <$ORACLE_HOME>/DBS directory.

■ Remove all data files.

■ If the cloning operation fails, use the dbca utility to delete the database. dbcasometimes removes directories, so verify before retrying the operation.

Guided RecoveryPre-clone check screen

510

Troubleshooting Guided RecoveryGuided Recovery operations are in addition to the normal NetBackup for Oracleoperations. If problems are encountered, all previously used troubleshooting stepsand evidence are also relevant. The following sections detail the additional keyinformation that is required to troubleshoot Guided Recovery when it fails.

On UNIX and Linux systems, gather all legacy logs at VERBOSE=5. On Windowssystems, gather them at General=2, Verbose=5, and Database=5. All unified logsshould be gathered at DebugLevel=6 and DiagnosticlLevel=6.

Troubleshooting files for metadata collection operations at the timeof the backup

From the Oracle client host:

■ netbackup/logs/bphdb legacy logs

■ netbackup/logs/dbclient legacy logs (The directory must be writable by theOracle users.)

■ ncf unified logs, OID 309, New Client Framework

■ ncforautil unified logs, OID 360, New Client Framework Oracle Utility

■ ncforaclepi, OID 348, New Client Framework Oracle Plugin

From the NetBackup media server: netbackup/logs/bpbrm legacy logs

From the NetBackup master server:

■ netbackup/logs/bprd legacy logs

■ nbars unified logs, OID 362, NetBackup Agent Request Service

■ dars unified logs, OID 363, Database Agent Request Service

Troubleshooting files for Guided Recovery validation operationsFrom the Oracle client host:

■ netbackup/logs/vnetd legacy logs

■ ncf unified logs, OID 309, New Client Framework

■ ncfnbcs unified logs, OID 366, New Client Framework NetBackup Client Services




511Guided RecoveryTroubleshooting Guided Recovery






From the Symantec OpsCenter server:

■ <SYMCOpsCenterServer>/config/log.conf file

■ opscenterserver unified logs, OID 148 (The default location is<SYMCOpsCenterServer >/logs)

■ opscentergui unified log, OID 147 (The default location is<SYMCOpsCenterGUI>/logs)

Troubleshooting files for Guided Recovery cloning operationsFrom the Oracle client host:

■ netbackup/logs/bphdb legacy logs (Includes the obk_stdout and obk_stderrlogs.)

■ netbackup/logs/bpdbsbora legacy logs

■ netbackup/logs/dbclient legacy logs (The directory must be writable by theOracle users.)

■ A tar of netbackup/logs/user_ops (UNIX/Linux)

■ A compress of NetBackup\Logs\user_ops (Windows)






From the Symantec OpsCenter server:

■ <SYMCOpsCenterServer>/config/log.conf file

■ opscenterserver unified logs, OID 148 (The default location is<SYMCOpsCenterServer >/logs)

■ opscentergui unified log, OID 147 (The default location is<SYMCOpsCenterGUI>/logs)

Guided RecoveryTroubleshooting Guided Recovery

512

Understanding andconfiguring OpsCenteralerts


■ About using SNMP with OpsCenter

■ About managing OpsCenter alerts using Microsoft System Center OperationsManager 2007

■ About managing OpsCenter alerts using HP OpenView Network Node Manager7.50/7.51 on Windows

About using SNMP with OpsCenterThis section provides information about SNMP and how OpsCenter uses SNMP.

About SNMPThe Simple Network Management Protocol (SNMP) is an application layer protocolthat facilitates the exchange of management information between network devices.It is part of the Transmission Control Protocol/Internet Protocol (TCP/IP) protocolsuite. SNMP enables network administrators to manage network performance,find and solve network problems, and plan for network growth.

SNMP is based on the manager and agent model consisting of a manager, an agent,a database of management information, managed objects, and the networkprotocol.

11Chapter

The manager provides the interface between the human network manager andthe management system. The agent provides the interface between the managerand the physical devices being managed.

The manager and agent use a Management Information Base (MIB) and a relativelysmall set of commands to exchange information. The MIB is organized in a treestructure with individual variables, such as point status or description, beingrepresented as leaves on the branches. A numeric tag or object identifier (OID) isused to distinguish each variable uniquely in the MIB and in SNMP messages.

About SNMP versionsMany versions of SNMP are available.

The versions of SNMP protocol are as follows:

■ SNMPv1The SNMPv1 version is the first version of the protocol. and is defined by RFC1157. This document replaces the earlier versions that were published as RFC1067 and RFC 1098. Security is based on community strings.

■ SNMPv2It was created as an update of SNMPv1 adding several features. The keyenhancements to SNMPv2 are focused on the SMI, manager-to-managercapability, and protocol operations.SNMPv2c combines the Community-based approach of SNMPv1 with theprotocol operation of SNMPv2 and omits all SNMPv2 security features.

■ The original SNMPv2 (SNMPv2p)

■ Community-based SNMPv2 (SNMPv2c)

■ User-based SNMPv2 (SNMPv2u)

■ SNMPv2 star (SNMPv2*).

■ SNMPv3This version of the protocol is a combination of user-based security and theprotocol operations and data types from SNMPv2p, and support for proxies.The security is based on that found in SNMPv2u and SNMPv2*. RFC 1905, RFC1906, RFC 2261, RFC 2262, RFC 2263, RFC 2264, and RFC 2265 define thisprotocol.

About SNMP versions supported in OpsCenterOpsCenter supports the following SNMP versions:

■ SNMPv1

Understanding and configuring OpsCenter alertsAbout using SNMP with OpsCenter

514

■ SNMPv2c

■ SNMPv3

About the Management Information Base (MIB) and OpsCenter supportEach SNMP element manages specific objects with each object having specificcharacteristics. Each object and characteristic has a unique object identifier (OID)that is associated with it. Each OID consists of the numbers that are separated bydecimal points (for example, 1.3.6.1.4.1.2682.1).

These OIDs form a tree. The MIB associates each OID with a readable label andvarious other parameters that are related to the object. The MIB then serves as adata dictionary that is used to assemble and interpret SNMP messages.

About SNMP trapsThis section explains the content of an SNMP trap that is sent from SymantecOpsCenter.

Each OpsCenter trap contains 2 standard object identifiers and 12OpsCenter-specific object identifiers. An object identifier (or OID) is a numericstring that is used to uniquely identify an object.

The following table shows the contents of a trap that is sent from OpsCenter. Atotal of 14 bindings (or 14 name-value pairs) are present in each trap that is sentfrom OpsCenter. Each binding associates a particular Management InformationBase (MIB) object instance with its current value.

Table 11-1 shows the name-value pairs that the traps pass to the SNMP manager.

Table 11-1 OpsCenter trap binding

ValueName

This field is the time (in hundredthsof a second) between when OpsCenterserver service starts and theOpsCenter trap is sent.

See Request for Comment (RFC) 1905and 2576 for a detailed definition.

http://www.ietf.org/rfc/rfc1905.txt


Example: 1173792454

1.3.6.1.2.1.1.3.0

515Understanding and configuring OpsCenter alertsAbout using SNMP with OpsCenter



Table 11-1 OpsCenter trap binding (continued)

ValueName

This field is the unique identifier forthis trap.

See RFC 1905 and RFC 2576 for adetailed definition.



Example: 1.3.6.1.4.1.1302.3.12.10.2.0.4

1.3.6.1.6.3.1.1.4.1.0

This field is the alert recipient name.

Example: Nancy Nieters

1.3.6.1.4.1.1302.3.12.10.1.1

(iso.org.dod.internet.private.enterprises.products.veritascc.

ccTrapDefinitionsBranch.ccTrapVarsBranch.alertRecipients)

This value specifies the alert ID, alertstatus, and alert summary in thefollowing format:

Alert ID (Alert Status) Alert Summary

Example: 100 (Active) Job Completedwith Exit Status 0

1.3.6.1.4.1.1302.3.12.10.1.2

(iso.org.dod.internet.private.enterprises.products.veritascc.ccTrapDefinitionsBranc

h.ccTrapVarsBranch.alertSummary)

This field is the alert description.

Examples for each alert condition areavailable.

See “About alert description”on page 518.

1.3.6.1.4.1.1302.3.12.10.1.3


ccTrapDefinitionsBranch.ccTrapVarsBranch.alertDescription)

This field is blank and not used.1.3.6.1.4.1.1302.3.12.10.1.4


ccTrapDefinitionsBranch.ccTrapVarsBranch.policyName)


(iso.org.dod.internet.private.enterprises.veritas.products.veritascc.ccTrapDefinition

sBranch.ccTrapVarsBranch.objectType)


516



Table 11-1 OpsCenter trap binding (continued)

ValueName



sBranch.ccTrapVarsBranch.collectorNam e)

This field is the IP address of theOpsCenter server.

Example: 10.212.12.148

1.3.6.1.4.1.1302.3.12.10.1.7


sBranch.ccTrapVarsBranch.ccHost)



sBranch.ccTrapVarsBranch.sourceId)



sBranch.ccTrapVarsBranch.ccObject)



sBranch.ccTrapVarsBranch.sampleData)

This field shows the alert severitylevel.

Example: Informational

1.3.6.1.4.1.1302.3.12.10.1.11


sBranch.ccTrapVarsBranch.ccAlertSeverity)

This field shows the time when thealert gets cleared.

Example: 13-10-2008 06:57:34 00

1.3.6.1.4.1.1302.3.12.10.1.12


sBranch.ccTrapVarsBranch.ccAlertTime)

The first two OIDs listed in the table are standard SNMP OIDs. The other OIDsstarting from 1.3.6.1.4.1.1302.3.12.10.1.1 to 1.3.6.1.4.1.1302.3.12.10.1.12 areOpsCenter OIDs. As per SNMPv2c trap definition, the two standard SNMP OIDsmust be present as part of every trap.


All the 12 OpsCenter OIDs are defined in the OpsCenter MIB files. However, thetwo standard OIDs are not defined in the OpsCenter MIB files.

About alert descriptionThis section shows the content that is sent for each OpsCenter alert as OID1.3.6.1.4.1.1302.3.12.10.1.3.

Note: 1.3.6.1.4.1.1302.3.12.10.1.3 representsiso.org.dod.internet.private.enterprises.products.veritascc.ccTrapDefinitionsBranch.ccTrapVarsBranch.alertDescription.

Most of the alert information in OpsCenter is sent as OID1.3.6.1.4.1.1302.3.12.10.1.3.

Table 11-2 shows the content that each OpsCenter alert sends as OID1.3.6.1.4.1.1302.3.12.10.1.3.


518

Table 11-2 Alert conditions in OpsCenter

Description (Example)Alert conditionAlerttype

Alert Raised on: September 5, 2009 5:00 PM

Tree Type : Policy

Nodes : Root Node

% Failed Jobs: 100.0

Alert Policy: high job failure rate policy view

OpsCenter Server: ccs-sol-qe-17

Severity: Warning

High job failure rateJob


Job: 25888

Tree Type : Policy

Nodes : ccs-win-qe-5

Job Policy: ccsqasol1

Client: ccs-win-qe-5

Alert Policy: Hung Job


Severity: Warning

Hung job


Job: 26356

Tree Type : Policy

Nodes : node1

Job Policy: sample_policy

Exit Status: 150 (termination requested byadministrator)


New State: Done

Alert Policy: Job Finalized


Severity: Warning

Job finalized

Incomplete Job





Job: 26356

Tree Type : Policy

Nodes : node1

Job Policy: sample_policy


Alert Policy: Incomplete Job


Severity: Warning


520



Alert Raised on: August 17, 2009 12:24 PM

Tree Type : Server

Nodes: node1

Frozen Media Name: A00004

Media server : ranjan

Alert Policy: frozen media policy

OpsCenter Server: localhost

Severity: Warning

Frozen mediaMedia


Suspended Media Name: 0122L2

Tree Type : Server

Nodes: node1

Media server : ccs-win-qe-13

Alert Policy: Suspended media policy


Severity: Informational

Suspended media


Media Name: A00009

Tree Type : Server

Nodes: node1

Media server : ccs-win-qe-13

Number of mounts: 3402

Alert Policy: Exceeded Max Media Mounts policy


Severity: Critical

Exceeded max mediamounts

Media required forrestore




Alert Raised on: December 4, 2008 4:39 PM

Tree Type : Server

Nodes: node1

Media: 000_00000_TL4 Required for restore

Master server: omwin12(omwin12)

Client: omwin12

Media server: macy

Restore Job ID: 615

Alert Policy: Media Required for Restore_root


Severity: Warning

Alert Raised on: August 12, 2009 11:54 AM

Tree Type: Server

Nodes: node1

Available Media: 4

Alert Policy: low available media


Severity: Warning

Low available media


Tree Type : Server

Nodes: node1

Suspended Media: 1

% Suspended Media: 25.0

Alert Policy: high percentage suspended media


Severity: Warning

High suspended media

High frozen media


522



Alert Raised on: December 8, 2008 10:24 AM

Tree Type : Server

Nodes: node1

Frozen media: 6

% Frozen Media: 66

Alert Policy: highfrozenmedia

OpsCenter Server: winfor11

Severity: Warning




Alert Raised on: December 8, 2008 10:08 AM

Master server : sargam(sargam)

Tree Type : Server

Nodes: node1

Available Catalog Space: 6480880 KB

Threshold Catalog Space: 102400 TB

Alert Policy: test_catalogspacelow


Severity: Warning

Catalog Space lowCatalog

Alert Raised on: September 7, 2009 9:54 AM

Tree Type : Server

Nodes : ccs-sol-qe-13

Threshold: 10 Minute(s)

Last Catalog BackUp Time: September 6, 2009 5:21PM

Alert Policy: Catalog not Backed up


Severity: Warning

Catalog not Backed up


Tree Type : Server


Alert Policy: Catalog Backup Disabled


Severity: Warning

Catalog BackupDisabled


524




Tree Type : Server


Barcode: 000014

Density: dlt

evsn: 000014

Mode: 82

Request ID: 120

rvsn: 000014

User: - Volume Group: 000_00000_TLD

Request Time: February 4, 1991 12:56 AM

Alert Policy: Mount Request


Severity: Warning

Mount RequestTape


Tree Type : Server


Media server : ranjan

Robot Number: 0

Alert Policy: no cleaning tape left


Severity: Warning

No Cleaning Tape

Zero Cleaning Left




Alert Raised on: December 13, 2008 12:02 PM

Tree Type : Server


Master server : ORLP-SPEECH01

Media server : ORLP-SPEECH01

Robot Number: 0

Cleaning Tape: CLN084

Alert Policy: test_zerocleaningleft_public


Severity: Warning


526




Tree Type : Server


Disk Pool ID: SSOD_Pool

Disk Pool Name: SSOD_Pool

Total Capacity: 1007664128 KB

Used Capacity: 1005702144 KB

Alert Policy: Disk Pool Full



Disk Pool FullDisk


Tree Type : Server


Disk Volume ID: /vol/luns/nbusd_sun10

Disk Pool ID: SSOD_Pool

Alert Policy: disk volume down pol



Disk Volume Down


Tree Type : Server


Disk Volume Free Capacity: 106 MB

Threshold: 20 %


Severity: Major

Low Disk VolumeCapacity

Drive is Down





Tree Type : Server


Media server : omlinux2

Drive Name: BNCHMARK.VS640.000

Drive Number: 1

Robot Number: 0

Alert Policy: drive down-individual alert

Device Path: /dev/nst0


Severity: Critical


Tree Type : Server


Drive Number: 1

% Down Drive Paths: 100.0

Alert Policy: high down drives


Severity: Major

High Down Drives


528



Agent Host Name : pinacolada

Server Host Name : PINACOLADA

Severity: Warning

Agent ServerCommunication break

Host

Alert Raised on: October 23, 2009 12:20 AM

Alert Policy: MasterServer

Unreachable OpsCenter Server: CCSQAWINSP1

Severity: Major

Master ServerUnreachable

Alert Raised on: February 18, 2008 1:33 PM

Master server : pmsun22

Media server : pmsun22

Alert Policy: lcm

OpsCenter Server: pmwin9

Severity: Warning

Lost Contact withMedia Server


Tree Type : Server


Media server : omlinux2

Process Name: nbkms

Alert Policy: Service stopped


Severity: Major

Service Stopped


ThreatCon is at Level 1:Normal

Alert Policy: THREAT_CON

OpsCenter Server: divakar

Severity: Warning

Symantec ThreatCon

Job Policy Change





Tree Type : Server


Changed Policy Name: BMRPolicy

Alert Policy: job policy_change


Modified Policy Attributes :

Severity: Warning

Configuring the SNMP trap community name for OpsCenterFor OpsCenter traps, the SNMP trap community name is OpsCenter (by default).Symantec OpsCenter uses a public community named Opscenter. Public communityimplies a read-only access to SNMP traps.

Use the following procedures to configure the SNMP trap community name onWindows and UNIX.

To configure the SNMP trap community name for OpsCenter traps on Windows

1 On the OpsCenter server host, stop all the OpsCenter server services.


2 Navigate to INSTALL_PATH\OpsCenter\server\config directory and openthe nm.conf file.

The file shows the following entry:

nm.trapCommunity=OpsCenter

Modify the value of nm.trapCommunity from OpsCenter to some other name.

3 Save the nm.conf file after making the changes.

4 Restart all OpsCenter services.



530

To configure the SNMP trap community name for OpsCenter traps on UNIX

1 On the OpsCenter server host, stop all the OpsCenter services.


2 Navigate to /opt/SYMCOpsCenterServer/config directory and open thenm.conf file.


nm.trapCommunity=OpsCenter

Modify the value of nm.trapCommunity from OpsCenter to some other name.


4 Restart all OpsCenter services.


Configuring the SNMP version for sending SNMP trapsThe default SNMP version through which SNMP traps are sent in OpsCenter isSNMPv2c. However, this SNMP version can be changed by modifying aconfiguration file.

The following procedure explains how to configure the default SNMP version onWindows and UNIX.

To configure the SNMP version for sending SNMP traps on Windows

1 On the OpsCenter server host, stop all the OpsCenter services.

INSTALL_PATH\server\bin\opsadmin.bat stop

2 Navigate to INSTALL_PATH\OpsCenter\server\config directory and openthe nm.conf file.


nm.trapVersion=v2c

Modify the value of nm.trapVersion from v2c to v1 (for SNMPv1) or v3 (forSNMPv3).


4 Restart all OpsCenter services:



To configure the SNMP version for sending SNMP traps on UNIX

1 On the OpsCenter server host, stop all the OpsCenter services:


2 Navigate to the OpsCenter configuration directory:

cd /opt/SYMCOpsCenterServer/config

3 Open the nm.conf file. The file shows the following entry:

nm.trapVersion="v2c"

Modify the value of nm.trapVersion from v2c to v1 (for SNMPv1) or v3 (forSNMPv3).


5 Restart all OpsCenter services:


About customizing alert settingsIn OpsCenter, you can customize a few alert settings using the am.conf

configuration file.

The am.conf configuration file is located at the following default location:

<INSTALL_DIR>\OpsCenter\server\config\am.confWindows

<INSTALL_DIR>/SYMCOpsCenterServer/config/am.confUNIX

The alert configuration settings are described as follows:

Note: By default all alert configuration parameters are set to “true”.

Set this parameter to “true”, if you want toautomatically clear the alerts.

am.autoClear

Make sure that the am.autoClearparameter is set to “true”, to apply thechange in the am.notifyOnAutoClearparameter setting.

Set this parameter to “true”, if you want tosend notification after an alert wasautomatically cleared.

am.notifyOnAutoClear


532

Set this parameter to “true”, if you want tosend notifications after manually clearingalerts.

am.notifyOnManualClear

Note: If you set an alert configuration parameter to a value other than “true” or“false”, OpsCenter assumes it as “false”.

Frequently asked SNMP questionsWhat are the default versions of SNMP that are supported in OpsCenter?

SNMPv1, SNMPv2c, and SNMPv3.

What is SNMPv2c? How it is different from SNMPv2?

See “About SNMP versions” on page 514.

Is the OpsCenter SNMP community name configurable?

Yes.

See “Configuring the SNMP trap community name for OpsCenter” on page 530.

How is the OpsCenter community related to the public community?

Is the default community name of "OpsCenter" just a name for the community,but still considered public because of certain attributes?

Generally, the "default read community string" for the public community is"public". Public community means read-only access to SNMP traps.

The "OpsCenter" community used by OpsCenter is public, but the communityname is maintained as "OpsCenter".

About managing OpsCenter alerts using MicrosoftSystem Center Operations Manager 2007

Microsoft System Center Operations Manager 2007 (SCOM), formerly MicrosoftOperations Manager (MOM), is a next-generation performance andevent-monitoring product from Microsoft. Microsoft System Center OperationsManager Management Pack for NetBackup lets you monitor and manage NetBackupalerts using Microsoft System Center Operations Manager 2007 (SCOM 2007). Bydetecting and alerting you on critical conditions, this Management Pack helpsprevent possible service outages.

The SCOM Management Pack for NetBackup and the documentation is availablefor download on the Symantec Support Web site.

533Understanding and configuring OpsCenter alertsAbout managing OpsCenter alerts using Microsoft System Center Operations Manager 2007


AboutmanagingOpsCenter alerts usingHPOpenViewNetwork Node Manager 7.50/7.51 on Windows

You can monitor and manage NetBackup alerts using HP OpenView Network NodeManager 7.50 or 7.51 on Windows. By detecting and alerting you on criticalconditions, HP OpenView Network Node Manager (NNM) can help you to preventpossible service outages.

You can download and use the nom_trapd.conf file to monitor and manageNetBackup alerts using HP OpenView Network Node Manager 7.50 or 7.51. Byusing nom_trapd.conf file and configuring NNM and OpsCenter, NNM can receivethe SNMP traps that have been configured in OpsCenter. As a result, NNM can beused for the centralized management of NetBackup alerts.

Note:The term HP OpenView Network Node Manager (NNM) in this section refersspecifically to HP OpenView Network Node Manager 7.50 or 7.51.

nom_trapd.conf file and the documentation is available for download on thesupport site.


More information about OpsCenter alerts is available.


Understanding and configuring OpsCenter alertsAbout managing OpsCenter alerts using HP OpenView Network Node Manager 7.50/7.51 on Windows

534



Reporting in OpsCenter


■ About OpsCenter reports

■ Working with Report Templates

■ Managing reports

■ Creating a custom report

■ Creating a report using SQL query

■ Managing My Reports

■ Managing My Dashboard

■ Managing folders

■ About schedules

■ Managing report schedules

■ Managing time schedules

■ About Report Templates descriptions

About OpsCenter reportsSymantec OpsCenter is a Web-based software application that helps organizationsby providing visibility into their data protection environment. By using OpsCenter,you can track the effectiveness of data backup and archive operations bygenerating comprehensive business-level reports.

OpsCenter displays customizable, multi-level views of backup and archiveresources and customizable reports for tracking service usage and expenditures.

12Chapter

It also contains tools for defining cost metrics and chargeback formulas or handlingalerts. A wide range of audiences benefit from the reporting and the managementcapabilities of OpsCenter. The audiences include IT (Information Technology)managers, application owners, IT finance teams, external compliance auditors,legal teams, line-of-business managers, external customers, IT architects, andcapacity planning teams.

About the OpsCenter reports UIThe OpsCenter reports UI consists of the following components:

This tab lists all Report Templates (orstandard or canned reports) that areavailable in OpsCenter. You can modify thedefault parameter values of a ReportTemplate as required and generate a newreport of that kind.

For example, use the existing Backups >Client Count Report Template , change therelative timeframe to four weeks (defaulttimeframe is two weeks) and generate a newClient Count report. You can see all clientsthat are backed up over the last four weeks.

See “About Report Templates” on page 537.

Report Templates tab

You can save generated reports for yourfuture use. These saved reports are storedin the My Reports tab. Use this section toview the saved reports or modify theparameters of the saved reports and generatenew reports out of them. You can also deletethe saved reports using the My Reports tab.

See “Managing My Reports” on page 557.

See “Saving a report” on page 551.

My Reports tab

Your saved reports are preserved in MyReports tab, which you can select andpublish on My Dashboard tab. You can selectmultiple reports and add them in the samedashboard section. Thus, you can createmultiple dashboard section containing anumber of reports.

See “Managing My Dashboard” on page 561.

My Dashboard tab

Reporting in OpsCenterAbout OpsCenter reports

536

This tab contains all report schedules.

You can create, edit, or delete schedulesusing this tab.

See “About schedules” on page 565.

Schedules tab

Use this tab to manage folders where youhave saved your reports.

See “Managing folders” on page 563.

Manage Folders tab

About report creation wizardsOpsCenter provides wizards, which guide you through the entire report creationprocedure.

To create a report, in the OpsCenter console on the Reports tab, click CreateNewReport. The following report creation options are available:

■ Create a report using an existing Report Template .See “Creating a report using a Report Template ” on page 550.

■ Create a custom report.See “Creating a custom report” on page 555.

■ Create a report using SQL Query.See “Creating a report using SQL query” on page 556.

About Report TemplatesThis section provides details of the Report Templates that are available inOpsCenter.

OpsCenter provides a number of Report Templates (or standard or canned reports)that you can modify and generate a new report of that kind.

In the OpsCenter console, when you click the Reports tab, the Report Templateshome page is displayed. Click any of the Report Template to view the respectivereport with default parameter values.

See “About Report Templates descriptions” on page 574.

Figure 12-1 shows various components of a report that is generated using atemplate.

537Reporting in OpsCenterAbout OpsCenter reports

Figure 12-1 Report Template

ReportTemplates tree

Report area

Report views

Tabular view

Time filters

Manage reportstoolbar

This tree lists all Report Templates that areavailable in OpsCenter.

Report Templates tree

Use this toolbar to save, export, or email thegenerated report.

Manage report toolbar

Use these time filters to view the data for aspecific period of time.

Time filters

OpsCenter reports are displayed here.Report area

Reports can be viewed in different forms orviews, Distribution, Historical, or Ranking.Use these options to change the currentreport view.

Report views

About changes in the reporting interface in OpsCenter 7.0.1This section lists the usability changes introduced in OpsCenter 7.0.1 in thereporting user interface.

The following table lists the differences between the user interfaces in OpsCenter7.0 and 7.0.1, such as locations and nomenclature of reports. In addition, enhancedreport descriptions have been added for all the reports in OpsCenter 7.0.1.

Table 12-1 described the reporting interface changes in OpsCenter 7.0.1.


538

Table 12-1 Differences between OpsCenter 7.0 and 7.0.1 reporting interface

Name and location of reports inOpsCenter 7.0.1

Name and location of reports inOpsCenter 7.0

Report Templates > Enterprise VaultArchiving > Archive Storage:

■ Archived Count

■ Tabular - Storage Report

■ Archived Size

Note: The folder Archive is renamed asEnterprise Vault Archiving.

Report Templates > Archive > ArchiveStorage:

■ Archived Count

■ Tabular - Storage Report

■ Archived Size

Report Templates > Enterprise VaultArchiving > Exchange:

■ Mailbox Quota > By Send Limit

■ Mailbox Quota > By Warning Limit

■ Mailbox Quota > By Receive Limit

■ Archive Size Vs Original Size

■ Item Count

■ Target Report Detail

■ Original Size

Note: The folder Archive is renamed asEnterprise Vault Archiving.

Report Templates > Archive > Exchange:

■ Mailbox Quota > By Send Limit

■ Mailbox Quota > By Warning Limit

■ Mailbox Quota > By Receive Limit

■ Archive Size Vs Original Size

■ Item Count

■ Target Report Detail

■ Original Size

Report Templates > Backup > Deduplication:

■ Deduplication Size Factor (earlier namedSize Factor)

■ Pre vs. Post Deduplication Size (earliernamed Protected Size vs Backed up Size)

■ Deduplication Size Savings (earliernamed Size Savings)

Note: The folder Backups is renamed asBackup.

The Size Factor report is renamed asDeduplication Size Factor report. TheProtected Size vs Backed up Size report isrenamed as Pre vs. Post Deduplication Size.The Size Savings report is renamed asDeduplication Size Savings.

Report Templates > Backup > Deduplication:

■ Size Factor

■ Protected Size vs Backed up Size

■ Size Savings


Table 12-1 Differences between OpsCenter 7.0 and 7.0.1 reporting interface(continued)



Report Templates > Backup > Job Activity >Variance:





Note: These reports were earlier locatedunder Report Templates > Job Reports folderin OpsCenter 7.0.

Report Templates > Job Reports:

■ Partially Successful Job Details

■ Skipped Files Summary

■ Backup Window Failures

■ Job Summary by Status





■ BMR Client Configuration BackupFailures

■ Job Details

■ Restore Job Details

■ Restore Job Summary by Job Count

■ Restore Job Summary by VolumeRestored

■ Job Exit Status Detail

Report Templates > Backup > Job Activity >Backup Window:

■ Job Count (earlier named Backup Window- Job Count)

■ Job Size (earlier named Backup Window- Job Size)

■ File Count (earlier named BackupWindow - File Count)

Note: These reports were earlier locatedunder Backups > Activity Planning > BackupWindow folder. In addition, the abovereports have been renamed. The BackupWindow - Job Count report is renamed as JobCount report. The Backup Window - Job Sizereport is renamed as Job Size report. TheBackup Window - File Count report isrenamed as File Count report.

Backups > Activity Planning > BackupWindow:

■ Backup Window - Job Count

■ Backup Window - Job Size

■ Backup Window - File Count


540




Report Templates > Chargeback:

■ Backup Chargeback (earlier CharegbackReport)

■ Deduplication Chargeback (earlierSavings Report)

■ Cost Tabular

Note: Chargeback Reports folder is renamedas Chargeback. Chargeback Report isrenamed as Backup Chargeback. SavingsReport is renamed as DeduplicationChargeback.

Report Templates > Chargeback Reports:

■ Chargeback Report

■ Savings Report

■ Cost Tabular

Report Templates > Backup > Job Activity:

■ File Count

■ Job Count

■ Job Size

■ Client Count

■ Job Duration

Note: In OpsCenter 7.0, the above reportswere located in the Report Templates >Backups > Activity Planning folder.

Report Templates > Backups > ActivityPlanning:

■ File Count

■ Job Count

■ Job Size

■ Client Count

■ Job Duration





Report Templates > Backup > PlanningActivity:

■ Capacity Planning (folder)

■ Forecast (folder)

■ Scheduled Job (folder)

■ Stored Backup Images (folder)

Note: The folder Backups is renamed asBackup. The Activity Planning folder isrenamed as Planning Activity.

Report Templates > Backups > ActivityPlanning:

■ Capacity Planning (folder)

■ Forecast (folder)

■ Scheduled Job (folder)

■ Stored Backup Images (folder)

■ Backup Window (folder) [moved to ReportTemplates > Backup > Job Activity folder]

■ File Count (moved to Report Templates> Backup > Job Activity)

■ Job Count (moved to Report Templates >Backup > Job Activity)

■ Job Size (moved to Report Templates >Backup > Job Activity)

■ Client Count (moved to Report Templates> Backup > Job Activity)

■ Job Duration (moved to Report Templates> Backup > Job Activity)

Report Templates > Backup > PlanningActivity > Scheduled Job:

■ Scheduled Job

■ Job Count Scheduled vs Actual

■ Job Count within Backup Window

■ Job Details-Scheduled vs Actual (earlierJob Count within Backup Window)

■ All Jobs

Note: Activity Planning folder is renamedas Planning Activity. The Job CountDetails-Scheduled vs Actual report isrenamed as Job Details-Scheduled vs Actualreport.

Report Templates > Backups > ActivityPlanning > Scheduled Job:

■ Scheduled Job

■ Job Count Scheduled vs Actual

■ Job Count within Backup Window

■ Job Count Details-Scheduled vs Actual

■ All Jobs


542




Report Templates > Backup > Status &Success Rate > Status:

■ Failed Job Count

■ Partially Successful Job Count

■ Successful Job Count




■ Week at a Glance





■ Job Details


■ Job Status

Note: The Report Templates > Backup >Status & Success Rate > Status foldercontains most reports from ReportTemplates > Backups > Status (except DailySummary of Backup Activity). Also, thefollowing reports from Report Templates >Job Reports folder have been added:





■ Job Details


Report Templates > Backups > Status:

■ Daily Summary of Backup Activity(renamed as Advanced Success Rate andexists in Report Templates > Backup >Status & Success Rate > Success Rate)

■ Failed Job Count

■ Partially Successful Job Count

■ Successful Job Count




■ Week at a Glance

■ Job Status





Report Templates > Backup > Status &Success Rate > Success Rate:

■ Success Rate - First Attempt

■ Success Rate - All Jobs (earlier namedSuccess Rate - At Least 1 Success PerClient)

■ Success Rate - All Attempts

■ Advanced Success Rate (earlier namedDaily Summary of Backup Activity inBackups > Status folder)

Note: Success Rate - At Least 1 Success PerClient is renamed as Success Rate - All Jobs

Report Templates > Backups > Success Rate:

■ Success Rate - First Attempt

■ Success Rate - At Least 1 Success PerClient

■ Success Rate - All Attempts

Report Templates > Chargeback:

■ Deduplication Chargeback (earlier wasSavings Report)

■ Cost Tabular

■ Backup Chargeback (earlier wasChargeback report)

Note: The Chargeback Reports folder isrenamed as Chargeback. Savings Report isrenamed as Deduplication Chargeback.Chargeback Report is renamed as BackupChargeback.

Report Templates > Chargeback Reports:

■ Savings Report

■ Cost Tabular

■ Chargeback Report


544




Report Templates > Client Reports:

■ Risk Analysis folder


■ Client Coverage

■ Recovery Point Objective



■ Job Success by Client

■ Job Success by Client (Tabular)


■ Client Restore


■ Jobs by Application

Note: The Risk Analysis folder is now underClient Reports. The reports under Backups> Risk Analysis have been moved to ClientReports > Risk Analysis folder. BMR ClientConfiguration Backup Failures report fromJob Reports folder is moved to ClientReports.

Report Templates > Backups > Risk Analysis:


■ Client Coverage

■ Recovery Point Objective

Client Reports



■ Job Success by Client

■ Job Success by Client (Tabular)


■ Client Restore

■ Jobs by Application





Report Templates > Disk and Tape DeviceActivity:


■ Current Disk Usage

■ NetBackup Disk Pool Capacity

■ NetBackup Disk Pool Size vs PercentageFull

■ NetBackup SAN Client Performance

■ Library Summary

■ Library Capacity Forecast



■ SAN Client Jobs

Note: All the reports from Disk Based DataProtection folder, Backups > Disk PoolReports folder, Backups > Tape Devicesfolder are now under Disk and Tape DeviceActivity folder.

Report Templates > Disk Based DataProtection:


■ Current Disk Usage

■ SAN Client Jobs

Backups > Disk Pool Reports:

■ NetBackup Disk Pool Size vs PercentageFull

■ NetBackup SAN Client Performance

■ NetBackup Disk Pool Capacity

Backups > Tape Devices:

■ Library Capacity Forecast



■ Library Summary

Report Templates > Media Reports:

■ Media State

■ Available Media Report

■ Drives in Use

■ Full Media Capacity (Tabular)


■ Media Utilization

■ Tape Count

■ Tapes Expiring in Future

■ Tapes Expiring Now

■ Vault Media Usage

■ Media Expiration Schedule

Note: The Vault Media Usage report hasbeen moved from Vault Reports to MediaReports folder.

Report Templates > Media Reports:

■ Media State

■ Available Media Report

■ Drives in Use

■ Full Media Capacity (Tabular)


■ Media Utilization

■ Tape Count

■ Tapes Expiring in Future

■ Tapes Expiring Now

■ Media Expiration Schedule

Vault Reports:

■ Vault Media Usage


546




Report Templates > Policy Reports:

■ Top 10 Policies Using most Server Space

■ Job success rate by policy type (tabular)

■ Job success rate by policy type(Graphical) [earlier was Job success rateby policy type]

■ Policy Change (Distribution)

■ Policy Change (Tabular)

■ Policy Summary Dashboard

Note: Job success rate by policy type reportis renamed as Job success rate by policy type(Graphical).

Report Templates > Policy Reports:

■ Top 10 Policies Using most Server Space

■ Job success rate by policy type (tabular)

■ Job success rate by policy type

■ Policy Change (Distribution)

■ Policy Change (Tabular)

■ Policy Summary Dashboard

Report Templates > Restore:




Note: The above three reports moved fromthe Job Reports folder to the Restore folder.

Report Templates > Job Reports:










■ Job Details





Note: The sequence in which the reports appear in the Report Templates tree inOpsCenter 7.0.1 is different than OpsCenter 7.0.


About custom reportsApart from generating reports using the existing templates, you can also createcustom reports in OpsCenter by changing the report parameters as required.

See “Creating a custom report” on page 555.

About custom SQL queryIn OpsCenter, you can create reports by directly running SQL queries. Using thisreport creation option, you do not need to go through multiple parameterselections.

Note: You can create only tabular reports by running SQL queries. You can alsorun stored procedures using this feature.

See “Creating a report using SQL query” on page 556.

Working with Report TemplatesSymantec OpsCenter provides a set of Report Templates or standard or cannedreports that have parameters set to default values. You can use modify the defaultparameters and generate reports to view the required data. OpsCenter reportshelp you to have a good visibility into your data protection environment.

See “About Report Templates” on page 537.

Report Templates are categorized as follows:

These reports are generated based on thearchive data that is collected from EnterpriseVault. You can report on the number ofmessages that are archived across mailboxesor on the size of these messages before andafter the archive operation.

Enterprise Vault Archiving Reports

Reporting in OpsCenterWorking with Report Templates

548

The backup reports show the informationthat is related to backups, such as successrate, job status, and protected bytes. Thiscategory also includes recovery reports.

Note: If you select Reports > ActivityPlanning > Job Size in the OpsCenter userinterface, the report that appears displaysthe wrong client name. Instead of showingthe client names, a list of backed up VMimages is displayed in this report. Inaddition, the list of VM images may not beaccurate.

Backup Reports

These reports provide details about thecatalogs.

Catalog Reports

The chargeback reports provide details ofthe backup services expenditures.

Using these reports you can track the backupand the recovery usage and the associatedcost. You can calculate the cost of dataprotection management and chargeback tocustomers and business units.

Chargeback Reports

These reports provide details about clientssuch as backup status, restore job details, orsummary dashboard.

Client Reports

Disk-based data protection (DBDP) reportsshow disk pool capacity and its usage,performance of clients on LAN or SAN,NetBackup Storage Lifecycle Map

Disk & Tape Device Activity Reports

These reports provide media data, such astape count or usage

Media Reports

These reports provide details of throughputsPerformance Reports

These reports show all details about thebackup job policies in NetBackup.

Policy Reports

These reports provide details about restoreoperation.

Restore Reports

549Reporting in OpsCenterWorking with Report Templates

About report filtersThere can be hundreds of records or thousands of MB of the data that you maynot be concerned about. For example, you want to view only those jobs that weresuccessful. To view this specific data, you need to use the ‘status’ filter. By settingthis filter to ‘Successful’ while generating the Job Count report, you can view alljobs that were successful.

OpsCenter provides a number of filters that you can use to view the required data.For each report category there is a different set of filters.

Creating a report using a Report TemplateThis section provides the procedure to create a report using an existing ReportTemplate .

To create a report using an existing Report Template

1 In the OpsCenter console, click Reports.

2 On the Reports Template tab, click Create New Report.

To view a report output of a template, select a template in the reports tree.The report output is as per the default parameter values. You cannot modifyany of the report parameters.

By clicking the Create New Report button, you can launch the report creationwizard that guides you through the entire report creation procedure. Hereyou can modify the report parameters and view the required data.

3 On the Report Wizard, retain the default selection that is ‘Create a reportusing an existing Report Template ’ and click Next.

4 On the Report Templates list, expand a report category to see the ReportTemplates within it. Select the Report Template that you want to create areport from and click Next.

5 Select time frame and other filters as required and click Next.

6 Modify display options and click Next.

Managing reportsThis section provides information on the operations that you can carry out onthe standard reports that you generate in OpsCenter.

You can carry out the following operations:

■ Saving a reportSee “Saving a report” on page 551.

Reporting in OpsCenterManaging reports

550

■ Exporting a reportSee “Exporting a report” on page 553.

■ Emailing a reportSee “Emailing a report” on page 554.

Saving a reportYou can save a standard report. This saves the filters that you have selected whilegenerating a report. You can use this set of filters to regenerate the reports withthe current time selections.

These reports are saved in the OpsCenter database, which you can view using theMy Reports tab.

See “Managing My Reports” on page 557.

To save a report

1 In the OpsCenter console, click Reports > Report Templates.

2 From the Reports tree, select the report template that you want to save.

3 In the report view area at the right-hand side, click the Save As Report icon.This opens the Save Report pop-up screen.

551Reporting in OpsCenterManaging reports

4 On the Save Report screen, enter the following information:

Enter the report name. For example, if youhave generated the Job Count standard

Report name

report with the group by option selectedas Policy Type, and report view asHistorical, you can name this report as:NumberofJobsbyPolicies

When you select this report on the SavedReports tab, the report is displayed withthe saved filters and in the report viewthat were selected when the reports weresaved, with respect to the current time.

Note: Report name should be uniqueacross the report tree.

Enter the short description for the report.Description

Select Public or Private folder. If you savethe report in a public folder, all other

Folder

OpsCenter users can view it. If you savethe report in a private folder, only you canview it.

Expand the Public or Private folder andselect a folder where you want to save thereport. Depending on the folder type thatyou have selected - public or private - thefolders displayed for selection vary.

Click this button to create a new public orprivate folder. Clicking on this button

Create New

changes the view of Folder. Enter thefolder name and click OK.

This folder is made available in the Foldertree for selection. Select this newlycreated folder where you want to save thereport.


552

Select this check box if you want tooverwrite the existing report with thesame name in the same folder. If you donot select this check box and save a reportwith a name same as any of the existingreports in the selected folder, aconfirmation message is displayed beforeyou overwrite the existing report.

Overwrite if file exists

5 Click OK.

After a successful save, My Reports tab is displayed with this report selected.

Exporting a reportUsing OpsCenter, you can preserve report data in files or print the data.

See “ About file formats available in OpsCenter” on page 553.

You can open the exported file using other applications, such as a spreadsheetprogram or a text editor.

To export a report


2 From the Reports tree, select the report template that you want to export.

3 In the report view area at the right-hand side, click the Export Report icon.This opens the Export Report pop-up screen.

4 On the Export Report pop-up screen, select the export options that you wantto export the report with: File format, such as PDF, CSV, or XML and contentor report view, such as Distribution, Historical, or Ranking.

5 Click OK. The system displays the export options pertaining to the file formatyou have selected. Select those options and export the report.

About file formats available in OpsCenterYou can export or email OpsCenter reports in the following file formats:

Can be viewed using a PDF reader, such as Adobe ReaderPDF (PortableDocument Format)

Use with spreadsheet programs, such as MS Excel.CSV (comma-separatedvalues)

553Reporting in OpsCenterManaging reports

Compatible with word-processing applications and text editorsTSV (tab-separatedvalues)

Can be opened using with Web browsersHTML (hypertextmarkup language )

Can be imported (using user-written scripts) by other programslike databases or billing applications

XML (ExtensibleMarkup Language)

Emailing a reportUsing OpsCenter, you can email report data to the selected recipients. You canemail a report in a number of different file formats.


To email a report


2 From the Reports tree, select the report template that you want to email.

3 In the report view area at the right-hand side, click the Email Report icon.This opens the Email Report pop-up screen.

4 On the Email Report pop-up screen, select the email options: File format, suchas PDF, CSV, or XML and content or report view, such as Distribution,Historical, or Ranking.

5 Enter email IDs in To, Cc, and Bcc text boxes, to which you want to sendemails.

If these email IDs do not already exist, they are automatically added to thedatabase.

Alternatively, you can add existing email recipients.

See “Adding email recipients” on page 554.

6 Enter the subject of the email.

7 Enter the message that may be a short description regarding the report datathat you want to email.

8 Click OK.

Adding email recipientsThis section provides information on how to add email recipients to whom youwant to send emails.


554

To add email recipients

1 On the Add Email Recipients screen, select the check boxes in front of theemail recipients to whom you want to send emails.

click To.., Cc.., or Bcc.. depending on where you want to add the selectedrecipients.

2 Click OK.

Creating a custom reportThis section provides the procedure to create a custom report. This feature isaccessible only to the Symantec OpsCenter Analytics users. This option is disabledin the unlicensed OpsCenter version.

To create a custom report


2 On the Report Templates tab, click Create New Report.

3 On the Report Wizard, select the ‘Create a custom report’ option and clickNext.

4 Select the report category and view type and click Next.

5 Select time frame and other filters as required and click Next.

6 Add conditions as follows:

■ Select a report column.

■ Select an operator.

■ Select a range of value. Select low threshold and high threshold values.See “About report conditions” on page 555.

■ Click Add.

When the specified condition is met, a notification is sent to the concernedperson.

7 Click Next.

About report conditionsIn the Conditions section of the Custom Report Wizard, specify conditions fornotification. Conditions represent potential problems, for example an unusuallyhigh percentage of backup job failures or an unusually low quantity of data beingbacked up. Each exception condition is defined by assigning threshold values fora particular metric, such as Success Rate or Total Backup Job Size. You can set a

555Reporting in OpsCenterCreating a custom report

low threshold, a high threshold, or both. Select a condition while generating acustom report, so that when a condition is true, an alert is triggered or an emailnotification is sent.

As an example, you can define a backup report with the following conditions:

■ Success Rate: Low threshold 80%The condition is met whenever the success rate falls below 80 percent.

■ Total Backup Job Size: Low threshold 500 GB, high threshold 1000 GBThe condition is met whenever the total size of backed-up data falls outsidethe range of 500-1000 GB.

Creating a report using SQL queryThis section provides the procedure to create a report using SQL query.

Only Symantec OpsCenter Analytics users can access the custom SQL queryfunction.

Note:OpsCenter Analyst and Reporter do not have access to the custom SQL queryoption.

Caution: Make sure about the impact that the entered SQL query has on theOpsCenter database before running it.

To create a report using SQL query


2 On the Report Templates tab, click Create New Report.

3 On the Report Wizard, select the ‘ Create a report using SQL Query’ optionand click Next.

4 On the SQL Query page, enter an SQL query to view the required data.

For example, to view all NetBackup master servers that are monitored andmanaged by OpsCenter, enter the following SQL query: select * fromdomain_masterserver

5 Click Next.

You can view all master server details that are stored in the‘domain_masterserver’ database table.

Reporting in OpsCenterCreating a report using SQL query

556

Managing My ReportsYou can save generated reports for your future use. These saved reports are storedin the My Reports tab. Use this section to view the saved reports or modify theparameters of the saved reports and generate new reports out of them. You canalso delete the saved reports using the My Reports tab.

Creating a report using My Reports tabThis section provides the procedure to create a report using My Reports tab.

To create a report

1 In the OpsCenter console, click Reports > My Reports.

2 On the My Reports tab, click Create New Report.

You can create a report in any of the following ways:

See “Creating a report using a Report Template ” on page 550.

See “Creating a custom report” on page 555.

See “Creating a report using SQL query” on page 556.

Deleting a saved reportThis section provides the procedure to delete a saved report.

To delete a saved report


2 On the My Reports tab, from the reports list, expand a report folder to viewthe reports that are saved within it.

3 Select the check box in front of the report name.

4 Click Delete.

Viewing a saved reportYou can view the saved reports using the My Reports tab.

To view a saved report


2 On the My Reports tab, from the reports list, expand a report folder to viewthe reports that are saved within it. Select the saved report that you want toview.

557Reporting in OpsCenterManaging My Reports

Editing a saved reportYou can edit a saved report. You can edit the report details, such as the reportname or the folder where you want to save the edited report.

To edit a saved report


2 On the My Reports tab, from the reports list, expand a report folder to viewthe reports that are saved within it. Select the saved report that you want toedit.

3 In the report view area at the right-hand side, click the Save As Report icon.This opens the Save Report pop-up screen.

Reporting in OpsCenterManaging My Reports

558

4 On the Save Report screen, enter the following information:

Enter a new name for the report.

When you select this report on the SavedReports tab, the report is displayed withthe saved filters and in the report viewthat were selected when you saved thereports, with respect to the current time.

Report name

Enter short description for the report.Description

Select Public or Private folder. If you savethe report in a public folder, all otherOpsCenter users can view it. If you savethe report in a private folder, only you canview it.

Expand the Public or Private folder andselect a folder where you want to save thereport. Depending on the folder type thatyou have selected - public or private - thefolders displayed for selection vary.

If you do not select any folder, the reportis saved on the root.

Folder

Click this button to create a new public orprivate folder. Clicking on this buttonchanges the view of Folder. Enter thefolder name and click OK.

This folder is made available in the Foldertree for selection. Select this newlycreated folder where you want to save thereport.

Create New

Select this check box if you want tooverwrite the existing report with the newchanges. If you do not select this checkbox and attempt to save the report withthe existing report name, the systemdisplays an alert message. You need toeither overwrite the existing report orsave it with a different name.


5 Click OK.

559Reporting in OpsCenterManaging My Reports

Export a saved reportUsing OpsCenter, you can preserve saved report data in files or print the data.You can email a report in a number of different file formats.


You can open the exported file using other applications, such as a spreadsheetprogram or a text editor.

To export a saved report


2 On the My Reports tab, from the reports list, expand a report folder to viewthe reports that are saved within it. Select the saved report that you want toexport.

3 In the report view area at the right-hand side, click the Export Report icon.This opens the Export Report pop-up screen.

4 On the Export Report pop-up screen, select the export options that you wantto export the report with. Select file format, such as PDF, CSV, or XML andcontent or report view, such as Distribution, Historical, or Ranking.

5 Click OK. The system displays the export options pertaining to the file formatyou have selected. Select those options and export the saved report.

Email a saved reportUsing OpsCenter, you can email the saved report data to the selected recipients.You can email the report in the following file formats:

Can be viewed using a PDF reader, such as Adobe ReaderPDF (PortableDocument Format)

Use with spreadsheet programs, such as MS Excel.CSV (comma-separatedvalues)

Compatible with word-processing applications and text editorsTSV (tab-separatedvalues)

Can be opened using with Web browsersHTML (hypertextmarkup language )

Can be imported (using user-written scripts) by other programslike databases or billing applications

XML (ExtensibleMarkup Language)

Reporting in OpsCenterManaging My Reports

560

To email a report

1 In the OpsCenter console, click Reports > Saved Reports.

2 On the My Reports tab, from the reports list, expand a report folder to viewthe reports that are saved within it. Select the saved report that you want toemail.

3 In the report view area at the right-hand side, click the Email Report icon.This opens the Email Report pop-up screen.

4 On the Email Report pop-up screen, select the email options: File format, suchas PDF, CSV, or XML and content or report view, such as Distribution,Historical, or Ranking.

5 Enter email IDs in To, Cc, and Bcc text boxes, to which you want to sendemails.

6 Enter the subject of the email.

7 Enter the message that may be a short description regarding the report datathat you want to email.

8 Click OK.

Managing My DashboardYour saved reports are preserved in My Reports tab, which you can select andpublish on My Dashboard tab. You can select multiple reports and add them inthe same dashboard section. Thus, you can create multiple dashboard sectionscontaining a number of reports.

You can add only 10 reports in a dashboard.

See “Adding reports to a dashboard” on page 561.

See “Modifying a dashboard section” on page 562.

See “Deleting a dashboard section” on page 562.

See “Emailing dashboard sections” on page 563.

See “Refreshing My Dashboard” on page 563.

Adding reports to a dashboardThis section provides the procedure to add reports to a dashboard.

561Reporting in OpsCenterManaging My Dashboard

To add reports to a dashboard

1 In the OpsCenter console, click Reports > My Dashboard.

2 Click Add.

3 On the Add Dashboard Section pop-up screen, enter the section name.

4 Expand the Private or Public Reports folder to view existing reports.

5 Select the check boxes in front of the report names, which you want to publishon the dashboard.

6 Click OK.

Modifying a dashboard sectionThis section provides the procedure to modify dashboard section.

To modify a dashboard


2 Click Edit.

3 On the Edit Dashboard Section pop-up screen, select the dashboard sectionfrom the drop-down list, that you want to modify.

4 Modify the section name.

5 Expand the Private or Public Reports folder to view existing reports.

6 Select or clear the check boxes in front of the report names, which you wantto publish on or remove from this dashboard section.

7 Click OK.

Deleting a dashboard sectionThis section provides the procedure to delete a dashboard section.

To delete a dashboard section


2 Click Delete.

3 On the Delete Dashboard Section pop-up screen, select the dashboard sectionfrom the drop-down list, that you want to delete.

4 Click OK.

Reporting in OpsCenterManaging My Dashboard

562

Emailing dashboard sectionsYou can email your dashboards.

To email a dashboard


2 Click the Email Dashboard icon.

3 On the Email Dashboard pop-up screen, select the format in which you wantto send the email.

4 Select email recipients from the To.., Cc.., and Bcc.. as appropriate.

Alternatively, enter new email recipients, which are added into the database.

5 Enter the email subject and message.

6 Click OK.

Refreshing My DashboardThis section provides the procedure to refresh My Dashboard.

To refresh My Dashboard


2 Click the Refresh icon.

Managing foldersOpsCenter provides a way to manage folders where you have saved your reports.They can be both private or public reports.

Using the Manage Folders tab in the Reports section, you can add new reportfolders, edit names of the existing folders, or delete them.

You can also select reports in a particular folder and delete them using this tab.

See “Adding a folder” on page 563.

See “Editing a folder” on page 564.

See “Deleting folders” on page 565.

See “Deleting reports from a folder ” on page 565.

Adding a folderThis section provides a procedure to add a report folder.

563Reporting in OpsCenterManaging folders

To add a folder

1 In the OpsCenter console, click Reports > Manage Folders.

2 On the Reports tree, select a check box in front of a private or public foldernode in which you want to create a new folder.

3 Click Add. This displays the Create new folder pop-up window.

Make sure that you have selected only one folder. If multiple folders areselected, the Add button is disabled.

4 Enter the folder name.

5 Click OK.

This folder is added in the selected node.

Editing a folderThis section provides a procedure to edit a report folder.

To edit a folder


2 On the Reports tree, select a check box in front of a private or public folderthat you want to edit.

3 Click Edit. This displays the Edit folder name pop-up window.

Make sure that you have selected only one folder. If multiple folders areselected, the Edit button is disabled.

4 Edit the folder name.

5 Click OK.

Reporting in OpsCenterManaging folders

564

Deleting foldersThis section provides a procedure to delete a report folder. If you delete a reportfolder, all reports that are saved in that folder are deleted.

To delete folders


2 On the Reports tree, select a check boxes in front of private or public foldersthat you want to delete.

3 Click Delete.

Deleting reports from a folderThis section provides a procedure to delete reports that are saved in a public orprivate folder.

To delete reports from a folder


2 On the Reports tree, select a private or public folder from which you want todelete the reports. This displays a list of reports that are saved in the selectedfolder, at the right-hand side of the page.

3 From the list of reports, select the check boxes in front of the reports thatyou want to delete.

4 Click Delete.

About schedulesUsing report schedules, you can email or export reports at a scheduled time. Eachreport schedule is associated with a time schedule at which it emails or sends thespecified reports.

OpsCenter provides a wizard to create a report schedule.

See “Creating a report schedule” on page 568.

The following table describes the steps that you need to carry out to email orexport a report on a specific schedule. This is a suggested flow of steps.

See “Managing time schedules” on page 572.

565Reporting in OpsCenterAbout schedules

Table 12-2 Creating a report schedule


See “Creating a time schedule”on page 572.

Create a time schedule.1

See “Creating a report schedule”on page 568.

Create a report schedule.

OpsCenter provides a wizard to createa report schedule. This wizard lets youspecify the following details:

■ Report schedule name

■ File format in which you want toemail or export reports

■ Select a time schedule.

You can either select an existingtime schedule that you have createdin the first step or create a newschedule from here to associate itwith this report schedule.

■ Specify details of export or emailoptions.

■ Select the reports that you want toexport or email on a specificschedule.

Note: You can select only savedreports in a schedule.

2

Managing report schedulesNetBackup OpsCenter provides you a way with which you can export or email areport on a specific schedule. For this you need to create a report schedule thatis associated with a time schedule on which the specified reports are exported oremailed.

Each report schedule can be associated with a single time schedule. A single timeschedule can be associated with multiple report schedules.

See “Managing time schedules” on page 572.

This section describes how to create and manage report schedules.

Viewing report schedule detailsThis section provides information on viewing the list of report schedules.

Reporting in OpsCenterManaging report schedules

566

If you have applied conditions for the selected report, the list of applicableconditions is shown on the last page of the wizard. You can select the appropriateconditions. An email notification is sent to the relevant recipients if the selectedcondition is satisfied.

To view a report schedule

1 In the OpsCenter console, click Reports > Schedules.

By default, the Report Schedules tab is selected.

2 On the Report Schedules tab, view the following report schedule details.

Name of a report scheduleName

Name of a time schedule that is associated with thisreport schedule

Time Schedule Name

Date on which this schedule runsStart Date

Date on which this schedule stopsEnd Date

Specifies whether you have exported the associatedreports

Export

Specifies whether you have emailed the associatedreports

Email

Number of the reports that are exported or emailed whenthis schedule runs

Reports

567Reporting in OpsCenterManaging report schedules

Creating a report scheduleTo create a report schedule


2 On the ReportSchedules tab, click Create. OpsCenter provides a wizard thatguides you through the procedure of creating a report schedule.

The Enter Report Schedule Details page appears as follows:

Enter the following report schedule details:

Enter report schedule name. This is amandatory field.

Report Schedule Name

Select a file format in which you want toexport or email report the associatedreports.

See “ About file formats available inOpsCenter” on page 553.

Select Format


568

3 Click Next.

The following page appears:

Select the Use existing schedule option if you want to run this schedule onany existing time schedule. If you want to create a new time schedule for thisreport schedule, select Create new time schedule.

See “Creating a time schedule” on page 572.

If you have selected Create new time schedule, the system takes you to theTime Schedule creation wizard. After creating a time schedule you can selectthe export and the email report options.

4 Click Next.


5 If you have selected the Use existing schedule option in the previous step,the Configure Export / Email Report Settings page, specify the followingdetails:

You can either select Export, Email, or both options.

Select this check box if you want to exportthe reports that are associated with thisschedule.

See “ About file formats available inOpsCenter” on page 553.

Export

Enter a directory path where you want tosave the exported report or click Browseto select the desired location.

Location

Select this check box if you want tooverwrite a file that already exists at thespecified location.


Select this check box if you want to emailthe reports that are associated with thisschedule.

Email

Select email IDs to which you want toemail reports.

To

Select email IDs to add in the Cc list ofemail.

Cc

Select email IDs to add in the Bcc listemail.

Bcc

Type the email subject. For example: DailyJob Count Report

Subject

Type any other related information.Message

6 Click Next.


570

7 Select the reports that you want to export or email on this schedule.

These reports should be saved.

Click Back if you want to change the previous selections.

8 Click Save.

Editing a report scheduleThis section describes how to edit report schedule details.

To edit a report schedule



2 On the Report Schedules tab, select a report schedule from the list that youwant to edit.

3 Click Edit.

4 Edit the report schedule details using the wizard.

5 Click Save.

Deleting a report scheduleThis section describes how to delete a report.


To delete a report schedule



2 On the Report Schedules tab, select a report schedule from the list that youwant to delete.

3 Click Delete.

Managing time schedulesThis section provides procedures to create and manage a report schedule.

Each report schedule can be associated with only a single time schedule. A singletime schedule can be associated with multiple report schedules.

See “Managing report schedules” on page 566.

Viewing time schedule detailsThis section provides a procedure to view the details of time schedules.

To view a time schedule


2 Click Time Schedules.

The following time schedule details appear:

Name of the time scheduleName

Time when the associated reports areexported or emailed

Schedule Time

A pattern with which this schedule runsRecurrence Pattern

Date when the schedule startsStart Date

Date when the schedule stopsEnd Date

Creating a time scheduleTo edit a time schedule



Reporting in OpsCenterManaging time schedules

572

3 On the Time Schedules tab, click Create.

4 On the Create Time Schedule page, specify the following details:

Enter name of the time schedule.Schedule Name

Enter the time when the schedule runsand the associated reports are exportedor emailed.

Schedule Time

Select a pattern with which you want thisschedule to be run.

The following schedule patterns areavailable:

■ One Time

■ Daily

■ Weekly

■ Monthly

■ Quarterly

■ Yearly

Depending on the pattern selected,options change.

Schedule Pattern

5 Click OK.

Editing a time scheduleTo edit a time schedule



3 On the TimeSchedules tab, from the table, select the time schedule that youwant to edit.

4 Click Edit.

5 Edit the time schedule details.

6 Click OK.

573Reporting in OpsCenterManaging time schedules

Deleting a time scheduleTo delete a time schedule



3 On the Time Schedules tab, from the table, select the time schedules thatyou want to delete.

4 Click Delete.

About Report Templates descriptionsThis section provides descriptions of all Report Templates available in OpsCenter.

A few important notes on the OpsCenter Report Templates :

■ The Week at a glance, Drive Throughput, and Drive Utilization reports can beexported and emailed only in the HTML format.The Week at a glance report does not display graphics when it is emailed orexported in an HTML format.

■ A tabular report that is scheduled for emailing can have up to 4000 rows.

■ Reports in the PDF, TSV, or CSV formats are sent as email attachments.

■ A report in the HTML format is sent as an inline message in email.

■ Sorting for HTML based reports (for example, Drive Utilization) is notsupported.

■ For the OpsCenter admin, the default view that is selected is All_Master_Server.

See “About Enterprise Vault Archiving reports” on page 575.

See “About Backup reports” on page 577.

See “About Catalog reports” on page 592.

See “About Chargeback reports” on page 592.

See “About Client reports” on page 593.

See “ About Disk and Tape Device Activity reports” on page 599.

See “ About Media reports” on page 602.

See “About Performance reports” on page 605.

See “About Policy reports” on page 608.

See “ About Restore reports” on page 610.

Reporting in OpsCenterAbout Report Templates descriptions

574

About Enterprise Vault Archiving reportsThis section provides descriptions of archive Report Templates available inOpsCenter.

Archive Storage > Archived CountThis report shows the number of messages or items that were archived acrossvault servers, sites, archive targets, provisioning groups, and business level views.

Archive Storage > Tabular - Storage ReportThe Storage Details report shows details of archive the data that is stored invarious Vault Stores and Vault Partitions.

The Archived Size report is available in the Archive Storage report category.

Archive Storage > Archived SizeThis report is available only in the Archive Storage report category. Use this reportif you want to determine the size of the Exchange Server data that was archived.You can determine how much is the size of the Exchange Server data that wasarchived and is stored in a specific Vault Store, Enterprise Vault Server, or VaultStore Partition.

The Archived Size report is available in the Archive Storage report category.

The Archive Size Vs Original Size report depicts the difference between the twosizes of Exchange Server data. The more the difference, the more efficient is yourarchival process.

Exchange > Mailbox QuotaThe Mailbox Quota report displays the top mailboxes in Exchange Server, whichhave exceeded a particular mailbox size limit. This report is available in theRanking report view.

There are three types of Mailbox Quota reports:

This report shows the mailboxes that have exceeded the Warninglimit set in Exchange Server.

The Warning limit is a limit set for mailboxes, which decides howmuch data mailboxes can contain.

For example: The Warning limit for mailboxes is set to 256 MB.The By Warning Limit report displays all mailboxes that haveexceeded 256 MB of data.

By Warning Limit

575Reporting in OpsCenterAbout Report Templates descriptions

This report shows the mailboxes that have exceeded the Sendlimit set in Exchange Server.

The Send limit is a limit set for mailboxes, which is greater thanthe Warning limit. If size of a mailbox exceeds this limit, emailscannot be sent from this mailbox.

By Send Limit

This report shows the mailboxes that have exceeded the Receivelimit.

If size of your mailbox exceeds the Receive limit, you cannotreceive any emails.

By Receive Limit

The Mailbox Quota reports are available in the Exchange report category.

Exchange > Archive Size Vs Original SizeThis report provides the comparison between original size and archived size ofExchange Server data. using the report, you can determine how much was theoriginal size of the data that was archived later. The difference between originalsize and archived size is termed as savings. If the savings are more, it implies thatdata was archived in a very efficient way and thus, lesser storage space wasrequired.

The Archive Size Vs Original Size report is available in the Exchange reportcategory.

Target Server is selected as the Report On parameter.

Exchange > Item CountThis report is available in both archive report categories, Exchange and ArchiveStorage. Use this report to determine the number of emails or items in eachExchange Server in an Enterprise Vault environment.

The Item Count report is available in all three graphical views, Historical, Ranking,and Distribution. This report provides different drill-down reports depending onthe archive report category that you have selected.

Exchange > Target Report DetailThe Target Details report shows details of all mailboxes in all Exchange Serversin an archive site. The word Target refers to individual mailboxes. The details inthe report includes the name of a mailbox, original size of emails in a mailbox(Item Original Size), archived size of emails (Item Archived Size), number of emails(Target Item Count), and so on.


576

Exchange > Original SizeThis report is available only in the Exchange report category. Generate this reportif you want to determine the original size of the Exchange Server data that wasarchived. You can view the original size of the archived data for a specific archivesite or Exchange Server. You can also determine how much was the original sizeof the data that was archived and has been stored in a specific Vault Store,Enterprise Vault Server, or Vault Store Partition. You can select these filters usingthe Advanced Filters option on the Report Wizard page.

The Original Size report is available in all three graphical views, Historical,Ranking, and Distribution.

The following example explains about the original size of the data that wasarchived:

■ You have 100 MB of Exchange Server data, which is the total mailbox size

■ Out of 100 MB data you want to archive 30 MB, as per the definition in anarchive policy

■ After archiving, the 30 MB data is compressed into 20 MB data

■ The Original Size of Exchange Server data was 30 MB and Archived Size isnow 20 MB

■ The total savings are equal to the difference between the Original Size andArchived Size. Total Savings = 30 MB - 20 MB = 10 MBBy archiving, you can save on huge amount of storage space.

About Backup reportsThis section provides descriptions on all backup Report Templates available inOpsCenter.

Deduplication > Deduplication Size Factor > HistoricalThis report is usually the most talked about when it comes to deduplication sinceit shows what the deduplication ratio is for each day over the last two weeks (thetime frame is modifiable). The deduplication ratio is calculated by taking the totalnumber of bytes that would normally be backed up and dividing it by the numberof bytes that have changed and were backed up. So if 100TB exists on all thebackups taking place but only 10TB were changed and therefore transferred youwould have a rate of 10.

This report shows only deduplication jobs. The default Report On parameter forthis report is Master Server.

This report is available in a line-chart format.


Deduplication > Deduplication Size Factor > RankingsThis deduplication report ranks the top hosts in terms of which ones have thebest deduplication ratio in bytes. These hosts have the least amount of changeand therefore you get the best benefit from deduplication.


Deduplication > Pre vs. Post Deduplication SizeThe report gives the comparison between the total number of bytes that exist onall the backups as if they were normal full backups and the number of bytes thathave changed and therefore needed to be transferred.

This report shows only deduplication jobs. The default Report On parameter forthis report is All Master Servers.

Deduplication > Deduplication Size Savings > HistoricalThis report shows the total number of bytes that do not need to be backed upbecause of deduplication. There is no calculation or ratio in this number, it is thenumber of bytes (MB, GB, TB etc.) that have not changed since the last backupand therefore don’t need to be backed up.


Deduplication > Deduplication Size Savings > RankingsThis report shows the number of bytes that have not changed within the timeframe and therefore do not have to be backed up due to deduplication. The reportgroups the total number of bytes saved per host being backed up to show the topfive hosts in terms of deduplication savings.


Job Activity > Variance > About Throughput Variance reportThis report provides an indication of how throughput (in MB per second) for abackup varies from the average throughput for a particular policy, client, andschedule type. You can detect any anomalies if the variation is too high.

This report calculates the backup throughput variation of the last good backupwith the average backup throughput per a server, client, policy, and schedule type.


578

If any variation calculation is greater than the selected value of variance whenthe report is run, the client, policy and schedule type combination is shown in thetable with the actual variation.

The Client Name column of the report provides a drilldown link to back up jobdetails for the specified time frame.

Job Activity > Variance > About File Count Variance reportThis report lets you investigate why a particular full backup is different thanusual. For example, a file server backup is successful, but contains fewer files thanusual for a full backup.

The report shows NetBackup jobs with significant differences in file counts fromthe average count for a master server, policy, and schedule.

If any variation calculation is greater than the selected value of variance whenthe report is run, the server, client, policy, and schedule type combination is shownwith the actual file count variation. The table provides the percent variance (infile counts) for each good job from the average for that server, policy, and schedule.


Job Activity > Variance > About Backup Duration VariancereportThis report provides an indication of how backup time varies from the averagebackup time. You can detect any anomalies if the variation is too high.

This report calculates the backup time variation of the last good backup with theaverage backup time per client, policy, and schedule type. If any variationcalculation is greater than the selected value of variance when the report is run,the client, policy, and schedule type combination is shown with the actual variation.

About client jobs for selected time frame report

This drilldown report from the Client Name column provides detailed jobinformation for the client for the selected time frame.

This drilldown report uses the run time parameters that are passed from the mainreport.

Job Activity > Variance > About Backup Job Size VariancereportThis report provides an indication of how a backup size varies from the averagesize. You can detect any anomalies if the variation is too high.


This report calculates the backup size variation of the last good backup with theaverage backup size per a client, policy, and schedule type. If any variationcalculation is greater than the selected value of variance when the report is run,the client, policy and schedule type combination is shown with the actual variation.

Size variance is calculated using the following formula: (the last backup size - theaverage backup size) / the average backup size x 100.


Job Activity > Backup Window > Job CountThis report shows the total number backup jobs in the last two weeks shown bythe hour of the day in which each job ends. It also renders a configurable backupwindow to help quickly identify if a lot of jobs end in or outside of what yourbackup window is or should be. The report can help you see if there are any hourswithin the backup window that are under utilized and whether any load balancingis appropriate.

In OpsCenter, the Job Count report does not include the jobs that were collectedduring the image data collection. These jobs are called Sparse Jobs. This is unlikethe Job Count report in VBR, which also included Sparse Jobs. Because of thischange, you may notice a mismatch between the job count on the OpsCenter reportand the corresponding VBR report.

Job Activity > Backup Window > Job SizeThis report shows the total gigabytes backed up in the last two weeks shown bythe hour of the day in which each job ends. It also renders a configurable backupwindow to help quickly identify if a lot of jobs end in or outside of what yourbackup window is or should be. The report can help you see if there are any hourswithin the backup window that are under utilized and whether any load balancingis appropriate.

Job Activity > Backup Window > File CountThis report shows the number of files that were backed up for each hour of theday. The height of each bar on the graph is the total number of files that are backedup for that hour across the entire date range selected. A user defined backupwindow is drawn in yellow for example to compare with what hours the filesshould have been backed up in. Bars outside of the yellow window represent theactivity that occurred outside of the backup window. The report can also be usedto see what hours may have capacity to add more backups while still remainingin the backup window.


580

Job Activity > Job Count > DistributionThis report gives you a breakdown of the number of jobs that are performed byeach media server in your environment. It highlights how busy each of your mediaservers are and if any type of load balancing between your media servers couldspread the workload.

Job Activity > Job Count > HistoricalThis report shows you the total number of backed jobs that are performed foreach day in the last two weeks. Unexpected variations in this report betweenyou're day-to-day incremental or between full backup cycles can indicate problems.

Job Activity > Job Count > RankingsThis report shows you the top 10 largest environments by ranking the total numberof jobs that are performed by each media server for the past two weeks.

Job Activity > Job Size > HistoricalThis report shows you the total gigabytes backed up for each day in the last twoweeks. Unexpected variations in this report between your day-to-day incrementalor between full backup cycles can indicate problems.

Job Activity > Job Size > RankingsThis report shows you the top 10 largest backup clients by ranking them on thetotal number of gigabytes backed up for that client in the specified time frame.The report can give you an idea of your top consumers and whether thoseconsumers are what you expected.

Job Activity > Job Size > DistributionThis report gives you a breakdown by each media server of the total gigabytesthey’ve backed up over the specified time frame. It shows you a very cleardistribution of the amount of data going to all your media servers and whetherany type of load balancing might be beneficial.

Job Activity > Client Count > HistoricalThis report shows the total number of unique clients that are backed up per dayfor the specified time frame broken down by each master server. It can help youhighlight potential problems by showing any variations in the number of clientsthat you think should be backed up and how many are in fact getting backed up.


Job Activity > Client Count > RankingThis report shows you the top 10 largest environments by listing the number ofunique clients that got backed up per each media server in your environment forthe specified time frame.

Job Activity > Client Count > DistributionThis report gives you a breakdown by each master server of the number of uniqueclients that got backed up in the specified time frame.

Job Activity > Job Duration > RankingThis report shows you the top 10 highest clients that are ranked by the totalamount of time they were backed up for specified time frame.

Job Activity > File Count > HistoricalThis report shows you the total number of files that got backed up for each dayin specified time frame for each of your master servers. Unexpected variationsin this report between your day-to-day incremental or between full backup cyclescan indicate problems.

Job Activity > File Count > RankingThis report shows you the top 10 largest backup clients by ranking them on thetotal number of files that were backed up for them for specified time frame.

Job Activity > File Count > DistributionThis report gives you a breakdown by each master server of the total number offiles that got backed up in specified time frame.

Job Browser > Tabular Backup ReportThis report shows you a detailed listing of all the backup activity that is performedfor the past two weeks. You can edit the report to show or hide the columns youare interested in. You can also filter the report to show activity for a limited sampleset, such as one or more policies or clients.

Planning Activity > Capacity Planning > Forecasted SizeThis report shows the supply vs. demand historically but now also adds a forecastline for both supply and demand that can show when in the future they may meet.The point that these two lines intersect would be the date that new capacity (more


582

disk or more backup tapes) needs to be added. In the above example the supply isby far outgrowing the demand, which would suggest that more capacity does notneed to be purchased. The default first view of this report shows the entire backupenvironment but for actual use it should be filtered to a specific tape library ordisk pool since some libraries or pools may be closer to full capacity than others.

Planning Activity > Capacity Planning > Historical SizeThis report shows the historical supply vs. demand. Supply is defined as allavailable free space on all the backup media in the backup application. For diskthis is an exact calculation of remaining free capacity. For tape this number iscalculated by taking the average size of all full media of the same tape type. Thataverage is then used for the predicted size of all other tapes that are not full ofthe same type. This is necessary since tapes do not have an exact capacity andare written to until the end of tape mark. On the demand side this is a calculationof all backup jobs for the time period. The idea for this report is that the differencebetween the two lines is the extra capacity that was not needed. In an idealenvironment these lines will match the blue line, for example, being slightly underthe line showing that all the space for backups is used. This report can sometimesbe referred to as the “just in time inventory” report since the concept was derivedfrom the business theory by the same name. The default is to show the totalenvironment but for operational use it would need to be filtered down to individualstorage locations since some can be closer to 100% capacity than others. This canbe easily done by clicking on “edit” at the top of the report.

Planning Activity > Forecast > Job CountThis report shows you the total number of backup jobs for each day in specifiedtime frame. A linear regression forecast is also performed to show you how manybackups you can expect to be do for the next three days based on the current data.

Planning Activity > Forecast > Job SizeThis report shows you the total gigabytes backed up for each week in the past twomonths. A linear regression forecast is also performed to show you how muchyou can expect to be back up for the next few weeks on the current data.

Planning Activity > Scheduled Job > Scheduled JobThis report is available in ranking report view, which depicts how many jobs havebeen scheduled to run in future. You can view the Scheduled Jobs per schedule,policy, master server, or client.


Note:By default, the Scheduled Jobs report shows job count per policy. If you wantto view the job count for clients, schedules, or master servers, change the reportparameters.

To change the report parameters

1 On the Scheduled Jobs report, click the Edit link.

2 On the Report Wizard, from the Report On drop-down list, select a ScheduledJob attribute. For example: Client, Master Server, Policy, or Schedule Name.

3 Click Run.

Note: To view job count for a specific client, policy, master server, or schedule,click ShowAdvancedFilters and select name of the client, policy, master server,or schedule, for which you want to view job count.

Planning Activity > Scheduled Job > Job Count Scheduled VsActualThis historical report depicts how many jobs were scheduled to run in future andhow many jobs are run. The report essentially shows the comparison betweenScheduled (Future) Job Count and Actual Job Count.

Using this report you can determine whether the jobs that were scheduled to runin future have been run on schedule.

By default the Actual Job Count includes manual jobs, which were initiatedmanually by NetBackup admin. To exclude manual jobs from the Actual Job count,and view only those jobs that have execution type as ‘Scheduled’, do the following:

To exclude manual jobs from the actual jobs

1 On the Job Count-Scheduled Vs Actual report, click the Edit link.

2 On the Report Wizard, in the Filter Options section, select “Yes” from theExclude Manual Jobs drop-down list.

3 Click Run.

Planning Activity > Scheduled Job > Job Count within BackupWindowThis historical report depicts how many jobs were scheduled and how many jobshave been run within the specified backup window. The report essentially showsthe comparison between Scheduled (Future) Job Count and Actual Job Count,during the backup window.


584

Use this report to determine whether your backup windows are appropriate andare properly used.

Planning Activity > Scheduled Jobs > Job Details ScheduledVs ActualThis tabular report shows the comparison between Scheduled Job count and ActualJob count for each of the combinations of clients, policies, and schedules, for eachday.

Note: By default, the Job Count Details-Scheduled Vs Actual report shows jobcount per policy. If you want to view the job count per client or master server,change the filter parameters.

To change the report parameters

1 On the Job Count Details-Scheduled Vs Actual report, click the Edit link.

2 On the Report Wizard, in the Define Viewable Columns section, select a columnname (Client or Master Server) from the Available Columns list.

3 Click >> button.

4 Click Run.

Note: To view job count for a specific client, policy, master server, or schedule,click Show Advanced Filters and select name of the policy, master server, orschedule, for which you want to view job count.

By default the jobs that were run (Actual Job Count) include manual jobs, whichdo not have any schedule time associated with them as they are initiated manually.You can exclude manual jobs from the actual job count, and view only the jobsthat are of execution type ‘Scheduled’.

To exclude manual jobs from the actual jobs

1 On the Job Count Details-Scheduled Vs Actual report, click the Edit link.

2 On the Report Wizard, in the Filter Options section, select Yes from theExclude Manual Jobs drop-down list.

3 Click Run.

The Job Count Details-Scheduled Vs Actual report shows comparison betweenScheduled Job count and Actual Job count. The Actual Job count includes ManualJobs.


Planning Activity > Scheduled Job > All JobsThis canned report shows jobs in a tabular form, which include the following:

These jobs are initiated manually, by NetBackup admin at his orher discretion. Therefore, these jobs do not have schedule timeassociated with them.

Note:While generating the Job Count-Scheduled Vs Actual report,you have an option to exclude the manual jobs from the actual jobcount and show only those jobs that are of execution type‘Scheduled’.

See “Planning Activity > Scheduled Job > Job Count Scheduled VsActual” on page 584.

Manual Jobs

These jobs are scheduled to run in future. Each Scheduled Jobinformation comprises a client, policy, schedule, and scheduletime. OpsCenter stores this information historically. EachScheduled Job when run on the specified schedule time becomesan actual job of execution type ‘Scheduled’. Thus, a Scheduled Jobhas a corresponding actual job entry in OpsCenter database. Thisparticular Scheduled Job can be identified by the uniquecombination of client, policy, schedule, and schedule time. Youcan compare the schedule time of this Scheduled Job with thecorresponding Job Start Time to determine whether that job wasrun on scheduled time or not.

Scheduled Jobs

Planning Activity > Stored Backup Images > Valid BackupImagesThis report shows unexpired backup images across products, domains, clients,policies and business level views. This report is valid only for NetBackup. Thisreport is available in Ranking and Distribution views.

Planning Activity > Stored Backup Images > Duplicate CopiesThe axis on the left is for the height of the blue bars for example that tells thenumber of duplicate backup copies that exist overall. The yellow line for exampleis the axis on the right and it shows the percentage of backup images that arecopies. This is a particularly useful report for situations where you want to makecertain there is always more than 1 backup copy. If two copies of a backup exist,the blue bar would be a height of 1 (since there is 1 extra copy) and the line wouldshow .5 for 50% since half of the backup images are copies. The same situationfor 3 copies would be a blue bar height of 2 and a yellow line percentage of .66 or66%. In operational use you can filter this report down to specific policies or the


586

clients that you want to ensure always have a 50% or greater yellow line so thatmore than 1 backup copy exists.

Planning Activity > Stored Backup Images > Stored BackupImages > HistoricalThis report shows you the total amount of data in gigabytes that was backed upbut has not expired yet for each of the days in the past two weeks. This reportshows results only for NetBackup.

Status & Success Rate > Status > Failed Job CountThis report aggregates failed jobs and shows these across a timeline. In reality,this report is the same as “all jobs” as no distinction on whether the failed job wasfirst or last one is made. It provides visualization of whether a problematic trendexists. It can be reported on against any view or level within a view along withany of the key backup infrastructure components (backup server, media server)and attributes (policy, policy type, schedule, OS, product, transport type). Filteringis available on all components and attributes. The primary use case of the reportis verification of whether actions taken to correct persistent failures produceresults and reversing trends.

Status&SuccessRate>Status>Partially Successful JobCountThis report aggregates partially successful jobs and shows these across a timeline.It provides a visualization of job volume trends that skip the files that are openduring the backup job. It can be reported on against any view or level within aview along with any of the key backup infrastructure components (backup server,media server) and attributes (policy, policy type, schedule, OS, product, transporttype). Filtering is available on all components and attributes. The primary usecase of the report is verification of whether actions taken to correct the open filesituation by moving the scheduling of the client or policies produce results andreversing trends.

Status & Success Rate > Status > Successful Job CountThis report aggregates successful jobs and shows these across a timeline. Itprovides a visualization of job volume trends. It can be reported on against anyview or level within a view along with any of the key backup infrastructurecomponents (backup server, media server) and attributes (policy, policy type,schedule, OS, product, transport type). Filtering is available on all componentsand attributes. The primary use case of the report is verification of trends andthe days that are exception to the norm. The report is highly effective for


presenting long-term historical data on one of the most fundamental metrics ofmanaging a backup operation.

Status & Success Rate > Status > All Failed BackupsThis report is one of three using the advanced success or failure calculation logicaround the notion of first, all and last job. They require schedule and windowparameters enabling a precise definition of timeframes. Additionally, these reportshave aggregation levels of job and client. The first job success or failure is thefirst job for a client/policy/schedule combination in its defined backup windowand last job is the opposite. As failed jobs are rerun one or more times, the “lastjob” represents the last of the reruns within the window. This report producesthe details of the failed jobs based on which one of the three (first or all or last)methods is chosen. The main use case for this report is based on last job wherefailure notification to users is based around last job and failures leading up to thelast one is ignored.

Status & Success Rate > Status > Consecutive FailuresThis report is the second of three using the advanced success or failure calculationlogic around the notion of first, all and last job. The main use case is the calculationof 2 or more consecutive failures based around Last Job Success/Failure. It appliesintricate logic to pick off the last failed job and in turn to determine that the lastjob failures are indeed consecutive. This report can be best verified through theClient Risk Analysis report where if 3 consecutive failures with 24 hour windowswere chosen, the client or the policy combo should also appear on the risk reportas not having a successful backup in 72 or more hours.

Status & Success Rate > Status > Success Rate LineThis is a Historical report that shows success rate across products, domains,clients, policies and business level views.

Status & Success Rate > Status > Week At A GlanceThis report summarizes activity for a week by symbolically displaying the resultof each job for each client under the day of the week. The symbols are the blue(Success) and yellow (Partial Success) men and failures that are denoted by a red“X”. A drill-down capability to the job level details (i.e Job ID, Start/End Time, Sizeetc.) is provided. It can be reported on against any view or level within a viewalong with any of the key backup infrastructure components (backup server, mediaserver) and attributes (policy, policy type, schedule, OS, product, transport type).Filtering is available on all components and attributes. The report is highly


588

effective as it provides a visualization of job status for the most current data andhow that compares to the previous six days.

Week at a Glance Report’s performance declines as the data to be displayed in thereport increases. For example, running a two-month report is slower than runninga two-week report.

Note: The Week at a glance report does not display graphics when it is emailedor exported in an HTML format.

Status & Success Rate > Status > Backup Window FailuresThis report lists the jobs which were scheduled to run but failed because thescheduled backup window was no longer open (the NetBackup status code is 196).

Status & Success Rate > Status > Partially Successful JobDetailsThis report provides details for all NetBackup partially successful jobs. Partiallysuccessful jobs have an exit status of 1. The table in the report is organized by jobID, server name, and client name.

Status & Success Rate > Status > Skipped Files SummaryThe information in this report is presented using a set of linked reports. The mainreport that is organized by master server, displays clients and policies, and thecorresponding number of files that were skipped.

About skipped file details for client report

This drilldown report from the Client Name column identifies risks to the clientbecause of any skipped files.


About skipped file details for policy report

This drilldown report from the Policy Name column identifies risks to the clientdue to any skipped files.



About skipped file details for policy and client report

This drilldown report from the No. of Skipped Files column provides the namesof all skipped files.


Status & Success Rate > Status > Job Exit Status DetailThis report provides information about the completion status for a NetBackupjob. The report table provides a count of jobs having a particular exit status on aparticular day. The table is organized by server name and date.

About job details by status report

This drilldown report from the Number of Occurrences column of the table of themain report shows job details, such as job type and policy name. The table includesall jobs having a particular exit status on a given day.


Status & Success Rate > Status > Job DetailsThis report provides detailed information about NetBackup jobs.

Status & Success Rate > Status > Job Summary by StatusThis report summarizes NetBackup jobs based on the job exit status for a specifiedtime interval. You can use this report to provide trend information.

The bar chart shows a count of successful, partially successful, and failed jobs pera given date.

Status & Success Rate > Status > Job Status > HistoricalA job status report in red (failure), yellow (partial success) and green (success)displayed in stacked bar format that is grouped by hour, day, week, month, oryear across any timeframe. The report is a count of jobs for each of the threeoutcomes. The simplicity of the presentation helps easily identify both positiveand negative trends as well as one-off deviations. For NetBackup environments,the report can also be generated where attempts rather than jobs are counted. InNetBackup, jobs can be configured for x many attempts before you exit with astatus. The report can be filtered across a selection that includes Views, Backupand Media Servers, Backup Level, Policies, Schedules, Transport Types, OperatingSystems and Business Classifications.


590

Status & Success Rate > Status > Job Status > DistributionA job status report in red (failure), yellow (partial success) and green (success)displayed in pie chart format. The report is a count of jobs for each of the threeoutcomes. The main use cases of the report are typically short-term verification(i.e. last 24 – 48 hours) of backup job status and long term (i.e. 1+ months)management level reporting requiring high-level status summaries. The reportcan be filtered across a selection that includes Views, Backup and Media Servers,Backup Level, Policies, Schedules, Transport Types, Operating Systems, andBusiness Classifications.

Status & Success Rate > Success Rate > Success Rate – AllJobsThis last of the single-line success rate reports give the highest number since itshows at least one success per client stream. Meaning as long as one job issuccessful despite any number of retries, it is a 100% success. This is typically areport to show overall exposure to someone outside the backup team. A 100% onthis report indicates that everything was backed up even though it may have takena number of retries.

Status & Success Rate > Success Rate > Advanced SuccessRateThis report uses the advanced success or the failure calculation logic around thenotion of first, all and last job. It collects all information around both successesand failures and presents the results that are grouped by (day or month) timeframefor either client or the job success rate. Client success rate is a count of successfulclients where all policies that are defined to the client must be successful to declarethe client successful. Thus a client is either 0% or 100% and no intermediate state.Job success rate is derived from all jobs and separated out by first, all and last anda specific client can have a job success rate that can range between 0% and 100%.End-user and customer typically get Last Job Success for job and client whereasback up architects and administrators examine all three. These reports work wellwith views and can be reported on at any level with robust filtering capabilities.

Status & Success Rate > Success Rate > Success Rate AllAttemptsThis report shows success rate as it’s aggregated at the attempt ( “try”) level. Jobscan be configured for x many attempts before exiting with a status. If for examplethe attempt setting is two and success is attained on the second attempt, thistranslates into a 50% attempt rate and 100% job success rate. This metric is onlysupported for backup applications in which attempt level data is available. A target


line is also supported providing for an effective visual presentation on when thetarget is exceeded. It can be reported on against any view or level within a viewalong with any of the key backup infrastructure components (backup server, mediaserver) and attributes (policy, policy type, schedule, OS, product, transport type).Filtering is available on all components and attributes. Main use case is long-termhistorical data on one of the key performance indicators.

Status & Success Rate > Success Rate > Success Rate - FirstAttemptThis report shows success rate as it is aggregated at the attempt (known as “try”)level. Specifically, it zooms in on the measurement of the first attempt for eachjob. Jobs can be configured for x many attempts before you exit with a status. Iffor example the attempt setting is two and success is attained on the secondattempt, this translates into a 50% All Attempt rate and 0% First Attempt rateand 100% job success rate. This metric is only supported for backup applicationsin which attempt level data is available. A target line is also supported providingfor an effective visual presentation on when the target is exceeded. Filtering isavailable on all components and attributes. Main use case is to use this and theAll Attempts report together to see how often success is attained on the firstattempt as opposed to second, third etc. attempts.

About Catalog reportsThis section describes catalog reports.

About cold catalog backup reportThis report shows the count of cold NetBackup catalog backups and informationabout the media that NetBackup uses for offline backups.

Tool tips in the bar chart show the report name and backup count. The table inthe report also lists the media that NetBackup uses for the backups for each masterserver.

About Chargeback reportsThis section provides descriptions of chargeback reports.

About the Deduplication Chargeback reportThis report shows the savings that is achieved because of the deduplicationtechnology.

To generate this report, you need to have a cost variable of Protected Job Size.


592

The deduplication technology can identify files and the data segments that containidentical data and treats them as a single instance of the file, which it backs uponly once. For example, PureDisk has backed up 100-MB data , in which 20 MB ofdata is duplicate or identical. PureDisk protects the same data but eliminates theduplicity using deduplication. Therefore, the data that is protected is 100 MB, butthe actual data that is backed up by PureDisk is 80 MB, as 20 MB of data is duplicatedata. This results in saving 20 MB of data. You can generate the Savings reportthat shows the amount you have saved using deduplication.

The Savings report is available in Distribution, Historical, and Ranking views.

About the Cost Tabular reportThis report shows the chargeback of your backup services in a tabular form.

OpsCenter provides organizations with a tool to evaluate the cost of the IT servicesthey consume, which is called Chargeback. You can create cost variables and theformulas that enable you to run the reports that show costs of backup services.

To generate the Cost report you need to have a cost formula created.

About the Chargeback reportThis report shows the chargeback of your backup services in Historical andRanking views. You need to have a cost formula created to generate this report.

About Client reportsThis section describes client reports.

Risk Analysis > Client Risk AnalysisThis report identifies the backup clients that have gone without a successfulbackup for a specified period of time and hence are at risk from a restore orrecoverability standpoint. The “specified period of time” is user- definable alongwith several other variables for filtering purposes. The report is interpreted asall client or policy combinations that have gone x hours, days, weeks, or monthswithout a successful backup. The level of granularity is at a client or policy leveland exposes the clients that have multiple backup policies where one of them mayrepeatedly fail. The primary use case is to show that all clients have been backedup as of the last x hours and all clients have a full backup not more than x daysago. The report also has a “Is Active” filter to include only those that are currentlyactive as well as the capability to count partial successes as success and vice versa.


Risk Analysis > Client CoverageThe purpose of this report is to show what hosts are not backed up because thebackup application is not even aware of them. The report does this by comparingwhat OpsCenter hosts are known to be backed up with an external list that is fedin by .csv or .tsv. The list can come from a content management database (CMDB),DNS listings or any other authoritative source of what hosts should be backed up.The report works across all backup applications and shows you what backupapplication and policy executed the backup and the time of the last full orincremental backup.

Risk Analysis > Recovery Point Objective- RPO Recovery Point Objective (RPO) and Recovery Time Objective (RTO) haveemerged as generally accepted metrics for client recoverability. This report ranksall clients by the amount of time that is elapsed since their last successful backup.In contrast to the Client Risk Analysis report, the level of granularity is the clientlevel and thus clients with multiple backup policies are represented by the policywith most recent success. This it is recommended that this report not be used formulti-policy clients. The client “Is Active” filter allows for those hosts that arenot actively backed up to be omitted. The elapsed time in the report is alwaysbetween now and the last successful backup. The report is effective in its graphicalrankings format placing the clients with longest elapsed time at the top.

About clients not backed up reportThis report provides a list of NetBackup clients that have not been backed up orclients having all backups fail during the reporting period.

You can determine if all jobs of a policy and client combination have failed or havenot been initiated during the reporting period. You can filter by type of policy likeSharePoint, Oracle, Windows NT and so on.

The client name is displayed multiple times in the report if the client has multipleNetBackup policies that are associated with it and none of the policies are runduring the reporting period. The report shows details like policy name, schedulename, and date of the last successful backup.

Virtual Client SummaryThe Virtual Client Summary report shows details of all virtual clients of aNetBackup Master Server. Using this report, you can determine whether thesevirtual clients were backed up by NetBackup or not. Thus, you can report on thevirtual clients that need to be protected. You can also drill down in this report tosee the job details of a specific virtual client.


594

The Virtual Client Summary report shows the following details:

Name of the virtual server host such as VMwareor Hyper-V server

Virtual Server Name

Name of the proxy server host that providesdetails of the virtual clients to the NetBackupMaster Server

In case of a Hyper-V type of virtual server, theBackup Proxy Name is the same as the VirtualServer Name.

Backup Proxy Name

Name of the virtual client running on a virtualserver and which is connected to the NetBackupMaster Server through a proxy server

Virtual clients are the physical partitions of avirtual server, such as VMware or Hyper-V.

Multiple virtual clients may have the same IPaddress. But they can be identified by their UUIDs.UUID is a unique identifier of a virtual client.

Note: Click the virtual client name link to viewits job details.

Virtual Client Name

A unique identifier of the virtual clientUUID

IP address of the virtual clientIP Address

Type of the virtual server that this client belongsto, such as VMware or Hyper-V

Type

Name of the NetBackup Master Server, whichbacks up this virtual client

This field is shown blank if this virtual client isnot backed up by any NetBackup Master Server

Server Name

This is a status field that describes whetherbacking up this virtual client is defined in anyNetBackup policy or not

If a NetBackup Master Server backs up this client,this field displays “Yes”. If it shows “No”, it meansthat this client should be backed up and beprotected.

Exists in a Policy


Time when this virtual client was backed up last

This field displays NA (not applicable) if the clientis not defined in a backup policy or it is yet to bebacked up.

Last Backup Time

About job success by client reportThis report shows the rate of success for client jobs.

The bar chart shows totals for successful, partially successful, and failed jobs foreach client for the selected server or server group. Tool tips in the bars show thesejob counts. The tool tips for each client also include links to a drill-down reportshowing details for all job types.

The table in the report summarizes job information (including the number ofsuccessful and partial successful jobs, and the job success rate). The table isorganized by master server and client.

The Client Name, Number of Successful Jobs, Number of Partially Successful Jobs,and Number of Failed Jobs columns provide drill down links to more detailedreports.

About job details by client report

This drilldown report from the Client Name column or a bar chart tool tip lists allthe jobs for the selected client and time frame. The table includes details such as,job type, exit status, and media server name.


About successful job details for client report

This drilldown report from the Number of Successful Jobs column shows detailsfor this job type for the selected client.


About partially successful job details for client report

This drilldown report from the Number of Partial Successful Jobs column showsdetails for this job type for the selected client.

This drill-down report uses the run time parameters that are passed from themain report.


596

About failed job details for client report

This drilldown report from the Number of Failed Jobs column lists the failed jobsfor the selected client. Any jobs with an exit status other than 0 or 1 are consideredto be failed jobs.


About client summary dashboard reportThis report summarizes several parameters for each client for the selected servercontext and acts as a dashboard of NetBackup activities. You can use drilldownlinks to view client detail reports for many of the columns in the table.

The drilldown reports provide information about the client and answer thefollowing questions:

■ What is the server name, IP address, and operating system type?

■ How much volume for a client is backed up?

■ How many successful, partially successful, and failed jobs for the client?

■ What is the number of restore jobs that run for the client?

■ What is the average job throughput?

The report can also be used as a tool to monitor the health of backup activitiesfor your managed clients.

About total jobs for client report

This drilldown report from the Number of Total Jobs column lists all the jobs forthe selected client and time frame. The job details include policy name, schedulename, and throughput (KB/sec).


About successful jobs for client report

This drilldown report from the Number of Successful Jobs column lists thesuccessful jobs for the selected client and time frame. The report lists job details,such as, job type, policy name, start and end times, and job duration.



About partially successful jobs for client report

This drilldown report from the Number of Partial Successful Jobs column showsthe partially successful jobs for the selected client and time frame. The reportlists job details, such as, job type, policy name, start and end times, and jobduration.


About failed jobs for client report

This drilldown report from the Number of Failed Jobs column lists the failed jobsfor the selected client and time frame. Any jobs with an exit status other than 0or 1 are considered to be failed jobs.

The report lists job details, such as, job type, policy name, start and end times,and job duration.


About restore jobs for client report

This drilldown report from the Number of Restore Jobs column lists restore jobdetails for the selected client. It provides details like policy name, schedule name,and throughput (KB/sec).


About client restore reportThis report provides restore job details for a specified client. The table in thereport contains information, such as, master and media server names, and startand end times.

About BMR client configuration backup failures reportIf a NetBackup policy has the Collect BMR Info flag set, the job backs up BMR(Bare Metal Restore) client configuration. This job type starts one or moredependant jobs to back up the client data.

This report shows all jobs that failed to completely back up a BMR clientconfiguration, but their related child jobs (client data backup jobs) were partiallyor fully successful.


598

About jobs by application reportThis report uses the NetBackup policy type to simulate an application level report.For example, an Oracle policy type implies an Oracle application. The report thenlets you see all Oracle backups.

The table in this report organizes jobs in the table by server, client, and applicationand includes the backup size in MBs and the number of files. The Application(policy type) column provides a drilldown link to job details for the respectiveapplication.

About job application details report

This drilldown report from the Application column lists all the jobs for the selectedclient and policy type. The table includes job details such as, job ID, exit status,and job start and end times, and a count of files.


About Disk and Tape Device Activity reportsThis section describes disk and tape device activity reports.

About license capacity reportThis report shows the used capacity and licensed capacity information forNetBackup capacity-based licensed features in the form of a table. This reportshows all of the capacity based licenses and the actual usage per disk type at yoursite. This report shows if you are in compliance with the license rules or if youneed to purchase more licenses. This report can warn you about approachinglicense limit expiration.

From the Feature Name column of the report table, you can drill down to view areport that shows the used capacity for your licensed capacity usage features. Allcapacity values for this report are calculated based on the definition that 1terabyte=1,099,511,627,776 bytes.

About trend of license capacity for feature report

This drilldown report from the Used Capacity column shows trends for licenseusage for a selected feature. This drilldown report uses the run time parametersthat are passed from the main report. This is a trending report which shows theused capacity and licensed capacity information for capacity-based license featuresin the form of a chart for a given time frame (for example, 14 days).


About current disk usage reportThis report shows the master servers that have disk pools configured. It providesdetails about the disk pool usage and also how much free space is available in thedisk pool.

About NetBackup Disk Pool Capacity reportThis report is specific to NetBackup 6.5 and above which introduced “Disk Pools”as a type of Storage Unit. The basic version of this report shows the total amountof space that is occupied by backups across all NetBackup 6.5 Disk Pools whichwould include OpenStorage Devices, PureDisk deduplication option storage,SharedDisk, or even AdvancedDisk pools. Along with usage the average of thehigh and the low water mark is taken for each disk pool and drawn on the graph.Since this is an average it should not be used for planning purposes but ratherestimation. In actual usage this report should be filtered on a specific Disk Poolto show the exact high and low water mark. Finally the forecast is shown so thatit can be determined when capacity needs to be added or backups expired tomaintain operations.

About NetBackup Disk Pool Size vs. Percentage Full reportThis report is specific to NetBackup 6.5 and above which has new devices andstorage units called “Disk Pools”. A Disk Pool may be an OpenStorage device, aPureDisk Deduplication system, SharedDisk, or a group of local or network diskvolumes that are pooled together. The bars represent the total number of availablebytes across all disk pools with the colors representing the total amount of spaceper disk pool. The lines represent the percentage full each disk pool is. So thisreport can help identify how much disk space is used for backups, which poolsare the largest, which ones are nearing capacity and how the backup environmentis load balancing across disk storage.

About NetBackup SAN Client Performance reportThis report is specific to NetBackup 6.5 and above which features Fibre Channelconnected clients called “SAN Clients”. The blue and the yellow bars for exampleare stacked together to show the total number of jobs per day – the blue barsrepresent the jobs that ran over the LAN and the yellow is jobs ran over the SAN.The purple and the yellow lines show the total job throughput for all those jobsthat ran that day – the purple representing total job throughput by LAN and theyellow representing total job throughput by SAN. This report helps identify whatratio of LAN to SAN traffic for backups are run and what performance benefit isgained by doing so.


600

About Library Summary reportThis report provides a current point in time inventory of library capacity. Thereports list the libraries name, Volume DB Server, used/available/total slot count,and used or available or total capacity. There are two calculated columns showingthe % utilization of slots and library capacity. The report provides a rich selectionof filters enabling users with a diverse tape library environment to zoom in onany segment of their tape library population.

About Library Capacity Forecast reportThis report provides a capacity forecast of Tape Libraries. A libraries’ capacity iscalculated by multiplying Slot Count by Slot Capacity. Slot capacity is the capacityof the tape in the slot. As no standard exists for measuring library capacity, thereport enables several methods by which an individual tapes capacity isdetermined. These consist of using the maximum, the minimum and the averagesize of full tapes to determine tape capacity. Additionally, user-defined capacityfor tape types is available in the report parameter selection UI. The reportextrapolates out the trend line through the forecast period using classic linearregression and also plots the libraries capacity. At the date in which the librarycapacity line intersects the capacity forecast line is when the libraries capacity isreached.

About Drive Throughput reportThis report shows the speed (KB/Sec) at which data backups flows through tapedrives. The report uses the “heat map” concept and depicts ranges of speeds (slowto fast) through configurable shades of green. Reports are based on eitherHour-Of-Day or Day-of-Week. Advanced averaging logic is used to determine thethroughput values for each cell in the report. The averaging is done at an imagefragment level ensuring granularity and precision in calculations. The reportscan be aggregated and filtered at the Tape Library, Media Server, Drive Type,Logical Drive and Physical Drive levels. The sort options allow for intuitivepresentation of voluminous data. These reports are important sources ofinformation for performance analysis and capacity planning activities.

About Drive Utilization reportThis report shows the utilization (0 – 100%) of tape drives. The report uses the“heat map” concept and depicts ranges of utilization (low to high) throughconfigurable shades of blue for example. Reports are based on either Hour-Of-Dayor Day-of- Week. Advanced logic is used to determine the utilization values foreach cell in the report. Utilization is calculated off a per minute basis ensuringprecision in calculations versus traditional methods of periodic polling of the


devices. The reports can be aggregated and filtered at the Tape Library, MediaServer, Drive Type, Logical Drive and Physical Drive levels. The sort options allowfor intuitive presentation of voluminous data. These reports are important sourcesof information for performance analysis and capacity planning activities.

About SAN client jobs reportThis report shows all the jobs for selected Fiber Transport (FT) media servers andselected SAN clients.

The report answers the following questions and provides the following information:

■ Did the job run on a LAN or an FT pipe?

■ Are two different clients backed up by a single media server, thus reducingthe throughput?

■ A list of all the FT media servers

■ A list of all the SAN clients.

About Media reportsThis section describes media reports.

About Media State reportThis report displays the media status and count (per media type) for each masterserver and media server combination. Media state can be frozen, active, offsite,and so on.

About Available Media reportThis report lists the media that is available for use by NetBackup for each masterserver that is selected.

The report table provides information, such as, media server, media status, robottype, volume group and pool, and the time assigned.

About Drives in Use reportThis report shows the drive usage for the selected server. The report table providesdetails for the drive, for example, drive name and type, robot number and type,and assigned host.


602

About Full Media Capacity reportThis report shows the average amount of protected data (in kilobytes) on a tapefor each master server and media type. These are the tapes that NetBackup markedas full.

The bar chart depicts the amount of data (in kilobytes) per media type.

The report table is organized by server, media type and count, and shows the sizeand number of images on the tape.

About Media Summary by Media Server reportFor each media server, this report provides the number of tapes and images, thelast written date, and amount of data on the tapes. The name of the media serveris also a drilldown link to a detailed report for media.

About media summary by media status for a media server report

This drilldown report from the Media Server column provides a media statussummary for a selected media server. This report displays media status, numberof tapes and images, the last written date, and amount of data on tapes.


About media details of media status for a media server report

This drilldown report from the Media Status column provides media details forthe selected media server and selected media status. Media status can be Active,Frozen, Full, Invalid, or Suspended.


The report displays media ID, type, volume pool, last written date, expiration date,number of images, and the amount of data on tape.

About Media Utilization reportThe stacked bar chart in this report shows the number of media in use for a serverper date. The segments in the bars show assigned, unassigned, frozen, full, offsite,or suspended media states. Tool tips in the chart show the count for each mediastate.

The data for this report is only calculated once in a day. So the report shows thesummary till the previous date. The data for today reflects in the report that yougenerate tomorrow.


The table in the report is organized by date and server, and shows counts for eachmedia state.

About Tape Count reportThis report shows tape count for the following Report On parameters:

■ Backup Media Retention Level

■ Tape Type

■ Volume Pool Name

In Veritas Backup Reporter (VBR), there was a separate report for each of theseparameters. In OpsCenter, the three reports are merged into one report.

The Tape Count report is available in the Distribution view.

About Tapes Expiring in Future reportThis report shows the number of media that expire at each day in the upcoming7 days. This time frame can be changed to show more in to the future. The reportis helpful in determining if a large quantity of media may become free in the futurewhich could justify delaying the purchase of more media.

About Tapes Expiring Now reportThis report lists the media that are about to expire. The Volume Pool Name , MediaID, and Media Barcode listed make it easy to locate the media. The default timeframe when the report is clicked will show what is expiring in the next 24 hoursbut that time frame can be changed to show media expiring in the next week,month or any future time window desirable.

About Vault Media Usage reportThis report shows offsite media trends for selected vaults and current offsitemedia count. The report consists of two component reports, a bar chart and atable.

This report helps understand your offsite media trends.

Questions like the following are answered by this report:

■ How does the offsite media count vary for each vault?

■ What are the details of the current offsite media?

The bar chart shows the weekly trend of offsite media counts for selected vaults.While running the report you select the vaults for which you want to run thisreport. The report shows a weekly line trend for selected vault. This chart is a


604

good indication of how the offsite media count varies over the period of time. Youcan compare the media counts of different vaults to see which vault is consumingmore media and how it varies.

The report table provides the details of vaulted media for the selected vaults.When you run the report you specify the vault names. The report providesimportant media details like media ID, offsite slot number, container ID, expirationdate, bar code, and so on.

About Media Expiration Schedule reportThis report gives graphical representation of the expiration schedule for media.The report predicts the availability of media based on the expiration date of themedia. Using this report you can determine what media will be available for reuse.

The stacked bars represent the number of media of a specific type that are expiredon a particular day. Different colors are used in the bars for the different mediatypes. Tool tips for the bar segments provide the media type and count of themedia that is available on that day.

About Performance reportsThis section describes performance reports.

About Storage Unit Usage reportThis report shows storage unit usage for a selected master server and time frame.The first column of each row of the report table lists a storage unit. The storageunit name is also a drilldown link to a detailed report. The media server name inthe second column is also a drilldown link.

The rest of the row provides details such as, total number of jobs, total volumeprocessed (KB), average throughput (KB/sec), duration of activity and percentageof utilization in terms of duration.

About storage unit throughput report

This drilldown report from the Storage Unit column shows the data transfer rate(throughput) of the selected storage unit.


About storage unit usage details for media server report

This drilldown report from the Media Server Name column shows the usage detailsfor all of the storage units of the selected media server.



The Storage unit column of the report table is a link to a drilldown throughputreport. The rest of the cells indicate whether the storage unit was in use or notduring the time slot.

About Master Server Job Throughput reportThis report provides a tool to compare performance of various master servers.

The pie chart displays the breakdown of jobs that are run across the selectedmaster servers. A drilldown detail link from each server pie slice for job detailsis provided.

The table of this report displays throughput and job success information for eachserver in the selected server context. It shows job count and job success rate, andenables you to compare throughputs of different servers to identify any serversthat are performing poorly.

Drilldown links for the server name, number of total and successful jobs columnsare also provided.

About total jobs of a server report

This drilldown report from the pie chart or Number of Total Jobs column lists thedetails for all jobs for a selected server. The report details includes details like jobtype and status, policy and schedule names, and start time.


About job details for client and master server report

This drill-down report from the client name column provides details for a givenclient, job type, and job status. The report details include exit status, start time,duration in seconds, volume in KB, and throughput.


About successful jobs of a server report

This drilldown report from the Number of Successful Jobs column shows detailsfor successful jobs for a given server. The report provides details like job type,policy and schedule names, volume, and file counts.



606

About Media Server Job ThroughputThis report provides details of data that is backed up by NetBackup media serversand shows server throughput. It is a useful tool to compare performance of themedia servers that are present in your NetBackup environment.

The pie chart provides a breakdown of the volume of data that is processed foreach media server. A drilldown detail link for throughput details is provided fromeach volume pie slice.

About job details for client and media server report

This drilldown report from the client name column provides details for a givenclient, job type, job status, and media server. The report details include job ID, jobtype, exit status, start time, and duration in seconds.

This drilldown report uses the run time parameters that are passed from theparent report.

About media server throughput for media server report

You can use this drill-down report from the Throughput (KB/sec) column to seethe variation of throughput per day. The throughput is represented by a bar foreach day of the reporting period.

This drill-down report uses the run time parameters that are passed from themain report.

About Disk Usage reportThis report shows disk usage for the selected server and time frame. The table inthe report provides details such as, total number of jobs, total volume processed(KB), average throughput (KB/sec), duration of activity, and percentage utilizationin terms of duration.

The Disk and Media Server Name columns of the table contain drilldown links todetailed throughput and disk usage reports.

About disk throughput for storage unit report

This drilldown report from the Disk column shows the data transfer rate(throughput) for a disk storage unit for the selected server or server groups.


About disk usage details for media server report

This drilldown report from the Media server Name column shows the usage detailsfor all the disk storage units for the selected media server.



The Disk cell in each row of the report table is a link to a drill-down report. Therest of the cells indicate whether the disk was in use or not during the time slot.

About Policy reportsThis section describes policy reports.

About Top 10 Policies Using Most Server Space reportThis report displays the 10 policies that have backed up the most data in yourNetBackup environment. Since the report is based on the server context selectedit is possible to get information for each individual managed server or for a groupof servers.

Drilldown links from the bar chart (tool tips) and the table in the report providedetails for the selected policy. The tool tip also shows the volume of data in MBs.

The report table includes information, such as, number of jobs and files, andvolume of data.

About job details for a policy report

This drilldown report from the Policy Name column and the colored bars in thechart provides details about all jobs for a selected policy name.


The table includes information, such as, job type, exit status, client name, andvolume in KB.

About Job Success Rate by Policy Type reportThis report provides a quick view of the status of jobs by policy type. The reportshows the job success rate for clients, server, and job policy type.

The bar chart shows the count of successful, partially successful, and failed jobsper policy type. The tool tips in the colored bars provide job counts and also aredrilldown links to view the details for the policy.

The table in the report displays job information, such as, client name, policy type,and the success rate.


608

Note: This report may not show appropriate data for duplication jobs that areassociated with SLP policy.

This is because the duplication jobs do not have a policy type. The job batchesduplication of images that are created from possibly different policies and policytypes. The duplication job itself has an internal policy that is created but thisinternal policy does not have the policy type set because this is not a backup job.

About job details for policy type report

This drilldown report from the Policy Type column and the colored bars in thechart provides details about all jobs for a selected policy type.


The table includes information, such as, exit status, client name, volume in KB,and count of files.

About successful, partially successful, and failed job details for policy typereport

There are three drilldown reports from the Number of Successful Jobs, Numberof Partially Successful Jobs, or Number of Failed Jobs columns. The job exit statusis used as a filter for the reports. These reports are similar and provide details forall jobs for a selected client and policy type.


The table in this report provides details like, policy and schedule name, start andend times, and duration for the job. The table for failed jobs also includes a columnfor the job exit status.

About Policy Change reportThis report shows a count of the changes that were made to job policies in a giventime frame for the selected servers.

The pie chart shows the number of policy changes (a policy can change multipletimes) for each master server. (Each different server appears in a different colorin the chart.) Tool tips in the chart provide a count of the changes.

The table in the report displays the count of changes that were made to each policyfor each server.


About Policy Summary Dashboard reportThis report acts as a dashboard of NetBackup activities that are summarized byyour policies. It gives an overview of activities and can be used as a tool totroubleshoot and manage by exception using the drilldown links to other detailreports.

It provides answers for some of the following questions for each policy:

■ What is the total number of jobs?

■ How many jobs were successful?

■ How many jobs were partially successful?

■ How many jobs failed?

The table in this report shows information per policy like policy name and type,job volume in MB, job count, and counts for job exit status. You can also drill downfrom the job exit status counts in the columns and view individual policy detailsbased on exit status and job policy and type.

About drilldown reports

These drilldown reports from the Total Jobs, Successful Jobs, Partial Jobs, or FailedJobs columns provide an overview of all jobs for the selected policy name, server,and time frame based on the job exit status.


The table provides details like schedule name, start times, and duration of thejob.

About Restore reportsThis section describes restore job reports. These reports are applicable only forNetBackup.

About Restore Job Summary by Job Count reportThis report is a graphical summary of the number of restore jobs run for theselected time frame.

About Restore Job Summary by Volume Restored reportThis report shows the restore job count by volumes.


610

About Restore Job Details reportThis report provides details of restore jobs. The report lists all completed restorejobs for the selected time frame.

The table in the report is organized by job ID, master server name, and client.



612

Additional information onPureDisk data collection

This appendix includes the following topics:

■ About AT configuration scenarios specific to PureDisk backup product

■ Setting up a trust between the OpsCenter AB host and PureDisk SPA host

AboutAT configuration scenarios specific to PureDiskbackup product

This section describes various configuration scenarios for Symantec ProductAuthentication Service (AT) that you should take into account before configuringPureDisk data collector.

On a broader level, there can be two types of OpsCenter - PureDisk setups withrespect to their AT root broker configurations:

■ Common AT root broker for OpsCenter server and PureDisk SPASee “Scenario 1: Common Root Broker” on page 614.

■ Different AT root broker for OpsCenter server and PureDisk SPA

Note: In this type of configuration, you need to set up a bi-directional trustbetween the OpsCenter AB host and PureDisk SPA host.

You need to establish trust between the authentication brokers of OpsCenterand PureDisk SPA for secure communication. This set up is a pre-requisite forPureDisk data collection from OpsCenter.

See “Scenario 2: Different Root Brokers” on page 615.

AAppendix

Scenario 1: Common Root BrokerThis section talks about all scenarios where the AT root broker is common forOpsCenter server as well as PureDisk SPA.

Figure A-1 describes a scenario where the AT root broker is configured on thePureDisk SPA host and OpsCenter server points to the same root broker. Thus forboth product hosts, the AT root broker is common. You do not need to carry outany additional steps for PureDisk data collection.

Figure A-1 Common root broker - root broker on PureDisk SPA

AT hierarchy

Data collection

Host B:PureDisk SPAAT Root Broker +Authentication Broker

Host A:OpsCenter ServerAT AuthenticationBroker

Figure A-2 describes a scenario where the AT root broker is configured on theOpsCenter server host and PureDisk SPA points to the same root broker. Thus forboth product hosts, the AT root broker is common.

Figure A-2 Common root broker - root broker on OpsCenter Server

AT hierarchy

Data collection

Host B:PureDisk SPAAT Authentication Broker

Host A:OpsCenter ServerAT Root Broker +Authentication Broker

Figure A-3 describes a scenario where the AT root broker is configured on theHost C and OpsCenter server host and PureDisk SPA point to this remote rootbroker. Thus for both product hosts, the AT root broker is common.

Figure A-3 Common root broker - root broker on a remote host

Data collection



Host C:AT Root Broker

AT hierarchyAT hierarchy

Additional information on PureDisk data collectionAbout AT configuration scenarios specific to PureDisk backup product

614

Scenario 2: Different Root BrokersThis section talks about all scenarios where the OpsCenter server and PureDiskSPA use different AT root brokers.

Note: If OpsCenter and PureDisk have different AT root broker configurations,you need to set up a bi-directional trust between the OpsCenter AB host and thePureDisk SPA host. This set up is a pre-requisite for collecting PureDisk data fromOpsCenter.

Note: Setting up trust between the PureDisk SPA host and OpsCenter AB host isa manual process.

Refer to the “Setting up a trust between PureDisk SPA host and OpsCenter ABhost” section.

Setting up trust between the OpsCenter Authentication Broker host and PureDiskSPA host is accomplished automatically after PureDisk data collector is configured.If it is not successful, you need to do it manually.

See “Setting up a trust between the OpsCenter AB host and PureDisk SPA host”on page 617.

Root brokers on local hostsFigure A-4 describes a scenario where the OpsCenter server and PureDisk SPAuse the AT root brokers that are configured on their respective hosts.

Figure A-4 Different root brokers - root brokers on local hosts

Data collection

Host B:PureDisk SPAAT Root Broker +Authentication Broker

Host A:OpsCenter ServerAT Root Broker +Authentication Broker

Note: If you have this kind of configuration, you need to set up a trust betweenthe two root broker hosts, that is between Host A and Host B.

Root brokers on remote hostsFigure A-5 describes a scenario where the OpsCenter server and PureDisk SPAuse the AT root brokers that are configured on two remote hosts.

615Additional information on PureDisk data collectionAbout AT configuration scenarios specific to PureDisk backup product

Figure A-5 Root brokers on remote hosts

Data collection




AT hierarchy

Host D:AT Root Broker

Remote root broker for OpsCenter server and local root forPureDiskFigure A-6 describes a scenario where the OpsCenter server uses remote rootbroker and PureDisk SPA uses local root broker.

Figure A-6 Remote root for OpsCenter server and local root for PureDisk

Data collection




AT hierarchy

Local root broker forOpsCenter server and remote for PureDiskFigure A-7 describes a scenario where PureDisk SPA uses remote root broker andOpsCenter server uses local root broker.

Additional information on PureDisk data collectionAbout AT configuration scenarios specific to PureDisk backup product

616

Figure A-7 Local root broker for OpsCenter server and remote for PureDisk

Data collection




AT hierarchy

Setting up a trust between the OpsCenter AB hostand PureDisk SPA host

This section provides the steps that are required to set up trust between theOpsCenter AB (authentication broker ) host and PureDisk SPA host.

Note: OpsCenter AB host is the host where the OpsCenter server is installed. IfOpsCenter is installed in a clustered mode, the OpsCenter AB host is the host namethat was provided as the remote AB host during the OpsCenter installation.

Note: Trust setup between the OpsCenter AB host and PureDisk SPA host isautomatically carried out when you create a PureDisk data collector in OpsCenter.

If the trust is not successfully established at this stage, carry out the manual stepsas follows.

617Additional information on PureDisk data collectionSetting up a trust between the OpsCenter AB host and PureDisk SPA host

To set up a trust between the OpsCenter AB host and PureDisk SPA host

◆ On the OpsCenter AB host, run the following command depending on theOpsCenter server operating system :

These are the default directory paths.

C:\Program

Files\VERITAS\Security\Authentication\bin\vssat

setuptrust --broker <PureDiskSPAhost:port>

--securitylevel high

Windows 32-bit

C:\Program Files

(x86)\VERITAS\Security\Authentication\bin\vssat

setuptrust --broker <PureDiskSPAhost:port>

--securitylevel high

Windows 64-bit

/opt/VRTSat/bin/vssat setuptrust --broker

<PureDiskSPAhost:port> --securitylevel high

UNIX

The registered port for authentication is 2821. If the AT root broker isconfigured with another port number, contact your security administratorfor more information.

After successfully setting up a trust between the OpsCenter AB host andPureDisk SPA host, the following message is displayed:

setuptrust

----------------------

----------------------

Setup Trust With Broker: PureDiskSPAhost

Additional information on PureDisk data collectionSetting up a trust between the OpsCenter AB host and PureDisk SPA host

618

Attributes of NetBackupdata


■ About backup data attributes

About backup data attributesThis section lists all attributes pertaining to data that OpsCenter collects fromNetBackup. You can select these attributes while generating custom reports.

Table B-1 lists all NetBackup attributes that OpsCenter collects.

Table B-1 NetBackup data attributes

ExplanationSample DataData Attributes

Backup Job Attributes

The name of the serverwhere a Backup Reporterdata collection agent isinstalled

host.symantec.comAgent Server

Filled in by the user inthe Job Reconciliationpage to indicate why ajob failed so others cansee.

Host cannot be reachedBackup job Comment

BAppendix

Table B-1 NetBackup data attributes (continued)


The deduplication filefactor for each PureDiskbackup job. Meaning thatfor every 321 files thatwere backed up only onefile was actually stored.(321 to 1 filededuplication rate)

321Backup job File CountDeduplication Factor

The number of files notneeding to be backed upfor every backup job inPureDisk because theywere already stored withdeduplication. Meaningthat if 500 files weretargeted for backup, only44 were stored since thesaving was 456.

456Backup job File CountDeduplication Savings

Within Backup Reporterthere is the ability tomark a job as ignored(yes/no). If it is ignoredit does not count towardsthings like success rateor time since lastsuccessful backup. Thismarking of a job asignored is done in the"Reports > Explorers"section.

Yes/NoBackup job Is Ignored

The number of files thatare processed in aPureDisk backup. Notethat this number is notactually stored since it isbefore deduplication.

400 filesBackup job ProtectedFile Count

The size in byes of aPureDisk backup jobbefore deduplication.

200GBBackup job ProtectedSize

Attributes of NetBackup dataAbout backup data attributes

620



The deduplication sizefactor for each PureDiskbackup job. Meaning thatfor every 567KB thatwere backed up only 1KBwas stored.

567Backup job SizeDeduplication Factor

The number of KB's notneeding to be backed upfor every backup job inPureDisk because theywere already stored withdeduplication. Meaningthat if 346KB werebacked up, the savings of345KB means only 1 KBwas needed to be stored.

345Backup job SizeDeduplication Savings

Each directory under ajob and it's type ofbackup.

Catalog, File System, MS Exchange,NDMP, Sybase

Backup job Sub Type

The transport that wasused to move the backupfrom backup client tomedia server

LAN, SANBackup job TransportType

The number of times abackup job had to beattempted before beingsuccessful or reachingthe maximum allowablenumber of retries

4Job Attempt Count

The name of a host beingbacked up as seen by abackup job

backup-client.symantec.comJob Client

The file system directorybeing backed up as seenby a backup job

C:\, /var, ALL_LOCAL_DRIVESJob Directory

621Attributes of NetBackup dataAbout backup data attributes



The amount of time inseconds for a backup tostart and finish as seenby a backup job

300 secondsJob Duration

The date and time that abackup ended

Tues 3/23/2008 03:34:43Job End Time

The exit code, statuscode, or error code for aparticular job

0,1,2,3…Job Error Code

The time at which thisjob (the image that thejob generates) willexpire.

Aug 01, 2008 22:03:48Job Expiration Time

The number of files abacked up during abackup job

300Job File Count

The group ID that theproduct group specifies.

Note:The secondary IDand the Group ID areintended for the samepurpose. These IDs groupthe jobs in some way thatis useful in reporting.

6114Job Group ID

The Schedule Type forthe backup job, Full,Incremental, Cumulative,User etc.

Full, Differential Incremental, UserBackup

Job Level

A unique number foreach backup job in abackup domain thatidentifies a backup job

5,234,234Job Primary ID


622



When a unique jobnumber is not enough todistinguish a job, asecondary ID may beused. For NBU, this fieldis the job Process ID

5,234,235Job Secondary ID

The amount in KB that abackup job transferredfrom client to mediaserver for backing up

2048Job Size

The date and time that abackup started

Tues 3/23/2008 02:34:43Job Start Time

A percent number that iscalculated based on thenumber of jobs that weresuccessful (NetBackupstatus 0) and partiallysuccessful (NetBackupstatus 1) divided by thetotal number of jobs ranin that period of time.Example: 98 successfuljobs / 100 total jobs (2failures) = 98%

98Job Success Rate(Complete and partial)

A percent number that iscalculated based on thenumber of jobs that weresuccessful (NetBackupstatus 0) divided by thetotal number of jobs ranin that period of time.Example: 98 successfuljobs / 100 total

99Job Success Rate(Complete only)




The speed of a backupjob in Kbytes/sec. This isthe speed of the overalljob which takes in toaccount transfer timefrom client to mediaserver and media serverto disk or tape storage. Itis not just the speed of atape drive.

3,234Job Throughput(Kbytes/sec)

The type of operationdone by the backupproduct

Backup, Restore, duplication, archive,label, erase

Job Type

The Schedule Type forthe backup job groupedinto just two options.Full vs. Other

Full, Differential Incremental, UserBackup

Level Type

The name of the masterserver that executed thebackup job

nbu-master.example.comMaster Server

The name of the mediaserver that performedthe backup job

nbu-media.example.comMedia Server

The name of the backuppolicy as seen by abackup job

Oracle Backup Policy, User BackupPolicy, File System Backup Policy

Policy

The name of the backuppolicy as seen by abackup job


Policy Description

The user-defineddescription of a policy asseen by a backup job

‘This policy is for doing Oracle backups’Policy Description

The backup product thata backup policy executeda job from

NetBackup Policy Domain, PureDiskPolicy Domain

Policy Domain Name


624



The type of policy asseen by a backup job

Standard (UNIX), Windows-NT, Oracle,Exchange

Policy Type

The backup product thatperforms backup, fromwhich OpsCenter collectsdata

NetBackup, PureDisk, TSMProduct

The name of a schedulewhich resides within apolicy as seen by abackup job

(user-defined), ex: Weekly-Fulls,Daily-Incrementals

Schedule

A word description foreach job that coorelatesstatus codes to theirenglish meaning. Allfailures are mapped tothe word ‘Failure’

Success, Partial, FailureStatus

The name of a storageunit which is choosen bya policy to receive andstore backups. StorageUnits are usuallygroupings of tape driveswithin a library ormultiple disk locationsthat are groupedtogether in pools. This isthe storage unit namethat was used by abackup job and thereforemay or may not exist inpresent time.

(user-defined), ex: tld0-hcart-0Storage Unit Name

The type of storage unitused and seen by abackup job

Disk, Media Manager (tape)Storage Unit Type

Job Scheduled Time

Window Closing Time

Job Execution Type




Original Job ID

Backup Image Attributes

A yes/no property of if abackup image stored inthe catalog wascompressed or not.

Yes/NoBackup ImageCompression State

The date/time that abackup image copy is setto expire

Mon 4/23/2008 4:32:34Backup Image CopyExpiration Time

A yes/no property of if abackup image is expiredor not. If it is expired itcan no longer be restoredand that space may berewritten to by thebackup application. If itis not expired it isavailable for restore.

Yes/NoBackup Image Copy IsCurrently Expired

A yes/no property of if abackup image is theprimary copy. If theimage is a 2nd or greatercopy this value would be‘no’.

Yes/NoBackup Image Copy IsPrimary

The name of the backupserver that performedthe copy of a backup to asecond location.

backup-server.symantec.comBackup Image CopyMedia Server

A true/false property asto if the backup imagecopy was written usingmultiplexing or not(multiple clients/jobsstreamed to one image)

True/FalseBackup Image CopyMultiplexed State


626



The type of storage unitthat the backup imagewas copied to. This couldbe disk, tape etc.

Media Manager (tape), DiskBackup Image CopyStorage Unit Type

The number offragments that make upa complete unexpiredbackup. A single backupcan have 1 or a multipleof fragments which areblocks of data seperatedby tape marks on tape orseperated in to separatefiles on the file system ifwritten to disk.

30Backup Image CopyUnexpired FragmentCount

A unique ID or key forevery backup stored inthe catalog. This key orID can be used to look upan image in the catalogfor restore or otheractivity

backupclient_23423Backup Image CopyUnique ID

A yes/no property of if abackup image wasencrypted between thebackup client and backupmedia server. This valuedoes NOT represent iftape drive or otherencryption was used ornot.

Yes/NoBackup ImageEncryption State

The date and time that abackup image will expire.When a backup imageexpires it is no longeravailable for restore andthe space that thebackup occupied can bereused for additionalbackups (overwritten)

Mon 4/23/2008 4:32:34Backup ImageExpiration Time




The actual number offiles that are storedwithin a backup image.

432Backup Image FileCount

The date/time that thebackup image fragmentis set to expire

Mon 4/23/2008 4:32:34Backup ImageFragment ExpirationTime

A yes/no property of ifthe backup imagefragment is expired ornot. Even if a backupfragment is expired, thatspace can not be reuseduntil the whole backupimage is expired (disk) orthe whole backup tapemedia is expired (tape)

Yes/NoBackup ImageFragment Is CurrentlyExpired

The true image restorestatus for a backupimage fragment. Trueimage restores allow arestore to take place atthe directory levelwithout overwriting filesthat weren't backed upbut are still in thedirectory. For this to bepossible a ‘true imagerestore’ backup imagemust exist.

TIR Info on Disk, TIR Rsv SyntheticInfo on Disk

Backup ImageFragment Is TIR

The size of the backupimage fragment. Bydefault NetBackup uses1TB fragments (ie nofragments) but this canbe configured todifferent values

2048Backup ImageFragment Size

A unique ID associatedwith every backup imagefragment

backupimagefragment_124Backup ImageFragment Unique ID


628



A yes/no property as toif the backup image isexpired or not

Yes/NoBackup Image IsCurrently Expired

The true image restorestatus for a backupimage. True imagerestores allow a restoreto take place at thedirectory level withoutoverwriting files thatweren't backed up butare still in the directory.For this to be possible a"true image restore"backup image must exist.

TIR Info on Disk, TIR Rsv SyntheticInfo on Disk

Backup Image TIRStatus

The type of backupimage. Catalog being aNBU catalog image fordisaster recovery

Regular, CatalogBackup Image Type

The number of copiesthat exist for a primarybackup image. These arecopies that are unexpiredand can be used for arestore.

1, 2, 3 etc.Backup ImageUnexpired Copy Count

A unique ID or key forevery backup stored inthe catalog. This key orID can be used to look upan image in the catalogfor restore or otheractivity

backupclient_23423Backup Image UniqueID

The date and time thatthe backup image wasfinished writing.

Mon 4/23/2008 4:32:34Backup Image WriteEnd Time

The date and time thatthe backup image beganto be written.

Mon 4/23/2008 4:32:34Backup Image WriteStart Time




The name of the serverthat classified thebackup image in somesort of ranking (gold,silver, bronze etc)

master-server.symantec.comData ClassificationMaster Server

The name of theclassification of data

Gold, Silver, Bronze,Non-DataClassification-Name

Data ClassificationName

The number ranking thatcorresponds with thename of dataclassification. A 1 wouldmean the data is moreimportant than a 2 forexample.

1,2,3,etcData ClassificationRank

Backup Attempt Attributes

The number in secondsthat a backup wasattempted

3500Attempt Duration

The number in secondsthat a backup wasattempted

3500Attempt Duration

The date and time that abackup attempt ended(each attempt is unique)

Mon 4/23/2008 4:32:34Attempt End Time

The error code that thebackup attempt finishedwith

0, 1, 2, 3 etc.Attempt Error Code

The number of files thebackup attempted toprocess

0, 1, 2, 3 etc.Attempt File Count

The number in KB for theamount an attemptedbackup tried to process

2048Attempt Size

The start time that abackup attempt began

Mon 4/23/2008 4:32:34Attempt Start Time


630



A named status thatmaps to the error codenumbers in the backupapplication (for examplea status 0 in NetBackupis a success, a status 1 ispartial and all othernumbers are failures)

Success, Partial, FailureAttempt Status

The average success rateacross all attempts in allbackups. Example wouldbe the average of 2backups were each wasattempted 3 times. Thesuccess rate would be thesuccess rate average ofthe 3 attempts withineach backup job. (Notethat this is different thanthe success rate acrossall jobs which does nottake in to accountattempts)

98%Attempt Success Rate

The speed of a backupattempt in Kbytes/sec.This is different than theoverall KB/sec for a jobwhich would take in toaccount all attempts.

2048Kbytes/secAttempt Throughput




The average success rateacross all attempts in allbackups but alsoincluding partialsuccesses (status 1 inNetBackup). Examplewould be the average of2 backups were each wasattempted 3 times. Thesuccess rate would be thesuccess rate average ofthe 3 attempts withineach backup job. (Notethat this is different thanthe success rate acrossall jobs which does nottake in to accountattempts)

98%Backup AttemptPartial Success Rate

The attempt number ina sequence. 1 wouldrepresent the firstattempt, 2 wouldrepresent the secondattempt etc.

1, 2, 3Backup AttemptSequence

The date and time that aparticular file wasskipped over during abackup

Mon 4/23/2008 4:32:34Backup Skipped FileTime

The status code for whythat file was skipped(usually a status 1)

1Skipped File Code

The reason a file wasskipped. (Usuallybecause file was in use)

File is open by another processSkipped File Reason

The actual file name thatwas skipped over duringa backup.

C:\Windows\an_open_file.dllSkipped File Name

Backup Policy Attributes


632



The host name of thebackup application hostthat contains the backuppolicy. In the case ofNetBackup this is themaster server.

nbu-master.example.comBackup Policy DomainMaster Server

The name of a backuppolicy that exists in thebackup application. Notethat this is similar andcan be the same as the‘backup job Attribute:Policy’ which showswhat policy the backupjob was executed from. Itis different though sincethis Policy Name simplymeans that this Policyexists not that anythingwas executed from it yet.


Backup Policy Name

The type of backuppolicy that exists in thebackup application. Notethat this is different thanthe ‘backup job Attribute:Policy Type’

Standard (UNIX), Windows-NT, Oracle,Exchange

Backup Policy Type

Data ClassificationName

Policy Storage Unit /Lifecycle policy

Policy Volume Pool

Job Priority

Active

Effective Date

Backup NetworkDrives




True Image Recovery

Compression

Encryption

Allow Multiple DataStreams

Block LevelIncremental

Perform Snapshot

Individual File RestoreFrom Raw

Virtual Machine Proxy

Multiple copies

Override policy storageselection

Override policy volumepool

Override media owner

Multiplexing

Fail all

Synthetic

Disk Only

File System Attributes

User defined field. Canbe one of ‘MissionCritical’, ‘BusinessCritical’ or ‘BusinessSupport’

‘Business Critical’Business Classification


634



A user defined field foran object ID of the filesystem. Typically used asa pairing with an assetmanagement database

asset123 etc.File System: OID

The file system directorybeing backed up.

C:\Documents and Settings\All Users\Filesystem Name

A user-defined field (thisis not collectedautomatically) of whattype of file system wasbacked up.

NTFS, UFS, ZFS, EXT3Filesystem Type

Host Attributes

User defined field (this isnot automaticallycollected) for filling inarchitecture type such asx86, x86-64, SPARC,POWER, PA-RISC, IA64etc

SPARC, x86Host Architecture

A user defined field forinserting any extrainformation regarding ahost

Pete's serverHost: Misc Info

A user defined field forinserting an object IDfrom an assetmanagement database

asset123, etc.Host: OID

The name of the hostobject that contains filesystems.

hostname.example.comHostname




The version of theoperating system.Usually grouped withOperating System namesince this will havevalues like ‘10’ (i.e.Solaris 10), or ‘2003’ (i.e.Windows 2003)

2003, 10O.S. Version

The operating systemname of the host

Windows, SolarisOperating System

Backup Media Attributes

The name of theOpsCenter agent thatcollected the mediainformation.

ops-agent.example.comAgent Server

The date/time that apiece of media was firstallocated or had it's firstbackup written to it.Once the media expiresit will have a newallocation date/timewhen it is reused

Mon 3/4/2008 3:34:34Backup MediaAllocation Time

How much is left on tapein KB. Value here persample is either the freecapacity if the media isactive, or 0 otherwise.

500,000 KBBackup MediaAvailable FreeCapacity

Total capacity of the tapein KB. Value here persample is either the totalcapacity if the media isactive, or 0 otherwise.

19,000,000KBBackup MediaAvailable TotalCapacity

The full barcode as readyby the physical robot.This can be longer thanthe 6 characters used bya NetBackup Media.

JFP000L2Backup Media Barcode


636



The date/time that abackup media is set toexpire

Mon 3/4/2008 3:34:34Backup MediaExpiration Time

How much is left on tapein KB. This number maybe estimated using analgorithm.

500,000 KBBackup Media FreeCapacity

A yes/no property of aparticular tapeindicating whether thetape has been sampled inthe last two collections.

Yes/NoBackup Media Is Active

A yes/no property of aparticular tapeindicating whether it canstill be written to.

Yes/NoBackup Media IsAvailable

A yes/no property of ifthe backup media existsin the currentconfiguration (and nothistorical)

Yes/NoBackup Media IsCurrent

A yes/no property of ifthe backup media hasexpired data on it or not

Yes/NoBackup Media Is DataExpired

A yes/no property of ifthe backup media ismarked as full (no morebackups can be writtento it)

Yes/NoBackup Media Is Full




A yes/no property of ifthe backup media wasimported. Importedmedia simply means thatthis paticular backupdomain did not originallywrite the data to themedia. This could be dueto disaster recoverywhere the catalog couldnot be moved from anexisting domain so thetapes were readindividually to determinewhat data was on them.It also is commonly usedto import Backup Execmedia to NetBackup.

Yes/NoBackup Media IsImported

A yes/no property of ifthe physical media isexpired or not. Once allthe backup images (data)has been expired on atape that entire cartridgeis marked as PhysicallyExpired=Yes and it canbe overwritten or used byfuture backups.

Yes/NoBackup Media IsPhysically Expired

Since capacity of a tapeis often estimated usingan algorithm. Thisspecifies whether it wasactually calculated, orprovided exactly by theDP product.

Yes/NoBackup Media Is TotalCapacity Estimated

A date/time that thebackup media was lastused to be read (restored)

Mon 3/4/2008 3:34:34Backup Media LastRead Time


638



A date/time that thebackup media was lastused to be written to(duplicates, backups)

Mon 3/4/2008 3:34:34Backup Media LastWrite Time

The physical slot numberthat a given piece ofmedia resides in

1, 2, 3 etc.Backup Media LibrarySlot Number

A yes/no property of if agiven piece of tape mediawill allow for multipleexpiration dates.Multiple expiration datesmeans that the wholetape can not be reuseduntil the last backup hasexpired on the media.

Yes/NoBackup Media MultipleRetention LevelsAllowed

A yes/no property of ifmultiplexing is allowedon a piece of tape media.Multiplexing means thatmultiple clients weremultiple clients or jobswere backed up to oneimage so that particularimage could have morethan one client inside it.

Yes/NoBackup MediaMultiplexing Allowed

Calculated valuerepresenting (availablefree capacity /availabletotal capacity ) inpercentage

0-100%Backup Media PercentAvailable FreeCapacity

Calculated valuerepresenting (freecapacity total capacity )in percentage

0-100%Backup Media PercentFree Capacity




Calculated valuerepresenting (usedcapacity / total capacity)in percentage

0-100%Backup Media PercentUsed Capacity

The date/time that apiece of media willphysically expire (allimages on the media) andbe able to be reused

Mon 3/4/2008 3:34:34Backup Media PhysicalExpiration Time

The retention level of themedia in number ofseconds. Divide by 86400to get the retention levelin days

63072000.00, 31536000.00, 1209600.00Backup MediaRetention Level

The date/time that allthe media informationwas collected from thebackup application toOpsCenter. History iskept so a history of thestate of all media can bedetermined.

Mon 3/4/2008 3:34:34Backup MediaSnapshot Time

The type of storage for agiven piece of media(disk or tape)

Disk, TapeBackup Media StorageType

Total capacity of the tapein KB. This number maybe estimated using analgorithm.

19,000,000 KBBackup Media TotalCapacity

The density or type ofmedia. This is used tomatch what drives themedia can go in for amixed mediaenvironment.

HCART, DLT, 8MM etc.Backup Media Type

The number of imagesthat are unexpired on agiven piece of media

1, 2, 3 etc.Backup MediaUnexpired ImageCount


640



Amount in KB used up inthe tape. This value isprovided by the DPproduct and is NOTestimated.

500,000 KBBackup Media UsedCapacity

A user defined field forgrouping volumes. Bydefault NetBackupassigns the robot numberand type so that TLD(2)would read‘000_00002_TLD’

User defined but defaults to things like‘000_00002_TLD’

Backup Media VolumeGroup Name

The path on disk wherebackup images arestored.

/disk_staging_file_system/,C:\disk_staging\

Backup Media VolumePath

Specific to NetBackup 6.5- this is the high watermark that is set for aFlexible Disk pool,OpenStorage disk pool orPureDisk backendstorage pools. When thisthreshold is reached bythe file system on thedisk pools backups willnot be attempted to thatdisk location since it willbe considered ‘full’.

95%Disk Pool High WaterMark

Specific to NetBackup 6.5- this is the low watermark that is set for aFlexible Disk pool,OpenStorage disk pool orPureDisk backendstorage pools. When thisthreshold is reached bythe file system on thedisk pools backups willnot be sent to thelocation as often

80%Disk Pool Low WaterMark




The name of theNetBackup master serverthat the disk poolbelongs to

nbu-master.example.comDisk Pool MasterServer

The name of the diskpool which defaults tothe disk array string or auser defined value

netappfi::fas3050-1a, DDPool, etc.Disk Pool Name

The raw size is the sizeof the disk volume(s) ina disk pool. Raw sizedoes not mean you canactually write to thatamount (that's whatusable size is) but justtells you there is morepossible disk space thatcould be allocated fromraw to usable.

69,990.40Disk Pool Raw Size

The type of flexible diskthat the pool is

AdvancedDisk, SharedDiskDisk Pool Server Type

The date/time that asnapshot was taken toproduce the backupimage that exists in thedisk pool

Mon 3/4/2008 3:34:34Disk Pool SnapshotTime

Similar to tape drivestatus, this tells if thedisk pool is UP meaningit is usable and can beused or DOWN meaningit is not usable. When inthe DOWN state jobs willnot attempt to use thedisk pool.

UP, DOWNDisk Pool Status


642



The usable size is thesize of the formatted filesystem and tells you howmuch data can be writtento the disk pool

1,208,893.44Disk Pool Usable Size

The number of diskvolumes that make upthe disk pool

4Disk Pool VolumeCount

The type of tape mediaas defined by the backupapplication. ForNetBackup this is alsocalled the ‘density’ andspecifies what types ofdrive the tape can go in.

HCART, DLT, 8MM etc.Media Density

Optical media headersize of a backup image

1024Media Hsize

The Media ID for a givenpiece of media, usually asubset of the barcode.For NetBackup this is a6-digit ID.

JFP000Media ID

The number of backupimages on a given pieceof tape media or diskpool

54Media Image Count

Logical block address ofthe beginning of theblock that a backupimage exists

2048Media L Offset

The number of times agiven piece of backupmedia has been used forrestores.

0, 1, 2, 3, etc.Media Restore Count

Optical media sector sizeof a backup image.

1024Media Ssize




The ID of the oppositeside of a optical platter.If on side A of a platterthis would show Side B

A/BPartner

The backup product thatthis piece of mediabelongs to

NetBackup, TSMProduct

The status of a givenpiece of media. Activemeaning it is being usedat a given point in time,Frozen meaning errorshave occurred on thetape media and it is nolonger being used forbackups, etc.

Active, Non-active, Suspended, FrozenStatus

The volume pool IDwhich automaticallystarts at 1 for the defaultpool "NetBackup".Things like Scratch Poolsor onsite/offsite poolsare typically also usedand these all have uniquevolume pool ID's. Manyencryption solutionssuch as Decru and IBMuse the volume pool IDto determine whatbackups to encrypt ornot

1, 2, 3, 4 etc.Volume Pool ID

This user defined field isthe name of the volumepool that media is placedin to. The default isNetBackup but manyothers are typicallycreated to segment tapesin to groups

NetBackup, Scratch, CatalogBackup,MSEO, WORM, etc.

Volume Pool Name


644



The name of the VolumeDatabase (pre-NetBackup6.) or EMM server(NetBackup 6.0+). This istypically the NBU Masterbut doesn't have to be inthe case where multiplemasters are sharing thesame EMM server.

nbu-master.example.comVolume/EMMDatabase Server

Tape Library Attributes

The backup applicationthat controls the tapedrive

NetBackup, TSMTape Library AgentProduct

The server host namethat the OpsCenter agentis installed on that isused to collect tape driveinformation.

ops-agent.example.comTape Library AgentServer

The device databaseserver that is controllingthe particular library.This is the EnterpriseMedia Manager server(EMM) in NetBackup 6.0+or the device controlhost in 5.1 and below.

NBU-device-host.example.comTape Library DeviceDatabase Server

The manufacturer asdetermined by the SCSIinquiry string in thebackup application.

STK, Quantum, IBM etc.Tape LibraryManufacturer

The serial number,unique, to each tapelibrary

ADIC203100468_LL0Tape Library SerialNumber

The total number of slotsthat exist in a tapelibrary

40, 120, 360Tape Library SlotCount




The type of tape library(TLD, ACS, 8MM, 4MM,TLM, TLH etc)

Tape Library DLT, Tape Library 8MM,Tape Library ACS

Tape Library Type

The unique numbergiven to each tape libraryin the EMM database.This ID is put togetherwith the library type inthe NBU GUI to showTLD(0), TLD(1) etc.

0, 1, 2 etc.Tape Library UniqueID

Tape Drive Attributes

The name of a tape driveas given by the backupapplication, usuallydefault names are basedon SCSI inquiry stringsthat contain themanufacturer name andmodel number

IBM.ULTRIUM-TD2.000Name

The number of a tapedrive as given by thebackup applicationwhich is unique for eachphysical drive (a numbercould be shared betweenmedia servers though)

0, 1, 2, 3 etc.Number

A simple true/false onweather the tape drive isshared across backupservers or not

true/falseShared

The device host (MediaServer) that the tapedrive is connected to.

NBU-device-host.example.comTape Drive DeviceHost


646



A simple true/false onweather the tape driveexists in the currentconfiguration (true) or ifit is historical and nolonger exists (false)

true/ falseTape Drive Is Current

The unique serialnumber for a physicaltape drive

768ZD03034Tape Drive SerialNumber

The storage unit that thetape drive is assigned to

dcdell214-dlt-robot-tld-0Tape Drive StorageUnit Name

The type of tape drive asdefined by the backupapplication. ForNetBackup this is alsocalled the ‘density’ andspecifies what types oftape can go in the drive.

hcart, hcart2, dlt, 8mm etc.Tape Drive Type

The tape drive numberinside the library

1, 2, 3, 4, 5, 6 etc.Tape Drive Unique IDfor Library

Tape Usage Attributes

The storage unit groupthat the storage unit thatthe tape drive belongs to

Storage Unit Tape GroupStorage Unit GroupName

The host (Media Server)that the tape drive isassigned to for use attime of tape driveinformation collection

nbu-host.example.comTape Drive Assigned

The robot type that iscontrolling the tape driveand it's associated statusof up or down at time oftape drive informationcollection

TLD, ACS, DOWN-TLD, DOWN-ACS etc.Tape Drive Control




A true / false for if thetape drive was enabled atthe time of tape driveinformation collection

true / falseTape Drive Enabled

A true / false for if thetape drive was in use atthe time of tape driveinformation collection

true / falseTape Drive In Use

The tape that was in thedrive at the time of tapedrive informationcollection

VT0036Tape Drive RecordedMedia ID

The date and time thatthe tape driveinformation wascollected

Apr 05, 2008 22:57:17Tape Drive SnapshotTime

Backup Log Attributes

The host name of theOpsCenter server wherethe database and webinterface resides

ops-server.example.comBackup Log AgentServer

The detailed statusmessages for each job

backup of client dcdell211 exited withstatus 71 (none of the files in the filelist exist)

Backup Log Message

The host server with thebackup application thatlogged the error message

nbu-host.example.comBackup Log SourceHost

The backup client thatwas associated with thelogged error message

nbu-client.example.comBackup Log Client

The process or daemonname that wrote theerror message

bptm, ndmpagent, nbpem, bpbrmBackup Log DaemonName


648



The group ID that can bespecified by the backupproduct to group them ina certain way. Note:Thesecondary ID and theGroup ID are basicallyintended for the samepurpose, that is to groupthe jobs in some way thatis useful in reporting.

5980Backup Log Job GroupID

A unique number foreach backup job in abackup domain thatidentifies what backupjob caused the errormessage to be logged

6021Log Primary ID

The date/time that theerror message or log waswritten to

Mon 3/4/2008 3:34:34Log Time

The backup applicationname that caused theerror message to becreated

NetBackup, TSMProduct

The severity code of theerror message

1, 2, 3, 4 etc.Severity Code

The code representingthe type of the log anderror message

1, 2, 3, 4 etc.Type Code

The version of thelog/error message

1, 2, 3, 4 etc.Version

Agent Monitoring

A unique number foreach data collectionagent under theOpsCenter server

1, 2, 3, 4 etc.Agent ConfigurationID




The host name of theOpsCenter datacollection agent

ops-agent.example.comAgent Host

The date and time of thelast heartbeat from thedata collection agent tothe OpsCenter server

May 04, 2008 10:52:28Last Heartbeat

The host name of theOpsCenter server wherethe database and webinterface resides

ops-server.example.comServer

The number of secondssince the last heartbeatfrom the data collectionagent to the OpsCenterserver

44Time Since Agent LastHeartbeat


650

Man pages for CLIs


■ changeDbPassword

■ changeVxATProperties

■ configurePorts

■ dbbackup

■ dbdefrag

■ opsadmin

■ opsCenterAgentSupport

■ opsCenterSupport

■ runstoredquery

■ startagent

■ startdb

■ startgui

■ startserver

■ stopagent

■ stopdb

■ stopgui

■ stopserver

CAppendix

changeDbPasswordchangeDbPassword – This script changes the OpsCenter database password. Thisis supported only for DBA user and not for guest and server passwords.

SYNOPSISchangedbpassword [--setDBAPassword=<DBA password>]|[--restoreDefault]

| [-h|-?|--help]

DESCRIPTIONSybase SA (SQL Anywhere) database management system is used to store theOpsCenter data. You require a user name and a password to access the database.The following database user account is shipped with OpsCenter:

The database administrator account. The dba account isrequired by the database queries that are used to updatethe database schema or upgrade to a new product version.

dba

When the tool changes the dba password, it updates a configuration file on thefile system so that the server can still access the database. The password isencrypted before it is stored in the configuration file. However, since the serverneeds to retrieve the password it cannot be stored with a one-way hash. Thus,someone could obtain the password. When the tool is run, the system administratoris advised to check the permissions on the configuration file to ensure that onlyan administrator can read the file.

OPTIONS--setDBAPassword

Changes the database DBA password.

--restoreDefault

Resets all passwords to default passwords.

--h|-?|--help

Shows the CLI usage statement and exits.

NOTESEnter the following command to change the database password on Windows:

INSTALL_PATH\OpsCenter\server\bin\changeDbPassword.bat

Man pages for CLIschangeDbPassword

652

Enter the following command to change the database password on UNIX:

/opt/SYMCOpsCenterServer/bin/changeDbPassword.sh

653Man pages for CLIschangeDbPassword

changeVxATPropertieschangeVxATProperties – This script configures the Symantec ProductAuthentication Service (AT) Server parameters.

SYNOPSISchangeVxATProperties

DESCRIPTIONThe changeVxATProperties script prompts you to enter the following details:

■ Authentication Service Host Name

■ Authentication Service Port Number

■ Authentication Service Domain Name

■ Authentication Service User Name

■ Authentication Service Password

OPTIONSNot applicable

NOTESEnter the following command to configure AT parameters on Windows:

INSTALL_PATH\OpsCenter\server\bin\changeVxATProperties.bat

Enter the following command to configure AT parameters on UNIX:

/opt/SYMCOpsCenterServer/bin/changeVxATProperties.sh

Man pages for CLIschangeVxATProperties

654

configurePortsconfigurePorts – This script is used to configure Web server ports on Unix orLinux systems.

SYNOPSISconfigurePorts.sh [-status]|[-httpPort <httpPort>][-httpsPort

<httpsPort>][-shutdownPort <shutdownPort>]

DESCRIPTIONThe configurePorts script is used for the following purposes:

■ For configuring http, https and Tomcat shutdown ports

■ For querying the current values for the above ports

OPTIONS-status

Queries the current values for http, https and Tomcat shutdown ports

This option is to be used exclusive of other attributes.

-httpPort <httpPort>

Modifies the httpPort to the new value in web.xml of Tomcat

-httpsPort <httpsPort>

Modifies the httpsPort to the new value in web.xml of Tomcat

- shutdownPort <shutdownPort>

Modifies the shutdownPort to the new value in web.xml of Tomcat

NOTESTo know the HTTP and HTTPS port that OpsCenter uses, run the configurePortsutility.

Run the follwoing command on Windows:

INSTALL_PATH\OpsCenter\gui\bin\goodies\configurePorts.cmd -status

Run the following command on UNIX:

/opt/SYMCOpsCenterGUI/bin/goodies/configurePorts.sh -status

655Man pages for CLIsconfigurePorts

dbbackupdbbackup – This script backus up the OpsCenter database.

SYNOPSISdbbackup <DB_BACKUP_DIR> [-v | -restore]

DESCRIPTIONdbbackup is a script used for backing up the OpsCenter database.

OPTIONSDB_BACKUP_DIR

(Required) DB_BACKUP_DIR is the directory where the OpsCenter databaseis backed up to, or restored from. DB_BACKUP_DIR should be an absolutepath.

-v

Option to validate the database after backup

- restore

Option to restore database frombackupDir to the current database directory.

NOTESOn Windows, you perform backups with the dbbackup.bat batch file.

The backup script creates the following files in the backup directory: vxpmdb.dband vxpmdb.log

Data spaces are started when the main database is started; therefore, starting andstopping the data space file is not required.

EXAMPLESThe following command backs up the OpsCenter database to the my_db_backups

directory on Windows:

INSTALL_PATH\OpsCenter\server\bin\dbbackup.bat C:\my_db_backups

The following command backs up the OpsCenter database to the my_db_backups

directory on UNIX:

/opt/SYMCOpsCenterServer/bin/dbbackup.sh /my_db_backups

Man pages for CLIsdbbackup

656

dbdefragdbdefrag – This script defragments the OpsCenter database.

SYNOPSISdbdefrag

DESCRIPTIONThe dbdefrag script is used to defragment the OpsCenter database.


NOTESTo defragment the OpsCenter database run the following commands.

Run the following command on Windows:




657Man pages for CLIsdbdefrag

opsadminopsadmin – This script is used to monitor/start/stop the OpsCenter services onUnix or Linux systems

SYNOPSISopsadmin.sh {start|stop|monitor}

DESCRIPTIONThe opsadmin script is used for monitoring/starting/stopping the OpsCenterservices.

OPTIONSstart

Starts all OpsCenter services. This includes OpsCenter database, OpsCenterserver and Web server services.

stop

Stops all OpsCenter services. This includes OpsCenter database, OpsCenterserver and Web server services.

monitor

Monitors all OpsCenter services and also AT (Symantec ProductAuthentication Service) and PBX (Symantec Private Branch Exchange)services

NOTESopsadmin

opsadmin.sh resides by default in the /opt/SYMCOpsCenterServer/bindirectory.

EXAMPLESEXAMPLE 1

The following command starts all OpsCenter services:


EXAMPLE 2

The following command monitors OpsCenter services:

Man pages for CLIsopsadmin

658

/opt/SYMCOpsCenterServer/bin/opsadmin.sh monitor

659Man pages for CLIsopsadmin

opsCenterAgentSupportopsCenterAgentSupport – This script collects OpsCenter Agent configurationfiles and logs.

SYNOPSISopsCenterAgentSupport

DESCRIPTIONThe opsCenterAgentSupport script collects OpsCenter Agent configuration filesand logs for troubleshooting.


NOTESRun the following commands to execute the support scripts for OpsCenter Agent.


INSTALL_PATH\OpsCenter\Agent\bin\opsCenterAgentSupport.bat


/opt/SYMCOpsCenterAgent/bin/opsCenterAgentSupport.sh

You can view the following status messages on the command prompt:

Stopping the OpsCenter Agent Service...

Support Directory Exists. This will be deleted...

Support Directory Deleted...

Created Support Directory... Zipping Support Folder...

Please collect Support.zip file from

C:\PROGRA~1\Symantec\OPSCEN~1\Agent\temp\support.zip

Starting the OpsCenter Agent...

C:\Program Files\Symantec\OpsCenter\Agent\bin>

Man pages for CLIsopsCenterAgentSupport

660

opsCenterSupportopsCenterSupport – This script collects OpsCenter server configuration files andlogs for troubleshooting.

SYNOPSISopsCenterSupport

DESCRIPTIONopsCenterSupport is a script used for collecting OpsCenter server configurationfiles and logs for troubleshooting.


NOTESRun the following command to collect OpsCenter server configuration information:


/opt/SYMCOpsCenterServer/bin/opsCenterSupport.sh


INSTALL_PATH\OpsCenter\server\bin\opsCenterSupport.bat

You can view the following statuses on the command prompt:

Stopping the OpsCenter Web Console Service...

Stopping the OpsCenter Server...

Stopping the OpsCenter database...

Support Directory Exists. This will be deleted...

Support Directory Deleted...

Created Support Directory...

SupportDir=E:\OPSCEN~1\OPSCEN~1\server\temp\support

Collecting Installed Paths Collecting System Properties

Collecting Memory & Processor Properties

661Man pages for CLIsopsCenterSupport

Collecting Disk Allocation for OpsCenter Installed Drive

Collecting Directory Structure for OpsCenter Collecting version file

Collecting Version File...

Getting Customized Collections...

Do you want to Collect Configuration files [y/n]: (y)y

Do you want to Collect Application Log files [y/n]: (y)y

Do you want to Collect OpsCenter GUI(147) Log files [y/n]: (y)y

Collecting 147 files...

Do you want to Collect OpsCenter Server(148) Log files [y/n]: (y)y

Collecting 148 files...

Do you want to Collect db Log files [y/n]: (y)y

Collecting db logs...

Do you want to Collect WebServer Log files [y/n]: (y)y

Collecting WebServer logs...

Do you want to Collect setEnv file [y/n]: (y)y

Collecting setenv file...

Do you want to Collect Database files [y/n]: (y)y

Collecting vxpmdb file...

Collecting vxpmdb.log file...

If this is an Upgrade scenario Do you want to Collect Old Database

files and logs [y/n]: (y)y

Old dbfiles are not present in the path, hence not collected...

Collecting upgrade logs...

If this is an install scenario Do you want to Collect Installation

Logs [y/n]: (y)y

Zipping Support Folder...

Please collect Support.zip file from

E:\OPSCEN~1\OPSCEN~1\server\temp\support.zip

Starting the OpsCenter Database...

Starting the OpsCenter Server...

Man pages for CLIsopsCenterSupport

662

Starting OpsCenter Web Console Service...

C:\Documents and Settings>

663Man pages for CLIsopsCenterSupport

runstoredqueryrunstoredquery –

SYNOPSISrunStoredQuery <Report Name> <User Name> <Domain Name> <Domain Type>

[<Output Type> pdf | csv]

DESCRIPTIONThe runstoredquery script runs saved customSQL and the OpsCenterAdministrator generates output in the desired format.

OPTIONSReport Name

Name of the report (surrounded with double-quotes)

Example: runStoredQuery "My Report" admin OpsCenterUsers vx pdf

User Name

Name of the user who has saved the report

Domain Name

Domain name for the user

Domain Type

Domain type for the user

Output Type

Report output type (pdf/csv). The default is csv.

EXAMPLErunStoredQuery "My Report" admin OpsCenterUsers vx pdf

Man pages for CLIsrunstoredquery

664

startagentstartagent – This script starts the OpsCenter Agent service.

SYNOPSISstartagent

DESCRIPTIONThe startagent script is used to start the OpsCenter Agent service.


NOTESEnter the following command to start the OpsCenter Agent service on Windows:

INSTALL_PATH\OpsCenter\Agent\bin\startagent.bat

Enter the following command to start the OpsCenter Agent process on UNIX:


665Man pages for CLIsstartagent

startdbstartdb – This script starts the OpsCenter database.

SYNOPSISstartdb

DESCRIPTIONThe startdb script is used to start the OpsCenter database.


NOTESTo start the database server, enter the following command on Windows:

INSTALL_PATH\OpsCenter\server\bin\startdb.bat

To start the database server, enter the following command on UNIX:


Man pages for CLIsstartdb

666

startguistartgui – This script is used to start the OpsCenter Web server service on Unixor Linux systems.

SYNOPSISstartgui.sh

DESCRIPTIONThe startgui script is used for starting the OpsCenter Web server service.


NOTESThe following command starts the OpsCenter WebServer service on Windows:

INSTALL_PATH\OpsCenter\gui\bin\startgui.cmd

The following command starts the OpsCenter WebServer service on UNIX:

/opt/SYMCOpsCenterGUI/bin/startgui.sh

667Man pages for CLIsstartgui

startserverstartserver – This script starts the OpsCenter Server.

SYNOPSISstartserver

DESCRIPTIONThe startserver script is used to start the OpsCenter Server.


NOTESRun the following command to start the OpsCenter Server on Windows:

INSTALL_PATH\OpsCenter\server\bin\startserver.bat

Run the following command to start the OpsCenter Server on UNIX:


Man pages for CLIsstartserver

668

stopagentstopagent – This script is used to stop the OpsCenter Agent.

SYNOPSISstopagent

DESCRIPTIONThe stopagent script is used to stop the OpsCenter Agent on UNIX.


NOTESRun the following command to stop the OpsCenter Agent:


669Man pages for CLIsstopagent

stopdbstopdb – This script is used to stop the OpsCenter database.

SYNOPSISstopdb

DESCRIPTIONThe stopdb script is used to stop the OpsCenter database.


NOTESRun the following command to stop the OpsCenter database on Windows:

INSTALL_PATH\OpsCenter\server\bin\stopdb.bat

Run the following command to stop the OpsCenter database on UNIX:


Man pages for CLIsstopdb

670

stopguistopgui – used to stop the OpsCenter Web server service.

SYNOPSISstopgui.sh

DESCRIPTIONThe stopgui script is used for stopping the OpsCenter Web server service.


NOTESThe following command stops the OpsCenter Web server service on Windows:

INSTALL_PATH\OpsCenter\gui\bin\stopgui.cmd

The following command stops the OpsCenter Web server process on UNIX:

/opt/SYMCOpsCenterGUI/bin/stopgui.sh

671Man pages for CLIsstopgui

stopserverstopserver – This script stops the OpsCenter Server.

SYNOPSISstopserver

DESCRIPTIONThe stopserver script is used to stop the OpsCenter Server.


NOTESRun the following command to stop the OpsCenter Server on Windows:

INSTALL_PATH\OpsCenter\server\bin\stopserver.bat

Run the following command to stop the OpsCenter Server on UNIX:


Man pages for CLIsstopserver

672

Administrator Console See CommandCentral Service View Builder.

application A program or group of programs designed to perform a specific task. OracleDatabase and Veritas NetBackup are examples of applications.

CommandCentral Alert

Manager

A Server component that manages policies associated with objects on the storagenetwork. A policy associates certain sets of conditions with storage resources anddefines actions to be taken when these conditions are detected. The Alert Manageris seamlessly integrated with the CommandCentral product offerings so thatConsole users can monitor, define, and modify policies.

Data Collector Data collector is a part of Symantec OpsCenter Agent that collects data fromvarious products.

event A notification that indicates when an action, such as an alert or a change in state,has occurred for one or more objects on the storage network.

My Reports In CommandCentral Service, a Console area in which to display and run customreports saved by the user.

VAS (VERITAS

Authentication Service)

A component of the VERITAS Security Services (VxSS) that is used by theCommandCentral offerings to provide user authentication. VAS is a set of processesand runtime libraries that enables users to log on to multiple VERITAS productswith one logon.

VxPBX (VERITASPrivate

Branch Exchange)

A common VERITAS component that uses socket passing to reduce the numberof ports required to be open across a firewall. VxPBX uses a paradigm similar tothat of a telephone switchboard in which calls placed to a switchboard areredirected to a known extension. In the PBX exchange, client connections sent tothe exchange's port are redirected to an extension associated with theCommandCentral Service Management Server.

CommandCentral

Console

A graphical user interface that displays reports and other information for usersof CommandCentral Service through a standard Web browser. The Consoleprovides a central point to manage cost analysis and chargeback for services,managing workflow, displaying and managing reports, and other tasks.

CommandCentral

Database

A database, residing on the Server, that gathers data related to performance andmonitoring, reports, alarms, service requests, and the SAN Access Layer (SAL). ASybase ASA (Adaptive Server Anywhere) database management system, the Serverdatabase is installed silently when you install CommandCentral Service.

Glossary

CommandCentral

Service

A product offering that tracks IT effectiveness by providing completebusiness-level reporting of resource utilization, costs, and service level delivery.CommandCentral Service also helps enable business customers ensure that theirapplication performance and availability requirements are met at the lowest cost.

Symantec OpsCenter

Analytics

The licensed version of OpsCenter is called Symantec OpsCenter Analytics.

Symantec OpsCenter Analytics lets you do advanced business-level reporting.

CommandCentral

Service Agent

The part of CommandCentral Service that collects information from discoverableapplications residing on remote host systems, such as VERITAS NetBackup,VERITAS Backup Exec, and EMC Legato Networker. CommandCentral Serviceformats the information collected from these applications and displays it throughthe CommandCentral Console.

CommandCentral

Service Management

Server

The portion of the CommandCentral Service product offering that resides on theprimary host.

CommandCentral

Service View Builder

A Flash-based application in which an administrator creates, modifies, andmanages access to the object views that users see in the CommandCentral Console.(An earlier, Java-based version of this application was known as the AdministratorConsole in earlier releases of CommandCentral Service.) See also object view.

Views Symantec OpsCenter views are logical groups of IT assets (hosts or file systems)organized in a hierarchical manner. You can create views in Java View Builderand make them available in the Symantec OpsCenter console. The following viewdetails appear in the Symantec OpsCenter console.

Symantec OpsCenter Glossary674

Aabout Symantec OpsCenter 19about Symantec OpsCenter Analytics 20access OpsCenter console 37ActiveX 35add

master server 354NetBackup 7.0 master server 355

addingexisting user 314new user 314

adding host alias 305adding licenses 300adding users 310Agent

deploying 125overview 30

Agent deployment 125agent.conf file 33alert policies

alert conditions 472alerts

filtering by type 461responding to 462

archive data 368

Bbacking up

OpsCenter database 271bookmarks

using with OpsCenter 75business planning 23

CchangeDbPassword 652changeVxATProperties 654changing AT parameters 263changing password 299chargeback

cost variables 325, 327

chargeback (continued)formulae 328modeling 329

cluster 235, 243fatal error during uninstallation 250installing OpsCenter server

UNIX 247Windows 240

limitationsUNIX 244Windows 237

OpsCenter serverWindows 236

preinstallation checklist 245all VCS cluster configurations 246VxVM 246

prerequisitesUNIX 244Windows 237

supported solutions 235uninstalling OpsCenter server

UNIX 249Windows 243

color codingin OpsCenter 68

compliance reporting 23configure

session timeout interval 50configure SMTP 303configure ThreatCon feature 304configurePorts 655configuring

Enterprise Vault data collector 377configuring NetBackup PureDisk data collector 366connected

master server state 353Content pane

enlarging 68Summary and Hierarchical views 65

control OpsCenter loggingon UNIX 288on Windows 287

Index

control OpsCenter servicesAgent service on UNIX 259Agent service on Windows 257all server services on UNIX 257all server services on Windows 256database server on UNIX 257database server on Windows 256OpsCenter server on UNIX 258OpsCenter server on Windows 256OpsCenter Web Server service on UNIX 258OpsCenter Web Server service on Windows 256

controlling OpsCenter services and processes 255copying

user profile 307cost

formulae 328cost estimation 329costs variables 325create alert policy 480creating

cost formulae 328cost variables 325custom report 555custom SQL query 556email recipients 319SNMP trap recipients 321views 388

custom reports 548custom SQL query 548customizing

alert settings 532

DData migration

from NOM to OpsCenter 177from VBR to OpsCenter 192

data purgeconfigure 301restore NOM or VBR purge settings after

upgrade 302database

see (OpsCenter database) 260dbbackup 656dbdefrag 657deduplication 364defining

cost formulae 328cost variables 325

deletemaster server 362

Deletinguser group 317

deletingalert recipients 323cost formulae 328

deleting user 314dependency of OpsCenter services 259deployment mode

multi domain 372single domain 372standalone mode 372

Difference between Symantec OpsCenter andSymantec OpsCenter Analytics 113

disable security warningson IE 6.0 37on Mozilla 38on Mozilla and IE 39

documentationfor Sybase 260HTTP and HTTPS ports 281NBSL 122NetBackup 34SymcOpsCenterWebServer 110VxUL 110

Eedit

master server 362editing

currency list 324editing user profile 314editing users 310email

report 554email recipients

creating 319EMC Legato Networker 380Enterprise Vault 368

data types 368versions supported 370

Enterprise Vault data collector 377data collection checklist 378deployment scenarios 370

error messageFatal error during installation 250

exportingreport 553

Index676

Ffile formats 553firewall considerations 276firewalls

Symantec Private Branch Exchange 28floating-point math and OpsCenter 230

Ggetting started with typical OpsCenter tasks 74Guided Recovery 503

Destination host and login screen 508Job Details screen 510metadata 504, 511Performing a cloning operation 505Post-clone operations 510Pre-clone check screen 510Pre-operation checks 504Select Control File Backup screen 507Select Destination Parameters screen 509Select Master Server screen 507Select Source Database screen 507Selection summary screen 509Troubleshooting 511

Hheap size

adjusting 222HTTP 280HTTPS 280

IIBM Tivoli Storage Manager 378icons for managed server status 68install

7.0.1 release update 77AT

UNIX 245Windows 238

clustering. See clusterNetBackup media kit 116OpsCenter DVD 116

install and upgrade checklist 130install OpsCenter

on UNIX 139on Windows 135

installingOpsCenter 7.0.1

AIX 99

installing (continued)OpsCenter 7.0.1 (continued)

UNIX (non-AIX) 96Windows 84

Installing OpsCenter 134

JJavaScript 35jre (Java Run Time Environment) 110

LLegato data collector 380License Capacity Alert 470license keys 112

adding 300deleting 301viewing 301

licensed OpsCenter features 114licensing model 111log files

on UNIX servers 291on Windows servers 288

loggingin to OpsCenter 44out of OpsCenter 50

MManage views

controlling scope 468manage alert policies 468manage devices 491manage storage 486

managed master server considerations 121managed server icons 68Management Information Base (MIB) 515managing

folders 563managing licenses 300merging objects 306Microsoft Internet Explorer 36Microsoft SQL Server

versions supported 370modeling

chargeback 329modifying

alert recipients 322cost formulae 328cost variables 327

677Index

modifying (continued)report export location 308tape library 306

Monitor viewscontrolling scope 400

monitor viewsmonitoring alerts 458monitoring devices 447monitoring hosts 454monitoring jobs 407monitoring media 437monitoring policies 429monitoring services 426

Mozilla Firefox 36My Dashboard tab 561My Reports tab 557

Nnbproxy process 259NetBackup data collection

adding a master server 354concept 348deleting a master server 362editing a master server 362enabling or disabling data collection 363managed master server versions 349supported data types and collection status 351

NetBackup Service Layer (NBSL) 122, 282, 348Network Address Translation (NAT) network

considerations 121not connected

master server state 353

Oobject types 308opsadmin 658OpsCenter

adjustingheap size 222Sybase cache size 227

and floating-point math 230color keys 68database 123defragmenting databases 263installing

UNIX 139Windows 135

sanity check after installing 212

OpsCenter (continued)sizing 122status bar 68status icons 68store database and logs on separate disk 264Sybase database used 111tasks performed on startup 213uninstalling

UNIX 233Windows 233

OpsCenter 7.0.1new features 24

OpsCenter 7.0.1 installationOperating System requirements 78supported backup and archive products 81

OpsCenter alertsabout alert policies 470alert conditions 472creating alert policy 472managing alert policy 485understanding alert counts 484

OpsCenter architecturedatabase 29Server and Authentication Service 30

OpsCenter back up and restore procedures 270OpsCenter console

alert summary pane 64content pane 65description 55quick links 64tabs and subtabs 58ThreatCon pane 63title bar 57View pane 59

OpsCenter context-sensitive helplocating 34

OpsCenter databaseback up using backupDB script 270backing up 271restoring 273

OpsCenter database password file 273OpsCenter database utilities

change database administrator password 261defragment OpsCenter databases 263

OpsCenter installationhardware requirements 122install checklist 130master server considerations 121Operating System requirements 116

Index678

OpsCenter installation (continued)supported backup and archive products 119,

337web browser considerations 35

OpsCenter post-installationstarting to use OpsCenter 212

OpsCenter processeson UNIX 253

OpsCenter reports 535OpsCenter Server 27

Authentication Service 30OpsCenter server scripts

on Windows and UNIX 254OpsCenter services

on Microsoft Windows 252OpsCenter start-up tasks 213OpsCenter system requirements

see OpsCenter 122OpsCenter upgrade procedures 159OpsCenter user profiles 272OpsCenter View Builder. See View Builder 33OpsCenter views

overview 383opsCenterAgentSupport 660opsCenterSupport 661originator ID 287OS considerations 80, 118

Ppartially connected

master server state 353PBX 28PDOS 364performance tuning 213policy

filtering by type 432ports

Symantec Private Branch Exchange 28product ID 287

Qquick links

minimizing 64quick start for OpsCenter tasks 74

Rrefresh OpsCenter console 59report schedules 566

report template 574report templates 537reports

Scheduled Jobs 583restoring

OpsCenter 273runstoredquery 664

Ssaving

report 551Scheduled Jobs reports 583

All Jobs report 586scheduled jobs reports

Job Count Details-Scheduled Vs Actualreport 585

Job Count Within Backup Window report 584Job Count-Scheduled Vs Actual report 584

schedules 565scripts

runstoredquery 664server.conf file 229services

controlling 428filtering by type 427

settingdefault currency 323

Simple Network Management Protocol (SNMP) 513configuring community name 530configuring SNMP version 531SNMP traps 515supported SNMP versions 514

Single Instance StorageSIS 364

SNMP in OpsCenter 282SNMP trap recipients

creating 321SNMP traps 282software components used by OpsCenter 109standard reports

descriptions 592start-up tasks

OpsCenter server 213startagent 665startdb 666startgui 667starting

runstoredquery 664startserver 668

679Index

status icons in OpsCenter 68stopagent 669stopdb 670stopgui 671stopserver 672supported backup and archive products 337supported backup products 23supported platforms 116supported upgrade paths 125Sybase cache size

adjusting 227Symantec Java Web Server

(SymcOpsCenterWebServer) 110Symantec OpsCenter Analytics and Symantec

OpsCenter 111Symantec Private Branch Exchange 28

port number configuration 110Symantec Private Branch Exchange (PBX) 110

port number configuration 359Symantec Private Branch Exchange (VxPBX)

port number configuration 281–282Symantec Product Authentication Service

installingUNIX 245

overview 30shared component 110Windows

installing 238

Ttables in OpsCenter

applying filters 73creating custom filters 73customizing 70selecting rows 72using filters 73viewing hidden columns 70viewing multiple pages 72

time schedule 572tool tips 69troubleshooting

accessing OpsCenter 41OpsCenter console logon issues 45OpsCenter server issues 51support script in OpsCenter 283VBR database inconsistency issues 176

TSMdata collector 378

tuning OpsCenter for performance 213

Uunified logging (VxUL) 286uninstall

7.0.1 release update 103uninstalling

OpsCenterUNIX 233

OpsCenter 7.0.1AIX 102UNIX (non-AIX) 105Windows 103

OpsCenter 7.0.1 clusterUNIX 106

OpsCenter on Windows 233UNIX

installingOpsCenter 139

upgrading to OpsCenterdefault data purge settings 302from NOM on UNIX 163from NOM on Windows 161from VBR on UNIX 172from VBR on Windows 166use NOM or VBR purge settings 302

user access rights 310user groups

creating 316user profiles

viewing 314using an old NOM or VBR installation 231

VVBR upgrade considerations 159Veritas Cluster Server (VCS) for UNIX/Linux

preinstallation checklist 246Veritas NetBackup PureDisk

PDOS 364Veritas Unified Logging (VxUL) 110

log files 286originator IDs used by OpsCenter 287

view NOM data migration status 186view OpsCenter alerts

using HP OV NNM 534using HP OV NNM 7.50/7.51 on Windows 534using SCOM 2007 533

View panemaking selections 60using 59

view VBR data migration status 200

Index680

viewingemail recipients 317host alias 305

viewing alertsusing List View 459using Summary View 464

viewing license 300views

view type 385visual keys

in the OpsCenter console 68

Wweb browser

book marks 75pop-up blockers 35support 36UTF-8 35

Windowsinstalling

OpsCenter 135uninstalling

OpsCenter 233

681Index