Net Backup Ops Center

Symantec OpsCenter Administrator's Guide
Windows and UNIX
Release 7.0
Symantec OpsCenter Administrator's Guide

The software described in this book is furnished under a license agreement and may be used only in accordance with the terms of the agreement. Documentation version 7.0
Legal Notice
Copyright 2009 Symantec Corporation. All rights reserved. Symantec, the Symantec Logo are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners. This Symantec product may contain third party software for which Symantec is required to provide attribution to the third party (Third Party Programs). Some of the Third Party Programs are available under open source or free software licenses. The License Agreement accompanying the Software does not alter any rights or obligations you may have under those open source or free software licenses. Please see the Third Party Legal Notice Appendix to this Documentation or TPIP ReadMe File accompanying this Symantec product for more information 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 document may be reproduced in any form by any means without prior written authorization of Symantec 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 OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE. The Licensed Software and Documentation are deemed to be commercial computer software as 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 in Commercial Computer Software or Commercial Computer Software Documentation", as applicable, 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 Corporation 350 Ellis Street Mountain View, CA 94043 http://www.symantec.com
Acknowledgments
examples: This product includes software developed by the Apache Software Foundation (http://www.apache.org/), namely Tomcat Servlet Container, Jakarta Commons, Sprint Framework, Active MQ, Ehcache, Xerces XML Parser, Piccolo XML Parser, Log4J and Apache XML-RPC. A copy of Apache Software License 1.1 and 2.0 can be found at www.apache.org/licenses/. The Piccolo XML Parser library is copyright Yuval Oren.
Technical Support
Symantec Technical Support maintains support centers globally. Technical Supports primary role is to respond to specific queries about product features and functionality. The Technical Support group also creates content for our online Knowledge Base. The Technical Support group works collaboratively with the other functional areas within Symantec to answer your questions in a timely fashion. For example, the Technical Support group works with Product Engineering and Symantec Security Response to provide alerting services and virus definition updates. Symantecs maintenance offerings include the following:
A range of support options that give you the flexibility to select the right amount of service for any size organization Telephone and Web-based support that provides rapid response and up-to-the-minute information Upgrade assurance that delivers automatic software upgrade protection Global support that is available 24 hours a day, 7 days a week Advanced features, including Account Management Services
For information about Symantecs Maintenance Programs, you can visit our Web site at the following URL: www.symantec.com/techsupp/
Contacting Technical Support

Customers with a current maintenance agreement may access Technical Support information at the following URL: www.symantec.com/techsupp/ Before contacting Technical Support, make sure you have satisfied the system requirements that are listed in your product documentation. Also, you should be at the computer on which the problem occurred, in case it is necessary to replicate the problem. When you contact Technical Support, please have the following information available:

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 registration

If your Symantec product requires registration or a license key, access our technical support Web page at the following URL: www.symantec.com/techsupp/
Customer service
Customer service information is available at the following URL: www.symantec.com/techsupp/ Customer Service is available to assist with the following 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 maintenance 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
Maintenance agreement resources

If you want to contact Symantec regarding an existing maintenance agreement, please contact the maintenance agreement administration team for your region as follows:
Asia-Pacific and Japan Europe, Middle-East, and Africa North America and Latin America customercare_apac@symantec.com semea@symantec.com supportsolutions@symantec.com
Additional enterprise services

Symantec offers a comprehensive set of services that allow you to maximize your investment in Symantec products and to develop your knowledge, expertise, and global insight, which enable you to manage your business risks proactively. Enterprise services that are available include the following:
Symantec Early Warning Solutions These solutions provide early warning of cyber attacks, comprehensive threat analysis, and countermeasures to prevent attacks before they occur. Managed Security Services These services remove the burden of managing and monitoring security devices and events, ensuring rapid response to real threats. Symantec Consulting Services provide on-site technical expertise from Symantec and its trusted partners. Symantec Consulting Services offer a variety of prepackaged and customizable options that include assessment, design, implementation, monitoring, and management capabilities. Each is focused on establishing and maintaining the integrity and availability of your IT resources. Educational Services provide a full array of technical training, security education, security certification, and awareness communication programs.
Consulting Services
Educational Services
To access more information about Enterprise services, please visit our Web site at the following URL: www.symantec.com Select your country or language from the site index.
Contents
Technical Support ............................................................................................... 4 Chapter 1 Getting started using Symantec OpsCenter .................. 19
About Symantec OpsCenter ............................................................ About Symantec OpsCenter functions ........................................ About Symantec OpsCenter Analytics functions .......................... About monitoring and managing NetBackup ............................... About alerting in OpsCenter ..................................................... About reporting in Symantec OpsCenter Analytics ....................... About whats new with OpsCenter in comparison with NOM and VBR ..................................................................................... About OpsCenter components ........................................................ About the OpsCenter Server ..................................................... About the OpsCenter Agent ...................................................... About the OpsCenter Java View Builder ..................................... About using the OpsCenter console ................................................. About starting the OpsCenter console .............................................. About Web browser considerations ........................................... About accessing the OpsCenter console ...................................... Logging on to the Symantec OpsCenter console ........................... Logging out of the OpsCenter console ........................................ Configuring the OpsCenter session timeout interval ..................... About possible OpsCenter console issues .................................... About OpsCenter console components ............................................. About using the links on the title bar ......................................... About using tabs and subtabs ................................................... About refreshing the OpsCenter console ..................................... Using the Task pane ............................................................... About the View pane ............................................................... About the Symantec ThreatCon pane ......................................... Using the quick links in the Task pane ....................................... Using the content pane ........................................................... About the OpsCenter status bar ................................................ About visual keys in the console ............................................... About using tables .................................................................. About quickly performing common tasks in OpsCenter ....................... 19 20 20 22 22 22 24 26 26 29 31 32 32 33 34 41 43 43 44 47 48 49 50 50 51 53 53 54 57 57 58 63
Contents
About using Web browser bookmarks .............................................. 64 About OpsCenter documentation .................................................... 64
Chapter 2
Installing Symantec OpsCenter ........................................ 67

Planning an OpsCenter installation ................................................. 67 About the software components that OpsCenter uses .................... 67 About the OpsCenter licensing model ........................................ 69 About the NetBackup and OpsCenter DVD .................................. 74 About platforms supported by OpsCenter ................................... 74 About backup and archiving products supported by Symantec OpsCenter ....................................................................... 76 About managed NetBackup master server considerations .............. 78 Design your OpsCenter server .................................................. 80 About supported upgrade paths ................................................ 81 About OpsCenter Agent deployment .......................................... 81 Before you install or upgrade .................................................... 86 Installing Symantec OpsCenter on Windows and UNIX ....................... 90 Installing Symantec OpsCenter on Windows ............................... 91 Installing Symantec OpsCenter on UNIX .................................... 96 Upgrading to OpsCenter on Windows and UNIX ............................... 102 Upgrade considerations ......................................................... 102 Upgrading from NetBackup Operations Manager to Symantec OpsCenter on Windows and UNIX ...................................... 103 Upgrading from Veritas Backup Reporter to OpsCenter Analytics on Windows and UNIX .................................................... 108 Monitoring data migration from NOM to Symantec OpsCenter ..................................................................... 120 Monitoring data migration from VBR to Symantec OpsCenter Analytics ...................................................................... 134 Upgrading to OpsCenter Server on a different UNIX system ......... 148 Post-installation tasks ................................................................ 153 Verifying that Symantec OpsCenter is running properly .............. 154 About starting to use OpsCenter .............................................. 154 About the start-up tasks that OpsCenter performs ...................... 155 Tuning OpsCenter for more performance .................................. 155 Using an earlier NOM or VBR installation after upgrade .................... 162 Uninstalling Symantec OpsCenter on Windows and UNIX .................. 163 Uninstalling Symantec OpsCenter on Windows .......................... 163 Uninstalling Symantec OpsCenter on UNIX .............................. 164 Clustering Symantec OpsCenter .................................................... 166 About a Symantec OpsCenter cluster ........................................ 166 Supported cluster solutions .................................................... 166
Contents
Clustering Symantec OpsCenter on Windows ............................. Uninstalling Symantec OpsCenter from the cluster ..................... Clustering Symantec OpsCenter Server on UNIX ........................ Uninstalling OpsCenter Server from the cluster .........................
167 173 173 181
Chapter 3
Administering Symantec OpsCenter ............................. 183

About OpsCenter services and processes used by OpsCenter ............... About services used by OpsCenter on Windows .......................... About processes used by OpsCenter on UNIX ............................. About OpsCenter server scripts on Windows and UNIX ..................... Controlling OpsCenter services and processes ........................... About dependency of services ................................................. About nbproxy processes on NetBackup master servers ............... About OpsCenter database administration ...................................... Running OpsCenter commands ............................................... Saving the OpsCenter database and database logs on separate hard disks ..................................................................... About database troubleshooting .............................................. About backup and restore of OpsCenter and OpsCenter Analytics ............................................................................ Backing up OpsCenter ........................................................... Restoring OpsCenter ............................................................. About communication and firewall considerations ........................... About ports required to communicate with backup products ....................................................................... About Web browser to OpsCenter Web GUI connection ............... About OpsCenter Web GUI to OpsCenter server software communication .............................................................. About OpsCenter server to NetBackup master server (NBSL) communication .............................................................. About SNMP traps ................................................................ About OpsCenter Web GUI/OpsCenter server to Sybase database communication .............................................................. About OpsCenter Web GUI to OpsCenter server email communication .............................................................. Gathering troubleshooting data with the support script ..................... About OpsCenter log files ............................................................. About VxUL log files ............................................................. About OpsCenter log files on Windows servers ........................... About OpsCenter log files on UNIX servers ................................ 183 183 184 185 187 191 191 192 192 195 199 199 199 202 205 208 209 210 211 211 211 211 212 213 213 215 217
10
Contents
Chapter 4
Understanding OpsCenter settings ............................... 221

About the settings in OpsCenter .................................................... Setting user preferences .............................................................. Changing your password ........................................................ Managing licenses ...................................................................... Adding license keys .............................................................. Viewing license keys ............................................................. Deleting license keys ............................................................. 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 ............................................................... Modifying object types .......................................................... Deleting object types ............................................................. Adding attributes ................................................................. Deleting attributes ................................................................ Managing users .......................................................................... About user access rights ........................................................ Viewing the list of existing users ............................................. Adding new users ................................................................. Editing users ....................................................................... Resetting user password ........................................................ Deleting users ...................................................................... Viewing user groups ............................................................. Adding user groups ............................................................... Editing user groups ............................................................... Deleting user groups ............................................................. Managing recipients ................................................................... Viewing email recipients ........................................................ Viewing SNMP trap recipients ................................................ Creating email recipients ....................................................... Creating SNMP trap recipients ................................................ Modifying Email or SNMP recipient information ........................ Deleting Email or SNMP recipient ............................................ Managing cost analysis and chargeback for OpsCenter Analytics ........ Setting a default currency for cost reports ................................ Editing currency list ............................................................. 222 223 225 226 226 227 227 227 228 229 230 231 232 232 233 233 234 234 234 235 235 235 239 239 240 240 241 241 242 242 242 243 243 244 245 247 248 249 249 249 250
Contents
11
Managing Cost Variables ....................................................... 251 Managing cost formulae ........................................................ 254 Managing cost estimation ...................................................... 255
Chapter 5
Understanding data collection ....................................... 259

About data collection in OpsCenter ................................................ About backup and archiving products supported by Symantec OpsCenter ..................................................................... About OpsCenter Agents ........................................................ About Data Collectors ............................................................ Managing OpsCenter Agents ........................................................ Viewing Agent status ............................................................ Configuring an OpsCenter Agent ............................................. Modifying an Agent .............................................................. Deleting Agents ................................................................... Managing Data Collectors ............................................................ Viewing Data Collector status ................................................. Configuring a Data Collector ................................................... Modifying a Data Collector configuration .................................. Deleting Data Collectors ........................................................ Configuring data collection for NetBackup ...................................... About the NetBackup data collection view ................................. How OpsCenter collects data from NetBackup ............................ About NetBackup versions that OpsCenter 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 ........................... Collecting data from Backup Exec .................................................. Collecting data from PureDisk ...................................................... Setting up a trust between the PureDisk SPA host and OpsCenter AB host ......................................................................... Configuring PureDisk data collector ......................................... Collecting data from Enterprise Vault ............................................ About Enterprise Vault .......................................................... About data collected from Enterprise Vault ............................... About versions supported by OpsCenter ................................... Planning the Enterprise Vault data collector deployment ............. About OpsCenter Agent deployment modes ............................... Accessing MS SQL Server host ................................................ 259 260 262 262 264 264 265 265 265 266 266 267 269 270 270 270 271 273 273 278 286 286 287 287 288 290 291 292 292 293 295 295 297 298
12
Contents
About creating a user for integrated logon ................................ Configuring the OpsCenter Agent properties for integrated logon ............................................................................ Installing MS SQL Server JDBC driver ...................................... Configuring Enterprise Vault data collector ............................... Collecting data from IBM Tivoli Storage Manager ............................. Collecting data from EMC Legato Networker ....................................
298 300 301 302 303 305
Chapter 6
Managing OpsCenter views
............................................ 307 307 309 310 310 310 311 311 312 313 314 314 315 315 316 316 316 317 318
About OpsCenter views ............................................................... About view types .................................................................. About accessing OpsCenter views ............................................ About view levels ................................................................. About nodes and objects ........................................................ Managing views ......................................................................... Viewing OpsCenter views and their details ................................ Creating views ..................................................................... Modifying views ................................................................... Deleting views ..................................................................... Modifying view level alias ...................................................... Managing nodes and objects ......................................................... Adding nodes to a view .......................................................... Modifying node details .......................................................... Deleting nodes ..................................................................... Adding objects to a view node ................................................. Deleting objects from a view node ............................................ Working with view filters .......................................................
Chapter 7
Monitoring NetBackup using Symantec OpsCenter .....................................................................

About the Monitor views .............................................................. Controlling the scope of Monitor views ........................................... About timeframe selection ..................................................... Monitoring NetBackup using the Overview subtab ............................ 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 ........................... About Top 7 Policies by Failed Jobs section ................................
323 323 324 324 325 326 326 327 327 328 329 330 330
Contents
13
Viewing the Alert Summary by Severity section ......................... Monitoring NetBackup jobs .......................................................... Using the List View for monitoring jobs .................................... Using the Summary View for monitoring jobs ............................ Using the Hierarchical View for monitoring jobs ........................ Monitoring NetBackup services ..................................................... Filtering on NetBackup service type ......................................... Controlling NetBackup services ............................................... Monitoring NetBackup policies ..................................................... Using the List View for monitoring NetBackup policies ................ Using the Summary View for monitoring policies ....................... Monitoring NetBackup media ....................................................... Using the List View for monitoring NetBackup media .................. Using the Summary View for monitoring NetBackup media ......... Using the Hierarchical View by Volume Pool for monitoring media ........................................................................... Using the Hierarchical View by Volume Group for monitoring media ........................................................................... Monitoring NetBackup devices ...................................................... Using the List View for monitoring drives ................................. Using the Summary view to monitor drives ............................... Monitoring NetBackup disk pools ............................................ Monitoring NetBackup hosts ........................................................ Monitoring NetBackup master servers ...................................... Monitoring NetBackup media servers ....................................... Monitoring NetBackup clients ................................................. Monitoring NetBackup alerts ........................................................ Using the List View for monitoring NetBackup alerts .................. Using the Summary View for monitoring NetBackup alerts ..........
331 331 332 340 343 348 349 350 350 351 357 359 360 364 365 366 368 369 373 374 375 376 378 378 379 380 386
Chapter 8
Managing NetBackup using Symantec OpsCenter .....................................................................

About the Manage views .............................................................. Controlling the scope of Manage views ........................................... Managing alert policies ............................................................... About OpsCenter alert policies ................................................ Viewing the details for a single alert policy ............................... Filtering on type of alert policy ............................................... Creating (or changing) an alert policy ....................................... Managing an alert policy ....................................................... Viewing the alerts associated with an alert policy ....................... Managing NetBackup storage .......................................................
389 389 390 390 392 393 393 394 407 407 408
14
Contents
Managing Storage Units ........................................................ Managing Storage Unit Groups ............................................... Managing storage lifecycle policy ............................................ Managing NetBackup devices ....................................................... Managing drives ................................................................... Managing robots .................................................................. Managing disk pools ............................................................. Managing SAN clients ........................................................... Managing Fibre Transport (FT) servers .....................................
408 410 411 413 414 418 420 422 423
Chapter 9
Using Guided Recovery ..................................................... 427

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 ................................................. Troubleshooting files for metadata collection operations at the time of the backup .......................................................... Troubleshooting files for Guided Recovery validation operations ..................................................................... Troubleshooting files for Guided Recovery cloning operations ..................................................................... 427 428 428 429 431 431 431 432 433 433 434 434 434 434 435 435 436
Chapter 10
Understanding OpsCenter alert policies and alerts ..............................................................................

About managing OpsCenter alerts in Microsoft Operations Manager 2005 .................................................................................. About managing OpsCenter alerts using Microsoft System Center Operations Manager 2007 ...................................................... About managing OpsCenter alerts using HP OpenView Network Node Manager 7.50/7.51 on Windows .............................................. About using SNMP with OpsCenter ................................................ About SNMP ........................................................................
437 437 438 438 439 439
Contents
15
About SNMP versions ............................................................ About SNMP versions supported in OpsCenter ........................... About the Management Information Base (MIB) and OpsCenter support ......................................................................... Configuring the SNMP trap community name for OpsCenter ..................................................................... Configuring the SNMP version for sending SNMP traps ............... About customizing alert settings ............................................. Frequently asked SNMP questions ...........................................
439 440 440 453 454 455 456
Chapter 11
Reporting in OpsCenter .................................................... 457

About OpsCenter reports ............................................................. About the OpsCenter reports UI .............................................. About report creation wizards ................................................ About Report Templates ........................................................ About custom reports ............................................................ About custom SQL query ....................................................... Working with Report Templates ................................................... About report filters ............................................................... Creating a report using a Report Template ............................... Managing reports ....................................................................... Saving a report .................................................................... Exporting a report ................................................................ Emailing a report ................................................................. Creating a custom report ............................................................. About report conditions ......................................................... Creating a report using SQL query ................................................. Managing My Reports ................................................................. Creating a report using My Reports tab .................................... Deleting a saved report .......................................................... Viewing a saved report .......................................................... Editing a saved report ........................................................... Export a saved report ............................................................ Email a saved report ............................................................. Managing My Dashboard ............................................................. Adding reports to a dashboard ................................................ Modifying a dashboard section ................................................ Deleting a dashboard section .................................................. Emailing dashboard sections .................................................. Refreshing My Dashboard ...................................................... Managing folders ....................................................................... Adding a folder .................................................................... 457 458 459 459 460 461 461 462 462 463 463 466 467 468 468 469 470 470 470 470 471 473 473 474 474 475 475 476 476 476 476
16
Contents
Editing a folder .................................................................... Deleting folders ................................................................... Deleting reports from a folder ................................................ About schedules ......................................................................... Managing report schedules .......................................................... Viewing report schedule details .............................................. Creating a report schedule ..................................................... Editing a report schedule ....................................................... Deleting a report schedule ...................................................... Managing time schedules ............................................................. Viewing time schedule details ................................................. Creating a time schedule ........................................................ Editing a time schedule .......................................................... Deleting a time schedule ........................................................ About Report Templates descriptions ............................................. About archive reports ........................................................... About backup reports ............................................................ About catalog reports ............................................................ About chargeback reports ...................................................... About client reports .............................................................. About Disk Based Data Protection ........................................... About job reports ................................................................. About media reports ............................................................. About performance reports .................................................... About policy reports ............................................................. About vault reports ...............................................................
477 478 478 478 479 479 481 484 484 485 485 485 486 487 487 488 489 504 505 505 510 511 514 517 520 522
Appendix A
About additional information on PureDisk data collection ....................................................................... 525

About AT configuration scenarios specific to PureDisk backup product .............................................................................. Scenario 1: Common Root Broker ............................................ Scenario 2: Different Root Brokers ........................................... Setting up a trust between the OpsCenter AB host and PureDisk SPA host ................................................................................... 525 526 527 529
Appendix B Appendix C
Attributes of NetBackup data ......................................... 531

About backup data attributes ........................................................ 531
Man pages for CLIs ............................................................ 563
Symantec OpsCenter Glossary ..................................................................... 585
Contents
17
Index ................................................................................................................... 587
18
Contents
Chapter
Getting started using Symantec OpsCenter

This chapter includes the following topics:

About Symantec OpsCenter About whats new with OpsCenter in comparison with NOM and VBR 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 OpsCenter

Symantec OpsCenter is a Web-based software application that helps organizations by providing visibility into their data protection environment. By using Symantec OpsCenter, you can track the effectiveness of data backup and archive operations by generating comprehensive reports. OpsCenter is a convergence of NetBackup Operations Manager (NOM) and Veritas Backup Reporter (VBR) and is available in the following two versions:
20
Getting started using Symantec OpsCenter About Symantec OpsCenter
Symantec OpsCenter
This OpsCenter version does not require any license. Symantec OpsCenter provides single deployment configuration and user interface for monitoring, alerting, and reporting functionality previously. These available in NOM and VBR.
Symantec OpsCenter Analytics
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 support for third-party data protection products. These features were available in VBR.
OpsCenter is a convergence of NetBackup Operations Manager (NOM) and Veritas Backup Reporter (VBR) and is available in the following two versions: Note: OpsCenter supports upgrade from NOM and VBR. For details on OpsCenter upgrade from NOM and VBR and data migration, refer to the Installing Symantec OpsCenter chapter.
About Symantec OpsCenter functions

The unlicensed version of OpsCenter is called Symantec OpsCenter. Symantec OpsCenter can perform the following functions:

Monitors NetBackup setups Manages or administers NetBackup setups Generates alerts depending on conditions that you have defined Provides operational reporting on the following Symantec products:

NetBackup NetBackup PureDisk Backup Exec Enterprise Vault
About Symantec OpsCenter Analytics functions

The licensed version of OpsCenter is called Symantec OpsCenter Analytics. Symantec OpsCenter Analytics can perform the following functions:
Monitors NetBackup setups
21
Manages or administers NetBackup setups See About monitoring and managing NetBackup on page 22. Generates alerts depending on conditions that you have defined See About alerting in OpsCenter on page 22. Creates and customizes views using Java View Builder Provides operational and business-level reporting on the following Symantec and third-party products:

Symantec NetBackup Symantec NetBackup PureDisk Symantec Backup Exec Symantec Enterprise Vault EMC Legato Networker IBM Tivoli Storage Manager
Provides chargeback, custom, and custom SQL reports
Symantec OpsCenter Analytics displays customizable, multi-level views of backup and archive resources and customizable reports for tracking service usage and expenditures. It also contains tools for defining cost metrics and chargeback formulas or handling alerts. A wide range of audiences can benefit from the reporting and management capabilities of Symantec OpsCenter Analytics. 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, and capacity planning teams. The primary objectives of Symantec OpsCenter Analytics are as follows:
Help organizations assess their compliance with business standards by allowing them to accomplish the following:
Help organizationg to establish the service level agreements by reporting on them Report to legal department, auditors, IT managers, and administrators Verify compliance with internal as well as external business-level regulations Identify risks in terms of shortfall of backup resources Assess recovery of clients and applications
22
Assist organizations in effective business planning by enabling them to do the following:
Estimate backup resources required in the future, with the help of backup trend analysis Calculate the cost of data protection management and chargeback to customers and business units Note: You can generate cost reports only for backup data. Cost reports for archive data are not available.
About monitoring and managing NetBackup

OpsCenter can manage and monitor NetBackup master and media servers, clients, and policies. It can manage up to 100 NetBackup master servers distributed across multiple locations. It does not require you to separately log on to each NetBackup master or media server. OpsCenter lets you view the operational status and health of your distributed data protection environment. OpsCenter focuses on how to maintain your backup environment after you complete the NetBackup configuration. You need to use the NetBackup Administration console and command-line interfaces for core NetBackup administrative functions such as configuring media, storage units, and policies.
About alerting in OpsCenter

OpsCenter provides a policy-based alert system, which monitors and notifies you before serious problems happen to your backup environment. You can use predefined alert conditions to create alert policies to monitor typical issues or thresholds within NetBackup or other products. You can send an email or SNMP notification in response to an actual alert, which lets administrators focus on other job responsibilities. They no longer need to be logged in to a terminal to monitor systems continuously. See Managing alert policies on page 390.
About reporting in Symantec OpsCenter Analytics

This section states the benefits that you can get from the Symantec OpsCenter Analytics reports. See About OpsCenter reports on page 457.
23
About compliance reporting

OpsCenter Analytics helps organizations evaluate their compliance with internal and external business standards by providing accurate and customizable reports. By using internal compliance reports, you can measure performance of the system against service level agreement (SLA). The results are then used to optimize data protection management. The reports, such as history or trend analysis, ensure your compliance with SLA. By using these reports, you can track the usage of backup resources and identify the risks involved. For example, you can generate a report that anticipates a shortfall of resources in the future based on the current backup trend. This report is then used to determine the time required to purchase new tape drives, master servers, or media servers. External compliance reports help you follow the policies laid down by various regulatory bodies that are related to federal, healthcare, internal processes, and others. These policies include Sarbanes-Oxley act (SOX) and Health Insurance Portability and Accountability Act (HIPAA). In addition to tracking the backup or archive information, OpsCenter reports ensure recovery of key information assets. The reports can help you ensure that the data recovery meets the recovery-time and recovery-point objectives. OpsCenter can generate reports filtered by views. A view shows a set of enterprise assets (hosts or file systems) organized in logical groups. For example, you can create views to display assets according to their locations in the organization, the line of business they represent, or the applications that are installed. OpsCenter can generate reports according to views created. These reports help you identify locations or departments containing assets with critical data. These reports are then used in resource planning.
About business planning

OpsCenter Analytics is a management tool that helps you optimize your data protection environment with effective business planning. It delivers backup services to organizations, which include reporting on backup and recovery trends and managing data centers. This product supports a wide range of backup and recovery solutions including Symantecs NetBackup and BackupExec. It seamlessly integrates with Symantecs as well as third-party backup products and provides consistent reporting across them. It can collect data from the following target products:

Symantec NetBackup Symantec BackupExec Symantec NetBackup PureDisk Symantec Enterprise Vault
24
Getting started using Symantec OpsCenter About whats new with OpsCenter in comparison with NOM and VBR
IBM Tivoli Storage Manager EMC Legato Networker
OpsCenters ability to forecast backup resource requirements helps data center executives to decide whether to maintain the existing resources or add new capacity. The detailed, drill-down OpsCenter reports help you determine the applications, databases, or business departments that are the heaviest consumers of backup resources. For example, in an environment running 20 instances of Oracle applications, you can generate a report showing resource consumption by department, server, or location. Depending on this information, organizations can provide appropriate resource planning in advance. Symantec OpsCenter Analytics offers you a set of chargeback reports that detail backup services expenditures. By using these reports, you can track the backup and recovery usage and the associated cost. By using the chargeback function, you can define pricing models for backup service delivery and allocate costs to customers based on these models. For example, you can create a formula that determines charges based on kilobytes of backed up data over a period of time. Using this chargeback data, you can then present itemized invoices to internal customers, export chargeback tables to third-party billing systems, or use the data to analyze and justify expenditures. Note: You can generate cost reports only for backup data. Cost reports for archive data are not available.
About reporting on archive data

Archives report category contains a number of reports that are generated based on the archive data collected from Enterprise Vault. You can report on the number of messages that are archived across mailboxes, the size of these messages before and after the archive operation.
About whats new with OpsCenter in comparison with NOM and VBR
OpsCenter offers the following enhancements or new functions, which were not part of NOM or VBR. Table 1-1 lists the new functions introduced in OpsCenter Analytics.
Getting started using Symantec OpsCenter About whats new with OpsCenter in comparison with NOM and VBR
25
Table 1-1
New OpsCenter functions Description

As per the new licensing model,OpsCenter is available in the following two versions: Symantec OpsCenter - This version does not require any license. See About Symantec OpsCenter functions on page 20. Symantec OpsCenter Analytics - This is a licensed version. If you want to use advanced OpsCenter features, add a license key to enable Symantec OpsCenter Analytics. See About Symantec OpsCenter Analytics functions on page 20.
OpsCenter function
New licensing model
With Symantec OpsCenter Analytics, you get the following additional functions, which are not available in the unlicensed version:

Create custom reports Create reports using SQL queries Collect data from third-party products like: IBM Tivoli Storage Manager (TSM)
EMC Legato NetWorker
Generate or configure chargeback reports View historical data in a report Create and customize multi-level views using Java View Builder
New user interface (UI)
OpsCenter UI offers simplified navigation, improved task efficiency, and a new look and feel. In addition, a restructured standard report tree has been added that supports single-click execution. In OpsCenter, five user roles are defined to perform various GUI functions.

New user roles
Security Administrator Administrator Operator Analyst Reporter
See About OpsCenter user roles on page 237.
26
Getting started using Symantec OpsCenter About OpsCenter components
About OpsCenter components

This section describes the following OpsCenter components:

About the OpsCenter Server About the OpsCenter Agent About the OpsCenter Java View Builder
About the OpsCenter Server

OpsCenter Server, the core of the architecture, is a Web application that normalizes backup / archive data collected from various applications. This normalized data is used for reporting on backup related information. OpsCenter server is supported on Windows and Solaris platforms. The OpsCenter server comprises the following components:
OpsCenter database Sybase SA (SQL Anywhere) database management system containing data related to backup /archive service usage and expenditure, cost metrics and chargeback formulas, and alerts. A set of common authentication runtime libraries and processes that enable users to log on once to access multiple products. AT validates identities based on external name spaces like Active Directory or other LDAP servers, UNIX identities based on password files, NIS/NISplus repositories or any identities that can be authenticated through PAM. It also provides a private user repository for service identities. Alert Manager Component that provides policy-based alert management, including notification, custom actions, and SNMP management capabilities. A common Web server (that uses Java Server Pages) and a JRE to serve the OpsCenter console. A common Veritas Licensing Module and API used to add, change, and remove Veritas product license keys. A common component that uses socket passing to reduce the number of ports required to be open across a firewall. Symantec Private Branch Exchange uses a paradigm similar to that of a telephone switchboard in which calls placed to a switchboard are redirected to a known extension. In the PBX exchange, client connections that are sent to the exchanges port are redirected to an extension associated with the OpsCenter Server.
Symantec Product Authentication Service (AT)
Symantec Web Server and Java Runtime Environment (JRE) Veritas Licensing Manager
Symantec Private Branch Exchange
27
Figure 1-1 shows OpsCenter Server architecture. Figure 1-1 OpsCenter Server architecture
OpsCenter Web Server View Builder Console OpsCenter Console Symantec Product Authentication Service (AT)
OpsCenter Server
CORBA Service
Alert Service
Reporting Service
View Builder Service
Licensing Service
Security Service
Database Access Layer
Server Communication Layer
OpsCenter Database (Sybase DBMS)
Symantec Backup Exec Symantec PureDisk (Web Services) OpsCenter Agent Symantec Enterprise Vault
NBSL Communication (CORBA)
IBM TSM CLI EMC Legato Networker
Symantec NetBackup
28
About the OpsCenter database

OpsCenter uses Sybase SQL Anywhere 11 (Sybase 11) database management system as a repository for the backup or archive data, such as backup service usage and expenditure reports, cost metrics, chargeback formulae, and alerts. OpsCenter uses a Sybase SQL Anywhere 11 (Sybase 11) database installation that is separate from the NetBackup database. Except for a very small number of system settings, all information that is in the Web UI is contained in the OpsCenter database, which consists of a single cross-platform database file. The OpsCenter database is completely embedded and requires no additional installation steps. The Sybase database is also self tuning and does not require a database administrator to maintain it. OpsCenter supports upgrade from NOM and VBR.
About the Symantec Product Authentication Service

The OpsCenter Server relies on Symantec Product Authentication Service (AT) for user authentication for connections between, OpsCenter Server, Agent, and Java View Builder. The Symantec Product Authentication Service is referred to as AT. Symantec Product Authentication Service is a shared component and is used for:
Authenticate users to the OpsCenter console based on external authentication systems such as Active Directory, NIS, NIS+, LDAP and even standard unix password. Provide for a secure transport of data between OpsCenter Agent's and the OpsCenter server. Enable trust between OpsCenter and other Symantec products that also use AT.
Note: For more details on AT, refer to the ICS documentation that is shipped with the NetBackup 7.0 documentation set. When the Symantec Product Authentication Service library authenticates a user for OpsCenter, it returns a credential that OpsCenter passes along when cross-linking to other Symantec products such as NetBackup Operations Manager. The Web credential provides a limited form of user authentication so that products do not prompt the user to log on again.
29
About the OpsCenter Agent

The OpsCenter Agent collects data from various Symantec and third-party backup / archiving products. These products can reside on the OpsCenter Agent host or on remote hosts. The OpsCenter Agent relies on the Java Runtime Environment (JRE) to perform its functions. The OpsCenter Agent also requires embedded AT (Symantec Product Authentication Service) to authenticate itself with the OpsCenter Server. Both JRE and AT libraries are installed automatically with the Agent installation. OpsCenter Agent is supported on Windows and Solaris platforms. OpsCenter formats the information collected from the following target products and displays it through the OpsCenter console:
Symantec NetBackup Note: If you want to collect image, error log, or scheduled job data from NetBackup master server of the versions older than 7.0, you need to have OpsCenter Agent installed and configured. Symantec Backup Exec (Windows only) Symantec Enterprise Vault (Windows only) EMC Legato Networker IBM Tivoli Storage Manager
OpsCenter server collects NetBackup data using the NBSL communication in the following scenarios:
If you want to collect Tape Drive Information, Media, Policy and Schedule, Job, or Skipped File data from NetBackup master server of any supported version If you want to collect any data type from NetBackup 7.0 master server
The OpsCenter Agent can reside on the same host as the OpsCenter server, or can be installed on a remote host. All OpsCenter data collectors are configured on every Agent. Configure and run only these data collectors for the target product that you want to monitor / report on. A number of combinations of OpsCenter Agent and Server installations are possible. For example, you can install an Agent on the OpsCenter Server host and configure the NetBackup data collector to collect data from a remote NetBackup master server. Alternatively, you can install an agent on the NetBackup master server host and configure the NetBackup data collector to collect data from the local NetBackup master server.
30
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 run different data collectors. The OpsCenter Agent communicates with the Server, schedules backup / archive data collection data types, and receives commands through the CORBA API. As the OpsCenter Server relies on Symantec Product Authentication Service to authenticate OpsCenter agent - server connections, the Symantec Product Authentication Service client libraries reside on the agent host. The OpsCenter Agent comprises Scheduler, CORBA Client/Server, and data collectors that collect backup data from all available backup application. The Scheduler 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 scheduler

The scheduler performs three basic functions for the OpsCenter Agent:
Checks the data collection schedules of all running data collectors and queues them. Periodically sends a heartbeat message to the OpsCenter Server to ensure the reliability of communications between the agent and the server. Monitors modifications made to the agent configuration using the OpsCenter console, which are stored on the OpsCenter Server.
About the CORBA Client/Server

The OpsCenter Agent implements a CORBA server that listens on a configurable port (default 7806) that allows the OpsCenter console to get the runtime status of the Agent. When you send a request to get the Agent status through the OpsCenter UI, the OpsCenter Server send the request to CORBA Server to receive the requested information. The Agent behaves as a CORBA client when sending data or alerts to the OpsCenter Server.
31
About data collectors

The data collectors convert the data specific to backup or archive products into a format that can be used by the OpsCenter Server. Each data collector must conform 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 log configurations and data collection event definitions, which are shared by all data collectors) and product-specific values. You need to configure a data collector on the OpsCenter Agent host that collects data from a backup or archive product host.
About Agent configuration and logging

Agent configuration settings are stored in the OpsCenter database. The OpsCenter Agent also caches the latest version of the configuration settings in the agent.conf file. The agent compares the local agent.conf file with the one stored in the database 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 agent is restarted. Note: You should not modify the agent.conf file. You should change the agent configuration settings using the OpsCenter Agent Configuration UI. The changes that you have made to the agent configuration settings using the OpsCenter UI or console are reflected after the next heartbeat. A heartbeat is a request that the OpsCenter Agent sends to the OpsCenter Server to check for any new changes in the configuration settings. By default, a heartbeat is sent every minute. Logging for the agent core and individual data collector is administered in the same fashion but written to different log files.
About the OpsCenter Java View Builder

The OpsCenter Java View Builder is an application in which an administrator creates, modifies, and manages access to the OpsCenter views that users see in the console. Note: To create or customize views using Java View Builder, you need to install the licensed version of OpsCenter called Symantec OpsCenter Analytics.
32
Getting started using Symantec OpsCenter About using the OpsCenter console
The Java View Builder relies on the AT client libraries which is installed automatically to communicate properly with the OpsCenter Server. To use the Java View Builder, you need to provide login credentials as you do while logging onto the OpsCenter console. See Logging on to the Symantec OpsCenter console on page 41. When you run the Java View Builder exe, it is directly connected to the OpsCenter Server. The View Builder fetches the existing object view definitions from OpsCenter database and displays them in the OpsCenter console. Actions performed using the View Builder console are then stored in the OpsCenter database.
About using the OpsCenter console

The following sections cover the basics of how to access and use OpsCenter. It includes how to log on and log off and how the console works. For information on how to understand and use the various OpsCenter views and related tasks, see the OpsCenter online Help . Context-sensitive help is available for all console views, task dialog boxes, and wizard task screens. To access the online Help , use the help option in most dialog boxes and wizard screens. 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 working knowledge of NetBackup and its concepts and components. Portions of the online Help may refer the user to other NetBackup documentation for descriptions of NetBackup fields and components. The following NetBackup documents are referenced in the OpsCenter online Help :

NetBackup Administration Console Help NetBackup Administrators Guide for Windows, Volume I NetBackup Administrators Guide for UNIX and Linux, Volume I NetBackup Troubleshooting Guide for UNIX, Windows, and Linux
About starting the OpsCenter console

The OpsCenter server is the focal point for centralized management of the NetBackup servers (release 6.0 MP5 and greater) in your backup environment. When you install Symantec OpsCenter, you select the computer that serves as the OpsCenter server. When you start the OpsCenter console to manage and
Getting started using Symantec OpsCenter About starting the OpsCenter console
33
monitor your NetBackup environment, you open a connection to the OpsCenter Web GUI.
About Web browser considerations

Consider the following recommendations and requirements for the Web browser to be able to access the OpsCenter console. Warning: Always refer to the OpsCenter sections of the NetBackup release notes for any last-minute changes to the information that is presented in this document. The release notes for your release of OpsCenter also include any restrictions or limits for OpsCenter. The following requirements and recommendations should be considered for the Web browser:
The OpsCenter console uses pop-up menus. If you use pop-up blockers with your Web browser, some of these menus may not display properly. You must disable pop-up blocking or add the OpsCenter Web address to the list of acceptable 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) before you 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-class systems, an enhanced security configuration can cause some pages to not display properly in Internet Explorer. If you encounter this issue, add the OpsCenter URL to the Trusted-sites list and lower the security setting. To resolve this issue, open Internet Explorer and select Tools > Internet Options > Security to configure the Trusted-sites list and lower the security level. If you use Internet Explorer 8.0 to access the OpsCenter console, security certificate warnings appear when you access a pop-up menu. Select Continue to this website (not recommended) to open the pop-up menu. Once you select this option, the security certificate warnings do not appear on the pop-up menus. The web browser cache must be cleared.
34
About Web browsers supported by OpsCenter

The OpsCenter user interface (the OpsCenter console) is supported with the following Web browsers. Table 1-2 lists the Web browsers that OpsCenter supports. Table 1-2 Web browser
Microsoft Internet Explorer
Web browsers supported by OpsCenter Supported Versions

6.x, 7.x, 8.0
Notes
IE 6.0 may display a security alert dialog box when you access OpsCenter. See Disabling the security alert dialog box in IE 6.0 on page 35. IE 7.0 and later versions may display a security certificate warning page when you access OpsCenter. See Disabling security certificate warnings permanently from browsers on page 37.
Mozilla Firefox
3.0 and higher versions
Mozilla Firefox may display an Untrusted Connection page when you access OpsCenter. See Disabling the Untrusted Connection page in Mozilla Firefox on page 36.
About accessing the OpsCenter console

Before accessing the OpsCenter console, review the following section thoroughly. See About Web browser considerations on page 33. On a system that has a network connection to the OpsCenter server, start the system'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 can
also be an IP address.
35
Note: By default, OpsCenter tries to run on port 80 (HTTP). If port 80 is not available, OpsCenter can use a different port. To know the HTTP and HTTPS port that OpsCenter uses, run the configurePorts utility. Run INSTALL_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 use http://<host.domain>:8181/opscenter. You can also use the URL that is presented at the end of the OpsCenter server installation to access OpsCenter.
Disabling the security alert dialog box in IE 6.0

When 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 this dialog box permanently. To disable the security alert dialog box permanently
1 2
Click Tools > Internet Options. In the Internet Options dialog box, click the Advanced tab.
36
3 4
Under Security, uncheck Warn about Invalid site certificates option. Restart your browser for the changes to take effect.
Disabling the Untrusted Connection page in Mozilla Firefox

When you access OpsCenter in Mozilla Firefox, you may see the Untrusted Connection 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. 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 Mozilla Firefox start page, or click Add Exception (when you expand the I Understand the Risks section) and permanently disable the page. To disable the Untrusted Connection page permanently
1 2 3
On the Untrusted Connection page, expand I Understand the Risks section and click Add Exception. In the Add Security Exception dialog box, click Get Certificate. Ensure that the Permanently store this exception option is checked. This option is checked by default.
37
4 5
Click Confirm Security Exception. Restart your browser for the changes to take effect.
Disabling security certificate warnings permanently from browsers

When you log on to OpsCenter console, you may see security certificate warnings on Mozilla Firefox and Internet Explorer browsers. This is because when you access OpsCenter using http://<host.domain>/opscenter, you are automatically redirected to HTTPS (hypertext transfer protocol Secure) which is a secure protocol and requires a certificate. In case you do not want to use HTTPS and disable the security certificate warnings while accessing OpsCenter console, you can disable the automatic redirection to HTTPS. However note that using HTTPS provides encryption and secure identification of the server.
38
To disable security warnings and HTTPS redirection
Open the web.xml configuration file in a text editor from the following locations:
For Windows: For UNIX: INSTALL_PATH\OpsCenter\WebServer\conf\web.xml /opt/SYMCOpsCenterWebServer/conf/web.xml
Note: Before you proceed with rest of the steps, it is recommended that you take a backup of the web.xml file.
In the web.xml file, locate the security constraint string (located towards the end 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>
39
Comment this portion from the web.xml file by adding  in the end. You can also add your comments inside. For example:

Stop the OpsCenter Web GUI service on Windows. Select Control Panel > Administrative Tools > Services and restart (stop and then start) the Symantec OpsCenter Web Server Service.
Restart the OpsCenter Web GUI service on UNIX. Enter the following command:
Stop service Start service /opt/SYMCOpsCenterGUI/bin/stopGUI /opt/SYMCOpsCenterGUI/bin/startGUI
About possible OpsCenter console access issues

You may see the following issues when you access the console. Table 1-3 describes possible OpsCenter console access issues and their solution.
40
Table 1-3 Issue

You cannot connect to the Web GUI. Your Web browser displays the following messages: "page cannot be displayed" or "connection was refused."
OpsCenter console access issues, causes, and solution Solution

Verify that the Symantec OpsCenter Web server Service is running. Verify that a Web browser on the OpsCenter server can connect to the OpsCenter console by using the following address: http://localhost:<HTTP port number>/opscenter
Cause
The OpsCenter Web 1 GUI (the OpsCenter console) is not running 2 or is inaccessible on the network.
Note: To know the HTTP and HTTPS port that OpsCenter

uses, run the configurePorts utility. Run INSTALL_PATH\OpsCenter\gui\bin\goodies\configurePorts.bat -status on Windows hosts or /opt/SYMCOpsCenterWebGUI/bin/goodies/configurePorts.sh -status on UNIX hosts.
The OpsCenter Web GUI The OpsCenter console Use the following steps on Windows: is running, but the application is not 1 Locate the opscenter.war file in the following directory OpsCenter console is not loaded. to verify that the OpsCenter application is installed: available. Your Web INSTALL_PATH\OpsCenter\WebServer\webapps browser displays an "HTTP STATUS 404" 2 Verify that all the OpsCenter server services are running. error. 3 Start all the OpsCenter server services by using the following command: INSTALL_PATH\OpsCenter\server\bin\opsadmin.bat start
Use the following steps on UNIX: 1

Locate the opscenter.war file in the following directory to verify that the OpsCenter application is installed: /opt/SYMCOpsCenterGUI
Verify that all OpsCenter server processes are running by using /opt/SYMCOpsCenterServer/bin/opsadmin monitor command. Start all the OpsCenter server processes by using the following commands: /opt/SYMCOpsCenterServer/bin/opsadmin.sh start
41
Logging on to the Symantec OpsCenter console

You must supply logon credentials on the OpsCenter login screen. To log on to Symantec OpsCenter console
Enter a user name and password, and select a domain from the Domain drop-down list. For administrator initial logon, the user name is admin and the password is password or any custom password that you chose during the installation. Select OpsCenterUsers(vx) from the Domain drop-down list. The domains that appear in the Domain drop-down list include the OpsCenterUsers(vx) domain, domains that are migrated if you upgrade to OpsCenter from NOM or VBR, and domains of the users that are added to the OpsCenter console. After the initial log on, you should change the user name and password. To change existing passwords, use Settings > User Preferences > My Profile view in the OpsCenter console. See Changing your password on page 225.
Click Log On. Initially, a monitoring overview of the NetBackup master servers appears. When you log off from the console, OpsCenter saves your settings and preferences and uses these settings when you restart the console again. Note: The first time you log on, OpsCenter uses the default language of the Web browser. If OpsCenter does not support this language, it uses English. After initial logon, you can specify a default language or locale from Settings > User Preferences > General. If you do not set a default, OpsCenter uses the Web browser language (or English). See Setting user preferences on page 223.
About possible OpsCenter console logon issues

Table 1-4 describes the issues you may find when you log on to the console and their solution.
42
Table 1-4 Issue
OpsCenter console logon issues Cause

The Symantec Product Authentication Service cannot validate the user name and password for the selected domain.
Solution
Enter a valid user name, password, and domain. Ensure that the Symantec Product Authentication Service is started and running properly. You can start authentication service by running 'net start vrtsat' on Windows and '/opt/VRTSat/bin/vxatd' on UNIX.
You have a user authentication error. The login screen displays the message "User authentication failed. Please enter valid user name and password. If problem persists contact your system administrator ." The entered user name is not a registered OpsCenter user. The login screen displays the message "This user is not authorized to use OpsCenter. Please contact the OpsCenter Administrator for adding this user."
The user name and Log on as the OpsCenter admin user domain are valid, but and add the user to the list of the user was not OpsCenter users. added to the list of users for OpsCenter.
You cannot connect to the The OpsCenter server OpsCenter server. The login is not running. screen displays the message "Error occurred while connecting to the OpsCenter Server. Please ensure that the server is running."
Start the Symantec OpsCenter Server Service and verify that it is running properly. Check your network configuration. Verify if hosts file has the correct IP address to host name mapping. The hosts file is located in C:\WINDOWS\system32\drivers\etc directory on Windows. Enter a valid user name and password.
Either the user name or Username and/or password or both have not password has not been entered. The login been specified. screen displays the message "Please enter valid user name and password. " Authentication service is Authentication down "Error occurred while service is down connecting to the Symantec Product Authentication Service (AT). Please ensure that the AT service is running."
Verify that Symantec Product Authentication Service is running. You can start authentication service by running net start vrtsat on Windows and /opt/VRTSat/bin/vxatd on UNIX.
43
Logging out of the OpsCenter console

When you log out from the console, OpsCenter saves most of the settings and changes 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 interval

When left at its default value, users are automatically logged out of the OpsCenter console when a session is left inactive for 30 minutes. However, the session timeout interval can be reconfigured. To configure the session timeout interval
Open the web.xml configuration file in a text editor from the following locations:
For Windows: For UNIX: INSTALL_PATH\OpsCenter\WebServer\conf\web.xml /opt/SYMCOpsCenterWebServer/conf/web.xml
In the web.xml file, locate the session-timeout parameter:

<session-config> <session-timeout>30</session-timeout> </session-config>
Change the session timeout parameter value to the desired length by changing the number encapsulated by the XML tags for session-timeout (in the example above, change "30" to the desired value). This value is set in minutes.
44
Stop the OpsCenter services. Enter the following command:

Windows UNIX INSTALL_PATH\OpsCenter\server\bin\opsadmin.bat stop /opt/SYMCOpsCenterServer/bin/opsadmin.sh stop
Restart the OpsCenter services. Enter the following command:

Windows UNIX INSTALL_PATH\OpsCenter\server\bin\opsadmin.bat start /opt/SYMCOpsCenterServer/bin/opsadmin.sh start
About possible OpsCenter console issues

Table 1-5 describes the issues you may find when you use the console. Table 1-5 Issue
Your OpsCenter console session times out. The login screen appears when you try to change views or refresh the current view.
Issues when you use OpsCenter console Cause

After 30 minutes of inactivity, the OpsCenter user automatically logs out of the console. Any attempt to use OpsCenter, displays the OpsCenter login screen.
Solution
Log on again. After successful logon, you then return to the OpsCenter view that you last visited. You can also configure the session timeout interval. See Configuring the OpsCenter session timeout interval on page 43.
An internal error occurs in the OpsCenter console. An exception error message appears in the OpsCenter console. You receive the message "An unknown error has occurred. Click here to log on and retry. "
This error results from an internal issue in the OpsCenter console application.
Click the link in the message and try to login again.
You receive the message Active scripting is disabled "Active scripting is required in the Web browser. to use this application. Enable active scripting in the browser."
Enable active scripting in the Web browser. You must enable it to use OpsCenter.
45
Table 1-5 Issue
Issues when you use OpsCenter console (continued) Cause Solution
An unresponsive script error is displayed when on Mozilla Firefox
46
Table 1-5 Issue

To tell Firefox to let the script run longer: In the Location bar, type about:config and press Enter. o The about:config "This might void your warranty!" warning page may appear. Click I'll be careful, I promise!, to continue to the about:config page. In the about:config page, search for the preference dom.max_script_run_time, and double-click on it. In the Enter integer value prompt, type 0.

Press OK.
With scripts now allowed to run for longer times, you may no longer receive the prompt. If you still receive the prompt (or if you want to see it again), you should set that preference back to the default value. In the Location bar, type about:config and press Enter. o The about:config "This might void your warranty!" warning page may appear. Click I'll be careful, I promise!, to continue to the about:config page. In the about:config page, search for the preference dom.max_script_run_time.
Getting started using Symantec OpsCenter About OpsCenter console components
47
Table 1-5 Issue
Right-click on it and choose Reset.
About OpsCenter console components

This section provides information on the panes and navigation features available in 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 out and log on again these settings are used. Figure 1-2 shows the OpsCenter console components. Figure 1-2
Tabs and subtabs
OpsCenter console components

Content pane List View Title bar links
Table Settings icon View Pane Task Pane (whole left pane) Minimize icons Symantec ThreatCon pane Quick links
Table page controls
Maximize icon
Details pane
Minimize icon
48
Table 1-6 lists the topics that describe the main elements of the console in greater detail. Table 1-6 Topic
About using the links on the title bar
Topics covered in this section Description

Describes how to use the links (for example, Logout and Help) available from the title bar Provides an overview about the tabs and subtabs available in the console
About using tabs and subtabs
About refreshing the OpsCenter console Describes how to control the frequency that the OpsCenter console refreshes to reflect changes in your backup environment Using the Task pane About the View pane Provides an overview about the Task pane. Provides an overview about the View pane.
Using the quick links in the Task pane Provides an overview about quick links in the task panes Using the content pane Describes how to use the main data display pane that OpsCenter uses Describes how to use the status bar at the bottom of the OpsCenter console Describes how to use the visual keys that OpsCenter uses to help you understand displayed information Describes how to use tables, select rows, and use filters.
About the OpsCenter status bar
About visual keys in the console
About using tables
About using the links on the title bar

On the title bar of the OpsCenter console, the Logged in as value shows the user name that is logged on to the OpsCenter server. To adjust the screen space that is used by the tabs and subtabs, click the Customize Tabs drop-down list. You can select the following options:
49
Small
Only the selected tab and subtab are shown in a single row. Clicking the arrow next to the selected tab displays rest of the tabs in a drop-down list. Similarly clicking the arrow next to the selected subtab displays rest of the subtabs in a drop-down list. The tabs and subtabs appear in two separate rows. The tabs do not have any icons above them. The tabs and subtabs appear in two separate rows. The tabs have icons placed above them.
Medium
Large
Use the links available in the title bar at the top of the console for the following tasks:

To know OpsCenter product version and copyright information (click About). Access Symantec OpsCenter help (click Help). Context-sensitive help for all views, wizards, and dialog boxes is available using this link. More information about online Help is available. See About OpsCenter documentation on page 64. Disconnect from the OpsCenter server to end your session (click Logout). See Logging out of the OpsCenter console on page 43.
About using tabs and subtabs

Table 1-7 describes the main tabs that provide access to the major areas of the OpsCenter console. Table 1-7 Tab
Monitor
Tabs and subtabs in the OpsCenter console Description

Monitor the status of NetBackup jobs, services, policies, media, devices, hosts, and display and respond to any OpsCenter alerts. Manage alert policies, NetBackup job policies, storage units, devices. Using this tab you can also restore data. View standard OpsCenter reports, create and run custom reports, and schedule reports.
Manage
Reports
Note: You can use custom report functionality only with a licensed
OpsCenter version (OpsCenter Analytics).
50
Table 1-7 Tab

Settings
Tabs and subtabs in the OpsCenter console (continued) Description

Customize the OpsCenter server, add OpsCenter users, define user preferences, add, and configure views, set up email and SNMP recipients, view chargeback settings, add master server etc.
Under each main tab is a series of subtabs. The contents of these subtabs vary depending on the current view and represent the views accessible from each main tab. 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 View pane. More information about View pane is available. See About the View pane on page 51.
About refreshing the OpsCenter console

As you use Symantec OpsCenter, the status of your backup environment is likely to change. Devices go online and offline, OpsCenter generates alerts, media usage fluctuates, and so on. You can control when the information in the console refreshes to reflect the changes in your backup environment. You can change the refresh setting from Settings > User Preferences > General view in the OpsCenter console. See Setting user preferences on page 223.
Using the Task pane

In many views in the console, a Task pane is available. The Task pane is located on the left side of the console and contains the View pane, Symantec ThreatCon pane, 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 called Collapse 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 to resize 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.
51
About the View pane

The 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. ALL MASTER SERVERS is the default view in the View pane. Using OpsCenter views, you can view NetBackup information for your whole management domain (in the case of ALL MASTER SERVERS view), a specific view type, 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 master servers in a particular region like Europe. You can also create client or policy views. More information about how to create views from Settings > Views is available. See About OpsCenter views on page 307. See the online Symantec OpsCenter Java View Builder Help to know how you can create 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 server that is Not Connected. Similarly a disabled master server is shown as a gray colored icon. See About visual keys in the console on page 57. Lets you access and change the views that you monitor or manage. As you navigate within the OpsCenter console, your view selection applies for any subsequent screens until you select a different view. Using the View pane is one of the methods you can use to determine the scope of information that you view.
Figure 1-3 shows a sample View pane in which ALL MASTER SERVERS view is selected.
52
Figure 1-3
View pane description
About selecting views from the View pane

From the View pane, you can select a view and a node that contains a group of master servers and also specific objects. For example, you can select the default view ALLMASTERSERVERS. When you select a view like ALLMASTERSERVERS or a node that contains a group of master servers, all the master servers that are currently in the view or node are automatically selected. In addition, the master servers 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 ALL MASTER SERVERS. To select a specific master server, first deselect the view or node 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 view and then deselecting the specific master server. Consider a scenario where there are two objects server A and server B in a particular view like ALL MASTER SERVERS. In case, you have selected the ALL MASTER SERVERS view and then specifically deselected server B , and in addition if you have selected a node that also contains server B, server Bis not considered 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 a master server from a view, which is also part of another selected view, the deselection or exclusion is given a higher priority because of which the master server is not considered. For this reason, it is recommended that you do not repeat a master server across groups.
53
About the Symantec ThreatCon pane

The Symantec ThreatCon pane shows the current ThreatCon level in the OpsCenter console. This level is same as the ThreatCon level which is shown on the following Web site: http://www.symantec.com/security_response/threatcon/index.jsp The Symantec ThreatCon pane is available in the OpsCenter console on the left-hand side. Figure 1-4 shows the Symantec ThreatCon pane in the OpsCenter console. Figure 1-4 Symantec ThreatCon pane in the OpsCenter console
Clicking the More Info link in the Symantec ThreatCon pane shows details about the ThreatCon level. OpsCenter periodically polls the ThreatCon Web service and updates the data which is shown in the Symantec ThreatCon pane. You can also configure this polling interval. Symantec ThreatCon feature is enabled by default. You can also disable or enable the Symantec ThreatCon feature. See Configuring Symantec ThreatCon feature in OpsCenter on page 229.
Using the quick links in the Task pane

In 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-8 shows the quick links available in OpsCenter and where they take you when you click these links. Table 1-8 Quick Link
Oracle Cloning Alert Policies
Quick links and where they point Destination

Manage > Oracle Cloning Manage > Alert Policies
54
Table 1-8 Quick Link
Quick links and where they point (continued) Destination

Settings > Configuration > NetBackup Settings > Views Settings > Users > Users
NetBackup Data Collection Views Users
To minimize the quick links
Click the minimize icon (down arrow) located on top of the quick links. Only the 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 minimize or maximize settings are applicable only for the current session.
Using the content pane

When you initially log on to Symantec OpsCenter, the content pane displays a summary 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 selections in 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 called Collapse Task Panel. Click the icon again to show all panes. Note: The Collapse Task Panel icon is not available in the Monitor > Overview page. Or You can also drag the line separating the View pane and the Content pane to resize 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.
55
Using the List, Summary, Hierarchical, and Details views

Most of the OpsCenter monitor and manage views present information in three main viewing modes: List View, Summary View, and Hierarchical View. You can view 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 switch between these views. Note: Not all viewing modes are available for all Monitor and Manage views. The drop-down list is available in the applicable views.
List View
Drop-down list
The Summary View presents information in a graphical format (pie charts). The List 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 a summary of all NetBackup jobs (for a master server) in the form of pie charts by using Summary View on the Monitor > Jobs page. You can view details about all NetBackup jobs and also relationships between jobs (for a master server) in a tabular format using Hierarchical View on the Monitor > Jobs page. In addition to the above views, a Details view is also available. A details view is available on some of the Monitor, Manage, and Settings pages. The Details view is shown in the following figure.
56
Maximize icon
Minimize icon
Tabs on the Details View
Details View
Contents of all the columns for the specific job ID is displayed in the Details View.
The Details view presents detailed information about an entity and shows contents of 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) shows detailed information about a specific job ID. Information in the Details view can be 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 of the Content pane to minimize the Details View. Click the icon (up arrow) between the Details View and the upper part of the Content pane to maximize the Details View. Or You can also drag the line separating the upper part of the Content pane and Details view to resize the Details View. The minimize or maximize settings are applicable only for the current session.
57
About the OpsCenter status bar

The status bar at the bottom of the OpsCenter console shows a Page generated value. The Page generated value shows the date and time of the OpsCenter server you are logged on to (adjusted to match your time zone). This value updates when the view changes or refreshes. More information on how to specify your time zone is available. See Setting user preferences on page 223.
About visual keys in the console

To help you understand the information it presents, Symantec OpsCenter uses several visual keys. These keys include color, status icons, and tool tips.
About color coding

This topic helps you to identify and understand the colors that are used along with status icons. The following colors are used along with status icons:
Red indicates a critical condition that may cause the system to be unable to perform an important function. Investigate critical conditions immediately. A server icon with a red dashed-circle means that the connection to the managed server is lost (Not Connected). A reattempt to connect happens after 10 minutes. Green indicates a normal condition, result, or operation. Blue-gray and gray often indicate enabled and disabled, or assigned and unassigned conditions respectively.
About status icons

Status 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 let you quickly determine the status of a particular area in your NetBackup environment. For example, the Monitor > Jobs view contains green icons for running jobs. Unique icons also appear in the drive details view for shared drives (the NetBackup SSO option). These icons represent the shared drives that are up on all servers
58
that share the drive. Icons also appear for shared drives where the drive status is mixed (up on some servers and down on other servers that share the drive). Table 1-9 lists the icons that are used for managed NetBackup master servers in the View pane. Table 1-9 Icon Icons used for managed master servers Description
A normal server icon means that the managed server is Connected. A server icon with a red dashed-circle means that a connection to the managed server is lost (Not Connected). A reattempt to connect happens after 10 minutes. A managed server icon with a line through it denotes that the server is Partially Connected. For a partially connected master server, OpsCenter tries to reconnect to NBSL in every 10 minutes to collect data for the data types for which Collection Status is Failed. A gray colored server icon means that data collection for the managed server was disabled by the user.
About tool tips

Tool tips provide brief descriptions of the tool and the status icons that appear in OpsCenter views. A tool tip appears when you place the mouse over an icon.
About using tables

OpsCenter collects information about aspects of your NetBackup environment and presents much of this information in tables. This section describes how to change the tables to display the information you want to see. The following is a sample table showing task icons. Figure 1-5 shows the task options for tables.
59
Figure 1-5
Create, Edit, and Delete filter icons
Sample screen with task options for tables

Table Settings icon
Table page controls
Customizing tables for your needs

You can customize the tables in the following manner. You can perform the following operations to a table:
Add or remove columns See Specifying which columns appear in a table on page 60.
Rearrange the order of the columns for your See Moving a column on page 60. individual requirements Choose the number of rows and columns to See Choosing the number of rows that display appear per page of a table on page 60. Sort columns in ascending or descending order Change the widths of columns See Sorting the contents of a table column on page 61. See Changing the width of a column on page 61. See Accessing multiple pages of data in tables on page 61. See Selecting rows in tables on page 61.
Pagination
Select rows in tables
60
The table refreshes after the operation and shows the changes you made. For these operations, OpsCenter saves and reloads your customized settings when you log on to the OpsCenter server again. Each user can have different customized table 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 2
Click the Table Settings icon at the top-right corner of the table. Initially, some OpsCenter tables do not show all available columns. To view any of these columns, you may first have to remove one or more columns from the table and then add the missing columns. Remove columns you do not want to appear by selecting the column in Selected Columns. Then click Remove. Add any columns that currently do not appear by selecting the column in the Available Columns list. Then click Add. Added columns appear as the last column in the table.
Moving a column
Use the following procedure to move columns in a table. To move a column
1 2 3
Click the Table Settings icon at the top of the table. Select the name of the column in Selected Columns. 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 page for a table. To choose the number of rows that appear per page for a table
1 2 3
Click the Table Settings icon at the top of the table. Select a number from the Rows Per Page drop-down list . Select Apply To All Tables if you want the Rows Per Page setting to apply to all tables in OpsCenter (includes reports).
61
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 by default. 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 2
Select the edge of the column heading and hold down the left mouse button. 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 tables display 10 rows at one time by default. You can also change the number of rows to be displayed in the table from the Table Settings icon. When you have more data to display than can fit in a table, the table contains multiple pages. Use the table page controls (located below the table) to help you navigate 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 the selected row.
62
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 again to deselect all selected rows.
Using filters to customize your views

Many tables in OpsCenter let you display a subset of the information available by creating 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 a filter. To create a custom filter
1 2 3
Select the Create filter icon. Type a name for the filter in the Name field. For Column, select the column name that you want to filter on from the drop-down list. For Operator, select an operator. Use != if you do not want to match a specific value. For Value, enter or select a value. If you select Start Time or End Time for Column, a calendar icon appears for Value. Click the calendar icon to choose a date and time and then click OK.
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 not what you want, click Remove to remove the clause from the query.
To continue building the filter, select another column. Repeat 3 and 4.
Click OK when you finish building the filter. Your new filter is available in the 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 view remains in effect until you change it by selecting another filter.
Getting started using Symantec OpsCenter About quickly performing common tasks in OpsCenter
63
To edit a custom filter
From the drop-down list, select a custom filter. Note: You cannot modify the ready-to-use OpsCenter filters. You can only modify custom filters.
2 3
Click the Edit filter icon. See To create a custom filter on page 62. This lists the instructions for using the dialog to edit a filter. Make your changes and click OK.
To remove a custom filter
From the drop-down list, select a custom filter. Note: You cannot delete the ready-to-use or built-in filters.
2 3
Click the Delete filter icon. Click OK to remove the filter.
About quickly performing common tasks in OpsCenter

Table 1-10 lists the common tasks and the corresponding links to the documentation. Table 1-10 To learn how to
Add master servers in the OpsCenter console Add authorized OpsCenter users Set up user preferences Configure the SMTP server and OpsCenter alert retention settings Set up recipients for alert and report notification
Quick links to the OpsCenter documentation Go to this topic

See Adding a master server on page 278.
See Managing users on page 235. See Setting user preferences on page 223. See Configuring SMTP server on page 228.
See Managing recipients on page 243.
64
Getting started using Symantec OpsCenter About using Web browser bookmarks
Table 1-10 To learn how to
Quick links to the OpsCenter documentation (continued) Go to this topic

See Creating views on page 312.
Configuring OpsCenter views
Create OpsCenter alert policies for your See Creating (or changing) an alert policy site on page 394. View and respond to OpsCenter alerts See Managing an alert policy on page 407. View the details for a NetBackup job View NetBackup job policies Control NetBackup job policies Export NetBackup job log files Control NetBackup services See Monitoring NetBackup jobs on page 331. See Monitoring NetBackup policies on page 350. See Managing a job policy on page 356. See Exporting NetBackup job logs on page 339. See Monitoring NetBackup services on page 348.
Understand and use OpsCenter reports See About OpsCenter reports on page 457. Create custom reports for your needs See Creating a custom report on page 468.
Note: This feature is available with a

licensed version (Symantec OpsCenter Analytics). Schedule when you want a report to run See Managing report schedules on page 479.
About using Web browser bookmarks

By using your Web browser, you can add a bookmark for any view in the OpsCenter console and return to it as needed. If you log out of the OpsCenter console, you can use the bookmark to return to the same view after you log onto the console.
About OpsCenter documentation

The Symantec OpsCenter Administrator's Guide (NetBackup_AdminGuide_OpsCenter.pdf) provides information on how to use OpsCenter. It includes information about how to monitor and manage NetBackup, collect data from Symantec as well as third-party products, generate alerts, and create various reports. It also provides details on the difference between Symantec OpsCenter (the unlicensed version of the product) and Symantec OpsCenter Analytics (the licensed version of the product).
Getting started using Symantec OpsCenter About OpsCenter documentation
65
Symantec OpsCenter Administrator's Guide is available on the product CD. Note: For the latest support information, for example, supported products or operating systems, see the Symantec NetBackup Hardware and Software Compatibility List, which is regularly updated on the Symantec Support Web site. Access the following URL: http://www.symantec.com/business/support/index.jsp You can find the OpsCenter PDF (Portable Document Format) document on the following default locations on the OpsCenter server host:
Windows C:\Program Files\Symantec\OpsCenter\Server\Docs /opt/SYMCOpsCenterServer/docs
Solaris
In addition to the PDF document, OpsCenter is also shipped with the following online Help documents:
OpsCenter Context-sensitive This WebGUI Help contains all information about the Help OpsCenter GUI. It provides context-sensitive help pages for all GUI screens. Java View Builder Context-sensitive Help This Java Help contains information about all information about Java View Builder dialog boxes and the procedures you carry out. You can access the context-sensitive Help by clicking the Help button available on a dialog box in the Java View Builder console.
NetBackup Status Codes Help This context-sensitive Help provides troubleshooting information about NetBackup status codes. In the OpsCenter console, click Monitor > Jobs and click a status code link in the jobs table to view its details. Table Settings Help This HTML help provides information on how you can change the settings of a table in the OpsCenter console. To access this Help, click the Help button on the Table Settings pop-up screen. OpsCenter is shipped with man pages / manual pages for various utilities that you can run from command prompt. Man pages are used to find reference and usage information about product-specific commands on UNIX computers.
Man Pages for Utilities
66
Getting started using Symantec OpsCenter About OpsCenter documentation
Chapter
Installing Symantec OpsCenter


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 installation

This section provides information on what all you need to take care of, before you proceed to OpsCenter installation or upgrade.
About the software components that OpsCenter uses

Along with OpsCenter specific components, OpsCenter uses some common Symantec components that are shared.
About components shared with other Symantec applications

The following components are used by OpsCenter and are also shared with other Symantec applications.
68
Installing Symantec OpsCenter Planning an OpsCenter installation
Symantec Private Branch Exchange (PBX) Symantec Private Branch Exchange lets Symantec applications share a common TCP/IP port, which reduces the number of ports in the firewalls that must be open to operate products. PBX also integrates with the Symantec Product Authentication Service to allow for authenticated connections in addition to non-authenticated connections. Since it is an independent component, the PBX port number can be changed using PBX configuration files. Changing the PBX port number on the server where OpsCenter is installed may cause OpsCenter to fail. Symantec Product Authentication Service (AT) This service is primarily used for user logon authentication and is required for secure communication between OpsCenter Agent, OpsCenter GUI, View Builder, and the OpsCenter server software. AT is also used for secure communication between NetBackup master servers and the OpsCenter server software. The OpsCenter server needs to be a legitimate server that is allowed to talk to NBU, wherein, the OpsCenter server must appear in the server list. Note that there is no requirement for Symantec Product Authorization Service to 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 on authentication services. See Security and Encryption Guide in the NetBackup DVD for information about NBAC. JRE (Java Runtime Environment ) The Symantec OpsCenter Web server and the OpsCenter application require this component.
Symantec OpsCenter specific components

The following components are used only by OpsCenter and are not shared with other Symantec applications.
Symantec Java Web server The OpsCenter Web GUI and the reporting service runs under Symantec Java Web server . Veritas Unified Logging (VxUL) This logging component is installed with OpsCenter Server and Agent and is used to configure and view OpsCenter logs. See the NetBackup Troubleshooting Guide for more information about VxUL logs.
69
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 model

OpsCenter requires no license. If you wish to enable additional functionality, add a license key to enable OpsCenter Analytics. The licensed version of OpsCenter is called Symantec OpsCenter Analytics. The unlicensed version of OpsCenter is called Symantec OpsCenter. This is visible from the title bar and logon page of the OpsCenter console. The Symantec OpsCenter Analytics licenses are charged depending on the following considerations:
The number of backup clients that OpsCenter reports on (for backup environments) The number of mailboxes that OpsCenter reports on (for Symantec Enterprise Vault environments)
Note: If you want to enable custom reporting on Enterprise Vault data, you must add the appropriate license key. For example: You have an OpsCenter - NetBackup set up with 100 backup clients and OpsCenter - Enterprise Vault set up with 500 mailboxes to report on. You need to purchase a license that enables you to report on 100 backup clients and 500 mailboxes. While installing OpsCenter, if you install Symantec Enterprise Vault enabled licensing key, the license option called Archive Mailbox is added. The license option 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 shown in the figure.
70
These entries show that the license to back up 1000 clients and the license to collect archive data of 1000 mailboxes from Enterprise Vault is installed. These entries show that the actual usage of Archive mailbox license option is 0 while the licensed value is 1000.
It may be possible that the number of mailboxes that you have configured exceeds the license limit or the number of backup clients that you have exceeds the license limit. To know this compare the Value and the Usage column from the Settings > Configuration > License page in the OpsCenter console.
About the license keys

OpsCenter has two types of license keys:
Demo key This is valid for 60 days from the day the key is generated. The purpose of the demo key is to enable you to try the product before you purchase it. A permanent key does not have an expiry date.
Permanent key
You can access the licensed features with both demo and permanent keys. With a licensed version, you can do advanced reporting, create custom reports, collect data from third-party products like IBM Tivoli Storage Manager (TSM) and EMC Legato NetWorker etc.
71
See About the OpsCenter Analytics licensed features on page 72. You can also add, delete, or view license keys after installation from the OpsCenter console. See Managing licenses on page 226.
About Symantec OpsCenter and Symantec OpsCenter Analytics

Table 2-1 lists the differences between Symantec OpsCenter and Symantec OpsCenter Analytics. Table 2-1 Difference between Symantec OpsCenter and Symantec OpsCenter Analytics Symantec OpsCenter Analytics
The licensed version of OpsCenter is called Symantec OpsCenter Analytics.
Symantec OpsCenter
The unlicensed version of OpsCenter is called Symantec OpsCenter
Symantec OpsCenter is visible from the title Symantec OpsCenter Analytics is visible bar and logon page of the OpsCenter console. from the title bar and logon page of the OpsCenter console. Symantec OpsCenter lets you do operational Symantec OpsCenter Analytics lets you do reporting. advanced business-level reporting. With Symantec OpsCenter Analytics, you have additional reporting functionality like creating custom reports, creating reports using SQL queries, NetWorker, running or configuring chargeback reports, viewing report data for any previous date etc. . You can also collecting data from third-party products like:

IBM TSM EMC Legato
More information about the licensed features is available. See About the OpsCenter Analytics licensed features on page 72. You cannot create or customize views using Symantec OpsCenter Analytics lets you Java View Builder. create and customize multi-level views using Java View Builder.
72
About the OpsCenter Analytics licensed features

Table 2-2 shows the list of licensed features, where they are located in the OpsCenter console, and how they appear in the unlicensed version. Table 2-2 Licensed Feature Licensed features in OpsCenter Analytics From where you can What is shown in the access this feature on the unlicensed OpsCenter OpsCenter Analytics version console
Reports > Report Templates Create a custom report > Create a New Report > option is disabled. Create a Custom Report Reports > My Reports > Create a New Report > Create a Custom Report Create a report using SQL query Reports > Report Templates Create a report using SQL > Create a New Report > query option is disabled. Create a report using SQL query Reports > My Reports > Create a New Report > Create a report using SQL query Run or view chargeback reports Report > Report Templates Chargeback reports are > Chargeback Reports disabled. Chargeback settings are disabled.
Create a Custom Report
Control chargeback settings Settings > Chargeback
Create or edit data collectors Settings > Configuration > for IBM TSM, EMC Legato Agent > Create Data NetWorker Collector
You cannot create or edit data collectors for third-party products like IBM Tivoli Storage Manager In the Data Collector Wizard, (TSM) and EMC Legato in the Select Product NetWorker. drop-down list, TSM and EMC Legato NetWorker options are disabled. Settings > Configuration > Agent > Edit Data Collector
73
Table 2-2 Licensed Feature
Licensed features in OpsCenter Analytics (continued) From where you can What is shown in the access this feature on the unlicensed OpsCenter OpsCenter Analytics version console
Report > Report Templates > Create New Report (Relative and Absolute Timeframe window on the Select Parameters page) Reports > My Reports > Create New Report (Relative and Absolute Timeframe window on the Select Parameters page) Report > Report templates (Run a report, click Edit Report and then Relative and Absolute Timeframe window.) Reports > My Reports (Run a report, click Edit Report and then Relative and Absolute Timeframe window.) You can view report data for the previous 60 days only. To view the data that is older than 60 days, you must use a licensed version.
Full control over report timeframe selection. You can view report data for any previous date.
Reconcile Task
Monitor > Jobs. The Reconcile option under the More drop-down list is disabled. Settings > Edit View level Alias Settings > Configuration > Object Types
The Reconcile option is disabled.
Edit View level Alias tab
The Edit View level Alias tab is disabled. The Object Types tab is disabled. You cannot log on to the View Builder. Access to the View Builder is denied if no license is there.
Object Types
View Builder
74
About the NetBackup and OpsCenter DVD

Symantec OpsCenter is shipped with the NetBackup media kit and also as a separate OpsCenter DVD.
About the NetBackup media kit

The NetBackup Enterprise Server media kit organizes the DVDs by operating system platform. The NetBackup media kit includes a separate DVD for each platform. Each NetBackup DVD also lets you install Symantec OpsCenter for the specific platform. You can use the appropriate DVD to install Symantec OpsCenter and required components. See the NetBackup Installation Guide for more details about 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 licensed version. With the unlicensed version (Symantec OpsCenter), you cannot access the licensed features. With the demo version, you can access the licensed OpsCenter features for 60 days (starting from the day you install the demo key). See About the OpsCenter licensing model on page 69.
About the Symantec OpsCenter DVD

A separate DVD that contains OpsCenter software is also available. This DVD contains 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 licensed version. With the unlicensed version (Symantec OpsCenter), you cannot access the licensed features. With the demo version, you can access the licensed OpsCenter Analytics features for 60 days (starting from the day you install the demo key). See About the OpsCenter licensing model on page 69.
About platforms supported by OpsCenter

This section provides information about the platforms that OpsCenter supports. Note: Refer to the compatibility matrix that is posted on the Symantec Support Web site for the latest information on the platforms that OpsCenter supports. This document is posted at the following URL: http://entsupport.symantec.com/docs/303344
75
Table 2-3 Platform
OpsCenter operating system requirements Server

32-bit 64-bit Yes
Agent
32-bit Yes 64-bit Yes* See Note Yes Yes Yes* See Note
View Builder
32-bit Yes 64-bit Yes* See Note
Windows 2003 SP2
Yes
Windows 2003 R2 Yes
Yes
Yes* See Note
Windows 2008
Yes
Yes
Yes
Yes* See Note
Yes
Yes* See Note
Windows 2008 R2 Yes
Yes
Yes
Yes* See Note
Yes
Yes* See Note
Solaris 9 Solaris 10 x64 Solaris 10 SPARC HP Itanium 11.23 11.31 AIX 5.3 AIX 6.1
No No No No
No Yes Yes Yes
No No No No
Yes No Yes No
No No No No
No No No No
No No
Yes Yes Yes
No No No
No No No
No No No
No No No
Linux RedHat 4.0, No 5.0 Linux SUSE ES 10 No (SP2) & 11
Yes
No
No
No
No
Note: * signifies 32-bit binaries working on 64-bit architecture.
76
About important notes on operating systems and OpsCenter deployment limitations

This section provides a few important notes regarding the supported operating systems and a few limitations that you need to take care of during OpsCenter deployment. Warning: Always refer to the OpsCenter sections of the NetBackup release notes for any last-minute changes to the information that is presented in this document. The release notes for your release of OpsCenter also include any restrictions or limits for OpsCenter. Important notes on operating systems:
On Windows system, the OpsCenter Server, Agent, and Java View Builder require the Microsoft C Runtime library 7.1 and Microsoft C++ runtime library 7.1. If installing OpsCenter on AIX, ensure that the XLC runtime version is 9.0 and higher. The OpsCenter Server is not supported on non-global Solaris zones. The OpsCenter Server and Agent are supported in a VMware virtual machine guest operating system environment.
OpsCenter deployment limitations:
You must install OpsCenter Server and Agent of the same versions. For example, Agent 7.0 works only with Server 7.0 or Server 6.5 is compatible only with Agent 6.5. Only the OpsCenter Server can be installed in a clustered mode on UNIX and Windows, with Veritas Cluster Server (VCS). The OpsCenter installer automatically sets the max heap size to 1024MB. Your system may require a lesser max heap size to properly run all applications. For more information, refer to the NetBackup Backup Planning and Performance Tuning Guide.
About backup and archiving products supported by Symantec OpsCenter

This section lists the backup and archiving products that OpsCenter supports. Note that with the licensed version of OpsCenter, you can do advanced reporting from the data that is collected from all of these products. With the unlicensed
77
version, you cannot collect data from third-party products like IBM Tivoli Storage Manager (TSM) and EMC Legato NetWorker. Warning: Always refer to the OpsCenter sections of the NetBackup release notes for any last-minute changes to the information that is presented in this document. The release notes for your release of OpsCenter also include any restrictions or limits for OpsCenter. Table 2-4 lists the backup and archiving products that OpsCenter supports. Table 2-4 Backup and archiving products supported by Symantec OpsCenter Versions Support level
Backup or Archiving product

Symantec NetBackup
6.0 MP7 and higher versions, All supported NetBackup 6.5 and higher versions, 7.0 platforms (except 7.0) by remote agent
Note: NBU 7.0 does not require

any Agent. Native agent for Windows 2003 (SP2 & R2), Windows 2008 (SP2 & R2), and Solaris 9, 10 Symantec NetBackup PureDisk Symantec Backup Exec 6.2, 6.2.2, 6.5, 6.5.1, 6.6 PureDisk supported platform (PDOS) by remote agent All supported Symantec Backup Exec platforms by remote agent. Native agent on backup servers on Windows 2003 (SP2 & R2), 2008 (SP2 & R2) All supported Symantec Enterprise Vault platforms by remote agent Native agent on Microsoft SQL Server 2005 or 2008 (where Enterprise Vault database resides) on Windows 2003 (SP2 & R2), 2008 (SP2 & R2).
10d, 11d, 12.0, 12.5
Note: OpsCenter does not

support Symantec Backup Exec running on NetWare.
Symantec Enterprise Vault
7.5, 8.0
78
Table 2-4
Backup and archiving products supported by Symantec OpsCenter (continued) Versions Support level
Native agent on backup servers on Windows 2003 (SP2 & R2), 2008 (SP2 & R2) and Solaris 9/10 Data collection is possible only with a licensed version of OpsCenter.
EMC Legato NetWorker 7.3
IBM Tivoli Storage Manager (TSM)
5.3, 5.4, 5.5
All supported TSM platforms by remote agent Native agent for backup server on Windows 2003 (SP2 & R2), 2008 (SP2 & R2) and Solaris 9/10 Data collection is possible only with a licensed version of OpsCenter.
About managed NetBackup master server considerations

Consider the following recommendations and requirements for your managed NetBackup master servers. Warning: Always refer to the OpsCenter sections of the NetBackup release notes for any last-minute changes to the information that is presented in this document. The release notes for your release of OpsCenter also include any restrictions or limits for OpsCenter. The following recommendations and requirements should be considered for your managed master servers:
Installation of OpsCenter server software on a NetBackup master or media server is possible if you want to monitor only one master server (i.e. the master server on which the OpsCenter server software is installed). To monitor more than one master server, Symantec recommends that you install the OpsCenter server software on a separate standalone server. For information on sizing requirements, please see the NetBackup 7.0 Additional Operational Notes technote at the following location: http://entsupport.symantec.com/docs/337179
79
OpsCenter does not collect data from the managed servers that are configured within a network address translation (NAT) network. The OpsCenter server should be configured as a fixed host with a static IP address. Symantec recommends that any NetBackup master server be monitored by only one OpsCenter server. OpsCenter can monitor NetBackup master servers with 6.0 MP5 and later versions. OpsCenter can be used to monitor a NetBackup cluster. See NetBackup High Availability Administrator's Guide for more details on setting up a NetBackup cluster environment. Also review the OpsCenter sections of the NetBackup release notes before using OpsCenter for monitoring NetBackup clusters.
More information about adding managed NetBackup servers in OpsCenter is available. See Adding a master server in the OpsCenter console on page 282.
About using NBSL to collect data from NetBackup master servers

A NetBackup 7.0 master server does not require any Agent or data collector for data collection. The data is collected automatically by the OpsCenter server from an NBU 7.0 master server using NetBackup Service Layer (NBSL). However, an Agent must be installed to collect specific data (image, error log, and scheduled jobs data) from a master server whose version is less than 7.0. Starting with the 6.0 release of NetBackup, NBSL components are included as a part of NetBackup on master and media servers. OpsCenter requires NBSL for all NetBackup monitoring, managing, and control functions. OpsCenter is affected if NBSL stops running on a managed NetBackup server. If NBSL stops, OpsCenter may not capture any changes that were made to the NetBackup configuration. When NBSL restarts, OpsCenter correctly recaptures the latest state. See the NetBackup Administrators Guide, Volume II for more information about NBSL.
80
Design your OpsCenter server

Before setting up a Symantec OpsCenter (OpsCenter) server, review the recommendations and requirements that are listed in the earlier sections. See About managed NetBackup master server considerations on page 78.
Sizing considerations
The size of your OpsCenter server depends largely on the number of NetBackup objects 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 be sized 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 space requirements, followed by a link to the sizing guidelines for OpsCenter.
About the OpsCenter database

The Sybase database that OpsCenter uses is similar to the database that NetBackup uses. The database is installed as part of the OpsCenter server installation. Note the following:
After you configure OpsCenter, OpsCenter disk space depends on the volume of data initially loaded on the OpsCenter server from the managed NetBackup servers. The initial data load on the OpsCenter server is in turn dependent on the following data present in the managed master servers:

Number of policy data records Number of job data records
81
Number of media data records
The rate of OpsCenter database growth depends on the quantity of managed data. This data can be policy data, job data, or media data.
Information is available on how to adjust database values for better OpsCenter performance. See Tuning OpsCenter for more performance on page 155.
About the OpsCenter sizing guidelines

To know the sizing guidelines for your OpsCenter server, see the following online PDF titled, NetBackup 7.0 Additional Operational Notes, contained in Technote number 337179 on the Symantec Support Web site. You can access this document from the following URL: http://entsupport.symantec.com/docs/337179 The online PDF also contains additional operational note information about OpsCenter.
About supported upgrade paths

OpsCenter 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 Latest Maintenance Pack of 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 the supported version. See the product documentation for details on how to upgrade.
About OpsCenter Agent deployment

This section describes the deployment scenarios of OpsCenter Agent. It helps you decide the Agent deployment in your environment.
82
Note: You must install OpsCenter Server and Agent of the same versions. For example, OpsCenter Agent 7.0 works only with OpsCenter Server 7.0. OpsCenter Agent can either be deployed on the OpsCenter Server host, product host (for example, a NetBackup master server whose version is less than 7.0, a Backup 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 OpsCenter host. This depends on the product that you want to collect data from and its operating system. The prerequisites for collecting data from each product vary and are described in their respective data collection sections. Note: A NetBackup 7.0 master server does not require any Agent for data collection. The data is collected automatically by the OpsCenter server from an NBU 7.0 master server using NBSL. However for a master server whose version is less than 7.0, an Agent must be installed to collect specific data (image, error log, and scheduled jobs data) .
Note: You do not require an OpsCenterAgent to collect data from PureDisk. If you have installed the VBR Agent only for PureDisk data collection, you must manually uninstall the VBR Agent. See About backup and archiving products supported by Symantec OpsCenter on page 76. A single Agent can have multiple data collectors configured which collect data from the respective product host. Note: In case of a NetBackup and EMC Legato Networker host, you need separate OpsCenter Agents to collect data from servers with different versions. See About data collection in OpsCenter on page 259. Only one Agent can be installed on a single host, which can have multiple data collectors (were called 'Agent Modules' previously) configured. See Installing Symantec OpsCenter on Windows and UNIX on page 90.
About Agent deployment in case of different product versions

The following section describes what should be the Agent deployment if you want to collect data from different product versions.
83
NetBackup
You need separate Agents to collect data from different versions of NetBackup master server . NetBackup binaries (Remote Admin Console for Windows and master or media server for UNIX) installed on the Agent host should match the version of the NetBackup master server .
Note: A NetBackup 7.0 master server does not require any

Agent for data collection. However for a master server whose version is less than 7.0, an Agent must be installed to collect specific data (scheduled jobs, image, and error logs). PureDisk You don't need a separate Agent to collect data from PureDisk. You can use the inbuilt Agent of the OpsCenter Server for data collection. To create or configure the data collector, select the Agent that is installed as Integrated Agent.
Note: You do not require an OpsCenterAgent to collect data

from PureDisk. If you have installed the VBR Agent only for PureDisk data collection, you must manually uninstall the VBR Agent. See Configuring PureDisk data collector on page 291. Backup Exec You can use same Agent to collect data from Backup Exec Servers with different versions.
Note: To collect data from Backup Exec Server host, you

need to install the Agent on a Windows host, as Backup Exec supports only Windows platform. IBM TSM You can use same OpsCenter Agent to collect data from TSM servers with different versions. You need separate OpsCenter Agents for Legato servers with different versions. Agent needs to be installed on the Legato server host. You can use the same OpsCenter Agent to collect Enterprise Vault data from Microsoft SQL Servers with different versions.
EMC Legato Networker
Enterprise Vault
Note: To collect Enterprise Vault / archive data, you need

to install the OpsCenter Agent on a Windows host, as Enterprise Vault supports only Windows platform.
About installing Agent on a product host

OpsCenter Agent can be installed on a product host.
84
The following products support local Agent installation:

Symantec Enterprise Vault Symantec NetBackup Symantec Backup Exec IBM TSM EMC Legato Networker Note: EMC Legato Networker does not support remote OpsCenter Agent installation. You must install the Agent on the EMC Legato Networker host.
Installing Agent in this fashion has a very low effect on the backup environment by adding agent. The OpsCenter Agent must support the operating system of the backup application host. Installing the Agent on a remote backup application host has the following advantages:

Ease of maintenance to upgrade agent; you only service one host. Minimal intrusion on backup hosts; one agent that is installed on a backup host.
A disadvantage of installing the OpsCenter Agent on a remote backup application host is that the Agent may use significant system resources, which can affect the backup application hosts performance.
About installing the Agent on a host different than a product host

OpsCenter Agent can be installed on a host different than the product host. The different 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 agent and backup application.
In such situations, the Agent should remotely communicate with backup products. The following products support Remote Agent installation:
85
Symantec NetBackup Symantec NetBackup PureDisk Note: PureDisk does not support local Agent installation, because OpsCenter does not support PDOS (PureDisk Operation System). Therefore PureDisk Server and OpsCenter Agent cannot reside on the same host. Symantec Backup Exec 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 server that you want to monitor / report on. UNIX platforms do not support RAC. For back up products (except Backup Exec), you need to have backup application client (.exe) on the Agent host to collect data remotely. See Collecting data from Enterprise Vault on page 292. Advantages of installing the Agent on the OpsCenter Server host or a separate host include the following:
You do not have to install additional software on backup application hosts as the 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 upgrading the agent.
Disadvantages of installing the Agent on the OpsCenter Server host include the following:
You must install a component of the backup application on the OpsCenter Server host. For example, you need separate OpsCenter Agents to collect data from different versions of NetBackup Master Server. NetBackup binaries (Remote Admin Console for Windows and Master or Media Server for Solaris) installed on the Agent host should match the version of the NetBackup Master Server. In some situations, a backup application license key is required for the component that is installed on the OpsCenter Server host.
86
Examples of Agent deployment in a NetBackup setup

In a NetBackup setup, the following OpsCenter deployment scenarios are valid:
OpsCenter Server is installed on OpsCenterHost 1, Agent is installed on AgentHost 1, and NetBackup 6.5 master server is installed on ProdHost 1 You need to install NetBackup 6.5 Remote Admin Console or NetBackup master server on AgentHost 1 and configure a data collector to collect data from ProdHost 1. OpsCenter Server and Agent are installed on OpsCenterHost 1 and NetBackup master server is installed on ProdHost 1 You need to install NetBackup 6.5 Remote Admin Console or NetBackup master server on OpsCenterHost 1 and configure a data collector to collect data from ProdHost 1. OpsCenter Server is installed on OpsCenterHost 1 and NetBackup master server and Agent are installed on ProdHost 1 You need to configure a data collector on OpsCenterHost 1 to collect data from ProdHost 1. OpsCenter Server and Agent are installed on OpsCenterHost 1, NetBackup 6.5 master server is installed on , and ProdHost 1 another NetBackup 6.5 master server is installed on ProdHost 2. You need to install NetBackup 6.5 Remote Admin Console or master server on OpsCenterHost 1 and configure two data collectors, one to collect data from ProdHost 1 and another to collect data from ProdHost 2. OpsCenter Server is installed on OpsCenterHost 1, Agent A1 is installed on AgentHost 1, and Agent A2 is installed on AgentHost 2. NetBackup 6.0 master server is installed on ProdHost 1 and NetBackup 6.5 master server is installed on ProdHost 2. You need to install NetBackup 6.0 Remote Admin Console or master server on AgentHost 1 and configure a data collector to collect data from ProdHost 1 and install NetBackup 6.5 Remote Admin Console or master server on the AgentHost 2 and configure a data collector to collect data from ProdHost 2
Before you install or upgrade

Review the following checklists before installing Symantec OpsCenter (OpsCenter) and before upgrading from NetBackup Operations Manager (NOM) or r Veritas Backup Reporter (VBR) to Symantec OpsCenter. Table 2-5 lists the things you must check before installing OpsCenter or before upgrading from NOM or VBR to OpsCenter on a Windows server.
87
Table 2-5 Serial No.

1.
OpsCenter install and upgrade checklist for Windows Checklist

Ensure that you install OpsCenter software on a supported platform. See About platforms supported by OpsCenter on page 74.
2. 3. 4.
Ensure that no other installation is in progress while installing OpsCenter. Ensure that the antivirus software is disabled before installing OpsCenter. Ensure that your OpsCenter server is configured as a fixed host with a static IP address. Ensure that the fully qualified domain name (FQDN) of your OpsCenter server has maximum 44 characters. For fresh OpsCenter installation, ensure that the database directory has at least 20 MB of available space. Note that once you install and start using OpsCenter, the database grows in size, and requires more space. See Design your OpsCenter server on page 80.
5.
6.
7.
Ensure that the necessary ports are opened before installing OpsCenter on a hardened server. See About communication and firewall considerations on page 205.
8.
Ensure that the name of the folder in which you are installing OpsCenter does not contain any special characters like %, ~, !, @, $, &, ^, #. If a file called 'program' exists in the C: folder of your OpsCenter server, rename, or delete the file before installing OpsCenter. If you need to monitor a single master server, install OpsCenter on the NetBackup master or media server (recommended). If you are upgrading from NOM to OpsCenter , ensure that you have one of the following NOM versions installed:

9.
10.
11.
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 to one of the supported versions. See the NOM documentation for details on how to perform this upgrade.
88

12.
OpsCenter install and upgrade checklist for Windows (continued) Checklist

If you are upgrading from VBR to OpsCenter Analytics, ensure that you have one 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 to one of the supported versions. See the VBR documentation for details on how to perform this upgrade. 13. If upgrading from VBR or NOM, ensure that the OpsCenter database directory has thrice as much space (3x) as that taken by your NOM database or VBR database (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 available space. Note that once you install and start using OpsCenter, the database grows in size, and requires more space. See Design your OpsCenter server on page 80.
Table 2-6 lists the things you must check before installing OpsCenter or before upgrading from NOM or VBR to OpsCenter on a UNIX server. Table 2-6 Serial No.
1.
OpsCenter install and upgrade checklist for UNIX Checklist

Ensure that you install OpsCenter software on a supported platform. See About platforms supported by OpsCenter on page 74.
2. 3.
Ensure that no other installation is in progress while installing OpsCenter. Ensure that your OpsCenter server is configured as a fixed host with a static IP address. Ensure that the OpsCenter server does not have a symbolic link to the /opt directory. Ensure that the fully qualified domain name (FQDN) of your OpsCenter server has maximum 44 characters. For fresh OpsCenter installation, ensure that the database directory has at least 20 MB of available space. Note that once you install and start using OpsCenter, the database grows in size, and requires more space. See Design your OpsCenter server on page 80.
4.
5.
6.
89

7.
OpsCenter install and upgrade checklist for UNIX (continued) Checklist

Ensure that the necessary ports are opened before installing OpsCenter on a hardened server. See About communication and firewall considerations on page 205.
8.
If you need to monitor a single master server, install OpsCenter on the NetBackup master or media server (recommended). If installing OpsCenter on an AIX platform, ensure that the XLC runtime version is 9.0 or higher. If you upgrade from NOM to OpsCenter , ensure that you have one of the following NOM versions installed:

9.
10.
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 to one of the supported versions. See the NOM documentation for details on how to perform this upgrade. 11. If you are upgrading from VBR to OpsCenter Analytics, ensure that you have one 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 to one of the supported versions. See the VBR documentation for details on how to perform this upgrade. 12. If you are upgrading from VBR or NOM, ensure that the OpsCenter database directory has thrice as much space as that taken by your NOM database or VBR 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 available space. Note that once you install and start using OpsCenter, the database grows in size, and requires more space. See Design your OpsCenter server on page 80.
90
Installing Symantec OpsCenter Installing Symantec OpsCenter on Windows and UNIX

13.
OpsCenter install and upgrade checklist for UNIX (continued) Checklist

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 like Solaris 8 or 9), run the Backup.sh script from the Server directory of the OpsCenter DVD to back up the necessary data. This backed up data can then be restored on the supported OpsCenter platform during installation. See Design your OpsCenter server on page 80.
Installing Symantec OpsCenter on Windows and UNIX

This section describes the procedures for fresh installation of OpsCenter on Windows and UNIX hosts. You can also upgrade from an earlier NOM or VBR installation. See Upgrading to OpsCenter on Windows and UNIX on page 102. You can install OpsCenter in a clustered mode. See Clustering Symantec OpsCenter on page 166. Table 2-7 provides steps to install OpsCenter components. You can use this table as a checklist while installing Symantec OpsCenter.
91
Table 2-7 Step number Step

1
Steps to install / upgrade / cluster Symantec OpsCenter Reference topic

See Planning an OpsCenter installation on page 67.
Review the hardware / software requirements for OpsCenter Server and Agent hosts, carefully. Make sure that you satisfy the operating system requirements. See About platforms supported by OpsCenter on page 74. Go through the firewall settings and port number information. See About communication and firewall considerations on page 205. Go through the Agent deployment section. See About OpsCenter Agent deployment on page 81. Review the Install/Upgrade checklists before installing OpsCenter. See Before you install or upgrade on page 86.
Go through the appropriate installation section. Different sections are available for fresh installation, upgrade, and clustering. properly.
See Installing Symantec OpsCenter on Windows on page 91. See Installing Symantec OpsCenter on See Upgrading to OpsCenter on Windows and UNIX on page 102. See Clustering Symantec OpsCenter on page 166.
Note: After installation, verify if OpsCenter is running UNIX on page 96.
Installing Symantec OpsCenter on Windows

Use the Installation Wizard to install OpsCenter on a Windows host. You may install 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. Note: You must not run any other installation while installing OpsCenter components. Additionally after an installation is complete, you should wait for some time before installing other OpsCenter components.
92
Installing Symantec OpsCenter Server on Windows

Use the following procedure to install Symantec OpsCenter server on Windows hosts. Note: In case you try to install OpsCenter components on a system where OpsCenter is already installed, the installer runs in a Maintenance mode and lets you repair or remove the OpsCenter component that is installed on your system. To install OpsCenter Server on Windows
On a Windows host where you want to install OpsCenter server, insert the appropriate OpsCenter product DVD in the DVD drive. You may install 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.
If autorun is enabled, the Symantec DVD Browser appears. If autorun is not enabled, click Start > Run. On the Run dialog box, in the Open text box, type D:\Browser.exe and press Enter: Where D is the DVD drive. The Symantec DVD Browser appears.
3 4
On the Symantec DVD browser, click the Installation link. If you use the NetBackup media kit to install OpsCenter, click OpsCenter Software Installation. Ignore this step if you install OpsCenter server software from the OpsCenter DVD. Click the OpsCenter Server Installation link to install Symantec OpsCenter server. The Symantec OpsCenter Installation Wizard appears. Click Next. Read the license agreement, check I accept the terms of the license agreement and click Next.
5 6 7
93
The following options are displayed:

Install to this computer only Select this option to install OpsCenter Server on this host. Install a clustered OpsCenter Select this option to install OpsCenter Server on all Server selected nodes, in a clustered mode. You need to install OpsCenter Server manually on each node of the cluster. This option is enabled if you have Veritas Cluster Server (VCS) installed. See Clustering Symantec OpsCenter on Windows on page 167. See Clustering Symantec OpsCenter Server on UNIX on page 173.
Select Install to this computer only.
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 actual space available in the installation directory. Note: Click Custom if you want to change the default settings, locations, or port numbers. Click Next.
10 On the License Keys screen, enter your demo or permanent key that you have
received with the purchase of OpsCenter and click Add Key. If you do not enter a key, you get an unlicensed version. With the unlicensed version (Symantec OpsCenter), you cannot access the licensed features. See About the license keys on page 70. You can also add the license keys later from the OpsCenter console. See Managing licenses on page 226.
11 Click Next. The installer shows the summary of the settings that you have
selected for installation. Check Save Summary to field to save the installation summary. Click Browse to save the installation summary in your preferred location.
94
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 view
installation logs.
14 Click Finish.
Installing Symantec OpsCenter Agent on Windows

Use the following procedure to install Symantec OpsCenter Agent on a Windows host. To install OpsCenter Agent
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 the OpsCenter Agent, review the information on Agent deployments. See About OpsCenter Agent deployment on page 81.
On a Windows host where you want to install OpsCenter Agent, insert the appropriate OpsCenter product DVD in the DVD drive. You may install OpsCenter Agent 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.
4 5
On the Symantec DVD Browser, click the Installation link. If you use the NetBackup media kit to install OpsCenter Agent, click OpsCenter Software Installation. Ignore this step if you install OpsCenter Agent software from the OpsCenter DVD. Click the OpsCenter Agent Installation link to install OpsCenter Agent. The Symantec OpsCenter Installation Wizard appears. Click Next.
6 7
95
8 9
Read the license agreement, check I accept the terms of the license agreement and click Next. The default installation location is C:\Program Files\Symantec. To install OpsCenter to a different directory, click Browse. Note: The default installation location on a Windows 64-bit machine is C:\Program Files (x86)\Symantec. Click Next.
10 The installer shows the summary of the settings that you have selected for
Agent installation. Check Save Summary to field to save the installation summary. Click Browse to save the installation summary in your preferred location.
11 Click Install.
The installer starts installation of OpsCenter Agent.
12 After successful installation, you can view Agent installation logs or open
the readme file.
13 Click Finish.
Installing Symantec OpsCenter View Builder on Windows

Use the following procedure to install Symantec OpsCenter View Builder. To install OpsCenter View Builder
On the OpsCenter Server host, insert the appropriate OpsCenter product DVD in the DVD drive. You may install 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.
On the Symantec DVD Browser, click the Installation link.
96
If you use the NetBackup media kit to install OpsCenter View Builder, click OpsCenter Software Installation. Ignore this step if you install OpsCenter View Builder software from the OpsCenter DVD. Click the OpsCenter View Builder Installation link to install Symantec OpsCenter View Builder. The Symantec OpsCenter Installation Wizard appears. Click Next. Read the license agreement, check I accept the terms of the license agreement and click Next. On the Installation Location screen, click Browse if you want to change the default location for Symantec OpsCenter View Builder installation. Note: The default installation location on a Windows 64-bit machine is C:\Program Files (x86)\Symantec.
5 6 7 8
Select a new location and click Next. Symantec OpsCenter View Builder installation. Check Save Summary to field to save the installation summary. Click Browse to save the installation summary in your preferred location.
10 The installer shows the summary of the settings that you have selected for
11 Click Install.
The installer starts installation of Symantec OpsCenter View Builder.
12 After successful installation, you can view the installation logs or open the
readme file.
13 Click Finish.
Installing Symantec OpsCenter on UNIX

This 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 media kit. The OpsCenter DVD contains OpsCenter software for all available platforms. The NetBackup media kit contains a separate DVD for each platform. Note: If installing OpsCenter on AIX, ensure that the XLC runtime version is 9.0 and higher.
97
Installing Symantec OpsCenter Server on UNIX

Use the following procedure to install OpsCenter server software on UNIX hosts. To install OpsCenter Server on UNIX
1 2
Open a UNIX console and log on as root on the target host. Mount the OpsCenter product DVD for the appropriate platform on which you are installing. You may install 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.
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 the Server directory on the DVD. Type the following command:./install. Press Enter.
If you use the NetBackup media kit to install OpsCenter, navigate to the Server directory.
cd OpsCenter/Server
Type the following command:./installOpsCenterServer. Press Enter.
4 5
The Welcome message is displayed. Press Enter to continue. The installer then checks if OpsCenter Server is installed on the system or not. It prompts you in case OpsCenter is already installed. The installer also examines the system for existing packages. For Solaris Sparc, the installer also asks for installing Server or Agent if you are installing from OpsCenter DVD.
The installer displays a list of components that get installed like PBX, AT, Symantec WebGUI Server, Symantec Database etc. Review this list and press Enter to continue.
98
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 OpsCenter Server packages and press Enter. To accept the default path (/opt), press Enter without typing a directory path. Non default installation is not supported on AIX platform.
8 9
Type y to confirm the directory path and press Enter. OpsCenter server is installed on the system. Type a directory path under which to install the OpsCenter database and press Enter. If you create an alternate database directory, the script creates the folder OpsCenterServer below your directory. To accept the default database installation directory (/var/Symantec), press Enter without typing a directory path. In case the database installation directory (/var/symantec) does not exist on the 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
99
10 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 temporary space, 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 press Enter.
11 Review the installation options you selected. The location of database directory
and the database temp directory is also displayed.
12 Type y and press Enter to confirm the selection and continue.

Type n and press Enter to repeat the configuration steps and revise your selection.
100
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 OpsCenter for the first time, you do not need to restore any data. Type n and then press Enter. Use this option if you are upgrading from NOM or VBR to OpsCenter server software on a different UNIX system. An example scenario is when NOM or VBR is running on Solaris 8 and you require the same data with OpsCenter on 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 the OpsCenter server. The Backup.sh script is located in the Server directory of the OpsCenter DVD. More information on how to upgrade to OpsCenter server on a different system is available. See Upgrading to OpsCenter Server on a different UNIX system on page 148.
14 You are prompted for license information. The installer prompts you with
the 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 purchase of OpsCenter and press Enter. If you do not enter a key, you get an unlicensed version. With the unlicensed version (Symantec OpsCenter), you cannot access the licensed features. See About the license keys on page 70. You can also add the license keys later from the OpsCenter console. See Managing licenses on page 226.
Installing Symantec OpsCenter Agent on UNIX

Use the following procedure to install OpsCenter Agent on UNIX.
101
To install OpsCenter Agent on UNIX
1 2
Open a UNIX console and log on as root on the target host. Mount the appropriate OpsCenter product DVD for the platform on which you are installing. You may install 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.
If you use the OpsCenter DVD to install OpsCenter Agent, navigate to the appropriate OpsCenter platform directory and then the Agent directory on the DVD. Type the following command: ./install. Press Enter. If you use the NetBackup media kit to install OpsCenter Agent, navigate to the following location:
cd OpsCenter/Agent
Type the following command: ./installOpsCenterAgent. Press Enter.
Type the following command:

./installOpsCenterAgent. Press Enter.
5 6
The Welcome message is displayed. Press Enter to continue. The installer then checks if OpsCenter Agent is installed on the system or not. It prompts you in case OpsCenter Agent is already installed. For Solaris Sparc, the installer also asks for installing Server or Agent if you are installing from OpsCenter DVD.
7 8
The installer displays a list of components that get installed like PBX, Symantec WebGUI Agent etc. Review this list and press Enter to continue. It is optional to configure the OpsCenter Agent during installation. You may choose 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.
102
Installing Symantec OpsCenter Upgrading to OpsCenter on Windows and UNIX
Enter the location where you want to install OpsCenter Agent. Type a directory path where you want to install the Symantec OpsCenter Agent packages and press Enter. To accept the default path (/opt), press Enter without typing a directory path.
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.
Upgrading to OpsCenter on Windows and UNIX

This section describes how you can upgrade from NOM or VBR to OpsCenter on Windows and UNIX platforms.
Upgrade considerations
When you upgrade from Veritas Backup Reporter to OpsCenter Server and access the OpsCenter console, you may not see data for some columns in the following views:
Monitor > Jobs No data is shown for Available Columns (columns that are not displayed) like PID, Owner, Parent, Data Movement etc. No data is shown in this view No data is shown for some columns No data is shown for some columns No data is shown for some columns No data is shown for some columns No data is shown for some columns
Monitor > Services Monitor > Policies Monitor > Media Monitor > Devices Manage > Storage Manage > Devices
This data is not shown because VBR does not collect this data and hence this data is not available in the VBR database. The data for all these columns is shown after data collection for the master server is enabled during data migration. Once the data collection is enabled, this data is collected from the master server and shown on the OpsCenter console.
103
Note: For most of the entities like policies, media, devices etc., all previous data is 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 Symantec OpsCenter on Windows and UNIX
The OpsCenter Installation Wizard automatically detects an older NOM installation. The OpsCenter installer only stops the existing NOM services. It does not uninstall your existing NOM installation. You can manually uninstall NOM after successfully migrating data and using Symantec OpsCenter for some time. During upgrade, OpsCenter server is installed, the older NOM database is saved and started. Note that a saved copy of the NOM database is used for upgrade. Data migration from the older NOM database to the new OpsCenter database starts once the Symantec OpsCenter Server Service is started while installing OpsCenter server. 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 that has to be migrated.
Upgrading from NetBackup Operations Manager to Symantec OpsCenter on Windows

Use the following procedure to upgrade to OpsCenter server on Windows. Note: You must not run any other installation while installing OpsCenter components. Additionally after an installation is complete, you should wait for some time before installing other OpsCenter components. To upgrade from NOM to Symantec OpsCenter on Windows
If autorun is enabled, the Symantec DVD Browser appears. If autorun is not enabled, click Start > Run. On the Run dialog box, in the Open text box, type D:\Browser.exe and press Enter:
104
Where D is the DVD drive. The Symantec DVD Browser appears.
3 4
On the Symantec DVD Browser, click the Installation link. If you use the NetBackup media kit to install OpsCenter, click OpsCenter Software Installation. Ignore this step if you install OpsCenter server software from the OpsCenter DVD. Click the OpsCenter Server Installation link to install Symantec OpsCenter server. The Symantec OpsCenter Installation Wizard appears. The Installation Wizard detects an existing installation of NetBackup Operations Manager 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 installed on your system: NetBackup Operations Manager Server: Version 6.5
5 6
Before you upgrade to Symantec OpsCenter, all existing NOM services are stopped automatically. After you successfully upgrade to Symantec OpsCenter, you can manually uninstall NOM.
7 8 9
Click Next. Read the license agreement, check I accept the terms of the license agreement and click Next. 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 and the actual space that is available. Note: Click Custom if you want to change the default settings, locations, or port numbers. Click Next.
105
10 Specify a location for saving the old NOM database. The default location is
C:\Program Files\Symantec\OpsCenter\SavedData. Click Browse to specify
a different location. Note: Ensure that the database location has adequate space by going through the Disk space requirements section on this page. A green checkmark appears in the Required column if there is adequate disk space.
11 On the Upgrade Settings page, enter a port number on which the old NOM
database can be started. The default port number is 13799. Click Next.
12 On the License Keys screen, enter your demo or permanent key that you have
received with the purchase of OpsCenter and click Add Key. If you do not enter a key, you get an unlicensed version (Symantec OpsCenter). With an unlicensed version, you cannot access the licensed features. See About the license keys on page 70.
selected for installation. Check Save Summary to option to save the installation summary. Click Browse to save the installation summary in your preferred location.
14 Click Install.
The installer installs OpsCenter Server software.
installation logs. Data migration from the old NOM database to the OpsCenter database starts once the Symantec OpsCenter Server service is started while installing OpsCenter server. You can also access the data migration status from the OpsCenter console. See Monitoring data migration from NOM to Symantec OpsCenter on page 120.
16 Click Finish.
Upgrading from NetBackup Operations Manager to OpsCenter on UNIX

Use the following procedure to upgrade from NOM to OpsCenter on UNIX.
106
To install OpsCenter Server on UNIX
1 2
If you use the OpsCenter DVD to install OpsCenter, go to the appropriate OpsCenter platform directory and then the Server directory. If using the NetBackup media kit, go to the following directory:
cd OpsCenter/Server
4 5 6
Type the following command:./installOpsCenterServer. Press Enter. The Welcome message is displayed. Press Enter to continue. The installer then checks for an existing NOM installation. It displays the following 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.
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 files can be saved and then press Enter. To accept the default directory path (/var/symantec), press Enter.
The installer displays a list of components that get installed like PBX, AT, Symantec WebGUI Server, Symantec Database etc. Review this list and press Enter to continue.
107
Type a directory path where you want to install the Symantec OpsCenter Server packages and press Enter. To accept the default path (/opt), press Enter without typing a directory path.
10 Type y to confirm the directory path and press Enter. 11 OpsCenter server is installed on the system.
Type a directory path under which to install the OpsCenter database and press Enter. If you create an alternate database directory, the script creates the folder OpsCenterServer below your directory. To accept the default database installation directory (/var/Symantec), press Enter without typing a directory path. 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

Type a directory path for the database server temporary space and press Enter. To use the database installation directory for database server temporary space, press Enter without typing a directory path.

108
15 Configuration changes are performed. You are prompted with the following
message:
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 press Enter. 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 any application.

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 the unlicensed 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 data migration status
Upgrading from Veritas Backup Reporter to OpsCenter Analytics on Windows and UNIX
The OpsCenter Installation Wizard automatically detects an older VBR installation. The OpsCenter installer only stops the existing VBR services. It does not uninstall your existing VBR installation. You can manually uninstall VBR after upgrading successfully to Symantec OpsCenter. During upgrade, OpsCenter is installed and the older VBR database is saved and started. Note that a saved copy of the VBR database is used for upgrade. The data migration from the older VBR database to the new OpsCenter database starts after you successfully upgrade to OpsCenter.
109
The data migration process happens for each master server. You can also view the data migration process from the OpsCenter logon page. The data migration process may take time depending on the data that has to be migrated.
Upgrading from Veritas Backup Reporter to OpsCenter Analytics on Windows

Use the following procedure to upgrade from Veritas Backup Reporter Server, Agent, and View Builder to Symantec OpsCenter Server, Agent, and View Builder respectively. Note: You must not run any other installation while installing OpsCenter components. Additionally after an installation is complete, you should wait for some time before installing other OpsCenter components.
Upgrading from Veritas Backup Reporter Server to OpsCenter Server on Windows

Use the following procedure to upgrade from Veritas Backup Reporter Server to Symantec OpsCenter Server on Windows. To upgrade to OpsCenter Server on Windows
3 4
On the Symantec DVD Browser, click the Installation link. If you use the NetBackup media kit to install OpsCenter, click OpsCenter Software Installation. Ignore this step if you install OpsCenter server software from the OpsCenter DVD. Click the OpsCenter Server Installation link to install Symantec OpsCenter Server.
110
The Symantec OpsCenter Installation Wizard appears. The Installation Wizard detects an existing installation of Veritas Backup Reporter on the system. Based on your installed VBR version, the following message may be displayed on the Welcome screen:
The Installation has detected that the following software is already installed on your system: 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.
7 8 9
Click Next to continue. Read the license agreement, check I accept the terms of the license agreement and click Next. 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 the actual space that is available. Note: Click Custom if you want to change the default settings, locations, or port numbers. Click Next.
10 Specify a location for saving the old VBR database. The default location is
C:\Program Files\Symantec\OpsCenter\SavedData. Click Browse to specify
a different location. Note: Ensure that the database location has adequate space by going through the Disk space requirements section on this page. A green checkmark appears in the Required column if there is adequate disk space.
11 Click Next to continue.
111
12 On the Upgrade Settings page, enter a port number on which the old VBR
database can be started. The default port number is 13799. Note: Ensure that the port number that you enter is free and not used by any other application. Click Next.
13 On the License Keys screen, enter the demo or permanent key that you have
received with the purchase of OpsCenter and click Add Key. The license keys that are already installed on the system are also displayed in the box that is shown on this screen. The license type is also shown along with the key. If you do not enter a license key, your existing license keys are used. See About the license keys on page 70.
selected for installation. Check Save Summary to field to save the installation summary. Click Browse to save the installation summary in your preferred location.
15 Click Install.
The installer upgrades VBR server to OpsCenter Server software.
installation logs. Data migration from the old VBR database to the OpsCenter database starts once the Symantec OpsCenter Server service is started while installing OpsCenter server. You can also access the data migration status from the OpsCenter console. See Monitoring data migration from VBR to Symantec OpsCenter Analytics on page 134.
17 Click Finish. Upgrading from Veritas Backup Reporter Agent to OpsCenter Agent on Windows
Use the following procedure to upgrade from Veritas Backup Reporter Agent to Symantec OpsCenter Agent. You do not require an OpsCenterAgent to collect data from NetBackup 7.0 or PureDisk. However, you must install OpsCenter Agent if you want to collect data from other backup products.
112
Note: Once you upgrade your VBR Agent to the OpsCenter Agent, the port number that the VBR Agent uses is not required in OpsCenter. By default, the VBR Agent uses port number 7806. To upgrade to OpsCenter Agent on Windows
On a Windows host where you want to install OpsCenter Agent, insert the appropriate OpsCenter product DVD in the DVD drive. You may install OpsCenter Agent 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 4
On the Symantec DVD Browser, click the Installation link. If you use the NetBackup media kit to install OpsCenter Agent, click OpsCenter Software Installation. Ignore this step if you install OpsCenter Agent software from the OpsCenter DVD. Click the OpsCenter Agent Installation link to install Symantec OpsCenter Agent. The Symantec OpsCenter Installation Wizard appears. The Installation Wizard detects an existing installation of Veritas Backup Reporter Agent on the system. Based on your installed VBR Agent version, the following message may be displayed on the Welcome screen:
The Installation has detected that the following software is already installed on your system: Veritas Backup Reporter Agent: <Version>
5 6
Before you upgrade to Symantec OpsCenter Agent, all Veritas Backup Reporter services are stopped automatically. After you successfully upgrade to Symantec OpsCenter Agent, you must manually uninstall Veritas Backup Reporter Agent.
7 8
Click Next to continue. Read the license agreement, check I accept the terms of the license agreement and click Next.
113
On the Installation Location screen, click Browse if you want to change the default location for Symantec OpsCenter Agent installation. Note: Ensure that the installation directory that you specify has adequate space by going through the Disk space requirements section on this page. A green checkmark appears in the Required column if there is adequate disk space.
10 Select a new location and click Next. 11 The installer shows a summary of the settings that you have selected for
Symantec OpsCenter Agent installation. Check Save Summary to field to save the installation summary. Click Browse to save the installation summary in your preferred location.
12 Click Install.
The installer starts installation of Symantec OpsCenter Agent.
readme file.
14 Click Finish. Upgrading from Veritas Backup Reporter View Builder to OpsCenter View Builder on Windows
Use the following procedure to upgrade from Veritas Backup Reporter View Builder to Symantec OpsCenter View Builder To upgrade from Veritas Backup Reporter View Builder to Symantec OpsCenter View Builder
On the OpsCenter View Builder host, insert the appropriate OpsCenter product DVD in the DVD drive. You may install 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.
On the Symantec DVD Browser, click the Installation link.
114
If you use the NetBackup media kit to install OpsCenter View Builder, click OpsCenter Software Installation. Ignore this step if you install OpsCenter View Builder software from the OpsCenter DVD. Click the OpsCenter View Builder Installation link to install Symantec OpsCenter View Builder. The Symantec OpsCenter Installation Wizard appears. The Installation Wizard detects an existing Veritas Backup Reporter View Builder and shows the following 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.
5 6
Click Next to continue.
7 8
Read the license agreement, check I accept the terms of the license agreement and click Next. On the Installation Location screen, click Browse if you want to change the default location for Symantec OpsCenter View Builder installation. Note: Ensure that the installation directory that you specify has adequate space by going through the Disk space requirements section on this page. A green checkmark appears in the Required column if there is adequate disk space.
Select a new location and click Next. Symantec OpsCenter View Builder installation. Check Save Summary to field to save the installation summary. Click Browse to save the installation summary in your preferred location.
10 The installer shows a summary of the settings that you have selected for
11 Click Install.
The installer starts installation of Symantec OpsCenter View Builder.
readme file.
13 Click Finish.
115
Upgrading from Veritas Backup Reporter to OpsCenter on UNIX

Use the following procedure to upgrade from Veritas Backup Reporter Server and Agent 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 to Symantec OpsCenter Server on UNIX. To upgrade from VBR Server to OpsCenter Server on UNIX
1 2
If you use the OpsCenter DVD to install OpsCenter, go to the appropriate OpsCenter platform directory and then the Server directory. If using the NetBackup media kit, go to the following directory:
cd OpsCenter/Server
4 5 6
Type the following command:./installOpsCenterServer. Press Enter. The Welcome message is displayed. Press Enter to continue. The installer then checks for an existing VBR installation. It displays the following 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.
116
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 and configuration files and then press Enter. To save the VBR database and configuration files in the default directory path (/var/symantec), press Enter only.
The installer displays a list of components that get installed like PBX, AT, Symantec WebGUI Server, Symantec Database etc. Review this list and press Enter to continue. Type a directory path where you want to install the Symantec OpsCenter Server packages and press Enter. To accept the default path (/opt), press Enter without typing a directory path.
10 Type y to confirm the installation directory path and press Enter.

If any older version of packages like VRTSpbx is detected, it is automatically uninstalled and the required version is installed.
11 OpsCenter server is installed on the system.

Type a directory path under which to install the OpsCenter database and press Enter. The script creates the folder OpsCenterServer below the directory that you specify. To accept the default database installation directory (/var/Symantec), press Enter without typing a directory path. 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
117

Type y and press Enter to specify an alternate directory for the database server temporary space. Specify the directory location when prompted. Review the installation options that you selected (database and database temp directory locations). Type y and then press Enter. To use the database installation directory for database server temporary space, press Enter without typing a directory path. Review the installation options that you selected (database and database temp directory locations). Type y and then press Enter.
13 Configuration changes are performed. You are prompted with the following
message:
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 press Enter. 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 any application.

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.
118
Link on the OpsCenter logon page from where you can access the data migration status
Upgrading from Veritas Backup Reporter Agent to OpsCenter Agent on UNIX

Use the following procedure to upgrade a VBR agent to an OpsCenter agent on UNIX. You do not require an OpsCenterAgent to collect data from NetBackup 7.0 or PureDisk. However, you must install OpsCenter Agent if you want to collect data from other backup products. Note: Once you upgrade your VBR Agent to the OpsCenter Agent, the port that the VBR Agent uses is not required in OpsCenter. The default port that the VBR Agent uses is 7806. To upgrade a VBR Agent to OpsCenter Agent on UNIX
1 2
Open a UNIX console and log on as root on the target host. Mount the appropriate OpsCenter product DVD for the platform on which you are installing OpsCenter software. You may install 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.
If you use the OpsCenter DVD to install OpsCenter, go to the appropriate OpsCenter platform directory and then the Agent directory. If using the NetBackup media kit, go to the following directory:
cd OpsCenter/Agent
Type the following command:

./installOpsCenterAgent. Press Enter.
5 6
The Welcome message is displayed. Press Enter to continue. The installer displays a list of components that get installed like PBX, Symantec WebGUI Agent etc. Review this list and press Enter to continue.
119
It is optional to configure OpsCenter Agent during installation. You may choose to configure OpsCenter Agent later either manually or by running ./opt/VRTS/install/installOpsCenterAgent -configurecommand. To configure OpsCenterAgent now, type y and press Enter.
Enter the location where you want to install OpsCenter Agent. Type a directory path where you want to install the Symantec OpsCenter Agent packages and press Enter. To accept the default path (/opt), press Enter without typing a directory path.
Type y and then press Enter to confirm your installation options. summary, and response files on the path mentioned.
10 The OpsCenter Agent is installed. You can view the installation log files,
Troubleshooting database inconsistency issues during upgrade

The upgrade process may fail due to database inconsistency when you upgrade from VBR to OpsCenter server. Additional information may be displayed in the ServerService_<timestamp>.log file. This file is located in <INSTALL_PATH>\OpsCenter\server\logs directory on Windows and /<INSTALL_PATH>/SYMCOpsCenterServer/logs directory 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 schema like added, modified, or removed columns or constraints from the VBR database tables. To resolve this issue, you must manually undo the modifications that you have made to the database so that the database schema is similar to the released version.
120
To resolve database inconsistency errors
Modify the database as per the message in the ServerService_<timestamp>.log file. This file is located in <INSTALL_PATH>\OpsCenter\server\logs directory on Windows and /<INSTALL_PATH>/SYMCOpsCenterServer/logs directory on Solaris. Copy the modified ccsvc.db and ccsvc.log files from VBR database to the following directory on the OpsCenter server: For Windows: <INSTALL_PATH>\server\db\upgrade\data For Solaris: <INSTALL_PATH>/SYMCOpsCenterServer/db/upgrade/data
Upgrade to OpsCenter server again. See Upgrading from Veritas Backup Reporter to OpsCenter Analytics on Windows and UNIX on page 108.
Monitoring data migration from NOM to Symantec OpsCenter

When you upgrade from NOM to OpsCenter server, the OpsCenter Installation Wizard automatically detects an older NOM installation. The OpsCenter installer only stops the existing NOM services. It does not uninstall your existing NOM installation. You can manually uninstall NOM after successfully migrating data and using Symantec OpsCenter for some time. During upgrade, the OpsCenter server is installed, the older NOM database is saved and started. Data migration from the older NOM database to the new OpsCenter database starts once the Symantec OpsCenter Server Service is started while installing OpsCenter server. The data migration process may take time depending on the volume of data that has to be migrated. The following sections describe the data migration process from NOM to Symantec OpsCenter in detail.
About upgrading the NOM database to Symantec OpsCenter

The data migration from the NOM database to the Symantec OpsCenter database starts once the Symantec OpsCenter Server Service is started while installing OpsCenter 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.4 database. 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 the OpsCenter database.
121
The data migration from NOM 6.5.4 to the OpsCenter database occurs in three stages. In the first stage, data that is specific to NOM is migrated to the OpsCenter database. The NOM data comprises of alerts, alert policies, users, domains, server groups etc. Note: You must create new alert policies in OpsCenter only after alert migration is complete. Table 2-8 gives details about the NOM data that is migrated and how it appears in OpsCenter. Table 2-8 NOM data migration Data in OpsCenter
Metadata about the managed master servers from NOM is migrated to OpsCenter. Once this data has been migrated to OpsCenter, you can view this data from Settings > Configuration > NetBackup page in the OpsCenter console. User information and domains The NOM users take the following user roles in OpsCenter: The admin user in NOM is the Security Administrator in Symantec OpsCenter. A normal NOM user is the Administrator in OpsCenter. A read-only NOM user is the Operator in OpsCenter.
NOM data that is migrated

Master server metadata
The NOM admin user of NOM_BuiltIn@hostname domain must log on to OpsCenter using the OpsCenterUsers(vx) domain. Users of other NOM domains can continue using their respective domains in OpsCenter. Once this data has been migrated to OpsCenter, you can view this data from the Settings > Users page in the OpsCenter console.
122
Table 2-8
NOM data migration (continued) Data in OpsCenter

All recipients and recipient groups are migrated from NOM to OpsCenter. Once the recipients have been migrated to OpsCenter, you can view this data from the Settings > Recipients page (both Email and SNMP subtabs) in the OpsCenter console.

Email and trap recipients
Note: Recipient groups are not supported

in OpsCenter. Even though recipient groups are migrated to the OpsCenter database, the OpsCenter console does not display recipient groups. Public and Private Groups The main (root) server, policy, or client node is mapped to the ALL MASTER SERVERS view. For each NOM user, three trees are created - PrivateTree_Server, PrivateTree_Client, and PrivateTree_Policy trees. The OpsCenter console displays all views in the drop-down list of the View Pane. Public and Private groups are migrated as nodes. A small group of master servers, policies, or clients are nodes in OpsCenter. A single host, policy, or client is an object in the View Pane.
123
Table 2-8

Saved Reports
124
Table 2-8

The following reports (and the schedules that are created for these reports) from NOM are 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 are migrated as dashboard reports. Once these reports have been migrated, you can view them from Reports > My Dashboard in the OpsCenter console. User-created reports in NOM (both Public and Private) are migrated as custom SQL queries. If you edit these reports in OpsCenter, you can directly edit SQL queries for these reports.
Note: To edit custom SQL reports in

OpsCenter, you must have a licensed version of OpsCenter (OpsCenter Analytics). All private graphical reports in NOM become tabular in OpsCenter. The concept of saving a report in NOM is different than OpsCenter. User must provide values for all the filters like Client Name, Policy Name etc. before you save a report in OpsCenter. In NOM, a user provides values for filters while running a report. Hence after migration is complete, these reports get default values for filters in OpsCenter. For example if you migrate a Skipped Files details for client report for a specific client like nom-ut6 from NOM, then in OpsCenter
125
Table 2-8

the report is configured to run on all the clients (instead of only nom-ut6). The WHERE clause of the OpsCenter SQL query has "IS NOT NULL" value. Shortcuts to reports are not migrated. Shortcuts to reports are not supported in OpsCenter. You need to manually configure My Portal again using OpsCenter reports.
Alert Policies and alerts
All alert policies and alerts are migrated from NOM to OpsCenter. You must create new alert policies in OpsCenter only after alert migration is complete. To see if alert policies have been migrated, see the Data Migration Status page. See Viewing the data migration status on page 128.
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
126
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 master server is enabled automatically. The status for the specific master server is shown as 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 the Monitor and Manage tabs of the OpsCenter console. Note: If data collection for a master server was disabled in NOM, then data collection for the specific master server remains disabled after you upgrade to OpsCenter. In such a case, data collection is not enabled automatically after migration. See Viewing the data migration status on page 128. In the third stage of data migration, the following data is migrated:
Jobs older than 30 days Jobs data older than 30 days is migrated for each master server.
127
Report Schedules
The concept of report schedules is different in NOM and OpsCenter. While creating schedule for a report in OpsCenter, you only need to specify the schedule details like time etc. However when you create a schedule in NOM, you provide the schedule details as well as filter values. The following steps are performed in the specified sequence to migrate scheduled reports from NOM to OpsCenter: The schedule is saved separately in the OpsCenter database The report filter values are inserted in the report definition The report is saved again.
In case a standard report is scheduled in NOM, the report is first saved under Reports > My Reports and then the schedule is attached to it. For example, if a standard report like Available Media is scheduled in NOM, then the standard report is saved in OpsCenter under Reports>MyReports view and the schedule is then attached to this report.
Note: Reports that come with NOM and are

composite reports (containing more than one report). Schedules for composite reports are not migrated. Example, Full Media Capacity, Restore Job Summary etc.
You can work in the OpsCenter console while this data is migrated in the background. Note: All NOM user preferences like column settings, SORD value etc. are not migrated to OpsCenter.
What happens when data migration is interrupted

Data 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:
128
For NOM versions less than 6.5.4, the database is first upgraded to NOM 6.5.4 database. 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 the OpsCenter database.
Based on the upgrade scenarios, the data migration process can either be interrupted when upgrade to NOM 6.5.4 database is in progress (this happens when a NOM version less than 6.5.4 is being upgraded to OpsCenter) or when upgrade from NOM 6.5.4 database to the OpsCenter database is in progress. Table 2-9 explains the specific scenarios and what happens when data migration is interrupted in these scenarios. Table 2-9 Scenario What happens when data migration is interrupted Migration status
Data migration is interrupted when a NOM In this case, data migration automatically database (NOM version lower than 6.5.4) is restarts from the beginning. being upgraded to the NOM 6.5.4 database. Data migration is interrupted when data is In this case, data migration resumes from migrated from NOM 6.5.4 to the OpsCenter the last checkpoint automatically. The data database. that had already been migrated does not need to be migrated again.
Note: The data migration for the following

entities does not resume from the last checkpoint and needs to be migrated again - Recipient, User, Reports, Groups, Robot, Services, DSM, License feature history, report schedules, and alert policy.
Viewing the data migration status

You can also view the data migration status using the OpsCenter console. To view the data migration status
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 address of the OpsCenter Server host.
129
Note: By default, OpsCenter tries to run on port 80 (HTTP). If port 80 is not available, OpsCenter can use a different port. To know the HTTP and HTTPS port that OpsCenter uses, run the configurePorts utility. Run
INSTALL_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 use http://<server-host>:8181/opscenter/dbUpgradeStatus.do. You can also use the URL that is presented at the end of the OpsCenter server installation and append /dbUpgradeStatus.do after the URL to access the data migration page at any point in time.
On the OpsCenter logon page, use the Click here to see migration status link as shown in the following figure. The link is located at the bottom of the 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:
130
The data migration status comprises Entity Migration Status and Master Server Entity Migration Status. The Entity Migration Status tab shows the following columns (along with the migration summary):
Entity Displays the name of the database entity, like master server , Alert Policy, Policy data (number of records) that are being migrated to OpsCenter. The total number of records of an entity that need to be migrated from NOM to Symantec OpsCenter.
Total Records
131
Migrated Records
Number of records of an entity that have been migrated to Symantec OpsCenter, as of now
Note: Migrated records are the number of

rows in tables. This does not necessarily mean that these many records for the specific entity will be shown on the OpsCenter console. For example, the migrated records for policies include policies as well as policy versions that are associated with it. Also the number of migrated recipients includes recipients as well as recipient groups. However, recipient groups are not shown on the OpsCenter console as they are not supported by OpsCenter. Skipped Records The number of records that were skipped during data migration because of the following possible reasons: The data was in an inconsistent state during upgrade. Such records are collected once the OpsCenter server starts. NOM data that is not migrated is also shown as Skipped Records. For example, NOM standard reports like Cycle Dashboard and also schedules for such standard reports (if any) are shown as skipped records.
Click the Master Server Entity Migration Status tab to view the details of entities that are migrated per master server. This is shown in the following figure:
132
This page shows the number of records that have been migrated for each master server. It also shows the time that is required for migrating those many records. The Entity Migration Status tab shows the following columns (in addition to the migration summary):
Server Name Displays the name of the master server that is being migrated to OpsCenter.
133
Status
The migration status for the respective master server. The following migration status is possible for a master server: Not Started: Data Migration has not started for this master server In Progress:: Entities for this master server are being migrated from NOM to OpsCenter Last 30 Days Jobs Migrated: This means that the second stage of data migration is complete for the specific master server. This status indicates that entities like policies, media, and jobs for the last 30 days have been migrated to OpsCenter and data collection in OpsCenter has been enabled for the selected master server. Because data collection has been enabled, the OpsCenter server starts collecting fresh data from the specific master server. You can start using the Monitor and Manage views of the OpsCenter console at this point.
Note: If data collection for a master server

was disabled in NOM, then data collection for the specific master server remains disabled after migration. Completed: Entities for this master server have been migrated from NOM to OpsCenter Failed: Entities for this master server cannot be migrated from NOM to OpsCenter. Total Records The total number of records for each master server that need to be migrated from NOM to Symantec OpsCenter.
134
Migrated Records
Number of records for each master server that have been migrated to Symantec OpsCenter, as of now

rows in tables. This does not necessarily mean that these many records for the specific entity will be shown on the OpsCenter console. For example, the migrated records for policies include policies as well as policy versions that are associated with it. Also the number of migrated recipients includes recipients as well as recipient groups. However, recipient groups are not shown on the OpsCenter console as OpsCenter does not support recipient groups. Skipped Records Number of records for each master server that were skipped during data migration because of the following possible reasons: The data was in an inconsistent state during upgrade. Such records are collected once the OpsCenter server starts. NOM data that is not migrated is also shown as Skipped Records. For example, NOM standard reports like Cycle Dashboard and also schedules for such standard reports (if any) are shown as skipped records.
Monitoring data migration from VBR to Symantec OpsCenter Analytics

When you upgrade from VBR to OpsCenter Analytics, the OpsCenter Installation Wizard automatically detects an older VBR installation. The OpsCenter installer only stops the existing VBR services. It does not uninstall your existing VBR installation. You can manually uninstall VBR after successfully migrating data and using Symantec OpsCenter for some time. During upgrade, the OpsCenter server is installed and the older VBR database is saved and started. The data migration from the older VBR database to the new OpsCenter database starts once the Symantec OpsCenter Server Service is started while installing OpsCenter server.
135
The data migration process may take time depending on the amount of data that has to be migrated. The following sections describe the data migration process from VBR to OpsCenter Analytics.
About upgrading the VBR database to Symantec OpsCenter Analytics

The data migration from the VBR database to the Symantec OpsCenter database starts once the Symantec OpsCenter Server Service is started while installing OpsCenter 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 the VBR 6.6 database. The VBR 6.6 database is then upgraded to the OpsCenter database. For VBR 6.6 and later versions, the database is upgraded directly to the OpsCenter database.
The data migration from VBR 6.6 to the OpsCenter database occurs in the following stages:
First stage in which VBR metadata and backup data is migrated from VBR to the 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 of entities 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 data is migrated. Third stage in which backup data older than 30 days (for NetBackup, Backup Exec, PureDisk, TSM, Legato Networker) is migrated from VBR to OpsCenter for each master server.
Table 2-10 gives details about the VBR metadata that is migrated in the first stage and how it appears in OpsCenter.
136
Table 2-10
VBR metadata migration in the first stage Data in OpsCenter

The Agents and data collectors that you have configured in VBR are migrated to OpsCenter. Once this data has been migrated to OpsCenter, the NetBackup agents and NetBackup data collectors can be viewed from Settings > Configuration > NetBackup in the OpsCenter console. The agents and data collectors for all products other than NetBackup can be viewed from Settings > Configuration > Agents in the OpsCenter console.
VBR data that is migrated

Agent and Data Collectors
Objects
Data related to master servers, media servers, clients, file systems, and EV archive-related information like vault server , Exchange Server is migrated to OpsCenter.
Note: Only those master servers, media

servers, and clients that have job data are migrated to OpsCenter.
137
Table 2-10
VBR metadata migration in the first stage (continued) Data in OpsCenter

The VBR users take the following user roles in OpsCenter: The Administrator in VBR is the Security Administrator in Symantec OpsCenter. A read-only VBR Administrator is the Analyst in OpsCenter. A normal VBR user is the Reporter in OpsCenter.

User information and domains
The users on the cc_users@hostname domain can continue using the same domain in OpsCenter. Users of other domains can also continue using their respective domains.
Note: Only the VBR default user

(admin@cc_users) must log on using OpsCenterUsers (vx) domain. All settings of the default admin user are now associated with the admin user of OpsCenterUsers(vx) domain. Once this data has been migrated to OpsCenter, you can view this data from the Settings > Users page in the OpsCenter console. Email and trap recipients All recipients and recipient groups are migrated from VBR to OpsCenter. Once this data has been migrated to OpsCenter, you can view this data from the Settings > Recipients page (both Email and SNMP subtabs) in the OpsCenter console.
Note: Recipient groups are not supported

in OpsCenter. Even though recipient groups are migrated to the OpsCenter database, the recipient groups are not displayed in the OpsCenter console. Views All views from VBR are migrated to OpsCenter as client-type views. Once this data has been migrated to OpsCenter, you can see these views in the View Pane of the OpsCenter console.
138
Table 2-10
VBR metadata migration in the first stage (continued) Data in OpsCenter

You must create new alert policies in OpsCenter only after alert policy migration is complete. To see if alert policies have been migrated, see the Data Migration Status page. See Viewing the data migration status on page 142.

Alert Policies
Note: Alerts from VBR are not migrated to

OpsCenter.
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 Media Media 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 to the OpsCenter database for each master server, data collection for each master server is enabled automatically. The status for the specific master server is shown as 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 the Monitor,Manage, and Reports tabs of the OpsCenter console. Note: If data collection for a master server was disabled in VBR, then data collection for the specific master server remains disabled after upgrading to OpsCenter Analytics. In such a case, data collection is not enabled automatically after migration.
139
After the first stage of data migration is complete, the second stage of data migration begins. In the second stage of data migration, Symantec Enterprise Vault archive data is migrated followed by report data. The following data is migrated as Symantec Enterprise Vault archive data in the second 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 second stage. Table 2-11 gives details about the report data that is migrated and how it appears in OpsCenter.
140
Table 2-11
VBR report data migration in the second stage Data in OpsCenter Analytics
After migration is complete, you can view the My Backup Reports folder under Private Reports tree. Earlier in VBR, the My Backup Reports folder was under My Saved Reports folder. Custom SQL and Stored Custom SQL reports are not migrated to Symantec OpsCenter. The following VBR reports are not migrated to OpsCenter:


Reports
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
Chargeback variables and formulas
All VBR chargeback variables and formulae are migrated to OpsCenter. Once this data has been migrated, the chargeback variables and formulae can be viewed from Settings > Chargeback view in the OpsCenter console.
Report schedules
All report schedules are migrated from VBR to OpsCenter.
After the second stage of data migration is complete, the third stage of data migration begins. In the third stage of data migration, the backup data that remains to be migrated in the first stage (data older than 30 days) is migrated for each master server. The following data is migrated in the third stage for each master server:
Media History (Older than 30 days)
141
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, you need to configure the following after data migration is complete:
SMTP server settings. The VBR SMTP server settings are not migrated to OpsCenter.
What happens when data migration is interrupted

Data migration can be interrupted due to many reasons, like network issues, accidental shutdown of OpsCenter server, stopping services on the OpsCenter server 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 the VBR 6.6 database. The VBR 6.6 database is then upgraded to the OpsCenter database. For VBR 6.6 and later versions, the database is upgraded directly to the OpsCenter database.
Based on the upgrade scenarios, the data migration process can either be interrupted when upgrade to VBR 6.6 database is in progress (this happens when a VBR version less than 6.6 is upgraded to OpsCenter Analytics) or when upgrade from VBR 6.6 database to the OpsCenter database is in progress. Table 2-9 explains the specific scenarios and what happens when data migration is interrupted in these scenarios. Table 2-12 Scenario
Data migration is interrupted when a VBR database (VBR version lower than 6.6) is being upgraded to the VBR 6.6 database.
What happens when data migration is interrupted Migration status

In this case, data migration automatically restarts from the beginning.
142
Table 2-12 Scenario
What happens when data migration is interrupted (continued) Migration status

In this case, data migration resumes from the last checkpoint automatically. The data that had already been migrated does not need to be migrated again.
Data migration is interrupted when data is being migrated from VBR 6.6 to the OpsCenter database.
Note: The data migration for the following

entities does not resume from the last checkpoint and is migrated again - list of clients and file systems, reports.
Viewing the data migration status

You can also view the data migration status using the OpsCenter console. To view the data migration status
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 address of the OpsCenter Server host. Note: By default, OpsCenter tries to run on port 80 (HTTP). If port 80 is not available, OpsCenter can use a different port. To know the HTTP and HTTPS port that OpsCenter uses, run the configurePorts utility. Run
INSTALL_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 use http://<host.domain>:8181/opscenter/dbUpgradeStatus.do to access the data migration page at any point in time. You can also use the URL that is presented at the end of the OpsCenter server installation and append /dbUpgradeStatus.do after the URL to access the data migration page at any point in time.
On the OpsCenter logon page, use the Click here to see migration status link as shown in the following figure. The link is located at the bottom of the logon page on the right-hand side. This link automatically disappears when the data migration is complete.
143
The data migration status is displayed as shown in the following figure:
144
The data migration status contains Entity Migration Status and Master Server Entity Migration Status tabs. The Entity Migration Status tab shows the following columns (along with the migration summary):
Entity Displays the name of the database entity, such as Alert Policy, Policy, Disk Pool, Jobs etc. that is being migrated to OpsCenter Analytics. The total number of records of an entity that need to be migrated from VBR to Symantec OpsCenter Analytics.
Total Records
145
Migrated Records
Number of records of an entity that have been migrated to Symantec OpsCenter, as of now

rows in tables. This does not necessarily mean that these many records for the specific entity will be shown on the OpsCenter console. For example, the migrated records for policies include policies as well as policy versions that are associated with it. Also the number of migrated recipients includes recipients as well as recipient groups. However, recipient groups are not shown on the OpsCenter console as they are not supported in OpsCenter. Skipped Records Number of the records that were skipped during data migration because of the following possible reason: The data was in an inconsistent state during upgrade. Such records are collected once the OpsCenter server starts (if they are present in the NetBackup host) . VBR data that is not migrated is also shown as Skipped Records. For example, VBR alerts are shown as skipped records.
Click the Master Server Entity Migration Status tab to view the details of entities that are migrated for each master server. The following figure shows a sample view of the Master Server Entity Migration Status tab:
146
This page shows the number of records that have been migrated for each master server. It also shows the time that is required for migrating those many records. The Entity Migration Status tab shows the following columns (along with migration summary):
Server Name Displays the name of the database entity, such as master server , Alert Policy, Policy data (number of records) that has been migrated to OpsCenter.
147
Status
The migration status for the respective master server. The following migration status are possible for a master server: Not Started: The data migration process for the master server has not started. In Progress: Entities for this master server are being migrated from VBR to OpsCenter Analytics. Last 30 Days Jobs Migrated: This means that the first stage of data migration is complete for the specific master server. This status indicates that entities like policies, media, and jobs for the last 30 days have been migrated to OpsCenter Analytics and data collection in OpsCenter Analytics has been enabled for the selected master server. Because data collection has been enabled, the OpsCenter server starts collecting fresh data from the specific master server. You can start using the Monitor and Manage views of the OpsCenter Analytics console at this point.
Note: If data collection for a master server

was disabled in VBR, then data collection for the specific master server remains disabled after migration. Completed: Entities for this master server have been migrated from VBR to OpsCenter Analytics Failed: Entities for this master server cannot be migrated from VBR to OpsCenter Analytics. Total Records The total number of records for each master server that need to be migrated to Symantec OpsCenter Analytics from VBR.
148
Migrated Records
Number of records for each master server that have been migrated to Symantec OpsCenter, as of now

rows in tables. This does not necessarily mean that these many records for the specific entity will be shown on the OpsCenter console. For example, the migrated records for policies include policies as well as policy versions associated with it. Also the number of migrated recipients includes recipients as well as recipient groups. However, recipient groups are not shown on the OpsCenter console as OpsCenter does not support recipient groups. Skipped Records Number of records for each master server that were skipped during data migration because of the following possible reasons: The data was in an inconsistent state during upgrade. Such records are collected once the OpsCenter server starts (if they are present in the NetBackup host). VBR data that is not migrated is also shown as Skipped Records. For example, VBR alerts are shown as skipped records.
Upgrading to OpsCenter Server on a different UNIX system

This section explains how you can upgrade from NOM or VBR to OpsCenter server software on a different UNIX system. An example scenario is when NOM or VBR is running on Solaris 8 and you require the same data with OpsCenter on Solaris 10. Note: 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 a Windows platform to Solaris 10.
Note: Manual upgrades are not supported for Windows platforms.
149
Use the following procedure to upgrade to OpsCenter server software on a different UNIX 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 149. Copy this data from the old server to the server where you plan to install OpsCenter server. Install the OpsCenter server software and restore the NOM or VBR data using the OpsCenter installer. See Upgrading to OpsCenter server on the new system on page 150.
Backing up your data on the NOM or VBR server

Use the following procedure to back up your database and configuration files on the NOM or VBR server. To back up the NOM or VBR database
1 2
Go to the NOM or VBR server and log on as root. Mount the appropriate OpsCenter product DVD for the platform on which you are installing OpsCenter software. You may install 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.
If you use the OpsCenter DVD, go to the appropriate OpsCenter platform directory and then the Server directory. If you use the NetBackup media kit, go to the following directory:
cd OpsCenter/Server
150
Run Backup.sh script. This script backs up the NOM or VBR database and configuration files on this system.
./Backup.sh
The script detects that you have NOM or VBR installed and prompts you for the 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 location and press Enter. To back up the <product> data in the default directory (/var/symantec), press Enter. A directory that is named OpsCenter_save is created in the backup location that you specify.
Upgrading to OpsCenter server on the new system

Use the following procedure to install OpsCenter server and restore the old VBR or NOM data on the new system. To upgrade to OpsCenter server on the new system
1 2 3
Log on as root on the server where you want to install OpsCenter. Copy the backed up NOM or VBR data (OpsCenter_save folder) from the older NOM or VBR server to this server. Mount the OpsCenter product DVD for the appropriate platform on which you are installing. You may install 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.
If you use the OpsCenter DVD to install OpsCenter server software, navigate to the appropriate OpsCenter platform directory and then the Server directory on the DVD. If you use the NetBackup media kit to install OpsCenter, navigate to the Server directory.
151
cd OpsCenter/Server
5 6 7
Type the following command:./installOpsCenterServer. Press Enter. The Welcome message is displayed. Press Enter to continue. The installer then checks if OpsCenter Server is installed on the system or not. It prompts you in case OpsCenter is already installed. The installer also examines the system for existing packages. The installer displays a list of components that get installed like PBX, AT, Symantec WebGUI Server, Symantec Database etc. Review this list and press Enter to continue. The installer prompts you with the following question:
10 Type y to confirm the directory path and press Enter.
152
11 OpsCenter server is installed on the system.

Type a directory path under which to install the OpsCenter database and press Enter. If you create an alternate database directory, the script creates the folder OpsCenterServer below your directory. To accept the default database installation directory (/var/Symantec), press Enter without typing a directory path. In case the database installation directory (/var/symantec) does not exist on the 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

To use the database installation directory for database server temporary space, 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 press Enter.

Installing Symantec OpsCenter Post-installation tasks
153
15 Once the configuration changes are completed, you are prompted with the
following 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 press Enter.
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 any other port that is available and press Enter.
18 You are prompted for license information. Depending on whether older license
keys are detected or not, the installer may prompt you with the following:
Enter a valid demo or permanent key that you have received with the purchase of OpsCenter Analytics and press Enter. If you do not enter a key, you get an unlicensed version. With the unlicensed version, you cannot access the licensed features. See About the license keys on page 70. You can also add the license keys later from the OpsCenter console. See Managing licenses on page 226.
Post-installation tasks
The following sections explain how to start using OpsCenter and includes some performance tuning tips for OpsCenter.
154
Verifying that Symantec OpsCenter is running properly

After installing Symantec OpsCenter on either Windows or UNIX, perform a check to verify that OpsCenter is running properly. To verify that OpsCenter is running properly
Use the URL that is presented at the end of the OpsCenter Server installation to 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 not available, OpsCenter can use a different port. To know the HTTP and HTTPS port that OpsCenter uses, run the configurePorts utility. Run
INSTALL_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 use http://<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.
Logon as admin (user name) /password (password) on the private domain: OpsCenterUsers(vx)
About starting to use OpsCenter

After you complete the OpsCenter installation, you are ready to start using the OpsCenter console. Table 2-13 lists the common tasks in OpsCenter and contains links to the corresponding topics and descriptions. Table 2-13 Task Topic Links to get you started with OpsCenter Topic Description
This topic provides instructions on how to access the console and log on, and provides solutions to possible issues.
To access and log on to the See About accessing the OpsCenter console. OpsCenter console on page 34.
155
Table 2-13 Task

To change the password for the administrator logon.
Links to get you started with OpsCenter (continued) Topic Description

For administrator initial logon, the user name is admin and the password is password if you have chosen to keep the default password during installation. After initial logon, it is recommended that you change the user name and password. This topic provides an overview of the console components.
Topic
See Changing your password on page 225.
To learn about the OpsCenter console components.
See About OpsCenter console components on page 47.
To learn more about using See About using the OpsCenter For instructions on understanding and using the the OpsCenter console. console on page 32. various OpsCenter monitoring, managing, reporting, and settings views and related tasks, use the OpsCenter online Help .
About the start-up tasks that OpsCenter performs

OpsCenter 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 broker requires. If these security domains are present, OpsCenter uses them. The following domains namely OpsCenterUsers, OpsCenterServices, and NOM_MACHINES are created when OpsCenter server is installed. Creates the OpsCenter admin user in the OpsCenterUsers domain with the default password as 'password'.
Tuning OpsCenter for more performance

The following settings can be tuned to improve OpsCenter performance.
Adjusting the heap size for OpsCenter components

Use the following procedures to adjust the heap size for OpsCenter components.
Adjusting the default heap size for the OpsCenter server

If the OpsCenter server processes are consuming a lot of memory (which may happen with large OpsCenter configurations), it may be helpful to increase the OpsCenter Server heap size. The OpsCenter Server default heap size can be increased from 1024 MB up to 1400 MB for 32-bit platforms. The OpsCenter Server
156
default heap size can be increased from 1024 MB up to 2048 MB for 64-bit platforms. To adjust the heap size on Windows servers
Open OpsCenterServerService.xml file from the following location on the OpsCenter server:
INSTALL_PATH\OpsCenter\server\bin
Modify the Xmx1024m value in the following string.

<CmdArg value="-Xmx1024M
For example, replace -Xmx1024M with -Xmx1400M to increase the maximum heap size from 1024 MB to 1400 MB.
3 4
Save the OpsCenterServerService.xml file. 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 server services as follows:
INSTALL_PATH\OpsCenter\server\bin\opsadmin.bat stop INSTALL_PATH\OpsCenter\server\bin\opsadmin.bat start
To adjust the heap size on UNIX servers
Open startserver file from the following location:

/opt/SYMCOpsCenterServer/bin
Modify the Xmx1024M value in the following string.

MAX_HEAP=-Xmx1024M
For example, replace -Xmx1024 with -Xmx1400 to increase the maximum heap size from 1024 MB to 1400 MB.
3 4
Save the startserver file. 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 server processes as follows:
/opt/SYMCOpsCenterServer/bin/opsadmin.sh stop /opt/SYMCOpsCenterServer/bin/opsadmin.sh start
157
Adjusting the default heap size for the Symantec OpsCenter Web server
The OpsCenter Web server default heap size can be increased from 1024 MB up to 1400 MB for 32-bit platforms. The OpsCenter Web server default heap size can be increased from 1024 MB up to 2048 MB for 64-bit platforms. Note: If you start seeing poor performance in the OpsCenter console every few days and restarting the Symantec OpsCenter Web server service fixes the problem, you should increase the Web server default. To adjust the heap size on Windows servers
Open OpsCenterGUIService.xml file from the following location on the OpsCenter server:
INSTALL_PATH\OpsCenter\gui\bin\OpsCenterGUIService.xml

<EnvVar name="JAVA_OPTS" value="-Xms512m -Xmx1024m
For example, replace -Xmx1024m with -Xmx1400m to increase the maximum heap size from 1024 MB to 1400 MB.
3 4
Save the OpsCenterGUIService.xml file. 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 server services as follows:
Open startGUI file from the following location:

/opt/SYMCOpsCenterGUI/bin

JAVA_OPTS="-d64 -Xms512M -Xmx1024m...
158
3 4
Save the startGUI file. 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 server processes as follows:
Adjusting the default heap size for the OpsCenter Agent

If the OpsCenter Agent processes are consuming a lot of memory (which may happen with large OpsCenter configurations), it may be helpful to increase the OpsCenter Agent heap size. The OpsCenter Agent default heap size can be increased from 1024 MB up to 1400 MB for 32-bit platforms. The OpsCenter Agent default heap size can be increased from 1024 MB up to 2048 MB for 64-bit platforms. To adjust the heap size on Windows servers
Open OpsCenterAgentService.xml file from the following location on the OpsCenter server:
INSTALL_PATH\OpsCenter\Agent\bin

<CmdArg value="-Xmx1024M
For example, replace -Xmx1024M with -Xmx1400M to increase the maximum heap size from 1024 MB to 1400 MB.
3 4
Save the OpsCenterAgentService.xml file. You must restart the OpsCenter Agent service for the changes to be effective. To do this, first stop and then start the Symantec OpsCenter Agent Service. Select Control Panel > Administrative Tools > Services and stop the Symantec OpsCenter Agent Service.
Select Control Panel > Administrative Tools > Services and start the Symantec OpsCenter Agent Service.
159
Open startagent file from the following location:

/opt/SYMCOpsCenterAgent/bin
Modify the Xmx1024M value in the following string.

MAX_HEAP=-Xmx1024M
3 4
Save the startagent file. You must restart the OpsCenter Agent process for the changes to be effective. Enter the following commands to first stop and then start OpsCenter agent process as follows:
/opt/SYMCOpsCenterAgent/bin/stopagent /opt/SYMCOpsCenterAgent/bin/startagent
Adjusting cache size of the OpsCenter database

The amount of memory available for database server cache is an important factor controlling OpsCenter performance. Symantec recommends that you adjust the Sybase cache size after installing OpsCenter. After you install OpsCenter, the database size can grow rapidly as you add more master servers. Sybase automatically adjusts the cache size for optimum performance. You can also set the cache size using the -c server option.
160
To set the cache size using the -c server option on Windows servers
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 the content 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.
Stop and restart the OpsCenter services, as follows:

161
To set the cache size using the -c server option on UNIX servers
Open the /opt/SYMCOpsCenterServer/db/conf/server.conffile and change the value of the -c option. For example, you can increase the Sybase cache size to 512 MB by changing the 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 the server.conf file to increase the cache size to 512 MB. In the same manner, to increase 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 minimum cache size respectively. The -cs option logs the cache size changes for the database server.
2 3
Save the server.conf file. Stop and restart the OpsCenter processes, as follows:
Purge data periodically

You should purge the OpsCenter data periodically. See Configuring data purge settings on page 227. The OpsCenter database should be defragmented after a purge operation. See Defragmenting the OpsCenter database on page 194.
162
Installing Symantec OpsCenter Using an earlier NOM or VBR installation after upgrade
OpsCenter performance and floating-point calculations

Symantec OpsCenter performs certain calculations that require floating-point math. If the server's processor does not have a dedicated floating-point unit, the calculations are handled in floating-point emulation. Note: Emulation mode slows down OpsCenter's performance. Symantec does not recommend running OpsCenter on any server that lacks a dedicated floating-point unit.
Using an earlier NOM or VBR installation after upgrade

It is possible to revert back to using your older NOM or VBR software even after you have upgraded to OpsCenter server. When you upgrade from NOM or VBR to OpsCenter server, the OpsCenter installer only stops the existing NOM or VBR services. It does not uninstall your existing NOM or VBR installation. If you have not uninstalled NOM or VBR, you can use your older installation. In case you have not uninstalled NOM or VBR and want to use your existing NOM or VBR software, use the following procedure. To start using NOM or VBR on Windows
1 2
Log on to the OpsCenter server as an Administrator. Uninstall OpsCenter server software. See Uninstalling Symantec OpsCenter on Windows on page 163.
Select Control Panel > Administrative Tools > Services and use the Windows Service Control Manager (SCM) to change the startup type of all NOM or VBR services to Automatic. Start all NOM or VBR services by entering the following command:
NOM <INSTALL_PATH>\NetBackup Operations Manager\bin\admincmd\NOMAdmin -start_service <INSTALL_PATH>\Tools\cscript vx_services_start.vbs
VBR
Log on to the NOM or VBR console.
Installing Symantec OpsCenter Uninstalling Symantec OpsCenter on Windows and UNIX
163
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 shipped with your NOM version. See the NOM documentation for more information. To start using NOM or VBR on UNIX
1 2
Log on to the OpsCenter server as root. Uninstall OpsCenter server software. See Uninstalling Symantec OpsCenter on UNIX on page 164.
Enter the following command to start all NOM or VBR processes:

NOM VBR /<INSTALL_PATH>/VRTSnom/bin/NOMAdmin -start_service /<INSTALL_PATH>/VRTSccsvs/bin/vbrserver start
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 shipped with your NOM version. See the NOM documentation for more information.
Uninstalling Symantec OpsCenter on Windows and UNIX

This section describes uninstallation procedures for OpsCenter on Windows and UNIX.
Uninstalling Symantec OpsCenter on Windows

Use the Windows Add/Remove Programs utility to uninstall OpsCenter on a Windows host. Note: Before uninstalling OpsCenter components, ensure that NetBackup-Windows GUI is not running. Close any NetBackup-Windows GUI consoles that are open before uninstalling OpsCenter components. To uninstall Symantec OpsCenter Server on Windows
1 2
Log on to the target host as a user with administrator privileges. In the Windows Control Panel, click Add/Remove Programs.
164
3 4
Click Symantec OpsCenter Server and click Remove. Click Next to continue and remove Symantec OpsCenter Server from your computer.
To uninstall Symantec OpsCenter Agent on Windows
1 2 3 4
Log on to the target host as a user with administrator privileges. In the Windows Control Panel, click Add/Remove Programs. Click Symantec OpsCenter Agent and click Remove. Click Next to continue and remove Symantec OpsCenter Agent from your computer.
To uninstall Symantec OpsCenter View Builder on Windows
1 2 3 4
Log on to the target host as a user with administrator privileges. In the Windows Control Panel, click Add/Remove Programs. Click Symantec OpsCenter View Builder and click Remove. Click Next to continue and remove Symantec OpsCenter View Builder from your computer.
Uninstalling Symantec OpsCenter on UNIX

Use the Uninstall Script, which resides in the root directory of the product DVD and also in INSTALL_PATH/VRTS/install directory, to uninstall OpsCenter on a UNIX host. Note: If you want to reinstall OpsCenter components, use the product DVD. You cannot reinstall OpsCenter components using the install scripts in the INSTALL_PATH/VRTS/install directory. To uninstall OpsCenter Server on UNIX
1 2
Open a UNIX console and log in as root on the target host. Change to the following directory:
INSTALL_PATH/VRTS/install
165
Type the following command and press Enter:

./uninstallopscenterserver
The Uninstall Script checks the components installed on the system. When you upgrade from VBR server to the OpsCenter server and then uninstall 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 not the OpsCenter uninstaller) must be used to remove the VRTSccsvs package.
When asked to confirm if you want to uninstall OpsCenter Server, do one of the following:
Type y and press Enter to start the uninstall process. The Uninstall Script stops all processes and then uninstalls the component packages. When the uninstall is complete, it displays a summary of the uninstall, including the location of the uninstall log files.
Type n and press Enter to cancel the uninstall procedure.
To uninstall OpsCenter Agent on UNIX
1 2
Open a UNIX console and log in as root on the target host. Change to the following directory:
/opt/VRTS/install

./uninstallopscenteragent
The Uninstall Script checks the components installed on the system.
When asked to confirm if you want to uninstall OpsCenter Agent, do one of the following:
166
Installing Symantec OpsCenter Clustering Symantec OpsCenter
Clustering Symantec OpsCenter

About a Symantec OpsCenter cluster
Clusters 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 nodes in a cluster are constantly aware of the status of resources on the other nodes. If a node becomes unavailable, resources running on that node migrate to an available node. Symantec OpsCenter (OpsCenter) operates in an active or passive failover configuration. OpsCenter Server must be installed on the active node and the passive (or failover nodes). When a failover occurs in a OpsCenter cluster, OpsCenter is shut down on the active node and starts on one of the failover nodes in the cluster. During failover, users experience only a short interruption in service. This failover provides high availability for OpsCenter. You can cluster only the OpsCenter Server. Installing OpsCenter in a clustered environment makes OpsCenter a highly available application.
Supported cluster solutions

For Symantec OpsCenter to be clustered, you must have Veritas Cluster Server (VCS) installed. Please refer to theSee Table 2-14 on page 166. for supported version of VCS. Table 2-14 Platform
VCS Windows VCS UNIX
OpsCenter cluster support matrix Latest supported version Start of support

5.1 5.0 4.1 4.1
VCS is a high-availability solution for cluster configurations. With VCS you can monitor systems and application services, and restart services on a different system 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.
167
Clustering Symantec OpsCenter on Windows

This section provides information about installing Symantec OpsCenter in a clustered mode, on a Windows host. Table 2-15 provides the Windows clustering steps. Table 2-15 Step
1
OpsCenter clustering steps Description

Understand the limitations of an OpsCenter cluster
Reference topic
See Limitations of Symantec OpsCenter cluster on Windows on page 167. See Prerequisites for Symantec OpsCenter cluster on Windows on page 167. See Installing Symantec Product Authentication Service on Windows on page 168.
Make sure that you have met all prerequisites.
Install OpsCenter 7.0.
Limitations of Symantec OpsCenter cluster on Windows

A OpsCenter cluster has the following limitations:
Only OpsCenter Server can be clustered.OpsCenter Agent and the Symantec OpsCenter View Builder cannot be clustered. Upgrades from previous versions of NOM or VBR to clustered OpsCenter Server is not supported. OpsCenter cluster cannot co-exist with any other Symantec product running in secure mode using the Symantec Product Authentication Service. OpsCenter does not support clustered AT.
Prerequisites for Symantec OpsCenter cluster on Windows

This section contains information about the requirements that must be met before you install and configure OpsCenter in a clustered mode, on a Windows host.
Verify that VCS and OpsCenter support your hardware. For a list of supported storage devices, visit the following Web site: http://entsupport.symantec.com Verify that the supported version of VCS is correctly installed and configured on Solaris. Follow the steps in the Veritas Cluster Server Installation Guide.
168
Verify that no VCS resource group and resource exist with the same name as that which you intend to use for OpsCenter. The SharedDisk must be configured and accessible to all cluster nodes where you want to install OpsCenter. Verify that you have an IP address and host name (virtual name) to be assigned to 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 license key. For a Windows cluster, verify that the cluster disk groups and dynamic volumes for OpsCenter are created on the shared storage. Refer to theVeritas Storage Foundation Administrators 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 admin account. Before installing OpsCenter Server, ensure that Symantec authentication service (AT) Server is installed separately in a non-clustered mode. AT can be installed in Root + AB or AB mode. For more information about installing AT, see the Symanetc Infrastructce Core Services Installation Guide.
Installing Symantec Product Authentication Service on Windows

OpsCenter Server requires that Symantec Product Authentication Service (AT) is installed on a standalone host, before OpsCenter can be clustered. You must install the version of AT Service that is shipped with OpsCenter 7.0. You can either configure AT in root + authentication broker (Root + AB) mode or authentication broker (AB) mode. Symantec recommends that you configure AT in a 'Root+AB' mode. Clustered OpsCenter Server uses this authentication broker. To establish a connection between AT host and OpsCenter Server host, you need to create a principal user on the AT host. Use the credentials of this user when installing OpsCenter Server.
169
Note: Symantec Product Authentication Service is installed when you install Veritas Cluster Server. You must upgrade to the version of authentication service that is shipped with OpsCenter 7.0.
Note: OpsCenter does not support clustered AT.
Note: In case of updates made to AT for OpsCenter 7.0, please refer to the following technote for the latest information: http://entsupport.symantec.com/docs/336967 Symantec Product Authentication Service can be installed in the following ways: To install AT
Logon to the host where you want to install AT. You should not cluster the AT service, as OpsCenter does not support clustered AT.
2 3
You may install AT from the OpsCenter DVD or from the NetBackup media kit.

If autorun is enabled, the Symantec OpsCenter Installation Wizard appears. If autorun is not enabled, click Start > Run. On the Run dialog box, in the Open text box, type D:\Browser.exe and press Enter: Where D is the DVD drive. The Symantec OpsCenter Installation Wizard appears.
4 5 6
On the Symantec OpsCenter Installation Wizard, click the Installation link. Click Symantec Product Authentication Service. Click Next. The VxSSVRTSatSetup.exe is executed. See Symantec Infrstructure Core Services Installation Guide for more information about the VxSSVRTSatSetup.exe.
170
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: %Program
Files%\VERITAS\Security\Authentication
The default location on 64-bit Windows platforms is:

%ProgramFiles(x86)%\VERITAS\Secruity\Authentication
Installing OpsCenter Server on a Windows cluster

To cluster OpsCenter and make it highly available, you must install and configure OpsCenter in a clustered mode. Note: To install OpsCenter Server in clustered mode, first install the OpsCenter Server on the active node and then on the passive nodes. Also, you need to install OpsCenter 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 Windows
On a Windows host where you want to install OpsCenter server, insert the appropriate OpsCenter product DVD in the DVD drive. You may install OpsCenter Server 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.
If autorun is enabled, the Symantec OpsCenter Installation Wizard appears. If autorun is not enabled, click Start > Run. On the Run dialog box, in the Open text box, type D:\Browser.exe and press Enter: Where D is the DVD drive. The Symantec OpsCenter Installation Wizard appears.
On the Symantec OpsCenter Installation Wizard, click the Installation link.
171
If you are using the NetBackup media kit to install OpsCenter, click OpsCenter Software Installation. Ignore this step if you are installing OpsCenter server software from the OpsCenter DVD. Click the OpsCenter Server Installation link to install Symantec OpsCenter server. Click Next. Read the license agreement, check I accept the terms of the license agreement and click Next. Select Install a clustered OpsCenter Server to install OpsCenter Server in clustered mode. You need to install OpsCenter Server manually on each node of the cluster. This option is enabled if you have Veritas Cluster Server (VCS) installed. Select Install to this computer only to install OpsCenter Server in non-clustered mode.
5 6 7 8
In the Installation Method section, click Typical to use the default settings and installation location. Also compare the space that is required for installation with the actual space available 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 have
received with the purchase of OpsCenter and click Add Key. Note: You can also add the license keys from the OpsCenter console. See Managing licenses on page 226. The license keys that are already installed on the system are also displayed in the box that is shown on this screen. The license type information is also shown along with the key. More information about licenses is available. See About the OpsCenter licensing model on page 69.
11 Click Next. The Authentication Settings screen is displayed.
172
12 On the Authentication Settings screen, enter the following details of a

principal 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 168.
13 Click Next. The Cluster Settings screen is displayed. 14 On the Cluster Settings screen, enter the following information:
Cluster Group Name Enter the name for the OpsCenter cluster. For example: OpsCenter_Server Enter the virtual host name that is assigned to the OpsCenter cluster. For example: OpsCenter_Cluster-1 Enter the IP address that assigned to the OpsCenter cluster Enter the subnet mask . For example: 255.255.252.0 Select the shared drive path that you have configured in VxVM. For example, Z:\ Select LAN as a public network. You can select different public network for passive nodes.
Virtual host Name
Virtual IP address
Subnet mask Path to Shared data
Public Network
selected for OpsCenter Server installation. Check Save Summary to field to save the installation summary. Click Browse to save the installation summary in your preferred location.
173
16 Click Install.
The installer starts installing the OpsCenter Server software. Note: In clustered mode, the default OpsCenter database location on Windows is the following location on the shared drive: OpsCenter\Server\db
installation logs.
18 Click Finish.
Uninstalling Symantec OpsCenter from the cluster

Use the Windows Add/Remove Programs utility to uninstall OpsCenter Server from a cluster node on Windows host. Note: Uninstall the OpsCenter Server first from the passive nodes and then from the active node.. To unistall Symantec OpsCenter Server on Windows
1 2 3 4
Log on to the target host as a user with administrator privileges. In the Windows Control Panel, click Add/Remove Programs. Click Symantec OpsCenter Server and click Remove. Click Next to continue and remove Symantec OpsCenter Server from your computer.
Clustering Symantec OpsCenter Server on UNIX

This section provides information about installing OpsCenter Server in a clustered mode, on a UNIX host. Table 2-16 provides the UNIX clustering steps. Table 2-16 Step
1
OpsCenter Server clustering steps Description

Understand the limitations of a OpsCentercluster
Reference topic
See Limitations of Symantec OpsCenter cluster on UNIX on page 174.
174
Table 2-16 Step

2
OpsCenter Server clustering steps (continued) Description

Make sure that you have met all prerequisites.
Reference topic
See Prerequisites for Symantec OpsCenter cluster on UNIX on page 174.
Make sure that your preinstallation See Preinstallation checklist for checklist is complete. a Symantec OpsCenter Server installation on page 176. Install OpsCenter7.0. See Installing Symantec OpsCenter Server in clustered mode on UNIX on page 178.
Limitations of Symantec OpsCenter cluster on UNIX

A OpsCenter cluster has the following limitations:
Only OpsCenter Server can be clustered.OpsCenter Agent and the Symantec OpsCenter View Builder cannot be clustered. Upgrade of OpsCenter Server is not supported. OpsCenter cluster cannot co-exist with any other Symantec product running in secure mode using the Symantec Product Authentication Service. OpsCenterdoes not support clustered AT.
Prerequisites for Symantec OpsCenter cluster on UNIX

The following requirements must be met before you install and configure a Symantec OpsCenter failover server:
Verify VCS and OpsCenter support your hardware. For a list of supported storage devices, visit the following Web site: http://entsupport.symantec.com Verify that the supported version of VCS is correctly installed and configured on Solaris. Follow the steps in the Veritas Cluster Server Installation Guide. Verify that no VCS resource group and resource exist with the same name as that which you intend to use for OpsCenter. The SharedDisk must be configured and accessible to all cluster nodes where you want to install NetBackup. Verify that you have an IP address and host name (virtual name) to be assigned to the OpsCenter resource in VCS. Only use these for the OpsCenter resource.
175
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 license key. Verify that OpsCenter Server installation is carried out with the domain admin account. Before installing OpsCenter Server, ensure that Symantec authentication service (AT) Server is installed separately in a non-clustered mode. AT can be installed in Root + AB or AB mode. For more information about installing AT, see the Symanetc Infrastructce Core Services Installation Guide.
Installing Symantec Product Authentication Service on UNIX

OpsCenter Server requires that Symantec Product Authentication Service (AT) is installed on a standalone host, before OpsCenter can be clustered. You must install the version of AT Service that is shipped with OpsCenter. You can either configure AT in root + authentication broker (Root + AB) mode or authentication broker (AB) mode. Clustered OpsCenter Server uses this authentication broker. To establish a connection between AT host and OpsCenter Server host, you need to create a principal user on the AT host. Use the credentials of this user when installing OpsCenter Server. Note: Symantec Product Authentication Service is installed when you install Veritas Cluster Server. You must upgrade to the version of authentication service that 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
Logon to the host where you want to install AT. You should not cluster the AT service, as OpsCenter does not support clustered AT.
In the product DVD, navigate to the following directory: D:/ICS/Authentication D is DVD drive.
176
Invoke the ./installics script . Theinstallics menu is displayed.
Select 1 to install AT. See Symantec Infrstructure Core Services Installation Guide for more details on usinginstallics script.
Preinstallation checklist for a Symantec OpsCenter Server installation

The OpsCenter Server requests certain cluster related information during installation. 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 Node Name IP address ---------------------------------------------------------------------------------------------------------------------Network device name (NIC)
---------------------------------------- ---------------------------------------- ------------------------------------------------------------------------------- ---------------------------------------- ------------------------------------------------------------------------------- ---------------------------------------- ----------------------------------------
About installation of Symantec OpsCenter with VCS

The following information is required if you use VCS. Review the scenario that fits your configuration. See Scenario 1 - with VxVM on page 176. See Scenario 2- with no Volume Manager on page 177. See Scenario 3 - with AIX LVMVG on page 177. See Scenario 4 - in HP-UX with logical volume manager on page 178.
Scenario 1 - with VxVM

The following information is required if you use VCS with VxVM.
177
Resource Disk group resource: Disk group : -------------------------------------Start volumes: ----------------------------------Stop volumes: ----------------------------------Volume resource: (optional) Volume: ------------------------------------------Mount resource: Mount point : -----------------------------------Block device: ----------------------------------FS Type: -----------------------------------------Mount option: ---------------------------------Fsck option: -------------------------------------
Example
opsdg 0 or 1 0 or 1
opsvol
/opt/VRTSnbu /dev/vx/dsk/opsdg/opsvol vxfs (optional) (if you add other options, -y is also required)
Scenario 2- with no Volume Manager

The following information is required if you use VCS with a disk only and no Volume Manager.
Resource Mount point : -----------------------------------Block device: ----------------------------------FS type: -----------------------------------------Mount option: ---------------------------------Fsck option: ------------------------------------Example /opt/VRTSnbu /dev/dsk/clt1dos3 vxfs (optional) (if you add other options, -y is also required)
Scenario 3 - with AIX LVMVG

The following information is required if you use VCS in an AIX environment with LVMVG.
Resource LVMG resource: Example
178
Volume group : ---------------------------------Major number: ----------------------------------
opsvg 58
Disks: ---------------------------------------------- hdisk1 or hdisk2 ImportvgOpt: -----------------------------------VaryonvgOpt: ----------------------------------SyncODM: --------------------------------------Mount resource: ------------------------------Mount point : -----------------------------------Block device: ----------------------------------FS type: -----------------------------------------Mount option: ---------------------------------Fsck option: ------------------------------------/opt/VRTSnbu /dev/opsdev jfs2 (optional) (if you add other options, -y is also required) (optional) (optional) (optional)
Scenario 4 - in HP-UX with logical volume manager

The following information is required if you use VCS in an HP-UX environment with logical volume manager .
Resource LVM volume group Resource: Volume group : ---------------------------------LVM logical volume Resource: Volume group : ---------------------------------Logical group: ---------------------------------vg0a lvol1 vg0a Example
Installing Symantec OpsCenter Server in clustered mode on UNIX

To cluster OpsCenter and make it highly available, you must install and configure OpsCenter in a clustered mode.
179
Note: To install OpsCenter Server in clustered mode, first install the OpsCenter Server on the active node and then on the passive nodes. Also, you need to install OpsCenter Server manually on all the nodes.
Note: Tomcat is not clustered or installed in the shared drive. Hence configurePortsutility has to be run on each node. To install a OpsCenter Server in clustered mode on UNIX
Fill out the checklist for all configurations and the checklist for your specific environment. See Preinstallation checklist for a Symantec OpsCenter Server installation on page 176.
2 3
Open a UNIX console and log on as root on the target host. Mount the OpsCenter product DVD for the appropriate platform on which you are installing. You may install OpsCenter Server 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.
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 volume the mount point is on and deport the disk group for that volume on all nodes of the cluster.
If you are using the OpsCenter DVD to install OpsCenter Server software, navigate to the appropriate OpsCenter Server platform directory and then theServer directory on the DVD. If you are using the NetBackup media kit to install OpsCenter Server, navigate to the Server directory.
cd OpsCenter/Server
6 7 8
Type the following command:./installOpsCenterServer. Press Enter. The Welcome message is displayed. Press Enter to continue. The installer then checks if OpsCenter Server is installed on the system or not. It prompts you in case OpsCenter is already installed. The installer also examines the system for existing packages.
180
The installer displays a list of components that are installed like PBX, Symantec WebGUI Server, Symantec Database etc. Review this list and press Enter to continue.
10 The installer prompts you with the following question:

11 Type y to confirm the directory path and press Enter. 12 When OpsCenter Server is installed on the clustered setup a confirmation
prompt is displayed.
When installing OpsCenter Server on the first node, you are prompted to confirm creation of a OpsCenter Server cluster. Type Yes to set up OpsCenter in HA mode. When installing OpsCenter Server on the subsequent nodes, information of already created NetBackup cluster group is displayed. You are prompted to join the group.
13 When you are prompted for cluster specific configuration details, refer to
the 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 cluster name that you provided during the installation. This name is case sensitive and must be in same format (FQDN/short) on all the nodes.
14 Allow OpsCenter to be installed in a cluster. When a OpsCenter Server is

installed:
On the first node, a single node cluster resource group for OpsCenter is created and brought online. On the other nodes, the installed node is added to the cluster resource group.
181
Uninstalling OpsCenter Server from the cluster

Use the Uninstall Script, which resides in the root directory of the product DVD and also in /opt/VRTS/install directory, to uninstall OpsCenter from a node on a UNIX host. To unistall OpsCenter Server on UNIX
1 2
Open a UNIX console and log on as root on the target host. Change to the following directory:
/opt/VRTS/install

./uninstallopscenterserver
The Uninstall Script checks the components that are installed on the system.
When you are asked to confirm if you want to uninstall OpsCenter Server, do one of the following:
182
Chapter
Administering Symantec OpsCenter


About OpsCenter services and processes used by OpsCenter About OpsCenter server scripts on Windows and UNIX About OpsCenter database administration 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 by OpsCenter

This section provides information about OpsCenter services and processes and how 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.
About services used by OpsCenter on Windows

After you install OpsCenter server and Agent on Windows, the following services should be active. OpsCenter depends on these services. If any of these services fail to start, OpsCenter does not start.
184
Administering Symantec OpsCenter About OpsCenter services and processes used by OpsCenter
Table 3-1 contains information about the services that OpsCenter uses on Windows. Table 3-1 Service Name Service Services used by OpsCenter on Windows Description
This service is for the Symantec OpsCenter Agent. By default, the OpsCenter Agent Service starts whenever you boot your Agent host. The OpsCenter server interacts with the OpsCenter GUI and provides the data that is requested by the GUI from the OpsCenter database. It also interacts with NetBackup through NBSL to get data regularly. This service manages the OpsCenter databases. This process must be running on the OpsCenter server during all normal operations like viewing reports, running reports and so on. This service is not an OpsCenter service. OpsCenter uses this service to host the OpsCenter Console. This service is not an OpsCenter service, but it is a component used by OpsCenter. Symantec Private Branch Exchange allows all socket communication to take place through a single port. This service is not an OpsCenter service. OpsCenter uses this service to authenticate users of OpsCenter.
Symantec OpsCenter Agent java.exe Service
Symantec OpsCenter Server Service
java.exe
Symantec OpsCenter Database Server
dbsrv11.exe
Symantec OpsCenter Web java.exe server Service Symantec Private Branch Exchange pbx_exchange.exe
Symantec Product Authentication Service
vxatd.exe
Controlling the services

Use the following procedure to verify if these services are running or not. To control these services
1 2 3
Use Start > Settings > Control Panel > Administrative Tools > Services. Check the Status column for each service. From the Status column, you can verify if a service is running or not. The Services panel can also be used to stop, start, and restart the OpsCenter services and Symantec shared services.
About processes used by OpsCenter on UNIX

After you install OpsCenter server and Agent on UNIX, the following processes should be active. Table 3-2 describes the processes that OpsCenter uses on UNIX.
Administering Symantec OpsCenter About OpsCenter server scripts on Windows and UNIX
185
Table 3-2 Process Description

Symantec OpsCenter Agent
Processes used by OpsCenter on UNIX Detailed Description
Process
/opt/SYMCOpsCenterAgent/bin/.OpsCenterAgentd This process is for the Symantec OpsCenter Agent. By default, the OpsCenter Agent process starts whenever you boot your Agent host. /opt/SYMCOpsCenterServer/bin/.OpsCenterServerd The OpsCenter server interacts with the OpsCenter GUI and provides the data that the GUI requests from the OpsCenter database. It also interacts with NetBackup to get data regularly. This process manages the OpsCenter databases. This process must be running on the OpsCenter server during all normal operations like viewing reports, running reports and so on. This process is not an OpsCenter process. OpsCenter uses this process to host the OpsCenter Console. Many Symantec Web consoles share this component. This process is not an OpsCenter process. but it is a component used by OpsCenter. PBX allows all socket communication to take place through a single port. This process is not an OpsCenter process. OpsCenter uses this process to authenticate users of OpsCenter.
Symantec OpsCenter Server
Symantec /opt/SYMCOpsCenterDatabase/bin/dbsrv11 OpsCenter Database Server
Symantec OpsCenter Web Server
java
/opt/VRTSpbx/bin/pbx_exchange
/opt/VRTSat/bin/vxatd
About OpsCenter server scripts on Windows and UNIX

The following scripts are used within OpsCenter. The OpsCenter administrator may use many of these scripts. Use the -h option for help about these scripts. Table 3-3 lists the OpsCenter server scripts on Windows.
186
Table 3-3 Script

startserver.bat and stopserver.bat dbbackup.bat
OpsCenter server scripts on Windows Function Invokes or Is Invoked by

Administrator
Location
INSTALL_PATH\OpsCenter\server\bin Starts or stops the OpsCenterServerd.
INSTALL_PATH\OpsCenter\server\bin Backs up the OpsCenter database INSTALL_PATH\OpsCenter\server\bin Starts or stops the OpsCenter database INSTALL_PATH\OpsCenter\server\bin Starts and stops all OpsCenter server services
OpsCenter Administrator
startdb.bat and stopdb.bat opsadmin.bat
dbdefrag.bat
INSTALL_PATH\OpsCenter\server\bin Defragments the OpsCenter OpsCenter Administrator database INSTALL_PATH\OpsCenter\server\bin Changes the OpsCenter database password OpsCenter Administrator
changedbpassword.bat
runStoredQuery.bat
INSTALL_PATH\OpsCenter\server\bin Runs saved custom SQL and OpsCenter Administrator generates output in the desired format.
Table 3-4 lists the OpsCenter server scripts on UNIX. Table 3-4 Script
startserver and stopserver startdb and stopdb /opt/SYMCOpsCenterServer/bin Starts or stops the OpsCenter Administrator OpsCenter database /opt/SYMCOpsCenterServer/bin Starts, stops, and monitors all OpsCenter server processes OpsCenter Administrator
OpsCenter server scripts on UNIX Function Invokes or Is Invoked by
Location
/opt/SYMCOpsCenterServer/bin Starts or stops the OpsCenterServer OpsCenterServerd.
opsadmin
187
Table 3-4 Script

OpsCenterServers
OpsCenter server scripts on UNIX (continued) Function Invokes or Is Invoked by
Location
Solaris: /etc/init.d
This script is used OpsCenterServer internally for clustering. The script starts, stops, or restarts the OpsCenter database, OpsCenter Server, and OpsCenter Web server (Tomcat).
dbbackup.sh
/opt/SYMCOpsCenterServer Backs up the OpsCenter Administrator OpsCenter database /opt/SYMCOpsCenterServer Defragments the OpsCenter Administrator OpsCenter database /opt/SYMCOpsCenterServer Changes the OpsCenter Administrator OpsCenter database password /opt/SYMCOpsCenterServer Runs saved custom OpsCenter Administrator SQL and generates output in the desired format.
dbdefrag
changeDbPassword
runStoredQuery
Controlling OpsCenter services and processes

This section provides information on how you can control the OpsCenter server services and OpsCenter Agent service.
Controlling all Symantec OpsCenter server services on Windows servers using opsadmin
The following procedure describes how you can start and stop all OpsCenter server services using the opsadmin script. To start all OpsCenter server services
Enter the following command:

INSTALL_PATH\OpsCenter\server\bin\opsadmin.bat start
188
To stop all OpsCenter server services

INSTALL_PATH\OpsCenter\server\bin\opsadmin.bat stop
Controlling the Symantec OpsCenter database server service on Windows servers

The following procedure describes how you can control the Symantec OpsCenter database server service on Windows servers. To start or stop the Symantec OpsCenter database server service
Select Control Panel > Administrative Tools > Services and start or stop the Symantec OpsCenter Database Server service.
Controlling the Symantec OpsCenter Server Service on Windows servers

The following procedure describes how you can control the Symantec OpsCenter server service on Windows servers. To start or stop the Symantec OpsCenter server service
Select Control Panel > Administrative Tools > Services and start or stop the Symantec OpsCenter Server Service.
Controlling the Symantec OpsCenter Web server Service

The following procedure describes how you can control the Symantec OpsCenter Web server service on Windows servers. To start or stop the Symantec OpsCenter Web server service
Select Control Panel > Administrative Tools > Services and start or stop the Symantec OpsCenter Web Server Service.
Controlling the Symantec OpsCenter Agent Service

The following procedure describes how you can control the Symantec OpsCenter Agent service on Windows servers. To start or stop the Symantec OpsCenter Agent service
Select Control Panel > Administrative Tools > Services and start or stop the Symantec OpsCenter Agent Service.
189
Controlling all Symantec OpsCenter server processes on UNIX servers using opsadmin.sh script
The following procedure describes how you can start, stop, and monitor all OpsCenter server processes using the opsadmin script. To start all OpsCenter server processes
Enter the following command to start all OpsCenter server processes:

/opt/SYMCOpsCenterServer/bin/opsadmin.sh start
To stop all OpsCenter server processes
Enter the following command to stop all OpsCenter server processes:

/opt/SYMCOpsCenterServer/bin/opsadmin.sh stop
To monitor all OpsCenter server processes
Enter the following command to monitor the status of all OpsCenter server processes:
/opt/SYMCOpsCenterServer/bin/opsadmin.sh monitor
Controlling the Symantec OpsCenter database server process on UNIX servers

The following procedure describes how you can control the OpsCenter database server process on UNIX servers. To start the database server
/opt/SYMCOpsCenterServer/bin/startdb
To stop the database server
/opt/SYMCOpsCenterServer/bin/stopdb
190
Controlling the Symantec OpsCenter server process on UNIX servers

The following procedure describes how you can control the OpsCenter server process on UNIX servers. To start the OpsCenter server
/opt/SYMCOpsCenterServer/bin/startserver
To stop the OpsCenter server
/opt/SYMCOpsCenterServer/bin/stopserver
Controlling the Symantec OpsCenter Web server process on UNIX servers

The following procedure describes how you can control the OpsCenter server process 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
Controlling the Symantec OpsCenter Agent process on UNIX servers

The following procedure describes how you can control the OpsCenter Agent process on UNIX servers.
191
To start the OpsCenter Agent

/opt/SYMCOpsCenterAgent/bin/startagent
To stop the OpsCenter Agent

/opt/SYMCOpsCenterAgent/bin/stopagent
About dependency of services

The Symantec OpsCenter server service requires that the following OpsCenter services (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.
About nbproxy processes on NetBackup master servers

When OpsCenter is connected to a master server, you may find one or more nbproxy processes running on the master server. You may also see nbproxy processes when NetBackup-Java GUI or NetBackup-Windows GUI request certain data from NetBackup (like LiveUpdate , storage lifecycle policies). Most of the nbproxy processes are started, managed, and removed by NBSL. This section talks about the nbproxy processes that NBSL manages. Note: Not all nbproxy processes on the master server are managed by NBSL. For example, 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
192
Administering Symantec OpsCenter About OpsCenter database administration
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 is removed from the OpsCenter console, all nbproxy processes are stopped immediately. If OpsCenter crashes (or is abruptly closed), the nbproxy process is removed within an hour. If NetBackup is stopped (and NBSL is already killed), all nbproxy processes are stopped immediately. If NBSL crashes (or is abruptly closed), all nbproxy processes exit within 10 minutes.
About OpsCenter database administration

The Sybase database that OpsCenter uses is similar to the NetBackup database and is installed as part of the OpsCenter installation. The database is located on the OpsCenter server. More information about Sybase database is available. See http://www.sybase.com/support/manuals.
Running OpsCenter commands

OpsCenter provides some useful commands to help manage the OpsCenter database. These utilities also let you change the authentication server parameters and provide user help. Table 3-5 lists the commands that are available. Table 3-5 Command
changeDbPassword
Commands available with OpsCenter Reference

See Changing the OpsCenter database administrator password on page 193. See Defragmenting the OpsCenter database on page 194. See Backing up the OpsCenter database on page 200. See Restoring the OpsCenter database on page 203.
dbdefrag
dbbackup
193
Table 3-5 Command
Commands available with OpsCenter (continued) Reference

See Configuring authentication server parameters on page 194.
changeVxATProperties
Changing the OpsCenter database administrator password

The changeDbPassword utility lets you change the database administrator password that is used for the OpsCenter database. Note: This utility is not used to change the logon password for OpsCenter. To change the existing logon password, you must use the OpsCenter console. See Changing your password on page 225. OpsCenter uses the Sybase SA (Server Anywhere) database to store data. You require a user name and a password to access the data that is stored in the database. The database administrator user ID is DBA and the initial password is SQL (password is case sensitive). Review the rules for forming a new database password. The OpsCenter database administrator password cannot have the following characteristics:

Exceed 30 characters. Contain consecutive black slash characters. Contain any bracket [ ] characters. Contain any of the following characters. These characters have special meaning in Windows or in shell scripts. ! $ % & . ; ^ | < > , { } $ " ~ [ ] \\ Contains the ASCII characters that are less than 32 or ASCII characters that are 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 235.
194
To change the database administrator password on Windows and UNIX
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 3
You are prompted for the old database administrator password. Enter the old database password. You are prompted for a new database administrator password. Enter the new password.
Defragmenting the OpsCenter database

You 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 and after a purge operation. Note: OpsCenter does not work during the time when the OpsCenter database is defragmented. To defragment the OpsCenter database on Windows and UNIX
To defragment the OpsCenter database on Windows, run the following command:

INSTALL_PATH\OpsCenter\server\bin\dbdefrag.bat
To defragment the OpsCenter database on UNIX, run the following command:

/opt/SYMCOpsCenterServer/bin/dbdefrag.sh
Configuring authentication server parameters

The authentication server parameters can be configured using the changeVxATProperties utility. Note: This procedure is applicable only for OpsCenter clusters where the authentication broker is remote. This procedure is not applicable when Symantec Product Authentication Service is installed on the local machine.
195
To configure authentication server parameters
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 values of the parameters are specified in brackets.
2 3
Enter the new values next to the respective parameter. If you do not enter a new value for a parameter, the value of the parameter does not change. 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 hard disks
To improve OpsCenter performance, OpsCenter database files and the log files that are associated with the OpsCenter database should be stored on separate hard disks. You can store the OpsCenter database files on one hard disk and the log files on another hard disk. Symantec also recommends that you not store the database files on the hard disk that contains your operating system files. You can specify a custom location (non-default location) for the OpsCenter database during OpsCenter installation. The default location for the OpsCenter database can also be changed after OpsCenter has been installed. Use the following procedures to move the OpsCenter database and log files to a different hard disk. The first two procedures are for moving the OpsCenter database files on Windows or UNIX. The last two procedures are for moving the database log files.
196
To move the OpsCenter database to a different hard disk on Windows
Stop all OpsCenter server services. Enter the following command:

Open the databases.conf file with a text editor like notepad from the following 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.
To move the database to a custom location like E:\Database, replace the contents of the file with the following:
"E:\Database\vxpmdb.db"
Make sure that you specify the path in double quotes. Also the directories in the 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 5
Copy the database file to the new location. Copy vxpmdb.db from INSTALL_PATH\OpsCenter\server\db\data to a location like E:\Database. Restart all OpsCenter server services. To restart all OpsCenter services, enter the following command:
You should run and monitor OpsCenter for a certain period after moving the database. If OpsCenter works as expected, you can delete vxpmdb.db from the default location (INSTALL_PATH\OpsCenter\server\db\data).
197
To move the OpsCenter database to a different hard disk on UNIX
Stop all OpsCenter server processes. Enter the following command:

The default location of the OpsCenter database in UNIX is /opt/SYMCOpsCenterServer/db/data. To move the database to a custom location like /usr/mydata,enter the following command:
mv /opt/SYMCOpsCenterServer/db/data /usr/mydata
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 /opt/SYMCOpsCenterServer/db/data
Restart all OpsCenter server processes by entering the following command:

You should run and monitor OpsCenter for a certain period after moving the database. If OpsCenter works as expected, you can delete vxpmdb.db from /opt/SYMCOpsCenterServer/db/data.
198
To move the database log files to a different hard disk on Windows

Navigate to the following location:

INSTALL_PATH\OpsCenter\server\db\WIN32
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 logs and database_path is the path where your database is located. This command moves the log file that is associated with the OpsCenter database to the new directory (directory_path). It is recommended to use vxpmdb.log as the name of the log file.
Restart all OpsCenter server services. To restart all OpsCenter services, enter the following command:
To move the database log files to a different hard disk on UNIX

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
Administering Symantec OpsCenter About backup and restore of OpsCenter and OpsCenter Analytics
199
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 log file and database_path is the path where the OpsCenter database is located. This command moves the log file that is associated with the OpsCenter database to the new directory (directory_path). It is recommended to use vxpmdb.log as the name of the log file.
Restart all OpsCenter server processes by entering the following command:

About database troubleshooting

Security information about the OpsCenter database is available. See About OpsCenter Web GUI/OpsCenter server to Sybase database communication on page 211. Information about the log files on Windows and UNIX servers is available. See About OpsCenter log files on Windows servers on page 215. See About OpsCenter log files on UNIX servers on page 217.
About backup and restore of OpsCenter and OpsCenter Analytics

The procedures in this section explain how you can back up and restore OpsCenter and OpsCenter Analytics in case of a disaster.
Backing up OpsCenter
The sequence of steps gives an overview about the steps that need to be followed to back up OpsCenter.
200
To back up OpsCenter in case of a disaster
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 OpsCenter database. See Backing up the OpsCenter database on page 200.
Along with the OpsCenter database, the user information that Symantec Product Authentication Service manages must be saved in a directory or by using a NetBackup backup policy. See Saving the OpsCenter user profiles managed by Symantec Product Authentication Service on page 201. Note: You can also create schedules for taking regular database and authentication profile backups. In this case, NetBackup policies can be created to back up the specified directories that contain OpsCenter database snapshots and the authentication service user configuration files. See the NetBackup Administrators Guide, Volume I for more information on how to configure a policy and schedule.
If you want to change the OpsCenter database password, you also need to back up the database password file. See Backing up the OpsCenter database password file on page 202.
Backing up the OpsCenter database

OpsCenter is shipped with a database backup script that performs backup of the database 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 as follows: vxpmdb.db and vxpmdb.log. The script backs up or restores the vxpmdb.db and vxpmdb.log file (if it exists). Note: Regular file system backups are not sufficient for backing up the OpsCenter database. You must schedule periodic hot backups for the OpsCenter database to avoid losing any important data.
201
To back up the OpsCenter database
Log on to the OpsCenter database server host in one of the following ways:
Windows UNIX As an administrator or user in the Administrator group root
2 3
Open the Windows command prompt or the UNIX console. Run the backup script that is appropriate for your platform. Specify one of the following backup directories depending on your platform:
Windows INSTALL_PATH\OpsCenter\server\bin\dbbackup.bat C:\MyDbBackupFolder /opt/SYMCOpsCenterServer/bin/dbbackup.sh /my_db_backup_dir
UNIX
The backup script creates vxpmdb.db and vxpmdb.log (if it exists) in the backup directory that you specified.
Saving the OpsCenter user profiles managed by Symantec Product Authentication Service
Use the following procedures to save the authentication service profiles on Windows and UNIX servers. To save authentication service profiles on Windows servers
Do one of the following to save the user profiles:
Copy the folder

INSTALL_PATH\VERITAS\Security\Authentication\systemprofile to
another folder.
Create a NetBackup job policy to back up the authentication service systemprofile 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 profile folder.
202
Backing up the OpsCenter database password file

If you want to change the OpsCenter database password you also need to back up the following password file (along with the backup of the OpsCenter database files and 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 in

INSTALL_PATH/OpsCenter/server/config directory.
To back up the OpsCenter database password file on UNIX
Back up the db.conf file that is located in /opt/SYMCOpsCenterServer/config directory.
Restoring OpsCenter
A restore of OpsCenter requires that the new OpsCenter server has the same host name and IP address of the old server that crashed. This limitation involves authentication service credentials (host name and IP address) which are stored on the server. Note: The following procedures assume that you have OpsCenter database snapshots and the authentication service user profiles saved in folders. The sequence of steps gives an overview about the steps that need to be followed to restore OpsCenter. To restore OpsCenter in case of a disaster
1 2 3
Install OpsCenter on a server with the same name as the server where problems happened. Stop all OpsCenter server services. Restore the OpsCenter database snapshot files and authentication service user profiles from the backup image. See Restoring the OpsCenter database on page 203. See Restoring the OpsCenter user profiles managed by Symantec Product Authentication Service on page 205.
If you saved a copy of the OpsCenter database password file, copy the file to the corresponding location on the newly installed OpsCenter server. Copy the db.conf file to INSTALL_PATH/OpsCenter/server/config directory on Windows or /opt/SYMCOpsCenterServer/config directory on UNIX. Restart all OpsCenter server services.
203
Restoring the OpsCenter database

After you back up the database, you can restore it. On Windows and UNIX hosts, the restore operation automatically stops the database, restores the backup database files, and restarts the database. The dbbackup script overwrites existing database (db) files before backing up or restoring the database. The database files are as follows: vxpmdb.db and vxpmdb.log. The script backs up or restores the vxpmdb.db and vxpmdb.log file (if it exists).
204
To restore a backed up OpsCenter database
On the OpsCenter server whose backup data you want to restore, open a UNIX console or a Windows command prompt and log on as root (on UNIX) or as an administrator or user in the Administrators group (on Windows).
Windows Open a Windows command prompt and log on as an administrator or user in the Administrators group. 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 database install paths. These paths may different for your site if the database was installed anywhere other than the default location.
To restore the backed up database, do one of the following:

Windows Type the following command and press Enter. INSTALL_PATH\OpsCenter\server\bin\dbbackup.bat <backupDir> -restore <restoreDir> UNIX Type the following command and press Enter. /opt/SYMCOpsCenterServer/bin/dbbackup.sh <backupDir> -restore <restoreDir>
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:
Windows UNIX INSTALL_PATH\OpsCenter\server\db\data /opt/SYMCOpsCenterServer/db/data
If you specified a non-default directory location, you must specify the restoreDir 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)
Administering Symantec OpsCenter About communication and firewall considerations
205
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 Symantec Product Authentication Service
Use the following procedures to save the authentication service profiles on Windows and UNIX servers. To restore the authentication user profiles on Windows

2 3
Copy or overwrite the folder containing the authentication service user profiles to INSTALL_PATH\VERITAS\Security\Authentication\systemprofile. Start all OpsCenter server services. Enter the following command:
To restore the authentication user profiles on UNIX

2 3
Copy or overwrite the folder containing the authentication service user profiles to /var/VRTSat Start all OpsCenter server processes. Enter the following command:
About communication and firewall considerations

Figure 3-1 shows the key OpsCenter components and the communication ports that are used.
206
Figure 3-1
Key OpsCenter components and how they communicate

The following HTTP and HTTPS port combinations are checked for availability in the specified sequence and the first available port combination is used as the default HTTP and HTTPS port respectively - Port 80 and Port 443, Port 8181 and Port 8443, and, Port 8282 and Port 8553. ViewBuilder Console
Web Browser
Possible Firewall
OpsCenter Web GUI
SMTP email Possible Firewall SNMP Port 162 traps
PBX default port 1556
Default Port 13786 OpsCenter Database
OpsCenter Server
PBX default port 1556 Possible Firewall NetBackup Master Server with NBAC Hosts where backup products like Backup Exec, PureDisk etc. are installed NetBackup Master Server without NBAC
Hosts where backup products like Backup Exec, PureDisk etc..are installed
The following table shows the default port settings for OpsCenter. SMTP recipient ports can be configured from the OpsCenter console (using Settings > Configuration > SMTP Server). The SNMP trap recipient ports can also be configured from the OpsCenter console (using Settings > Recipients > SNMP).
207
If these ports are changed then the appropriate hardware ports have to be opened. Table 3-6 lists the communication ports that are used by key OpsCenter components. Table 3-6 Source Host
OpsCenter Server OpsCenter Server OpsCenter Server
Communication ports used by key OpsCenter components Usage (Process Port Configuration Name)
SMTP Allow from source to destination.
Destination Port Number Host

Mail server 25
SNMP Server 162
SNMP trap recipient PBX (pbx_exchange)
Allow from source to destination.
NetBackup Master Server(s)
1556
Allow between source and destination (bi-directional). PBX port number configuration is supported. See About OpsCenter Web GUI to OpsCenter server software communication on page 210.
OpsCenter Client
OpsCenter Server
1556
PBX (pbx_exchange)
Allow between source and destination. Some hardened servers and firewall configurations may block this port. PBX port number configuration is not supported. See About OpsCenter Web GUI to OpsCenter server software communication on page 210.
208
Table 3-6
Communication ports used by key OpsCenter components (continued) Usage (Process Port Configuration Name)
Allow from all hosts on network.
Source Host
Destination Port Number Host
Web browser OpsCenter Server
The following HTTP and HTTP and HTTPS HTTPS ports are checked for availability in the specified sequence and the first available port combination is used by default:
80 (HTTP) and 443 (HTTPS) 8181 (HTTP) and 8443 (HTTPS) 8282 (HTTP) and 8553 (HTTPS) Sybase database Allow between source and destination. (dbsrv11) Some hardened servers and firewall configurations may block this port. Symantec Allow between source and destination in case Product NBAC is enabled on NetBackup master server. Authentication Service (vxatd)
OpsCenter Server
OpsCenter Server
13786
OpsCenter Server
Host where 2821 Symantec Product Authentication Service (AT) Server is installed
About ports required to communicate with backup products

This section provides information about the ports that OpsCenter Agent uses to communicate with backup products like NetBackup, Backup Exec, PureDisk, TSM etc. Table 3-7 lists the ports that must be opened on OpsCenter Agent to collect data from various backup products.
209
Table 3-7 Backup product

NetBackup
Ports required to communicate with other backup product Communication

OpsCenter (NetBackup data collector) communicates with the NetBackup master server. 13782 port should be used to connect to the NetBackup master server and 13724 port should be used to respond to the Agent host. The response is sent on a port in the reserved port range 512-1023 if not configured to use vnetd The following processes are used for NetBackup data collection:

Port number
13782 & 13724
bperror.exe bpretlevel.exe bpimagelist.exe 6106
Backup Exec
OpsCenter (Backup Exec data collector) communicates with Backup Exec Server using Backup Exec API
PureDisk
OpsCenter (PureDisk data collector) 443 (HTTPS) communicates with PureDisk SPA 2821 (AT) using atssl OpsCenter (TSM data collector) communicates with TSM Server using TSM CLI dsmadmc 1500
TSM
OpsCenter (Legato data collector) This is a local host communicates with Legato Server communication locally
About Web browser to OpsCenter Web GUI connection

Web browsers use Insecure hypertext transfer protocol (HTTP) and Secure hypertext transfer protocol (HTTPS) to communicate with the OpsCenter Web GUI. These protocols use TCP/IP. For HTTP, specific ports are checked for availability in a particular sequence and the first available port is used by default.
210
Table 3-8 lists how the default HTTP and HTTPS ports are selected. Table 3-8 Sr. No.
1.
Default HTTP and HTTPS ports HTTPS port number

443
HTTP port number

80
Description
Port 80 and Port 443 are checked for availability. If port 80 and port 443 are available, port 80 is used as the default HTTP port and port 443 is used as the default HTTPS port. In case, some other application like a Web server uses one or both ports, then the next port combination is checked for availability.
2.
8181
8443
Port 8181 and Port 8443 are checked for availability. If port 8181and port 8443 are available, port 8181 is used as the default HTTP port and port 8443 is used as the default HTTPS port. In case, some other application like VRTSWeb installed with VCS or any other product uses one or both ports, then the next port combination is checked for availability.
3.
8282
8553
Port 8282 and Port 8553 are checked for availability.
These HTTP and HTTPS ports are opened only for input and are configurable using the command lines. See configurePorts on page 566.
About OpsCenter Web GUI to OpsCenter server software communication

The OpsCenter Web GUI uses Symantec Private Branch Exchange (PBX) to communicate with the OpsCenter server software. The default port is 1556. The PBX port is opened for input and output traffic.
211
About OpsCenter server to NetBackup master server (NBSL) communication

OpsCenter requires the NetBackup Service Layer (NBSL) to be present on all managed master servers. The OpsCenter server software collects data from NBSL in the following ways:

Initial data load Listening for change notifications or events
Whenever OpsCenter server software starts, when data collection for a master server is enabled or when a master server is added to OpsCenter, the OpsCenter server starts collecting all the available data from NetBackup master server into the OpsCenter database using NBSL. The initial data load happens serially for each data type. As soon as the initial data load is complete, the OpsCenter server software listens to notifications sent by NBSL for any change in NetBackup data, and updates the OpsCenter database. Symantec Private Branch Exchange (PBX) is used for communication and requires a port opened on the OpsCenter server and the NetBackup master server for input and output. The default PBX port that is used is 1556. If you change the PBX port on the NetBackup master server, you can configure the same in OpsCenter while adding or editing a master server. See Adding a master server on page 278.
About SNMP traps

SNMP trap protocol is used for outbound UDP traffic and requires a port that opens for output. The port number is 162.
About OpsCenter Web GUI/OpsCenter server to Sybase database communication

The OpsCenter Web GUI communicates with the OpsCenter Sybase SQL Anywhere database server by using the default port 13786. The Sybase database server port is closed to all inbound connections. The database is available only to resident OpsCenter components on the OpsCenter server.
About OpsCenter Web GUI to OpsCenter server email communication

SMTP email server protocol is used for outgoing mail. The port number is defined when the user specifies the SMTP server port (see Settings > Configuration >
212
Administering Symantec OpsCenter Gathering troubleshooting data with the support script
SMTP Server in the OpsCenter console to specify this port). The port is opened for output only.
Gathering troubleshooting data with the support script

If you are running OpsCenter on UNIX or Windows, you can use the supportscript to gather troubleshooting information for OpsCenter server and OpsCenter Agent. The script collects server and agent logs, collects information about any data collection problems, captures the current agent configuration, and compresses the results into a zip file. This file can serve as a first-level information for the Support team in case of an issue with OpsCenter. To gather troubleshooting data with the support script on Windows
Run the following commands to execute the support scripts for server and agent respectively:
INSTALL_PATH\OpsCenter\server\bin\opsCenterSupport.bat INSTALL_PATH\OpsCenter\Agent\bin\opsCenterAgentSupport.bat
Note: The following are the default directory locations on Windows machines.
This script stops all the OpsCenter services and then collects system information and OpsCenter configuration information. It then compresses all this information in a file that is called Support.zip. You can also choose to add log files, OpsCenter database files etc. to this zip file. Adding log files and OpsCenter database files can increase the file size of the resulting Support.zip file.
This zip file is stored in the following directories: For OpsCenter Server: INSTALL_PATH\OpsCenter\server\temp\support For OpsCenter Agent: INSTALL_PATH\OpsCenter\Agent\temp\support
After the zip file is created, the script starts all the OpsCenter services.
Administering Symantec OpsCenter About OpsCenter log files
213
To gather troubleshooting data with the support script on UNIX
Run the following commands to execute the support scripts for server and agent respectively:
/opt/SYMCOpsCenterServer/bin/opsCenterSupport.sh /opt/SYMCOpsCenterServer/bin/opsCenterAgentSupport.sh
Note: The following are the default directory locations on UNIX machines.
This script stops all the OpsCenter processes and then collects system information and OpsCenter configuration information. It then collates all this information in a Support.zip file. You can also choose to add log files, OpsCenter database files etc. to this zip file. Adding log files and OpsCenter database files can increase the file size of the resulting Support.zip.
This zip file is stored in the following directories: For OpsCenter Server: /opt/SYMCOpsCenterServer/temp/support For OpsCenter Agent: /opt/SYMCOpsCenterAgent/temp/support
After the zip file is created, the script automatically starts all the OpsCenter processes.
About OpsCenter log files

OpsCenter creates log files that you can use to troubleshoot installation, performance, and other issues. OpsCenter writes log files using Veritas Unified Logging (VxUL), legacy, and other log file formats. See About OpsCenter log files on Windows servers on page 215. See About OpsCenter log files on UNIX servers on page 217.
About VxUL log files

The VxUL log file creates log file names and messages in a format that is standardized across all Symantec components. These messages use VxUL IDs (a product ID and an originator ID) that identify the component that wrote the log message. OpsCenter components create most log messages in VxUL format. Table 3-9 shows the originator IDs used by OpsCenter and key shared components.
214
Table 3-9
VxUL IDs used by OpsCenter components Originator name

Symantec Private Branch Exchange service (PBX) NetBackup Service Layer (NBSL) Symantec OpsCenter Agent Symantec OpsCenter Web GUI Symantec OpsCenter Server
VxUL originator ID
103 132 146 147 148
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, OpsCenter Agent, and the OpsCenter Web GUI. The following OID values must be used for OpsCenter server, OpsCenter Agent, and OpsCenter Web GUI.
OpsCenter Server OpsCenter Agent OpsCenter Web GUI 148 146 147
Table 3-10 lists the commands by which you can control logging on Windows. Table 3-10 Control Logging Control logging on Windows Command
To change the log directory INSTALL_PATH\OpsCenter\server\bin\vxlogcfg.exe -a -p destination (default value is 58330 -o <OID> -s LogDirectory="<New log directory location>" <INSTALL_PATH\OpsCenter\server\logs Note: 58330 is the OpsCenter product ID. To configure the verbosity level (default value is 1) INSTALL_PATH\OpsCenter\server\bin\vxlogcfg.exe -a -p 58330 -o <OID> -s DebugLevel=1
215
Table 3-10 Control Logging
Control logging on Windows (continued) Command
To configure the diagnostic INSTALL_PATH\OpsCenter\server\bin\vxlogcfg.exe -a -p level (default value is 1) 58330 -o <OID> -s DiagnosticLevel=1 To configure the number of INSTALL_PATH\OpsCenter\server\bin\vxlogcfg.exe -a -p log files that are created 58330 -o <OID> -s NumberOfLogFiles=100 (default value is 100)
Table 3-11 lists the commands by which you can control logging on UNIX. Table 3-11 Control logging Control logging on UNIX Command
To change the log directory destination /opt/SYMCOpsCenterServer/bin/vxlogcfg (default value is -a -p 58330 -o <OID> -s LogDirectory="<New <INSTALL_PATH/SYMCOpsCenterServer/logs) log directory location>"
Note: 58330 is the OpsCenter product ID.

To configure the debug level (default value is 1) /opt/SYMCOpsCenterServer/bin/vxlogcfg -a -p 58330 -o <OID> -s DebugLevel=<New debug level> /opt/SYMCOpsCenterServer/bin/vxlogcfg -a -p 58330 -o <OID> -s DiagnosticLevel=<New diagnostic level>
To configure the diagnostic level (default value is 1)
To configure the number of log files that are /opt/SYMCOpsCenterServer/bin/vxlogcfg created (default value is 100) -a -p 58330 -o <OID> -s NumberOfLogFiles=<New number>
About OpsCenter log files on Windows servers

OpsCenter creates the following log files using VxUL and legacy formats.
About OpsCenter log files

Table 3-12 shows details about the OpsCenter log files.
216
Table 3-12 Log file directory

INSTALL_PATH\ OpsCenter\server\ logs\
OpsCenter log files Log file Troubleshooting purpose
ServerService_timestamp.log These log files for system.err and system.out of OpsCenter server service.
About log files associated with Symantec Product Authentication Service

Table 3-13 lists the log files that are associated with Symantec Product Authentication Service. Table 3-13 Log file directory Log files for Symantec Product Authentication Service Log file Troubleshooting purpose
Authentication activity.
On 32-bit Windows vxatd.log platforms: %ProgramFiles% vssconfig.log \Veritas\Security \Authentication\bin On 64-bit Windows platforms: %ProgramFiles(x86)% \Veritas\Security \Authentication\bin
About OpsCenter database log files

Table 3-14 lists the log files that are associated with the OpsCenter database. Table 3-14 Log file directory
INSTALL_PATH\ OpsCenter\server\db\log\ INSTALL_PATH\ OpsCenter\server\db\data\
Log files associated with the OpsCenter database Log file

server.log
Troubleshooting purpose
OpsCenter Sybase database activity. OpsCenter Sybase database transaction files.
vxpmdb.log
Note: Do not change this log file.
217
About OpsCenter Web server log files

The log files that are associated with the OpsCenter Web server are present in the INSTALL_PATH\OpsCenter\WebServer\logs directory.
About VxUL log files for OpsCenter and the components that OpsCenter uses
Table 3-15 lists the log files that are associated with VxUL and other components that OpsCenter uses. Table 3-15 Log file directory Log files associated with VxUL and other components Log file Troubleshooting purpose
PBX activity. NBSL activity.
INSTALL_PATH\VERITAS\VxPBX\bin\ 50936-103-*.log INSTALL_PATH\VERITAS\NetBackup\ 51216-132-*.log logs\ INSTALL_PATH\ OpsCenter\Agent\logs INSTALL_PATH\ OpsCenter\gui\logs\ INSTALL_PATH\ OpsCenter\server\logs 51216-146-*.log
Agent activity.
51216-147-*.log
OpsCenter Web GUI activity.
58330-148*.log
OpsCenter server activity.
About OpsCenter log files on UNIX servers

OpsCenter creates the following log files by using VxUL and legacy formats.
About log files associated with OpsCenter

Table 3-16 lists the log files for OpsCenter. Table 3-16 Log files for OpsCenter Troubleshooting purpose
stdout and stderr for the OpsCenterServer daemon. Shows the details of purge operations.
OpsCenter log file

/opt/SYMCOpsCenterServer/logs/ OpsCenterServer_out.log /opt/SYMCOpsCenterServer/logs/ purge-status.log /var/VRTS/install/logs/ (directory)
Provides a trace for any installation issues.
218
About log files for Symantec Product Authentication Service

Table 3-17 lists the log files that are associated with Symantec Product Authentication Service. Table 3-17 Log file
/var/VRTSat/vxatd.log
Log files for Symantec Product Authentication Service Troubleshooting purpose

Authentication activity.
About log files associated with OpsCenter database

Table 3-18 lists the log files that are associated with the OpsCenter database. Table 3-18 Log files associated with OpsCenter database Troubleshooting purpose
OpsCenter Sybase database activity.
OpsCenter log file

/opt/SYMCOpsCenterServer/db/log/ dbserver.log
/opt/SYMCOpsCenterServer/db/data/ OpsCenter Sybase database transaction files. vxpmdb.log Note: Do not change this log file.
About log files associated with OpsCenter Web server

Table 3-19 lists the log files that are associated with the OpsCenter Web server. Table 3-19 Log files associated with the OpsCenter Web server Troubleshooting purpose
OpsCenter Web GUI application activity (stdout).
OpsCenter log directory

/opt/SYMCOpsCenterWebServer/logs
About log files associated with VxUL and other components

Table 3-20 lists the log files that are associated with VxUL and other components. Table 3-20 Log files associated with VxUL and other components Troubleshooting purpose
PBX activity. NBSL activity.
OpsCenter log file

/opt/VRTSpbx/log/50936-103-*.log /opt/openv/logs/51216-132-*.log
219
Table 3-20
Log files associated with VxUL and other components (continued) Troubleshooting purpose
OpsCenter Agent activity.
OpsCenter log file

/opt/SYMCOpsCenterAgent/logs/ 51216-146-*.log /opt/SYMCOpsCenterGUI/logs/ 51216-147-*.log /opt/SYMCOpsCenterServer/logs/ 558330-148*.log
OpsCenter Web GUI activity.
OpsCenter server activity.
220
Chapter
Understanding OpsCenter settings


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
222
Understanding OpsCenter settings About the settings in OpsCenter
About the settings in OpsCenter

This section describes the various OpsCenter settings. An OpsCenter Admin can configure these settings using the OpsCenter console. The normal users can view or access the information that is relevant only to their profiles, which the OpsCenter Admin has set. Following are the various settings that you can configure in OpsCenter. Table 4-1 Name of the setting Settings in OpsCenter Lets you... Reference topic
User Preferences Add user-specific details and create user See Setting user profiles. preferences on page 223. NetBackup Add NetBackup master servers and their See Configuring data properties to collect data from it. collection for NetBackup on page 270. Create Agent and Data Collectors to collect data from non-NetBackup products. See Managing OpsCenter Agents on page 264.
Agent
License
Manage permanent or demo license keys. See Adding license keys on page 226. Specify when you want to purge the data See Configuring data purge that is collected from various products. settings on page 227. Configure the SMTP server details that See Configuring SMTP you need while sending reports or alerts server on page 228. through emails. Configure Symantec ThreatCon feature in OpsCenter. The Symantec ThreatCon feature is used to show how secure or vulnerable your network is. See Configuring Symantec ThreatCon feature in OpsCenter on page 229.
Data Purge
SMTP Sever
ThreatCon
Host Alias
Add aliases for hosts.
See Adding host aliases on page 230.
Object Merger
Configure OpsCenter to merge the objects See Merging objects (hosts) that represent the same backup client, on page 231. but registered as separate objects
Understanding OpsCenter settings Setting user preferences
223
Table 4-1 Name of the setting

Tape Library
Settings in OpsCenter (continued) Lets you...

Modify tape library information
Reference topic
See Merging objects (hosts) on page 231. See Copying user profiles on page 232.
Copy User Profile Configure OpsCenter to copy a user's profile to another user. Report Export Location Object Type
Specify the location where the exported See Setting report export reports are stored. location on page 233. Add new object types and attributes. See Managing Object Types on page 233. See Managing views on page 311. See Managing users on page 235. See Managing recipients on page 243.
Views
Create and manage OpsCenter views.
Users
Manage users and user groups.
Recipients
Manage Email and SNMP recipients.
Currency Settings
Manage the currency settings that appear See Setting a default in cost reports. You can select a currency currency for cost reports from the global currency list and set it as on page 249. default. Create cost variables. See Managing Cost Variables on page 251. See Managing cost formulae on page 254. See Managing cost estimation on page 255.
Cost Variables
Cost Formulae
Create cost formulae.
Cost Estimation
Manage cost estimation
Setting user preferences

In OpsCenter, you can set your preferences, such as default locale or time zone and personal details, such as email ID or name. You can also change your password using the User Preferences tab, if your user account belongs to the OpsCenterUsers domain.
224
To set user preferences
1 2
In the OpsCenter console, click Settings > User Preferences. The user preferences options are organized in the General and My Profile tabs. Click the General tab to set the following user preferences:
Default Locale Select a locale of your choice from the drop-down list. For example, if you select English as a default locale, all OpsCenter GUI screens use English as a default language. Select a preferred time zone - either OpsCenter Server time zone or any other time zone from the Other drop-down list. OpsCenter displays time on the GUI screens according to the selected time zone. Enter the time that is used as the start time of a day in reports. Report data is grouped depending on this start time. Select this check box if you do not want to automatically refresh the OpsCenter GUI. By default, the auto-refresh option is enabled. Auto Refresh Interval (Minutes) Enter auto-refresh interval in minutes. For example, if you want to refresh the OpsCenter GUI to show updated data after every 5 minutes, enter five in the Auto Refresh Interval text box.
Data Display Time Zone
Start 24 Hour Day at Disable Auto Refresh
Click Save.
225
Click the My Profile tab to view the following options: You can modify some of the options.
User Name Password Displays the user name. The OpsCenter security admin sets a default password for each user when it creates the profiles. The users that belong to the OpsCenterUsers domain can change their passwords after logging on . To change password, click the Change Password link. See Changing your password on page 225. The users from other domains cannot change their passwords using this option. User Role Domain Name Email Address The role of this user Name of the domain to which this user belongs The email address of this user
In General details, you can see the following information

First Name Last Name Cost Center Department Work Number Mobile Number Pager Number Displays the first name of the user Displays the last name of the user Displays the cost center user belongs to Displays the department of the user. Displays the work number of the user. Displays the mobile number of the user. Displays the pager number of the user.
Click Save.
Changing your password

It is recommended that you change the administrator-assigned password the first time you logon to Symantec OpsCenter console and then change it at regular intervals thereafter.
226
Understanding OpsCenter settings Managing licenses
To change the password with which you log on to OpsCenter
1 2 3
In the OpsCenter console, click Settings > My Profile. In the My Profile dialog box, click Change Password. 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.
Click Save.
Managing licenses
This section provides procedures to manage license keys from the OpsCenter. To use the advanced features that are not available in Symantec OpsCenter, you need to use a license key and enable Symantec OpsCenter Analytics. See About Symantec OpsCenter on page 19. See Adding license keys on page 226. See Viewing license keys on page 227. See Deleting license keys on page 227.
Adding license keys

An OpsCenter administrator can install OpsCenter license keys to activate additional 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 2 3 4 5
Logon to the OpsCenter server host as admin. In the console, click Settings > Configuration . Click the License tab. Click Add. On the Add License Key pop-up screen, enter a license key and click OK.
Understanding OpsCenter settings Configuring data purge settings
227
Viewing license keys

You can view the license keys that are installed on the OpsCenterserver host. To view OpsCenter license keys
1 2 3
Logon to the OpsCenterServer host as admin. In the console, click Settings > Configuration. Click the License tab.
Deleting license keys

You can remove one or more Symantec OpsCenter Analytics license keys from the OpsCenter Server, on which you are connected as an administrator. To delete Symantec OpsCenter Analytics license keys
1 2 3 4 5
Log on to the OpsCenter Server host as admin. In the OpsCenter console, click Settings > Configuration. Click the License tab. Select the check box in front of the license key that you want to delete. Click Delete.
Configuring data purge settings

You can configure the OpsCenterServer retention periods for the data types that are 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 2 3
Log on to the OpsCenter console as admin. In the OpsCenter click Settings > Configuration. Click the Data Purge tab. By default, data purge is enabled.
228
Understanding OpsCenter settings Configuring SMTP server
Edit the default data purge settings for the following data:
Backup Job Set the number of days after which you want to purge the backup jobs. The number of days set for backup logs should be less than or equal to the number of days set for backup jobs. In other words, logs can be purged earlier than their respective jobs, or they can be purged at 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 10 days and for Backup Logs are five days. The backup logs are purged after five days but the related jobs are still present. Because, the backup jobs are set to be purged after 10 days. Thus, the logs of such jobs are collected again by the OpsCenter Agent. Backup Log Set the number of days after which you want to purge the backup logs. To retain Tape Drive History logs
Tape Drive History Media History Alert
To retain Media History logs Enter the number of days for which you want to retain the alert data. Alert data older than this number is purged from the OpsCenter database.
5 6
In the Time of Purge text box, enter the time of day (in 24-hour clock format) When you want to purge the data. Click Save.
Configuring SMTP server

This section provides the procedure to configure the SMTP server that you can use for sending emails and alerts. To configure SMTP server settings for OpsCenter
1 2
Logon to the OpsCenter server as admin. In the OpsCenter console, click Settings > Configuration.
Understanding OpsCenter settings Configuring Symantec ThreatCon feature in OpsCenter
229
Click SMTP Server. OpsCenter uses these global server settings to send email notifications using the SMTP server that you specify..
Enter the following information:

SMTP server Name Enter the SMTP (Simple Mail Transfer Protocol) Server host name that you have entered while installing the OpsCenter application. Notifications of alerts that are generated in OpsCenter are sent using this SMTP server. SMTP server port Enter the SMTP (Simple Mail Transfer Protocol) Server port number. Enter the name that is associated with the email ID. For example, Backup Reporting Department Specify the email ID to receive any replies to alerts or the reports that were sent by OpsCenter. Some SMTP servers may require user name and password credentials to send email. Enter the user name. Server User Password Some SMTP servers may require user name and password credentials to send email. Enter the password for this user account.
Sender Display Name
Sender Display Email Address Server User Name
Click Save.
Configuring Symantec ThreatCon feature in OpsCenter

This section provides information on how to configure the Symantec ThreatCon feature in OpsCenter. The Symantec ThreatCon feature is used to show how secure or vulnerable your network is.See About the Symantec ThreatCon pane on page 53. Use the following procedure to enable or disable the Symantec ThreatCon feature. The ThreatCon feature is enabled by default. To disable ThreatCon, uncheck the box next to Enable ThreatCon Collection
230
Understanding OpsCenter settings Adding host aliases
To configure Symantec ThreatCon feature on Windows for OpsCenter
1 2 3 4
Log on to the OpsCenterServer with administrator privileges. In the OpsCenter, click Settings > Configuration. Click ThreatCon. Edit the following default information:
Enable ThreatCon Collection Disable or enable the ThreatCon data collection using this check box.
Polling Interval Set the minutes for Polling Interval. Server Name
Note: The proxy server configuration is not mandatory. Enter the

following proxy server details if you want to use it for accessing the latest ThreatCon ratings, if the default network is down. Enter the proxy server name.
Port User Name Password
Enter the port number to connect to the proxy server. Enter the user name of the proxy server. Set the password for the user account that you use to connect to the proxy server.
Click Save.
Adding host aliases

This section provides the procedures to add aliases for hosts. The hosts primary alias is displayed in all console functions and reports. Other host 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 DNS names or with the names by which they are known to applications such as NetBackup and Backup Exec. For example, if you use an alias that is unknown to OpsCenter, the explorer stops collecting information from the OpsCenter host and instead attempts to collect data from a host with the alias name.
Understanding OpsCenter settings Merging objects (hosts)
231
To add a host alias
1 2
In the OpsCenter console, click Settings> Configuration > Host Alias. From the drop-down list select a host name or type a host name, and Click Show Alias. All the existing aliases are displayed.
3 4 5
Click Add Alias. Enter the alias name for the host that you have selected from the drop-down list. click Save
Merging objects (hosts)

OpsCenter provides a facility to merge objects (hosts) that represent the same master server, media server, backup client, but registered as separate objects (hosts). Using the OpsCenter UI, you can merge only one object into other, at a time. In OpsCenter, you can merge objects (hosts) representing the same backup client. Caution: Object merging is not reversible. To merge two objects
1 2 3 4 5 6 7
Logon to the OpsCenter Server host with administrator privileges. In the OpsCenter console, click Settings > Configuration > Object merger. Select the Host Type: Master Server, Media Server, or Client. Select the Source Host from the drop-down list. An auto-suggest feature is available. Select the Target Host from the drop-down list. An auto-suggest feature is available. Click Validate Object Merging. You can view the snapshot of the selection that you have made earlier. To modify the Source Host or Target Host click Back. To begin the merge click Start Merge Repeat these steps if you want to merge more objects.
232
Understanding OpsCenter settings Modifying Tape Library information
Modifying Tape Library information

OpsCenter 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, slot count of the tape drives the data collector uses. To modify tape library information in OpsCenter
1 2 3 4 5
Log on to the OpsCenterServer with administrator privileges. In the OpsCenter, click Settings > Configuration. Click Tape Library. You can view the list of the tape libraries in OpsCenter. Select the check box next to tape library, for which you want to edit the information. Edit the following information:
Type Serial Number Manufacturer Alias Slot Count Select the type of tape library from the drop-down list. Enter the serial number of the tape library Enter the manufacturer of the tape library. Enter the alias for the tape library. Enter the slot count you want for the tape library.
Click Save.
Copying user profiles

Most 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 profile functionality, you can copy information from one user account to another. Copy user profile
1 2 3 4 5 6
Logon to the Symantec OpsCenter Server with administrator privileges. In the OpsCenter console, click Settings > Configuration > Copy User Profile Select the source user account from the From User drop-down list. Select the target user account from the To User drop-down list. In the Copy Items options, select the items you want to copy, for example reports or cost rates and formulae. Click Next
Understanding OpsCenter settings Setting report export location
233
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 are implicitly copied.
Click Copy
Setting report export location

In 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 defined any location. To set reports for exporting
1 2 3 4
Log on to the Symantec OpsCenter Server with administrator privileges. In the OpsCenter console, click Settings > Configuration > Report Export Location In the Report Export Location box type the directory where you want to save the reports. Click Save.
Managing Object Types

In OpsCenter you can add or edit attributes of predefined object types. You can also add new object types and attributes for those new object types. To add an object type
1 2 3 4 5
Logon to the Symantec OpsCenter Server with administrator privileges In the OpsCenter console, click Settings > Configuration > Object Types. Click Add. Enter the name in the Add Object Type pop-up screen. Click OK.
See Modifying object types on page 234. See Deleting object types on page 234. See Adding attributes on page 234. See Deleting attributes on page 235.
234
Understanding OpsCenter settings Managing Object Types
Modifying object types

You can only modify the name of an object type that you have created. You cannot modify the name of the predefined objects in the drop-down list. To modify an object type name
1 2 3
Logon to the Symantec OpsCenter Server with administrator privileges. In the OpsCenter console, click Settings > Configuration > Object Type. 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 rename the predefined object types.
4 5
Click Add. Add
Deleting object types

You can only delete an object type that you have created. You cannot delete the predefined objects in the drop-down list. To delete object types
1 2 3 4
Logon to the Symantec OpsCenter Server with administrator privileges In the OpsCenter console, click Settings > Configuration > Object Types. Select the object type from the drop-down list. You can delete the object types that you have created. You cannot delete predefined object types. Click Delete
Adding attributes
You can add attributes to all object types. To add attributes
1 2 3 4
Logon to the Symantec OpsCenter Server with administrator privileges In the OpsCenter console, click Settings > Configuration > Object Types. Select the object type from the drop-down list and in Attributes section, click Add. Enter the name of the attribute and click OK.
Understanding OpsCenter settings Managing users
235
Deleting attributes
You can delete attributes that are added to an object type. To delete attributes
1 2 3 4
Logon to the Symantec OpsCenter Server with administrator privileges In the OpsCenter console, click Settings > Configuration > Object Types. 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. Click Delete.
Managing users
After you install Symantec OpsCenter, you need to create user accounts. The Symantec Product Authentication Service validates credentials of OpsCenter users based on Windows, NIS, or private domains. See About user access rights on page 235. See Adding new users on page 239. See Resetting user password on page 240. See Adding user groups on page 242.
About user access rights

This section provides information on OpsCenter users and the functions that they can perform in the OpsCenter GUI.
About OpsCenter UI functions

Table 4-2 provides details of the OpsCenter UI functions that you can perform. Table 4-2 OpsCenter UI functions
OpsCenterfunctions Tasks
User Management 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
236
Table 4-2
OpsCenter UI functions (continued)
OpsCenterManagement The OpsCenter Management function includes the following tasks:

Add, Update, Delete Master Server Add, Update, Delete OpsCenter Agents Set default currency, SNMP, SMTP server
NetBackup Configuration Management
The NetBackup Configuration Management function includes the following tasks:
Add, update, delete NetBackup entities: Host Properties, Policy, Media and Devices, and others
NetBackup Operations 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
Backup and Recovery
The Backup and the Recovery function includes the following tasks:

Execute manual backups Search and restore files, folders, application (Oracle, SQL Server, and Exchange Server)
Views Management
The Views Management function includes the following tasks:

Create, update, delete OpsCenter views and nodes Assign Read / Write permissions to users on OpsCenter views and nodes
All Views Read
The NetBackup Operations function includes the following tasks:
View OpsCenter views and nodes
Report Execution
This function includes the following tasks:

Execute report templates and public custom reports Schedule canned and public custom reports Create, update Dashboard
237
Table 4-2
OpsCenter UI functions (continued)
Custom Reports This function includes the following tasks:

Create, update, delete custom reports Make custom reports public and/or private
Custom SQL Reports
This function includes the following tasks:
Create, update, delete custom SQL reports
Monitoring
Monitoring includes the following tasks:
View entities ( Dashboards, Summary, Details): Job, Policy, Media, Alerts, Drives, Others
Alert Management
The Alert Management function includes the following tasks:

Create, update, delete alert policies Assign, acknowledge, clear alerts
About OpsCenter user roles

OpsCenter users are categorized as follows:
Security Administrator This is a super admin user who can perform all OpsCenter functions including 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 in OpsCenter. Administrator This user can perform all OpsCenter functions except for user management. The OpsCenter Administrator cannot create, edit, or delete users.
Note: A NOM user becomes an Administrator in OpsCenter.

Operator 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.
238
Analyst
The role of this user is to mainly analyze the operational and business-level reports. This user cannot perform functions, such as user management or backup & recovery. The Analyst has the Read permission on all views.
Note: A VBR read-only admin becomes an Analyst in OpsCenter.

Reporter The role of this user is to mainly generate the operational and business-level reports for further analysis.
Note: A VBR user becomes a Reporter in OpsCenter.
About OpsCenter user roles and their functions

Table 4-3 lists the OpsCenter user roles and the OpsCenter UI functions that these users can perform. Table 4-3 OpsCenter function
User Management OpsCenter Management NetBackup Configuration Management NetBackup Operations Backup and Recovery Views Management
User roles Administrator

Y
Security Administrator
Y
Operator
N
Analyst
N
Reporter
N
N (Restricted to only permitted entities through Java View Builder)
N (Restricted to only permitted entities through Java View Builder) Restricted to only permitted entities
All Views Read
Restricted to only permitted entities
239
Table 4-3 OpsCenter function

Report Execution Custom Reports Custom SQL Reports Monitoring Alert Management
User roles (continued) Administrator

Y
Security Administrator
Y
Operator
Y
Analyst
Y
Reporter
Y
Y Y
Y Y
Y Y
Y Y
Y Y
Y represents Yes, which means that the users of this role can perform this particular OpsCenter function. N represents No, which means that the users of this role can perform this particular OpsCenter function.
Viewing the list of existing users

You can view a list of OpsCenter users and their information such as, name, user name, access level, authentication domain, and so on. The user information is arranged in a tabular format. You can sort the table by user attributes To view OpsCenter user account information
1 2 3
Logon to the Symantec OpsCenter host with administrator privileges. In the Symantec OpsCenter console, click Settings > Users. Click Users to view the list of users.
Adding new users

You can either add the existing users that are discovered from various domains to OpsCenter or create users in the private OpsCenterUsers domain. To add a new user to OpsCenter
1 2 3
Log on to the OpsCenter host with administrator privileges. In the OpsCenter console, click Settings > Users. On the Users tab, click Add .
240
4 5
Select the user creation type: New User or Existing Domain User. 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 237. If you have selected the Existing Domain User option, you do not have to enter Password and Confirm Password. If you have selected the New User option, specify the password, and enter it once again for confirmation.
Click Save.
Editing users
You can edit the existing users. To edit an existing user
1 2 3 4 5
Logon to the OpsCenter host with administrator privileges. In the OpsCenter console, click Settings > Users. On the Users tab, click the check box in front of the user that you want to edit. Click Edit. 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 240.
Click Save.
Resetting user password

This section describes how to reset a user password. The Reset Password functionality is applicable only for OpsCenter users.
241
To reset a user password
1 2 3 4 5 6 7
Logon to the OpsCenter host with administrator privileges. In the OpsCenter console, click Settings > Users. On the Users tab, click the check box in front of the user for whom you want to reset the password. Edit. In the General Details pane, click Reset Password. On the Reset Password page, enter the new password and confirm password for the selected user. Click Save.
Deleting users
You 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
1 2 3 4 5
Logon to the OpsCenter host with administrator privileges. In the OpsCenter console, click Settings > Users. Click Users. Check the box next to the user account you want to delete. Click Delete.
Viewing user groups

This section provides the procedure to view the existing user groups. To view a user group
1 2 3
Logon to the Symantec OpsCenter host with administrator privileges. In the Symantec OpsCenter console, click Settings > Users. Click User Groups to view the list of user groups.
242
Adding user groups

If you want to give the same privileges to multiple users, add them to a single user group. The same access rights on views are attributed to all users in the user group . To create an OpsCenter user group
1 2 3 4 5 6 7 8 9
Logon to the OpsCenter host with administrator privileges. In the OpsCenter console, click Settings > Users. Click User Groups. Click Add. On the User Groups tab, enter the name of the group and description. In the List of Users pane, click Add to open the Add Users pop-up screen. On the Add Users pop-up screen, select the users that you want to add to this user group. Click OK. On the User Group tab, click Save.
Editing user groups

You can modify an existing user group. To edit a Symantec OpsCenter user group
1 2 3 4 5 6 7 8
Logon to the OpsCenter Server host with administrator privileges. In the OpsCenter console, click Settings > Users. Click User Groups . Select the check box in front of the user group that you want to edit. Click Edit. Modify the user group name or description. Add or delete the users using the List of Users pane and Add Users pop-up screen. Click Save.
Deleting user groups

You can delete a user group that you no longer need.
Understanding OpsCenter settings Managing recipients
243
To delete a Symantec OpsCenter user group
1 2 3 4 5
Logon to the OpsCenter Server host with administrator privileges. In the OpsCenter console, click Settings > Users. Click User Groups. Select the check box next to the user groups that you want to delete. Click Delete.
Managing recipients
You can specify the recipients to whom you want to send alert notifications or email reports. Note: Make sure that the mail server is configured to send emails. See Configuring SMTP server on page 228. See Creating email recipients on page 245. See Creating SNMP trap recipients on page 247.
Viewing email recipients

This section provides the procedure to view the available email recipients.
244
To view the email recipients
1 2
Logon to the OpsCenter Server host. In the OpsCenterconsole, click Settings > Recipients. By default, the Email tab is selected. All email recipients are displayed on this tab. The following email recipient details are displayed in a table:
Recipient Name Email Address Active Name of the email recipient
Email ID of the recipient
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 Adding Email Recipients pop-up screen, when emails are sent.
Description Description about the email recipient
Viewing SNMP trap recipients

This section provides the procedure to view the available SNMP trap recipients. To view the SNMP trap recipients
1 2 3
Log on to the OpsCenter Server host. In the OpsCenterconsole, click Settings >Recipients. Click SNMP. The following trap recipient details are displayed in a table:
Recipient Name Name of the SNMP trap recipient
SNMP Host Name of the SNMP host Port Active Port number on the SNMP host where you want to send traps 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 Adding Trap Recipients pop-up screen, when alert policies are configured. Description Description about the trap recipient
245
Creating email recipients

This section describes how to create email recipients. To create email recipients
1 2 3
Logon to the OpsCenter Server host with administrator privileges. In the OpsCenter console, click Settings > Recipients. In the Email tab, click Add to create new email recipients.
246
Enter the following information:

Email Recipient Name Enter the name of the official whom you want to notify about an alert or send reports. Enter the email ID of the official, to which alert notifications or reports are sent. Select this check box if you want the recipient to receive alert notifications and reports by emails. Enter a short description about the alert or report so that recipients can understand. Select this check box to activate the Alert Notification Delivery Limit settings. If you do not select this check box, Maximum Number of Messages, Delivery Time Span, and Reset Message Count After Time are not taken into account when notifications are send. Enter the maximum number of notifications that you want to receive within the specified Delivery Time Span. Enter the time duration in hours, minutes, or seconds, during which notifications are sent. Once the message count reaches Maximum Number of Messages, the Notification Manager blocks the delivery of any new notifications to the associated recipient for the time period that is specified for Reset Message Count After Time.
Email Address
Active
Description
Activate Delivery Limit
Maximum Number of Messages Delivery Time Span
Reset Message Count After Enter the time period in hours, minutes, or seconds, Time during which notifications are blocked if the message count has reached Maximum Number of Messages. Once this time period is over, Maximum Number of Messages is reset and the Notification Manager starts sending notifications for the specified Delivery Time Span.
Note: For example, if Maximum Number of Messages =

10, Delivery Time Span = 30 Minutes, and Reset Message Count After Time = 2 Hours, Alert Manager sends messages until message count reaches 10 in 30 Minutes. Once it has sent 10 messages, it blocks the delivery of new messages for next two Hours. After two hours, Alert Manager once again starts sending messages until message count reaches 10.
Click Save.
247
Creating SNMP trap recipients

Traps, (interrupts), are signals sent to inform the programs that an event has occurred. In OpsCenter, traps are the notifications that are sent to a specified SNMP host or group of hosts when a condition is met. A trap recipient is a host that receives notifications in the form of SNMP traps when an alert condition is met. For example, a trap is sent after an alert was generated as a result of failure of communication between the OpsCenter Agent and Server. For more details, refer to the About using SNMP with OpsCenter section. To create SNMP recipients
1 2 3 4 5
Log on to the OpsCenter Server host with administrator privileges. In the OpsCenter console, click Settings > Recipients. Click SNMP. Click Add In the SNMP Attributes page enter the following information:
248
Recipient Name SNMP Host SNMP Port
Enter the name of the SNMP trap recipient. Enter an SNMP host, to which you want to send traps. Enter the port number on the SNMP host where you want to send traps. Select this check box if you want the recipient to receive notifications by SNMP traps. Enter a short description about the traps.
Active
Description
Activate Delivery Limit Select this check box to activate the Alert Notification Delivery Limit settings. If you do not select this check box, Maximum Number of Messages, Delivery Time Span, and Reset Message Count After Time are not taken into account when notifications are send. The notifications are sent as soon as alerts are generated. Maximum Number of Messages Delivery Time Span Enter a maximum number of notifications that can be sent within the specified Delivery Time Span. Enter the time duration in hours, minutes, or seconds, during which notifications are sent. Once the message count reaches Maximum Number of Messages, Alert Manager blocks the delivery of any new notifications to the associated recipient for the time period that is specified for Reset Message Count After Time. Enter the time period in hours, minutes, or seconds, during which notifications are blocked if the message count has reached Maximum Number of Messages. Once this time period is over, Maximum Number of Messages is reset and Alert Manager starts sending notifications for the specified Delivery Time Span.
Reset Message Count After Time
Click Save.
Modifying Email or SNMP recipient information

Only OpsCenter administrator can modify email / trap recipient information. See Creating email recipients on page 245. See Creating SNMP trap recipients on page 247.
Understanding OpsCenter settings Managing cost analysis and chargeback for OpsCenter Analytics
249
To modify Email or SNMP trap recipient information
1 2 3 4
In the OpsCenter console, click Settings > Recipients. In the Email Recipients tab or SNMP Recipients tab, select email / trap recipient from the table, that you want to edit. On the modify email / trap recipient page, change email / trap recipient attributes and Alert Notification Delivery Limit Settings. Click Save.
Deleting Email or SNMP recipient

Only OpsCenter administrator can delete email or trap recipient. See Creating email recipients on page 245. To delete Email or SNMP trap recipient
1 2 3 4
In the OpsCenter console, click Settings > Recipients. In the Email Recipients tab or SNMP Recipients tab, select email / trap recipient from the table, that you want to delete. ClickDelete. Click Save.
Managing cost analysis and chargeback for OpsCenter Analytics

This feature is accessible only to Symantec OpsCenter Analytics users. In OpsCenter Analytics, you can choose the currency that you want to be displayed on cost reports. If you have OpsCenter administrator privilege, you can set multiple global currencies, one of which can be set as default currency. You can set the cost variable, cost formulae, and cost estimation that you want to run the cost reports. You cannot access the Settings > Chargeback feature if you do not have Symantec OpsCenter Analytics. This feature is disabled for unlicensed OpsCenter version.
Setting a default currency for cost reports

This section provides the procedure to set the default currency that you want to be displayed on OpsCenter cost reports.
250
Note: Setting the default currency gives you the flexibility of displaying cost report values in the currency of your choice. However, OpsCenter does not support conversion of currencies. To set the default currency
1 2
Logon to the OpsCenter Server with administrator privileges. In the console, click Settings > Chargeback. You cannot access the Settings > Chargeback feature if you do not have Symantec OpsCenter Analytics. This feature is disabled for unlicensed OpsCenter version.
On the Currency Settings tab, in the Default Currency drop-down list, all global 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 250.
Select the Currency Display Mode: Currency Code or Currency Symbol. For example, for US dollar currency, you can either select a currency code USD or symbol $, which appears on chargeback reports. Select the Display Currency Option in Cost Reports check box to show the default currency on the cost reports. Click Save.
5 6
Editing currency list

This section provides the procedure to edit the global currency list, which is made available when a default currency is selected to be displayed on OpsCenter cost reports. To edit currency list
1 2
Log on to the OpsCenter Server with administrator privileges. In the console, click Settings > Chargeback. If you have not entered the Symantec OpsCenter Analytics license key, you cannot access the Settings > Chargeback feature. This feature is disabled for unlicensed OpsCenter version.
On the Currency Settings tab, click Edit Currency List.
251
On the Edit Currency List pop-up screen, select currencies from the Global Currency list, which you want to make available for selection in the Default Currency drop-down list on the Currency Settings tab. See Setting a default currency for cost reports on page 249.
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 User Currency list.
Click OK.
Managing Cost Variables

You can create cost variables based on various parameters to determine cost of various services. See Creating cost variables on page 251. See Modifying cost variables on page 253. See Deleting cost variables on page 253.
Creating cost variables

Cost reports in OpsCenter Analytics are based on the user-defined variables that define the cost of various services. Typically, each service is represented by one variable that reflects the cost of the service, for example $1.00 per backup job. However, you can account for rate changes in one of two ways: by creating two variables for the same service (which you can include in a single cost formula later) or by incorporating both rates into a single variable. For example, a single variable can incorporate the rate of $1.00 per backup job until 31 December 2004 and the rate of $1.25 per backup job starting on 1 January 2005. Note: To generate deduplication savings reports, you must create a cost variable with the Protected Job Size (GB) metric. To set up OpsCenter to run cost reports, you need to create the variables that define the cost of various services. To create a cost variable
1 2
Log on to the OpsCenter Server with administrator privileges. In the console, click Settings > Chargeback. Click Cost Variable.
252
3 4 5
On the Cost Variable tab, click Add. Enter the variable name. Select any of the following variable metrics from the drop-down list:

Daily Occupancy Job Count Job Size Protected Job Size
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 variable metric.
Job Type Measure costs for a specific type of job, for example Backup or Restore. The default option is All. Measure costs for the jobs that use a specific policy type. In NetBackup, the policy type determines the type of clients that can be part of the policy and, in some cases, the types of backups that can be performed on the clients. Examples include DB2, Sybase, and MS-Exchange-Server. The default policy type is All.
Job Policy Type
Job Transport Type Measure cost for a specific transport type for example, LAN (Local Area Network) or SAN (Storage Area Network). The default option is All. Job Storage Type Measure cost for a specific storage type for example, tape or disk. OpsCenter supports NetBackup's disk-based data protection feature, which enables you to select disk as a storage type, when a cost variable is created. The default option is All.
Add one or more date ranges and associated rates using the drop-down lists for Month, Day, Year, and Time and by typing a cost per service unit (such as backup jobs or backed-up GB) in the Rate field. Add at least one date range.
253
Optionally, to add more date ranges, click Add New Range. This can be useful for defining multiple date ranges to represent historical or future changes in service costs. You can also modify the variable later to add or delete date ranges as costs change.
Click OK . You can now use the variable you created to build the formulas that form the basis for cost reports. See Creating cost formulae on page 254.
Modifying cost variables

You can update cost variables and formulas without having to recreate the reports that rely on them. For example, you can modify the name, date ranges and rates of a variable to reflect changing conditions in your enterprise. To modify a cost variable
1 2
Logon to the OpsCenter Server with administrator privileges. In the console, click Settings > Chargeback. Click Cost Variables.
3 4 5 6
Select the check box in front of the variable name that you want to modify. Click Edit. Modify the cost variable details. Click OK.
Deleting cost variables

You can variables you no longer need. Deleting a cost variable removes it permanently from the database, and you must update any formulas that use the variable. To restore a deleted variable, you must recreate the variable manually. To delete a cost variable
1 2 3 4 5
Log on to the OpsCenter Server with administrator privileges. In the console, click Settings > Chargeback. Click Cost Variables. Select the check box in front of the cost variable that you want to delete. ClickDelete.
254
Managing cost formulae

Based on cost variables you can create the cost formulas that you can use to generate cost reports. See Creating cost formulae on page 254. See Modifying cost formulae on page 254. See Deleting a cost formulae on page 255.
Creating cost formulae

After you create cost variables, create the formula that define the cost of various services to run cost reports. To create a cost formula
1 2
Logon to the OpsCenter Server with administrator privileges. In the console, click Settings > Chargeback. Click Cost Formulae.
3 4 5
On the Cost Formulae tab, click Add. Enter the name of the formula. Select a cost variable from the drop-down list. You need to select at least one cost variable.
Optionally, to define formulae containing more than one variable, click Add new cost variable. Select a different variable from the nes drop-down list. You can also modify the formulae later to add or delete variables.
Click OK. You now can use the formula to create cost reports with which you can evaluate the cost of services and make decisions about what to charge for performing those services.
Modifying cost formulae

You 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 that rely on them. For example, you might want to update a formula that is called RecoveryRate to reflect a change in the hourly rate that is charged for recovery operations.
255
To modify a cost formulae
1 2
3 4 5 6
On the Cost Formulae tab, select the cost formulae that you want to modify. Click Edit. Modify the details of the cost formula. Click OK.
Deleting a cost formulae

You can also delete formulae that you no longer need. Deleting a cost formula removes it permanently from the database. To delete cost formulae
1 2
3 4 5
On the Cost Formulae tab, select the cost formulae that you want to delete. Click Delete. On the confirmation dialog box, click OK.
Managing cost estimation

The Formula Modeling Tool offers an easy way to estimate baseline rates for the IT services you provide. Using historical data, it provides you with an estimate of how much it costs your organization to provide a specific kind of service. For example, suppose you anticipate spending $500,000 over the next year to provide backup services throughout your enterprise. By inserting the metric Daily Occupancy into the tool, along with the amount $500000, you can obtain an estimate per kilobyte that is based on the backup activity you performed last year. See Creating cost variables on page 251. See Creating cost formulae on page 254.
256
To estimate baseline (chargeback) costs using the Formula Modeling Tool
1 2
Logon to the OpsCenter Server with administrator privileges. In the console, click Settings > Chargeback. Click Cost Estimation.
3 4
Select a Report Grouping parameter to define the models scope: Use the following Metric Selection parameters to specify the metric whose rate you want to estimate:
Metric Select a metric, or category of service. Example: Daily Occupancy Amount Specify the total amount of money, in dollars, you expect to charge for service within that category in a given time frame. Examples: $50000, $10000, or $10000.00
Use the following Time Frame parameters to define the time intervals for which data is modeled:
257
Time Frame
Defines the beginning and end of the time interval the estimate must cover. You can choose either absolute dates, meaning that the estimates contents remains static whenever you display it, or relative dates, meaning that the estimate always reflects data that is collected over the most recent time interval. Select one of the following: Click Absolute to configure an absolute time frame. Then select a start time (month, day, year, and time of day) using the From drop-down lists, and a stop time using the To drop-down lists. The estimate reflects data from the time period between the start and the end dates. Example: From MAR 1 2004 12:00 A.M. to APR 30 2004 12:00 A.M. Example: Unbounded to APR 30 2004 12:00 A.M. Click Relative to configure a relative time frame. Then select a time interval using the Last drop-down lists. The estimate reflects the data that is collected within the specified time period, up to the current time. Examples: Last 21 Days or Last two Quarters The Relative setting is especially useful for the estimates that you plan to generate on a regular basis. Such estimates always reflect the data that is collected over the most recent time interval.
Click Run Model to input different values into the model, or to run a new model.
258
Chapter
Understanding data collection


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 OpsCenter

OpsCenter provides extensive reporting on the data that is collected from backup and archiving products. An OpsCenter Agent comprises product-specific data collectors that collect data from point products and return it to the OpsCenter Server. Note: Only one OpsCenter Agent can be installed on a single host.
260
Understanding data collection About data collection in OpsCenter
An OpsCenter Agent consists of the data collectors that can collect data from the following backup and archiving products:
Symantec Backup Exec (Windows only) Note: To collect data from Backup Exec Server host, you need to install the OpsCenter Agent on a Windows host. Symantec NetBackup PureDisk Symantec Enterprise Vault (Windows only) Note: To collect archive data from Enterprise Vault, you need to install the OpsCenter Agent on a Windows host. IBM Tivoli Storage Manager (TSM) EMC Legato Networker
See Configuring data collection for NetBackup on page 270.
About backup and archiving products supported by Symantec OpsCenter

This section lists the backup and archiving products that OpsCenter supports. Note that with the licensed version of OpsCenter, you can do advanced reporting from the data that is collected from all of these products. With the unlicensed version, you cannot collect data from third-party products like IBM Tivoli Storage Manager (TSM) and EMC Legato NetWorker. Warning: Always refer to the OpsCenter sections of the NetBackup release notes for any last-minute changes to the information that is presented in this document. The release notes for your release of OpsCenter also include any restrictions or limits for OpsCenter. Table 5-1 lists the backup and archiving products that OpsCenter supports.
261
Table 5-1
Backup and archiving products supported by Symantec OpsCenter Versions

6.0 MP7 and higher versions, 6.5 and higher versions, 7.0

Symantec NetBackup
Support level
All supported NetBackup platforms (except 7.0) by remote agent
Note: NBU 7.0 does not require any

Agent. Native agent for Windows 2003 (SP2 & R2), Windows 2008 (SP2 & R2), and Solaris 9, 10
Symantec NetBackup PureDisk Symantec Backup Exec
6.2, 6.2.2, 6.5, 6.5.1, 6.6
PureDisk supported platform (PDOS) by remote agent
10d, 11d, 12.0, 12.5
All supported Symantec Backup Note: OpsCenter does not Exec platforms by remote agent. support Symantec Backup Native agent on backup servers on Exec running on NetWare. Windows 2003 (SP2 & R2), 2008 (SP2 & R2)
7.5, 8.0
All supported Symantec Enterprise Vault platforms by remote agent Native agent on Microsoft SQL Server 2005 or 2008 (where Enterprise Vault database resides) on Windows 2003 (SP2 & R2), 2008 (SP2 & R2).
EMC Legato NetWorker
7.3
Native agent on backup servers on Windows 2003 (SP2 & R2), 2008 (SP2 & R2) and Solaris 9/10 Data collection is possible only with a licensed version of OpsCenter.
IBM Tivoli Storage Manager (TSM)
5.3, 5.4, 5.5
All supported TSM platforms by remote agent Native agent for backup server on Windows 2003 (SP2 & R2), 2008 (SP2 & R2) and Solaris 9/10 Data collection is possible only with a licensed version of OpsCenter.
262
About OpsCenter Agents

The OpsCenter Agent collects data from various Symantec and third-party backup and archiving products. These products can reside on the OpsCenter Agent host or on remote hosts. For more details on OpsCenter Agent installation and deployment scenarios, refer to the Installing Symantec OpsCenter chapter. Note: When you install the OpsCenter Server,OpsCenter Integrated Agent is also installed and configured, which you can use to collect only PureDisk data. To collect PureDisk data, you do not need to manually install or configure OpsCenter Agent. You cannot delete the Integrated Agent. You can collect PureDisk data only through the OpsCenter Integrated Agent.
About OpsCenter Agent logs

OpsCenter Agent logs are stored at the following location: InstallPath\Symantec\OpsCenter\Agent\logs 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 Collectors

The OpsCenter data collectors, collect data from backup and archiving product hosts. Each data collector collects data from a single product host. You can configure multiple data collectors on a single OpsCenter Agent host. You can create data collectors to communicate with the various products, such as Backup Exec, Enterprise Vault, or EMC Networker. These data collectors collect the specified data type as specified in the configuration. You can specify to collect all or some of the data types for that product. For example, Backup Exec data collector can collect Tape Drive Usage, Media, Policy and Schedule, Job, or Image.
263
Note: Error logs and skipped files are collected as part of job data. You can enable or disable a data collector. Table 5-2 lists the data collectors that you can configure in OpsCenter. Table 5-2 Data collector types Description
Data Collector type
Symantec Backup Exec Data Create this data collector to collect data from Backup Exec. Collector (Windows only) See Collecting data from Backup Exec on page 287. NetBackup PureDisk Data Collector Create this data collector to collect data from NetBackup PureDisk. See Collecting data from PureDisk on page 288.
Note: You can collect the PureDisk data only through the
OpsCenter Integrated Agent that is installed with the OpsCenter server. To collect PureDisk data, you need to create a data collector for the Integrated Agent. Symantec Enterprise Vault Data Collector (Windows only) TSM Data Collector Create this data collector to collect archive data from Symantec Enterprise Vault database See Collecting data from Enterprise Vault on page 292. Create this data collector to collect data from TSM. See Collecting data from IBM Tivoli Storage Manager on page 303. Legato Networker Data Collector Create this data collector to collect data from Legato Networker. See Collecting data from EMC Legato Networker on page 305.
Table 5-3 lists data types that are collected by OpsCenter data collectors from various products. Table 5-3 Backup product
Symantec Backup Exec
Data types collected Data type collected by OpsCenter

Tape Drive Information, Media, Policy and Schedule, Job Policy and Schedule, Job
Symantec NetBackup PureDisk
264
Understanding data collection Managing OpsCenter Agents
Table 5-3 Backup product
Data types collected (continued) Data type collected by OpsCenter

Archive Policy, Vault Store, Target, Archive Tape Drive Information, Media, Policy and Schedule, Job Tape Drive Information, Media, Policy and Schedule, Job
Symantec Enterprise Vault IBM Tivoli Storage Manager
Managing OpsCenter Agents

This section provides procedures to view, modify, create, and delete an OpsCenter Agent configuration. See About the OpsCenter Agent on page 29.
Viewing Agent status

Use this section to view general details and status of an OpsCenter Agent that you have configured in OpsCenter. To view Agent status
1 2
In the OpsCenter console, click Settings > Configuration > Agent. 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, which you have specified when you created this Agent. See Configuring an OpsCenter Agent on page 265.
Agent Host PBX Port Displays the name of the Agent host Displays the port number that is used to connect to the PBX on the OpsCenter Server Displays the network address of the OpsCenter Server
OpsCenter Server Network Address
Click Agent Summary by Data Collector Status, Agent Summary by Data Type Status, or Agent Summary by Data Collector Count tab to view the relevant details.
Understanding data collection Managing OpsCenter Agents
265
Configuring an OpsCenter Agent

This section provides the procedure to configure an OpsCenter Agent. To configure an OpsCenter Agent
1 2
In the OpsCenter console, click Settings > Configuration > Agent. Click Create Agent.
Agent Host Enter the host name where you want to configure the OpsCenter Agent Select the operating system family of the host where you want to install Agent. For example: Solaris Family or Windows Family Enter the port number that the OpsCenter Agent requires to connect to the PBX on the OpsCenter Server Select the network address from the drop-down list, using which you want to connect to the OpsCenter Server
Agent Operating System Family
PBX Port
OpsCenter Server Network Address
Click Save.
Modifying an Agent
This section provides the procedure to modify an OpsCenter Agent information. To modify an OpsCenter Agent
1 2 3 4 5
In the OpsCenter console, click Settings > Configuration > Agent. From the list of agents, select the check box in front of the Agent that you want to modify. Click Edit Agent. On the Edit Agent page, modify PBX port or OpsCenter Server Network Address. Click Save.
Deleting Agents
This section provides the procedure to delete an OpsCenter Agent.
266
Understanding data collection Managing Data Collectors
To delete an OpsCenter Agent
1 2 3
In the OpsCenter console, click Settings > Configuration > Agent. From the list of agents, select the check box in front of the Agent that you want to delete. Click Delete.
Managing Data Collectors

This section provides procedures to view, configure, modify, and delete a data collector.
Viewing Data Collector status

Use this section to view general details and status of a Data Collector that you have configured for an Agent. To view data collector status
1 2
In the OpsCenter console, click Settings > Configuration > Agent. On the Agent list, expand an Agent to view the Data Collectors that are configured for this Agent.
267
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 Collector details, which you have specified when you created this Data Collector. See Configuring a Data Collector on page 267.
Product Displays the name of the product type, for which this Data Collector is configured For example: Symantec Backup Exec Product Host Status Displays the name of the target host, which this Data Collector collects data from Displays the status of the Data Collector as Enabled or Disabled that you have set If the Data Collector status is disabled, the data is not collected from the target host.
Select the Data Collection Status tab. The following details are displayed:
Data Type List of the data types that this data collector collects from the product host The time when the full data was successfully collected from the product host
Last Successful Data Load Last Run Time Collection Status Last Exception Message
The time when this schedule was last run to collect data.
The collection status of the data collector for each data type, such as Complete, Failed, or Not Started The message that appeared at the time of the last exception
Configuring a Data Collector

OpsCenter is designed to provide extensive reporting on the data that is received from backup and archiving products. OpsCenter consists of Server, Agent, Java View Builder, and a console. The OpsCenter Agent contains product-specific data
268
collectors collecting data from the products and returning it to the OpsCenter Server. 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 265. To configure a data collector
1 2 3 4
In the OpsCenter console, click Settings > Configuration > Agent. On the Agent list, select a check box in front of the Agent, for which you want to configure a Data Collector. Click Create Data Collector. On the Create Data Collector: Product Selection page, enter the following information:
Select Product Select the name of the product from which you want to collect data. For example, Symantec Backup Exec. The options available in the Select Product drop-down list depends on the Agent operating system family that you have selected while creating the respective Agent. Target host name Enter the name of the product host from which you want to collect backup or archiving data.
Click Next. On the Create Data Collector: Details page, the Target Details, Configuration Settings, and Data Collection details are displayed.
Verify or modify the default Target Details:

Product Displays the name of the product from which this data collector collects data. You need to specify the product name when you create the data collector. For example: Symantec Backup Exec Displays the name of the product host from which this data collector collects data. You need to specify the product name when you create the data collector. By default, the data collector status is Enabled. You can disable the data collection by changing the status.
Target host name
Data Collector Status
269
Enter the data collector configuration settings. These settings vary depending on the data collector type you configure. For product specific configuration settings, refer to the respective data collector settings. See Collecting data from Backup Exec on page 287. See Collecting data from Enterprise Vault on page 292. See Collecting data from IBM Tivoli Storage Manager on page 303. See Collecting data from EMC Legato Networker on page 305.
Enter the following data collector settings:

Blackout Period Start Time Select the start time of a blackout period. The data is not collected during the time that is specified in Blackout Period Start Time and Blackout Period End Time. Select the end time of a blackout period. The data is not collected during the time that is specified in Blackout Period Start Time and Blackout Period End Time. Select this check box to collect the associated data type. Lists the data types that can be collected from a product host. The data types vary depending on the product that you are collect data from. See About Data Collectors on page 262. Collection Interval (sec) Enter the collection interval in minutes, hours, and days. Collection interval is the time interval that you want to set between the two consecutive data collections. For example: You have set the Collection Interval to 15 Minutes. The first data collection starts at say 9:00 A.M. till all archive records are collected and ends at 11:00 A.M. The next data collection starts at 11:15 A.M. after 15-minutes interval . Last Successful Data Load States whether last data load was successful or not. See Viewing Agent status on page 264.
Blackout Period End Time
Configuration Status Collectible Data Type
Click Save.
Modifying a Data Collector configuration

This section provides procedure to modify configuration of a Data Collector.
270
Understanding data collection Configuring data collection for NetBackup
To modify a Data Collector configuration
1 2 3 4 5 6 7 8 9
Log on to the OpsCenter console. In the OpsCenter console, click Settings > Configuration > Agent.. On the Agent list, expand an Agent to view Data Collectors that are configured for this Agent. Select a check box in front of the Data Collector that you want to modify. Click Edit Data Collector. On the Edit Data Collector: Details page, modify the Target Details. Modify data collection configuration settings. These settings vary depending on the product, which this data collector collects data from. Modify blackout period settings. Modify collection interval.
10 Click Save.
Deleting Data Collectors

This section provides procedure for deleting Data Collector configurations from an Agent. To delete a Data Collector configuration
1 2 3 4 5
Log on to the OpsCenter Server. In the console, click Settings > Configuration > Agent. On the Agent list, expand an Agent to view Data Collectors that are configured for this Agent. Select check boxes in front of the Data Collectors that you want to delete. Click Delete Data Collector.
Configuring data collection for NetBackup

This section describes how OpsCenter collects data from NetBackup. It also describes how you can add, edit, delete, and control data collection for a master server.
About the NetBackup data collection view

This view is displayed when you select Settings > Configuration > NetBackup from the OpsCenter console. This view shows details of master servers.
271
The table that appears in this view shows the following columns:
Network Name Name or IP address of the master server that is configured. The display name that you have chosen for the master server. Operating system of the master server. Backup product and version from where the data is collected. The last time that OpsCenter successfully initiated contact with the particular master server. The Last Contact column does not necessarily represent the last time that OpsCenter collected information from the master server. The master server can show any of the following states:

Display Name
Operating system Product
Last Contact
State
Connected Partially Connected Not Connected Disabled
See About the master server state on page 277.
How OpsCenter collects data from NetBackup

OpsCenter is used to monitor, manage, and report on NetBackup master and media servers, clients, and policies. To perform the monitoring, management, and reporting functions, OpsCenter collects data from the NetBackup master servers. The NetBackup data collection and management logic that OpsCenter uses is built into NetBackup master servers. This logic is included in the NetBackup Service Layer (NBSL). Starting with the 6.0 release of NetBackup, NetBackup Service Layer (NBSL) components are included as a part of NetBackup on master and media servers. Note: OpsCenter only uses the NBSL on master servers for data collection. Though NBSL is also included on media servers, OpsCenter does not use it. You must add only master servers to the OpsCenter console. You must not add any media servers to the OpsCenter console.
272
NBSL provides a single point of access to key NetBackup data, objects, and change events. The NetBackup UI also uses NBSL. NBSL runs as a service or daemon and has local configuration information, but no local database. OpsCenter uses NBSL for all NetBackup monitoring, managing, and control functions. 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 the NetBackup configuration. When NBSL restarts, OpsCenter correctly recaptures the latest state. See About the data collection status of a master server on page 274. See the NetBackup Administrators Guide, Volume II for more information about NBSL. Note: A NetBackup 7.0 master server does not require any OpsCenter Agent or data collector for data collection. However, an OpsCenter Agent must be installed if you want to collect specific data like image, error log, and scheduled jobs from a master server whose version is less than 7.0. In earlier master server versions, the VBR agents collected the data for image, error log, and scheduled jobs. For NetBackup 7.0 master servers, this data is collected automatically by the OpsCenter Server. OpsCenter Agents do not need to be installed on the NetBackup 7.0 master servers. The OpsCenter server software collects data from NBSL in the following ways:

Initial data load Listening for change notifications
Whenever OpsCenter server software starts, when data collection for a master server is enabled or when a master server is added to OpsCenter, the OpsCenter server starts collecting all the available data from NetBackup master server into the OpsCenter database using NBSL. The initial data load happens serially for each data type. As soon as the initial data load is complete, OpsCenter server software 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 server software starts after a long time, or when the data collection for a master server is enabled after a long time. In this case, it may take some time for the OpsCenter server to collect all data (such as media, jobs, images, drives etc.) from the NetBackup master server and insert it into the OpsCenter database.
273
Consider a scenario where a master server is already added on the OpsCenter console, and you uninstall and then reinstall NetBackup on the master server. In this case, the State of the master server shows as Not Connected in the OpsCenter console (State column in Settings > Configuration > NetBackup) and OpsCenter does not collect any new data from the specific master server. To begin data collection from the master server, you must delete the master server from the OpsCenter console and then add the master server again. Once you add the master server in the OpsCenter console, the OpsCenter server can start collecting data from the master server. See Adding a master server in the OpsCenter console on page 282. Symantec Private Branch Exchange (PBX) is used for communication and requires a port to be opened on the OpsCenter server and the NetBackup master server for input and output. The default PBX port that is used is 1556. If you change the PBX port on the NetBackup master server, you can configure the same in OpsCenter while adding or editing a master server.
About NetBackup versions that OpsCenter can monitor and manage

OpsCenter can monitor and manage all NetBackup versions between 6.0 MP7 and 7.0. The NetBackup master servers that OpsCenter manages are referred to as managed NetBackup servers. Each managed NetBackup master server that OpsCenter manages must have NBSL present and in operation. Starting with the 6.0 release of NetBackup, NetBackup Service Layer (NBSL) components are included as a part of NetBackup on master servers. These managed NetBackup servers harvest pertinent NetBackup data and store it in the OpsCenter database. See About the OpsCenter database on page 28. OpsCenter can also be used to monitor a NetBackup cluster. See NetBackup High Availability Administrator's Guide for more details on setting up a NetBackup cluster environment. Also review the OpsCenter sections of the NetBackup release notes before using OpsCenter for monitoring NetBackup clusters.
Viewing master server details and data collection status

Use the following procedure to view the details for a master server. The details for the master server are shown at the bottom of the Settings > Configuration > NetBackup view under the following tabs:
274
General
This tab displays the contents of many of the columns that are displayed in the table. This tab displays the collection status for each of the data types. The Data Collection Status tab is shown by default when you select Settings > Configuration > NetBackup. It also lists details like the time when the data load was last successful, when data collection last happened, and the exception message if the data collection failed for any of the data types. See About the data collection status of a master server on page 274.
Data Collection Status
To view the details and the data collection status for a master server
1 2
In the OpsCenter console, select Settings > Configurations > NetBackup. 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 server

This section describes the NetBackup data types that OpsCenter collects and the different states for managed servers. Figure 5-1 shows a sample data collection status view for a master server. Figure 5-1 Sample Data Collection Status view
275
Table 5-4 gives a description of the contents in the Data Collection Status tab. Table 5-4 Column
Data Type
Data Collection Status view Description

The type of data that is collected from NetBackup. See About NetBackup data types and collection status on page 275.
Last Successful Data Load Last Run Time
This column lists the date and time when the last successful data load happened for the specific data type. This column lists the date and time when data collection was attempted. This column provides the status of each data load activity that OpsCenter requests. This column lists the last exception message if data collection failed for a data type.
Collection Status
Last Exception Message
About NetBackup data types and collection status

OpsCenter collects data for many NetBackup data types (such as jobs, policy, media server, service, storage unit etc.) by using NBSL. For most operations and changes in NetBackup, NBSL sends notifications to OpsCenter. For changes such as job, policy, services, and devices, the notification also contains the changed data. This data is stored in the OpsCenter database. The following are the collection status for the different data types and their description:
276
Not Applicable
This status may come when the master server version does not support the specific data type. For example, NetBackup 6.0 does not support disk, FT data types. This status also comes when your master server version is lower than 7.0 and you have not configured data collection for the following data types:

Error Logs Scheduled jobs Image
You can enable data collection for these data types while adding or editing a master server under Advanced Data Collection Properties section. See Adding a master server in the OpsCenter console on page 282. See Editing a master server on page 286. Not Started The data collection for the specific data type has not started. This may happen when you initially add a master server or when you start the OpsCenter server. The data collection for the specific data type is queued. The data collection for the specific data type is in progress. The data collection for the specific data type is complete.
Queued
Running
Completed
277
Failed
The data collection for the specific data type has failed. When the data collection fails, you can see the exception message from the Last Exception Message column.
Note: Data collection can fail, and then start

after some time. This is normal behavior. If data collection for a particular data type fails, it should be automatically started again within 10 minutes. All the functionality other than the functionality of the failed data type can be used normally while collection for a data type fails. Not Licensed This status is seen when the specific data type like FT is not licensed in NetBackup.
About the master server state

This section lists the different states that can exist for a master server and what they mean. The master server can have any of the following states:
Connected The master server is Connected when the data collection status for all data types is not Failed. This means that the collection status for all the data types must be any other status except Failed. The master server is Partially Connected when data collection for some data types fails while data collection has happened or is happening for other data types. For example, data collection for catalog data type is Completed but data collection for client, device, disk etc. fails. Master servers may show as Partially Connected temporarily for some time. This is because data collection can fail, and then start after some time. This is normal behavior. If data collection for a particular data type fails, it should be automatically started again within 10 minutes. All the functionality other than the functionality of the failed data type can be used normally while collection for a data type fails.
Partially Connected
278
Not Connected
The master server is Not Connected when the data collection for all data types fails. This may be when there is a network issue because of which OpsCenter is not able to connect and collect data from NetBackup.
Note: Data collection can fail, and then start

after some time. This is normal behavior. If data collection for a particular data type fails, it should be automatically started again within 10 minutes. All the functionality other than the functionality of the failed data type can be used normally while collection for a data type fails. Disabled The master server is Disabled when the data collection for the selected master server is disabled.
Adding a master server

To allow OpsCenter to communicate with a managed NetBackup server and collect data requires some security configuration. OpsCenter can monitor the master servers which have NetBackup Access Control (NBAC) configured and also those servers that do not have NBAC configured. Note: A single OpsCenter Server should monitor only one NetBackup Master Server. Use the following steps to add a master server. Note that you must first configure the master server to allow server access and data collection by OpsCenter. After configuring the master server, you must add this server to the OpsCenter console so that it can be monitored. To add a master server
Configure your managed master server to allow server access and data collection by OpsCenter. See Configuring a master server for server access and data collection by OpsCenter on page 280.
After configuring the master server, you must add the master server to the OpsCenter console so that it can be monitored. See Adding a master server in the OpsCenter console on page 282.
279
Note: You can use an alternate procedure to add a NetBackup 7.0 master server to OpsCenter. This procedure can be used for both NBAC and non-NBAC servers. See Adding a NetBackup 7.0 master server on page 279.
Adding a NetBackup 7.0 master server

Use the following procedure to add a NetBackup 7.0 master server to the OpsCenter console. This procedure can be used for both NBAC and non-NBAC servers. In case of a clustered NetBackup setup, use this procedure for each node of the cluster. To add a NetBackup 7.0 server to the OpsCenter console on Windows and UNIX
1 2
Log on to the managed master server as Administrator or root for Windows and UNIX respectively. Browse to the following location:
Windows UNIX %Program Files%/NetBackup/bin/admincmd /usr/openv/netbackup/bin/admincmd
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 nbregopsc has been added to NetBackup 7.0. In addition, a new entry that is called OPS_CENTER_SERVER_NAME has been added to the bp.conf file. The nbregopsc command registers OpsCenter with the current master server and adds this master server to OpsCenter. This command also establishes a trust relationship from the authentication broker of NetBackup master server to the authentication broker of OpsCenter Server.
280
Ignore this step for master servers for which NBAC is not configured. However if the master server is NBAC-enabled, a trust relationship must be established from the authentication broker of the OpsCenter server to the authentication broker(AB) of the NetBackup master server. OpsCenter cannot monitor NetBackup servers if the trust relationship has not been set up between OpsCenter and NetBackup server. To establish the trust relationship, log on as Administrator or root on the OpsCenter server host and navigate to the following location:
Windows %Program Files%\Veritas\Security\Authentication\bin /opt/VRTSat/bin
UNIX
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.
Restart all the NetBackup services (processes). Once you perform this procedure, the master server is automatically added to the OpsCenter console. Note: In case running the nbregopsc command fails, you must manually add the master server to the OpsCenter console. See Adding a master server in the OpsCenter console on page 282.
Configuring a master server for server access and data collection by OpsCenter
Use the following procedures to configure a master server for data collection by OpsCenter on Windows and UNIX. This procedure applies to both NBAC and non-NBAC master servers. In case of a clustered NetBackup setup, use this procedure on each node of the cluster.
281
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 servers. See Adding a master server in the OpsCenter console on page 282. To configure a master server on Windows and UNIX
1 2 3 4 5 6 7
Log on to the managed master server as Administrator or root on Windows and UNIX respectively. Start the NetBackup Administration Console. Expand NetBackup Management > Host Properties > Master Servers. Double-click the master server name to view its properties. The Master Server Properties dialog box appears. From the Master Server Properties dialog box, select the Servers tab to display the server list. To add the OpsCenter server to the server list, click Add. The Add a New Server Entry dialog box appears. Type the OpsCenter server name in the field and click Add to add the server to the list. Ensure that the OpsCenter server name that you add is reachable from the NetBackup server.
8 9
Click Close. In the Master Server Properties dialog box, click OK.
282
10 Ignore this step for master servers on which NBAC is not configured.
However if the master server is NBAC-enabled, a bi-directional trust relationship must be established between the authentication broker of the OpsCenter server and the authentication broker(AB) of each managed NetBackup server. OpsCenter cannot monitor NetBackup servers if the trust relationship has not been set up between OpsCenter and NetBackup server (NBAC enabled). To set up these trust relationships, use the vssat command in Symantec Product 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 is installed. However if OpsCenter is installed in a clustered mode, then <OpscenterAB> is the host name that is provided as the remote authentication broker host during the OpsCenter installation. Similarly, log on as Administrator or root on the OpsCenter server host and run 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.
See Adding a master server in the OpsCenter console on page 282.
Adding a master server in the OpsCenter console

You 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 2
In the OpsCenter console, select Settings > Configurations > NetBackup . Click Add.
283
Enter the following detailsforthemasterserverunderGeneralPropertiesandAdvancedPropertiessections:
Network Name
Enter a host name or an IP address. This field is required. In case the master server is clustered, enter the virtual name of the master server.
Display Name
Enter an alternate name for the server. The display name is used for the master server on all views of the OpsCenter console. Note that this field is required.
NetBackup PBX port
The NetBackup PBX port allows all socket communication to take place while connecting through a single port. The default NetBackup PBX port is 1556. Note that this field is required.
OpsCenter's Preferred network address
The OpsCenter server may have multiple network interface cards (NIC). You can select a preferred network address from the drop-down list. OpsCenter uses the address that you select to connect to the master server.
The Advanced Data Collection Properties section is applicable if your NetBackup master server version is lower than 7.0. In earlier master server versions, the VBR agents collected the data for image, error log, and scheduled jobs. For NetBackup 7.0 master servers, this data is collected automatically by NBSL and OpsCenter Agents do not need to be installed on the master servers. The data for image, error log, and scheduled jobs is used in OpsCenter reports. Enter the following details under Advanced Data Collection Properties section:
284
Agent
Select an agent from the drop-down list. In case, no agent is configured, click Configure Agent. You can create an OpsCenter Agent from Settings > Configuration > Agent > Create Agent. See Configuring an OpsCenter Agent on page 265.
Install Directory
The directory path on the OpsCenter Agent host where the NetBackup application is installed. In case of remote data collection, this is the path on the OpsCenter Agent host where RAC (Remote Admin Console) is installed. Example of install directory path on a Windows machine: C:\Program Files\VERITAS\NetBackup Example of install directory path on a Solaris machine: /usr/openv/netbackup
Volume Manager Directory
The directory path on the OpsCenter Agent host where the Volume Manager is installed. Example of Volume Manager directory on a Windows machine: C:\Program Files\VERITAS\Volmgr Example of Volume Manager directory on a Solaris machine: /usr/openv/volmgr
Enable Image Data Collection
Click the checkbox if you want to enable image data collection from the master server. Click the checkbox if you want to enable error log data collection from the master server.
Enable Error Log data Collection
285
Enable Scheduled Job Data Collection
Click the checkbox if you want to enable scheduled job data collection from the master server. Note that you must enter the value in Username and Password fields so that scheduled job data can be collected.
Username
Enter the user name to access the NetBackup master server. A user name is required if you enable scheduled job data collection. Ignore this field in the following scenarios: If you have set the Scheduled Jobs option to Disable If you want to collect the scheduled jobs data from a local NetBackup host.
If you want to collect the scheduled jobs data remotely, using the nbpemreq CLI, set the Future Scheduled Jobs option to Enable, and specify valid NetBackup admin credentials.
Note: The Username field is disabled if

Enable Scheduled Job Data checkbox is unchecked.
Note: Username and Password is not

needed if the agent is installed on NBU master server. Password Enter the password of the NetBackup user account. This is required if you enable scheduled job data collection.
Note: The Password field is disabled if

Enable Scheduled Job Data checkbox is unchecked.
Click Locate to check if OpsCenter can connect to the master server. An error appears if OpsCenter cannot connect to the NetBackup master server on the network. Click Save to add the master server. Alternately, you can click Cancel to exit.
286
Editing a master server

Use the following procedure to change the configuration information for a NetBackup master server To edit a master server
1 2 3 4
In the OpsCenter console, select Settings > Configurations > NetBackup. Use the checkbox to select a master server from the Network Name column. Click Edit. Edit the information that is displayed on the Edit Master Server page. You can change the data that is shown for General Properties, Advanced Properties, and Advanced Data Collection Properties sections. A description of the fields present in these sections is available. See Adding a master server in the OpsCenter console on page 282. Note that you cannot edit the Network Name for the master server. The Network Name field falls under the General Properties section.
Click Save.
Deleting a master server

You can delete one or more master servers using the following procedure. Note that deleting a master server deletes all the data that is associated with the master server. Note: Deleting a master server may take some time. To delete a master server
1 2 3 4
In the OpsCenter console, select Settings > Configurations > NetBackup . Use the checkbox to select one or more master servers from the Network Name column. Click Delete. The following warning message appears:
Deletion of the selected master server(s) will delete all related data. Do you want to proceed?
Click OK.
Understanding data collection Collecting data from Backup Exec
287
Controlling data collection for a master server

You can disable or enable OpsCenter data collection for a particular managed NetBackup 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 data collection again. To disable data collection for a master server
1 2 3
In the OpsCenter console, select Settings > Configurations > NetBackup. Use the checkbox to select one or more master servers from the Network Name column. Click Disable Data Collection.
To enable data collection for a master server
1 2 3
In the OpsCenter console, select Settings > Configurations > NetBackup . Use the checkbox to select one or more master servers from the Network Name column. Click Enable Data Collection.
Collecting data from Backup Exec

This section describes data collection from Backup Exec. Caution: The Backup Exec data collector requires the following component to be installed on the OpsCenter Agent host, to collect data properly. Microsoft Visual C++ 2005 SP1 Redistributable Package (x86) that is vcredist_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 Exec data collector as described in the following section.
288
Understanding data collection Collecting data from PureDisk
To configure Backup Exec data collector
1 2 3 4 5 6 7
Click Settings > Configuration > Agent . On the Agent list, select a check box in front of the Agent, for which you want to configure a Data Collector. Click Create Data Collector. On the Create Data Collector: Product Selection page, select Symantec Backup Exec from the Select Product drop-down list. In the Target Host Name text box, enter the Backup Exec Server host name, from which you want to collect data. Click Next. On the Create Data Collector: Details page, specify the following Backup Exec data collector configuration settings:
User name Enter the name of the user account that is required to connect to the Backup Exec Database . Enter the password of this user account. Select the version of the Symantec Backup Exec server - 10.x, 11.x, or 12.x - from which you want to collect data.
Password Version
Select blackout period details, data types to be collected, and collection interval. For more details on collection interval, and other data collector settings, refer to the following section: See Configuring a Data Collector on page 267.
Click Save.
Collecting data from PureDisk

OpsCenter supports collection of data from Symantec NetBackup PureDisk. The collected data is stored in the OpsCenter database, based on which you can generate reports. OpsCenter can collect Policy & Schedule and Job data types from PureDisk Storage Pool Authority (PureDisk SPA). For more details on PureDisk, refer to the Symantec NetBackup PureDisk documentation.
289
PureDisk SPA and its components that run on the PureDisk operating system (PDOS). The Single Instance Storage (SIS) or deduplication technology of NetBackup PureDisk is unique in storage and backup industry. PureDisk identifies files and the data segments that contain identical data and treats them as a single instance 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 the file are present on hosts across the network, including remote hosts. By using the deduplication technology, PureDisk stores only one instance of the file. Table 5-5 describes the steps that you need to carry out to collect data from PureDisk. Table 5-5 Steps to collect data from PureDisk Reference topic
Refer to the Installing Symantec OpsCenter on Windows and UNIX section.
Step number Step

1 Install OpsCenter server.
Note: When you install OpsCenter

server,OpsCenter Integrated Agent is also installed and configured, which you can use to collect only PureDisk data. To collect PureDisk data, you do not need to manually install or configure OpsCenter Agent. You cannot delete the Integrated Agent. cannot be deleted
Note: You can collect PureDisk data only through

the OpsCenter Integrated Agent. 2 You need to establish trust between the See Setting up a trust authentication brokers of OpsCenter and PureDisk between the PureDisk SPA for secure communication. SPA host and OpsCenter AB host This is a pre-requisite for PureDisk data collection on page 290. from OpsCenter. Using the OpsCenter console, configure PureDisk See Configuring data collector for the Integrated Agent. PureDisk data collector on page 291.
290
Setting up a trust between the PureDisk SPA host and OpsCenter AB host
You need to set up a bi-directional trust between the PureDisk SPA host and OpsCenter AB (authentication broker ) host. This is a pre-requisite for PureDisk data collection from OpsCenter. 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 AB host is the host name that was provided as the remote authentication broker host during the OpsCenter installation. The OpsCenter AB hostname is stored in the vxss.hostname parameter in the following file: On Windows: C:\Program
Files\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 PureDisk SPA host, to setup trust between the PureDisk SPA host and the OpsCenter authentication broker host. To set up a trust between PureDisk SPA host and OpsCenter AB host
On the PureDisk SPA host, logon as root and run the following command:
su www-data
As a www-data user, run the following command:

/opt/VRTSat/bin/vssat setuptrust --broker OpsCenterABhost:2821 --securitylevel high
After successfully setting up a trust between the PureDisk SPA host and OpsCenter AB host, the following message is displayed:
setuptrust ------------------------------------------Setup Trust With Broker: OpsCenterABhost
291
Note: Setting up a trust between the OpsCenter AB host and PureDisk SPA host from the OpsCenter AB host is accomplished automatically after the PureDisk data collector is configured.
Configuring PureDisk data collector

This section provides the procedure to configure NetBackup PureDisk data collector on the OpsCenter UI. To configure NetBackup PureDisk data collector
1 2
Click Settings > Configuration > Agent . On the Agent list, select a check box in front of the Integrated Agent. When you install OpsCenter server,OpsCenter Integrated Agent is also installed and configured, which you can use to collect only PureDisk data. To collect PureDisk data, you do not need to manually install or configure OpsCenter Agent. You can collect PureDisk data only through the OpsCenter Integrated Agent.
3 4 5 6
Click Create Data Collector. On the Create Data Collector: Product Selection page, select Symantec NetBackup PureDisk from the Select Product drop-down list. In the Target Host Name text box, enter the PureDisk SPA Server host name, from which you want to collect data. Click Next.
292
Understanding data collection Collecting data from Enterprise Vault
On the Create Data Collector: Details page, specify the following PureDisk configuration settings:
Product Version Select any of the following Symantec NetBackup PureDisk 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
For more details on collection interval, and other data collector settings, refer to the following section: See Configuring a Data Collector on page 267.
Click Save. Setting up a trust between the OpsCenter authentication broker host and PureDisk SPA host is accomplished automatically after PureDisk data collector is 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 PureDisk SPA host" in the OpsCenter Administrator's Guide.
Collecting data from Enterprise Vault

This section provides information about Enterprise Vault Data Collector configuration.
About Enterprise Vault

Symantec Enterprise Vault software application provides a flexible framework for archiving emails, file systems, and collaborative environments. It is supported only 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.
293
About data collected from Enterprise Vault

OpsCenter categorizes the data that is collected from Enterprise Vault database into various data types. Table 5-6 lists the data types in OpsCenter that represent type of data that is collected from Enterprise Vault. For example, OpsCenter collects Policy and Retention Category data from Enterprise Vault database and stores it as Archive Policy data type. Table 5-6 Enterprise Vault data types Data in Enterprise Vault
Policy and Retention Category Vault Store and Vault Store Partition Mailbox, Public Folder, and Provisioning Group SaveSet
Data type in OpsCenter

Archive Policy Vault Store Target Archive
You can select these data types while configuring the Enterprise Vault data collector. The data collector collects the information from Enterprise Vault that is associated with the selected data types, , as per the specified schedule. See Configuring Enterprise Vault data collector on page 302. Figure 5-2 shows the hierarchy of archive data in Enterprise Vault.
294
Figure 5-2
Representation of Enterprise Vault data in OpsCenter reports
Archive Site
Exchange Server
Enterprise Vault Server
Vault Store Provisioning Group Vault Partition ----------------- Archives ------------------------------ Archive Storage -------------
An archive site is a logical group of hosts that need to be archived (Exchange Servers, Provisioning Groups), storage media (vault stores, vault partitions), and Enterprise Vault Servers. It is at the highest level in the Enterprise Vault data hierarchy. Using OpsCenter archive reports you can determine the details about both archiving activities and archival storage, depending on which path you follow to drill down the site information. See About OpsCenter reports on page 457. OpsCenter reports present archive data in the following two ways:
295
Archiving activities
A few archive reports show details about archiving activities. For example: Details of mailboxes to be archived, original size of data that has been archived, the number of mailboxes that exceed their warning limits per Exchange Server or Provisioning Group, and so 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 show only Exchange Server data.
Note: Mailboxes are referred to as targets and an individual email

is referred to as an item. Storage of archived data A few archive reports show details about the storage of archived data. For example: details of vault stores and vault partitions where the archive data has been stored, or how many emails were archived per Enterprise Vault Server, and so on.
About versions supported by OpsCenter

OpsCenter supports the following versions of Enterprise Vault. It supports all versions of Microsoft SQL Server that the Enterprise Vault supports.
Enterprise Vault Microsoft SQL Server 7.5, 8.0 2005, 2008
Planning the Enterprise Vault data collector deployment

Enterprise Vault stores the archive metadata in the directory and the storage database residing in Microsoft SQL Server. To collect the archive metadata from Microsoft SQL Server, you need to configure OpsCenter Agent and data collector using the OpsCenter console. OpsCenter supports local as well as remote archive-data collection. However, Symantec recommends the remote data collection method, in which OpsCenter Agent and MS SQL Server are installed on different hosts. Table 5-7 lists the steps that you need to carry out before configuring the Enterprise Vault data collector for archive-data collection in the OpsCenter console.
296
Table 5-7
Planning and deployment steps Reference topic
Step number Step

1
Deploy OpsCenter Agent in any of the following See About single-domain ways, to collect archive data remotely: deployment mode on page 297. Single-domain mode See About multi-domain Multi-domain mode deployment mode Standalone mode on page 297. Note: Symantec recommends that to collect See About standalone Enterprise Vault data, you deploy the deployment mode OpsCenter Agent in single-domain mode. on page 297. Make sure that the user whose credentials you See Accessing MS SQL use for the integrated logon has required access Server host on page 298. rights on the MS SQL Server, where the archive data resides. This can be an existing user, or you can create a new user in MS SQL Server and give required access rights.
Depending on the deployment mode of the OpsCenter Agent, add a user in the appropriate domain or workgroup, which you want to use for integrated logon between Agent host and MS SQL Server host.
See About creating a user in single-domain deployment mode on page 299. See About creating a user in multi-domain deployment mode on page 299. See About creating a user in standalone deployment mode on page 299.
Install MS SQL Server JDBC driver on the OpsCenter Agent host.
See Installing MS SQL Server JDBC driver on page 301. See Configuring the OpsCenter Agent properties for integrated logon on page 300.
For integrated logon, configure the OpsCenter Agent to run in the context of the user or group that has access to MS SQL Server, where the Enterprise Vault data resides, depending on the OpsCenter Agent deployment mode.
297
You need to configure the Enterprise Vault data collector using the OpsCenter console and schedule data collection. See Configuring Enterprise Vault data collector on page 302.
About OpsCenter Agent deployment modes

This section describes various deployment modes in which you can deploy OpsCenter Agent, depending on your setup. This section mainly talks about the remote agent deployment modes. However, Enterprise Vault also supports local Agent deployment. You can deploy the OpsCenter Agent on MS SQL Server host or OpsCenter Server host.
About single-domain deployment mode

Symantec recommends that you deploy the OpsCenter Agent in single-domain mode to collect Enterprise Vault data. In this deployment mode, the OpsCenter Agent host and the MS SQL Server host (Enterprise Vault database instance) share the same Windows domain.
About multi-domain deployment mode

In addition to single-domain mode, you can deploy the OpsCenter Agent in multi-domain mode. In this deployment mode, the OpsCenter Agent host and the MS SQL Server host (Enterprise Vault database instance) do not share the same Windows domain. The OpsCenter Agent host is in a domain different than the SQL Server domain. Note: To collect Enterprise Vault data, Symantec does not recommend the multi-domain or standalone deployment of the OpsCenter Agent.
About standalone deployment mode

In this deployment mode, the OpsCenter Agent host and the MS SQL Server host (Enterprise Vault database instance) do not share the same Windows domain. The OpsCenter Agent host is installed on a standalone host. Note: To collect Enterprise Vault data, Symantec does not recommend the multi-domain or standalone deployment of the OpsCenter Agent.
298
Accessing MS SQL Server host

This section describes how to give the required rights to a user to access MS SQL Server. To give rights to a user to access MS SQL Server
1 2
Create a Windows domain user on the MS SQL Server host. For example, create a user with credentials localadmin and pass. Open the MS SQL Server admin console, using SQL Server Management Studio Express or any other MS SQL Server client. Add this Windows domain user (local admin) to the MS SQL Server. Add this user (local admin) to the Enterprise Vault databases, on which you want the access rights. Note: To report on Enterprise Vault / archive data, OpsCenter Agent needs access to the Enterprise Vault directory and storage databases. You need to add the user to these databases and give the required access rights on these databases.
4 5 6
In the MS SQL Server admin console, in the Object Explorer, expand the Security folder. Expand the logons folder. Right-click the user name - for example OpsDomain\localadmin with the password pass - with which you want to perform integrated logon on the Agent host and MS SQL Server host. Click Properties. On the logon Properties screen, in the Select a page pane, select Server Roles. 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 has the rights to access MS SQL Server.
7 8 9
10 Additionally, make sure that the user has datareader rights to access the
desired database.
About creating a user for integrated logon

This section provides procedures to create a user that is required for integrated logon between the OpsCenter Agent host and MS SQL Server host, where the archive data resides.
299
Depending on the OpsCenter Agent deployment mode, the procedure to create a logon user varies.
About creating a user in single-domain deployment mode

Make sure that the user whose credentials (for example, User name: 'localadmin' and Password: 'pass') you use for the integrated logon has required access rights on the MS SQL Server, where the archive data resides. The user 'localadmin' can be an existing user, or you can create a new user with these credentials in MS SQL Server and give required access rights. See Accessing MS SQL Server host on page 298. If you have deployed the OpsCenter Agent in the single-domain mode, create a user, (User name: 'localadmin' and Password: 'pass') in the Agent host domain that is the Windows domain. See About single-domain deployment mode on page 297. Use credentials of this user (User name: 'localadmin' and Password: 'pass') when you configure the Agent properties for integrated logon. See Configuring the OpsCenter Agent properties for integrated logon on page 300.
About creating a user in multi-domain deployment mode

Make sure that the user whose credentials (for example, User name: 'localadmin' and Password: 'pass') you use for the integrated logon has required access rights on the MS SQL Server, where the archive data resides. The user 'localadmin' can be an existing user, or you can create a new user with these credentials in MS SQL Server and give required access rights. See Accessing MS SQL Server host on page 298. If you have deployed the OpsCenter Agent in the multi-domain mode, create a user (User name: 'localadmin' and Password: 'pass') in the Agent host domain. See About multi-domain deployment mode on page 297. Use credentials of this user (User name: 'localadmin' and Password: 'pass') when you configure the Agent properties for integrated logon. See Configuring the OpsCenter Agent properties for integrated logon on page 300.
About creating a user in standalone deployment mode

Make sure that the user whose credentials (for example, User name: 'localadmin' and Password: 'pass') you use for the integrated logon has required access rights on the MS SQL Server, where the archive data resides.
300
The user 'localadmin' can be an existing user, or you can create a new user with these credentials in MS SQL Server and give required access rights. See Accessing MS SQL Server host on page 298. If you have deployed the OpsCenter Agent in the standalone mode, create a user for example (User name: 'localadmin' and Password: 'pass') in the appropriate workgroup. See About standalone deployment mode on page 297. Use credentials of this user (User name: 'localadmin' and Password: 'pass') when you configure the Agent properties for integrated logon. See Configuring the OpsCenter Agent properties for integrated logon on page 300.
Configuring the OpsCenter Agent properties for integrated logon

The Enterprise Vault data collector that is configured in OpsCenter collects the Enterprise Vault archive data residing on the MS SQL Server. However, the data collection is not possible if the OpsCenter Agent is not configured to run in the context 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 See Accessing MS SQL Server host on page 298. To configure OpsCenter Agent properties
1 2 3
On the OpsCenter Agent host (Windows system), click Start > Run. In the Run dialog box, in the Open text box, enter services.msc. Click Enter. The Windows Services screen is displayed.
4 5 6 7
On the Services screen, on the services list, right-click the Symantec OpsCenter Agent service. On the right-click menu, click Properties. On the Symantec OpsCenter Agent Properties screen, on the Log On tab, select the This account option. 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 Enterprise Vault archive data resides. Alternatively, click Browse. This opens the Select User dialog box.
301
Enter a user name in the text box. This user should have access rights on MS SQL Server. Click Check Names to check whether the user name that is specified is present in the Windows domain or not. Click OK.
10 Click OK on the LogOn tab.
Installing MS SQL Server JDBC driver

To collect the Enterprise Vault data residing on Microsoft SQL Server (or MS SQL Server or SQL Server), you require the SQL Server JDBC driver that is installed on the OpsCenter Agent host. The Agent requires the JDBC driver to communicate with the MS SQL Server. Microsoft provides a Java Database Connectivity (JDBC) driver for use with SQL Server 2005. The SQL Server 2005 JDBC driver is available to all SQL Server users at no additional charge, and provides access to SQL Server 2000 and SQL Server 2005 from any Java application, application server, or Java-enabled applet. This driver is a Type 4 JDBC driver that provides database connectivity through the standard JDBC application program interfaces (APIs) available in J2EE (Java2 Enterprise Edition). The SQL Server 2005 JDBC Driver is JDBC 3.0 compliant and runs on the Java Runtime Environment (JRE) 1.4 and later versions. To install MS SQL Server JDBC driver
Click the following link: Download Microsoft SQL Server 2005 JDBC Driver 1.2
2 3
On the Microsoft SQL Server 2005 JDBC Driver 1.2 page, click Download. On the MICROSOFT SOFTWARE LICENSE TERMS page, select the following: I Accept and I want to download the Microsoft Windows version The File Download dialog box is displayed.
4 5
Click Save to save the .zip file to a desired location. Unzip the file.
302
Copy sqljdbc_1.2\enu\auth\x86\sqljdbc_auth.dll and sqljdbc_1.2\enu\sqljdbc.jar files to the following location on the Agent host.
Install Dir\Symantec\OpsCenter\Agent\lib
Install Dir is the location where you have installed OpsCenter Click the following link for more information and frequently asked questions on the JDBC driver. Microsoft SQL Server 2005 JDBC Driver
Restart the Agent service.
Configuring Enterprise Vault data collector

This section provides the procedure to configure the Enterprise Vault data collector in the OpsCenter console. This data collector collects archive data from MS SQL Server where the Enterprise Vault database resides. To collect archive data, the Enterprise Vault data collector needs the Agent to be configured to run in the context of the user or the group that can access MS SQL Server. See Configuring the OpsCenter Agent properties for integrated logon on page 300. To configure Enterprise Vault data collector
1 2 3 4 5 6 7
In the OpsCenter console, click Settings > Configuration > Agent . On the Agent list, select a check box in front of the Agent for which you want to configure the Data Collector. Click Create Data Collector. On the Create Data Collector: Product Selection page, select Symantec Enterprise Vault from the Select Product drop-down list. Enter the name of the host, from where you want to collect the archive data. Click Next. Enter the following Configuration Settings:
Database Instance Name This is the database instance name. By default this field is left blank.
Database port number Enter the port number that is used to connect to the MS SQL Server. The default port number is 1433.
Understanding data collection Collecting data from IBM Tivoli Storage Manager
303
8 9
Specify blackout period details. Select the data types that you want to collect. You can collect the following data 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 checklist

Ensure the following before you start collecting data from Enterprise Vault database:
The SQL Server JDBC driver has been installed on the OpsCenter Agent host See Installing MS SQL Server JDBC driver on page 301. The OpsCenter Agent has been configured to run in the context of the user or user group that has access to MS SQL Server database where Enterprise Vault data is stored. See Configuring the OpsCenter Agent properties for integrated logon on page 300. The OpsCenter Agent service is running. The SQL Server services are running. You have entered the appropriate information for Enterprise Vault data collector variables. See Configuring Enterprise Vault data collector on page 302. You have selected the data types / events to be collected from the Enterprise Vault database, that is the MS SQL Server. You have specified the collection interval within which you want to collect the archive data.
Collecting data from IBM Tivoli Storage Manager

OpsCenter supports the collection of the following data types from IBM Tivoli Storage Manager (TSM): The variables to configure for the IBM Tivoli Storage Manager data collector are as follows:
304
Understanding data collection Collecting data from IBM Tivoli Storage Manager
Home Directory
The home directory for the Tivoli Storage Manager installation. (This variable can be left blank.) An administrator-level logon that is used to connect to the Tivoli Storage Manager server. (The default is admin.) The password for the account (specified in tsmId) for connecting to the TSM server. (The default password is admin.) (Windows only) The TCP port on the TSM server through which the data collector establishes a connection. The TSM Server Port has no effect on Solaris. The Solaris data collector uses only product host settings.
TSM ID
TSM Password
TSM Server Port
dsmConfig dsmDir dsmadmc Location
The path to the dsm.opt file. The path where files to be run dsmadmc reside. The path of TSM administrative client (dsmadmc).
Note: The TSM product environment variables DSM_CONFIG and DSM_SYS point to the dsmadmc required files dsm.opt and dsm.sys (Solaris and AIX). For more information, refer to your TSM documentation. Specify the TSM server host (also called product host) value for the TSM data collector in the following manner:
Windows Use the fully qualified host name. In short, product host is the value that you can use with the dsmadmc -tcpserveraddress option. For example, the following entries are valid for product host: Host.sample.domain.com Host assuming that Host can be fully qualified.
Understanding data collection Collecting data from EMC Legato Networker
305
Solaris and AIX
The product host must be the value that is specified in the dsm.sys file, for tag SErvername (note the case). In short, product host is the value that you can use with the dsmadmc -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 ******************************************
Collecting data from EMC Legato Networker

The variables to configure for the EMC Legato Networker data collector are as follows:
Home Directory The home directory for the EMC Legato Networker installation. The directory path for the log file containing group-complete messages. This path may be absolute or relative to homeDirectory. The default file name is messages. To increase the efficiency of the Networker data collector, configure Networker to create a log that contains only group complete messages, and point messagesFile to this log Location of mminfo.exe The directory path of the mminfo command-line interface (CLI), absolute, or relative to homeDirectory The directory path of the nsradmin CLI, absolute, or relative to homeDirectory
Location of messages file
Location of nsradmin.exe
306
Understanding data collection Collecting data from EMC Legato Networker
Location of nsrres file
The Networker resource file to use instead of the default file that is used by nsradmin (Optional) Output of an nsradmin command (Optional) The OpsCenter console displays nsrResFile, nsrFile, and mminfoFile even though these variables are optional and only advanced users must set them.
Location of nsr file
Location of mminfo file
Output of mminfo(Optional)
Chapter
Managing OpsCenter views


About OpsCenter views Managing views Managing nodes and objects
About OpsCenter views

Symantec OpsCenter views are logical groups of IT assets (master servers or clients) organized in a hierarchical manner. You can create views in Java View Builder and make them available in the OpsCenter console. Figure 6-1 shows the details that are displayed on the Views tab in the OpsCenter console.
308
Managing OpsCenter views About OpsCenter views
Figure 6-1
The Views tab
Note: If you do not have the admin privileges you can still copy a view object from a read-only view to your view. However, you cannot modify its attributes because you do not have the write permissions for that view.
Note: To manage views, an OpsCenter Analyst and Reporter need to have the required rights assigned to them through Java View Builder. If they do not have these rights, they cannot manage - create, edit, or delete - views using the OpsCenter 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 the required permissions. See About user access rights on page 235. In a OpsCenter view, IT assets that are scattered across organization can be arranged according to their locations, business units, or applications. You can generate various OpsCenter reports that are filtered by views. With these reports, you can identify the locations or departments with hosts storing business critical data.
309
After you install and run the OpsCenter Server and the OpsCenter Agent, OpsCenter detects theIT assets, which are then stored in the database. The Java View 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 (Exchange Server / Enterprise Vault Server) > Target (Mailbox / Journal Mailbox / Public Folder) See Collecting data from Enterprise Vault on page 292. 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 of user-defined levels. An OpsCenter view is a homogeneous one, it cannot have hosts and file systems in the same tree.
About view types

In OpsCenter, each view is associated with a view type. Depending on the type of the view, objects are made available for assigning to that view. Note: All Veritas Backup Reporter (VBR) views are migrated to OpsCenter as Client views. 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 reports with views. You can create views of the following types:
Client If you create a view of type Client, only backup clients are available to be assigned to the view. If you create a view of type Master Server, only Master Servers are available to be assigned to the view. If you create a view of type Policy, only policies are available to be assigned to the view.
Master server
Policy
310
Enterprise Vault server
If you create a view of type Enterprise Vault server, only EV servers are available to be assigned to the view. If you create a view of type Exchange server, only Exchange servers are available to be assigned to the view. If you create a view of type Vault, only vaults are available to be assigned to the view. If you create a view of type File System, only file systems are available to be assigned to the view.
Exchange server
Vault
File System
About accessing OpsCenter views

While 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 312.
Public view Private view All OpsCenter users can access public views. Only view owner and OpsCenter admin can access private views.
About view levels

A newly created view has only one level. You can add multiple nodes to a view at different levels. You can add alias for each of these view levels. See Modifying view level alias on page 314. 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 intermediate levels to organize view objects into logical groups, to create a hierarchical structure in the view.
About nodes and objects

An OpsCenter view comprises nodes and view objects. A node is a logical entity that 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 multiple nodes. Figure 6-2 shows an example of a view comprising multiple nodes and objects.
Managing OpsCenter views Managing views
311
Figure 6-2
View nodes and objects
Managing views
This section provides procedures to add, edit, or delete OpsCenter views.
Viewing OpsCenter views and their details

This section provides the procedure to view OpsCenter views. See About OpsCenter views on page 307. To view OpsCenter views
In the OpsCenter console, click Settings > Views. A list of views that you have already created is displayed. See Modifying views on page 313. See Creating views on page 312.
To check the details of a view, select the view from the views list. The details are displayed in the lower section of the page.
312
Alias View Levels tab
This tab shows the details of view level aliases of the selected view. Default view level aliases are as follows: Level 1, Level 2, and so on. The Alias View Levels tab does not contain any data, if you have not added any nodes or objects to the selected view. You can modify the view level aliases. See Modifying view level alias on page 314.
General tab
The General tab displays the following details:

Name of the selected view Description of the view
Date and time when the view was created Name of the user who has created this view
Creating views
This section provides the procedure to create a view using OpsCenter. To create a view
1 2
In the OpsCenter console, click Settings > Views. Click Add.
313
On the Add View dialog box, specify the following view details:
Name View type Enter the view name Select the view type: Client, Master Server, Policy, Enterprise Vault Server, or Exchange Server See About view types on page 309. Description Enter description about the view. For example: This is a geographical view that comprises of master servers located in Asia Pacific, Europe, and North America. Make the View Public 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 310. If you do not select this check box, the view becomes private. Users other than you and OpsCenter admin cannot access this view.
Click OK.
Modifying views
This section provides the procedure to modify view details. To modify views
1 2 3
In the OpsCenter console, click Settings > Views. From the list of views, select a view that you want to modify. Click Edit.
314
On the Edit View dialog box, you can modify the following view details:
Name Description Make the View Public Modify the view name Modify the view 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 310.
Click OK.
Deleting views
This 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
1 2 3
In the OpsCenter console, click Settings > Views. From the list of views, select a view that you want to delete. Click Delete.
Modifying view level alias

This section provides the procedure to modify alias of view levels. See Adding nodes to a view on page 315. To modify alias view levels
1 2 3
In the OpsCenter console, click Settings > Views. From the list of views, select a view for which you want to modify view level alias. Click Edit Alias View Levels.
Managing OpsCenter views Managing nodes and objects
315
On the Alias View Levels dialog box, text boxes for entering aliases for all available view levels appear. For example, if the selected view has only one level, the Alias View Levels dialog box appears as follows:
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. Click OK.
Managing nodes and objects

This section provides procedures to create, modify, and delete nodes and objects of a view.
Adding nodes to a view

This section provides the procedure to add a node to a view. See About nodes and objects on page 310. To add nodes to a view
1 2 3 4 5 6 7
In the OpsCenter console, click Settings > Views. From the list of views, select a view to which you want to add nodes and objects. Click Manage Nodes and Objects. On the view tree, select the view to which you want to add a node. Click Add. On the Add dialog box, enter the node name. Click OK.
316
Modifying node details

This section provides the procedure to modify the information of a view node. See Adding nodes to a view on page 315. To modify node information
1 2 3 4 5 6 7 8
In the OpsCenter console, click Settings > Views. From the list of views, select a view to modify the information of associated nodes. Click Manage Nodes and Objects. On the view tree, expand the view to see the associated nodes. Select the node that you want to modify. Click Edit. On the Edit dialog box, modify the name of the node. Click OK.
Deleting nodes
This section provides the procedure to delete the nodes from a view. See Adding nodes to a view on page 315. To delete a node
1 2 3 4 5 6 7
In the OpsCenter console, click Settings > Views. From the list of views, select a view from which you want to delete nodes. Click Manage Nodes and Objects. On the view tree, expand the view to see the associated nodes. Select the node that you want to delete. Click Delete. On the confirmation dialog box, click OK.
Adding objects to a view node

This section provides the procedure to add objects to a view or a node within a view.
317
To add an object to a view node
1 2 3 4 5
In the OpsCenter console, click Settings > Views. From the list of views, select the view to which you want to add objects. Click Manage Nodes and Objects. On the view tree, select the view name or a view node to which you want to add an object. In the right-hand-side pane, select the Unassigned Objects tab. The available objects list varies depending on the view type. For example: If the view is of type Client, only client hosts are available on the Unassigned Objects tab for selection. The Unassigned Objects tab contains all objects that have not yet been assigned to the selected view or view node. You can filter the unassigned objects with the help of default filters or you can create new filters and apply them to view the required objects on the tab. See Working with view filters on page 318.
6 7
Select the check boxes in front of the view objects that you want to add to the selected view or view node. Click Add to Node. The added view objects are removed from the Unassigned Objects tab and appear on the Objects on Node tab.
Deleting objects from a view node

This section provides the procedure to delete the objects from a view or a view node. To delete an object from a view node
1 2 3 4
In the OpsCenter console, click Settings > Views. From the list of views, select the view from which you want to delete objects. Click Manage Nodes and Objects. On the view tree, select the view name or a view node from which you want to delete an object. The objects that are assigned to this view or the view node are displayed on the Objects on Node tab.
Select the check boxes in front of the view objects that you want to delete.
318
6 7
Click Delete from Node. On the confirmation dialog box, click OK.
Working with view filters

OpsCenter provides a set of default filters using which you can filter the view objects that you need to add to a view. You can also create your own filters and apply them to view the required list of view objects. The default set of filters vary depending on the view type. Table 6-1 lists the default filters available for various view types. Table 6-1 View type
Client
Default filters Default filters

All Clients, Windows Clients, Solaris Clients, Linux Clients, Other Clients All Servers, Connected Servers, Partially Connected Servers, Not Connected Servers, Windows Servers, Solaris Servers, Linux Servers, Other Servers All Policies, Active Policies, Inactive Policies, Windows Policies, Catalog Policies, Standard Policies, Other Policies
Master Server
Policy
Creating a view object filter

This section provides the procedure to create user-defined view object filters. See Working with view filters on page 318. To create a view object filter
1 2 3 4 5
In the OpsCenter console, click Settings > Views. From the list of views, select the view to which you want to assign objects. Click Manage Nodes and Objects. On the view tree, select the view name or the view node to which you want to assign view objects. In the right-hand-side pane, select the Unassigned Objects tab. The list of objects that is displayed varies depending on the view type. For example: If the view is of type Client, only client hosts are available on the Unassigned Objects tab for selection.
Click the Create Filter icon.
319
On the dialog box, specify the following filter details:

Name Definition Enter the filter name. The filter definition comprises the following components: Column - Select a column of filed name that you want to filter on. Operator - Select an operator to form a filter criteria. Value - Enter the value for the selected column, with which you want to filter the available view objects. And - Select And or Or as appropriate. This lets you specify multiple filter criteria.
Use the links appearing in the Link as follows: Click Add to add a new row for specifying new filter criteria. Click Remove to remove the respective row from the filter criteria.
The following figure shows an example of creating a filter.
Click OK. This user-defiled filter is now added in the Filter drop-down list on the Unassigned Objects tab, which you can modify or delete. See Modifying view object filters on page 320. See Deleting view object filters on page 320.
320
Modifying view object filters

You can modify definition of user-defined view object filters. You cannot modify the default filters. See Creating a view object filter on page 318. To modify view object filters
1 2 3 4 5
In the OpsCenter console, click Settings > Views. From the list of views, select the view to which you want to assign objects. Click Manage Nodes and Objects. On the view tree, select the view name or a view node to which you want to assign view objects. In the right-hand-side pane, select the Unassigned Objects tab. The list of objects that is displayed varies depending on the view type. For example: If the view is of type Client, only client hosts are available on the Unassigned Objects tab for selection.
6 7
From the Filter drop-down list, select the user-defined filter that you want to modify. Select the Edit Filter icon. If you have selected a default filter, the Edit Filter icon is disabled.
8 9
On the dialog box, modify name or definition of the filter. Click OK.
Deleting view object filters

You can delete user-defined view object filters. You cannot delete the default filters. See Creating a view object filter on page 318. To delete view object filters
1 2 3 4
In the OpsCenter console, click Settings > Views. From the list of views, select the view to which you want to assign objects. Click Manage Nodes and Objects. On the view tree, select the view name or a view node to which you want to assign view objects.
321
5 6
In the right-hand-side pane, select the Unassigned Objects tab. The list of objects that is displayed varies depending on the view type. From the Filter drop-down list, select the user-defined filter that you want to delete. If you have selected a default filter, the Delete Filter icon is disabled.
322
Chapter
Monitoring NetBackup using 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 views

From the Monitor tab and associated subtabs, you can view detailed information about your NetBackup environment including jobs, services, policies, media, devices, hosts, and alerts.
324
Monitoring NetBackup using Symantec OpsCenter Controlling the scope of Monitor views
Controlling the scope of Monitor views

The content that is shown in the Monitor views is based on your current View pane selection. You can select the following default option from the View pane:
ALL MASTER SERVERS Select ALL MASTER SERVERS to view information for all the NetBackup servers in your environment.
In addition to using the default view i.e. ALL MASTER SERVERS, you can also create your own views from Settings > Views or by using Java View Builder. For example, you can create a view like Geography to view details about master servers in a particular region like Europe. More information about how to create views by using the Settings > Views is available. See About OpsCenter views on page 307. See the online Symantec OpsCenter Java View Builder Help to know how you can create views using Java View Builder. Use the following procedure to view details of all master servers or specific master servers. To view details of all master servers
In the OpsCenter console, select ALL MASTER SERVERS from the drop-down list in the View pane.
To view details of specific master servers
1 2
In the OpsCenter console, select ALL MASTER SERVERS from the drop-down list in the View pane. Deselect the checkbox next to ALL MASTER SERVERS and select the specific master servers from the list of master servers. Ensure that other master servers are unchecked. Click Apply Selection.
About timeframe selection

You can also view data for the last 24, 48, or 72 hours for some of the Monitor views 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. Note that by default data for the last 24 hours is shown in these views.
Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup using the Overview subtab
325
You can control timeframe selection for the following Monitor views:
Monitor > Overview (Job Summary by State, Job Summary by Exit Status, Top 7 Policies by Failed Jobs, Top 7 Job Error Log Summary, and Alert Summary by Severity sections) Monitor > Jobs Monitor > Alerts Monitor > Policies (Summary View)
In addition, you can also customize the timeframe selection by clicking Customize and specifying an absolute timeframe or relative timeframe. Using the Customize option, you can view data for any timeframe that you want like you can view jobs data for the previous three weeks. The Customize option is located on the top-right corner 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 subtab

This view is displayed when you select Monitor > Overview. This view gives an overview of your NetBackup environment. This view contains the different sections which display specific information about your NetBackup environment. From this view, you can use links to drill down and access detailed information about many aspects of your NetBackup environment. Pie charts for most monitoring categories appear. The pie segments are also links to more details for the 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 About Top 7 Policies by Failed Jobs section
326
Viewing the Alert Summary by Severity section
Viewing the Job Summary by State section

The Job Summary by State section shows an overall distribution of jobs by job state for the current selection in the View pane and timeframe selection. This information is shown in a pie chart as well as a table. Data for the last 24 hours is 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 324. A pie chart with different colors represents the job distribution. Each color of the pie chart represents how jobs are distributed in your environment as per the job state in the selected timeframe. You can also view the color code summary in this section to know the colors that represent different job states. Pointing on the pie chart gives the number and percentage of jobs in a particular job state in your NetBackup environment. For example, pointing on the yellow color in the pie chart shows that in the last 24 hours, 22 jobs, or 42% jobs in your environment are 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 2
In the OpsCenter console, select Monitor > Overview. 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 particular job state. For example, click on the yellow section of the pie chart to view details for Queued jobs.
Viewing the Media Summary by Status section

The Media Summary by Status section shows an overall distribution of media by media status for the current selection in the View pane. This information is shown in 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 your environment as per the media status. You can also view the color code summary in this section to know the colors that represent different media status. Pointing on the pie chart gives the number and percentage of media with a particular media
327
status in your NetBackup environment. For example, pointing on the red color in the 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 status like details for frozen and active media. To view media by media status
1 2
In the OpsCenter console, select Monitor > Overview. In the Media Summary by Status section, do either of the following:
Click the number of media (link) for a particular media status from the table. For example, click the number for Frozen media. Or Click a colored section of the pie chart that corresponds to a particular media status. For example, click on the red section of the pie chart to view details for Frozen media.
About Top 7 Job Error Log Summary section

The Top 7 Job Error Log Summary section lists seven exit status codes responsible for maximum failed jobs in your environment. The content that is shown in this section is based on the current View pane selection. Data for the last 24 hours is 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 324. The table that appears in the section lists the top seven exit status codes responsible for maximum job failure and also lists the number of failed jobs for each exit status in the selected timeframe. Note that the failed jobs that are shown in the Failed Job Count column are arranged in descending order in the table. By viewing this section, you can quickly analyze the reasons behind maximum job failures in your environment.
Viewing the Services Summary section

The Services Summary section provides a high-level view that shows the total number of running and stopped NetBackup services for the current View pane selection. 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 stopped services.
328
To view running or stopped services
1 2
In the OpsCenter console, select Monitor > Overview. In the Service Summary section, click the number that is shown in the Service Count column of the table. For example, click on the number that is shown for Running services to view details for the services that are running.
Viewing the Master Server Summary section

The Master Server Summary section provides the specific information about the master 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 OpsCenter console Number of the master servers that appear as Not Connected in the OpsCenter console 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 in your 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 backup policy configured for them. To view all master servers
1 2
In the OpsCenter console, select Monitor > Overview. In the Master Server Summary section, click the number that is shown in the Total column.
To view the master servers that are connected
1 2
In the OpsCenter console, select Monitor > Overview. In the Master Server Summary section, click the number that is shown in the Connected column.
To view details of the master servers that are not connected
1 2
In the OpsCenter console, select Monitor > Overview. In the Master Server Summary section, click the number that is shown in the Not Connected column.
329
To view details of the clients that are at risk
1 2
In the OpsCenter console, select Monitor > Overview. In the Master Server Summary section, click the number that is shown in the Clients at Risk column.
Viewing the Job Summary by Exit Status section

The Job Summary by Exit Status section shows an overall distribution of jobs by exit status 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 24 hours is 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 324. A pie chart with different colors represents the job distribution by exit status in the selected timeframe. Each color of the pie chart represents how jobs are distributed in your environment as per the exit status. You can also view the color code summary in this section to know the colors that represent different exit status. Pointing on the pie chart gives the total number and percentage of successful, 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 24 hours, 72 jobs, or 42% jobs in your environment failed. This information is also listed in a tabular format. In addition, a table also shows the amount of data that has been backed up for the selected view and timeframe. You can drill down from this section to see details for failed, successful, or partially successful jobs. To view jobs by exit status
1 2 3
In the OpsCenter console, select Monitor > Overview. Select Summary View from the drop-down list. Note that the drop-down list is located on the top-right corner of the page. In the Job Summary by Exit Status section, do either of the following:
Click the number of jobs (link) corresponding to a particular exit status from the table. Or Click a colored section of the pie chart that corresponds to a particular exit status. For example, click on the red section of the pie chart to view details for failed jobs.
330
Viewing the Drive Summary by Status section

The Drive Summary by Status section shows an overall distribution of drives by drive status for the current View pane selection. This information is shown in a pie chart as well as a table. A pie chart with different colors represents the distribution of drives by drive status in the selected timeframe. Each color of the pie chart represents how drives are distributed in your environment as per the drive status. You can also view the color code summary in this section to know the colors that represent different exit status. Pointing on the pie chart provides the number and percentage of drives with up or down status in your NetBackup environment. For example, pointing on the green color in the pie chart shows that 5 drives or 100% drives in your environment 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
1 2
In the OpsCenter console, select Monitor > Overview. In the Drive Summary by Status section, do either of the following:
Click the number of drives (link) for a particular drive status from the table. For example, click the number for Up drives Or Click a colored section of the pie chart that corresponds to a particular drive status. For example, click on the green section of the pie chart to view details for the drives that are up.
About Top 7 Policies by Failed Jobs section

The Top 7 Policies by Failed Jobs section lists the top five policies which have the maximum failed jobs for the current View pane and timeframe selection. Data for the last 24 hours is 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 324. The table that is shown in the section lists the top seven policies which have maximum failed jobs associated with them. The table also shows the number of failed jobs for each policy. Note that the failed jobs (shown in Total Number of Failed Jobs column) are arranged in descending order in the table. From this section you can quickly view the policies which have the maximum failed jobs associated with them.
Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup jobs
331
Viewing the Alert Summary by Severity section

The Alert Summary by Severity section shows an overall distribution of alerts by severity for the current View pane and timeframe selection. This information is shown in a pie chart as well as a table. Data for the last 24 hours is 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 324. A pie chart with different colors represents the alert distribution by severity in this section. Each color of the pie chart represents how alerts are distributed in your environment as per the alert severity. You can also view the color code summary in this section to know the colors that represent different severity. Pointing on the pie chart gives the number and percentage of alerts with a particular severity in your NetBackup environment. For example, pointing on the green 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
1 2
In the OpsCenter console, select Monitor > Overview. In the Alert Summary by Severity section, do either of the following:
Click the number of alerts (link) for a particular alert severity from the table. 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 particular alert severity. For example, click on the red section of the pie chart to view details for critical alerts.
Monitoring NetBackup jobs

The Monitor > Jobs view provides details of NetBackup jobs. You can use the following views to see NetBackup job information:
332
List View
This view is shown by default when you select Monitor > Jobs. This view displays detailed information about jobs based on the current View pane and timeframe selection.
Note: You can only view jobs data for the

last 30 days from the List View. See Using the List View for monitoring jobs on page 332. Summary View The Summary View contains the different sections which show the NetBackup job distribution by exit status, job state, and job type based on the current View pane and timeframe selection. This information is shown in pie charts and tables. See Using the Summary View for monitoring jobs on page 340. Hierarchical View The Hierarchical View shows all parent-child jobs in a hierarchical fashion based on the current View pane and timeframe selection.
Note: You can only view jobs data for the

last 30 days from the Hierarchical View. See Using the Hierarchical View for monitoring jobs on page 343.
Note: You can select these views from the drop-down list. The drop-down list is located at the top-right corner of the page.
Using the List View for monitoring jobs

This view is displayed when you select Monitor > Jobs. The List View is shown by default. This view displays detailed information for jobs for the current View Pane and timeframe selection. Data for the last 24 hours is 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 324. 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:
333
Job ID
This column shows the unique ID associated with the job (link). This column shows the name of the master server (link) associated with the job. You can click on the link to view details for the master server. This column lists the job type like whether the job is a DB Backup or an Image Cleanup job. This column lists the current NetBackup job state like whether the job is Queued, Waiting for Retry, Done etc. Exit status of the job. The link provides status description and details on troubleshooting in case it failed. This column lists the name of the policy that is associated with the job. This column lists the name of the client on which the job is run. This column lists the date, time, and year when the job started. This column lists the time that is taken by the job. The Elapsed Time is the difference between End Time and Start Time values. For a running job, Elapsed Time is the difference between the current time and Start time.
Master Server
Type
State
Status
Policy
Client
Start Time
Elapsed Time
Note: The contents of the Elapsed Time

column cannot be sorted in ascending or descending order (when you click on the column name.) End Time This column lists the date, time, and year when the job ended. This column lists the size of the job. This column lists the number of files that have been backed up by this job.
Job Size Files
334
% Complete
This column lists the percentage of job that has been completed.
Not all columns are displayed in the table by default. More columns can be added to your view by clicking the Table Settings icon. The Table Settings icon is located on 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
335
Reconciliation Reason Data Reduction Savings (%) Priority State Details
See the online NetBackup Administration Console Help for a detailed description of these fields. More information about how to customize tables and view specific columns is available. See About using tables on page 58.
Viewing the details for a single NetBackup job

All 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:
General The General tab of the Details pane displays all information available for the job. It also includes the contents of all the available columns that can be viewed from the table. The Attempts tab shows details of the attempts that have been made to complete a job. The File List tab shows the files that have been backed up by the job and also their location.
Attempts
File List
To view details for a single NetBackup job
1 2
In the OpsCenter console, select Monitor > Jobs. Click the ID (link) for a job from the Job ID column of the table. View the job details in the Details pane
Viewing the details for a master server associated with a job

Use the following procedure to view the details for a master server that is associated with a job.
336
To view information for the master server that is associated with a job
1 2
In the OpsCenter console, select Monitor > Jobs. Click the server name (link) associated with the job in the Master Server column of the table. The details of the master server are shown on a separate page. You can also enable or disable data collection for the master server from this page.
Viewing policy information for a job

Use the following procedure to view the details for the policy that is associated with a job. To view policy information for a job
1 2 3
In the OpsCenter console, select Monitor > Jobs. Click the policy name (link) for the job in the Policy column of the table. A separate page appears that shows policy information on the following tabs:
General This tab is shown by default. Most of the policy details are listed. Click on the master server link to view details of the master server that is associated with the policy. Schedules This tab displays the properties of schedules that are associated with the policy. This tab displays the details of clients to be backed up This tab shows the files that are to be backed up
Clients
Selection
Filtering on NetBackup job state

You can filter by using any of the built-in job filters. These filters are available from the drop-down list which is present on top of the table. The built-in job filters are the following:
All Jobs (default filter) Active Jobs Select this filter to view details of all the jobs. Select this filter to view only active jobs
337
Queued Jobs Done Jobs Suspended Jobs
Select this filter to view only queued jobs. Select this filter to view only Done jobs. Select this filter to view the jobs that have been suspended. Select this filter to view the jobs that are waiting for retry. Select this filter to view the jobs that are incomplete. Select this filter to view the jobs that have been canceled. Select this filter to view the jobs that are undefined. Select this filter to view the jobs that are successful. Select this filter to view the jobs that are partially successful. Select this filter to view the jobs that failed.
Waiting for Retry Jobs
Incomplete Jobs
Canceled Jobs
Undefined Jobs
Successful Jobs
Partially Successful Jobs
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 62. To view details by job state
1 2
Select Monitor > Jobs. Select a filter from the drop-down list. Note that the drop-down list is located on top of the table.
Controlling NetBackup jobs

Use the following procedure to cancel, suspend, resume, or restart a job. Before you perform these tasks, manually refresh your Web browser to obtain an updated view for all jobs. Note: These tasks are not visible if you log on with an Analyst or a Reporter role.
338
To control a job
1 2 3 4
In the OpsCenter console, select Monitor > Jobs. Ensure that List View is selected in the drop-down list. Note that the drop-down list is located on the top-right corner of the page. Select a job from the table. You may select one or more jobs. Click Cancel, Restart, Resume, Suspend. These buttons are located on top of the table. The OpsCenter console may take some time to show the updated status once you perform the tasks.
Reconciling NetBackup jobs

You can use the Reconcile option to prevent the jobs that failed due to reasons like user terminating a job, host cannot be reached etc. from being billed. By using the Reconcile option and selecting a reason, you can let your service provider know not to bill you for these jobs as these jobs failed due to specific issues at your end. Note: The Reconcile option is disabled in the unlicensed version (Symantec OpsCenter). Before you perform this task, manually refresh your Web browser to obtain an updated view for all jobs To reconcile NetBackup jobs
1 2 3 4 5
In the OpsCenter console, select Monitor > Jobs. Ensure that List View is selected in the drop-down list. Note that the drop-down list is located on the top-right corner of the page. Select a job from the table. You can select one or more jobs. From the More drop-down list, select Reconcile. In the Reconcile Jobs dialog box, select a reason for reconciling the job from the drop-down list. Note that you can select Un-Reconcile from the drop-down list to undo a reconciliation.
Click OK.
339
Changing the job priority

You 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 running NetBackup 6.5.2 or higher versions.
To change the job priority
1 2 3 4 5 6 7
In the OpsCenter console, select Monitor > Jobs. Ensure that List View is selected in the drop-down list. Note that the drop-down list is located on the top-right corner of the page. Select an active job or a queued job from the table. From the More drop-down list, select Change Job Priority. In the Change Priority dialog box, set the job priority to a particular value. You can also increment or decrement the job priority. Click OK. Click Finish. The OpsCenter console may take some time to show the updated status once you perform this task.
Exporting NetBackup job logs

You can export the log files that are associated with a job. You can view or save the exported log files in an Excel format. Note: The Export Job Logs option is not visible if you log on with an Analyst or a Reporter role.
Note: Logs are not available for all job types. Before exporting a log file, ensure that the NetBackup master server is Connected and the selected job logs are enabled. To export the NetBackup log files for a job
1 2
In the OpsCenter console, select Monitor > Jobs. Ensure that List View is selected in the drop-down list. Note that the drop-down list is located on the top-right corner of the page.
340
Select a job from the table. You can export only one job log at a time.
4 5
From the More drop-down list, select Export Job Logs. Click Open or Save from the dialog box to view or save the log file in an Excel format.
Using the Summary View for monitoring jobs

This view is displayed when you select Monitor > Jobs and then select Summary View from the drop-down list. The drop-down list is located at the top-right corner of the page. The content that is shown in the Summary 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 last 48 hours or 72 hours. See Controlling the scope of Monitor views on page 324. The Summary View contains the different sections which display specific information about NetBackup jobs. These sections show NetBackup job information in a table as well as a pie chart. The table and the pie charts include links to filtered detail views. You can use these links to drill down and access detailed information about NetBackup jobs. Note: All the sections that are shown in the Summary View can also be viewed from Monitor > Overview. 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
Viewing the Job Summary by Exit Status section

The Job Summary by Exit Status section shows an overall distribution of jobs by exit status. The data that is shown in this view is 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 24 hours is 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 324.
341
A pie chart with different colors represents the job distribution by exit status in this section. Each color of the pie chart represents how jobs are distributed in your environment as per the exit status. You can also view the color code summary in this section to know the colors that represent different exit status. Pointing on the pie chart gives the number and percentage of jobs with a particular exit status in your NetBackup environment. For example, pointing on the red color in the pie chart shows that in the last 24 hours, 72 jobs or 42% jobs in your environment failed. You can drill down from this section to see details for successful, partially successful, and failed jobs. To view jobs by exit status
1 2 3
In the OpsCenter console, select Monitor > Jobs. Select Summary View from the drop-down list. Note that the drop-down list is located on the top-right corner of the page. In the Job Summary by Exit Status section, do either of the following:
Click the number of jobs (link) corresponding to a particular exit status from the table. Or Click a colored section of the pie chart that corresponds to a particular exit status. For example, click on the red section of the pie chart to view details for failed jobs.
Viewing the Job Summary by State section

The Job Summary by State section shows an overall distribution of jobs by the NetBackup 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 24 hours is 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 324. A pie chart with different colors represents the job distribution by job state. Each color of the pie chart represents how jobs are distributed in your environment as per the job state. You can also view the color code summary in this section to know the colors that represent different job states. Pointing on the pie chart gives the number and percentage of jobs in a particular job state in your NetBackup environment. For example, pointing on the yellow color in the pie chart shows that in the last 24 hours, 22 jobs, or 42% jobs in your environment are in a queued state. You can drill down from this section to see details for the jobs that failed, the jobs that are waiting for retry, queued or active jobs etc.
342
To view jobs by job state
1 2 3
In the OpsCenter console, select Monitor > Jobs. Select Summary View from the drop-down list. Note that the drop-down list is located on the top-right corner of the page. 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. 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 particular job state. For example, click on the yellow section of the pie chart to view details for Queued jobs.
Viewing the Job Summary by Type section

The Job Summary by Type section shows an overall distribution of jobs by the job type 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 24 hours is shown by default. You can also view data for the last 48 or 72 hours. See Controlling the scope of Monitor views on page 324. A pie chart with different colors represents the job distribution by job type in this section. Each color of the pie chart represents how jobs are distributed in your environment as per the job type. You can also view the color code summary in this section to know the colors that represent different job types. Pointing on the pie chart gives the number and percentage of jobs of a particular job type in your NetBackup environment. For example, pointing on the red color in the pie chart shows that in the last 24 hours, 22 jobs or 42% jobs in your environment are DBBackup jobs. You can drill down from this section to see details for different job types like DBBackup, Image Cleanup etc. To view jobs by job type
1 2 3
In the OpsCenter console, select Monitor > Jobs. Select Summary View from the drop-down list. Note that the drop-down list is located on the top-right corner of the page. In the Job Summary by Type section, do either of the following:
Click the number of jobs (link) corresponding to a particular job type from the table. For example, click on the number that is shown for DBBackup jobs. Or
343
Click a colored section of the pie chart that corresponds to a particular job type. For example, click on the red section of the pie chart to view details for DBBackup jobs.
Using the Hierarchical View for monitoring jobs

This view is displayed when you select Monitor > Jobs and then select Hierarchical View from the drop-down list. The data that is shown 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 last 48 or 72 hours. Note: You can only view jobs data for the last 30 days from the Hierarchical View. See Controlling the scope of Monitor views on page 324. In the Hierarchical View, all related jobs can be grouped and you can see all parent-child jobs in a hierarchical fashion. You can view details of only the top level, parent job in this view with the ability to expand and drill into the details of child jobs if there are failures. The Hierarchical View shows details of all jobs and also highlights the parent-child relationship between jobs wherever applicable. All parent jobs have a +sign before the job ID. You can click the + sign to see all child jobs. A child job is indented to the 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 does not have a relationship with any other job (meaning it is neither a parent nor a child job), it is represented only by its job ID in the Job ID column. Neither is there a + sign before the job ID of such a job nor this job is indented to the right-hand side. Note the following things about the related jobs that are shown in the Hierarchical View:
The filters are applied only to parent jobs. The filters are not applied to child jobs. For example, if you apply the Partially Successful Jobs filter, child jobs are not considered at all. Only parent jobs or unrelated jobs (jobs that are not related to any other job) with partially successful status are considered. The sorting feature in the Hierarchical View applies to both parent jobs and child jobs. When you expand a parent job, the current selected sort order is applied to child jobs. All tasks that apply to the parent job are also applicable to its child jobs.
344
Viewing the details for a single NetBackup job

All 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:
General The General tab of the Details pane displays all information available for the job. It also includes the contents of all the available columns that can be viewed from the table. The Attempts tab shows details of the attempts that have been made to complete a job. The File List tab shows the files that have been backed up by the job and also their location.
Attempts
File List
To view details for a single NetBackup job
1 2 3 4
In the OpsCenter console, select Monitor > Jobs. Select Hierarchical View from the drop-down list. The drop-down list is located at the top-right corner of the view. Click the ID (link) for a job from the Job ID column of the table. View the job details in the Details pane.
Viewing the details for a master server associated with a job

Use the following procedure to view the details for a master server that is associated with a job. To view information for the master server that is associated with a job
1 2 3
In the OpsCenter console, select Monitor > Jobs. Select Hierarchical View from the drop-down list. The drop-down list is located at the top-right corner of the view. Click the server name (link) associated with the job in the Master Server column of the table. The details of the master server are shown on a separate page. You can also enable or disable data collection for the master server from this page.
345
Viewing policy information for a job

Use the following procedure to view the details for the policy that is associated with a job. Note: You can also view policy information from the List View. To view policy information for a job
1 2 3 4
In the OpsCenter console, select Monitor > Jobs. Select Hierarchical View from the drop-down list. The drop-down list is located at the top-right corner of the view. Click the policy name (link) for the job in the Policy column of the table. A separate page appears that shows policy information on the following tabs:
General (default tab) Schedules This tab shows most of the policy details. This tab displays the properties of the schedules that are associated with the policy. This tab displays the details of clients to be backed up. This tab shows the files that are to be backed up.
Clients
Selection
Filtering on NetBackup job state

You can filter by using any of the following built-in job filters. These filters are available from the drop-down list which is present on top of the table. The built-in job filters are the following:
All Jobs (default filter) Active Jobs Queued Jobs Done Jobs Suspended Jobs Select this filter to view details of all the jobs. Select this filter to view only active jobs Select this filter to view only queued jobs. Select this filter to view only Done jobs. Select this filter to view the jobs that have been suspended.
346
Waiting for Retry Jobs
Select this filter to view the jobs that are waiting for retry. Select this filter to view the jobs that are incomplete. Select this filter to view the jobs that are undefined. Select this filter to view the jobs that have been canceled. Select this filter to view the jobs that are successful. Select this filter to view the jobs that are partially successful. Select this filter to view the jobs that failed.
Incomplete Jobs
Undefined Jobs
Canceled Jobs
Successful Jobs
Partially Successful Jobs
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 62. To view details by job state
1 2 3
In the OpsCenter console, select Monitor > Jobs. Select Hierarchical View from the drop-down list. The drop-down list is located at the top-right corner of the view. Select a filter from the drop-down list. Note that the drop-down list is located on top of the table.
Controlling NetBackup jobs

Use the following procedure to cancel, suspend, resume, or restart a job. Before you perform these tasks, manually refresh your Web browser to obtain an updated view for all jobs. Note: These tasks are not visible if you log on with an Analyst or a Reporter role. To control a job
1 2
In the OpsCenter console, select Monitor > Jobs. Select Hierarchical View from the drop-down list. Note that the drop-down list is located on the top-right corner of the page.
347
3 4
Select a job from the table. You may select one or more jobs. Click Cancel, Restart, Resume, Suspend. The OpsCenter console may take some time to show the updated status once you perform these tasks.
Reconciling NetBackup jobs

You can use the Reconcile option to prevent the jobs that failed due to reasons like user terminating a job, host cannot be reached etc. from being billed. By using the Reconcile option and selecting a reason, you can let your service provider know not to bill you for these jobs as these jobs failed due to specific issues at your end. Note: The Reconcile option is disabled in the unlicensed version (Symantec OpsCenter). The Reconcile option is not visible if you log on with an Analyst or a Reporter role. Before you perform this task, manually refresh your Web browser to obtain an updated view for all jobs To reconcile NetBackup jobs
1 2 3 4 5
In the OpsCenter console, select Monitor > Jobs. Select Hierarchical View from the drop-down list. Note that the drop-down list is located on the top-right corner of the page. Select a job from the table. You can select one or more jobs. From the More drop-down list, select Reconcile. In the Reconcile Jobs dialog box, select a reason for reconciling the job from the drop-down list. Note that you can select Un-Reconcile from the drop-down list to undo a reconciliation.
Click OK.
Changing the job priority

You 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.
348
Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup services
Priority can be changed only for jobs from the master servers that are running NetBackup 6.5.2 or higher versions.
Note: The Change Job Priority option is not visible if you log on with an Analyst or a Reporter role. To change the job priority
1 2 3 4 5 6 7
In the OpsCenter console, select Monitor > Jobs. Select Hierarchical View from the drop-down list. Note that the drop-down list is located on the top-right corner of the page. Select an active job or a queued job from the table. From the More drop-down list, select Change Job Priority. In the Change Priority dialog box, set the job priority to a particular value. You can also increment or decrement the job priority. Click OK. Click Finish. The OpsCenter console may take some time to show the updated status once you perform this task.
Monitoring NetBackup services

This view is displayed when you select Monitor > Services. This view contains detailed information for services. The data that is shown in this view is based on the current View pane selection. See Controlling the scope of Monitor views on page 324. The table that appears in this view has the following columns:
Name Host Name This column lists the name of the service. This column lists the name of the master server or media server where the service or daemon is present. This column lists the NetBackup service type. Example: Vault Manager, Device Manager, or Service Layer
Service Type
Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup services
349
Status
The operational status of the service or daemon. This status can be Stopped, Running, or Other. Other can be Not Installed, Not Licensed, Start Pending, Stop Pending, Restart Pending, Failed, or Unknown.
Note: The status for some services may

show as Stopped on the Monitor > Services page in the OpsCenter console. This may be because the license for these services is either not installed or configured for a specific media or master server.
You can perform the following tasks from this view:

Use filters to view specific services See Filtering on NetBackup service type on page 349. See Controlling NetBackup services on page 350.
Control NetBackup services
Filtering on NetBackup service type

You can filter by using any of the four built-in filters. These filters are available from the drop-down list which is present on top of the table. The built-in filters are the following:
All Services (default filter) Select this filter to view details of all the services. Select this filter to view details of the services that have been stopped. Select this filter to view details of running services. Select this filter to view details of all other services like Not Licensed, Unknown (not recognized by OpsCenter), or Not Applicable (some services may not be applicable to earlier versions).
Stopped Services
Running Services
Other Services
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 62.
350
Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup policies
Use the following procedure to view details by type of service. To view details by type of service
1 2
In the OpsCenter console, select Monitor > Services. Select a filter from the drop-down list. Note that the drop-down list is located on top of the table.
Controlling NetBackup services

Under certain circumstances there may be issues among multiple OpsCenter users. For instance, one OpsCenter user stops a service while another user tries to start the same service. Note: NetBackup service layer (nbsl) cannot be controlled from OpsCenter. To control a service
1 2 3 4
Refresh your Web browser to obtain an updated state for all services. In the OpsCenter console, select Monitor > Services. Select a service from the table. You can select one or more services. Click Start, Stop, or Restart. Note that these tasks are located on top of the table. Note: These tasks are not visible if you log on with an Analyst or a Reporter role. The OpsCenter console may take some time to show the updated status once you perform these tasks. Stop, Running, or Restart Pending appears in the Status 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 policies

The Monitor > Policies view provides details of NetBackup policies. You can use the following views to see NetBackup policy information:
351
List View
The List View is shown by default when you select Monitor > Policies. This view shows detailed information about NetBackup policies based on the current View pane selection. See Using the List View for monitoring NetBackup policies on page 351.
Summary View
The Summary View contains the different sections that display specific information about NetBackup policies based on the current View pane and timeframe selection. These sections show specific policy information in a table as well as a pie chart. See Using the Summary View for monitoring policies on page 357.
Using the List View for monitoring NetBackup policies

This view is displayed when you select Monitor > Policies. This view contains detailed information about policies. The data that is shown in this view is based on the current View pane selection. See Controlling the scope of Monitor views on page 324. The table that appears in this view has the following columns:
Name Name of the policy. Click the link to view details about the policy. Name of the master server that is associated with the policy. Click the link to view details of master server. This column is the policy type. Usually, the Policy type determines the type of clients that can be backed up by this policy. Example: DB2, NBU-Catalog, Oracle, Sybase, Vault etc. Storage that is associated with the policy. Click the link to view details for storage.
Master Server
Type
Storage
352
Volume Pool
Volume pool that is associated with the policy. Click the link to view details of volume pool. Interval (in minutes) between two checkpoints in NetBackup. The total number of jobs that are associated with the policy. Priority that you have defined for the policy. Zero means the lowest priority. This column determines whether the policy is Active or not.
CheckPoint Interval
Jobs/Policy
Priority
Active
Not all of the available columns appear initially in this view. The following columns do not appear, but can be added to your view by clicking the Table Settings icon:

Data Classification Effective Date Compression 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
353
Keyword Phrase Policy Domain Name
See the online NetBackup Administration Console Help for a detailed description of these fields. More information about how to customize tables and view specific columns is available. See About using tables on page 58. You can perform the following tasks from this view:
Use filters to view specific policies See Filtering on NetBackup policy type on page 353. See Viewing details for a single NetBackup policy on page 354. See Viewing the details for a master server associated with a policy on page 355.
View the details for a single NetBackup policy View the details for a master server associated with a policy
View the details for storage that is associated See Viewing the details for storage with a policy associated with a policy on page 355. View the details for a volume pool that is associated with a policy Manage a job policy Start a manual backup View the history for a job policy See Viewing the details for a volume pool associated with a policy on page 355. See Managing a job policy on page 356. See Starting a manual backup on page 356. See Viewing the history for a single job policy on page 357.
See Using the Summary View for monitoring policies on page 357.
Filtering on NetBackup policy type

You can filter by using any of the seven built-in filters. These filters are available from the drop-down list which is present on top of the table. The built-in filters are the following:
All Policies (default filter) Select this filter to view details of all NetBackup policies. Select this filter to view details of the policies that are active.
Active Policies
354
Inactive Policies
Select this filter to view details of the policies that are inactive. Select this filter to view details of all policies that apply to Windows clients. Select this filter to view details of catalog policies. Select this filter to view details of Standard policies. Select this filter to view details of all other policies like DB2 policies, SAP policies, OS2 policies etc.
Windows Policies
Catalog Policies
Standard Policies
Other Policies
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 62. Use the following procedure to view details by type of policy. To view details by type of policy
1 2
In the OpsCenter console, select Monitor > Policies. Select a filter from the drop-down list. Note that the drop-down list is located on top of the table.
Viewing details for a single NetBackup policy

All the details that are associated with a policy 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:
General The General tab of the Details pane displays all information available for the policy. It also includes contents of all the columns that can be viewed from the table. You can also click the master server name (link) to get details of the master server. Schedules The Schedules tab displays details of the schedules that are associated with the policy. The Clients tab shows details of clients to be backed up by the policy.
Clients
355
Selections
The Selections tab shows the files that have been backed up by the policy and also their location.
To view details for a single NetBackup policy
1 2 3
In the OpsCenter console, select Monitor > Policies. Click the name (link) for a policy from the Name column of the table. View the policy details in the Details pane.
Viewing the details for a master server associated with a policy

Use the following procedure to view the details for a master server that is associated with a policy. To view information for the master server that is associated with a policy
1 2
In the OpsCenter console, select Monitor > Policies. Click the server name (link) associated with the policy from the Master Server column of the table. The details of the master server are shown on a separate page. You can also enable or disable data collection for the master server from this page.
Viewing the details for storage associated with a policy

Use the following procedure to view the details for the storage that is associated with a policy. To view information for the storage that is associated with a policy
1 2
In the OpsCenter console, select Monitor > Policies. Click the storage name (link) associated with the policy in the Storage column of the table. The details of the storage are shown on a separate page. You can also view details for the master server from this page.
Viewing the details for a volume pool associated with a policy

Use the following procedure to view the details for a volume pool that is associated with a policy. To view information for the volume pool that is associated with a policy
1 2
In the OpsCenter console, select Monitor > Policies. Click the volume pool name (link) associated with the policy from the Volume Pool column in the table. The details of the volume pool are shown on a separate page.
356
Managing a job policy

Use the following procedure to activate or deactivate a policy. Before you perform these tasks, manually refresh your Web browser to obtain an updated view of all policies. Note: These tasks are not visible if you log on with an Analyst or a Reporter role. To activate or deactivate a policy
1 2 3
In the OpsCenter console, select Monitor > Policies. Select a job policy from the table. Click Activate or Deactivate. Note that these options are located on top of the table. The OpsCenter console may take some time to show the updated status once you perform these tasks.
Starting a manual backup

Use the following procedure to start a manual backup. Before you perform this task, 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 you perform this task. Note: This task is not visible if you log on with an Analyst or a Reporter role. To start a manual backup
1 2 3 4
In the OpsCenter console, select Monitor > Policies. Select a policy from the table. You can select only one policy and it must be an active policy. Click Manual Backup. Note that this option is located on top of the table. 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 highest retention level. If you do not select a client, NetBackup backs up all scheduled clients.
357
Viewing the history for a single job policy

Use 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
1 2 3 4
In the OpsCenter console, select Monitor > Policies. Select a job policy from the table. Click View History. Note that this option is located on top of the table. The Compare Policies tab displays the policy versions. You must select two versions from the Retirement Date column to compare versions. The changes are highlighted in red color. To view only the differences between the versions, click the View Differences tab.
Using the Summary View for monitoring policies

This view is displayed when you select Monitor > Policies and then select Summary View from the drop-down list. The drop-down list is located at the top-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 View pane and timeframe selection. Data for the last 24 hours is shown by default. You can also view data for the last 48 or 72 hours. See Controlling the scope of Monitor views on page 324. The Summary View contains the different sections which display specific information about NetBackup policies. These sections show specific policy information in a table as well as a pie chart. The table and the pie charts include links to filtered detail views. You can use these links to drill down and access detailed 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
358
About Top 5 Policies by Data Backed up section

The Top 5 Policies by Data Backed up section lists the top five policies which have the maximum data backed up for the current View pane and timeframe selection. Data for the last 24 hours is shown by default. You can also view data for the last 48 or 72 hours. See Controlling the scope of Monitor views on page 324. The table that is shown in the section lists the top five policies which have maximum data backed up. The table also shows the data that is backed up for each policy. Note that the data that is backed up (shown in Volume (Bytes) column) is arranged in descending order in the table. From this section, you can quickly view the policies which have the maximum data backed up.
About Top 7 Policies by Failed Jobs section

The Top 7 Policies by Failed Jobs section lists seven policies which have the maximum failed jobs for the current View pane and timeframe selection. Data for the last 24 hours is shown by default. You can also view data for the last 48 or 72 hours. See Controlling the scope of Monitor views on page 324. The table that is shown in the section lists the top seven policies which have maximum failed jobs associated with them. The table also shows the total number of failed jobs for each policy. Note that the failed jobs (shown in Total Number of Jobs column) are arranged in descending order in the table. From this section, you can quickly view the policies which have the maximum failed jobs associated with them. Note: This section can also be viewed from Monitor > Overview.
About Top 7 Policies by No. of Jobs section

The Top 7 Policies by No. of Jobs section lists seven policies which have the maximum number of jobs. This data 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 last 48 or 72 hours. See Controlling the scope of Monitor views on page 324. The table that is shown in the section lists the policies which have maximum number of jobs. The table also shows the total number of jobs for each policy. Note that the total number of jobs for each policy (shown in Total Number of Jobs column) are arranged in descending order in the table. From this section, you can
Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup media
359
quickly view the policies which have the maximum number of jobs associated with them.
Monitoring NetBackup media

The Monitor > Media view provides details of NetBackup media. You can use the following views to see details about NetBackup media:
List View The List View is shown by default when you select Monitor > Media. This view shows detailed information about NetBackup media for the current View pane selection. See Using the List View for monitoring NetBackup media on page 360. Summary View The Summary View displays the volume pool available for each master server for the current View pane selection. It also shows other media details that are associated with the master server like Frozen Media Count, Suspended Media Count etc. See Using the Summary View for monitoring NetBackup media on page 364. Hierarchical View by Volume Pool The Hierarchical View by Volume Pool shows details of all media and also groups media by volume pool for the current View pane selection. See Using the Hierarchical View by Volume Pool for monitoring media on page 365. Hierarchical View by Volume Group The Hierarchical View by Volume Group shows details of all media and also groups media by volume group for the current View pane selection. See Using the Hierarchical View by Volume Group for monitoring media on page 366.
360
Using the List View for monitoring NetBackup media

This view is displayed when you select Monitor > Media. This view contains detailed information for media. This data is based on the current View pane selection. See Controlling the scope of Monitor views on page 324. The table that appears in this view has the following columns:
Media ID Unique ID associated with a media. Click the link to view details about the media. Name of the master server that is associated with the media. Click the link to view details of master server. Type of media like 8mm, 4mm etc. Specifies the robot type of the robot to inventory. Example: tl4, tl8 etc. Unique, logical identification number for the robot to inventory. Slot in the robot that contains the volume. The number of times that the volume has been mounted. The date when the volume was assigned for use. The maximum number of mounts (or cleanings) that are allowed for the volume. Zero (0) indicates unlimited mounts. Date when the images on the volume expire. The most recent time NetBackup used the volume for backups. Current media status like Frozen, Active etc. Capacity that has been used.
Master Server
Media Type Robot Type
Robot Number
Slot Mounts
Time Assigned
Max. Mounts
Data Expiration Last Written
Media Status Used Capacity
Last Write Host
361
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 the online NetBackup Administration Console Help for a detailed description of these fields.
362
More information about how to customize tables and view specific columns is available. See About using tables on page 58. You can perform the following tasks from this view:
View the details for a particular NetBackup See Viewing the details for NetBackup media media on page 362. View the details for a master server that is associated with the media Use filters to view specific media See Viewing the details for a master server associated with the media on page 362. See Filtering on NetBackup media type on page 362. See Controlling media on page 363.
Control media
Viewing the details for NetBackup media

All the details that are associated with a media can be viewed from the Details pane. The Details pane is located at the bottom of the view. To view the details for a particular media
1 2
In the OpsCenter console, select Monitor > Media. Click a drilldown link from the Media ID column. View the media properties from the Details pane. From the Details pane, you can also click the master server link to see details about the master server that is associated with the media.
Viewing the details for a master server associated with the media
Use the following procedure to view the details for a master server that is associated with a media. To view the details for a master server associated with a media
1 2
In the OpsCenter console, select Monitor > Media. Click the server name (link) associated with the media in the Master Server column of the table. The details of the master server are shown on a separate page.
Filtering on NetBackup media type

You can sort and filter this view to focus on the specific type of media that you want to see. For example, you can create and apply a filter that displays full media
363
only. You can filter by using any of the built-in filters. These filters are available from the drop-down list which is present on top of the table. The built-in filters are the following:
All Media (default filter) Assigned Media Select this filter to view details of all media. Select this filter to view details of the media that have been assigned to an individual for further action. Select this filter to view details of the media that are unassigned. Select this filter to view details of the media that are frozen. Select this filter to view details of the media that are full. Select this filter to view details of the media that are suspended. Select this filter to view details of all other media like Multi Retention Level media, BE media etc. Select this filter to view details of media with Active status. Select this filter to view details of cleaning media.
Unassigned Media
Frozen Media
Full Media
Suspended Media
Other Media
Active Media
Cleaning Media
In addition to the built-in filters, you can create your own custom filters. See Using filters to customize your views on page 62. Use the following procedure to view details by type of media. To view details by type of media
1 2
In the OpsCenter console, select Monitor > Media. Select a filter from the drop-down list. Note that the drop-down list is located on top of the table.
Controlling media
Use the following procedure to freeze, unfreeze, suspend, or unsuspend specific media. 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.
364
Note: These tasks are not visible if you log on with an Analyst or a Reporter role. To perform media tasks
1 2 3
In the OpsCenter console, select Monitor > Media. Select a media ID from the table (use the check box). Click Freeze, Unfreeze, Suspend, or Unsuspend. Note that these options are present on top of the table. The OpsCenter console may take some time to show the updated status once you perform these tasks.
Using the Summary View for monitoring NetBackup media

This view is displayed when you select Monitor > Media and then select Summary View from the drop-down list. The drop-down list is located at the top-right corner of the page. The data that is shown in this view is based on the current View pane selection. See Controlling the scope of Monitor views on page 324. The table that appears in this view displays the volume pool available for each master server. It also shows other media details that are associated with the master server like Frozen Media Count, Suspended Media Count etc. The following columns are shown in the table:
Master Server Volume Pool name Name of the master server Name of the volume pool that is associated with the master server Total number of the frozen media that is associated with the master server. Total number of the suspended media that is associated with the master server. Total number of the full media associated with the master server. Total number of active media associated with the master server. Total number of all other media like Multi Retention Level media, BE media etc. that are associated with the master server .
Frozen Media Count
Suspended Media Count
Full Media Count
Active Media Count
Other Media Count
365
Available Media Count
Total number of the media that are available for the master server.
Using the Hierarchical View by Volume Pool for monitoring media

This view is displayed when you select Monitor > Media and then select Heirarchical View by Volume Pool from the drop-down list. The drop-down list is located at the top-right corner of the page. The data that is shown in this view is based on the current View pane selection. See Controlling the scope of Monitor views on page 324. The Hierarchical View by Volume Pool shows details of all media and also groups media by volume pool. Each volume pool that is shown in the Media ID column has a +sign before it. You can expand a volume pool to see all media that are a part of this volume pool. Note that the media are indented to the right-hand side in the Media ID column. The sorting feature in this view applies only to media in the volume pool. When you expand a volume pool, the current selected sort order is applied to media in the pool. The following tasks can be performed from this view:
View the details for volume pool See Viewing the details for volume pool on page 365.
View details for the media that are a part of See Viewing the details for media a specific volume pool on page 366. Control media See Controlling media on page 366.
Viewing the details for volume pool

Use the following procedure to view the details for a volume pool. To view details for a volume pool
1 2 3
In the OpsCenter console, select Monitor > Media. Select Hierarchical View by Volume Pool from the drop-down list. The drop-down list is located at the top-right corner of the page. Click a volume pool (link) from the Media ID column. Note that a volume pool has a + sign on the left side. The details for the volume pool are shown in the General tab at the bottom of this view.
366
Viewing the details for media

Use the following procedure to view details for the media that are part of a specific volume pool. To view the details for media
1 2 3
In the OpsCenter console, select Monitor > Media. Select Hierarchical View by Volume Pool from the drop-down list. The drop-down list is located at the top-right corner of the page. Expand a volume pool from the Media ID column. This shows the media that are a part of the volume pool. Note that the media are indented to the right-hand side Click the media ID (link). Details for the media are shown in the General tab at the bottom of the view.
Controlling media
Use the following procedure to freeze, unfreeze, suspend, or unsuspend specific media. 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. Note: These tasks are not visible if you log on with an Analyst or a Reporter role. To perform media tasks
1 2 3
In the OpsCenter console, select Monitor > Media. Select Hierarchical View by Volume Pool from the drop-down list. The drop-down list is located at the top-right corner of the page. Expand a volume pool from the Media ID column. This shows the media that are a part of the volume pool. Note that the media are indented to the right-hand side Select a media ID (use the check box). Click Freeze, Unfreeze, Suspend, or Unsuspend. Note that these tasks are present on top of the table. The OpsCenter console may take some time to show the updated status once you perform these tasks.
4 5
Using the Hierarchical View by Volume Group for monitoring media

This view is displayed when you select Monitor > Media and then select Heirarchical View by Volume Group from the drop-down list. The drop-down
367
list is located at the top-right corner of the page. The data that is shown in this view is based on the current View pane selection. See Controlling the scope of Monitor views on page 324. The Hierarchical View by Volume Group shows details of all media and also groups media by volume group. Each volume group shown in the Media ID column has a +sign before it. You can expand a volume group to see all media that are a part of this volume group. Note that the media are indented to the right-hand side in the Media ID column. The sorting feature in this view applies to media in the volume group. When you expand a volume group, the current selected sort order is applied to media in that group. You can perform the following tasks from this view:
View the details for a volume group See Viewing the details for a volume group on page 367.
View details for the media that are part of a See Viewing the details for media specific volume group on page 367. Control media See Controlling media on page 368.
Viewing the details for a volume group

Use the following procedure to view the details for a specific volume group. To view details for a volume group
1 2 3
In the OpsCenter console, select Monitor > Media. Select Hierarchical View by Volume Group from the drop-down list. The drop-down list is located at the top-right corner of the page. Click a volume group (link) from the Media ID column. Note that a volume group has a + sign on the left side. The details for the volume group are shown in the General tab at the bottom of this view.
Viewing the details for media

Use the following procedure to view details for media that are part of a specific volume group. To view the details for media
1 2
In the OpsCenter console, select Monitor > Media. Select Hierarchical View by Volume Group from the drop-down list. The drop-down list is located at the top-right corner of the page.
368
Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup devices
Expand a volume group from the Media ID column. This shows the media that are a part of the volume group. Note that the media are indented to the right-hand side Click the media ID (link). Details for the media are shown in the General tab at the bottom of the view.
Controlling media
Use the following procedure to freeze, unfreeze, suspend, or unsuspend specific media. 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. Note: These tasks are not visible if you log on with an Analyst or a Reporter role. To perform media tasks
1 2 3
In the OpsCenter console, select Monitor > Media. Select Hierarchical View by Volume Group from the drop-down list. The drop-down list is located at the top-right corner of the page. Expand a volume group from the Media ID column. This shows the media that are a part of the volume group. Note that the media are indented to the right-hand side Select a media ID (use the check box). Click Freeze, Unfreeze, Suspend, or Unsuspend. Note that these options are present on top of the table. The OpsCenter console may take some time to show the updated status once you perform these tasks.
4 5
Monitoring NetBackup devices

This view is displayed when you select Monitor > Devices. This view contains the following two tabs:
369
Drives
This tab is shown by default when you select Monitor > Devices. The contents of the Drives tab are shown by default. This view displays detailed information about drives based on the current View pane selection. See Using the List View for monitoring drives on page 369. See Using the Summary view to monitor drives on page 373.
Disk Pools
This view displays detailed information about the disk pools that are configured for use by NetBackup based on the current View pane selection. See Monitoring NetBackup disk pools on page 374.
Using the List View for monitoring drives

This view is displayed when you select Monitor > Devices > Drives. This view contains detailed information for drives. The data that is shown in this view is based on the current View pane selection. See Controlling the scope of Monitor views on page 324. The table that appears in this view shows the following information:
Drive Name The name that is assigned to the drive when it was added to NetBackup. The name of the device host where the drive is connected. Name of the master server that is associated with the drive. Type of drive like 4mm, 8mm etc. The type of robot that contains this drive. Contains Yes if the path is enabled. Contains No if the path is not enabled. If multiple drive paths are configured, this column contains Multiple.
Device Host
Master Server
Drive Type Robot Type Enabled
370

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
371
Total Time User Name VM Host Write Enabled
See the online NetBackup Administration Console Help for a detailed description of these fields. More information about how to customize tables and view specific columns is available. See About using tables on page 58. You can perform the following tasks from this view:
View the details for a single drive See Viewing the details for a single drive on page 371. See Viewing the details for a master server associated with a drive on page 371. See Filtering on NetBackup drive category on page 372. See Controlling drives on page 372.
View the details for a master server that is associated with a drive Use filters to view specific drives
Control drives
Viewing the details for a single drive

All the details that are associated with a drive can be viewed from the Details pane. The Details pane is located at the bottom of the view. To view the details for a single drive
1 2
Select Monitor > Devices > Drives. The List View is shown by default. Click the drilldown link from the Drive Name column. The drive information can be viewed from the General and Paths tab of the Details pane. From the General tab, you can also click the master server link to see details about the master server that is associated with the drive.
Viewing the details for a master server associated with a drive

Use the following procedure to view details for a master server that is associated with a drive.
372
To view the details for a master server associated with a drive
1 2
Select Monitor > Devices > Drives. The List View is shown by default. Click the drilldown link from the Master Server column. The master server information can be viewed from a separate page.
Filtering on NetBackup drive category

You can sort and filter this view to focus on the specific type of drives that you want to see. For example, you can apply a filter that displays only those drives that are up. You can filter by using any of the built-in filters. These filters are available from the drop-down list which is present on top of the table. The following built-in filters are available:
All Drives The All Drives filter is the default filter. Select this filter to view all drives. Select this filter to view only those drives that are up. For up drives, all drive paths are up. Select this filter to view only those drives that are down. For down drives, all drive paths are down. Select this filter to view mixed drives. For mixed drives, some drive paths are up and some drive paths are down.
Up Drives
Down Drives
Mixed Drives
In addition to the built-in filters, you can create your own custom filters. See Using filters to customize your views on page 62. Use the following procedure to view details by type of drives. To view details by type of drives
1 2
In the OpsCenter console, select Monitor > Devices > Drives. Ensure that List View is selected in the drop-down list. Select a filter from the drop-down list. Note that the drop-down list is located on top of the table.
Controlling drives
See the NetBackup Administrator's Guide, Volume I for information on drive states and how to control drives.
373
Before you perform these tasks, manually refresh your Web browser to obtain an updated view of all drives. When you refresh, you also ensure that the drive is not involved in any tasks by other users. Note: These tasks are not visible if you log on with an Analyst or a Reporter role. To control drives
1 2 3
In the OpsCenter console, select Monitor > Devices > Drives. The List View is displayed by default. Select a drive from the Drive Name column in the table. Click Up, Down, or Reset. Note that these buttons are located on top of the drive details table. The OpsCenter console may take some time to show the updated status once you perform these tasks.
Using the Summary view to monitor drives

This view is displayed when you select Monitor > Devices > Drives and then select Summary View from the drop-down list. The drop-down list is located at the top-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 section

The Drive Summary by Status section shows an overall distribution of drives by drive status for the current View pane selection. This information is shown in a pie chart as well as a table. Each color of the pie chart represents how drives are distributed in your environment as per the drive status. You can also view the color code summary in this section to know the colors that represent different exit status. Pointing on the pie chart gives the number and percentage of drives with up or down status in your NetBackup environment. For example, pointing on the green color in the pie 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.
374
You can drill down from this section to see details of the drives that are up or down. To view drives by drive status
1 2
In the OpsCenter console, select Monitor > Jobs. In the Drive Summary by Status section, do either of the following:
Click the number of drives (link) for a particular drive status from the table. For example, click the number for Up drives Or Click a colored section of the pie chart that corresponds to a particular drive status. For example, click on the green section of the pie chart to view details for the drives that are up.
Monitoring NetBackup disk pools

This view is displayed when you select Monitor > Devices > Disk Pools. This view displays detailed information about the disk pools that are configured for use by NetBackup. The data that is shown in this view is based on the current View pane selection. See Controlling the scope of Monitor views on page 324. The table that appears in this view shows the following information:
Name Server Type Name of the disk pool The storage server type. For OpenStorage, the server type depends on the vendor name. Number of disk volumes in the disk pool. The amount of storage space in use. The total raw, unformatted size of the storage in the disk pool. The estimated amount of disk space available for storage after file metadata overhead is taken into account. The low water mark for the disk pool. (The default is 80%.) When the capacity of the disk pool returns to the low water mark, NetBackup again assigns jobs to the storage unit.
Number of Volumes Used Capacity Raw Size
Usable Size
Low Watermark (%)
Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup hosts
375

High Water Mark(%) Master Server State Imported
See the online NetBackup Administration Console Help for a detailed description of these fields. More information about how to customize tables and view specific columns is available. See About using tables on page 58. You can perform the following task from this view:
View the details for a single disk pool See Viewing the details for a single disk pool on page 375.
Viewing the details for a single disk pool

All the details that are associated with a disk pool can be viewed from the Details pane. The Details pane is located at the bottom of the view. To view the details for a single disk pool
1 2
In the OpsCenter console, select Monitor > Devices > Disk Pools. Click the drilldown link from the Name column. The disk pool information can 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 details about the master server that is associated with the disk pool.
Monitoring NetBackup hosts

This view is displayed when you select Monitor > Hosts. This view contains the following subtabs:
376
Master Server
This tab is shown by default when you select Monitor > Hosts. This view displays detailed information about NetBackup master servers based on the current View pane selection. See Monitoring NetBackup master servers on page 376.
Media Server
This view displays detailed information about NetBackup media servers based on the current View pane selection. See Monitoring NetBackup media servers on page 378.
Client
This view displays detailed information about NetBackup clients based on the current View pane selection. See Monitoring NetBackup clients on page 378.
Monitoring NetBackup master servers

This view shows details of master servers. The data that is shown in this view is based on the current View pane selection. See Controlling the scope of Monitor views on page 324. The table that appears in this view shows the following columns:
Network Name Fully qualified domain name or IP address of the master server that is configured. The display name that you have chosen for the master server. Operating system of the master server. Back up product from where the data is being collected like PureDisk, Backup Exec etc. The last time when OpsCenter successfully initiated contact with the master server. This does not necessarily represent the last time that OpsCenter collected information from the master server.
Display Name
Operating System Product
Last Contact
377
State
Shows the current state of the master server like Connected, Not Connected etc.
You can perform the following task from this view:

Use filters to view specific master servers See Filtering by NetBackup master server type and status on page 377.
Filtering by NetBackup master server type and status

You can sort and filter this view to focus on the specific type of master servers that you want to see. For example, you can apply a filter that displays Windows servers only. These filters are available from the drop-down list which is present on top of the table. The built-in filters are the following:
All Servers (default filter) Select this filter to view details of all master servers. Select this filter to view details of those master servers that are connected. Select this filter to view details of those master servers that are partially connected. Select this filter to view details of those master servers that appear as not connected. Select this filter to view details of Windows servers. Select this filter to view details of Solaris servers. Select this filter to view details of Linux servers. Select this filter to view details of all other servers like AIX servers, HP-UX servers etc.
Connected Servers
Partially Connected Servers
Not Connected Servers
Windows Servers
Solaris Servers
Linux Servers
Other Servers
In addition to the built-in filters, you can create your own custom filters. See Using filters to customize your views on page 62. Use the following procedure to view details by type of master server.
378
To view details by type of master server
1 2
In the OpsCenter console, select Monitor > Hosts > Master Server. Select a filter from the drop-down list. Note that the drop-down list is located on top of the table.
Monitoring NetBackup media servers

This view shows details of media servers. The data that is shown in this view is based on the current View pane selection. See Controlling the scope of Monitor views on page 324. The table that appears in this view shows the following columns:
Name Master Server Name of the media server. Name of the master server that is associated with the media server.
You can perform the following tasks from this view:

View the details of a master server that is associated with a media server See Viewing the details of a master server that is associated with a media server on page 378.
Viewing the details of a master server that is associated with a media server
Use the following procedure to view the details of a master server that is associated with a media server. To view the details of a master server that is associated with a media server
1 2
In the OpsCenter console, select Monitor > Hosts > Media Servers. Click the drilldown link from the Master Server column.
Monitoring NetBackup clients

This view shows details of NetBackup clients. The data that is shown in this view is based on the current View pane selection. See Controlling the scope of Monitor views on page 324. The table that appears in this view shows the following columns:
Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup alerts
379
Client Name Master Server
Name of the client that is to be backed up. Name of the master server that is associated with the client. Operating system on the client like Linux, HP-UX etc. Hardware of the client machine like PC.
OS Type
Hardware
You can perform the following task from this view:

View the details for a single master server See Viewing the details for a single master server on page 379.
Viewing the details for a single master server

All the details for a master server that is associated with a client can be viewed from the General tab. To view the details for a single master server
1 2
In the OpsCenter console, select Monitor > Hosts > Client. Click the drilldown link in the Master Server column.
Monitoring NetBackup alerts

The Monitor > Alerts view provides details of NetBackup alerts. The data that is shown 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 last 48 hours or 72 hours. See Controlling the scope of Monitor views on page 324. Note: The OpsCenter console displays active alerts by default (these are the alerts that have not been cleared). You can use the following views to see NetBackup alert information:
380
List View
The List View is shown by default when you select Monitor > Alerts. The List View shows active alerts by default. This view also lets you view detailed information about all NetBackup alerts and also filter, respond to alerts. See Using the List View for monitoring NetBackup alerts on page 380.
Summary View
The Summary View only displays active alerts (these are the alerts that have not been cleared). The Summary View shows how active alerts are distributed in your environment as per the alert severity. This information is shown in a pie chart as well as a table. See Using the Summary View for monitoring NetBackup alerts on page 386.
Using the List View for monitoring NetBackup alerts

The List view is displayed when you select Monitor > Alerts. This view contains detailed 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 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 last 48 hours or 72 hours. See Controlling the scope of Monitor views on page 324. Note: The List View displays active alerts by default (these are the alerts that have not been cleared). The table that appears in this view shows the following information:
Alert ID Unique ID associated with each NetBackup alert. The severity of the alert. The severity type helps you determine how quickly you want to respond. Name of the policy that is associated with the alert.
Severity
Alert Policy
381
Alert Condition Status
The alert condition that is used for the alert. Current status of the alert like Active, Cleared etc. Name of the individual to whom the alert has been assigned. Time, date, and year when the alert was raised. Time, date, and year when the alert was modified. Name of the individual who last modified the alert.
Assigned To
Time Raised
Last Update Time
Updated by
Not all of the available columns appear initially in this view. The Assignment State column does not appear, but can be added to your view by clicking the Table Settings icon. More information about how to customize tables and view specific columns is available. See About using tables on page 58. The following tasks can be performed from this view:
View the details for a single alert See Viewing the details for a single alert on page 381. See Viewing the details of the alert policy associated with an alert on page 382. See Filtering by alert type on page 382. See Responding to alerts on page 383.
View the details of an alert policy that is associated with the alert Use filters to view specific alerts Respond to alerts
Viewing the details for a single alert

All the details that are associated with an alert can be viewed from the Details pane. The Details pane is located at the bottom of the view.
382
To view the details of a single alert
1 2
In the OpsCenter console, select Monitor > Alerts. Click a drill-down link from the Alert ID column. The alert details are shown under General and Comments tabs of the Details pane. In addition to the information that is shown in the table, the General tab also shows master server, policy name, job ID, and exit status information. The Comments tab shows comments on the alert (if any), the time these comments were given and the individual who last updated the alert.
Viewing the details of the alert policy associated with an alert

Use the following procedure to view the details of the alert policy that is associated with an alert. To view the details of alert policy associated with the alert
1 2
In the OpsCenter console, select Monitor > Alerts. Click the drill-down link from the Alert Policy column.
Filtering by alert type

Since the Monitor > Alerts view can include large numbers of alerts, a filter is available. 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 focus on only the specific alerts that interest you. For example, you can create and apply a filter that only displays the alerts that are acknowledged. You can filter using any of the following nine built-in alert filters. These filters are available from the drop-down list which is present on top of the alert details table.
Active (default filter) Select this filter to view Active alerts. This does not include the alerts that have been cleared. Select this filter to only view the alerts whose severity is Critical. Select this filter to only view the alerts whose severity is Major. Select this filter to only view the alerts whose severity is Warning. Select this filter to only view the alerts whose severity is Informational.
Critical
Major
Warning
Informational
383
Unassigned
Select this filter to only view the alerts that have not been assigned to anybody. Select this filter to only view the alerts that have been assigned to other OpsCenter users. Select this filter to only view the alerts that have been acknowledged by an OpsCenter user. Select this filter to only view the alerts that have been cleared. More information on cleared alerts is available. See Responding to alerts on page 383.
Assigned
Acknowledged
Cleared
All Alerts
Select this filter to view the details of all alerts. This includes both active and cleared alerts.
In addition to the built-in filters, you can create your own custom filters. See Using filters to customize your views on page 62. Use the following procedure to view details by type of alerts. To view details by type of alert
1 2
In the OpsCenter console, select Monitor > Alerts. Select a filter using the Filter drop-down list. For example, select All Alerts to view details of both active and cleared alerts.
Responding to alerts
You can manage OpsCenter alerts from the Monitor > Alerts view by adding comments or by assigning the alert to an individual for further review. You can also clear or acknowledge an alert. OpsCenter allows multiple users to process or take action on an alert. When you acknowledge an alert, you inform other users who see the alert that action on the alert occurred. If you clear an alert, you cannot perform any further activity on the alert (for example, assign or acknowledge). Cleared alerts do not appear in the alert view by default. Note: Under certain circumstances there may be issues among multiple OpsCenter users. For instance, an OpsCenter user comments on an alert while another OpsCenter user tries to clear the same alert.
384
The OpsCenter console displays active alerts by default (these are the alerts that have not been cleared). Some alerts (for example, Drive is Down) are cleared automatically when the condition is resolved. You can view cleared alerts from Monitor > Alerts view (List View) by using the Cleared or All Alerts filter. See Filtering by alert type on page 382. 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 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
385
Note: You can also purge NetBackup alert data from Settings > Configuration > Data Purge 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 OpsCenter performance degrade when there is a high number of alerts in the OpsCenter database. See Configuring data purge settings on page 227. To acknowledge an alert
1 2 3
In the OpsCenter console, select Monitor > Alerts. Select an alert from the table. Click Acknowledge or Clear.
To add a comment for an alert
1 2 3
In the OpsCenter console, select Monitor > Alerts. Select an alert from the table. Click Add Comment. You can add a comment as a reminder to yourself or for other users.
To clear an alert
1 2 3
In the OpsCenter console, select Monitor > Alerts. Select an alert from the table. Click More and then select Clear from the drop-down list.
To assign an alert to an individual
1 2 3
In the OpsCenter console, select Monitor > Alerts. Select an alert from the table. Click Assign. You can assign an alert to a user for their action or information.
4 5
Select a user to whom you want to assign the alert. Click OK.
To change the policy that is associated with an alert
1 2
In the OpsCenter console, select Monitor > Alerts. Select an alert from the table. The Alert Policy Wizard is also used to create a policy.
Click More and then select Edit Policy from the drop-down list.
386
See Understanding alert counts in the Monitor view on page 406.
Using the Summary View for monitoring NetBackup alerts

The Summary View gives an overall summary of alerts by severity. It contains the Alert Summary by Severity section which shows an overall distribution of alerts by severity for the current View pane and timeframe selection. This information is shown in a pie chart as well as a table. Data for the last 24 hours is 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 324. A pie chart with different colors represents the alert distribution by severity in this section. Each color of the pie chart represents how alerts are distributed in your environment as per the alert severity. You can also view the color code summary in this section to know the colors that represent different severity. Note: The Summary View only displays active alerts (these are the alerts that have not been cleared). Pointing on the pie chart gives the number and percentage of alerts with a particular severity in your NetBackup environment. For example, pointing on the green 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
1 2 3
In the OpsCenter console, select Monitor > Alerts. Select Summary View from the drop-down list. The drop-down list is located at the top-right corner of the page. In the Alert Summary by Severity section, do either of the following:
Click the number of alerts (link) for a particular alert severity from the table. 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 particular alert severity. For example, click on the red section of the pie chart to view details for critical alerts.
387
See Understanding alert counts in the Monitor view on page 406.
388
Chapter
Managing NetBackup using Symantec OpsCenter


About the Manage views Controlling the scope of Manage views Managing alert policies Managing NetBackup storage Managing NetBackup devices
About the Manage views

From the Manage tab and associated subtabs, you can view and manage your NetBackup environment, which also include OpsCenter alert policies, storage, and devices. The OpsCenter server collects data from NetBackup master servers, stores it in a database, and displays it on demand. Most of the data is sent by NetBackup and appears almost instantaneously after it changes. (Network, system delays, or browser refresh settings can affect how quickly it appears). This data is collected mainly using notifications. For most operations and changes in NetBackup, NBSL sends a notification to OpsCenter. See How OpsCenter collects data from NetBackup on page 271.
390
Managing NetBackup using Symantec OpsCenter Controlling the scope of Manage views
Controlling the scope of Manage views

The content that is shown in the Manage views is based on your current View pane selection. You can select the following default option from the View pane:
ALL MASTER SERVERS Select ALL MASTER SERVERS to view information for all the NetBackup servers in your environment.
In addition to using the default view i.e. ALL MASTER SERVERS, you can also create your own views from Settings > Views or by using Java View Builder. For example, you can create a view like Geography to view details about master servers in a particular region like Europe. More information about how to create views using Settings > Views is available. See About OpsCenter views on page 307. See the online Symantec OpsCenter Java View Builder Help to know how you can create views using Java View Builder. Use the following procedure to view details of all master servers or specific master servers. To view details of all master servers
In the OpsCenter console, select ALL MASTER SERVERS from the drop-down list in the View pane.
To view details of specific master servers
1 2
In the OpsCenter console, select ALL MASTER SERVERS from the drop-down list in the View pane. Deselect the checkbox next to ALL MASTER SERVERS and select specific master servers from the list of master servers. Ensure that other master servers are unchecked. Click Apply Selection.
Managing alert policies

This view is displayed when you select Manage > Alert Policies. This view displays detailed information for OpsCenter alert policies for the current View pane selection. See Controlling the scope of Manage views on page 390.
Managing NetBackup using Symantec OpsCenter Managing alert policies
391
The table that appears in this view shows the following columns by default:
Name This column lists the name of the alert policy. Click the link to view details about the policy. This column lists the description for the alert policy. This column lists the alert condition that is used for the alert policy. Example: Hung Job, Job Finalized, High Frozen Media etc. See About alert conditions on page 394. Enabled This column determines whether the alert policy is enabled or not. This column lists the severity that is associated with the alert policy. This column lists the severity of the email or trap that is sent when the alert is cleared. This column lists the date and time when the alert policy was created. This column lists the date and time when the alert policy was last modified. This column lists the OpsCenter user who last modified the alert policy.
Description
Alert Condition
Severity
Clear Severity
Creation Time
Modification Time
Modified By
Table 8-1 lists the topics that describe how to manage alert policies. Table 8-1 Topic
See About OpsCenter alert policies on page 392. See Viewing the details for a single alert policy on page 393. See Filtering on type of alert policy on page 393.
Topic contents and description Description

Explains the concept of alert policies. Also explains the License Capacity alert policy. Explains how to view the details for an alert policy. Explains how to filter and view the alert policies that are of interest to you.
See Creating (or changing) an alert policy Explains how to create an alert policy using on page 394. the Alert Policy Wizard.
392
Table 8-1 Topic
Topic contents and description (continued) Description
See Managing an alert policy on page 407. Explains the tasks that are available for managing a single alert policy. This includes tasks like editing, copying, deleting, activating, or deactivating an alert policy. See Viewing the alerts associated with an alert policy on page 407. Explains how you can view the alerts that are associated with an alert policy.
About OpsCenter alert policies

OpsCenter provides tools to create and manage alert policies and handle any resulting alerts that the policies generate. Alert policies help you manage your NetBackup environment by providing constant monitoring of your NetBackup systems. When certain events or conditions occur in your environment, OpsCenter helps you manage your NetBackup server network by generating alerts or sending email 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 configured in the policy. The OpsCenter console displays views to help you track and manage these alerts.
You can specify email or SNMP notification in response to an alert, which lets administrators focus on other job responsibilities. Administrators do not need to monitor a terminal continuously. Alert policies are defined as informational, warning, major, or critical. Under certain circumstances there may be issues among multiple OpsCenter users. For instance, an OpsCenter user changes a policy while another user tries to remove the same policy.
About the License Capacity alert policy

OpsCenter contains an internal predefined alert policy that is called the License Capacity Alert. The License Capacity alert is generated for a capacity-based licensed NetBackup feature if the used capacity exceeds the licensed capacity. This alert is automatically cleared for the licensed feature if the used capacity is less than licensed capacity. If an alert is generated for a licensed feature and the alert has not been cleared for 7 days (i.e. the used capacity is more than the licensed capacity
393
for seven days after the alert is generated), a new alert is generated and the old alert is cleared automatically. The License Capacity alert is an informational alert. It is internal to OpsCenter and cannot be modified. However, you can disable (or enable) the License Capacity alert policy if you do not want to receive these alerts. See Managing an alert policy on page 407. Note: The License Capacity alert is not generated for the capacity-based licenses for OpenStorage Disk option, PureDisk Storage option, and Virtual Tape option. All capacity values for this alert are calculated based on the definition that 1 terabyte=1,099,511,627,776 bytes.
Viewing the details for a single alert policy

All the details that are associated with an alert policy can be viewed from the bottom of the Manage > Alert Policies view under the General tab. The General tab displays all the details that are shown in the table. To view the details of a single alert
1 2
In the OpsCenter console, select Manage > Alert Policies. Click a drill-down link from the Name column. The alert policy details are shown at the bottom of this view under the General tab.
Filtering on type of alert policy

A filter is available in the Manage > Alert Policies view to limit the types of alert policies that appear. You can filter using any of the following three built-in filters. These filters are available from the drop-down list which is present on top of the table.
All Alert Policies Enabled Alert Policies Select this filter to view all alert policies. Select this filter to view the alert policies that are enabled. Select this filter to view the alert policies that are disabled.
Disabled Alert Policies
You can also create your own filters which let you focus on only the specific alert policies that interest you. See Using filters to customize your views on page 62.
394
To view details by type of alert policy
1 2
In the OpsCenter console, select Manage > Alert Policies. Select a filter from the drop-down list. Note that the drop-down list is located on top of the table.
Creating (or changing) an alert policy

You can create alert policies to detect when something goes wrong with NetBackup and troubleshoot it. You can create policies to automate responses to key events in your enterprise. For example, you can create a policy to alert you when a job fails on a specific master server. You can monitor for frozen media and email the operator when the number of frozen media exceeds a threshold value. You can then take corrective action. OpsCenter periodically retrieves data from NetBackup based on notifications and a wait time (of up to 15 minutes). This time delay between the NetBackup Activity Monitor and the OpsCenter console can mean that many intermediate job states may be lost.
About alert conditions

OpsCenter comes with a set of predefined alert conditions. You can create alert policies based on these alert conditions to detect when something goes wrong in your NetBackup environment and troubleshoot NetBackup. The alerts help you to anticipate and handle problems before they occur. You can receive these alerts by logging on to OpsCenter, and also by email or SNMP traps. You can specify email and SNMP recipients while creating an alert policy. Alert conditions can be divided into the following categories:
Event-based alert conditions For these alert conditions, OpsCenter retrieves data from NetBackup based on notifications from NBSL. For these alert conditions, OpsCenter retrieves data from NetBackup based on a wait time (of up to 15 minutes).
Periodic alert conditions
Table 8-2 lists the alert conditions, alert category, and descriptions.
395
Table 8-2 Alert Type

Job
Alert conditions in OpsCenter Alert Category Description
Alert condition
High job failure rate Hung job
Event-based An alert is generated when the job failure rate becomes more than the specified rate. Periodic
396
Alert conditions in OpsCenter (continued) Alert Category Description

An alert is generated when a job hangs (runs for more than the specified time) for a selected policy or a client for a specified period. The Hung Job condition is checked every 15 minutes. Depending upon when a job starts within a check cycle, an alert may not occur. For Hung Job alert, you can configure OpsCenter to ignore the time for which a job is in a queued state. While checking the Hung Job condition, OpsCenter considers the start time of a job by default. This also includes the time for which a job is in a queued state. A job may not always be in an active state after it starts. Due to unavailability of resources, a job may first be in a queued state before it becomes active. If you configure OpsCenter to ignore the queued time for a job, OpsCenter considers the time when a job becomes active while checking the Hung Job condition. Note that the active start time of the first attempt is considered. For example, suppose a policy is created with a job threshold of 25 minutes. A job starts 10 minutes after a first check cycle and ends 13 minutes 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 first check, was running less than the threshold during 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 the job has executed for 26 minutes (11 + 15 minutes).
Alert condition
Job finalized
Events-based
397

An alert is generated when a job of specified type, of the specified policy or client ended in the specified status.
Alert condition
Media
Frozen media
Events-based An alert is generated when any of the selected media is frozen.
Suspended media Events-based An alert is generated when any of the selected media is suspended. Exceeded max media mounts Media required for restore Events-based An alert is generated when a media exceeds the threshold number of mounts. Events-based An alert is generated when a restore operation requires media. The restore operation may require a specific media which contains the specific image to be restored. Periodic An alert is generated when the number of available media becomes less than the predefined threshold value. An alert is generated when the percentage of suspended media exceeds the predefined threshold value. An alert is generated when the percentage of frozen media exceeds the predefined threshold value.
Low available media
High suspended media
Periodic
High frozen media
Periodic
398

An alert is generated when space available for catalogs becomes less than the threshold value or size. For Catalog Space low condition, you can specify the threshold value for a particular policy in percentage, bytes, kilobytes (KB), megabytes (MB), gigabytes (GB), terabytes (TB) or petabytes (PB) and generate alerts. The generated alert can also show available catalog space using these units. An alert is generated when catalog backup does not take place for a predefined time period. This does not necessarily mean that if you do not receive this alert, the catalog backup was successful.
Alert condition
Catalog Catalog Space low Periodic
Catalog not Backed up
Periodic
Catalog Backup Disabled
Periodic
An alert is generated when all the catalog backup policies are disabled. If the policy has been defined for a server group, an alert is generated for every master server within the group that satisfies this criteria. The alert is not generated if no catalog backup policy exists for a master server.
Tape
Mount Request
Events-based An alert is generated on a media mount request. An alert is generated when no cleaning tapes are left.
No Cleaning Tape Periodic
Zero Cleaning Left
Events-based An alert is generated when a cleaning tape has zero cleaning left.
399

Disk.
Alert condition
Disk Pool Full
Events-based An alert is generated when a disk pool(s) reaches the high water mark. An alert policy based on Disk Pool Full condition generates an alert only when the used capacity of the disk pool reaches the high water mark. Events-based An alert is generated when the selected disk volume(s) is down. An alert is generated when a disk volume capacity is running below the threshold limit.
Disk Volume Down
Low Disk Volume Periodic Capacity Drive is Down
Events-based An alert is generated when a drive in a specified robot or media server in the selected server context goes down. An alert is generated when the percentage of down drives exceeds the predefined threshold value.
High Down Drives Periodic
400

Host
Alert conditions in OpsCenter (continued) Alert Category

Periodic
Alert condition
Agent Server Communication break
Description
An alert is generated when the communication between Agent and OpsCenter Server breaks. By default, this alert is automatically cleared when the communication is re-established.
Master Server Unreachable
Events-based An alert is generated when OpsCenter loses contact with the master server. This alert condition means that the connection between OpsCenter and the managed NetBackup master server is lost. It does not necessarily mean that NetBackup backups are not working.
Lost Contact with Events-based An alert is generated when OpsCenter loses Media Server contact with the media server. Service Stopped Events-based An alert is generated when the selected service stops on any of the selected servers in the selected view. Events-based An alert is generated when the Symantec ThreatCon level is equal to or more than the threshold level that you specify. To create the alert policy, select the Symantec ThreatCon alert condition and then specify the threshold ThreatCon rating. The Symantec ThreatCon alerts are cleared automatically when the ThreatCon level becomes less than the threshold level that you have specified. For example, if you have created an alert policy that alerts you when the Symantec ThreatCon level becomes 3, then the alert is cleared automatically once the ThreatCon level becomes 2 or less. Job Policy Change Events-based
Symantec ThreatCon
401

An alert is generated when a policy attribute for a job policy is changed. Multiple alerts are generated if multiple attributes are changed for a job policy See Additional information on Job Policy Change condition on page 401. If you select a particular job policy, only the selected job policy is monitored for change. If you do not select any job policy, all the job policies are monitored for changes.
Alert condition
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 name Checkpoint interval Effective date Compression Block level incrementals Snapshot method Master server Collect bmr info Fail on error Frozen image Number of copies Residence Schedules Storage unit Policy client type Checkpoint Backup network drives Encryption Offhost Snapshot arguments Client name Collect true image restore info Ext sec info Keyword phrase Off host backup Catalog Clients Volume pool
402
Jobs/Policy Cross mount points Allow multiple data streams Alternate client Individual file restore from raw Block increment Data mover type File list Max fragmentation size Pfi enabled Data classification name Policy active
Priority True image recovery Keyword phrase Data mover Status Backup copy Disaster recovery Follows nfs mounts Max jobs per policy Proxy client Share group
Adding an alert policy

Follow the screens of the Alert Policy Wizard to define an alert policy. The required information and the required number of screens vary depending on the alert condition you choose. For some alert conditions, you can skip the optional screens. Note: The Alert Policy Wizard is also used when you edit an alert policy. To add an alert policy
1 2
In the OpsCenter console, select Manage > Alert Policies. Click Add. The alert Policy Wizard appears.
403
Enter the following details in the Alert Policy Wizard :

Name Enter a name for the alert policy. The name must be unique. This is a required field. Description Alert Condition Enter a description for the alert policy. Select an alert condition from the list of alert conditions that are available. See About alert conditions on page 394.
Click Next to continue. You may click Cancel to exit the Wizard at any stage.
Specify attributes for the alert condition that you selected. The attributes differ for each alert condition. For many alert conditions (for example, for the Job Finalized condition), you may need to enter threshold attributes and other required or optional attributes. These attributes define and limit the alert. Click Next.
Select the view that should be verified for the alert condition. You can select a view and a node that contains a group of master servers and also specific objects. For example, you can select the default view ALL MASTER SERVERS to be checked for the alert condition. When you select a view like ALL MASTER SERVERS or a node that contains a group of master servers, all the master servers that are currently in the view or node are automatically selected. In addition, master servers that you may add later to this view or node will also be automatically selected and hence verified for the alert condition. You may also select only specific objects of a particular view or node to be checked for the alert condition. For example, you may select only a specific master server(s) under the default view ALL MASTER SERVERS to be checked for the alert condition. To select a specific master server, first deselect the view or node 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 view and then deselecting the specific master server. Consider a scenario where there are two objects server A and server B in a particular view like ALL MASTER SERVERS. In case, you have selected the ALL MASTER SERVERS view and then specifically deselected server B , and in addition if 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
404
selected view or node. This is because you have specifically deselected server B from the ALL MASTER SERVER view. When you specifically deselect a master server from a view, which is also part of another selected view, the deselection or exclusion is given a higher priority because of which the master server is not verified for the alert condition. For this reason, it is recommended that 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 views or nodes for specific alert conditions. For example, for the Job Finalized alert condition, you can select the view as well as the specific policies and clients that should be checked for the alert. You can view the applicable attributes like policy name, client name, media server 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 ThreatCon alert condition. This is because the Symantec ThreatCon alert condition does not depend on any views or master servers. You must select at least one object, node, or view from this page. Click Next to continue.
Optionally in the Email Recipients and Trap Recipients sections, you can select email or SNMP recipients (or both) to receive the alert notification. See Adding email recipients on page 405.
405
See Adding SNMP trap recipients on page 406. Note that if you create an alert policy and do not define any recipients, the alert is still displayed in the Monitor > Alerts view. In the Severity section, do the following:
Select a severity level from the Alert Severity drop-down list. (If this alert occurs, the alert is displayed in the Monitor > Alerts view.) Select an appropriate severity level from the Severity of email/trap sent for cleared alert drop-down list. With Severity of email/trap sent for cleared alert option, you can configure the severity for an email or trap that is sent when an alert is cleared. The default severity level is Informational. In OpsCenter, an alert is raised with the severity specified in the alert policy. Whenever this alert is cleared, an email or trap informing the user that the alert is cleared is sent with the same severity that is defined in the alert policy. This is the default behavior. For example, you may have created an alert policy for a Hung Job alert condition with a Critical severity. As a result, you receive Hung Job alert with Critical severity. When this Hung Job alert gets cleared, you receive an email or trap that informs you that the alert has been cleared. This email or trap also has a Critical severity. You can now configure the severity for this email or trap from Critical to some other severity like Informational while creating the alert policy. Note that you can configure the severity only for email or trap. The Activate Condition option is checked by default. This means that by default, the policy will be active once you create it. Deselect the Activate Condition option if you want to deactivate the policy. You can always activate or deactivate the policy later from the OpsCenter console. See Managing an alert policy on page 407.
7 8
Click Save to save the alert policy. Click Finish once the policy is successfully created.
Adding email recipients

While creating an alert policy using the Alert Policy Wizard, go to the Actions screen. On the Actions screen, click To, Cc, or Bcc from the Email Recipients section. In the Add Email Recipients dialog box, select the specific recipients from the Recipient Name column and click To, Cc, or Bcc based on your requirements. Click OK
406
Adding SNMP trap recipients

While creating an alert policy using the Alert Policy Wizard, go to the Actions screen. On the Actions screen, click To from the Trap Recipients section. In the Add Trap Recipients dialog box, select the specific recipients from the Recipient Name column and click To. Click OK
Understanding alert counts in the Monitor view

Alerts apply only to the object (master server) where the corresponding alert policy is created. When alerts are raised for that policy they are raised on the selected object. For example, a Frozen Media alert occurs when any of the selected media on the selected master server (object) are frozen. Consider a case where you 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 select the 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 to calculate the job failure rate. The alert does not apply to a single master server in 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 the servers in the selected group is more than a user-defined threshold. An alert is not generated for every master server that is a part of the group. Therefore, the alert 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 raised on the server since the server is the selected object. The alert can also be viewed if 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
407
Managing an alert policy

Use the following procedure to edit, delete, copy, activate, or deactivate an alert policy. 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 you can make changes to it. To edit an alert policy
1 2 3
In the OpsCenter console, select Manage > Alert Policies. Select an alert policy from the Name column in the table. Click Edit. The Alert Policy Wizard is used to create or edit a policy. See Adding an alert policy on page 402.
To delete an alert policy
1 2 3
In the OpsCenter console, select Manage > Alert Policies. Select an alert policy from the Name column in the table. Click Delete.
To copy an alert policy
1 2 3 4 5
In the OpsCenter console, select Manage > Alert Policies. Select an alert policy from the Name column in the table. Click More and then click Copy from the drop-down list. In the Copy Alert Policy dialog box, enter the new name for the alert policy. Click OK. The copy of the alert policy is available in the alert policy details table where you can make changes to it.
To enable or disable an alert policy
1 2 3
In the OpsCenter console, select Manage > Alert Policies. Select an alert policy from the Name column in the table. Click More and then click Enable or Disable from the drop-down list.
Viewing the alerts associated with an alert policy

Use the following procedure to view the alerts that are associated with an alert policy.
408
Managing NetBackup using Symantec OpsCenter Managing NetBackup storage
To view the alerts associated with an alert policy
1 2 3
In the OpsCenter console, select Manage > Alert Policies. Select an alert policy from the Name column in the table. Click More and then select View Alerts from the drop-down list.
Managing NetBackup storage

This view is displayed when you select Manage > Storage. Included in this view are subtabs for Storage Unit, Storage Unit Group, and Storage Lifecycle Policy. Using these subtabs you can view detailed information about NetBackup storage for the current View pane selection. See Controlling the scope of Manage views on page 390. Table 8-3 lists the topics on how to manage NetBackup storage. Table 8-3 Topic Topic contents and descriptions Description
See Managing Storage Units on page 408. Explains the capabilities that are available using the Manage > Storage > Storage Unit view. See Managing Storage Unit Groups on page 410. Explains the capabilities that are available using the Manage > Storage > Storage Unit Group view. Explains the capabilities that are available using the Manage > Storage > Storage Lifecycle Policy view.
See Managing storage lifecycle policy on page 411.
Managing Storage Units

This view is displayed when you select Manage > Storage > Storage Unit. This view 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 the View pane. See Controlling the scope of Manage views on page 390. The table that appears in this view shows the following columns by default:
409
Name
This column lists the name of the storage unit. Click the link to view details about the storage unit. This column specifies the type of robot (if any) that the storage unit contains. This column specifies a unique, logical identification number for the robotic library. This column lists the density of the storage unit. This column specifies whether the storage unit is available exclusively on demand. This happens only when a policy or schedule is explicitly configured to use this storage unit. . This column specifies the absolute path to a file system or a volume available for disk backups.
Robot Type
Robot Number
Density
On Demand
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 Host
410
Fragment Size Multiplexing Disk Type Time Last Selected Disk Pool Host List
See the online NetBackup Administration Console Help for a detailed description of these fields. More information about how to customize tables and view specific columns is available. See About using tables on page 58. The following task can be performed from this view:
View the details for a single storage unit See Viewing the details for a single storage unit on page 410.
Viewing the details for a single storage unit

Use the following procedure to view the details for a single storage unit. To view details for a single storage unit
1 2
In the OpsCenter console, select Manage > Storage > Storage Unit. 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 the General tab. This tab displays many of the available columns of the table.
Managing Storage Unit Groups

This 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 pane selection. The table contains one row for each storage unit group for the current selection in the View pane. See Controlling the scope of Manage views on page 390. The table that appears in this view shows the following columns by default:
411
Name
This column lists the name of the storage unit group. Click the link to view details about the storage unit group. This column specifies the order that storage units are selected when they are included in a group. . This column specifies the date and time when the storage unit group was last seen.
Storage Unit Selection
Last Seen Time
The following task can be performed from this view:

View the details for a single storage unit group See Viewing the details for a single storage unit group on page 411.
Viewing the details for a single storage unit group

Use 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 the following tabs:
General This tab shows the details of the storage unit group that are also shown in the table. This tab shows the details of the storage units that are a part of the storage unit group.
Storage Unit
To view details for a single storage unit group
1 2
In the OpsCenter console, select Manage > Storage > Storage Unit Group. Click the name of a storage unit group (drilldown link) from the Name column in the table.
Managing storage lifecycle policy

This view is displayed when you select Manage > Storage > Storage Lifecycle Policy. This view shows the storage lifecycle policy details for the current View pane selection. A storage lifecycle consists of one or more storage units. The table contains one row for each Storage lifecycle policy for the current selection in the View pane. See Controlling the scope of Manage views on page 390.
412
The table that appears in this view shows the following columns by default:
Name This column lists the name of the storage lifecycle policy. Click the link to view details about the storage lifecycle Policy. This column lists the data classification that has been selected for the storage lifecycle, which applies to all of the storage units in the lifecycle. For example, the data might be classified as gold or silver. This column specifies the priority that a policy has for backup resources. The default for all policies is 0, the lowest priority possible. Any policy with a priority greater than zero has priority over the default setting. . This column lists the master server that is associated with the storage lifecycle Policy. Click the link to view more details about the master server.
Data Classification
Job Priority
Master Server
The following tasks can be performed from this view:

View the details of a single storage lifecycle See Viewing the details for a single storage policy lifecycle policy on page 412. View the details of a master server that is associated with a storage lifecycle policy See Viewing the details for a master server associated with a storage lifecycle policy on page 413.
Viewing the details for a single storage lifecycle policy

Use 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:
General This tab shows the details of the storage unit group that are also shown in the table. This tab shows the details of the storage destinations that are a part of the storage lifecycle policy.
Storage Destinations
Managing NetBackup using Symantec OpsCenter Managing NetBackup devices
413
To view the details for a storage lifecycle policy
1 2
In the OpsCenter console, select Manage > Storage > Storage Lifecycle Policy. Click the name of a storage lifecycle policy (drilldown link) from the Name column in the table.
Viewing the details for a master server associated with a storage lifecycle policy
Use the following procedure to view the details for a master server that is associated with a storage lifecycle policy. The details are shown on a separate page. To view the details for a master server associated with a storage lifecycle Policy
1 2
In the OpsCenter console, select Manage > Storage > Storage Lifecycle Policy. Click the name of the master server (drilldown link) from the Master Server column in the table.
Managing NetBackup devices

Under certain circumstances there may be issues among multiple OpsCenter users managing devices. For instance, a user brings a drive down while another user tries to bring up the same drive. Table 8-4 lists the topics on how to manage NetBackup devices. Table 8-4 Topic
See Managing drives on page 414.
Topic contents and descriptions Description

Explains the capabilities that are available using the Manage > Devices > Drive view. Explains the capabilities that are available using the Manage > Devices > Robot view. Explains the capabilities that are available using the Manage > Devices > Disk Pool view. Explains the capabilities that are available using the Manage > Devices > SAN Client view.
See Managing robots on page 418.
See Managing disk pools on page 420.
See Managing SAN clients on page 422.
See Managing Fibre Transport (FT) servers Explains the capabilities that are available on page 423. using the Manage > Devices > FT Server view.
414
Managing drives
This view is displayed when you select Manage > Devices > Drive. This view shows details for the drives that are configured for use by NetBackup for the current View pane selection. See Controlling the scope of Manage views on page 390. The table that appears in this view shows the following columns by default:
Drive Name This column lists the configured name of the drive. Click the link to view details about the drive. This column lists the name of the device host (media server) where this drive is attached. If multiple drive paths are configured, this column contains Multiple. If the drive is configured as a shared drive (SSO), this column contains Multiple. This column lists the name of the master server that is associated with the drive. This column specifies the type of drive. Example: hcart2, hcart3, 4MM. Robot Type This column specifies the type of robot that contains this drive. Example: TL4, TLD. Enabled This column contains 'Yes' if the path is enabled. The column contains 'No' if the path is not enabled. If multiple drive paths are configured, this column contains 'Multiple'.
Device Host
Master Server
Drive Type

Serial Number Cleaning Frequency Shared Inquiry Information Volume Header Path ACS
415
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 Total Time User Name VM Host Write Enabled
See the online NetBackup Administration Console Help for a detailed description of these fields. More information about how to customize tables and view specific columns is available.
416
See About using tables on page 58. The following tasks can be performed from this view:
View the details for a single drive See Viewing the details for a single drive on page 416. See Viewing the details for a master server associated with a drive on page 416. See Filtering on NetBackup drive category on page 416. See Controlling drives on page 417.
View the details of a master server that is associated with a drive Use filters to view specific drives
Control drives
Viewing the details for a single drive

Use the following procedure to view the details of a single drive. To view the details for a single drive
1 2
In the OpsCenter console, select Manage > Devices > Drive. Click the name of the drive (drilldown link) from the Drive Name column in the table. Detailed properties and status for the drive are shown at the bottom of the view under the General tab. The Paths tab shows the paths that were configured for the drive.
Viewing the details for a master server associated with a drive

Use the following procedure to view the details of a master server that is associated with a drive. To view the details for a master server
1 2
In the OpsCenter console, select Manage > Devices > Drive. Click the name of the drive (drilldown link) from the Master Server column in the table. Details for the specific master server are shown on a separate page.
Filtering on NetBackup drive category

You can sort and filter this view to focus on the specific type of drives that you want to see. For example, you can apply a filter that displays only those drives that are up. You can filter by using any of the built-in filters. These filters are available from the drop-down list which is present on top of the table.
417
The following built-in filters are available:

All Drives All Drives is the default filter. Select this filter to view all drives. Select this filter to view only those drives that are up. For up drives, all drive paths are up. Select this filter to view only those drives that are down. For down drives, all drive paths are down. Select this filter to view mixed drives. For mixed drives, some drive paths are up and some drive paths are down.
Up Drives
Down Drives
Mixed Drives
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 62. To view details by type of drive
1 2
In the OpsCenter console, select Manage > Devices > Drive. Select a filter from the drop-down list. Note that the drop-down list is located on top of the table.
Controlling drives
Use the following procedure to control drives. Before you perform these tasks, manually refresh your Web browser to obtain an updated view of all drives. Note: These tasks are not visible if you log on with an Analyst or a Reporter role. To control drives
1 2 3
In the OpsCenter console, select Manage > Devices > Drive. Select a drive from the Drive Name column in the table (use the check box). Select Up Drive, Down Drive, or Reset Drive. The OpsCenter console may take some time to show the updated status once you perform these tasks.
418
Managing robots
This view is displayed when you select Manage > Devices > Robot. This view shows details for the robots that are configured for use by NetBackup for the current View pane selection. See Controlling the scope of Manage views on page 390. The table that appears in this view shows the following columns by default:
Robot Name This column contains the name of the robot. The robot name contains the type and number of the robot, for example TLD(3). Click the link to view details about the robot. Device Host This column lists the name of the device host where this robot is attached. This column contains the robot serial number. If the robot is controlled by a remote host, this column contains the name of the host that controls the robot. This column lists the master server that is associated with the robot. Click the link to view details about the master server. Media Server This column lists the media server that is associated with the robot. Click the link to view details about the media server.
Serial Number
Robot Control Host
Master Server

Robot Type Robot Number Inquiry Information Last Seen Time Max Drive Max Slot
419
Remote ID VM Host
See the online NetBackup Administration Console Help for a detailed description of these fields. More information about how to customize tables and view specific columns is available. See About using tables on page 58. The following tasks can be performed from this view:
View the details of a robot See Viewing the details for a single robot on page 419. See Viewing the details for a master server associated with a robot on page 419. See Viewing the details for a media server associated with a robot on page 420.
View the details for a master server that is associated with a robot View the details for a media server that is associated with a robot
Viewing the details for a single robot

Use the following procedure to view the details of a single robot. To view the details for a single robot
1 2
In the OpsCenter console, select Manage > Devices > Robot. Click the name of the robot (drilldown link) from the Robot Name column in the table. Detailed properties for the robot are shown at the bottom of the view under the General tab. The Paths tab shows the paths that were configured for the robot.
Viewing the details for a master server associated with a robot

Use the following procedure to view the details of a master server that is associated with a robot. To view the details for a master server associated with a robot
1 2
In the OpsCenter console, select Manage > Devices > Robot. Click the name of the master server (drilldown link) from the Master Server column in the table. Detailed properties for the master server are shown on a separate page.
420
Viewing the details for a media server associated with a robot

Use the following procedure to view the details of a media server that is associated with a robot. To view the details for a media server associated with a robot
1 2
In the OpsCenter console, select Manage > Devices > Robot. Click the name of the media server (drilldown link) from the Media Server column in the table. Detailed properties for the media server are shown on a separate page.
Managing disk pools

This view is displayed when you select Manage > Devices > Disk Pool. This view shows details for the disk pools that are configured for use by NetBackup in the current View pane selection. See Controlling the scope of Manage views on page 390. The table that appears in this view shows the following columns by default:
Name Server Type This column lists the name of the disk pool This column lists the storage server type. For OpenStorage, the server type depends on the vendor name. This column lists the number of disk volumes in the disk pool. This column lists the amount of storage space in use. This column lists the total raw, unformatted size of the storage in the disk pool. This column lists the estimated amount of disk space available for storage after file metadata overhead is taken into account. This column lists the low water mark for the disk pool. (The default is 80%.) When the capacity of the disk pool returns to the low water mark, NetBackup again assigns jobs to the storage unit.
Number of Volumes
Used Capacity
Raw Size
Usable Size
Low Watermark (%)
421

High Water Mark (%) Master Server State Imported
See the online NetBackup Administration Console Help for a detailed description of these fields. More information about how to customize tables and view specific columns is available. See About using tables on page 58. The following tasks can be performed from this view:
View the details for a disk pool See Viewing the details for a disk pool on page 421.
Viewing the details for a disk pool

Use the following procedure to view the details for a disk pool. The details for the disk pool are shown at the bottom of the Manage > Devices > Disk Pool view under the following tabs:
General This tab shows the detailed properties for a disk pool. Click the master server link to view details about the master server that is associated with the disk pool. This tab shows details about the disk volumes that are associated with the disk pool. This tab shows details about the storage servers that are associated with the disk pool.
Disk Volume
Storage Server
To view the details for a disk pool
1 2
In the OpsCenter console, select Manage > Devices > Disk Pool. Click the name of the disk pool (drilldown link) from the Name column in the table. The details are shown at the bottom of this view.
422
Managing SAN clients

This view is displayed when you select Manage > Devices > SAN Client. This view shows details for the SAN clients that are configured for use by NetBackup in the current View pane selection. See Controlling the scope of Manage views on page 390. The table that appears in this view shows the following columns by default:
Name State This column lists the name of the SAN client. This column lists the state of the FT device on the SAN client. The different states can be active, disabled etc. Usage Preference This column determines when to use the FT media server. This column lists the number of NetBackup media servers that support FT transport and that the client can send data to or receive data from. The number of minutes to wait for an FT media server for a backup operation. The number of minutes to wait for an FT media server for a restore operation. This column lists the master server that is associated with the SAN client.
No. of FT Media Servers
Backup Wait Period
Restore Wait Period
Master Server
The Version column does not appear, but can be added to your view by clicking the Table Settings icon. The following task can be performed from this view:
View the details of a SAN client See Viewing the details for a SAN client on page 423. See Viewing the details for a master server associated with a SAN client on page 423.
View the details of a master server that is associated with a SAN client
423
Viewing the details for a SAN client

Use the following procedure to view the details of a SAN client. The details for the SAN Client are shown at the bottom of Manage > Devices > SAN Client view under the following tabs:
General This tab shows detailed properties and status for the SAN client. Click the master server link to view details about the master server that is associated with the SAN client. This tab shows the FT target devices information for the selected SAN client.
FT device
To view the details for a SAN client
1 2
In the OpsCenter console, select Manage > Devices > SAN Client. Click the name of the SAN client (drilldown link) from the Name column in the table. The details are shown at the bottom of this view.
Viewing the details for a master server associated with a SAN client
Use the following procedure to view the details of a master server that is associated with a SAN client. To view the details for a master server associated with a SAN client
1 2
In the OpsCenter console, select Manage > Devices > SAN Client. Click the name of the master server (drilldown link) from the Master Server column in the table. Detailed properties for the master server are shown on a separate page.
Managing Fibre Transport (FT) servers

This view is displayed when you select Manage > Devices > FT Server. This view shows details for the FT media servers that are configured for use by NetBackup for the current View pane selection. See Controlling the scope of Manage views on page 390. The table that appears in this view shows the following columns by default:
424
Name
This column contains the name of the FT media server. Click the link to view details about the robot.
State
This column lists the state of the FT media server. This column lists the master server that is associated with the FT server. This column specifies the number of FT connections to allow to a media server.
Master Server
Max Allowed Connections
The following tasks can be performed from this view:

View the details of an FT server See Viewing the details for an FT server on page 424. See Viewing the details for a master server associated with an FT server on page 424.
View the details for a master server that is associated with an FT server
Viewing the details for an FT server

Use the following procedure to view the details for an FT server. The details for the FT server are shown at the bottom of Manage > Devices > FT Server view under the following tabs:
General This tab shows detailed properties and status for the FT server. This tab shows the FT target devices information for the selected FT server.
FT device
To view the details for an FT server
1 2
In the OpsCenter console, select Manage > Devices > FT Server. Click the name of the Fibre Transport server (drilldown link) from the Name column in the table. The details are shown at the bottom of this view.
Viewing the details for a master server associated with an FT server

Use the following procedure to view the details of a master server that is associated with an FT server.
425
To view the details for a master server associated with an FT server
1 2
In the OpsCenter console, select Manage > Devices > FT Server. Click the name of the master server (drilldown link) from the Master Server column in the table. Detailed properties for the master server are shown on a separate page.
426
Chapter
Using 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 Recovery

The use of the OpsCenter Web-based user interface to guide a user through the Oracle cloning operation offers several benefits:
The process is more automated, making the operation easier to perform.
428
Using Guided Recovery Setting up for cloning
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 cloning operation. You do not need access to the original database to perform the cloning operation.
Setting up for cloning

The following items must be done before you perform a Guided Recovery cloning operation:
Oracle uses metadata cataloging, which enables database information to appear in the OpsCenter interface. Ensure that the Oracle metadata parameter in the client'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 appear in the OpsCenter interface. Use the bpsetconfig command (install_path\NetBackup\bin\admincmd\bpsetconfig) on the server to set a client's configuration. For example:
# bpsetconfig -h myoracleclient ORACLE_METADATA=YES
Set up all destination file paths before you run the cloning operation, because the operation does not create new file paths during the process. Ensure that the user has write access to these paths.
Pre-operation checks
Check the following items before you begin the cloning process:
Ensure that the source and destination systems and the source and destination databases are compatible. Examples are Solaris 9 to Solaris 10 and Oracle 11 to Oracle 11. The cloning operation does not support offline tablespaces or raw tablespaces.
Using Guided Recovery Performing a cloning operation
429
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 change what 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 the source database. More information is available for the 'BKUP_IMAGE_PERM' variable. If the destination client is different than the source client, perform an alternate restore procedure. If the NetBackup client service runs as the Oracle user, then that user needs to 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 exclusive mode appears. If the cloning user shares an existing Oracle home, the user must have write access to some directories such as DBS.
Performing a cloning operation

You need to log onto OpsCenter, to perform a cloning operation. OpsCenter is the Web GUI that you use to perform all guided recovery operations. To perform a cloning operation on an Oracle database in OpsCenter
1 2
When you log onto OpsCenter, the first screen that appears is the Monitor Overview screen. Along the top of the screen, click Manage > Oracle Cloning. On the Select Master Server screen, use the drop-down menu to select the master server that you want to work with, then click Go. See Select Master Server screen on page 431.
The Select Source Database screen lets you filter the list of databases by database name, host name, database version, platform, and date. The default condition is to display all databases that are backed up in the default date range. Click Show Databases. More information is available on this screen. See Select Source Database screen on page 431.
430
Using Guided Recovery Performing a cloning operation
The databases appear under the filtering part of the same screen. Select the database on which you want to perform a cloning operation by clicking option at the left side of the desired database entry. Then click Next>. The Select Control File Backup screen shows a timeline view of the control file backups. Select the icon for the desired control file backup from the timeline 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 display all versions of the backup for that time periods. Additional information is available to verify that you have selected the correct control file. The lower left corner of the screen lists three links. More information is available about these links. See Select Control File Backup screen on page 431. Click on the icon of the control file backup you want to restore for the clone of the selected database. The default is the latest backup selected. Then click Next>.
The Destination Host and Login screen contains parameters for the destination of the clone to be created. Enter the destination host name in the text box that is provided or click Browse and select from a list of available hosts. 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 432. For operating system authentication, enter a user name, password (Windows), and domain (Windows). Then click Next>.
The Define Destination Parameters screen appears. The five tabs on this screen are used to change database attributes, the destination paths of control files, data files, and redo logs, and restore options. After you have changed the destination parameters, click Next>. See Destination Parameters screen on page 433.
Using Guided Recovery Select Master Server screen
431
The SelectionSummary screen lets you scan the information you have entered on the previous screens. Links to the recovery sets and destination database attributes let you view and verify any changes you have made. When you are satisfied with the summary information, click Next>. See Selection summary screen on page 433.
The Pre-clone Check screen lets you validate the database attributes and the file paths. To validate, click the underlined word here. If a directory path does not already exist, the validation check flags the error. If a file already exists, the validation check also flags the error, so that the cloning operation does not overwrite the file. See Pre-clone check screen on page 434. When you are ready to launch the cloning operation, click Launch Cloning Process. A display appears that is similar to the NetBackup Activity Monitor.
Select Master Server screen

From the pulldown menu, select the NetBackup master server that collected the backup information to be used for the cloning operation.
Select Source Database screen

When the Select Source Database screen first appears, the lowest portion of the screen shows a list of the latest backups for all the databases that the master server 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, host name, database version, and date range. Multiple filter parameters can be used at the same time. For example, to show only the Solaris databases that are backed up between 11/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 to display the new filtered list of databases.
Select Control File Backup screen

The Select Control File Backup screen is a timeline view of all the control files that are backed up for the selected database. The timeline displays an icon for each control file that is associated with the backed up database. When you first enter this screen, the latest backup control file is already selected .
432
Using Guided Recovery Destination host and login screen
Hover over the icon on the timeline to display a popup that shows information about 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 instances of control files, you may need to increase the scope of the timeline. You can display the timeline in days, weeks, months, or years. If multiple control files were backed up during a single timeline unit, a different icon appears representing more than one control file (for example, if the database was backed up twice in an hour). To select from among these files, hover over the icon. A popup lists each control file in table format. It shows several items including the backup name and the type of 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 you have selected the proper control file.
View Database Schema shows the schema of the selected control file. It shows how 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 the restore process. It also shows the backup and image information that is displayed for each data file. The data file recovery set is generated only for the files that are backed up as part of an incremental strategy. Even though files that are backed up as part of a full backup do not appear in this list, the clone 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 be used to recover the database to the latest point in time of that control file. This set is generated only for the files that are backed up as part of an incremental strategy. Even though files that are backed up as part of a full backup do not appear in this list, the clone still completes successfully.
Destination host and login screen

The Select Destination Parameters screen lets you enter the destination host and the 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 user name. 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.
Using Guided Recovery Destination Parameters screen
433
Destination Parameters screen

Guided Recovery uses many values from the source database as default values for the destination database. You can modify these values if not appropriate for the destination database. The Destination Parameters screen contains the following tabs:
Database Attributes. This pane appears when you first enter the Database Attributes screen. Each attribute name has identical source and destination attributes. You can change the destination attribute of the instance name, database name, and database home. Note that the instance name is case sensitive while the database name is not case sensitive. Control File Paths. This pane displays the source path and the destination path for each control file. You can change a control file destination path by clicking in the associated text window and entering the new path. You can also click Browse to navigate to the desired path. When you change a path, a highlight bar appears around the text window as a visual indicator that this path has changed. Data File Paths. This pane lets you change the destination path for one or more data files. Enter the path in the text window provided, then select the data files on which to apply it, and press the Apply option. Redo Log Paths. This pane displays the source path and the destination path for all redo logs. You can type in a new destination path or click Browse to navigate to the desired path. When you change a path, a highlight bar appears around the text window as a visual indicator that this path has changed. Restore Options. This pane displays restore options. The option that is displayed on this pane is Number of parallel streams for restore and recover.
When you are done making changes on this screen, click Next>. All the information from the previous screen is saved in preparation for the cloning operation. All the changes that are made in this screen are temporary and are active only for the cloning session.
Selection summary screen

The following information appears on this screen:

The selected master server and the source database attributes. The date and time of the selected control file backup, and the backup media type. The database recovery set and the archived log recovery set.
434
Using Guided Recovery Pre-clone check screen
The destination database attributes selected in the previous screen and the database initialization parameters to be used for the cloning operation.
Pre-clone check screen

The Pre-clone Check screen lets you validate the database attributes and the file paths. To validate, click the underlined word here. If a file path does not already exist, the validation check flags the error. If a file already exists, the validation check also flags the error, so that the cloning operation does not overwrite the file. You can also specify an email address, so when the cloning process completes, an email is sent to you that gives you the status of the cloning operation along with other pertinent information.
Job Details screen

The Job Details screen is intended to reflect the NetBackup Activity Monitor. More information is available on the Activity Monitor. See the NetBackup Administrator's Guide, Volume I.
Post-clone operations
Perform the following after the cloning operation has completed:
On UNIX systems, update the oratab file with the appropriate instance information. 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 with the 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. dbca sometimes removes directories, so verify before retrying the operation.
Troubleshooting Guided Recovery

Guided Recovery operations are in addition to the normal NetBackup for Oracle operations. If problems are encountered, all previously used troubleshooting steps
Using Guided Recovery Troubleshooting Guided Recovery
435
and evidence are also relevant. The following sections detail the additional key information that is required to troubleshoot Guided Recovery when it fails. On UNIX and Linux systems, gather all legacy logs at VERBOSE=5. On Windows systems, gather them at General=2, Verbose=5, and Database=5. All unified logs should be gathered at DebugLevel=6 and DiagnosticlLevel=6.
Troubleshooting files for metadata collection operations at the time of the backup
From the Oracle client host:

netbackup/logs/bphdb legacy logs netbackup/logs/dbclient legacy logs (The directory must be writable by the Oracle 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 operations


netbackup/logs/vnetd legacy logs ncf unified logs, OID 309, New Client Framework ncfnbcs unified logs, OID 366, New Client Framework NetBackup Client Services
From the NetBackup master server:

netbackup/logs/vnetd legacy logs nbars unified logs, OID 362, NetBackup Agent Request Service dars unified logs, OID 363, Database Agent Request Service
netbackup/logs/bprd legacy logs
436
Using Guided Recovery Troubleshooting Guided Recovery
nbars unified logs, OID 362, NetBackup Agent Request Service dars unified logs, OID 363, Database Agent Request Service
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 operations

netbackup/logs/bphdb legacy logs (Includes the obk_stdout and obk_stderr logs.) netbackup/logs/bpdbsbora legacy logs netbackup/logs/dbclient legacy logs (The directory must be writable by the Oracle users.) A tar of netbackup/logs/user_ops (UNIX/Linux) A compress of NetBackup\Logs\user_ops (Windows)

netbackup/logs/vnetd legacy logs netbackup/logs/bprd legacy logs nbars unified logs, OID 362, NetBackup Agent Request Service dars unified logs, OID 363, Database Agent Request Service
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)
Chapter
10
Understanding OpsCenter alert policies and alerts


About managing OpsCenter alerts in Microsoft Operations Manager 2005 About managing OpsCenter alerts using Microsoft System Center Operations Manager 2007 About managing OpsCenter alerts using HP OpenView Network Node Manager 7.50/7.51 on Windows About using SNMP with OpsCenter
About managing OpsCenter alerts in Microsoft Operations Manager 2005

You can deploy and configure the MOM management pack for NetBackup into your existing MOM environment. Microsoft Operations Manager management pack for NetBackup lets you receive the SNMP trap alerts that have been configured in OpsCenter using Microsoft Operations Manager 2005. By detecting and alerting you on critical conditions, this Management Pack helps prevent possible service outages. The MOM Management Pack for NetBackup and the documentation is available for download on the Symantec Support Web site. http://seer.entsupport.symantec.com/docs/295691 Note: The term MOM refers specifically to MOM 2005.
438
Understanding OpsCenter alert policies and alerts About managing OpsCenter alerts using Microsoft System Center Operations Manager 2007
About managing OpsCenter alerts using Microsoft System Center Operations Manager 2007
Microsoft System Center Operations Manager 2007 (SCOM), formerly Microsoft Operations Manager (MOM), is a next-generation performance and event-monitoring product from Microsoft. Microsoft System Center Operations Manager Management Pack for NetBackup lets you monitor and manage NetBackup alerts using Microsoft System Center Operations Manager 2007 (SCOM 2007). By detecting and alerting you on critical conditions, this Management Pack helps prevent possible service outages. The SCOM Management Pack for NetBackup and the documentation is available for download on the Symantec Support Web site. http://seer.entsupport.symantec.com/docs/305573
About managing OpsCenter alerts using HP OpenView Network Node Manager 7.50/7.51 on Windows
You can monitor and manage NetBackup alerts using HP OpenView Network Node Manager 7.50 or 7.51 on Windows. By detecting and alerting you on critical conditions, HP OpenView Network Node Manager (NNM) can help you to prevent possible service outages. You can download and use the cc_trapd.conf file to monitor and manage NetBackup alerts using HP OpenView Network Node Manager 7.50 or 7.51. Currently, NetBackup Operations Manager (OpsCenter), a management solution that is shipped with NetBackup, can generate and monitor NetBackup alerts. By using cc_trapd.conf file and configuring NNM and OpsCenter, NNM can receive the SNMP traps that have been configured in OpsCenter. As a result, NNM can be used for the centralized management of NetBackup alerts. Note: The term HP OpenView Network Node Manager (NNM) in this section refers specifically to HP OpenView Network Node Manager 7.50 or 7.51.
cc_trapd.conf file and the documentation is available for download on the support
site. http://seer.entsupport.symantec.com/docs/295154 More information about OpsCenter alerts is available. See About alert conditions on page 394.
Understanding OpsCenter alert policies and alerts About using SNMP with OpsCenter
439
About using SNMP with OpsCenter

This section provides information about SNMP and how OpsCenter uses SNMP.
About SNMP
The Simple Network Management Protocol (SNMP) is an application layer protocol that facilitates the exchange of management information between network devices. It is part of the Transmission Control Protocol/Internet Protocol (TCP/IP) protocol suite. 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 network protocol. The manager provides the interface between the human network manager and the management system. The agent provides the interface between the manager and the physical devices being managed. The manager and agent use a Management Information Base (MIB) and a relatively small set of commands to exchange information. The MIB is organized in a tree structure with individual variables, such as point status or description, being represented as leaves on the branches. A numeric tag or object identifier (OID) is used to distinguish each variable uniquely in the MIB and in SNMP messages.
About SNMP versions

Many versions of SNMP are available. The versions of SNMP protocol are as follows:
SNMPv1 The SNMPv1 version is the first version of the protocol. and is defined by RFC 1157. This document replaces the earlier versions that were published as RFC 1067 and RFC 1098. Security is based on community strings. SNMPv2 It was created as an update of SNMPv1 adding several features. The key enhancements to SNMPv2 are focused on the SMI, manager-to-manager capability, and protocol operations. SNMPv2c combines the Community-based approach of SNMPv1 with the protocol operation of SNMPv2 and omits all SNMPv2 security features.

The original SNMPv2 (SNMPv2p) Community-based SNMPv2 (SNMPv2c)
440
User-based SNMPv2 (SNMPv2u) SNMPv2 star (SNMPv2*).
SNMPv3 This version of the protocol is a combination of user-based security and the protocol operations and data types from SNMPv2p, and support for proxies. The security is based on that found in SNMPv2u and SNMPv2*. RFC 1905, RFC 1906, RFC 2261, RFC 2262, RFC 2263, RFC 2264, and RFC 2265 define this protocol.
About SNMP versions supported in OpsCenter

OpsCenter supports the following SNMP versions:

SNMPv1 SNMPv2c SNMPv3
About the Management Information Base (MIB) and OpsCenter support

Each SNMP element manages specific objects with each object having specific characteristics. Each object and characteristic has a unique object identifier (OID) that is associated with it. Each OID consists of the numbers that are separated by decimal 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 and various other parameters that are related to the object. The MIB then serves as a data dictionary that is used to assemble and interpret SNMP messages.
About SNMP traps

This section explains the content of an SNMP trap that is sent from Symantec OpsCenter. Each OpsCenter trap contains 2 standard object identifiers and 12 OpsCenter-specific object identifiers. An object identifier (or OID) is a numeric string that is used to uniquely identify an object. The following table shows the contents of a trap that is sent from OpsCenter. A total of 14 bindings (or 14 name-value pairs) are present in each trap that is sent from OpsCenter. Each binding associates a particular Management Information Base (MIB) object instance with its current value. Table 10-1 shows the name-value pairs that the traps pass to the SNMP manager.
441
Table 10-1 Name

1.3.6.1.2.1.1.3.0
OpsCenter trap binding Value

This field is the time (in hundredths of a second) between when OpsCenter server service starts and the OpsCenter trap is sent. See Request for Comment (RFC) 1905 and 2576 for a detailed definition. Example: 1173792454
1.3.6.1.6.3.1.1.4.1.0
This field is the unique identifier for this trap. See RFC 1905 and RFC 2576 for a detailed definition. Example: 1.3.6.1.4.1.1302.3.12.10.2.0.4
1.3.6.1.4.1.1302.3.12.10.1.1
This field is the alert recipient name.
(iso.org.dod.internet.private.enterprises.p Example: Nancy Nieters roducts.veritascc. ccTrapDefinitionsBranch.ccTrapVarsBran ch.alertRecipients) 1.3.6.1.4.1.1302.3.12.10.1.2 This value specifies the alert ID, alert status, and alert summary in the (iso.org.dod.internet.private.enterprises.p following format: roducts.veritascc.ccTrapDefinitionsBranc Alert ID (Alert Status) Alert Summary h.ccTrapVarsBranch.alertSummary) Example: 100 (Active) Job Completed with Exit Status 0 1.3.6.1.4.1.1302.3.12.10.1.3 (iso.org.dod.internet.private.enterprises.p roducts.veritascc. ccTrapDefinitionsBranch.ccTrapVarsBran ch.alertDescription) This field is the alert description. Example: Alert Raised on: Tue Mar 13 18:57:33 IST 2007 Job: {DAFB3333-B3ED-46F0-974A-948DC68967 70};1336 master server : d-c02904a(d-c02904a) NBU Policy: pol86 Exit Status: 0 Client: d-c02904a New State: Done Alert Policy: JobFinalizedWithExitStatusZero OpsCenter Server: cn-sol5
442
Table 10-1 Name
OpsCenter trap binding (continued) Value

This field is blank and not used.
1.3.6.1.4.1.1302.3.12.10.1.4 (iso.org.dod.internet.private.enterprises.p roducts.veritascc. ccTrapDefinitionsBranch.ccTrapVarsBran ch.policyName) 1.3.6.1.4.1.1302.3.12.10.1.5 (iso.org.dod.internet.private.enterprises.v eritas.products.veritascc.ccTrapDefinition sBranch.ccTrapVarsBranch.objectType) 1.3.6.1.4.1.1302.3.12.10.1.6 (iso.org.dod.internet.private.enterprises.v eritas.products.veritascc.ccTrapDefinition sBranch.ccTrapVarsBranch.collectorNam e) 1.3.6.1.4.1.1302.3.12.10.1.7
(iso.org.dod.internet.private.enterprises.v eritas.products.veritascc.ccTrapDefinition Example: 10.212.12.148 sBranch.ccTrapVarsBranch.ccHost) 1.3.6.1.4.1.1302.3.12.10.1.8 (iso.org.dod.internet.private.enterprises.v eritas.products.veritascc.ccTrapDefinition sBranch.ccTrapVarsBranch.sourceId) 1.3.6.1.4.1.1302.3.12.10.1.9 (iso.org.dod.internet.private.enterprises.v eritas.products.veritascc.ccTrapDefinition sBranch.ccTrapVarsBranch.ccObject) 1.3.6.1.4.1.1302.3.12.10.1.10 (iso.org.dod.internet.private.enterprises.v eritas.products.veritascc.ccTrapDefinition sBranch.ccTrapVarsBranch.sampleData)
This field is the IP address of the OpsCenter server.
443
Table 10-1 Name
OpsCenter trap binding (continued) Value

This field shows the alert severity level.
1.3.6.1.4.1.1302.3.12.10.1.11
(iso.org.dod.internet.private.enterprises.v eritas.products.veritascc.ccTrapDefinition Example: Informational sBranch.ccTrapVarsBranch.ccAlertSeveri ty) 1.3.6.1.4.1.1302.3.12.10.1.12
(iso.org.dod.internet.private.enterprises.v eritas.products.veritascc.ccTrapDefinition Example: 13-10-2008 06:57:34 00 sBranch.ccTrapVarsBranch.ccAlertTime)
This field shows the time when the alert gets cleared.
The first two OIDs listed in the table are standard SNMP OIDs. The other OIDs starting 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 are OpsCenter OIDs. As per SNMPv2c trap definition, the two standard SNMP OIDs must be present as part of every trap. All the 12 OpsCenter OIDs are defined in the OpsCenter MIB files. However, the two standard OIDs are not defined in the OpsCenter MIB files.
About alert description

This section shows the content that is sent for each OpsCenter alert as OID 1.3.6.1.4.1.1302.3.12.10.1.3. Note: 1.3.6.1.4.1.1302.3.12.10.1.3 represents iso.org.dod.internet.private.enterprises.products.veritascc. ccTrapDefinitionsBranch.ccTrapVarsBranch.alertDescription. Most of the alert information in OpsCenter is sent as OID 1.3.6.1.4.1.1302.3.12.10.1.3. Table 10-2 shows the content that each OpsCenter alert sends as OID 1.3.6.1.4.1.1302.3.12.10.1.3.
444
Table 10-2 Alert type

Job
Alert conditions in OpsCenter Alert condition

High job failure rate
Description (Example)
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
Hung job
Alert Raised on: September 7, 2009 2:21 PM Job: 25888 Tree Type : Server Nodes : ccs-win-qe-5 Job Policy: ccsqasol1 Client: ccs-win-qe-5 Alert Policy: Hung Job OpsCenter Server: ccs-sol-qe-17 Severity: Warning
Job finalized
Alert Raised on: September 9, 2009 4:54 PM Job: 26356 Tree Type : Policy Nodes : node1 Job Policy: sample_policy Exit Status: 150 (termination requested by administrator) Client: ccs-win-qe-5 New State: Done Alert Policy: Job Finalized OpsCenter Server: ccs-sol-qe-11 Severity: Warning
445

Media
Alert conditions in OpsCenter (continued) Alert condition

Frozen media
Alert Raised on: August 17, 2009 12:24 PM Tree Type : Policy Nodes: node1 Frozen Media Name: A00004 Media server : ranjan Alert Policy: frozen media policy OpsCenter Server: localhost Severity: Warning
Suspended media
Alert Raised on: August 12, 2009 3:36 PM Suspended Media Name: 0122L2 Tree Type : Policy Nodes: node1 Media server : ccs-win-qe-13 Alert Policy: Suspended media policy OpsCenter Server: localhost Severity: Informational
Exceeded max media mounts
Alert Raised on: August 12, 2009 3:27 PM Media Name: A00009 Tree Type : Policy Nodes: node1 Media server : ccs-win-qe-13 Number of mounts: 3402 Alert Policy: Exceeded Max Media Mounts policy OpsCenter Server: localhost Severity: Critical
Media required for restore
446
Alert conditions in OpsCenter (continued) Alert condition Description (Example)

Alert Raised on: December 4, 2008 4:39 PM Tree Type : Policy 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 OpsCenter Server: ccs-sol-qe-10 Low available media Alert Raised on: August 12, 2009 11:54 AM Tree Type : Policy Nodes: node1 Available Media: 4 Alert Policy: low available media OpsCenter Server: localhost Severity: Warning High suspended media Alert Raised on: August 12, 2009 11:40 AM Tree Type : Policy Nodes: node1 Suspended Media: 1 % Suspended Media: 25.0 Alert Policy: high percentage suspended media OpsCenter Server: localhost Severity: Warning High frozen media
447

Alert Raised on: December 8, 2008 10:24 AM Tree Type : Policy Nodes: node1 Frozen media: 6 % Frozen Media: 66 Alert Policy: highfrozenmedia OpsCenter Server: winfor11 Severity: Warning
448

Catalog

Catalog Space low
Alert Raised on: December 8, 2008 10:08 AM Master server : sargam(sargam) Tree Type : Policy Nodes: node1 Available Catalog Space: 6480880 KB Threshold Catalog Space: 102400 TB Alert Policy: test_catalogspacelow OpsCenter Server: winfor11
Catalog not Backed up 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:21 PM Alert Policy: Catalog not Backed up OpsCenter Server: ccs-sol-qe-17 Severity: Warning Catalog Backup Disabled Alert Raised on: September 5, 2009 3:44 PM Tree Type : Server Nodes : ccs-win-qe-1 Alert Policy: Catalog Backup Disabled OpsCenter Server: ccs-sol-qe-17 Severity: Warning
449

Tape

Mount Request
Alert Raised on: September 7, 2009 6:52 PM Tree Type : Server Nodes : ccs-win-qe-1 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 OpsCenter Server: ccs-sol-qe-12 Severity: Warning
No Cleaning Tape
Alert Raised on: August 17, 2009 12:30 PM Media server : ranjan Robot Number: 0 Alert Policy: no cleaning tape left OpsCenter Server: localhost Severity: Warning
Zero Cleaning Left
Alert Raised on: December 13, 2008 12:02 PM Master server : ORLP-SPEECH01 Media server : ORLP-SPEECH01 Robot Number: 0 Cleaning Tape: CLN084 Alert Policy: test_zerocleaningleft_public OpsCenter Server: winfor11
450

Disk

Disk Pool Full
Alert Raised on: August 20, 2009 5:25 PM Disk Pool ID: SSOD_Pool Disk Pool Name: SSOD_Pool Total Capacity: 1007664128 KB Used Capacity: 1005702144 KB Alert Policy: Disk Pool Full OpsCenter Server: localhost Severity: Informational
Disk Volume Down
Alert Raised on: August 17, 2009 5:08 PM Disk Volume ID: /vol/luns/nbusd_sun10 Disk Pool ID: SSOD_Pool Alert Policy: disk volume down pol OpsCenter Server: localhost Severity: Informational
Low Disk Volume Capacity
Alert Raised on: August 26, 2009 10:35 AM Disk Volume Free Capacity: 106 MB Threshold: 20 % OpsCenter Server: localhost Severity: Major
Drive is Down
Alert Raised on: August 12, 2009 10:39 AM Media server : omlinux2 Drive Name: BNCHMARK.VS640.000 Drive Number: 1 Robot Number: 0 Alert Policy: drive down-individual alert Device Path: /dev/nst0 OpsCenter Server: localhost Severity: Critical
451

High Down Drives
Alert Raised on: August 12, 2009 3:13 PM Drive Number: 1 % Down Drive Paths: 100.0 Alert Policy: high down drives OpsCenter Server: localhost Severity: Major
452

Host
Agent Server Agent Host Name : pinacolada Communication break Server Host Name : PINACOLADA Severity: Warning Master Server Unreachable Alert Raised on: October 23, 2009 12:20 AM Alert Policy: MasterServer Unreachable OpsCenter Server: CCSQAWINSP1 Severity: Major Lost Contact with Media Server Alert Raised on: February 18, 2008 1:33 PM Master server : pmsun22 Media server : pmsun22 Alert Policy: lcm OpsCenter Server: pmwin9 Service Stopped Alert Raised on: August 31, 2009 5:59 PM Tree Type : Server Nodes : ccs-win-qe-1 Media server : omlinux2 Process Name: nbkms Alert Policy: Service stopped OpsCenter Server: ccs-sol-qe-14 Severity: Major Symantec ThreatCon Alert Raised on: September 7, 2009 12:29 PM ThreatCon is at Level 1:Normal Alert Policy: THREAT_CON OpsCenter Server: divakar Severity: Warning Job Policy Change
453

Alert Raised on: September 7, 2009 12:29 PM Tree Type : Server Nodes : ccs-win-qe-5 Changed Policy Name: BMRPolicy Alert Policy: hhjob pol change OpsCenter Server: ccs-sol-qe-17 Modified Policy Attributes : Severity: Warning
Configuring the SNMP trap community name for OpsCenter

For OpsCenter traps, the SNMP trap community name string is OpsCenter by default. Symantec OpsCenter uses a public community named Opscenter. Public community implies a read-only access to SNMP traps. Use the following procedures to configure the SNMP trap community name on Windows and UNIX. To configure the SNMP trap community name for OpsCenter traps on Windows
On the OpsCenter server host, stop all the OpsCenter server services.
Navigate to INSTALL_PATH\OpsCenter\server\config directory and open the 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 4
Save the nm.conf file after making the changes. Restart all OpsCenter services.
454
To configure the SNMP trap community name for OpsCenter traps on UNIX
On the OpsCenter server host, stop all the OpsCenter services.

Navigate to /opt/SYMCOpsCenterServer/config directory and open the 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 4
Save the nm.conf file after making the changes. Restart all OpsCenter services. /opt/SYMCOpsCenterServer/bin/opsadmin.sh start
Configuring the SNMP version for sending SNMP traps

The default SNMP version through which SNMP traps are sent in OpsCenter is SNMPv2c. However, this SNMP version can be changed by modifying a configuration file. The following procedure explains how to configure the default SNMP version on Windows and UNIX. To configure the SNMP version for sending SNMP traps on Windows
On the OpsCenter server host, stop all the OpsCenter services. INSTALL_PATH\server\bin\opsadmin.bat stop
Navigate to INSTALL_PATH\OpsCenter\server\config directory and 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 (for SNMPv3).
3 4
Save the nm.conf file after making the changes. Restart all OpsCenter services: INSTALL_PATH\OpsCenter\server\bin\opsadmin.bat start
455
To configure the SNMP version for sending SNMP traps on UNIX
On the OpsCenter server host, stop all the OpsCenter services: /opt/SYMCOpsCenterServer/bin/opsadmin.sh stop
Navigate to the OpsCenter configuration directory: cd /opt/SYMCOpsCenterServer/config
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 (for SNMPv3).
4 5
Save the nm.conf file after making the changes. Restart all OpsCenter services: /opt/SYMCOpsCenterServer/bin/opsadmin.sh start
About customizing alert settings

In 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:
Windows UNIX <INSTALL_DIR>\OpsCenter\server\config\am.conf <INSTALL_DIR>/SYMCOpsCenterServer/config/am.conf
The alert configuration settings are described as follows: Note: By default all alert configuration parameters are set to true.
am.autoClear Set this parameter to true, if you want to automatically clear the alerts. Make sure that the am.autoClear parameter is set to true, to apply the change in the am.notifyOnAutoClear parameter setting. Set this parameter to true, if you want to send notification after an alert was automatically cleared.
am.notifyOnAutoClear
456
am.notifyOnManualClear
Set this parameter to true, if you want to send notifications after manually clearing alerts.
Note: If you set an alert configuration parameter to a value other than true or false, OpsCenter assumes it as false.
Frequently asked SNMP questions

What 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 439. Is the OpsCenter SNMP community name configurable? Yes. See Configuring the SNMP trap community name for OpsCenter on page 453. 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 community name is maintained as "OpsCenter".
Chapter
11
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 reports

Symantec OpsCenter is a Web-based software application that helps organizations by providing visibility into their data protection environment. By using OpsCenter, you can track the effectiveness of data backup and archive operations by generating comprehensive business-level reports. OpsCenter displays customizable, multi-level views of backup and archive resources and customizable reports for tracking service usage and expenditures.
458
Reporting in OpsCenter About OpsCenter reports
It also contains tools for defining cost metrics and chargeback formulas or handling alerts. A wide range of audiences benefit from the reporting and the management capabilities 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, and capacity planning teams.
About the OpsCenter reports UI

The OpsCenter reports UI consists of the following components:
Report Templates tab This tab lists all Report Templates (or standard or canned reports) that are available in OpsCenter. You can modify the default parameter values of a Report Template as required and generate a new report of that kind. For example, use the existing Backups > Client Count Report Template , change the relative timeframe to four weeks (default timeframe is two weeks) and generate a new Client Count report. You can see all clients that are backed up over the last four weeks. See About Report Templates on page 459. My Reports tab You can save generated reports for your future use. These saved reports are stored in the My Reports tab. Use this section to view the saved reports or modify the parameters of the saved reports and generate new reports out of them. You can also delete the saved reports using the My Reports tab. See Managing My Reports on page 470. See Saving a report on page 463. My Dashboard tab Your saved reports are preserved in My Reports tab, which you can select and publish on My Dashboard tab. You can select multiple reports and add them in the same dashboard section. Thus, you can create multiple dashboard section containing a number of reports. See Managing My Dashboard on page 474.
459
Schedules tab
This tab contains all report schedules. You can create, edit, or delete schedules using this tab. See About schedules on page 478.
Manage Folders tab
Use this tab to manage folders where you have saved your reports. See Managing folders on page 476.
About report creation wizards

OpsCenter provides wizards, which guide you through the entire report creation procedure. To create a report, in the OpsCenter console on the Reports tab, click Create New Report. 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 462. Create a custom report. See Creating a custom report on page 468. Create a report using SQL Query. See Creating a report using SQL query on page 469.
About Report Templates

This section provides details of the Report Templates that are available in OpsCenter. 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 Templates home page is displayed. Click any of the Report Template to view the respective report with default parameter values. See About Report Templates descriptions on page 487. Figure 11-1 shows various components of a report that is generated using a template.
460
Figure 11-1
Report Template
Manage reports toolbar Time filters Report Templates tree Report views Report area
Tabular view
Report Templates tree
This tree lists all Report Templates that are available in OpsCenterOpsCenter.
Manage report options Manage report toolbar Use this toolbar to save, export, or email the generated report. Use these time filters to view the data for a specific period of time. OpsCenter reports are displayed here. Reports can be viewed in different forms or views, Distribution, Historical, or Ranking. Use these options to change the current report view.
Time filters
Report area Report views
About custom reports

Apart from generating reports using the existing templates, you can also create custom reports in OpsCenter by changing the report parameters as required. See Creating a custom report on page 468.
Reporting in OpsCenter Working with Report Templates
461
About custom SQL query

In OpsCenter, you can create reports by directly running SQL queries. Using this report creation option, you do not need to go through multiple parameter selections. Note: You can create only tabular reports bu running SQL queries. You can also run stored procedures using this feature. See Creating a report using SQL query on page 469.
Working with Report Templates

Symantec OpsCenter provides a set of Report Templates or standard or canned reports that have parameters set to default values. You can use modify the default parameters and generate reports to view the required data. OpsCenter reports help you to have a good visibility into your data protection environment. Report Templates are categorized as follows:
Archive These reports are generated based on the archive data that is collected from Enterprise Vault. You can report on the number of messages that are archived across mailboxes or on the size of these messages before and after the archive operation. The backup reports show the information that is related to backups, such as success rate, job status, and protected bytes. This category also includes recovery reports. These reports provide details about the catalogs. The chargeback reports provide details of the backup services expenditures. Using these reports you can track the backup and the recovery usage and the associated cost. You can calculate the cost of data protection management and chargeback to customers and business units. Client reports
Backups
Catalog reports
Chargeback reports
462
Reporting in OpsCenter Working with Report Templates
Disk Based Data Protection
Disk-based data protection (DBDP) reports show disk pool capacity and its usage, performance of clients on LAN or SAN, NetBackup Storage Lifecycle Map These are the job status reports. Using this report category, you can determine the number of jobs that are successful, or partially successful and so on. These reports provide media data, such as tape count or usage These reports show all details about the backup job policies in NetBackup. These reports provide details about vault media.
Job reports
Media reports
Policy reports
Vault reports
See About Report Templates on page 459.
About report filters

There can be hundreds of records or thousands of MB of the data that you may not be concerned about. For example, you want to view only those jobs that were successful. To view this specific data, you need to use the status filter. By setting this filter to Successful while generating the Job Count report, you can view all jobs 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 Template

This section provides the procedure to create a report using an existing Report Template .
Reporting in OpsCenter Managing reports
463
To create a report using an existing Report Template
1 2
In the OpsCenter console, click Reports. 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 modify any of the report parameters. By clicking the Create New Report button, you can launch the report creation wizard that guides you through the entire report creation procedure. Here you can modify the report parameters and view the required data.
3 4
On the Report Wizard, retain the default selection that is Create a report using an existing Report Template and click Next. On the Report Templates list, expand a report category to see the Report Templates within it. Select the Report Template that you want to create a report from and click Next. Select time frame and other filters as required and click Next. Modify display options and click Next.
5 6
Managing reports
This section provides information on the operations that you can carry out on the standard reports that you generate in OpsCenter. You can carry out the following operations:
Saving a report See Saving a report on page 463. Exporting a report See Exporting a report on page 466. Emailing a report See Emailing a report on page 467.
Saving a report
You can save a standard report. This saves the filters that you have selected while generating a report. You can use this set of filters to regenerate the reports with the current time selections. These reports are saved in the OpsCenter database, which you can view using the My Reports tab.
464
See Managing My Reports on page 470. To save a report
1 2 3
In the OpsCenter console, click Reports > Standard Reports. From the Reports tree, select the standard report that you want to save. In the report view area at the right-hand side, click the Save As Report icon. This opens the Save Report pop-up screen.
465
On the Save Report screen, enter the following information:

Report name Enter the report name. For example, if you have generated the Job Count standard report with the group by option selected as Policy Type, and report view as Historical, you can name this report as: NumberofJobsbyPolicies When you select this report on the Saved Reports tab, the report is displayed with the saved filters and in the report view that were selected when the reports were saved, with respect to the current time.
Note: Report name should be unique

across the report tree. Description Sharing Enter the short description for the report. Select Public or Private from this drop-down list. If you save the report in a public folder, all other OpsCenter users can view it. If you save the report in a private folder, only you can view it. Depending on the folder type that you have selected - public or private - the folders displayed for selection vary. In the Folder tree, select a folder where you want to save the report. Create New Click this button to create a new public or private folder. Clicking on this button changes the view of Folder. Enter the folder name and click OK. This folder is made available in the Folder tree for selection. Select this newly created folder where you want to save the report.
Folder
466
Overwrite if file exists
Select this check box if you want to overwrite the existing report with the same name in the same folder. If you do not select this check box and save a report with a name same as any of the existing reports in the selected folder, a confirmation message is displayed before you overwrite the existing report.
Click OK. After a successful save, My Reports tab is displayed with this report selected.
Exporting a report
Using OpsCenter, you can preserve report data in files or print the data. See About file formats available in OpsCenter on page 466. You can open the exported file using other applications, such as a spreadsheet program or a text editor. To export a report
1 2 3 4
In the OpsCenter console, click Reports > Standard Reports. From the Reports tree, select the standard report that you want to export. In the report view area at the right-hand side, click the Export Report icon. This opens the Export Report pop-up screen. On the Export Report pop-up screen, select the export options that you want to export the report with: File format, such as PDF, CSV, or XML and content or report view, such as Distribution, Historical, or Ranking. Click OK. The system displays the export options pertaining to the file format you have selected. Select those options and export the report.
About file formats available in OpsCenter

You can export or email OpsCenter reports in the following file formats:
PDF (Portable Document Format) Can be viewed using a PDF reader, such as Adobe Reader
CSV (comma-separated Use with spreadsheet programs, such as MS Excel. values)
467
TSV (tab-separated values) HTML (hypertext markup language ) XML (Extensible Markup Language)
Compatible with word-processing applications and text editors
Can be opened using with Web browsers
Can be imported (using user-written scripts) by other programs like databases or billing applications
Emailing a report
Using OpsCenter, you can email report data to the selected recipients. You can email a report in a number of different file formats. See About file formats available in OpsCenter on page 466. To email a report
1 2 3 4
In the OpsCenter console, click Reports > Standard Reports. From the Reports tree, select the standard report that you want to email. In the report view area at the right-hand side, click the Email Report icon. This opens the Email Report pop-up screen. On the Email Report pop-up screen, select the email options: File format, such as PDF, CSV, or XML and content or report view, such as Distribution, Historical, or Ranking. Enter email IDs in To, Cc, and Bcc text boxes, to which you want to send emails. If these email IDs do not already exist, they are automatically added to the database. Alternatively, you can add existing email recipients. See Adding email recipients on page 467.
6 7 8
Enter the subject of the email. Enter the message that may be a short description regarding the report data that you want to email. Click OK.
Adding email recipients

This section provides information on how to add email recipients to whom you want to send emails.
468
Reporting in OpsCenter Creating a custom report
To add email recipients
On the Add Email Recipients screen, select the check boxes in front of the email recipients to whom you want to send emails. click To.., Cc.., or Bcc.. depending on where you want to add the selected recipients.
Click OK.
Creating a custom report

This section provides the procedure to create a custom report. This feature is accessible only to the Symantec OpsCenter Analytics users. This option is disabled in the unlicensed OpsCenter version. To create a custom report
1 2 3 4 5 6
In the OpsCenter console, click Reports. On the Report Templates tab, click Create New Report. On the Report Wizard, select the Create a custom report option and click Next. Select the report category and view type and click Next. Select time frame and other filters as required and click Next. 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 468. Click Add.
When the specified condition is met, a notification is sent to the concerned person.
Click Next.
About report conditions

In the Conditions section of the Custom Report Wizard, specify conditions for notification. Conditions represent potential problems, for example an unusually high percentage of backup job failures or an unusually low quantity of data being backed up. Each exception condition is defined by assigning threshold values for a particular metric, such as Success Rate or Total Backup Job Size. You can set a
Reporting in OpsCenter Creating a report using SQL query
469
low threshold, a high threshold, or both. Select a condition while generating a custom report, so that when a condition is true, an alert is triggered or an email notification 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 GB The condition is met whenever the total size of backed-up data falls outside the range of 500-1000 GB.
Creating a report using SQL query

This section provides the procedure to create a report using SQL query. Only Symantec OpsCenter Analytics users can access the custom SQL query function. Note: OpsCenter Analyst and Reporter do not have access to the custom SQL query option. See About user access rights on page 235.
Caution: Make sure about the impact that the entered SQL query has on the OpsCenter database before running it. To create a report using SQL query
1 2 3 4
In the OpsCenter console, click Reports. On the Report Templates tab, click Create New Report. On the Report Wizard, select the Create a report using SQL Query option and click Next. 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 and managed by OpsCenter, enter the following SQL query: select * from domain_masterserver
Click Next. You can view all master server details that are stored in the domain_masterserver database table.
470
Reporting in OpsCenter Managing My Reports
Managing My Reports
You can save generated reports for your future use. These saved reports are stored in the My Reports tab. Use this section to view the saved reports or modify the parameters of the saved reports and generate new reports out of them. You can also delete the saved reports using the My Reports tab.
Creating a report using My Reports tab

This section provides the procedure to create a report using My Reports tab. To create a report
1 2
In the OpsCenter console, click Reports > My Reports. 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 462. See Creating a custom report on page 468. See Creating a report using SQL query on page 469.
Deleting a saved report

This section provides the procedure to delete a saved report. To delete a saved report
1 2 3 4
In the OpsCenter console, click Reports > My Reports. On the My Reports tab, from the reports list, expand a report folder to view the reports that are saved within it. Select the check box in front of the report name. Click Delete.
Viewing a saved report

You can view the saved reports using the My Reports tab. To view a saved report
1 2
In the OpsCenter console, click Reports > My Reports. On the My Reports tab, from the reports list, expand a report folder to view the reports that are saved within it. Select the saved report that you want to view.
471
Editing a saved report

You can edit a saved report. You can edit the report details, such as the report name or the folder where you want to save the edited report. To edit a saved report
1 2
In the OpsCenter console, click Reports > My Reports. On the My Reports tab, from the reports list, expand a report folder to view the reports that are saved within it. Select the saved report that you want to edit. In the report view area at the right-hand side, click the Save As Report icon. This opens the Save Report pop-up screen.
472
On the Save Report screen, enter the following information:

Report name Enter a new name for the report. When you select this report on the Saved Reports tab, the report is displayed with the saved filters and in the report view that were selected when you saved the reports, with respect to the current time. Description Sharing Enter short description for the report. Select Public or Private from this drop-down list. If you save the report in a public folder, all other OpsCenter users can view it. If you save the report in a private folder, only you can view it. Depending on the folder type that you have selected - public or private - the folders displayed for selection vary. In the Folder tree, select a folder where you want to save the report. If you do not select any folder, the report is saved on the root. Create New Click this button to create a new public or private folder. Clicking on this button changes the view of Folder. Enter the folder name and click OK. This folder is made available in the Folder tree for selection. Select this newly created folder where you want to save the report. Overwrite if file exists Select this check box if you want to overwrite the existing report with the new changes. If you do not select this check box and attempt to save the report with the existing report name, the system displays an alert message. You need to either overwrite the existing report or save it with a different name.
Folder
Click OK.
473
Export a saved report

Using 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. See About file formats available in OpsCenter on page 466. You can open the exported file using other applications, such as a spreadsheet program or a text editor. To export a saved report
1 2
In the OpsCenter console, click Reports > My Reports. On the My Reports tab, from the reports list, expand a report folder to view the reports that are saved within it. Select the saved report that you want to export. In the report view area at the right-hand side, click the Export Report icon. This opens the Export Report pop-up screen. On the Export Report pop-up screen, select the export options that you want to export the report with. Select file format, such as PDF, CSV, or XML and content or report view, such as Distribution, Historical, or Ranking. Click OK. The system displays the export options pertaining to the file format you have selected. Select those options and export the saved report.
3 4
Email a saved report

Using OpsCenter, you can email the saved report data to the selected recipients. You can email the report in the following file formats:
PDF (Portable Document Format) Can be viewed using a PDF reader, such as Adobe Reader
CSV (comma-separated Use with spreadsheet programs, such as MS Excel. values) TSV (tab-separated values) HTML (hypertext markup language ) XML (Extensible Markup Language) Compatible with word-processing applications and text editors
Can be opened using with Web browsers
Can be imported (using user-written scripts) by other programs like databases or billing applications
474
Reporting in OpsCenter Managing My Dashboard
To email a report
1 2
In the OpsCenter console, click Reports > Saved Reports. On the My Reports tab, from the reports list, expand a report folder to view the reports that are saved within it. Select the saved report that you want to email. In the report view area at the right-hand side, click the Email Report icon. This opens the Email Report pop-up screen. On the Email Report pop-up screen, select the email options: File format, such as PDF, CSV, or XML and content or report view, such as Distribution, Historical, or Ranking. Enter email IDs in To, Cc, and Bcc text boxes, to which you want to send emails. Enter the subject of the email. Enter the message that may be a short description regarding the report data that you want to email. Click OK.
3 4
5 6 7 8
Managing My Dashboard
Your saved reports are preserved in My Reports tab, which you can select and publish on My Dashboard tab. You can select multiple reports and add them in the same dashboard section. Thus, you can create multiple dashboard sections containing a number of reports. You can add only 10 reports in a dashboard. See Adding reports to a dashboard on page 474. See Modifying a dashboard section on page 475. See Deleting a dashboard section on page 475. See Emailing dashboard sections on page 476. See Refreshing My Dashboard on page 476.
Adding reports to a dashboard

This section provides the procedure to add reports to a dashboard.
Reporting in OpsCenter Managing My Dashboard
475
To add reports to a dashboard
1 2 3 4 5 6
In the OpsCenter console, click Reports > My Dashboard. Click Add. On the Add Dashboard Section pop-up screen, enter the section name. Expand the Private or Public Reports folder to view existing reports. Select the check boxes in front of the report names, which you want to publish on the dashboard. Click OK.
Modifying a dashboard section

This section provides the procedure to modify dashboard section. To modify a dashboard
1 2 3 4 5 6 7
In the OpsCenter console, click Reports > My Dashboard. Click Edit. On the Edit Dashboard Section pop-up screen, select the dashboard section from the drop-down list, that you want to modify. Modify the section name. Expand the Private or Public Reports folder to view existing reports. Select or clear the check boxes in front of the report names, which you want to publish on or remove from this dashboard section. Click OK.
Deleting a dashboard section

This section provides the procedure to delete a dashboard section. To delete a dashboard section
1 2 3 4
In the OpsCenter console, click Reports > My Dashboard. Click Delete. On the Delete Dashboard Section pop-up screen, select the dashboard section from the drop-down list, that you want to delete. Click OK.
476
Reporting in OpsCenter Managing folders
Emailing dashboard sections

You can email your dashboards. To email a dashboard
1 2 3 4
In the OpsCenter console, click Reports > My Dashboard. Click the Email Dashboard icon. On the Email Dashboard pop-up screen, select the format in which you want to send the email. Select email recipients from the To.., Cc.., and Bcc.. as appropriate. Alternatively, enter new email recipients, which are added into the database.
5 6
Enter the email subject and message. Click OK.
Refreshing My Dashboard
This section provides the procedure to refresh My Dashboard. To refresh My Dashboard
1 2
In the OpsCenter console, click Reports > My Dashboard. Click the Refresh icon.
Managing folders
OpsCenter 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 report folders, 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 476. See Editing a folder on page 477. See Deleting folders on page 478. See Deleting reports from a folder on page 478.
Adding a folder
This section provides a procedure to add a report folder.
Reporting in OpsCenter Managing folders
477
To add a folder
1 2
In the OpsCenter console, click Reports > Manage Folders. On the Reports tree, select a check box in front of a private or public folder node in which you want to create a new folder.
Click Add. This displays the Create new folder pop-up window. Make sure that you have selected only one folder. If multiple folders are selected, the Add button is disabled.
4 5
Enter the folder name. Click OK. This folder is added in the selected node.
Editing a folder
This section provides a procedure to edit a report folder. To edit a folder
1 2 3
In the OpsCenter console, click Reports > Manage Folders. On the Reports tree, select a check box in front of a private or public folder that you want to edit. Click Edit. This displays the Edit folder name pop-up window. Make sure that you have selected only one folder. If multiple folders are selected, the Edit button is disabled.
4 5
Edit the folder name. Click OK.
478
Reporting in OpsCenter About schedules
Deleting folders
This section provides a procedure to delete a report folder. If you delete a report folder, all reports that are saved in that folder are deleted. To delete folders
1 2 3
In the OpsCenter console, click Reports > Manage Folders. On the Reports tree, select a check boxes in front of private or public folders that you want to delete. Click Delete.
Deleting reports from a folder

This section provides a procedure to delete reports that are saved in a public or private folder. To delete reports from a folder
1 2
In the OpsCenter console, click Reports > Manage Folders. On the Reports tree, select a private or public folder from which you want to delete the reports. This displays a list of reports that are saved in the selected folder, at the right-hand side of the page. From the list of reports, select the check boxes in front of the reports that you want to delete. Click Delete.
3 4
About schedules
Using report schedules, you can email or export reports at a scheduled time. Each report schedule is associated with a time schedule at which it emails or sends the specified reports. OpsCenter provides a wizard to create a report schedule. See Creating a report schedule on page 481. The following table describes the steps that you need to carry out to email or export a report on a specific schedule. This is a suggested flow of steps. See Managing time schedules on page 485.
Reporting in OpsCenter Managing report schedules
479
Table 11-1
Creating a report schedule Reference topic

See Creating a time schedule on page 485. See Creating a report schedule on page 481.
Step number Step

1 Create a time schedule.
Create a report schedule. OpsCenter provides a wizard to create a report schedule. This wizard lets you specify the following details:

Report schedule name
File format in which you want to email or export reports Select a time schedule. You can either select an existing time schedule that you have created in the first step or create a new schedule from here to associate it with this report schedule. Specify details of export or email options. Select the reports that you want to export or email on a specific schedule.
Note: You can select only saved

reports in a schedule.
Managing report schedules

NetBackup OpsCenter provides you a way with which you can export or email a report on a specific schedule. For this you need to create a report schedule that is associated with a time schedule on which the specified reports are exported or emailed. Each report schedule can be associated with a single time schedule. A single time schedule can be associated with multiple report schedules. See Managing time schedules on page 485. This section describes how to create and manage report schedules.
Viewing report schedule details

This section provides information on viewing the list of report schedules.
480
If you have applied conditions for the selected report, the list of applicable conditions is shown on the last page of the wizard. You can select the appropriate conditions. An email notification is sent to the relevant recipients if the selected condition is satisfied. To view a report schedule
In the OpsCenter console, click Reports > Schedules. By default, the Report Schedules tab is selected.
On the Report Schedules tab, view the following report schedule details.
Name Status Name Name of a time schedule that is associated with this report schedule Date on which this schedule runs Date on which this schedule stops Specifies whether you have exported the associated reports Specifies whether you have emailed the associated reports Number of the reports that are exported or emailed when this schedule runs Name of a report schedule
Start Date End Date Export
Email
Reports
481
Creating a report schedule

To create a report schedule
1 2
In the OpsCenter console, click Reports > Schedules. On the Report Schedules tab, click Create. OpsCenter provides a wizard that guides you through the procedure of creating a report schedule. The Enter Report Schedule Details page appears as follows:
Enter the following report schedule details:

Report Schedule Name Enter report schedule name. This is a mandatory field. Select a file format in which you want to export or email report the associated reports. See About file formats available in OpsCenter on page 466.
Select Format
482
Click Next. The following page appears:
Select the Use existing schedule option if you want to run this schedule on any existing time schedule. If you want to create a new time schedule for this report schedule, select Create new time schedule. See Creating a time schedule on page 485. If you have selected Create new time schedule, the system takes you to the Time Schedule creation wizard. After creating a time schedule you can select the export and the email report options.
Click Next.
483
If you have selected the Use existing schedule option in the previous step, the Configure Export / Email Report Settings page, specify the following details: You can either select Export, Email, or both options.
Export Select this check box if you want to export the reports that are associated with this schedule. See About file formats available in OpsCenter on page 466. Location Enter a directory path where you want to save the exported report or click Browse to select the desired location. Select this check box if you want to overwrite a file that already exists at the specified location. Select this check box if you want to email the reports that are associated with this schedule. Select email IDs to which you want to email reports. Select email IDs to add in the Cc list of email. Select email IDs to add in the Bcc list email. Type the email subject. For example: Daily Job Count Report Type any other related information.
Overwrite if file exists
Email
To
Cc
Bcc
Subject
Message
Click Next.
484
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.
Click Save.
Editing a report schedule

This section describes how to edit report schedule details. To edit a report schedule
2 3 4 5
On the Report Schedules tab, select a report schedule from the list that you want to edit. Click Edit. Edit the report schedule details using the wizard. Click Save.
Deleting a report schedule

This section describes how to delete a report.
Reporting in OpsCenter Managing time schedules
485
To delete a report schedule
2 3
On the Report Schedules tab, select a report schedule from the list that you want to delete. Click Delete.
Managing time schedules

This section provides procedures to create and manage a report schedule. Each report schedule can be associated with only a single time schedule. A single time schedule can be associated with multiple report schedules. See Managing report schedules on page 479.
Viewing time schedule details

This section provides a procedure to view the details of time schedules. To view a time schedule
1 2
In the OpsCenter console, click Reports > Schedules. Click Time Schedules. The following time schedule details appear:
Name Time of Report Generation Name of the time schedule Time when the associated reports are exported or emailed A pattern with which this schedule runs Date when the schedule starts Date when the schedule stops
Recurrence Pattern Start Date End Date
Creating a time schedule

To edit a time schedule
1 2
In the OpsCenter console, click Reports > Schedules. Click Time Schedules.
486
Reporting in OpsCenter Managing time schedules
3 4
On the Time Schedules tab, click Create. On the Create Time Schedule page, specify the following details:
Schedule Name Time of Report Generation Enter name of the time schedule. Enter the time when the schedule runs and the associated reports are exported or emailed. Select a pattern with which you want this schedule to be run. The following schedule patterns are available:

Schedule Pattern
One Time Daily Weekly Monthly Quarterly Yearly
Depending on the pattern selected, options change.
Click OK.
Editing a time schedule

To edit a time schedule
1 2 3 4 5 6
In the OpsCenter console, click Reports > Schedules. Click Time Schedules. On the Time Schedules tab, from the table, select the time schedule that you want to edit. Click Edit. Edit the time schedule details. Click OK.
Reporting in OpsCenter About Report Templates descriptions
487
Deleting a time schedule

To delete a time schedule
1 2 3 4
In the OpsCenter console, click Reports > Schedules. Click Time Schedules. On the Time Schedules tab, from the table, select the time schedules that you want to delete. Click Delete.
About Report Templates descriptions

This 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 be exported and emailed only in the 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 not supported. For the OpsCenter admin, the default view that is selected is All_Master_Server.
See About archive reports on page 488. See About backup reports on page 489. See About catalog reports on page 504. See About chargeback reports on page 505. See About client reports on page 505. See About Disk Based Data Protection on page 510. See About job reports on page 511. See About media reports on page 514. See About performance reports on page 517. See About policy reports on page 520. See About vault reports on page 522.
488
About archive reports

This section provides descriptions of archive Report Templates available in OpsCenter.
Archived Size
This report is available only in the Archive Storage report category. Use this report if you want to determine the archived size of the Exchange Server data that was archived. You can determine how much is the size of the Exchange Server 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 using the Advanced Filters option on the Report Wizard page. The Archived Size report is available in the Archive Storage report category. The Original Size Vs Archived Size report depicts the difference between the two size of Exchange Server data. The more the difference, the more efficient is your archival process.
Original Size Vs Archived Size report

This report provides the comparison between original size and archived size of Exchange Server data. using the report, you can determine how much was the original size of the data that was archived later. The difference between original size and archived size is termed as savings. If the savings are more, it implies that data was archived in a very efficient way and thus, lesser storage space was required. The Original Size Vs Archived Size report is available in the Exchange report category. Target Server is selected as the Report On parameter.
Storage Report - Tabular

The Storage Details report shows details of archive the data that is stored in various Vault Stores and Vault Partitions. The Archived Size report is available in the Archive Storage report category.
Exchange > Mailbox Quota

The Mailbox Quota report displays the top mailboxes in Exchange Server, which have exceeded a particular mailbox size limit. This report is available in the Ranking report view. There are three types of Mailbox Quota reports:
489
By Warning Limit
This report shows the mailboxes that have exceeded the Warning limit set in Exchange Server. The Warning limit is a limit set for mailboxes, which decides how much 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 have exceeded 256 MB of data.
By Send Limit
This report shows the mailboxes that have exceeded the Send limit set in Exchange Server. The Send limit is a limit set for mailboxes, which is greater than the Warning limit. If size of a mailbox exceeds this limit, emails cannot be sent from this mailbox.
By Receive Limit
This report shows the mailboxes that have exceeded the Receive limit. If size of your mailbox exceeds the Receive limit, you cannot receive any emails.
The Mailbox Quota reports are available in the Exchange report category.
About backup reports

This section provides descriptions on all backup Report Templates available in OpsCenter.
Activity Planning > Capacity Planning -> Historical Size

This report shows the historical supply vs. demand. Supply (yellow line) is defined as all available free space on all the backup media in the backup application. For disk this is an exact calculation of remaining free capacity. For tape this number is calculated by taking the average size of all full media of the same tape type. That average is then used for the predicted size of all other tapes that are not full of the same type. This is necessary since tapes do not have an exact capacity and are written to until the end of tape mark. On the demand side (blue line) this is a calculation of all backup jobs for the time period. The idea for this report is that the difference between the blue line and yellow line is the extra capacity that was not needed. In an ideal environment these lines would match with the blue line being slightly under the yellow line showing that all the space for backups is used. This report can sometimes be referred to as the just in time inventory report since the concept was derived from the business theory by the same name. The default is to show the total environment but for operational use it would need to be filtered down to individual storage locations since some can be closer to 100%
490
capacity than others. This can be easily done by clicking on edit at the top of the report.
Activity Planning > Capacity Planning -> Forecasted Size

Similar to the previous report this shows the supply vs. demand historically but now also adds a forecast line 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 disk or more backup tapes) needs to be added. In the above example the supply is by far outgrowing the demand, which would suggest that more capacity doesnt need to be purchased. The default first view of this report shows the entire backup environment but for actual use it should be filtered to a specific tape library or disk pool since some libraries or pools may be closer to full capacity than others.
Activity Planning -> Forecast -> Job Count

This report shows you the total number of backup jobs for each day in the past two weeks. A linear regression forecast is also performed to show you how many backups you can expect to be do for the next three days based on the current data.
Activity Planning -> Forecast -> Job Size

This report shows you the total gigabytes backed up for each week in the past two months. A linear regression forecast is also performed to show you how much you can expect to be back up for the next three weeks based on the current data.
Activity Planning -> Scheduled Jobs -> Scheduled Jobs report

This report is available in ranking report view, which depicts how many jobs have been 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 want to view the job count for clients, schedules, or master servers, change the report parameters. To change the report parameters
1 2 3
On the Scheduled Jobs report, click the Edit link. On the Report Wizard, from the Report On drop-down list, select a Scheduled Job attribute. For example: Client, Master Server, Policy, or Schedule Name. Click Run.
491
Note: To view job count for a specific client, policy, master server, or schedule, click Show Advanced Filters and select name of the client, policy, master server, or schedule, for which you want to view job count.
Activity Planning -> Scheduled Jobs -> Job Count-Scheduled Vs Actual

This historical report depicts how many jobs were scheduled to run in future and how many jobs are run. The report essentially shows the comparison between Scheduled (Future) Job Count and Actual Job Count. Using this report you can determine whether the jobs that were scheduled to run in future have been run on schedule. By default the Actual Job Count includes manual jobs, which were initiated manually 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 2 3
On the Job Count-Scheduled Vs Actual report, click the Edit link. On the Report Wizard, in the Filter Options section, select Yes from the Exclude Manual Jobs drop-down list. Click Run.
Activity Planning -> Scheduled Jobs -> Job Count Within Backup Window
This historical report depicts how many jobs were scheduled and how many jobs have been run within the specified backup window. The report essentially shows the comparison between Scheduled (Future) Job Count and Actual Job Count, during the backup window. Use this report to determine whether your backup windows are appropriate and are properly used.
Activity Planning -> Scheduled Jobs -> Job Count Details-Scheduled Vs Actual
This tabular report shows the comparison between Scheduled Job count and Actual Job count for each of the combinations of clients, policies, and schedules, for each day.
492
Note: By default, the Job Count Details-Scheduled Vs Actual report shows job count 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 2 3 4
On the Job Count Details-Scheduled Vs Actual report, click the Edit link. On the Report Wizard, in the Define Viewable Columns section, select a column name (Client or Master Server) from the Available Columns list. Click >> button. 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, or schedule, for which you want to view job count. By default the jobs that were run (Actual Job Count) include manual jobs, which do 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 jobs that are of execution type Scheduled. To exclude manual jobs from the actual jobs
1 2 3
On the Job Count Details-Scheduled Vs Actual report, click the Edit link. On the Report Wizard, in the Filter Options section, select Yes from the Exclude Manual Jobs drop-down list. Click Run.
The Job Count Details-Scheduled Vs Actual report shows comparison between Scheduled Job count and Actual Job count. The Actual Job count includes Manual Jobs.
Activity Planning -> Scheduled Jobs -> All Jobs

This canned report shows jobs in a tabular form, which include the following:
493
Manual Jobs
These jobs are initiated manually, by NetBackup admin at his or her discretion. Therefore, these jobs do not have schedule time associated with them.
Note: While generating the Job Count-Scheduled Vs Actual report,

you have an option to exclude the manual jobs from the actual job count and show only those jobs that are of execution type Scheduled. See Activity Planning -> Scheduled Jobs -> Job Count-Scheduled Vs Actual on page 491. Scheduled Jobs These jobs are scheduled to run in future. Each Scheduled Job information comprises a client, policy, schedule, and schedule time. OpsCenter stores this information historically. Each Scheduled Job when run on the specified schedule time becomes an actual job of execution type Scheduled. Thus, a Scheduled Job has a corresponding actual job entry in OpsCenter database. This particular Scheduled Job can be identified by the unique combination of client, policy, schedule, and schedule time. You can compare the schedule time of this Scheduled Job with the corresponding Job Start Time to determine whether that job was run on scheduled time or not.
Activity Planning -> Stored Backup Images -> Historical

This report shows you the total amount of data in gigabytes that was backed up but has not expired yet for each of the days in the past two weeks. This report shows results only for NetBackup.
Activity Planning -> Stored Backup Images -> Rankings

This report shows you the top 10 largest clients that are ranked by the amount of data they have backed up and which has not expired yet for the past two weeks. This report shows results only for NetBackup.
Activity Planning -> Stored Backup Images -> Distribution

This report gives you a breakdown of the backup clients that are ranked by the amount of data they have backed up and which have not expired yet for the past two weeks. This report shows results only for NetBackup.
Activity Planning -> Stored Backup Images -> Duplicate Copies

The axis on the left is for the height of the blue bars that tells the number of duplicate backup copies that exist overall. The yellow line is the axis on the right
494
and it shows the percentage of backup images that are copies. This is a particularly useful report for situations where you want to make certain 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 yellow line would show .5 for 50% since half of the backup images are copies. The same situation for 3 copies would be a blue bar height of 2 and a yellow line percentage of .66 or 66%. In operational use you can filter this report down to specific policies or the clients that you want to ensure always have a 50% or greater yellow line so that more than 1 backup copy exists.
Activity Planning -> Backup Window > Job Count

This report shows the total number backup jobs in the last two weeks shown by the hour of the day in which each job ends. It also renders a configurable backup window to help quickly identify if a lot of jobs end in or outside of what your backup window is or should be. The report can help you see if there are any hours within the backup window that are under utilized and whether any load balancing is appropriate.
Activity Planning -> Backup Window > Job Size

This report shows the total gigabytes backed up in the last two weeks shown by the hour of the day in which each job ends. It also renders a configurable backup window to help quickly identify if a lot of jobs end in or outside of what your backup window is or should be. The report can help you see if there are any hours within the backup window that are under utilized and whether any load balancing is appropriate.
Activity Planning -> Backup Window > File Count

This report shows the number of files that were backed up for each hour of the day. The height of each bar on the graph is the total number of files that are backed up for that hour across the entire date range selected. A user defined backup window is drawn in yellow to compare with what hours the files should have been backed up in. Bars outside of the yellow window represent the activity that occurred outside of the backup window. The report can also be used to see what hours may have capacity to add more backups while still remaining in the backup window.
Activity Planning > Client Count -> Historical

This report shows the total number of unique clients that are backed up per day for the last two weeks broken down by each master server. It can help you highlight potential problems by showing any variations in the number of clients that you think should be backed up and how many are in fact getting backed up.
495
Activity Planning -> Client Count -> Rankings

This report shows you the top 10 largest environments by listing the number of unique clients that got backed up per each media server in your environment for the past two weeks.
Activity Planning -> Client Count -> Distribution

This report gives you a breakdown by each master server of the number of unique clients that got backed up in the last two weeks.
Activity Planning -> Job Duration -> Historical

This report shows the total amount of time spent that is when backups are done each day for the past two weeks.
Activity Planning -> Job Duration -> Rankings

This report shows you the top 10 highest clients that are ranked by the total amount of time theyve taken to be backed up for the past two weeks.
Activity Planning ->Job Size-> Historical

This report shows you the total gigabytes backed up for each day in the last two weeks. Unexpected variations in this report between your day-to-day incremental or between full backup cycles can indicate problems.
Activity Planning ->Job Size-> Rankings

This report shows you the top 10 largest backup clients by ranking them on the total number of gigabytes backed up for that client in the past two weeks. The report can give you an idea of your top consumers and whether those consumers are what you expected.
Activity Planning ->Job Size-> Distribution

This report gives you a breakdown by each media server of the total gigabytes theyve backed up over the past two weeks. It shows you a very clear distribution of the amount of data going to all your media servers and whether any type of load balancing might be beneficial.
496
Activity Planning -> Job Count -> Historical

This report shows you the total number of backed jobs that are performed for each day in the last two weeks. Unexpected variations in this report between you're day-to-day incremental or between full backup cycles can indicate problems.
Activity Planning -> Job Count -> Rankings

This report shows you the top 10 largest environments by ranking the total number of jobs that are performed by each media server for the past two weeks.
Activity Planning -> Job Count -> Distribution

This report gives you a breakdown of the number of jobs that are performed by each media server in your environment. It highlights how busy each of your media servers are and if any type of load balancing between your media servers could spread the workload.
Activity Planning -> File Count -> Historical

This report shows you the total number of files that got backed up for each day in the last two weeks for each of your master servers. Unexpected variations in this report between your day-to-day incremental or between full backup cycles can indicate problems.
Activity Planning -> File Count -> Rankings

This report shows you the top 10 largest backup clients by ranking them on the total number of files that were backed up for them for the past two weeks.
Activity Planning -> File Count -> Distribution

This report gives you a breakdown by each master server of the total number of files that got backed up in the last two weeks.
Deduplication -> Size Factor -> Historical

This report is usually the most talked about when it comes to deduplication since it shows what the deduplication ratio is for each day over the last two weeks (the time frame is modifiable). The deduplication ratio is calculated by taking the total number of bytes that would normally be backed up and dividing it by the number of bytes that have changed and were backed up. So if 100TB exists on all the backups taking place but only 10TB were changed and therefore transferred you would have a rate of 10.
497
Deduplication -> Size Factor -> Rankings

This deduplication report ranks the top hosts in terms of which ones have the best deduplication ratio in bytes. These hosts have the least amount of change and therefore you get the best benefit from deduplication.
Deduplication -> Size Savings -> Historical

This report is similar to the file factor report but instead shows the total number of bytes that dont need to be backed up because of deduplication. There is no calculation or ratio in this number, it is the number of bytes (MB, GB, TB etc.) that have not changed since the last backup and therefore dont need to be backed up.
Deduplication -> Size Savings -> Rankings

Similar to the previous report this one shows the number of bytes that have not changed within the time frame and therefore dont have to be backed up due to deduplication. The report groups the total number of bytes saved per host being backed up to show the top five hosts in terms of deduplication savings.
Deduplication -> Protected Files vs. Backed Up Files

The blue bars in this report show the number of files being protected and the yellow line is the number of files that needed to be transferred since they have not changed. The difference between these bars and lines are the savings as shown in the File Savings report folder and the blue bar when divided by the yellow line is the File Factor reports in the same folder.
Deduplication -> Protected Size vs. Backed Up Size

Similar to the previous report this shows the numbers in bytes instead of files. So for block level deduplication the blue bars represent the total number of bytes that exist on all the backups as if they were normal full backups and the yellow line represents the number of bytes that have changed and therefore needed to be transferred. The Size Savings and Size Factor report folders shows the difference between the bars and lines or the deduplication ratio respectively.
Disk Pools -> NetBackup Disk Pool Capacity

This 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 amount of space that is occupied by backups across all NetBackup 6.5 Disk Pools which would include OpenStorage Devices, PureDisk deduplication option storage, SharedDisk, or even AdvancedDisk pools. Along with usage the average of the high and the low water mark is taken for each disk pool and drawn on the graph.
498
Since this is an average it should not be used for planning purposes but rather estimation. In actual usage this report should be filtered on a specific Disk Pool to show the exact high and low water mark. Finally the forecast is shown so that it can be determined when capacity needs to be added or backups expired to maintain operations.
Disk Pools -> NetBackup Disk Pool Size vs. Percentage Full
This report is specific to NetBackup 6.5 and above which has new devices and storage units called Disk Pools. A Disk Pool may be an OpenStorage device, a PureDisk Deduplication system, SharedDisk, or a group of local or network disk volumes that are pooled together. The bars represent the total number of available bytes across all disk pools with the colors representing the total amount of space per disk pool. The lines represent the percentage full each disk pool is. So this report can help identify how much disk space is used for backups, which pools are the largest, which ones are nearing capacity and how the backup environment is load balancing across disk storage.
Disk Pools -> NetBackup SAN Client Performance

This report is specific to NetBackup 6.5 and above which features Fibre Channel connected clients called SAN Clients. The blue and the yellow bars are stacked together to show the total number of jobs per day the blue bars represent 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 jobs that ran that day the purple representing total job throughput by LAN and the yellow representing total job throughput by SAN. This report helps identify what ratio of LAN to SAN traffic for backups are run and what performance benefit is gained by doing so.
Job Browser -> Tabular Backup Report

This report shows you a detailed listing of all the backup activity that is performed for the past two weeks. You can edit the report to show or hide the columns you are interested in. You can also filter the report to show activity for a limited sample set, such as one or more policies or clients.
Risk Analysis -> Client Risk Analysis

This report identifies the backup clients that have gone without a successful backup for a specified period of time and hence are at risk from a restore or recoverability standpoint. The specified period of time is user- definable along with several other variables for filtering purposes. The report is interpreted as all client or policy combinations that have gone x hours, days, weeks, or months
499
without a successful backup. The level of granularity is at a client or policy level and exposes the clients that have multiple backup policies where one of them may repeatedly fail. The primary use case is to show that all clients have been backed up as of the last x hours and all clients have a full backup not more than x days ago. The report also has a Is Active filter to include only those that are currently active as well as the capability to count partial successes as success and vice versa.
Risk Analysis -> Client Coverage

The purpose of this report is to show what hosts are not backed up because the backup application is not even aware of them. The report does this by comparing what OpsCenter hosts are known to be backed up with an external list that is fed in 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 backup application and policy executed the backup and the time of the last full or incremental backup.
Risk Analysis -> Recovery Point Objective

- RPO Recovery Point Objective (RPO) and Recovery Time Objective (RTO) have emerged as generally accepted metrics for client recoverability. This report ranks all 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 client level and thus clients with multiple backup policies are represented by the policy with most recent success. This it is recommended that this report not be used for multi-policy clients. The client Is Active filter allows for those hosts that are not actively backed up to be omitted. The elapsed time in the report is always between now and the last successful backup. The report is effective in its graphical rankings format placing the clients with longest elapsed time at the top.
Status -> Daily Summary of Backup Activity

This report is the third of three using the advanced success or the failure calculation logic around the notion of first, all and last job. It collects all information around both successes and failures and presents the results that are grouped by (day or month) timeframe for either client or the job success rate. Client success rate is a count of successful clients where all policies that are defined to the client must be successful to declare the 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 and a 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 whereas back up architects and
500
administrators examine all three. These reports work well with views and can be reported on at any level with robust filtering capabilities.
Status -> Failed Job Count

This 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 was first or last one is made. It provides visualization of whether a problematic trend exists. It can be reported on against any view or level within a view along with any of the key backup infrastructure components (backup server, media server) and attributes (policy, policy type, schedule, OS, product, transport type). Filtering is available on all components and attributes. The primary use case of the report is verification of whether actions taken to correct persistent failures produce results and reversing trends.
Status -> Partially Successful Job Count

This 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 open during the backup job. It can be reported on against any view or level within a view along with any of the key backup infrastructure components (backup server, media server) and attributes (policy, policy type, schedule, OS, product, transport type). Filtering is available on all components and attributes. The primary use case of the report is verification of whether actions taken to correct the open file situation by moving the scheduling of the client or policies produce results and reversing trends.
Status -> Successful Job Count

This report aggregates successful jobs and shows these across a timeline. It provides a visualization of job volume trends. It can be reported on against any view or level within a view along with any of the key backup infrastructure components (backup server, media server) and attributes (policy, policy type, schedule, OS, product, transport type). Filtering is available on all components and attributes. The primary use case of the report is verification of trends and the 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 of managing a backup operation.
Status -> All Failed Backups

This report is one of three using the advanced success or failure calculation logic around the notion of first, all and last job. They require schedule and window parameters enabling a precise definition of timeframes. Additionally, these reports
501
have aggregation levels of job and client. The first job success or failure is the first job for a client/policy/schedule combination in its defined backup window and last job is the opposite. As failed jobs are rerun one or more times, the last job represents the last of the reruns within the window. This report produces the 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 where failure notification to users is based around last job and failures leading up to the last one is ignored.
Status -> Consecutive Failures

This report is the second of three using the advanced success or failure calculation logic around the notion of first, all and last job. The main use case is the calculation of 2 or more consecutive failures based around Last Job Success/Failure. It applies intricate logic to pick off the last failed job and in turn to determine that the last job failures are indeed consecutive. This report can be best verified through the Client Risk Analysis report where if 3 consecutive failures with 24 hour windows were chosen, the client or the policy combo should also appear on the risk report as not having a successful backup in 72 or more hours.
Status -> Job Status -> Historical

A 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, or year across any timeframe. The report is a count of jobs for each of the three outcomes. The simplicity of the presentation helps easily identify both positive and negative trends as well as one-off deviations. For NetBackup environments, the report can also be generated where attempts rather than jobs are counted. In NetBackup, jobs can be configured for x many attempts before you exit with a status. The report can be filtered across a selection that includes Views, Backup and Media Servers, Backup Level, Policies, Schedules, Transport Types, Operating Systems and Business Classifications.
Status -> Week At A Glance

This report summarizes activity for a week by symbolically displaying the result of 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, Size etc.) is provided. It can be reported on against any view or level within a view along with any of the key backup infrastructure components (backup server, media server) and attributes (policy, policy type, schedule, OS, product, transport type). Filtering is available on all components and attributes. The report is highly
502
effective as it provides a visualization of job status for the most current data and how that compares to the previous six days.
Status -> Job Status -> Distribution

A 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 three outcomes. 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 report can be filtered across a selection that includes Views, Backup and Media Servers, Backup Level, Policies, Schedules, Transport Types, Operating Systems, and Business Classifications.
Success Rate -> Success Rate - First Attempts

This report shows success rate as its aggregated at the attempt (known as try) level. Specifically, it zooms in on the measurement of the first attempt for each job. Jobs can be configured for x many attempts before you exit with a status. If for example the attempt setting is two and success is attained on the second attempt, this translates into a 50% All Attempt rate and 0% First Attempt rate and 100% job success rate. This metric is only supported for backup applications in which attempt level data is available. A target line is also supported providing for an effective visual presentation on when the target is exceeded. Filtering is available on all components and attributes. Main use case is to use this and the All Attempts report together to see how often success is attained on the first attempt as opposed to second, third etc. attempts.
Success Rate -> Success Rate At Least one Success Per Client
This last of the single-line success rate reports give the highest number since it shows at least one success per client stream. Meaning as long as one job is successful despite any number of retries, it is a 100% success. This is typically a report to show overall exposure to someone outside the backup team. A 100% on this report indicates that everything was backed up even though it may have taken a number of retries.
Success Rate -> Success Rate > All Attempts

This report shows success rate as its aggregated at the attempt ( try) level. Jobs can be configured for x many attempts before exiting with a status. If for example the attempt setting is two and success is attained on the second attempt, this translates into a 50% attempt rate and 100% job success rate. This metric is only supported for backup applications in which attempt level data is available. A target
503
line is also supported providing for an effective visual presentation on when the target is exceeded. It can be reported on against any view or level within a view along with any of the key backup infrastructure components (backup server, media server) and attributes (policy, policy type, schedule, OS, product, transport type). Filtering is available on all components and attributes. Main use case is long-term historical data on one of the key performance indicators.
Tape Devices-> Library Capacity Forecast

This report provides a capacity forecast of Tape Libraries. A libraries capacity is calculated by multiplying Slot Count by Slot Capacity. Slot capacity is the capacity of the tape in the slot. As no standard exists for measuring library capacity, the report enables several methods by which an individual tapes capacity is determined. These consist of using the maximum, the minimum and the average size of full tapes to determine tape capacity. Additionally, user-defined capacity for tape types is available in the report parameter selection UI. The report extrapolates out the trend line through the forecast period using classic linear regression and also plots the libraries capacity. At the date in which the library capacity line intersects the capacity forecast line is when the libraries capacity is reached.
Tape Devices-> Drive Throughput

This report shows the speed (KB/Sec) at which data backups flows through tape drives. The report uses the heat map concept and depicts ranges of speeds (slow to fast) through configurable shades of green. Reports are based on either Hour-Of-Day or Day-of-Week. Advanced averaging logic is used to determine the throughput values for each cell in the report. The averaging is done at an image fragment level ensuring granularity and precision in calculations. The reports can be aggregated and filtered at the Tape Library, Media Server, Drive Type, Logical Drive and Physical Drive levels. The sort options allow for intuitive presentation of voluminous data. These reports are important sources of information for performance analysis and capacity planning activities.
Tape Devices-> Drive Utilization

This report shows the utilization (0 100%) of tape drives. The report uses the heat map concept and depicts ranges of utilization (low to high) through configurable shades of blue. Reports are based on either Hour-Of-Day or Day-ofWeek. Advanced logic is used to determine the utilization values for each cell in the report. Utilization is calculated off a per minute basis knowing which job uses the ensuring precision in calculations versus traditional methods of periodic polling of the devices. The reports can be aggregated and filtered at the Tape Library, Media Server, Drive Type, Logical Drive and Physical Drive levels. The
504
sort options allow for intuitive presentation of voluminous data. These reports are important sources of information for performance analysis and capacity planning activities.
Tape Devices-> Library Summary

This report provides a current point in time inventory of library capacity. The reports list the libraries name, Volume DB Server, used/available/total slot count, and used or available or total capacity. There are two calculated columns showing the % utilization of slots and library capacity. The report provides a rich selection of filters enabling users with a diverse tape library environment to zoom in on any segment of their tape library population.
Media -> Tape Count -> By Volume Pool (Distribution)

This report shows the percentage of the media in each volume pool. You can also get the total count (rather than the percentage) of media by moving the mouse over the volume pool in the pie chart or the legend. Alternatively you can click on Show Table option to obtain the same information in the tabular format.
Media -> Tape Count -> By Retention Level (Distribution)

This report is a pie chart that shows the percent of backup media at each retention level. This can be used to easily identify if a large quantity of the backup media is committed for a long time suggesting a longer lifecycle due to possible regulatory compliance or highly important data. Infinite means that backup media is never used again for backups unless it is manually expired. If the actual value or count is desired it can be seen by placing the mouse over any of the colored sections in the pie chart or legend.
About catalog reports

This section describes catalog reports.
About cold catalog backup report

This report shows the count of cold NetBackup catalog backups and information about the media that NetBackup uses for offline backups. Tool tips in the bar chart show the report name and backup count. The table in the report also lists the media that NetBackup uses for the backups for each master server.
505
About chargeback reports

This section provides descriptions of OpsCenter chargeback reports.
About the Savings report

This report shows the savings that is achieved because of the deduplication technology. To generate this report, you need to have a cost variable of Protected Job Size. The deduplication technology can identify files and the data segments that contain identical data and treats them as a single instance of the file, which it backs up only once. For example, PureDisk has backed up 100-MB data , in which 20 MB of data is duplicate or identical. PureDisk protects the same data but eliminates the duplicity using deduplication. Therefore, the data that is protected is 100 MB, but the actual data that is backed up by PureDisk is 80 MB, as 20 MB of data is duplicate data. This results in saving 20 MB of data. You can generate the Savings report that shows the amount you have saved using deduplication. The Savings report is available in Distribution, Historical, and Ranking views.
About the Cost Tabular report

This 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 services they consume, which is called Chargeback. You can create cost variables and the formulas 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 report

This report shows the chargeback of your backup services in Historical and Ranking views. You need to have a cost formula created to generate this report.
About client reports

This section describes client reports.
About client restore report

This report provides restore job details for a specified client. The table in the report contains information, such as, master and media server names, and start and end times.
506
About clients not backed up report

This report provides a list of NetBackup clients that have not been backed up or clients having all backups fail during the reporting period. You can determine if all jobs of a policy and client combination have failed or have not been initiated during the reporting period. You can filter by type of policy like SharePoint, Oracle, Windows NT and so on. The client name is displayed multiple times in the report if the client has multiple NetBackup policies that are associated with it and none of the policies are run during the reporting period. The report shows details like policy name, schedule name, and date of the last successful backup.
About job success by client report

This report shows the rate of success for client jobs. The bar chart shows totals for successful, partially successful, and failed jobs for each client for the selected server or server group. Tool tips in the bars show these job counts. The tool tips for each client also include links to a drill-down report showing details for all job types. The table in the report summarizes job information (including the number of successful and partial successful jobs, and the job success rate). The table is organized 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 detailed reports.
About job details by client report

This drilldown report from the Client Name column or a bar chart tool tip lists all the jobs for the selected client and time frame. The table includes details such as, job type, exit status, and media server name. This drilldown report uses the run time parameters that are passed from the main report.
About successful job details for client report

This drilldown report from the Number of Successful Jobs column shows details for this job type for the selected client. This drilldown report uses the run time parameters that are passed from the main report.
507
About partially successful job details for client report

This drilldown report from the Number of Partial Successful Jobs column shows details for this job type for the selected client. This drill-down report uses the run time parameters that are passed from the main report.
About failed job details for client report

This drilldown report from the Number of Failed Jobs column lists the failed jobs for the selected client. Any jobs with an exit status other than 0 or 1 are considered to be failed jobs. This drilldown report uses the run time parameters that are passed from the main report.
About client summary dashboard report

This report summarizes several parameters for each client for the selected server context and acts as a dashboard of NetBackup activities. You can use drilldown links to view client detail reports for many of the columns in the table. The drilldown reports provide information about the client and answer the following 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 activities for your managed clients.
About total jobs for client report

This drilldown report from the Number of Total Jobs column lists all the jobs for the selected client and time frame. The job details include policy name, schedule name, and throughput (KB/sec). This drilldown report uses the run time parameters that are passed from the main report.
508
About successful jobs for client report

This drilldown report from the Number of Successful Jobs column lists the successful 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. This drilldown report uses the run time parameters that are passed from the main report.
About partially successful jobs for client report

This drilldown report from the Number of Partial Successful Jobs column shows the partially successful 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. This drilldown report uses the run time parameters that are passed from the main report.
About failed jobs for client report

This drilldown report from the Number of Failed Jobs column lists the failed jobs for the selected client and time frame. Any jobs with an exit status other than 0 or 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. This drilldown report uses the run time parameters that are passed from the main report.
About restore jobs for client report

This drilldown report from the Number of Restore Jobs column lists restore job details for the selected client. It provides details like policy name, schedule name, and throughput (KB/sec). This drilldown report uses the run time parameters that are passed from the main report.
About jobs by application report

This report uses the NetBackup policy type to simulate an application level report. For example, an Oracle policy type implies an Oracle application. The report then lets you see all Oracle backups. The table in this report organizes jobs in the table by server, client, and application and 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 respective application.
509
About job application details report

This drilldown report from the Application column lists all the jobs for the selected client 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. This drilldown report uses the run time parameters that are passed from the main report.
Virtual Client Summary

The Virtual Client Summary report shows details of all virtual clients of a NetBackup Master Server. Using this report, you can determine whether these virtual clients were backed up by NetBackup or not. Thus, you can report on the virtual clients that need to be protected. You can also drill down in this report to see the job details of a specific virtual client. The Virtual Client Summary report shows the following details:
Virtual Server Name Name of the virtual server host such as VMware or Hyper-V server Name of the proxy server host that provides details of the virtual clients to the NetBackup Master Server In case of a Hyper-V type of virtual server, the Backup Proxy Name is the same as the Virtual Server Name. Virtual Client Name Name of the virtual client running on a virtual server and which is connected to the NetBackup Master Server through a proxy server Virtual clients are the physical partitions of a virtual server, such as VMware or Hyper-V. Multiple virtual clients may have the same IP address. But they can be identified by their UUIDs. UUID is a unique identifier of a virtual client.
Backup Proxy Name
Note: Click the virtual client name link to view

its job details. UUID IP Address Type A unique identifier of the virtual client IP address of the virtual client Type of the virtual server that this client belongs to, such as VMware or Hyper-V
510
Server Name
Name of the NetBackup Master Server, which backs up this virtual client This field is shown blank if this virtual client is not backed up by any NetBackup Master Server
Exists in a Policy
This is a status field that describes whether backing up this virtual client is defined in any NetBackup policy or not If a NetBackup Master Server backs up this client, this field displays Yes. If it shows No, it means that this client should be backed up and be protected.
Last Backup Time
Time when this virtual client was backed up last This field displays NA (not applicable) if the client is not defined in a backup policy or it is yet to be backed up.
About Disk Based Data Protection

This section describes DBDP (disk based data protection) reports.
About license capacity report

This report shows the used capacity and licensed capacity information for NetBackup capacity-based licensed features in the form of a table. This report shows all of the capacity based licenses and the actual usage per disk type at your site. This report shows if you are in compliance with the license rules or if you need to purchase more licenses. This report can warn you about approaching license limit expiration. From the Feature Name column of the report table, you can drill down to view a report that shows the used capacity for your licensed capacity usage features. All capacity values for this report are calculated based on the definition that 1 terabyte=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 license usage for a selected feature. This drilldown report uses the run time parameters that are passed from the main report. This is a trending report which shows the used capacity and licensed capacity information for capacity-based license features in the form of a chart for a given time frame (for example, 14 days).
511
About current disk usage report

This report shows the master servers that have disk pools configured. It provides details about the disk pool usage and also how much free space is available in the disk pool.
About SAN client jobs report

This report shows all the jobs for selected Fiber Transport (FT) media servers and selected 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 reducing the throughput? A list of all the FT media servers A list of all the SAN clients.
About job reports

About partially successful job details report
This report provides details for all NetBackup partially successful jobs. Partially successful jobs have an exit status of 1. The table in the report is organized by job ID, server name, and client name.
About skipped files summary report

The information in this report is presented using a set of linked reports. The main report that is organized by master server, displays clients and policies, and the corresponding 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 client because of any skipped files. This drilldown report uses the run time parameters that are passed from the main report.
About skipped file details for policy report

This drilldown report from the Policy Name column identifies risks to the client due to any skipped files.
512
This drilldown report uses the run time parameters that are passed from the main report.
About skipped file details for policy and client report

This drilldown report from the No. of Skipped Files column provides the names of all skipped files. This drilldown report uses the run time parameters that are passed from the main report.
About backup window failures report

This report lists the jobs which were scheduled to run but failed because the scheduled backup window was no longer open (the NetBackup status code is 196).
About job summary by status report

This report summarizes NetBackup jobs based on the job exit status for a specified time interval. You can use this report to provide trend information. The bar chart shows a count of successful, partially successful, and failed jobs per a given date. The area chart shows the percent of jobs that failed each day.
About backup job size variance report

This report provides an indication of how a backup size varies from the average size. You can detect any anomalies if the variation is too high. This report calculates the backup size variation of the last good backup with the average backup size per a client, policy, and schedule type. If any variation calculation 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 - the average backup size) / the average backup size x 100. The Client Name column of the report provides a drilldown link to back up job details for the specified time frame.
About throughput variance report

This report provides an indication of how throughput (in MB per second) for a backup varies from the average throughput for a particular policy, client, and schedule type. You can detect any anomalies if the variation is too high.
513
This report calculates the backup throughput variation of the last good backup with the average backup throughput per a server, client, policy, and schedule type. If any variation calculation is greater than the selected value of variance when the report is run, the client, policy and schedule type combination is shown in the table with the actual variation. The Client Name column of the report provides a drilldown link to back up job details for the specified time frame.
About file count variance report

This report lets you investigate why a particular full backup is different than usual. For example, a file server backup is successful, but contains fewer files than usual for a full backup. The report shows NetBackup jobs with significant differences in file counts from the average count for a master server, policy, and schedule. If any variation calculation is greater than the selected value of variance when the report is run, the server, client, policy, and schedule type combination is shown with the actual file count variation. The table provides the percent variance (in file counts) for each good job from the average for that server, policy, and schedule. The Client Name column of the report provides a drilldown link to back up job details for the specified time frame.
About Backup duration variance report

This report provides an indication of how backup time varies from the average backup 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 the average backup time per client, policy, and schedule type. If any variation calculation 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 job information for the client for the selected time frame. This drilldown report uses the run time parameters that are passed from the main report.
514
About BMR client configuration backup failures report

If 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 more dependant jobs to back up the client data. This report shows all jobs that failed to completely back up a BMR client configuration, but their related child jobs (client data backup jobs) were partially or fully successful.
About job details report

This report provides detailed information about NetBackup jobs.
About restore job details report

This report provides details for restore jobs. The table in the report is organized by job ID, master server name, and client.
About job exit status detail report

This report provides information about the completion status for a NetBackup job. The report table provides a count of jobs having a particular exit status on a particular 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 the main report shows job details, such as job type and policy name. The table includes all jobs having a particular exit status on a given day. This drilldown report uses the run time parameters that are passed from the main report.
About media reports

This section describes media reports.
About media state report

This report displays the media status and count (per media type) for each master server and media server combination. Media state can be frozen, active, offsite, and so on.
515
About available media report

This report lists the media that is available for use by NetBackup for each master server that is selected. The report table provides information, such as, media server, media status, robot type, volume group and pool, and the time assigned.
About drives in use report

This report shows the drive usage for the selected server. The report table provides details for the drive, for example, drive name and type, robot number and type, and assigned host.
About full media capacity report

This report shows the average amount of protected data (in kilobytes) on a tape for each master server and media type. These are the tapes that NetBackup marked as 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 size and number of images on the tape.
About media summary by media server report

For each media server, this report provides the number of tapes and images, the last written date, and amount of data on the tapes. The name of the media server is 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 status summary for a selected media server. This report displays media status, number of tapes and images, the last written date, and amount of data on tapes. This drilldown report uses the run time parameters that are passed from the main report.
About media details of media status for a media server report

This drilldown report from the Media Status column provides media details for the selected media server and selected media status. Media status can be Active, Frozen, Full, Invalid, or Suspended. This drilldown report uses the run time parameters that are passed from the main report.
516
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 report

The stacked bar chart in this report shows the number of media in use for a server per 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 media state. The data for this report is only calculated once in a day. So the report shows the summary till the previous date. The data for today reflects in the report that you generate tomorrow. The table in the report is organized by date and server, and shows counts for each media state.
Media -> Tapes expiring Now

This report lists the media that are about to expire. The Volume Pool Name , Media ID, and Media Barcode listed make it easy to locate the media. The default time frame when the report is clicked will show what is expiring in the next 24 hours but that time frame can be changed to show media expiring in the next week, month or any future time window desirable.
Media -> Tapes Expiring in Future

Similar to the previous report but at a higher level this shows the number of media that expire at each day in the upcoming 7 days. This time frame can be changed to show more in to the future. The report is helpful in determining if a large quantity of media may become free in the future which could justify delaying the purchase of more media.
About media expiration schedule report

This report gives graphical representation of the expiration schedule for media. The report predicts the availability of media based on the expiration date of the media. 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 expired on a particular day. Different colors are used in the bars for the different media types. Tool tips for the bar segments provide the media type and count of the media that is available on that day.
517
About performance reports

This section describes performance reports.
About storage unit usage report

This 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 storage unit name is also a drilldown link to a detailed report. The media server name in the second column is also a drilldown link. The rest of the row provides details such as, total number of jobs, total volume processed (KB), average throughput (KB/sec), duration of activity and percentage of 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. This drilldown report uses the run time parameters that are passed from the main report.
About storage unit usage details for media server report

This drilldown report from the Media Server Name column shows the usage details for all of the storage units of the selected media server. This drilldown report uses the run time parameters that are passed from the main report. The Storage unit column of the report table is a link to a drilldown throughput report. The rest of the cells indicate whether the storage unit was in use or not during the time slot.
About master server job throughput report

This report provides a tool to compare performance of various master servers. The pie chart displays the breakdown of jobs that are run across the selected master servers. A drilldown detail link from each server pie slice for job details is provided. The table of this report displays throughput and job success information for each server in the selected server context. It shows job count and job success rate, and enables you to compare throughputs of different servers to identify any servers that are performing poorly.
518
Drilldown links for the server name, number of total and successful jobs columns are also provided.
About total jobs of a server report

This drilldown report from the pie chart or Number of Total Jobs column lists the details for all jobs for a selected server. The report details includes details like job type and status, policy and schedule names, and start time. This drilldown report uses the run time parameters that are passed from the main report.
About job details for client and master server report

This drill-down report from the client name column provides details for a given client, job type, and job status. The report details include exit status, start time, duration in seconds, volume in KB, and throughput. This drilldown report uses the run time parameters that are passed from the main report.
About successful jobs of a server report

This drilldown report from the Number of Successful Jobs column shows details for successful jobs for a given server. The report provides details like job type, policy and schedule names, volume, and file counts. This drilldown report uses the run time parameters that are passed from the main report.
About media server job throughput

This report provides details of data that is backed up by NetBackup media servers and shows server throughput. It is a useful tool to compare performance of the media servers that are present in your NetBackup environment. The pie chart provides a breakdown of the volume of data that is processed for each media server. A drilldown detail link for throughput details is provided from each volume pie slice. The table in the report shows the throughput of all the media servers present in the selected server context. You can compare the load on each media server present in the environment. The table also contains drilldown links to detail reports for the media servers and their throughput.
About job summary by client for media server report

This drilldown report from the Media Server column lists all the jobs for each client that is associated with the server.
519
This drilldown report uses the run time parameters that are passed from the main report. In the report, the first cell in each row represents the client name. This name is also a drilldown link to a detailed report for the client and the media server. The other cells in a row indicate the details for each job. The color of each cell indicates job schedule type (for example, full or incremental) and unique icons indicate the job exit status and job type. The tool tips for each icon also show client name, schedule type, job type, day on which the job run, and backup size.
About job details for client and media server report

This drilldown report from the client name column provides details for a given client, job type, job status, and media server. The report details include job ID, job type, exit status, start time, and duration in seconds. This drilldown report uses the run time parameters that are passed from the parent report.
About media server throughput for media server report

You can use this drill-down report from the Throughput (KB/sec) column to see the variation of throughput per day. The throughput is represented by a bar for each day of the reporting period. This drill-down report uses the run time parameters that are passed from the main report.
About disk usage report

This report shows disk usage for the selected server and time frame. The table in the report provides details such as, total number of jobs, total volume processed (KB), average throughput (KB/sec), duration of activity, and percentage utilization in terms of duration. The Disk and Media Server Name columns of the table contain drilldown links to detailed 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. This drilldown report uses the run time parameters that are passed from the main report.
520
About disk usage details for media server report

This drilldown report from the Media server Name column shows the usage details for all the disk storage units for the selected media server. This drilldown report uses the run time parameters that are passed from the main report. The Disk cell in each row of the report table is a link to a drill-down report. The rest of the cells indicate whether the disk was in use or not during the time slot.
About policy reports

This section describes policy reports.
About top 10 policies using most server space report

This report displays the 10 policies that have backed up the most data in your NetBackup environment. Since the report is based on the server context selected it is possible to get information for each individual managed server or for a group of servers. Drilldown links from the bar chart (tool tips) and the table in the report provide details 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, and volume of data.
About job details for a policy report

This drilldown report from the Policy Name column and the colored bars in the chart provides details about all jobs for a selected policy name. This drilldown report uses the run time parameters that are passed from the main report. The table includes information, such as, job type, exit status, client name, and volume in KB.
About job success rate by policy type report

This report provides a quick view of the status of jobs by policy type. The report shows the job success rate for clients, server, and job policy type. The bar chart shows the count of successful, partially successful, and failed jobs per policy type. The tool tips in the colored bars provide job counts and also are drilldown 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.
521
Note: This report may not show appropriate data for duplication jobs that are associated with SLP policy. This is because the duplication jobs do not have a policy type. The job batches duplication of images that are created from possibly different policies and policy types. The duplication job itself has an internal policy that is created but this internal 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 the chart provides details about all jobs for a selected policy type. This drilldown report uses the run time parameters that are passed from the main report. 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 type report
There are three drilldown reports from the Number of Successful Jobs, Number of Partially Successful Jobs, or Number of Failed Jobs columns. The job exit status is used as a filter for the reports. These reports are similar and provide details for all jobs for a selected client and policy type. This drilldown report uses the run time parameters that are passed from the main report. The table in this report provides details like, policy and schedule name, start and end times, and duration for the job. The table for failed jobs also includes a column for the job exit status.
About policy change report

This report shows a count of the changes that were made to job policies in a given time frame for the selected servers. The pie chart shows the number of policy changes (a policy can change multiple times) for each master server. (Each different server appears in a different color in 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 policy for each server.
522
About policy summary dashboard report

This report acts as a dashboard of NetBackup activities that are summarized by your policies. It gives an overview of activities and can be used as a tool to troubleshoot and manage by exception using the drilldown links to other detail reports. 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 down from the job exit status counts in the columns and view individual policy details based on exit status and job policy and type.
About drilldown reports

These drilldown reports from the Total Jobs, Successful Jobs, Partial Jobs, or Failed Jobs columns provide an overview of all jobs for the selected policy name, server, and time frame based on the job exit status. This drilldown report uses the run time parameters that are passed from the main report. The table provides details like schedule name, start times, and duration of the job.
About vault reports

This section provides descriptions of vault reports.
About vault media usage report

This report shows offsite media trends for selected vaults and current offsite media count. The report consists of two component reports, a line chart and a table. 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?
523
The line 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 this report. The report shows a weekly line trend for selected vault. This chart is a good indication of how the offsite media count varies over the period of time. You can compare the media counts of different vaults to see which vault is consuming more media and how it is varys. 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 provides important media details like media ID, offsite slot number, container ID, expiration date, bar code, and so on.
524
Appendix
About additional information on PureDisk 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
About AT configuration scenarios specific to PureDisk backup product

This section describes various configuration scenarios for Symantec Product Authentication Service (AT) that you should take into account before configuring PureDisk data collector. On a broader level, there can be two types of OpsCenter - PureDisk setups with respect to their AT root broker configurations:
Common AT root broker for OpsCenter server and PureDisk SPA See Scenario 1: Common Root Broker on page 526. Different AT root broker for OpsCenter server and PureDisk SPA
526
About additional information on PureDisk data collection About AT configuration scenarios specific to PureDisk backup product
Note: In this type of configuration, you need to set up a bi-directional trust between the OpsCenter AB host and PureDisk SPA host. You need to establish trust between the authentication brokers of OpsCenter and PureDisk SPA for secure communication. This set up is a pre-requisite for PureDisk data collection from OpsCenter. See Scenario 2: Different Root Brokers on page 527.
Scenario 1: Common Root Broker

This section talks about all scenarios where the AT root broker is common for OpsCenter server as well as PureDisk SPA. Figure A-1 describes a scenario where the AT root broker is configured on the PureDisk SPA host and OpsCenter server points to the same root broker. Thus for both product hosts, the AT root broker is common. You do not need to carry out any additional steps for PureDisk data collection. Figure A-1 Common root broker - root broker on PureDisk SPA
AT hierarchy Host B: PureDisk SPA AT Root Broker + Authentication Broker
Host A: OpsCenter Server AT Authentication Broker
Data collection
Figure A-2 describes a scenario where the AT root broker is configured on the OpsCenter server host and PureDisk SPA points to the same root broker. Thus for both product hosts, the AT root broker is common. Figure A-2 Common root broker - root broker on OpsCenter Server
AT hierarchy Host B: PureDisk SPA AT Authentication Broker
Host A: OpsCenter Server AT Root Broker + Authentication Broker
Data collection
Figure A-3 describes a scenario where the AT root broker is configured on the Host C and OpsCenter server host and PureDisk SPA point to this remote root broker. Thus for both product hosts, the AT root broker is common.
527
Figure A-3
Common root broker - root broker on a remote host
Host C: AT Root Broker AT hierarchy Host A: OpsCenter Server AT Authentication Broker AT hierarchy Host B: PureDisk SPA AT Authentication Broker
Data collection
Scenario 2: Different Root Brokers

This section talks about all scenarios where the OpsCenter server and PureDisk SPA 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 the PureDisk SPA host. This set up is a pre-requisite for collecting PureDisk data from OpsCenter.
Note: Setting up trust between the PureDisk SPA host and OpsCenter AB host is a manual process. Refer to the Setting up a trust between PureDisk SPA host and OpsCenter AB host section. Setting up trust between the OpsCenter Authentication Broker host and PureDisk SPA 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 529.
Root brokers on local hosts

Figure A-4 describes a scenario where the OpsCenter server and PureDisk SPA use the AT root brokers that are configured on their respective hosts.
528
Figure A-4
Different root brokers - root brokers on local hosts

Host B: PureDisk SPA AT Root Broker + Authentication Broker
Host A: OpsCenter Server AT Root Broker + Authentication Broker
Data collection
Note: If you have this kind of configuration, you need to set up a trust between the two root broker hosts, that is between Host A and Host B.
Root brokers on remote hosts

Figure A-5 describes a scenario where the OpsCenter server and PureDisk SPA use the AT root brokers that are configured on two remote hosts. Figure A-5 Root brokers on remote hosts
Host C: AT Root Broker
Host D: AT Root Broker
AT hierarchy
Host A: OpsCenter Server AT Authentication Broker
Data collection
Host B: PureDisk SPA AT Authentication Broker
Remote root broker for OpsCenter server and local root for PureDisk
Figure A-6 describes a scenario where the OpsCenter server uses remote root broker and PureDisk SPA uses local root broker.
About additional information on PureDisk data collection Setting up a trust between the OpsCenter AB host and PureDisk SPA host
529
Figure A-6
Remote root for OpsCenter server and local root for PureDisk
AT hierarchy Host A: OpsCenter Server AT Authentication Broker Host B: PureDisk SPA AT Authentication Broker
Data collection
Local root broker for OpsCenter server and remote for PureDisk
Figure A-7 describes a scenario where PureDisk SPA uses remote root broker and OpsCenter server uses local root broker. Figure A-7 Local root broker for OpsCenter server and remote for PureDisk
AT hierarchy Host A: OpsCenter Server AT Authentication Broker Host B: PureDisk SPA AT Authentication Broker
Data collection
Setting up a trust between the OpsCenter AB host and PureDisk SPA host
This section provides the steps that are required to set up trust between the OpsCenter AB (authentication broker ) host and PureDisk SPA host. Note: OpsCenter AB host is the host where the OpsCenter server is installed. If OpsCenter is installed in a clustered mode, the OpsCenter AB host is the host name that was provided as the remote AB host during the OpsCenter installation.
530
About additional information on PureDisk data collection Setting up a trust between the OpsCenter AB host and PureDisk SPA host
Note: Trust setup between the OpsCenter AB host and PureDisk SPA host is automatically 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 steps as follows. 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 the OpsCenter server operating system : These are the default directory paths.
Windows 32-bit C:\Program Files\VERITAS\Security\Authentication\bin\vssat setuptrust --broker <PureDiskSPAhost:port> --securitylevel high C:\Program Files (x86)\VERITAS\Security\Authentication\bin\vssat setuptrust --broker <PureDiskSPAhost:port> --securitylevel high /opt/VRTSat/bin/vssat setuptrust --broker <PureDiskSPAhost:port> --securitylevel high
Windows 64-bit
UNIX
The registered port for authentication is 2821. If the AT root broker is configured with another port number, contact your security administrator for more information. After successfully setting up a trust between the OpsCenter AB host and PureDisk SPA host, the following message is displayed:
setuptrust ------------------------------------------Setup Trust With Broker: PureDiskSPAhost
Appendix
Attributes of NetBackup data

This appendix includes the following topics:
About backup data attributes
About backup data attributes

This section lists all attributes pertaining to data that OpsCenter collects from NetBackup. You can select these attributes while generating custom reports. Table B-1 lists all NetBackup attributes that OpsCenter collects. Table B-1 Data Attributes
Backup Job Attributes Agent Server host.symantec.com The name of the server where a Backup Reporter data collection agent is installed Filled in by the user in the Job Reconciliation page to indicate why a job failed so others can see.
NetBackup data attributes Sample Data Explanation
Backup job Comment
Host cannot be reached
532
Attributes of NetBackup data About backup data attributes
Table B-1 Data Attributes
NetBackup data attributes (continued) Sample Data

321
Explanation
The deduplication file factor for each PureDisk backup job. Meaning that for every 321 files that were backed up only one file was actually stored. (321 to 1 file deduplication rate) The number of files not needing to be backed up for every backup job in PureDisk because they were already stored with deduplication. Meaning that if 500 files were targeted for backup, only 44 were stored since the saving was 456. Within Backup Reporter there is the ability to mark a job as ignored (yes/no). If it is ignored it does not count towards things like success rate or time since last successful backup. This marking of a job as ignored is done in the "Reports > Explorers" section. The number of files that are processed in a PureDisk backup. Note that this number is not actually stored since it is before deduplication. The size in byes of a PureDisk backup job before deduplication.
Backup job File Count Deduplication Factor
Backup job File Count 456 Deduplication Savings
Backup job Is Ignored
Yes/No
Backup job Protected File Count
400 files
Backup job Protected Size
200GB
533

567
Explanation
The deduplication size factor for each PureDisk backup job. Meaning that for every 567KB that were backed up only 1KB was stored. The number of KB's not needing to be backed up for every backup job in PureDisk because they were already stored with deduplication. Meaning that if 346KB were backed up, the savings of 345KB means only 1 KB was needed to be stored. Each directory under a job and it's type of backup. The transport that was used to move the backup from backup client to media server The number of times a backup job had to be attempted before being successful or reaching the maximum allowable number of retries The name of a host being backed up as seen by a backup job The file system directory being backed up as seen by a backup job
Backup job Size Deduplication Factor
Backup job Size 345 Deduplication Savings
Backup job Sub Type
Catalog, File System, MS Exchange, NDMP, Sybase
Backup job Transport Type
LAN, SAN
Job Attempt Count
Job Client
backup-client.symantec.com
Job Directory
C:\, /var, ALL_LOCAL_DRIVES
534

Job Duration

300 seconds
Explanation
The amount of time in seconds for a backup to start and finish as seen by a backup job The date and time that a backup ended The exit code, status code, or error code for a particular job The time at which this job (the image that the job generates) will expire. The number of files a backed up during a backup job The group ID that the product group specifies. Note:The secondary ID and the Group ID are intended for the same purpose. These IDs group the jobs in some way that is useful in reporting.
Job End Time
Tues 3/23/2008 03:34:43
Job Error Code
0,1,2,3
Job Expiration Time
Aug 01, 2008 22:03:48
Job File Count
300
Job Group ID
6114
Job Level
Full, Differential Incremental, User Backup
The Schedule Type for the backup job, Full, Incremental, Cumulative, User etc. A unique number for each backup job in a backup domain that identifies a backup job
Job Primary ID
5,234,234
535

Job Secondary ID

5,234,235
Explanation
When a unique job number is not enough to distinguish a job, a secondary ID may be used. For NBU, this field is the job Process ID The amount in KB that a backup job transferred from client to media server for backing up The date and time that a backup started A percent number that is calculated based on the number of jobs that were successful (NetBackup status 0) and partially successful (NetBackup status 1) divided by the total number of jobs ran in that period of time. Example: 98 successful jobs / 100 total jobs (2 failures) = 98% A percent number that is calculated based on the number of jobs that were successful (NetBackup status 0) divided by the total number of jobs ran in that period of time. Example: 98 successful jobs / 100 total
Job Size
2048
Job Start Time
Tues 3/23/2008 02:34:43
Job Success Rate 98 (Complete and partial)
Job Success Rate (Complete only)
99
536

Job Throughput (Kbytes/sec)

3,234
Explanation
The speed of a backup job in Kbytes/sec. This is the speed of the overall job which takes in to account transfer time from client to media server and media server to disk or tape storage. It is not just the speed of a tape drive. The type of operation done by the backup product The Schedule Type for the backup job grouped into just two options. Full vs. Other The name of the master server that executed the backup job The name of the media server that performed the backup job The name of the backup policy as seen by a backup job The name of the backup policy as seen by a backup job
Job Type
Backup, Restore, duplication, archive, label, erase
Level Type
Full, Differential Incremental, User Backup
Master Server
nbu-master.example.com
Media Server
nbu-media.example.com
Policy
Oracle Backup Policy, User Backup Policy, File System Backup Policy
Policy Description
Policy Description
This policy is for doing Oracle backups The user-defined description of a policy as seen by a backup job NetBackup Policy Domain, PureDisk Policy Domain The backup product that a backup policy executed a job from
Policy Domain Name
537

Policy Type
NetBackup data attributes (continued) Sample Data Explanation
Standard (UNIX), Windows-NT, Oracle, The type of policy as Exchange seen by a backup job NetBackup, PureDisk, TSM The backup product that performs backup, from which OpsCenter collects data The name of a schedule which resides within a policy as seen by a backup job A word description for each job that coorelates status codes to their english meaning. All failures are mapped to the word Failure The name of a storage unit which is choosen by a policy to receive and store backups. Storage Units are usually groupings of tape drives within a library or multiple disk locations that are grouped together in pools. This is the storage unit name that was used by a backup job and therefore may or may not exist in present time. The type of storage unit used and seen by a backup job
Product
Schedule
(user-defined), ex: Weekly-Fulls, Daily-Incrementals
Status
Success, Partial, Failure
Storage Unit Name
(user-defined), ex: tld0-hcart-0
Storage Unit Type
Disk, Media Manager (tape)
Job Scheduled Time Window Closing Time Job Execution Type
538

Original Job ID
Backup Image Attributes Backup Image Compression State Yes/No A yes/no property of if a backup image stored in the catalog was compressed or not. The date/time that a backup image copy is set to expire A yes/no property of if a backup image is expired or not. If it is expired it can no longer be restored and that space may be rewritten to by the backup application. If it is not expired it is available for restore. A yes/no property of if a backup image is the primary copy. If the image is a 2nd or greater copy this value would be no. The name of the backup server that performed the copy of a backup to a second location. A true/false property as to if the backup image copy was written using multiplexing or not (multiple clients/jobs streamed to one image)
Backup Image Copy Expiration Time
Mon 4/23/2008 4:32:34
Backup Image Copy Is Yes/No Currently Expired
Backup Image Copy Is Yes/No Primary
Backup Image Copy Media Server
backup-server.symantec.com
Backup Image Copy Multiplexed State
True/False
539

Media Manager (tape), Disk
Explanation
The type of storage unit that the backup image was copied to. This could be disk, tape etc. The number of fragments that make up a complete unexpired backup. A single backup can have 1 or a multiple of fragments which are blocks of data seperated by tape marks on tape or seperated in to separate files on the file system if written to disk. A unique ID or key for every backup stored in the catalog. This key or ID can be used to look up an image in the catalog for restore or other activity A yes/no property of if a backup image was encrypted between the backup client and backup media server. This value does NOT represent if tape drive or other encryption was used or not. The date and time that a backup image will expire. When a backup image expires it is no longer available for restore and the space that the backup occupied can be reused for additional backups (overwritten)
Backup Image Copy Storage Unit Type
Backup Image Copy Unexpired Fragment Count
30
Backup Image Copy Unique ID
backupclient_23423
Backup Image Encryption State
Yes/No
Backup Image Expiration Time
Mon 4/23/2008 4:32:34
540

Backup Image File Count

432
Explanation
The actual number of files that are stored within a backup image. The date/time that the backup image fragment is set to expire A yes/no property of if the backup image fragment is expired or not. Even if a backup fragment is expired, that space can not be reused until the whole backup image is expired (disk) or the whole backup tape media is expired (tape) The true image restore status for a backup image fragment. True image restores allow a restore to take place at the directory level without overwriting files that weren't backed up but are still in the directory. For this to be possible a true image restore backup image must exist. The size of the backup image fragment. By default NetBackup uses 1TB fragments (ie no fragments) but this can be configured to different values A unique ID associated with every backup image fragment
Backup Image Fragment Expiration Time
Mon 4/23/2008 4:32:34
Backup Image Yes/No Fragment Is Currently Expired
Backup Image Fragment Is TIR
TIR Info on Disk, TIR Rsv Synthetic Info on Disk
Backup Image Fragment Size
2048
Backup Image Fragment Unique ID
backupimagefragment_124
541

Backup Image Is Currently Expired

Yes/No
Explanation
A yes/no property as to if the backup image is expired or not The true image restore status for a backup image. True image restores allow a restore to take place at the directory level without overwriting files that weren't backed up but are still in the directory. For this to be possible a "true image restore" backup image must exist. The type of backup image. Catalog being a NBU catalog image for disaster recovery The number of copies that exist for a primary backup image. These are copies that are unexpired and can be used for a restore. A unique ID or key for every backup stored in the catalog. This key or ID can be used to look up an image in the catalog for restore or other activity The date and time that the backup image was finished writing. The date and time that the backup image began to be written.
Backup Image TIR Status
TIR Info on Disk, TIR Rsv Synthetic Info on Disk
Backup Image Type
Regular, Catalog
Backup Image 1, 2, 3 etc. Unexpired Copy Count
Backup Image Unique backupclient_23423 ID
Backup Image Write End Time
Mon 4/23/2008 4:32:34
Backup Image Write Start Time
Mon 4/23/2008 4:32:34
542

Data Classification Master Server

master-server.symantec.com
Explanation
The name of the server that classified the backup image in some sort of ranking (gold, silver, bronze etc) The name of the classification of data The number ranking that corresponds with the name of data classification. A 1 would mean the data is more important than a 2 for example.
Data Classification Name Data Classification Rank
Gold, Silver, Bronze, Non-DataClassification-Name 1,2,3,etc
Backup Attempt Attributes Attempt Duration 3500 The number in seconds that a backup was attempted The number in seconds that a backup was attempted The date and time that a backup attempt ended (each attempt is unique) The error code that the backup attempt finished with The number of files the backup attempted to process The number in KB for the amount an attempted backup tried to process The start time that a backup attempt began
Attempt Duration
3500
Attempt End Time
Mon 4/23/2008 4:32:34
Attempt Error Code
0, 1, 2, 3 etc.
Attempt File Count
0, 1, 2, 3 etc.
Attempt Size
2048
Attempt Start Time
Mon 4/23/2008 4:32:34
543

Attempt Status

Success, Partial, Failure
Explanation
A named status that maps to the error code numbers in the backup application (for example a status 0 in NetBackup is a success, a status 1 is partial and all other numbers are failures) The average success rate across all attempts in all backups. Example would be the average of 2 backups were each was attempted 3 times. The success rate would be the success rate average of the 3 attempts within each backup job. (Note that this is different than the success rate across all jobs which does not take in to account attempts) The speed of a backup attempt in Kbytes/sec. This is different than the overall KB/sec for a job which would take in to account all attempts.
Attempt Success Rate 98%
Attempt Throughput
2048Kbytes/sec
544

98%
Explanation
The average success rate across all attempts in all backups but also including partial successes (status 1 in NetBackup). Example would be the average of 2 backups were each was attempted 3 times. The success rate would be the success rate average of the 3 attempts within each backup job. (Note that this is different than the success rate across all jobs which does not take in to account attempts) The attempt number in a sequence. 1 would represent the first attempt, 2 would represent the second attempt etc. The date and time that a particular file was skipped over during a backup The status code for why that file was skipped (usually a status 1) The reason a file was skipped. (Usually because file was in use) The actual file name that was skipped over during a backup.
Backup Attempt Partial Success Rate
Backup Attempt Sequence
1, 2, 3
Backup Skipped File Time
Mon 4/23/2008 4:32:34
Skipped File Code
Skipped File Reason
File is open by another process
Skipped File Name
C:\Windows\an_open_file.dll
Backup Policy Attributes
545

The host name of the backup application host that contains the backup policy. In the case of NetBackup this is the master server. The name of a backup policy that exists in the backup application. Note that this is similar and can be the same as the backup job Attribute: Policy which shows what policy the backup job was executed from. It is different though since this Policy Name simply means that this Policy exists not that anything was executed from it yet.
Backup Policy Domain nbu-master.example.com Master Server
Backup Policy Name
Backup Policy Type
Standard (UNIX), Windows-NT, Oracle, The type of backup Exchange policy that exists in the backup application. Note that this is different than the backup job Attribute: Policy Type
Data Classification Name Policy Storage Unit / Lifecycle policy Policy Volume Pool Job Priority Active Effective Date Backup Network Drives
546
True Image Recovery Compression Encryption Allow Multiple Data Streams Block Level Incremental Perform Snapshot Individual File Restore From Raw Virtual Machine Proxy Multiple copies Override policy storage selection Override policy volume pool Override media owner Multiplexing Fail all Synthetic Disk Only File System Attributes Business Classification Business Critical User defined field. Can be one of Mission Critical, Business Critical or Business Support
547

File System: OID

asset123 etc.
Explanation
A user defined field for an object ID of the file system. Typically used as a pairing with an asset management database
Filesystem Name
C:\Documents and Settings\All Users\ The file system directory being backed up. NTFS, UFS, ZFS, EXT3 A user-defined field (this is not collected automatically) of what type of file system was backed up.
Filesystem Type
Host Attributes Host Architecture SPARC, x86 User defined field (this is not automatically collected) for filling in architecture type such as x86, x86-64, SPARC, POWER, PA-RISC, IA64 etc A user defined field for inserting any extra information regarding a host A user defined field for inserting an object ID from an asset management database The name of the host object that contains file systems.
Host: Misc Info
Pete's server
Host: OID
asset123, etc.
Hostname
hostname.example.com
548

O.S. Version

2003, 10
Explanation
The version of the operating system. Usually grouped with Operating System name since this will have values like 10 (i.e. Solaris 10), or 2003 (i.e. Windows 2003) The operating system name of the host
Operating System
Windows, Solaris
Backup Media Attributes Agent Server ops-agent.example.com The name of the OpsCenter agent that collected the media information. The date/time that a piece of media was first allocated or had it's first backup written to it. Once the media expires it will have a new allocation date/time when it is reused How much is left on tape in KB. Value here per sample is either the free capacity if the media is active, or 0 otherwise. Total capacity of the tape in KB. Value here per sample is either the total capacity if the media is active, or 0 otherwise. The full barcode as ready by the physical robot. This can be longer than the 6 characters used by a NetBackup Media.
Backup Media Allocation Time
Mon 3/4/2008 3:34:34
Backup Media Available Free Capacity
500,000 KB
Backup Media Available Total Capacity
19,000,000KB
Backup Media Barcode JFP000L2
549

Backup Media Expiration Time

Mon 3/4/2008 3:34:34
Explanation
The date/time that a backup media is set to expire How much is left on tape in KB. This number may be estimated using an algorithm. A yes/no property of a particular tape indicating whether the tape has been sampled in the last two collections. A yes/no property of a particular tape indicating whether it can still be written to. A yes/no property of if the backup media exists in the current configuration (and not historical) A yes/no property of if the backup media has expired data on it or not A yes/no property of if the backup media is marked as full (no more backups can be written to it)
Backup Media Free Capacity
500,000 KB
Backup Media Is Active Yes/No
Backup Media Is Available
Yes/No
Backup Media Is Current
Yes/No
Backup Media Is Data Expired
Yes/No
Backup Media Is Full
Yes/No
550

Backup Media Is Imported

Yes/No
Explanation
A yes/no property of if the backup media was imported. Imported media simply means that this paticular backup domain did not originally write the data to the media. This could be due to disaster recovery where the catalog could not be moved from an existing domain so the tapes were read individually to determine what data was on them. It also is commonly used to import Backup Exec media to NetBackup. A yes/no property of if the physical media is expired or not. Once all the backup images (data) has been expired on a tape that entire cartridge is marked as Physically Expired=Yes and it can be overwritten or used by future backups. Since capacity of a tape is often estimated using an algorithm. This specifies whether it was actually calculated, or provided exactly by the DP product. A date/time that the backup media was last used to be read (restored)
Backup Media Is Physically Expired
Yes/No
Backup Media Is Total Yes/No Capacity Estimated
Backup Media Last Read Time
Mon 3/4/2008 3:34:34
551

Backup Media Last Write Time

Mon 3/4/2008 3:34:34
Explanation
A date/time that the backup media was last used to be written to (duplicates, backups) The physical slot number that a given piece of media resides in A yes/no property of if a given piece of tape media will allow for multiple expiration dates. Multiple expiration dates means that the whole tape can not be reused until the last backup has expired on the media. A yes/no property of if multiplexing is allowed on a piece of tape media. Multiplexing means that multiple clients were multiple clients or jobs were backed up to one image so that particular image could have more than one client inside it. Calculated value representing (available free capacity /available total capacity ) in percentage Calculated value representing (free capacity total capacity ) in percentage
Backup Media Library 1, 2, 3 etc. Slot Number
Backup Media Multiple Yes/No Retention Levels Allowed
Backup Media Multiplexing Allowed
Yes/No
Backup Media Percent 0-100% Available Free Capacity
Backup Media Percent 0-100% Free Capacity
552

Calculated value representing (used capacity / total capacity) in percentage The date/time that a piece of media will physically expire (all images on the media) and be able to be reused
Backup Media Percent 0-100% Used Capacity
Backup Media Physical Mon 3/4/2008 3:34:34 Expiration Time
Backup Media Retention Level
63072000.00, 31536000.00, 1209600.00 The retention level of the media in number of seconds. Divide by 86400 to get the retention level in days Mon 3/4/2008 3:34:34 The date/time that all the media information was collected from the backup application to OpsCenter. History is kept so a history of the state of all media can be determined. The type of storage for a given piece of media (disk or tape) Total capacity of the tape in KB. This number may be estimated using an algorithm. The density or type of media. This is used to match what drives the media can go in for a mixed media environment. The number of images that are unexpired on a given piece of media
Backup Media Snapshot Time
Backup Media Storage Disk, Tape Type
Backup Media Total Capacity
19,000,000 KB
Backup Media Type
HCART, DLT, 8MM etc.
Backup Media Unexpired Image Count
1, 2, 3 etc.
553

500,000 KB
Explanation
Amount in KB used up in the tape. This value is provided by the DP product and is NOT estimated.
Backup Media Used Capacity
Backup Media Volume User defined but defaults to things like A user defined field for Group Name 000_00002_TLD grouping volumes. By default NetBackup assigns the robot number and type so that TLD(2) would read 000_00002_TLD Backup Media Volume /disk_staging_file_system/, Path C:\disk_staging\ The path on disk where backup images are stored. Specific to NetBackup 6.5 - this is the high water mark that is set for a Flexible Disk pool, OpenStorage disk pool or PureDisk backend storage pools. When this threshold is reached by the file system on the disk pools backups will not be attempted to that disk location since it will be considered full. Specific to NetBackup 6.5 - this is the low water mark that is set for a Flexible Disk pool, OpenStorage disk pool or PureDisk backend storage pools. When this threshold is reached by the file system on the disk pools backups will not be sent to the location as often
Disk Pool High Water Mark
95%
Disk Pool Low Water Mark
80%
554

Disk Pool Master Server

Explanation
The name of the NetBackup master server that the disk pool belongs to The name of the disk pool which defaults to the disk array string or a user defined value The raw size is the size of the disk volume(s) in a disk pool. Raw size does not mean you can actually write to that amount (that's what usable size is) but just tells you there is more possible disk space that could be allocated from raw to usable. The type of flexible disk that the pool is The date/time that a snapshot was taken to produce the backup image that exists in the disk pool Similar to tape drive status, this tells if the disk pool is UP meaning it is usable and can be used or DOWN meaning it is not usable. When in the DOWN state jobs will not attempt to use the disk pool.
Disk Pool Name
netappfi::fas3050-1a, DDPool, etc.
Disk Pool Raw Size
69,990.40
Disk Pool Server Type AdvancedDisk, SharedDisk
Disk Pool Snapshot Time
Mon 3/4/2008 3:34:34
Disk Pool Status
UP, DOWN
555

1,208,893.44
Explanation
The usable size is the size of the formatted file system and tells you how much data can be written to the disk pool The number of disk volumes that make up the disk pool The type of tape media as defined by the backup application. For NetBackup this is also called the density and specifies what types of drive the tape can go in. Optical media header size of a backup image The Media ID for a given piece of media, usually a subset of the barcode. For NetBackup this is a 6-digit ID. The number of backup images on a given piece of tape media or disk pool Logical block address of the beginning of the block that a backup image exists The number of times a given piece of backup media has been used for restores. Optical media sector size of a backup image.
Disk Pool Usable Size
Disk Pool Volume Count
Media Density
HCART, DLT, 8MM etc.
Media Hsize
1024
Media ID
JFP000
Media Image Count
54
Media L Offset
2048
Media Restore Count
0, 1, 2, 3, etc.
Media Ssize
1024
556

Partner

A/B
Explanation
The ID of the opposite side of a optical platter. If on side A of a platter this would show Side B The backup product that this piece of media belongs to
Product
NetBackup, TSM
Status
Active, Non-active, Suspended, Frozen The status of a given piece of media. Active meaning it is being used at a given point in time, Frozen meaning errors have occurred on the tape media and it is no longer being used for backups, etc. 1, 2, 3, 4 etc. The volume pool ID which automatically starts at 1 for the default pool "NetBackup". Things like Scratch Pools or onsite/offsite pools are typically also used and these all have unique volume pool ID's. Many encryption solutions such as Decru and IBM use the volume pool ID to determine what backups to encrypt or not This user defined field is the name of the volume pool that media is placed in to. The default is NetBackup but many others are typically created to segment tapes in to groups
Volume Pool ID
Volume Pool Name
NetBackup, Scratch, CatalogBackup, MSEO, WORM, etc.
557

Volume/EMM Database Server

Explanation
The name of the Volume Database (pre-NetBackup 6.) or EMM server (NetBackup 6.0+). This is typically the NBU Master but doesn't have to be in the case where multiple masters are sharing the same EMM server.
Tape Library Attributes Tape Library Agent Product NetBackup, TSM The backup application that controls the tape drive The server host name that the OpsCenter agent is installed on that is used to collect tape drive information. The device database server that is controlling the particular library. This is the Enterprise Media Manager server (EMM) in NetBackup 6.0+ or the device control host in 5.1 and below. The manufacturer as determined by the SCSI inquiry string in the backup application. The serial number, unique, to each tape library The total number of slots that exist in a tape library
Tape Library Agent Server
ops-agent.example.com
Tape Library Device Database Server
NBU-device-host.example.com
Tape Library Manufacturer
STK, Quantum, IBM etc.
Tape Library Serial Number
ADIC203100468_LL0
Tape Library Slot Count
40, 120, 360
558

Tape Library Type
Tape Library DLT, Tape Library 8MM, The type of tape library Tape Library ACS (TLD, ACS, 8MM, 4MM, TLM, TLH etc) 0, 1, 2 etc. The unique number given to each tape library in the EMM database. This ID is put together with the library type in the NBU GUI to show TLD(0), TLD(1) etc.
Tape Library Unique ID
Tape Drive Attributes Name IBM.ULTRIUM-TD2.000 The name of a tape drive as given by the backup application, usually default names are based on SCSI inquiry strings that contain the manufacturer name and model number The number of a tape drive as given by the backup application which is unique for each physical drive (a number could be shared between media servers though) A simple true/false on weather the tape drive is shared across backup servers or not The device host (Media Server) that the tape drive is connected to.
Number
0, 1, 2, 3 etc.
Shared
true/false
Tape Drive Device Host
NBU-device-host.example.com
559

true/ false
Explanation
A simple true/false on weather the tape drive exists in the current configuration (true) or if it is historical and no longer exists (false) The unique serial number for a physical tape drive The storage unit that the tape drive is assigned to The type of tape drive as defined by the backup application. For NetBackup this is also called the density and specifies what types of tape can go in the drive. The tape drive number inside the library
Tape Drive Is Current
Tape Drive Serial Number
768ZD03034
Tape Drive Storage Unit Name Tape Drive Type
dcdell214-dlt-robot-tld-0
hcart, hcart2, dlt, 8mm etc.
Tape Drive Unique ID for Library Tape Usage Attributes Storage Unit Group Name
1, 2, 3, 4, 5, 6 etc.
Storage Unit Tape Group
The storage unit group that the storage unit that the tape drive belongs to The host (Media Server) that the tape drive is assigned to for use at time of tape drive information collection
Tape Drive Assigned
nbu-host.example.com
Tape Drive Control
TLD, ACS, DOWN-TLD, DOWN-ACS etc. The robot type that is controlling the tape drive and it's associated status of up or down at time of tape drive information collection
560

true / false
Explanation
A true / false for if the tape drive was enabled at the time of tape drive information collection A true / false for if the tape drive was in use at the time of tape drive information collection The tape that was in the drive at the time of tape drive information collection The date and time that the tape drive information was collected
Tape Drive Enabled
Tape Drive In Use
true / false
Tape Drive Recorded Media ID
VT0036
Tape Drive Snapshot Time
Apr 05, 2008 22:57:17
Backup Log Attributes Backup Log Agent Server ops-server.example.com The host name of the OpsCenter server where the database and web interface resides
Backup Log Message
backup of client dcdell211 exited with The detailed status status 71 (none of the files in the file messages for each job list exist) nbu-host.example.com The host server with the backup application that logged the error message The backup client that was associated with the logged error message The process or daemon name that wrote the error message
Backup Log Source Host
Backup Log Client
nbu-client.example.com
Backup Log Daemon Name
bptm, ndmpagent, nbpem, bpbrm
561

The group ID that can be specified by the backup product to group them in a certain way. Note:The secondary ID and the Group ID are basically intended for the same purpose, that is to group the jobs in some way that is useful in reporting. A unique number for each backup job in a backup domain that identifies what backup job caused the error message to be logged The date/time that the error message or log was written to The backup application name that caused the error message to be created The severity code of the error message The code representing the type of the log and error message The version of the log/error message
Backup Log Job Group 5980 ID
Log Primary ID
6021
Log Time
Mon 3/4/2008 3:34:34
Product
NetBackup, TSM
Severity Code
1, 2, 3, 4 etc.
Type Code
1, 2, 3, 4 etc.
Version
1, 2, 3, 4 etc.
Agent Monitoring Agent Configuration ID 1, 2, 3, 4 etc. A unique number for each data collection agent under the OpsCenter server
562

Agent Host

ops-agent.example.com
Explanation
The host name of the OpsCenter data collection agent The date and time of the last heartbeat from the data collection agent to the OpsCenter server The host name of the OpsCenter server where the database and web interface resides The number of seconds since the last heartbeat from the data collection agent to the OpsCenter server
Last Heartbeat
May 04, 2008 10:52:28
Server
ops-server.example.com
Time Since Agent Last 44 Heartbeat
Appendix
Man pages for CLIs
564
Man pages for CLIs changeDbPassword
changeDbPassword
changeDbPassword This script changes the OpsCenter database password. This
is supported only for DBA user and not for guest and server passwords.
SYNOPSIS
changedbpassword [--setDBAPassword=<DBA password>]|[--restoreDefault] | [-h|-?|--help]
DESCRIPTION
Sybase SA (SQL Anywhere) database management system is used to store the OpsCenter data. You require a user name and a password to access the database. The following database user account is shipped with OpsCenter:
dba The database administrator account. The dba account is required by the database queries that are used to update the database schema or upgrade to a new product version.
When the tool changes the dba password, it updates a configuration file on the file system so that the server can still access the database. The password is encrypted before it is stored in the configuration file. However, since the server needs 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 administrator is advised to check the permissions on the configuration file to ensure that only an 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.
Man pages for CLIs changeVxATProperties
565
changeVxATProperties This script configures the Symantec Product
Authentication Service (AT) Server parameters.
SYNOPSIS
DESCRIPTION
The 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
OPTIONS
Not applicable
NOTES
Enter 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
566
Man pages for CLIs configurePorts
configurePorts
configurePorts This script is used to configure Web server ports on Unix or
Linux systems.
SYNOPSIS
configurePorts.sh [-status]|[-httpPort <httpPort>][-httpsPort <httpsPort>][-shutdownPort <shutdownPort>]
DESCRIPTION
The 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
NOTES
To know the HTTP and HTTPS port that OpsCenter uses, run the configurePorts utility. On Windows, run the follwoing command:
INSTALL_PATH\OpsCenter\gui\bin\goodies\configurePorts.bat -status
On UNIX, run the following command:

/opt/SYMCOpsCenterWebGUI/bin/goodies/configurePorts.sh -status
Man pages for CLIs dbbackup
567
dbbackup
dbbackup This script backus up the OpsCenter database.
SYNOPSIS
dbbackup {backupDir | -restore [restoreDir]} [-o [logfile]]
DESCRIPTION
dbbackup is a script used for backing up the OpsCenter database.
OPTIONS
backupDir
(Required) backupDir is the directory where the OpsCenter database is backed up to, or restored from. backupDir should be an absolute path.
restore restoreDir
(Optional) restoreDir is the directory where the OpsCenter database is restored. If not included, dbbackup restores the database to the default data directory (/var/symantec/OpsCenterServer/data). restoreDir should be an absolute path.
-o logfile
Record backup and restore actions to a log file. If logfile is unspecified, output is written to the current directory.
NOTES
On Windows, you perform backups with the dbbackup.bat batch file. The backup script creates the following files in the backup directory: vxpmdb.db and vxpmdb.log Data spaces are started when the main database is started; therefore, starting and stopping the data space file is not required.
EXAMPLES
The following command backs up the OpsCenter database to the my_db_backups directory:
/opt/SYMCOpsCenterServer/bin/dbbackup /my_db_backups
568
Man pages for CLIs dbdefrag
dbdefrag
dbdefrag This script defragments the OpsCenter database.
SYNOPSIS
dbdefrag
DESCRIPTION
The dbdefrag script is used to defragment the OpsCenter database.
OPTIONS
Not applicable
NOTES
To defragment the OpsCenter database run the following commands. On Windows:
INSTALL_PATH\OpsCenter\server\bin\dbdefrag.bat
On UNIX:
/opt/SYMCOpsCenterServer/bin/dbdefrag.sh
Man pages for CLIs opsadmin
569
opsadmin
opsadmin This script is used to monitor/start/stop the OpsCenter services on
Unix or Linux systems
SYNOPSIS
opsadmin.sh {start|stop|monitor}
DESCRIPTION
The opsadmin script is used for monitoring/starting/stopping the OpsCenter services.
OPTIONS
start
Starts all OpsCenter services. This includes OpsCenter database, OpsCenter server and Web server services.
stop
Stops all OpsCenter services. This includes OpsCenter database, OpsCenter server and Web server services.
monitor
Monitors all OpsCenter services and also AT (Symantec Product Authentication Service) and PBX (Symantec Private Branch Exchange)services
NOTES
opsadmin opsadmin.sh resides by default in the /opt/SYMCOpsCenterServer/bin directory.
EXAMPLES
EXAMPLE 1 The following command starts all OpsCenter services:
EXAMPLE 2 The following command monitors OpsCenter services:
570
Man pages for CLIs opsadmin
/opt/SYMCOpsCenterServer/bin/opsadmin.sh monitor
Man pages for CLIs opsCenterAgentSupport
571
opsCenterAgentSupport
opsCenterAgentSupport This script collects OpsCenter Agent configuration
files and logs.
SYNOPSIS
opsCenterAgentSupport
DESCRIPTION
The opsCenterAgentSupport script collects OpsCenter Agent configuration files and logs for troubleshooting.
OPTIONS
Not applicable
NOTES
Run the following commands to execute the support scripts for OpsCenter Agent: On Windows:
INSTALL_PATH\OpsCenter\Agent\bin\opsCenterAgentSupport.bat
On UNIX:
/opt/SYMCOpsCenterServer/bin/opsCenterAgentSupport.sh
You can view the following statuses 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>
572
Man pages for CLIs opsCenterSupport
opsCenterSupport
opsCenterSupport This script collects OpsCenter server configuration files and
logs for troubleshooting.
SYNOPSIS
opsCenterSupport
DESCRIPTION
opsCenterSupport is a script used for collecting OpsCenter server configuration
files and logs for troubleshooting.
OPTIONS
Not applicable
NOTES
Run the following command to collect OpsCenter server configuration information: On UNIX:
/opt/SYMCOpsCenterServer/bin/opsCenterSupport.sh
On Windows:
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
573
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...
574
Starting OpsCenter Web Console Service... C:\Documents and Settings>
Man pages for CLIs runstoredquery
575
runstoredquery
runstoredquery
SYNOPSIS
runStoredQuery <Report Name> <User Name> <Domain Name> <Domain Type> [<Output Type> pdf | csv]
DESCRIPTION
The runstoredquery script runs saved customSQL and the OpsCenter Administrator generates output in the desired format.
OPTIONS
Report Name
Name of the report (surrounded with double-quotes)" " : " " : " " : " " : ." "Example: runStoredQuery "My Report" admin OpsCenterUsers@myhost 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) Default is csv
EXAMPLE
runStoredQuery "My Report" admin OpsCenterUsers@myhost vx pdf
576
Man pages for CLIs startagent
startagent
startagent This script starts the OpsCenter Agent service.
SYNOPSIS
startagent
DESCRIPTION
The startagent script is used to start the OpsCenter Agent service.
OPTIONS
Not applicable
NOTES
Enter the following command to start the OpsCenter Agent process on a UNIX machine:
/opt/SYMCOpsCenterAgent/bin/startagent
Man pages for CLIs startdb
577
startdb
startdb This script starts the OpsCenter database.
SYNOPSIS
startdb
DESCRIPTION
The startdb script is used to start the OpsCenter database.
OPTIONS
Not applicable
NOTES
To start the database server, enter the following command:
/opt/SYMCOpsCenterServer/bin/startdb
578
Man pages for CLIs startgui
startgui
startgui This script is used to start the OpsCenter Web server service on Unix
or Linux systems.
SYNOPSIS
startgui.sh
DESCRIPTION
The startgui script is used for starting the OpsCenter Web server service.
OPTIONS
Not applicable
NOTES
The startgui.sh script by default resides in the /opt/SYMCOpsCenterGUI/bin directory. The following command starts the OpsCenter WebServer service:
/opt/SYMCOpsCenterGUI/bin/startgui.sh
Man pages for CLIs startserver
579
startserver
startserver This script starts the OpsCenter Server.
SYNOPSIS
startserver
DESCRIPTION
The startserver script is used to start the OpsCenter Server.
OPTIONS
Not applicable
NOTES
Run the following command to start the OpsCenter Server:
/opt/SYMCOpsCenterServer/bin
580
Man pages for CLIs stopagent
stopagent
stopagent This script is used to stop the OpsCenter Agent.
SYNOPSIS
stopagent
DESCRIPTION
The stopagent script is used to stop the OpsCenter Agent.
OPTIONS
Not applicable
NOTES
Run the following command to stop the OpsCenter Agent:
/opt/SYMCOpsCenterAgent/bin/stopagent
Man pages for CLIs stopdb
581
stopdb
stopdb This script is used to stop the OpsCenter database.
SYNOPSIS
stopdb
DESCRIPTION
The stopdb script is used to stop the OpsCenter database.
OPTIONS
Not applicable
NOTES
Run the following command to stop the OpsCenter database:
/opt/SYMCOpsCenterServer/bin/stopdb
582
Man pages for CLIs stopgui
stopgui
stopgui used to stop the OpsCenter Web server service on Unix or Linux systems.
SYNOPSIS
stopgui.sh
DESCRIPTION
The stopgui script is used for stopping the OpsCenter Web server service.
OPTIONS
Not applicable
NOTES
stopgui.sh resides by default in the /opt/SYMCOpsCenterGUI/bin directory.
The following command stops the OpsCenter Web server service:

/opt/SYMCOpsCenterGUI/bin/stopgui.sh
Man pages for CLIs stopserver
583
stopserver
stopserver This script stops the OpsCenter Server.
SYNOPSIS
stopserver
DESCRIPTION
The stopserver script is used to stop the OpsCenter Server.
OPTIONS
Not applicable
NOTES
Run the following command to stop the OpsCenter Server.
/opt/SYMCOpsCenterServer/bin/stopserver
584
Man pages for CLIs stopserver
Glossary
Agent Alerts
See Symantec OpsCenter Agent An alert is a warning that the Symantec OpsCenter application generates when a specific condition - usually an alarming situation - occurs in the system. You can notify the concerned officials about the alerts by sending an email or an SNMP trap, which help them take corrective actions. The generated alerts are stored in the Symantec OpsCenter database. You can view them using the Alerts section in the Symantec OpsCenter console. Alert Manager is a component in Symantec OpsCenter that comprises an alerting mechanism. It keeps track of the alert conditions specified in the policies and generates alerts appropriately. Data collector is a part of Symantec OpsCenter Agent that collects data from various products. A notification that indicates when an action, such as an alert or a change in state, has occurred for one or more objects in the data center. In Symantec OpsCenter, a console area in which to display and run reports saved by the user. A component that is used by the Symantec products to provide user authentication. Symantec Product Authentication Service is a set of processes and runtime libraries that enables users to log on to multiple Symantec products with one logon. A common Symantec component that uses socket passing to reduce the number of ports required to be open across a firewall. Symantec Private Branch Exchange uses a paradigm similar to that of a telephone switchboard in which calls placed to a switchboard are redirected to a known extension. In the PBX exchange, client connections sent to the exchange's port are redirected to an extension associated with the Symantec OpsCenter Server. A graphical user interface that displays reports and other information for users of Symantec OpsCenter through a standard Web browser. The console provides a central point to manage cost analysis and chargeback for services, managing workflow, displaying and managing reports, and other tasks. Sybase SA (SQL Anywhere) database management system containing data related to backup /archive service usage and expenditure, cost metrics and chargeback
Alert Manager
Data Collector
event
My Reports
Symantec OpsCenter console
Symantec OpsCenter database
586
Symantec OpsCenter Glossary
formulas, and alerts. Symantec OpsCenter database is installed silently when you install Symantec OpsCenter Server.
Symantec OpsCenter
The unlicensed version of OpsCenter is called Symantec OpsCenter. Symantec OpsCenter is a Web-based software application that helps organizations by providing visibility into their data protection environment. Symantec OpsCenter lets you do operational reporting
Symantec OpsCenter Analytics Symantec OpsCenter Agent
The licensed version of OpsCenter is called Symantec OpsCenter Analytics. Symantec OpsCenter Analytics lets you do advanced business-level reporting. A Symantec OpsCenter component that collects information from discoverable applications residing on remote host systems, such as Symantec NetBackup, Symantec Backup Exec, EMC Legato Networker, or Entreprise Vault. Symantec OpsCenter formats the information collected from these applications and displays it through the Symantec OpsCenter console. Symantec OpsCenter Server, the core of the architecture, is a Web application that normalizes backup or archive data collected from various applications. This normalized data is used for reporting on backup related information. The Symantec OpsCenter Java View Builder is an application in which an administrator creates, modifies, and manages access to the Symantec OpsCenter views that users see in the console.. 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 Builder and make them available in the Symantec OpsCenter console. The following view details appear in the Symantec OpsCenter console.
Symantec OpsCenter Server
Symantec OpsCenter View Builder
Views
Index
A
about Symantec OpsCenter 19 about Symantec OpsCenter Analytics 20 access OpsCenter console 34 ActiveX 33 add master server 278 NetBackup 7.0 master server 279 adding existing user 239240 new user 239240 adding host alias 230 adding licenses 226 adding users 235 Agent deploying 81 overview 29 Agent deployment 81 agent.conf file 31 alert policies alert conditions 394 alerts filtering by type 382 responding to 383 archive data 292
B
backing up OpsCenter database 200 bookmarks using with OpsCenter 64 business planning 23
C
changeDbPassword 564 changeVxATProperties 565 changing AT parameters 194 changing password 225 chargeback cost variables 251, 253
chargeback (continued) formulae 254 modeling 255 cluster 166, 173 installing OpsCenter server UNIX 178 Windows 170 limitations UNIX 174 Windows 167 OpsCenter server Windows 167 preinstallation checklist 176 AIX LVMVG 177 all VCS cluster configurations 176 disk only 177 HP-UX with volume manager 178 no volume manager 177 VxVM 176 prerequisites UNIX 174 Windows 167 supported solutions 166 uninstalling OpsCenter server UNIX 181 Windows 173 color coding in OpsCenter 57 compliance reporting 23 configure session timeout interval 43 configure SMTP 228 configure ThreatCon feature 229 configurePorts 566 configuring Enterprise Vault data collector 302 configuring NetBackup PureDisk data collector 291 connected master server state 277 Content pane enlarging 57 Summary and Hierarchical views 55
588
Index
control OpsCenter logging on UNIX 215 on Windows 214 control OpsCenter services Agent service on UNIX 190 Agent service on Windows 188 all server services on UNIX 189 all server services on Windows 187 database server on UNIX 189 database server on Windows 188 OpsCenter server on UNIX 190 OpsCenter server on Windows 188 OpsCenter Web Server service on UNIX 190 OpsCenter Web Server service on Windows 188 controlling OpsCenter services and processes 187 copying user profile 232 cost formulae 254 cost estimation 255 costs variables 251 create alert policy 402 creating cost formulae 254 cost variables 251 custom report 468 custom SQL query 469 email recipients 245 SNMP trap recipients 247 views 312 custom reports 460 custom SQL query 461 customizing alert settings 455
delete master server 286 Deleting user group 242 deleting alert recipients 249 cost formulae 254 deleting user 239240 dependency of OpsCenter services 191 deployment mode multi domain 297 single domain 297 standalone mode 297 Difference between Symantec OpsCenter and Symantec OpsCenter Analytics 71 disable security warnings on IE 6.0 35 on Mozilla 36 on Mozilla and IE 37 documentation for Sybase 192 HTTP and HTTPS ports 210 NBSL 79 NetBackup 32 SymcOpsCenterWebServer 68 VxUL 68 drives controlling 417
E
edit master server 286 editing currency list 250 editing user profile 239240 editing users 235 email report 467 email recipients creating 245 EMC Legato Networker 305 Enterprise Vault 292 data types 293 versions supported 295 Enterprise Vault data collector 302 data collection checklist 303 deployment scenarios 295 exporting report 466
D
Data migration from NOM to OpsCenter 120 from VBR to OpsCenter 134 data purge configure 227 database see (OpsCenter database) 192 dbbackup 567 dbdefrag 568 deduplication 288 defining cost formulae 254 cost variables 251
Index
589
F
file formats 466 firewall considerations 205 firewalls Symantec Private Branch Exchange 26 floating-point math and OpsCenter 162
L
Legato data collector 305 License Capacity Alert 392 license keys 70 adding 226 deleting 227 viewing 227 licensed OpsCenter features 72 licensing model 69 log files on UNIX servers 217 on Windows servers 215 logging in to OpsCenter 41 out of OpsCenter 43
G
getting started with typical OpsCenter tasks 63 Guided Recovery 427 Destination host and login screen 432 Job Details screen 434 metadata 428, 435 Performing a cloning operation 429 Post-clone operations 434 Pre-clone check screen 434 Pre-operation checks 428 Select Control File Backup screen 431 Select Destination Parameters screen 433 Select Master Server screen 431 Select Source Database screen 431 Selection summary screen 433 Troubleshooting 434
M
Manage views controlling scope 390 manage alert policies 390 manage devices 413 manage storage 408 managed master server considerations 78 managed server icons 57 Management Information Base (MIB) 440 managing folders 476 managing licenses 226 merging objects 231 Microsoft Internet Explorer 34 Microsoft SQL Server versions supported 295 modeling chargeback 255 modifying alert recipients 248 cost formulae 254 cost variables 253 report export location 233 tape library 232 Monitor views controlling scope 324 monitor views monitoring alerts 379 monitoring devices 368 monitoring hosts 375 monitoring jobs 331 monitoring media 359 monitoring policies 350
H
heap size adjusting 155
I
IBM Tivoli Storage Manager 303 icons for managed server status 57 install AT UNIX 175 Windows 168 clustering. See cluster NetBackup media kit 74 OpsCenter DVD 74 install and upgrade checklist 86 install OpsCenter on UNIX 96 on Windows 91 Installing OpsCenter 90
J
JavaScript 33 jre (Java Run Time Environment) 68
590
Index
monitor views (continued) monitoring services 348 Mozilla Firefox 34 My Dashboard tab 474 My Reports tab 470
N
nbproxy process 191 NetBackup data collection adding a master server 278 concept 271 deleting a master server 286 editing a master server 286 enabling or disabling data collection 287 managed master server versions 273 supported data types and collection status 275 NetBackup Service Layer (NBSL) 79, 211, 271 Network Address Translation (NAT) network considerations 79 not connected master server state 277
O
object types 233 opsadmin 569 OpsCenter adjusting heap size 155 Sybase cache size 159 and floating-point math 162 color keys 57 database 80 defragmenting databases 194 installing UNIX 96 Windows 91 sanity check after installing 154 sizing 80 status bar 57 status icons 57 store database and logs on separate disk 195 Sybase database used 69 tasks performed on startup 155 uninstalling UNIX 164 Windows 163 OpsCenter alerts about alert policies 392
OpsCenter alerts (continued) alert conditions 394 creating alert policy 394 managing alert policy 407 understanding alert counts 406 OpsCenter architecture database 28 Server and Authentication Service 28 OpsCenter back up and restore procedures 199 OpsCenter console content pane 54 description 47 quick links 53 tabs and subtabs 49 ThreatCon pane 53 title bar 48 View pane 51 OpsCenter context-sensitive help locating 32 OpsCenter database back up using backupDB script 199 backing up 200 restoring 202 OpsCenter database password file 202 OpsCenter database utilities change database administrator password 193 defragment OpsCenter databases 194 OpsCenter installation hardware requirements 80 install checklist 86 master server considerations 78 Operating System requirements 74 supported backup and archive products 76, 260 web browser considerations 33 OpsCenter post-installation starting to use OpsCenter 154 OpsCenter processes on UNIX 184 OpsCenter reports 457 OpsCenter Server 26 Authentication Service 28 OpsCenter server scripts on Windows and UNIX 185 OpsCenter services on Microsoft Windows 183 OpsCenter start-up tasks 155 OpsCenter system requirements see OpsCenter 80 OpsCenter upgrade procedures 102
Index
591
OpsCenter user profiles 201 OpsCenter View Builder. See View Builder 31 OpsCenter views overview 307 opsCenterAgentSupport 571 opsCenterSupport 572 originator ID 213 OS considerations 76
P
partially connected master server state 277 PBX 26 PDOS 288 performance tuning 155 policy filtering by type 353 port numbers backup and archive products 208 HTTP 209 HTTPS 209 key OpsCenter components 205 ports Symantec Private Branch Exchange 26 product ID 213
Q
quick links minimizing 54 quick start for OpsCenter tasks 63
R
refresh OpsCenter console 50 report schedules 479 report template 487 report templates 459 reports Scheduled Jobs 490 restoring OpsCenter 202 runstoredquery 575
S
saving report 463 Scheduled Jobs reports 490 All Jobs report 492
scheduled jobs reports Job Count Details-Scheduled Vs Actual report 491 Job Count Within Backup Window report 491 Job Count-Scheduled Vs Actual report 491 schedules 478 scripts runstoredquery 575 server.conf file 161 services controlling 350 filtering by type 349 setting default currency 249 Simple Network Management Protocol (SNMP) 439 configuring community name 453 configuring SNMP version 454 SNMP traps 440 supported SNMP versions 440 Single Instance Storage SIS 288 SNMP port 211 SNMP trap recipients creating 247 software components used by OpsCenter 67 standard reports descriptions 504 start-up tasks OpsCenter server 155 startagent 576 startdb 577 startgui 578 starting runstoredquery 575 startserver 579 status icons in OpsCenter 57 stopagent 580 stopdb 581 stopgui 582 stopserver 583 supported backup and archive products 76, 260 supported backup products 23 supported platforms 74 supported upgrade paths 81 Sybase cache size adjusting 159 Symantec Java Web Server (SymcOpsCenterWebServer) 68
592
Index
Symantec OpsCenter Analytics and Symantec OpsCenter 69 Symantec Private Branch Exchange 26 port number configuration 68 Symantec Private Branch Exchange (PBX) 68 port number configuration 283 Symantec Product Authentication Service installing UNIX 175 overview 28 shared component 68 Windows installing 168
upgrading to OpsCenter (continued) from VBR on Windows 109 user access rights 235 user groups creating 242 user profiles viewing 239 using an old NOM or VBR installation 162
V
VBR upgrade considerations 102 Veritas Cluster Server (VCS) for UNIX/Linux preinstallation checklist 176 Veritas NetBackup PureDisk PDOS 288 Veritas Unified Logging (VxUL) 68 log files 213 originator IDs used by OpsCenter 213 view NOM data migration status 128 view OpsCenter alerts using HP OV NNM 438 using HP OV NNM 7.50/7.51 on Windows 438 using MOM 2005 437 using SCOM 2007 438 View pane using 51 view VBR data migration status 142 viewing email recipients 243 host alias 230 viewing alerts using List View 380 using Summary View 386 viewing license 226 views view type 309 visual keys in the OpsCenter console 57
T
tables in OpsCenter applying filters 62 creating custom filters 62 customizing 59 selecting rows 61 using filters 62 viewing hidden columns 59 viewing multiple pages 61 time schedule 485 tool tips 58 troubleshooting accessing OpsCenter 39 OpsCenter console logon issues 41 OpsCenter server issues 44 support script in OpsCenter 212 VBR database inconsistency issues 119 TSM data collector 303 tuning OpsCenter for performance 155
U
unified logging (VxUL) 213 uninstalling OpsCenter UNIX 164 OpsCenter on Windows 163 UNIX installing OpsCenter 96 upgrading to OpsCenter from NOM on UNIX 105 from NOM on Windows 103 from VBR on UNIX 115
W
web browser book marks 64 pop-up blockers 33 support 34 UTF-8 33 Windows installing OpsCenter 91
Index
593
Windows (continued) uninstalling OpsCenter 163

Net Backup Ops Center

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Net Backup Ops Center

Uploaded by

Copyright:

Available Formats

Symantec OpsCenter Administrator's Guide

Windows and UNIX

Symantec OpsCenter Administrator's Guide

Symantec Corporation 350 Ellis Street Mountain View, CA 94043 http://www.symantec.com

Contacting Technical Support

Licensing and registration

Maintenance agreement resources

Additional enterprise services

Installing Symantec OpsCenter ........................................ 67

167 173 173 181

Administering Symantec OpsCenter ............................. 183

Understanding OpsCenter settings ............................... 221

Understanding data collection ....................................... 259

298 300 301 302 303 305

Managing OpsCenter views

Monitoring NetBackup using Symantec OpsCenter .....................................................................

Managing NetBackup using Symantec OpsCenter .....................................................................

408 410 411 413 414 418 420 422 423

Using Guided Recovery ..................................................... 427

Understanding OpsCenter alert policies and alerts ..............................................................................

437 437 438 438 439 439

439 440 440 453 454 455 456

Reporting in OpsCenter .................................................... 457

About additional information on PureDisk data collection ....................................................................... 525

Attributes of NetBackup data ......................................... 531

Man pages for CLIs ............................................................ 563

Symantec OpsCenter Glossary ..................................................................... 585

Index ................................................................................................................... 587

Getting started using Symantec OpsCenter

About Symantec OpsCenter

Getting started using Symantec OpsCenter About Symantec OpsCenter

Symantec OpsCenter Analytics

About Symantec OpsCenter functions

NetBackup NetBackup PureDisk Backup Exec Enterprise Vault

About Symantec OpsCenter Analytics functions

Monitors NetBackup setups

Getting started using Symantec OpsCenter About Symantec OpsCenter

Provides chargeback, custom, and custom SQL reports

Getting started using Symantec OpsCenter About Symantec OpsCenter

Assist organizations in effective business planning by enabling them to do the following:

About monitoring and managing NetBackup

About alerting in OpsCenter

About reporting in Symantec OpsCenter Analytics

Getting started using Symantec OpsCenter About Symantec OpsCenter

About compliance reporting

About business planning

IBM Tivoli Storage Manager EMC Legato Networker

About reporting on archive data

New OpsCenter functions Description

EMC Legato NetWorker

New user interface (UI)

New user roles

Security Administrator Administrator Operator Analyst Reporter

See About OpsCenter user roles on page 237.

Getting started using Symantec OpsCenter About OpsCenter components

About OpsCenter components

About the OpsCenter Server

Symantec Product Authentication Service (AT)

Symantec Private Branch Exchange

Getting started using Symantec OpsCenter About OpsCenter components

View Builder Service

Database Access Layer

Server Communication Layer