Symantec OpsCenter Administrator's GuideWindows 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 Support’s 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. Symantec’s 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 Symantec’s 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
[email protected] [email protected] [email protected] 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 what’s 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 8 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 9 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 ........................................................................................... Configuring the OpsCenter Agent properties for integrated logon ..................... Managing views ................................. 307 307 309 310 310 310 311 311 312 313 314 314 315 315 316 316 316 317 318 About OpsCenter views ......... Viewing the Job Summary by Exit Status section ............................ Modifying node details ......................................................................................................................................................................................................................... About Top 7 Policies by Failed Jobs section .......... About Top 7 Job Error Log Summary section ................ Monitoring NetBackup using the Overview subtab ............... Configuring Enterprise Vault data collector ................................... Adding objects to a view node .................................. Viewing the Services Summary section ........ Modifying views ........... Modifying view level alias ....................................................................................................................... About nodes and objects ..... About view types ................. About the Monitor views ......................... Deleting objects from a view node ................................................... Viewing the Media Summary by Status section ..................................................................................... Adding nodes to a view ............................. Collecting data from EMC Legato Networker ............................ About accessing OpsCenter views ...................................... Working with view filters ..................................12 Contents About creating a user for integrated logon ............................................................... 298 300 301 302 303 305 Chapter 6 Managing OpsCenter views ............................. Collecting data from IBM Tivoli Storage Manager ...................................................................................................................... Viewing OpsCenter views and their details ....... About timeframe selection .. Installing MS SQL Server JDBC driver ............. Viewing the Master Server Summary section .......................................................................................................... Deleting nodes .................................................................... About view levels .................... Creating views ............. Viewing the Drive Summary by Status section ....................................................................................................................................................... Managing nodes and objects ................... Chapter 7 Monitoring NetBackup using Symantec OpsCenter ................................................................................................. Deleting views ................. 323 323 324 324 325 326 326 327 327 328 329 330 330 ............................. Viewing the Job Summary by State section .............................................................................................................. Controlling the scope of Monitor views ..... ................. Using the Summary View for monitoring NetBackup media ..... About OpsCenter alert policies ........................................... Managing alert policies .......................................................................................................................... Using the Hierarchical View for monitoring jobs ........................................ Monitoring NetBackup services ...................................................................... Managing an alert policy ........................ Using the Hierarchical View by Volume Pool for monitoring media ........ Viewing the details for a single alert policy ............................................................................................... Monitoring NetBackup media servers .............................................................................................................. Using the List View for monitoring NetBackup policies .............................................. Monitoring NetBackup clients ....................... Monitoring NetBackup jobs ..... Filtering on type of alert policy ..................................... Using the Summary View for monitoring policies ........... 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 ...... Using the Summary View for monitoring jobs ........... Monitoring NetBackup devices ..................................................................... Monitoring NetBackup alerts ..... Creating (or changing) an alert policy ............... Using the List View for monitoring NetBackup alerts .......... Viewing the alerts associated with an alert policy ............ Using the List View for monitoring drives .................. Controlling the scope of Manage views ..Contents 13 Viewing the Alert Summary by Severity section .. Managing NetBackup storage ....................................................................................................................................................... Using the List View for monitoring NetBackup media ... About the Manage views ............................................... Monitoring NetBackup hosts ......................................... Filtering on NetBackup service type .... Monitoring NetBackup disk pools .................................... Controlling NetBackup services ........................................................................................................................ Monitoring NetBackup media ................................................................................ 389 389 390 390 392 393 393 394 407 407 408 .......... Using the Summary View for monitoring NetBackup alerts ........................................................................ Monitoring NetBackup policies ................................................ Using the Summary view to monitor drives .................... Using the Hierarchical View by Volume Group for monitoring media .................................................................................... Using the List View for monitoring jobs ............................................................... Monitoring NetBackup master servers ............... ............. About SNMP ................................................................................................................................ 437 437 438 438 439 439 ............................................................................ Troubleshooting files for Guided Recovery cloning operations ...................................................................................... Troubleshooting Guided Recovery ............................ Pre-clone check screen .......................................................................................... Managing storage lifecycle policy .............................................................................................................14 Contents Managing Storage Units ....................................................... About using SNMP with OpsCenter ......................................... Troubleshooting files for Guided Recovery validation operations ........................................... Setting up for cloning .............51 on Windows ... 408 410 411 413 414 418 420 422 423 Chapter 9 Using Guided Recovery ............................ Select Master Server screen ........................................................ Managing Storage Unit Groups .... 427 About Guided Recovery ................................................................................................................................ Performing a cloning operation ............................................................................ Managing disk pools . About managing OpsCenter alerts in Microsoft Operations Manager 2005 .................. Destination Parameters screen ....50/7...................................................... 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 ............................................... Managing robots ............................................... Pre-operation checks .................... Managing NetBackup devices ... About managing OpsCenter alerts using HP OpenView Network Node Manager 7............................................................... Selection summary screen .................................................. Job Details screen ............................................... Destination host and login screen ................................................................. Managing drives .............................................................. Managing SAN clients ....................................................................................................................................................................................................... Managing Fibre Transport (FT) servers ......................................... Select Control File Backup screen ................. Troubleshooting files for metadata collection operations at the time of the backup ......................................................................... Post-clone operations ............................................................................................................................................. Select Source Database screen ....... About managing OpsCenter alerts using Microsoft System Center Operations Manager 2007 .......... .... Managing folders ............ Creating a report using a Report Template ............... Managing My Reports ............... Creating a report using SQL query .. Configuring the SNMP version for sending SNMP traps ............................. About report filters .. 457 About OpsCenter reports ................................................................................................................................................................................................................................................ Deleting a saved report ........................................................................................................ 439 440 440 453 454 455 456 Chapter 11 Reporting in OpsCenter .......................................................... Managing reports .... About customizing alert settings ............................................................................................................ 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 .......................................................................................... Adding a folder .................................... Working with Report Templates ......................................................... About the Management Information Base (MIB) and OpsCenter support .................. Creating a report using My Reports tab ................................. Configuring the SNMP trap community name for OpsCenter ....................................................................... Exporting a report ........................ Viewing a saved report ................... About custom reports ............. Managing My Dashboard .............................................................................................................................................................. Emailing dashboard sections .......................... About the OpsCenter reports UI ..... Email a saved report ..........Contents 15 About SNMP versions ........... About custom SQL query ...................................................................... Saving a report ......................................................................................... Editing a saved report ...... About SNMP versions supported in OpsCenter ..................................................................................................................................................................................................................................... About report creation wizards .................................................. Modifying a dashboard section ....................................................................................................... Emailing a report ................ Frequently asked SNMP questions .............................................................................................................................................................................. About Report Templates .................................................................................. Deleting a dashboard section .................................. Export a saved report .... Adding reports to a dashboard ............................................................ Creating a custom report ........... Refreshing My Dashboard ......................................... About report conditions ..... ................................................................ 531 Man pages for CLIs ........................ Managing report schedules ......................................................................................................... Editing a report schedule ...............16 Contents Editing a folder .......................................................................................................... About policy reports ........................... Viewing report schedule details .............................................. About schedules ......................................................................................... About performance reports ................................................. About archive reports ...................... About vault reports ......... About Report Templates descriptions ...................... 525 About AT configuration scenarios specific to PureDisk backup product ............................................................................................................................................... 585 .... About catalog reports ............................................................................. Scenario 1: Common Root Broker .............................................. Scenario 2: Different Root Brokers ............................... About job reports ....... About chargeback reports .. 563 Symantec OpsCenter Glossary ............................................................................................................................. About client reports ............ Deleting a report schedule ............. About media reports ............................................................... About backup reports ............................................................................................. 525 526 527 529 Appendix B Appendix C Attributes of NetBackup data ................................. Creating a report schedule ................. Setting up a trust between the OpsCenter AB host and PureDisk SPA host .......................................................... Deleting a time schedule ......................... Deleting folders ........................................................................ Managing time schedules ........................................... 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 .................................................................................................................................................................................................. Creating a time schedule ............................................................................... About Disk Based Data Protection .................................................... Viewing time schedule details ........................ Editing a time schedule .................................................................................................... Deleting reports from a folder ....................................................................................... 531 About backup data attributes ....................................................... ..................... 587 ....................................................Contents 17 Index ........................................... 18 Contents . Chapter 1 Getting started using Symantec OpsCenter This chapter includes the following topics: ■ ■ ■ ■ ■ ■ ■ ■ ■ About Symantec OpsCenter About what’s 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. OpsCenter is a convergence of NetBackup Operations Manager (NOM) and Veritas Backup Reporter (VBR) and is available in the following two versions: . you can track the effectiveness of data backup and archive operations by generating comprehensive reports. By using Symantec OpsCenter. Analytics offers report customization. In addition to the features available in the unlicensed OpsCenter version. refer to the Installing Symantec OpsCenter chapter. chargeback reporting and support for third-party data protection products. 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. For details on OpsCenter upgrade from NOM and VBR and data migration. and reporting functionality previously. Symantec OpsCenter Analytics This is the licensed version of OpsCenter. Symantec OpsCenter provides single deployment configuration and user interface for monitoring. These available in NOM and VBR. Symantec OpsCenter Analytics can perform the following functions: ■ Monitors NetBackup setups . 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. These features were available in VBR.20 Getting started using Symantec OpsCenter About Symantec OpsCenter Symantec OpsCenter This OpsCenter version does not require any license. alerting. About Symantec OpsCenter functions The unlicensed version of OpsCenter is called Symantec OpsCenter. and capacity planning teams. A wide range of audiences can benefit from the reporting and management capabilities of Symantec OpsCenter Analytics. IT finance teams. IT architects. custom. The audiences include IT (Information Technology) managers. external compliance auditors. application owners. external customers. multi-level views of backup and archive resources and customizable reports for tracking service usage and expenditures. and custom SQL reports Symantec OpsCenter Analytics displays customizable. 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. 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 ■ ■ ■ ■ . It also contains tools for defining cost metrics and chargeback formulas or handling alerts. 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. Generates alerts depending on conditions that you have defined See “About alerting in OpsCenter” on page 22. legal teams.Getting started using Symantec OpsCenter About Symantec OpsCenter 21 ■ Manages or administers NetBackup setups See “ About monitoring and managing NetBackup” on page 22. auditors. line-of-business managers. IT managers. It does not require you to separately log on to each NetBackup master or media server. 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. See “About OpsCenter reports” on page 457. which lets administrators focus on other job responsibilities. which monitors and notifies you before serious problems happen to your backup environment. clients. and policies. You can use predefined alert conditions to create alert policies to monitor typical issues or thresholds within NetBackup or other products. It can manage up to 100 NetBackup master servers distributed across multiple locations. . OpsCenter lets you view the operational status and health of your distributed data protection environment. ■ About monitoring and managing NetBackup OpsCenter can manage and monitor NetBackup master and media servers.22 Getting started using Symantec OpsCenter About Symantec OpsCenter ■ Assist organizations in effective business planning by enabling them to do the following: ■ Estimate backup resources required in the future. and policies. Cost reports for archive data are not available. About alerting in OpsCenter OpsCenter provides a policy-based alert system. See “Managing alert policies” on page 390. You can send an email or SNMP notification in response to an actual alert. About reporting in Symantec OpsCenter Analytics This section states the benefits that you can get from the Symantec OpsCenter Analytics reports. They no longer need to be logged in to a terminal to monitor systems continuously. 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. OpsCenter can generate reports filtered by views. These reports help you identify locations or departments containing assets with critical data. you can measure performance of the system against service level agreement (SLA). such as history or trend analysis. It seamlessly integrates with Symantec’s as well as third-party backup products and provides consistent reporting across them. External compliance reports help you follow the policies laid down by various regulatory bodies that are related to federal. In addition to tracking the backup or archive information.Getting started using Symantec OpsCenter About Symantec OpsCenter 23 About compliance reporting OpsCenter Analytics helps organizations evaluate their compliance with internal and external business standards by providing accurate and customizable reports. For example. you can track the usage of backup resources and identify the risks involved. The reports. For example. These reports are then used in resource planning. This report is then used to determine the time required to purchase new tape drives. master servers. It can collect data from the following target products: ■ ■ ■ ■ Symantec NetBackup Symantec BackupExec Symantec NetBackup PureDisk Symantec Enterprise Vault . The results are then used to optimize data protection management. These policies include Sarbanes-Oxley act (SOX) and Health Insurance Portability and Accountability Act (HIPAA). healthcare. the line of business they represent. It delivers backup services to organizations. OpsCenter reports ensure recovery of key information assets. About business planning OpsCenter Analytics is a management tool that helps you optimize your data protection environment with effective business planning. you can create views to display assets according to their locations in the organization. The reports can help you ensure that the data recovery meets the recovery-time and recovery-point objectives. This product supports a wide range of backup and recovery solutions including Symantec’s NetBackup and BackupExec. or media servers. By using internal compliance reports. you can generate a report that anticipates a shortfall of resources in the future based on the current backup trend. A view shows a set of enterprise assets (hosts or file systems) organized in logical groups. or the applications that are installed. which include reporting on backup and recovery trends and managing data centers. ensure your compliance with SLA. internal processes. and others. By using these reports. OpsCenter can generate reports according to views created. 24 Getting started using Symantec OpsCenter About what’s new with OpsCenter in comparison with NOM and VBR ■ ■ IBM Tivoli Storage Manager EMC Legato Networker OpsCenter’s ability to forecast backup resource requirements helps data center executives to decide whether to maintain the existing resources or add new capacity. drill-down OpsCenter reports help you determine the applications. you can create a formula that determines charges based on kilobytes of backed up data over a period of time. About what’s new with OpsCenter in comparison with NOM and VBR OpsCenter offers the following enhancements or new functions. organizations can provide appropriate resource planning in advance. you can generate a report showing resource consumption by department. you can then present itemized invoices to internal customers. databases. 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. the size of these messages before and after the archive operation. Table 1-1 lists the new functions introduced in OpsCenter Analytics. or business departments that are the heaviest consumers of backup resources. Cost reports for archive data are not available. By using the chargeback function. or location. in an environment running 20 instances of Oracle applications. export chargeback tables to third-party billing systems. or use the data to analyze and justify expenditures. Using this chargeback data. Depending on this information. . Note: You can generate cost reports only for backup data. Symantec OpsCenter Analytics offers you a set of chargeback reports that detail backup services expenditures. you can track the backup and recovery usage and the associated cost. By using these reports. You can report on the number of messages that are archived across mailboxes. server. For example. For example. you can define pricing models for backup service delivery and allocate costs to customers based on these models. The detailed. which were not part of NOM or VBR. ■ Symantec OpsCenter Analytics . In OpsCenter.Getting started using Symantec OpsCenter About what’s new with OpsCenter in comparison with NOM and VBR 25 Table 1-1 New OpsCenter functions Description As per the new licensing model. See “About Symantec OpsCenter Analytics functions” on page 20. add a license key to enable Symantec OpsCenter Analytics.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. 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. five user roles are defined to perform various GUI functions. and a new look and feel. a restructured standard report tree has been added that supports single-click execution. ■ OpsCenter function New licensing model With Symantec OpsCenter Analytics.This is a licensed version. In addition. ■ ■ ■ ■ ■ New user roles Security Administrator Administrator Operator Analyst Reporter See “About OpsCenter user roles” on page 237. improved task efficiency. If you want to use advanced OpsCenter features. you get the following additional functions. client connections that are sent to the exchange’s port are redirected to an extension associated with the OpsCenter Server. including notification. A set of common authentication runtime libraries and processes that enable users to log on once to access multiple products. is a Web application that normalizes backup / archive data collected from various applications. 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. OpsCenter server is supported on Windows and Solaris platforms. Alert Manager Component that provides policy-based alert management. NIS/NISplus repositories or any identities that can be authenticated through PAM. custom actions. This normalized data is used for reporting on backup related information. and remove Veritas product license keys. A common Web server (that uses Java Server Pages) and a JRE to serve the OpsCenter console. AT validates identities based on external name spaces like Active Directory or other LDAP servers. change. 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. In the PBX exchange. and alerts. the core of the architecture. A common component that uses socket passing to reduce the number of ports required to be open across a firewall. cost metrics and chargeback formulas. and SNMP management capabilities. A common Veritas Licensing Module and API used to add. UNIX identities based on password files. Symantec Product Authentication Service (AT) Symantec Web Server and Java Runtime Environment (JRE) Veritas Licensing Manager Symantec Private Branch Exchange .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. It also provides a private user repository for service identities. 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 .Getting started using Symantec OpsCenter About OpsCenter components 27 Figure 1-1 shows OpsCenter Server architecture. The OpsCenter database is completely embedded and requires no additional installation steps. chargeback formulae. 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+. OpsCenter uses a Sybase SQL Anywhere 11 (Sybase 11) database installation that is separate from the NetBackup database. OpsCenter supports upgrade from NOM and VBR. ■ ■ Note: For more details on AT. Agent. Enable trust between OpsCenter and other Symantec products that also use AT. About the Symantec Product Authentication Service The OpsCenter Server relies on Symantec Product Authentication Service (AT) for user authentication for connections between. refer to the ICS documentation that is shipped with the NetBackup 7.0 documentation set. which consists of a single cross-platform database file. . all information that is in the Web UI is contained in the OpsCenter database. Provide for a secure transport of data between OpsCenter Agent's and the OpsCenter server. The Symantec Product Authentication Service is referred to as AT. it returns a credential that OpsCenter passes along when cross-linking to other Symantec products such as NetBackup Operations Manager. LDAP and even standard unix password. and alerts. OpsCenter Server. The Sybase database is also self tuning and does not require a database administrator to maintain it. The Web credential provides a limited form of user authentication so that products do not prompt the user to log on again. and Java View Builder. NIS. When the Symantec Product Authentication Service library authenticates a user for OpsCenter. Except for a very small number of system settings.28 Getting started using Symantec OpsCenter About OpsCenter components 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. OpsCenter Agent is supported on Windows and Solaris platforms. 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. The OpsCenter Agent relies on the Java Runtime Environment (JRE) to perform its functions. Job. For example. . Alternatively. or scheduled job data from NetBackup master server of the versions older than 7.0. 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. Media. or Skipped File data from NetBackup master server of any supported version If you want to collect any data type from NetBackup 7. These products can reside on the OpsCenter Agent host or on remote hosts. Policy and Schedule. or can be installed on a remote host. you need to have OpsCenter Agent installed and configured. A number of combinations of OpsCenter Agent and Server installations are possible. Both JRE and AT libraries are installed automatically with the Agent installation. 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. The OpsCenter Agent also requires embedded AT (Symantec Product Authentication Service) to authenticate itself with the OpsCenter Server. All OpsCenter data collectors are configured on every Agent.0 master server ■ The OpsCenter Agent can reside on the same host as the OpsCenter server. error log. Configure and run only these data collectors for the target product that you want to monitor / report on. 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.Getting started using Symantec OpsCenter About OpsCenter components 29 About the OpsCenter Agent The OpsCenter Agent collects data from various Symantec and third-party backup / archiving products. When you send a request to get the Agent status through the OpsCenter UI. The core of the OpsCenter Agent is a Java virtual machine (JVM) in which you run different data collectors. Monitors modifications made to the agent configuration using the OpsCenter console. The Scheduler and CORBA form the agent core. schedules backup / archive data collection data types. the OpsCenter Server send the request to CORBA Server to receive the requested information. Periodically sends a heartbeat message to the OpsCenter Server to ensure the reliability of communications between the agent and the server. and receives commands through the CORBA API. The OpsCenter Agent comprises Scheduler. ■ ■ 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. and data collectors that collect backup data from all available backup application. 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. the agent must be installed on the Legato server host. which are stored on the OpsCenter Server.30 Getting started using Symantec OpsCenter About OpsCenter components Note: Legato data collector does not support remote data collection. . Therefore.server connections. the Symantec Product Authentication Service client libraries reside on the agent host. The Agent behaves as a CORBA client when sending data or alerts to the OpsCenter Server. The OpsCenter Agent communicates with the Server. As the OpsCenter Server relies on Symantec Product Authentication Service to authenticate OpsCenter agent . CORBA Client/Server. 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. Each data collector must conform to an interface that defines its interaction with the OpsCenter Agent. A heartbeat is a request that the OpsCenter Agent sends to the OpsCenter Server to check for any new changes in the configuration settings. You should change the agent configuration settings using the OpsCenter Agent Configuration UI. modifies. About the OpsCenter Java View Builder The OpsCenter Java View Builder is an application in which an administrator creates. The changes that you have made to the agent configuration settings using the OpsCenter UI or console are reflected after the next heartbeat. By default. . you need to install the licensed version of OpsCenter called Symantec OpsCenter Analytics. any changes made to the local agent.Getting started using Symantec OpsCenter About OpsCenter components 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. About Agent configuration and logging Agent configuration settings are stored in the OpsCenter database. a heartbeat is sent every minute. The agent compares the local agent.conf file with the one stored in the database when the agent process is started.conf file. Logging for the agent core and individual data collector is administered in the same fashion but written to different log files. and manages access to the OpsCenter views that users see in the console.conf file do not take place until the agent is restarted. The OpsCenter Agent also caches the latest version of the configuration settings in the agent. Note: You should not modify the agent. The data collector is implemented in a way that suits the underlying product. Note: To create or customize views using Java View Builder. You need to configure a data collector on the OpsCenter Agent host that collects data from a backup or archive product host.conf file. If the agent process has already started. Portions of the online Help may refer the user to other NetBackup documentation for descriptions of NetBackup fields and components. About using the OpsCenter console The following sections cover the basics of how to access and use OpsCenter. Windows. When you run the Java View Builder exe. and Linux About starting the OpsCenter console The OpsCenter server is the focal point for centralized management of the NetBackup servers (release 6. you need to provide login credentials as you do while logging onto the OpsCenter console. task dialog boxes. The View Builder fetches the existing object view definitions from OpsCenter database and displays them in the OpsCenter console. When you start the OpsCenter console to manage and . The following NetBackup documents are referenced in the OpsCenter online Help : ■ ■ ■ ■ NetBackup Administration Console Help NetBackup Administrator’s Guide for Windows. it is directly connected to the OpsCenter Server. Volume I NetBackup Troubleshooting Guide for UNIX. See “Logging on to the Symantec OpsCenter console” on page 41. Actions performed using the View Builder console are then stored in the OpsCenter database. The OpsCenter online documentation assumes that the user has a good working knowledge of NetBackup and its concepts and components. When you install Symantec OpsCenter. For information on how to understand and use the various OpsCenter views and related tasks. It includes how to log on and log off and how the console works. To use the Java View Builder. you select the computer that serves as the OpsCenter server. see the OpsCenter online Help . To access the online Help .0 MP5 and greater) in your backup environment.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. You can also use the help option on the title bar of OpsCenter views. and wizard task screens. Volume I NetBackup Administrator’s Guide for UNIX and Linux. use the help option in most dialog boxes and wizard screens. Context-sensitive help is available for all console views. some of these menus may not display properly. Open the Internet Explorer browser and select View > Encoding > Unicode (UTF-8). add the OpsCenter URL to the Trusted-sites list and lower the security setting. About Web browser considerations Consider the following recommendations and requirements for the Web browser to be able to access the OpsCenter console. the security certificate warnings do not appear on the pop-up menus. Select Continue to this website (not recommended) to open the pop-up menu. ■ ■ ■ ■ ■ .Getting started using Symantec OpsCenter About starting the OpsCenter console 33 monitor your NetBackup environment. The Web browser should have active scripting (ActiveX and JavaScript) enabled. open Internet Explorer and select Tools > Internet Options > Security to configure the Trusted-sites list and lower the security level. The web browser cache must be cleared. The release notes for your release of OpsCenter also include any restrictions or limits for OpsCenter. Once you select this option. If you use pop-up blockers with your Web browser. The following requirements and recommendations should be considered for the Web browser: ■ The OpsCenter console uses pop-up menus. If you encounter this issue. security certificate warnings appear when you access a pop-up menu. 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. Ensure that the character encoding for the browser is Unicode (UTF 8) before you access the OpsCenter console.0 to access the OpsCenter console. You must disable pop-up blocking or add the OpsCenter Web address to the list of acceptable sites in your browser. On some server-class systems. To resolve this issue. an enhanced security configuration can cause some pages to not display properly in Internet Explorer. Open the Mozilla Firefox browser and select View > Character Encoding > Unicode (UTF 8). you open a connection to the OpsCenter Web GUI. If you use Internet Explorer 8. domain is the fully qualified domain name of the OpsCenter server and can also be an IP address. In the Web browser address bar. enter the following: http://<host. IE 7.0 may display a security alert dialog box when you access OpsCenter.0 and higher versions Mozilla Firefox may display an Untrusted Connection page when you access OpsCenter.x.0 and later versions may display a security certificate warning page when you access OpsCenter. Table 1-2 Web browser Microsoft Internet Explorer Web browsers supported by OpsCenter Supported Versions 6. See “Disabling the security alert dialog box in IE 6. 8.x. .34 Getting started using Symantec OpsCenter About starting the OpsCenter console About Web browsers supported by OpsCenter The OpsCenter user interface (the OpsCenter console) is supported with the following Web browsers.0 Notes IE 6. On a system that has a network connection to the OpsCenter server. See “Disabling security certificate warnings permanently from browsers” on page 37. start the system's Web browser. review the following section thoroughly. About accessing the OpsCenter console Before accessing the OpsCenter console.domain>/opscenter host. Mozilla Firefox 3. Table 1-2 lists the Web browsers that OpsCenter supports.0” on page 35. 7. See “Disabling the Untrusted Connection page in Mozilla Firefox” on page 36. See “About Web browser considerations” on page 33. sh -status on UNIX hosts. Run INSTALL_PATH\OpsCenter\gui\bin\goodies\configurePorts. then use http://<host. if OpsCenter uses HTTP port 8181. you may see the security alert dialog box. click the Advanced tab. The following dialog box may be displayed when you access OpsCenter: You can click Yes to proceed further. To know the HTTP and HTTPS port that OpsCenter uses. If port 80 is not available. Disabling the security alert dialog box in IE 6. In the Internet Options dialog box. Use the following procedure to disable this dialog box permanently. OpsCenter can use a different port.0. To disable the security alert dialog box permanently 1 2 Click Tools > Internet Options. . run the configurePorts utility.0 When you access OpsCenter in IE 6.bat -status on Windows hosts or /opt/SYMCOpsCenterWebGUI/bin/goodies/configurePorts. For example. You can also use the URL that is presented at the end of the OpsCenter server installation to access OpsCenter.Getting started using Symantec OpsCenter About starting the OpsCenter console 35 Note: By default. OpsCenter tries to run on port 80 (HTTP).domain>:8181/opscenter. and you shouldn't continue. Ensure that the Permanently store this exception option is checked.domain>. 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.36 Getting started using Symantec OpsCenter About starting the OpsCenter console 3 4 Under Security. click Get Certificate. this error could mean that someone is trying to impersonate the site. this site's identity can't be verified. The following page may open when you access OpsCenter: -------------------------------------------------------------This Connection is Untrusted You have asked Firefox to connect securely to <OpsCenterhost. Restart your browser for the changes to take effect. However. or click Add Exception (when you expand the I Understand the Risks section) and permanently disable the page. In the Add Security Exception dialog box. This option is checked by default. uncheck Warn about Invalid site certificates option. Disabling the Untrusted Connection page in Mozilla Firefox When you access OpsCenter in Mozilla Firefox. when you try to connect securely. To disable the Untrusted Connection page permanently 1 2 3 On the Untrusted Connection page. . you may see the Untrusted Connection page. expand I Understand the Risks section and click Add Exception. sites will present trusted identification to prove that you are going to the right place. Normally. but we can't confirm that your connection is secure. What Should I do? If you usually connect to this site without problems. Getting started using Symantec OpsCenter About starting the OpsCenter console 37 4 5 Click Confirm Security Exception. This is because when you access OpsCenter using http://<host. . you are automatically redirected to HTTPS (hypertext transfer protocol Secure) which is a secure protocol and requires a certificate.domain>/opscenter. you can disable the automatic redirection to HTTPS. Restart your browser for the changes to take effect. However note that using HTTPS provides encryption and secure identification of the server. Disabling security certificate warnings permanently from browsers When you log on to OpsCenter console. In case you do not want to use HTTPS and disable the security certificate warnings while accessing OpsCenter console. you may see security certificate warnings on Mozilla Firefox and Internet Explorer browsers. 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> .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. 2 In the web.38 Getting started using Symantec OpsCenter About starting the OpsCenter console To disable security warnings and HTTPS redirection 1 Open the web.xml file.xml file. it is recommended that you take a backup of the web.xml Note: Before you proceed with rest of the steps. 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.Commenting to disable https <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> Comments End --> 4 Stop the OpsCenter Web GUI service on Windows.Getting started using Symantec OpsCenter About starting the OpsCenter console 39 3 Comment this portion from the web. Table 1-3 describes possible OpsCenter console access issues and their solution. You can also add your comments inside. .in the beginning and --> in the end. For example: <!-.xml file by adding <!-. 5 Restart the OpsCenter Web GUI service on UNIX. Select Control Panel > Administrative Tools > Services and restart (stop and then start) the Symantec OpsCenter Web Server Service. Your Web browser displays the following messages: "page cannot be displayed" or "connection was refused." OpsCenter console access issues.40 Getting started using Symantec OpsCenter About starting the OpsCenter console Table 1-3 Issue You cannot connect to the Web GUI. but the application is not 1 Locate the opscenter.bat -status on Windows hosts or /opt/SYMCOpsCenterWebGUI/bin/goodies/configurePorts. Start all the OpsCenter server processes by using the following commands: /opt/SYMCOpsCenterServer/bin/opsadmin. Your Web INSTALL_PATH\OpsCenter\WebServer\webapps browser displays an "HTTP STATUS 404" 2 Verify that all the OpsCenter server services are running.war file in the following directory to verify that the OpsCenter application is installed: /opt/SYMCOpsCenterGUI 2 Verify that all OpsCenter server processes are running by using /opt/SYMCOpsCenterServer/bin/opsadmin monitor command. 3 Start all the OpsCenter server services by using the following command: INSTALL_PATH\OpsCenter\server\bin\opsadmin. 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. run the configurePorts utility.sh start 3 . to verify that the OpsCenter application is installed: available.sh -status on UNIX hosts. Run INSTALL_PATH\OpsCenter\gui\bin\goodies\configurePorts. causes.bat start Use the following steps on UNIX: 1 Locate the opscenter. The OpsCenter Web GUI The OpsCenter console Use the following steps on Windows: is running.war file in the following directory OpsCenter console is not loaded. and solution Solution Verify that the Symantec OpsCenter Web server Service is running. error. Note: To know the HTTP and HTTPS port that OpsCenter uses. The domains that appear in the Domain drop-down list include the OpsCenterUsers(vx) domain. the user name is admin and the password is password or any custom password that you chose during the installation. you should change the user name and password. a monitoring overview of the NetBackup master servers appears. After the initial log on. and select a domain from the Domain drop-down list. See “Changing your password” on page 225. After initial logon.Getting started using Symantec OpsCenter About starting the OpsCenter console 41 Logging on to the Symantec OpsCenter console You must supply logon credentials on the OpsCenter login screen. OpsCenter uses the default language of the Web browser. you can specify a default language or locale from Settings > User Preferences > General. To log on to Symantec OpsCenter console 1 Enter a user name and password. OpsCenter saves your settings and preferences and uses these settings when you restart the console again. OpsCenter uses the Web browser language (or English). use Settings > User Preferences > My Profile view in the OpsCenter console. See “Setting user preferences” on page 223. If OpsCenter does not support this language. Note: The first time you log on. Initially. it uses English. 2 Click Log On. . domains that are migrated if you upgrade to OpsCenter from NOM or VBR. 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. and domains of the users that are added to the OpsCenter console. To change existing passwords. For administrator initial logon. When you log off from the console. Select OpsCenterUsers(vx) from the Domain drop-down list. If you do not set a default. The login screen displays the message "This user is not authorized to use OpsCenter. Ensure that the Symantec Product Authentication Service is started and running properly. Please ensure that the AT service is running. Either the user name or Username and/or password or both have not password has not been entered. Solution Enter a valid user name. " Authentication service is Authentication down "Error occurred while service is down connecting to the Symantec Product Authentication Service (AT). Verify if hosts file has the correct IP address to host name mapping. The login screen displays the message "User authentication failed. You have a user authentication error. The login been specified. password. Check your network configuration. and domain." The user name and Log on as the OpsCenter admin user domain are valid. Please enter valid user name and password.42 Getting started using Symantec OpsCenter About starting the OpsCenter console 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." Verify that Symantec Product Authentication Service is running. Enter a valid user name and password. You cannot connect to the The OpsCenter server OpsCenter server. The hosts file is located in C:\WINDOWS\system32\drivers\etc directory on Windows. You can start authentication service by running 'net start vrtsat' on Windows and '/opt/VRTSat/bin/vxatd' on UNIX. Please ensure that the server is running. added to the list of users for OpsCenter." The entered user name is not a registered OpsCenter user. The login is not running. Please contact the OpsCenter Administrator for adding this user. screen displays the message "Error occurred while connecting to the OpsCenter Server. but and add the user to the list of the user was not OpsCenter users. You can start authentication service by running net start vrtsat on Windows and /opt/VRTSat/bin/vxatd on UNIX. screen displays the message "Please enter valid user name and password. If problem persists contact your system administrator ." Start the Symantec OpsCenter Server Service and verify that it is running properly. . change "30" to the desired value). Configuring the OpsCenter session timeout interval When left at its default value.xml /opt/SYMCOpsCenterWebServer/conf/web. . This value is set in minutes. To log out from Symantec OpsCenter ◆ Click Logout located on the right side of the title bar. users are automatically logged out of the OpsCenter console when a session is left inactive for 30 minutes. the session timeout interval can be reconfigured. OpsCenter saves most of the settings and changes you make in an OpsCenter session.xml configuration file in a text editor from the following locations: For Windows: For UNIX: INSTALL_PATH\OpsCenter\WebServer\conf\web.xml file. However. To configure the session timeout interval 1 Open the web.xml 2 In the web.Getting started using Symantec OpsCenter About starting the OpsCenter console 43 Logging out of the OpsCenter console When you log out from the console. locate the session-timeout parameter: <session-config> <session-timeout>30</session-timeout> </session-config> 3 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. 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.sh stop 5 Restart the OpsCenter services. Click here to log on and retry. An exception error message appears in the OpsCenter console. " This error results from an internal issue in the OpsCenter console application. You must enable it to use OpsCenter. Enter the following command: Windows UNIX INSTALL_PATH\OpsCenter\server\bin\opsadmin. . Table 1-5 Issue Your OpsCenter console session times out. Solution Log on again. See “Configuring the OpsCenter session timeout interval” on page 43.44 Getting started using Symantec OpsCenter About starting the OpsCenter console 4 Stop the OpsCenter services. you then return to the OpsCenter view that you last visited.bat start /opt/SYMCOpsCenterServer/bin/opsadmin. Enable active scripting in the browser. the OpsCenter user automatically logs out of the console.bat stop /opt/SYMCOpsCenterServer/bin/opsadmin. Any attempt to use OpsCenter. An internal error occurs in the OpsCenter console. Issues when you use OpsCenter console Cause After 30 minutes of inactivity. After successful logon." Enable active scripting in the Web browser. The login screen appears when you try to change views or refresh the current view. You can also configure the session timeout interval. You receive the message "An unknown error has occurred. Enter the following command: Windows UNIX INSTALL_PATH\OpsCenter\server\bin\opsadmin. to use this application. displays the OpsCenter login screen.sh start About possible OpsCenter console issues Table 1-5 describes the issues you may find when you use the console. Getting started using Symantec OpsCenter About starting the OpsCenter console 45 Table 1-5 Issue Issues when you use OpsCenter console (continued) Cause Solution An unresponsive script error is displayed when on Mozilla Firefox . you should set that preference back to the default value.max_script_run_time. If you still receive the prompt (or if you want to see it again). type about:config and press Enter. and double-click on it. ■ . ■ In the about:config page. I promise!. With scripts now allowed to run for longer times. o The about:config "This might void your warranty!" warning page may appear. In the Location bar. you may no longer receive the prompt. ■ In the about:config page. search for the preference dom. type 0. ■ ■ Press OK. to continue to the about:config page.max_script_run_time. type about:config and press Enter. I promise!. search for the preference dom. Click I'll be careful. ■ In the Enter integer value prompt. o ■ The about:config "This might void your warranty!" warning page may appear. to continue to the about:config page.46 Getting started using Symantec OpsCenter About starting the OpsCenter console Table 1-5 Issue Issues when you use OpsCenter console (continued) Cause Solution To tell Firefox to let the script run longer: In the Location bar. Click I'll be careful. When you change the settings and preferences they are saved and if you log out and log on again these settings are used. You can view the console by using a Web browser. 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 . About OpsCenter console components This section provides information on the panes and navigation features available in the OpsCenter console. Figure 1-2 shows the OpsCenter console components. The following is an example view that shows the OpsCenter console components.Getting started using Symantec OpsCenter About OpsCenter console components 47 Table 1-5 Issue Issues when you use OpsCenter console (continued) Cause Solution ■ Right-click on it and choose Reset. the Monitor > Overview view appears. When you log on initially. To adjust the screen space that is used by the tabs and subtabs. the Logged in as value shows the user name that is logged on to the OpsCenter server. Provides an overview about the View pane. select rows. 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. and use filters. You can select the following options: .48 Getting started using Symantec OpsCenter About OpsCenter console components Table 1-6 lists the topics that describe the main elements of the console in greater detail. 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. click the Customize Tabs drop-down list. 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. 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. Context-sensitive help for all views. Using this tab you can also restore data. View standard OpsCenter reports.Getting started using Symantec OpsCenter About OpsCenter console components 49 Small Only the selected tab and subtab are shown in a single row. More information about online Help is available. wizards. hosts. media. and display and respond to any OpsCenter alerts. create and run custom reports. and schedule reports. Manage alert policies. . Table 1-7 Tab Monitor Tabs and subtabs in the OpsCenter console Description Monitor the status of NetBackup jobs. The tabs and subtabs appear in two separate rows. devices. The tabs do not have any icons above them. The tabs have icons placed above them. See “Logging out of the OpsCenter console” on page 43. and dialog boxes is available using this link. 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). NetBackup job policies. Similarly clicking the arrow next to the selected subtab displays rest of the subtabs in a drop-down list. ■ About using tabs and subtabs Table 1-7 describes the main tabs that provide access to the major areas of the OpsCenter console. Manage Reports Note: You can use custom report functionality only with a licensed OpsCenter version (OpsCenter Analytics). See “About OpsCenter documentation ” on page 64. The tabs and subtabs appear in two separate rows. Access Symantec OpsCenter help (click Help). services. Clicking the arrow next to the selected tab displays rest of the tabs in a drop-down list. storage units. Disconnect from the OpsCenter server to end your session (click Logout). devices. policies. Devices go online and offline. The data that is shown in OpsCenter views depends on what you select in the View pane. Symantec ThreatCon pane. See “Setting user preferences” on page 223. set up email and SNMP recipients. and so on. Or You can also drag the line separating the Task pane and the Content pane to resize the Task pane. and Quick Links at the bottom. For example. Click the icon again to show all panes. Also you cannot resize the Task pane from the Monitor > Overview page. . Using the Task pane In many views in the console. The contents of these subtabs vary depending on the current view and represent the views accessible from each main tab.50 Getting started using Symantec OpsCenter About OpsCenter console components Table 1-7 Tab Settings Tabs and subtabs in the OpsCenter console (continued) Description Customize the OpsCenter server. More information about View pane is available. view chargeback settings. You can control when the information in the console refreshes to reflect the changes in your backup environment. add. You can change the refresh setting from Settings > User Preferences > General view in the OpsCenter console. a Task pane is available. Jobs. The minimize or maximize settings are applicable only for the current session. To enlarge the Task pane ◆ Click the icon between the Task pane and the content pane. OpsCenter generates alerts. Under each main tab is a series of subtabs. and configure views. The Task pane is located on the left side of the console and contains the View pane. define user preferences. media usage fluctuates. Services. This icon is called Collapse Task Panel. Policies etc. the status of your backup environment is likely to change. add master server etc. add OpsCenter users. About refreshing the OpsCenter console As you use Symantec OpsCenter. under the Monitor tab there are subtabs like Overview. See “About the View pane” on page 51. See “About visual keys in the console” on page 57. an icon with a red dashed-circle represents a managed server that is Not Connected. Using OpsCenter views. More information about how to create views from Settings > Views is available. For example. As you navigate within the OpsCenter console. Uses unique icons and colors to convey operational states. ALL MASTER SERVERS is the default view in the View pane. You can create views from Settings > Views or by using the Java View Builder. ■ Figure 1-3 shows a sample View pane in which ALL MASTER SERVERS view is selected. The View pane has the following features: ■ ■ Is available in any OpsCenter view where you can change the view. This pane lets you select the views to control the scope of your console views. See “About OpsCenter views ” on page 307. you can create a view like Geography to view details about master servers in a particular region like Europe. Lets you access and change the views that you monitor or manage. Using the View pane is one of the methods you can use to determine the scope of information that you view. or an individual server. Similarly a disabled master server is shown as a gray colored icon.Getting started using Symantec OpsCenter About OpsCenter console components 51 About the View pane The View pane is a key navigation and configuration tool in Symantec OpsCenter. . See the online Symantec OpsCenter Java View Builder Help to know how you can create views using Java View Builder. you can view NetBackup information for your whole management domain (in the case of ALL MASTER SERVERS view). a specific view type. You can also create client or policy views. your view selection applies for any subsequent screens until you select a different view. For example. it is recommended that you do not repeat a master server across groups. When you specifically deselect a master server from a view. . Consider a scenario where there are two objects server A and server B in a particular view like ALL MASTER SERVERS. For example. For this reason. the master servers that you may add later to this view or node are also automatically selected. For example. and in addition if you have selected a node that also contains server B. you can select the default view ALLMASTERSERVERS. which is also part of another selected view. all the master servers that are currently in the view or node are automatically selected. To select a specific master server. In addition. You may also deselect a specific master server from a view by selecting the view and then deselecting the specific master server. When you select a view like ALLMASTERSERVERS or a node that contains a group of master servers. server Bis not considered even though it is a part of the selected view or node. you can select a view and a node that contains a group of master servers and also specific objects. first deselect the view or node that contains the master server and then select the master server. In case. you have selected the ALL MASTER SERVERS view and then specifically deselected server B . the deselection or exclusion is given a higher priority because of which the master server is not considered.52 Getting started using Symantec OpsCenter About OpsCenter console components Figure 1-3 View pane description About selecting views from the View pane From the View pane. you may select only a specific master server(s) under the default view ALL MASTER SERVERS. You may also select only specific objects of a particular view or node. This is because you have specifically deselected server B from the ALL MASTER SERVER view. 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. You can also configure this polling interval. This level is same as the ThreatCon level which is shown on the following Web site: http://www. Figure 1-4 shows the Symantec ThreatCon pane in the OpsCenter console.Getting started using Symantec OpsCenter About OpsCenter console components 53 About the Symantec ThreatCon pane The Symantec ThreatCon pane shows the current ThreatCon level in the OpsCenter console. a task pane is available. See “Configuring Symantec ThreatCon feature in OpsCenter” on page 229. Using the quick links in the Task pane In many views in the console.symantec.jsp The Symantec ThreatCon pane is available in the OpsCenter console on the left-hand side. Table 1-8 Quick Link Oracle Cloning Alert Policies Quick links and where they point Destination Manage > Oracle Cloning Manage > Alert Policies . OpsCenter periodically polls the ThreatCon Web service and updates the data which is shown in the Symantec ThreatCon pane. You can also disable or enable the Symantec ThreatCon feature.com/security_response/threatcon/index. 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. Symantec ThreatCon feature is enabled by default. To enlarge the content pane ◆ Click the icon between the task pane and the content pane. the tabs and subtabs. the content pane displays a summary of information for all master servers in the OpsCenter console. a monitoring overview appears (Monitor > Overview). Using the content pane When you initially log on to Symantec OpsCenter. and the timeframe. Information in the content pane varies and is context sensitive to current selections in the View pane.54 Getting started using Symantec OpsCenter About OpsCenter console components 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. 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. . Click the icon again to show all panes. The minimize or maximize settings are applicable only for the current session. Only the icons for quick link tasks are visible when the quick links are minimized. This icon is called Collapse Task Panel. Click the maximize icon (up arrow) again to view the quick links. Note: The Quick links are shown by default in a maximized state. Initially. The minimize or maximize settings are applicable only for the current session. Also you cannot resize the Content pane from the Monitor > Overview page. For example. Use the drop-down list on the top-right corner of the OpsCenter console to switch between these views. Manage. The Details view is shown in the following figure. a Details view is also available. . Hierarchical. In addition to the above views. and Hierarchical View. 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. Note: Not all viewing modes are available for all Monitor and Manage views. you can view details about all NetBackup jobs (for a master server) in a tabular format using List View on the Monitor > Jobs page. A details view is available on some of the Monitor. The List and Hierarchical views present information in tabular formats. List View Drop-down list The Summary View presents information in a graphical format (pie charts). and Details views Most of the OpsCenter monitor and manage views present information in three main viewing modes: List View. You can view information about your NetBackup environment in any of the available views. Summary. and Settings pages.Getting started using Symantec OpsCenter About OpsCenter console components 55 Using the List. Summary View. The drop-down list is available in the applicable views. 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. Click the icon (up arrow) between the Details View and the upper part of the Content pane to maximize the Details View. .56 Getting started using Symantec OpsCenter About OpsCenter console components 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 on the Monitor > Jobs page (List View) shows detailed information about a specific job ID. 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. Or You can also drag the line separating the upper part of the Content pane and Details view to resize 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. The minimize or maximize settings are applicable only for the current session. For example. Information in the Details view can be viewed from tabs available in this view. or operation. This value updates when the view changes or refreshes. Symantec OpsCenter uses several visual keys. Investigate critical conditions immediately. 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. About visual keys in the console To help you understand the information it presents. or drive path. A server icon with a red dashed-circle means that the connection to the managed server is lost (Not Connected). These icon colors represent critical. Connected or Not Connected) for a managed NetBackup server. warning. ■ ■ About status icons Status icons are also used with color coding. These keys include color.Getting started using Symantec OpsCenter About OpsCenter console components 57 About the OpsCenter status bar The status bar at the bottom of the OpsCenter console shows a Page generated value. A reattempt to connect happens after 10 minutes. More information on how to specify your time zone is available. Blue-gray and gray often indicate enabled and disabled. Green indicates a normal condition. When OpsCenter detects a condition (for example. status icons. See “Setting user preferences” on page 223. result. the icon contains color coding. The Page generated value shows the date and time of the OpsCenter server you are logged on to (adjusted to match your time zone). and tool tips. For example. drive. About color coding This topic helps you to identify and understand the colors that are used along with status icons. the Monitor > Jobs view contains green icons for running jobs. or assigned and unassigned conditions respectively. These icons represent the shared drives that are up on all servers . Unique icons also appear in the drive details view for shared drives (the NetBackup SSO option). job. or informational conditions and let you quickly determine the status of a particular area in your NetBackup environment. About tool tips Tool tips provide brief descriptions of the tool and the status icons that appear in OpsCenter views. A managed server icon with a line through it denotes that the server is Partially Connected. The following is a sample table showing task icons. OpsCenter tries to reconnect to NBSL in every 10 minutes to collect data for the data types for which Collection Status is Failed. A server icon with a red dashed-circle means that a connection to the managed server is lost (Not Connected). .58 Getting started using Symantec OpsCenter About OpsCenter console components that share the drive. A tool tip appears when you place the mouse over an icon. For a partially connected master server. A gray colored server icon means that data collection for the managed server was disabled by the user. This section describes how to change the tables to display the information you want to see. Table 1-9 Icon Icons used for managed master servers Description A normal server icon means that the managed server is Connected. About using tables OpsCenter collects information about aspects of your NetBackup environment and presents much of this information in tables. A reattempt to connect happens after 10 minutes. Figure 1-5 shows the task options for tables. 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. 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. Edit. Sort columns in ascending or descending order Change the widths of columns See “Sorting the contents of a table column” on page 61. See “Accessing multiple pages of data in tables” on page 61. Pagination Select rows in tables .Getting started using Symantec OpsCenter About OpsCenter console components 59 Figure 1-5 Create. 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. 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. See “Selecting rows in tables” on page 61. See “Changing the width of a column” on page 61. Select the name of the column in Selected Columns. Click Move Up to move the column to the left in the table. Then click Add. 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. Then click Remove. Added columns appear as the last column in the table.60 Getting started using Symantec OpsCenter About OpsCenter console components The table refreshes after the operation and shows the changes you made. Initially. Click Move Down to move the column to the right in the table. Select a number from the Rows Per Page drop-down list . you may first have to remove one or more columns from the table and then add the missing columns. To view any of these columns. . To specify which columns appear in a table 1 2 Click the Table Settings icon at the top-right corner of the table. Each user can have different customized table settings. Add any columns that currently do not appear by selecting the column in the Available Columns list. Specifying which columns appear in a table Use the following procedure to specify which columns appear in a table. Remove columns you do not want to appear by selecting the column in Selected Columns. For these operations. 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. some OpsCenter tables do not show all available columns. 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 Apply To All Tables if you want the Rows Per Page setting to apply to all tables in OpsCenter (includes reports). OpsCenter saves and reloads your customized settings when you log on to the OpsCenter server again. To sort the contents of a column or multiple columns ◆ In a table. To select a row in a table ◆ Click the check box for that row. Click the check box again to deselect the selected row. Accessing multiple pages of data in tables Much of the monitoring information appears in a table format. use the table page controls. To go to a specific page ◆ Click the page number. To change the width of a column 1 2 Select the edge of the column heading and hold down the left mouse button. To go to the first or the last page ◆ Click the double left arrow or the double right arrow. Changing the width of a column Use the following procedure to change the width of a column. To display the next 10 rows or to return to a previous set of rows in large tables. click the column name again. Drag the edge of the column heading to the right or left. You can also change the number of rows to be displayed in the table from the Table Settings icon. .Getting started using Symantec OpsCenter About OpsCenter console components 61 Sorting the contents of a table column Use the following procedure to sort the contents of a column or multiple columns. you must select a row or rows to enable the tasks. click the column name. To go to the previous or the next page ◆ Click the left arrow or the right arrow. When you have more data to display than can fit in a table. The column sorts in ascending order by default. Use the table page controls (located below the table) to help you navigate the pages. OpsCenter tables display 10 rows at one time by default. Selecting rows in tables For many tables in OpsCenter. the table contains multiple pages. To sort in descending order. . Click the check box again to deselect all selected rows. The view remains in effect until you change it by selecting another filter. or remove a filter. a calendar icon appears for Value. 4 From the drop-down list. If you select Start Time or End Time for Column. Type a name for the filter in the Name field. select another column. 6 Click OK when you finish building the filter. For Column. For Value. edit. To create a custom filter 1 2 3 Select the Create filter icon.62 Getting started using Symantec OpsCenter About OpsCenter console components To select all rows on the current page of the table ◆ Click the check box in the header row of the table. select And or Or to build the filter query. 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. select a custom filter or a OpsCenter built-in filter. Click the calendar icon to choose a date and time and then click OK. apply. select the column name that you want to filter on from the drop-down list. A filter screens information that is based on a set of conditions that you define. click Add to add another clause to the query. If the clause is not what you want. filtering icons appear above the table. you can save it. OpsCenter filters the table according to the criteria you specify. To apply a filter ◆ From the drop-down list. or by using the predefined (ready-to-use) filters. The following procedures describe how you can create. enter or select a value. Your new filter is available in the filter drop-down list. select an operator. For Link. Use != if you do not want to match a specific value. In the views that allow filtering. edit it. 5 To continue building the filter. or remove it. Repeat 3 and 4. click Remove to remove the clause from the query. Once you create a filter. For Operator. This lists the instructions for using the dialog to edit a filter. See “Configuring SMTP server” on page 228. To remove a custom filter 1 From the drop-down list. select a custom filter. Click OK to remove the filter. 2 3 Click the Delete filter icon. About quickly performing common tasks in OpsCenter Table 1-10 lists the common tasks and the corresponding links to the documentation. . See “To create a custom filter” on page 62. You can only modify custom filters. See “Managing recipients” on page 243. Note: You cannot delete the ready-to-use or built-in filters. Note: You cannot modify the ready-to-use OpsCenter filters. Make your changes and click OK. See “Managing users” on page 235.Getting started using Symantec OpsCenter About quickly performing common tasks in OpsCenter 63 To edit a custom filter 1 From the drop-down list. 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 “Setting user preferences” on page 223. 2 3 Click the Edit filter icon. select a custom filter. Note: This feature is available with a licensed version (Symantec OpsCenter Analytics). 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). See “Monitoring NetBackup policies” on page 350. Understand and use OpsCenter reports See “About OpsCenter reports” on page 457. About using Web browser bookmarks By using your Web browser. collect data from Symantec as well as third-party products. It includes information about how to monitor and manage NetBackup. See “Managing a job policy” on page 356. View and respond to OpsCenter alerts See “Managing an alert policy ” on page 407.pdf) provides information on how to use OpsCenter. 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. If you log out of the OpsCenter console. Schedule when you want a report to run See “Managing report schedules” on page 479. generate alerts. See “Monitoring NetBackup services” on page 348. See “Exporting NetBackup job logs” on page 339. About OpsCenter documentation The Symantec OpsCenter Administrator's Guide (NetBackup_AdminGuide_OpsCenter. . you can add a bookmark for any view in the OpsCenter console and return to it as needed. and create various reports.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. Create custom reports for your needs See “Creating a custom report” on page 468. you can use the bookmark to return to the same view after you log onto the console. Configuring OpsCenter views Create OpsCenter alert policies for your See “Creating (or changing) an alert policy” site on page 394. which is regularly updated on the Symantec Support Web site. Man Pages for Utilities . Man pages are used to find reference and usage information about product-specific commands on UNIX computers.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. In the OpsCenter console.com/business/support/index. OpsCenter is shipped with man pages / manual pages for various utilities that you can run from command prompt. supported products or operating systems. NetBackup Status Codes Help This context-sensitive Help provides troubleshooting information about NetBackup status codes. Access the following URL: http://www. Table Settings Help This HTML help provides information on how you can change the settings of a table in the OpsCenter console. 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. To access this Help. see the Symantec NetBackup Hardware and Software Compatibility List. for example.Getting started using Symantec OpsCenter About OpsCenter documentation 65 Symantec OpsCenter Administrator's Guide is available on the product CD. OpsCenter is also shipped with the following online Help documents: OpsCenter Context-sensitive This WebGUI Help contains all information about the Help OpsCenter GUI. You can access the context-sensitive Help by clicking the ‘Help’ button available on a dialog box in the Java View Builder console. Note: For the latest support information. click the Help button on the Table Settings pop-up screen. It provides context-sensitive help pages for all GUI screens. click Monitor > Jobs and click a status code link in the jobs table to view its details.symantec. 66 Getting started using Symantec OpsCenter About OpsCenter documentation . About components shared with other Symantec applications The following components are used by OpsCenter and are also shared with other Symantec applications. OpsCenter uses some common Symantec components that are shared. before you proceed to OpsCenter installation or upgrade.Chapter 2 Installing Symantec OpsCenter This chapter includes the following topics: ■ ■ ■ ■ ■ ■ ■ 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. . About the software components that OpsCenter uses Along with OpsCenter specific components. JRE (Java Runtime Environment ) The Symantec OpsCenter Web server and the OpsCenter application require this component. Veritas Unified Logging (VxUL) This logging component is installed with OpsCenter Server and Agent and is used to configure and view OpsCenter logs. which reduces the number of ports in the firewalls that must be open to operate products. Note that there is no requirement for Symantec Product Authorization Service to be installed. Symantec Product Authentication Service (AT) This service is primarily used for user logon authentication and is required for secure communication between OpsCenter Agent.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. the PBX port number can be changed using PBX configuration files. AT is also used for secure communication between NetBackup master servers and the OpsCenter server software. See the files in the docs directory of the NetBackup DVD for information on authentication services. The OpsCenter server needs to be a legitimate server that is allowed to talk to NBU. View Builder. ■ Symantec Java Web server The OpsCenter Web GUI and the reporting service runs under Symantec Java Web server . and the OpsCenter server software. ■ ■ Symantec OpsCenter specific components The following components are used only by OpsCenter and are not shared with other Symantec applications. See the NetBackup Troubleshooting Guide for more information about VxUL logs. Also. there is no requirement for NetBackup Service Layer (NBAC) to be configured on your managed NetBackup master servers. the OpsCenter server must appear in the server list. Changing the PBX port number on the server where OpsCenter is installed may cause OpsCenter to fail. PBX also integrates with the Symantec Product Authentication Service to allow for authenticated connections in addition to non-authenticated connections. wherein. OpsCenter GUI. Since it is an independent component. See Security and Encryption Guide in the NetBackup DVD for information about NBAC. ■ . add a license key to enable OpsCenter Analytics.NetBackup set up with 100 backup clients and OpsCenter . the license option called Archive Mailbox is added. The licensed version of OpsCenter is called Symantec OpsCenter Analytics.com/support/manuals.Installing Symantec OpsCenter Planning an OpsCenter installation 69 ■ Sybase database . . This is visible from the title bar and logon page of the OpsCenter console. See http://www. The unlicensed version of OpsCenter is called Symantec OpsCenter. If you have a license for 1000 mailboxes. you must add the appropriate license key.OpsCenter uses a Sybase SQL Anywhere 11 (Sybase 11) database installation that is separate from the NetBackup database. For example: You have an OpsCenter . on the Settings > Configuration > License page. You need to purchase a license that enables you to report on 100 backup clients and 500 mailboxes. The license option is visible in the OpsCenter console. it is added as 'Archive Mailbox' as shown in the figure. While installing OpsCenter. More information about the Sybase component is available.sybase. If you wish to enable additional functionality. 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.Enterprise Vault set up with 500 mailboxes to report on. if you install Symantec Enterprise Vault enabled licensing key. About the OpsCenter licensing model OpsCenter requires no license. These entries show that the actual usage of Archive mailbox license option is 0 while the licensed value is 1000.70 Installing Symantec OpsCenter Planning an OpsCenter installation 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. 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. The purpose of the demo key is to enable you to try the product before you purchase it. 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. you can do advanced reporting. . collect data from third-party products like IBM Tivoli Storage Manager (TSM) and EMC Legato NetWorker etc. create custom reports. With a licensed version. To know this compare the Value and the Usage column from the Settings > Configuration > License page in the OpsCenter console. Permanent key You can access the licensed features with both demo and permanent keys. A permanent key does not have an expiry date. create and customize multi-level views using Java View Builder.Installing Symantec OpsCenter Planning an OpsCenter installation 71 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. from the title bar and logon page of the OpsCenter console. viewing report data for any previous date etc. advanced business-level reporting. delete. About Symantec OpsCenter and Symantec OpsCenter Analytics Table 2-1 lists the differences between Symantec OpsCenter and Symantec OpsCenter Analytics. running or configuring chargeback reports. you have additional reporting functionality like creating custom reports. NetWorker. See “Managing licenses” on page 226. With Symantec OpsCenter Analytics. creating reports using SQL queries. or view license keys after installation from the OpsCenter console. You can also add. 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. See “About the OpsCenter Analytics licensed features” on page 72. You can also collecting data from third-party products like: ■ ■ ■ IBM TSM EMC Legato More information about the licensed features is available. . 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 lets you do operational Symantec OpsCenter Analytics lets you do reporting. 72 Installing Symantec OpsCenter Planning an OpsCenter installation 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 Installing Symantec OpsCenter Planning an OpsCenter installation 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 Installing Symantec OpsCenter Planning an OpsCenter installation 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 Installing Symantec OpsCenter Planning an OpsCenter installation 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 Installing Symantec OpsCenter Planning an OpsCenter installation 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 Installing Symantec OpsCenter Planning an OpsCenter installation 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 Installing Symantec OpsCenter Planning an OpsCenter installation 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. Backup or Archiving product 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 Installing Symantec OpsCenter Planning an OpsCenter installation 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 Administrator’s Guide, Volume II for more information about NBSL. 80 Installing Symantec OpsCenter Planning an OpsCenter installation 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 Installing Symantec OpsCenter Planning an OpsCenter installation 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 Installing Symantec OpsCenter Planning an OpsCenter installation 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. You can use the inbuilt Agent of the OpsCenter Server for data collection. See “Configuring PureDisk data collector” on page 291. PureDisk You don't need a separate Agent to collect data from PureDisk. You need separate OpsCenter Agents for Legato servers with different versions. as Backup Exec supports only Windows platform. 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 . an Agent must be installed to collect specific data (scheduled jobs. Agent needs to be installed on the Legato server host. image. . you need to install the Agent on a Windows host. as Enterprise Vault supports only Windows platform. Note: A NetBackup 7. select the Agent that is installed as Integrated Agent. EMC Legato Networker Enterprise Vault Note: To collect Enterprise Vault / archive data. and error logs). About installing Agent on a product host OpsCenter Agent can be installed on a product host. you need to install the OpsCenter Agent on a Windows host. However for a master server whose version is less than 7. If you have installed the VBR Agent only for PureDisk data collection. Note: To collect data from Backup Exec Server host. You can use the same OpsCenter Agent to collect Enterprise Vault data from Microsoft SQL Servers with different versions. Note: You do not require an OpsCenterAgent to collect data from PureDisk. Backup Exec You can use same Agent to collect data from Backup Exec Servers with different versions.0 master server does not require any Agent for data collection.Installing Symantec OpsCenter Planning an OpsCenter installation 83 NetBackup You need separate Agents to collect data from different versions of NetBackup master server . IBM TSM You can use same OpsCenter Agent to collect data from TSM servers with different versions. you must manually uninstall the VBR Agent.0. To create or configure the data collector. The following products support Remote Agent installation: ■ Symantec Enterprise Vault . ■ In such situations. 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. Minimal intrusion on backup hosts. Installing Agent in this fashion has a very low effect on the backup environment by adding agent. The different host may be the OpsCenter Server host or a separate host. you only service one host. The OpsCenter Agent must support the operating system of the backup application host. When host system has insufficient resources to support colocation of agent and backup application. for example HP-UX.84 Installing Symantec OpsCenter Planning an OpsCenter installation 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. A disadvantage of installing the OpsCenter Agent on a remote backup application host is that the Agent may use significant system resources. one agent that is installed on a backup host. You should deploy Remote Agent in the following situations: ■ When OpsCenter Agent does not support the operating system of the product. Installing the Agent on a remote backup application host has the following advantages: ■ ■ Ease of maintenance to upgrade agent. the Agent should remotely communicate with backup products. You must install the Agent on the EMC Legato Networker host. which can affect the backup application host’s performance. Installing Symantec OpsCenter Planning an OpsCenter installation 85 ■ ■ Symantec NetBackup Symantec NetBackup PureDisk Note: PureDisk does not support local Agent installation. See “Collecting data from Enterprise Vault” on page 292. 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. For example. In some situations. 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. For back up products (except Backup Exec). 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. you need separate OpsCenter Agents to collect data from different versions of NetBackup Master Server. ■ 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. You need to maintain only one machine for both OpsCenter Server and agent. ■ .exe) on the Agent host to collect data remotely. UNIX platforms do not support RAC. because OpsCenter does not support PDOS (PureDisk Operation System). you need to have backup application client (. which avoids the maintenance that might otherwise be involved in upgrading the agent. a backup application license key is required for the component that is installed on the OpsCenter Server host. to collect data from another master server that you want to monitor / report on. 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. 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.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. OpsCenter Server is installed on OpsCenterHost 1.0 master server is installed on ProdHost 1 and NetBackup 6.86 Installing Symantec OpsCenter Planning an OpsCenter installation Examples of Agent deployment in a NetBackup setup In a NetBackup setup.5 Remote Admin Console or NetBackup master server on OpsCenterHost 1 and configure a data collector to collect data from ProdHost 1.5 master server is installed on ProdHost 2.5 master server is installed on . OpsCenter Server and Agent are installed on OpsCenterHost 1. NetBackup 6. NetBackup 6. Agent A1 is installed on AgentHost 1.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. Agent is installed on AgentHost 1. and NetBackup 6.5 Remote Admin Console or master server on OpsCenterHost 1 and configure two data collectors. You need to install NetBackup 6. and Agent A2 is installed on AgentHost 2. .5 master server is installed on ProdHost 2. one to collect data from ProdHost 1 and another to collect data from ProdHost 2. You need to install NetBackup 6. and ProdHost 1 another 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. the following OpsCenter deployment scenarios are valid: ■ OpsCenter Server is installed on OpsCenterHost 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. See “Design your OpsCenter server” on page 80. If a file called 'program' exists in the C: folder of your OpsCenter server. Ensure that no other installation is in progress while installing OpsCenter. Ensure that the fully qualified domain name (FQDN) of your OpsCenter server has maximum 44 characters. 8. the database grows in size. &. install OpsCenter on the NetBackup master or media server (recommended). ensure that the database directory has at least 20 MB of available space. If you need to monitor a single master server. 3. Ensure that the name of the folder in which you are installing OpsCenter does not contain any special characters like %. 4. rename. first upgrade to one of the supported versions. See “About communication and firewall considerations” on page 205. See “About platforms supported by OpsCenter” on page 74. or delete the file before installing OpsCenter. For fresh OpsCenter installation.0 NOM 6. See the NOM documentation for details on how to perform this upgrade. If you are upgrading from NOM to OpsCenter . !. Latest Maintenance Pack of NOM 6. #. and requires more space. 11. Ensure that your OpsCenter server is configured as a fixed host with a static IP address. ensure that you have one of the following NOM versions installed: ■ ■ 9. @. $. 6.5 and higher versions If you are upgrading from a NOM version not listed above.Installing Symantec OpsCenter Planning an OpsCenter installation 87 Table 2-5 Serial No. 5. 10. Ensure that the antivirus software is disabled before installing OpsCenter. OpsCenter install and upgrade checklist for Windows Checklist Ensure that you install OpsCenter software on a supported platform. Ensure that the necessary ports are opened before installing OpsCenter on a hardened server. Note that once you install and start using OpsCenter. 2. . 1. 7. ~. ^. first upgrade to one of the supported versions.1 VBR 6. 4. Ensure that no other installation is in progress while installing OpsCenter. 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. 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. See the VBR documentation for details on how to perform this upgrade. 12. Table 2-6 Serial No. See “Design your OpsCenter server” on page 80. See “Design your OpsCenter server” on page 80. VBR 6.88 Installing Symantec OpsCenter Planning an OpsCenter installation Table 2-5 Serial No. ensure that the database directory has at least 20 MB of available space. Ensure that your OpsCenter server is configured as a fixed host with a static IP address. 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. For example. the database grows in size. the database grows in size. VBR 6.6.5. 1. .1. 3. Note that once you install and start using OpsCenter.5. For fresh OpsCenter installation. 2. 6. ensure that the OpsCenter database directory has thrice as much space (3x) as that taken by your NOM database or VBR database (x). If upgrading from VBR or NOM. See “About platforms supported by OpsCenter” on page 74.6. 5. if your NOM database or VBR database is 1 GB. and requires more space.1. and requires more space.5. OpsCenter install and upgrade checklist for UNIX Checklist Ensure that you install OpsCenter software on a supported platform. then the OpsCenter database directory must have at least 3 GB of available space. 13. Note that once you install and start using OpsCenter.1 If you are upgrading from a VBR version not listed above. VBR 6. 0 MP7 NOM 6. and requires more space. VBR 6. Latest Maintenance Pack of NOM 6. . If you upgrade from NOM to OpsCenter . if your NOM database or VBR database is 1 GB. the database grows in size. If you are upgrading from VBR to OpsCenter Analytics. See “About communication and firewall considerations” on page 205.6. install OpsCenter on the NetBackup master or media server (recommended). See “Design your OpsCenter server” on page 80.6. OpsCenter install and upgrade checklist for UNIX (continued) Checklist Ensure that the necessary ports are opened before installing OpsCenter on a hardened server. first upgrade to one of the supported versions.1.5.1 VBR 6.Installing Symantec OpsCenter Planning an OpsCenter installation 89 Table 2-6 Serial No. 7.0 or higher. If you are upgrading from VBR or NOM. Note that once you install and start using OpsCenter.5 and higher versions If you are upgrading from a NOM version not listed above. ensure that the XLC runtime version is 9.1 If you are upgrading from a VBR version not listed above. 10. first upgrade to one of the supported versions. See the NOM documentation for details on how to perform this upgrade. See the VBR documentation for details on how to perform this upgrade. VBR 6. ensure that the OpsCenter database directory has thrice as much space as that taken by your NOM database or VBR database. For example. 8. If you need to monitor a single master server.1. ensure that you have one of the following NOM versions installed: ■ ■ 9. 11.5. then the OpsCenter database directory must have at least 3 GB of available space. If installing OpsCenter on an AIX platform. ensure that you have one of the following VBR versions installed: ■ ■ VBR 6. VBR 6.5. 12. You can use this table as a checklist while installing Symantec OpsCenter. See “Upgrading to OpsCenter on Windows and UNIX” on page 102.90 Installing Symantec OpsCenter Installing Symantec OpsCenter on Windows and UNIX Table 2-6 Serial No. See “Clustering Symantec OpsCenter” on page 166. Installing Symantec OpsCenter on Windows and UNIX This section describes the procedures for fresh installation of OpsCenter on Windows and UNIX hosts. This backed up data can then be restored on the supported OpsCenter platform during installation. run the Backup. 13.sh script from the Server directory of the OpsCenter DVD to back up the necessary data. See “Design your OpsCenter server” on page 80. . You can also upgrade from an earlier NOM or VBR installation. Table 2-7 provides steps to install OpsCenter components. 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). You can install OpsCenter in a clustered mode. properly. See “About platforms supported by OpsCenter” on page 74. See “About OpsCenter Agent deployment” on page 81. Note: After installation. carefully. and clustering. Make sure that you satisfy the operating system requirements. . Go through the Agent deployment section. See “About communication and firewall considerations” on page 205. 2 Go through the appropriate installation section. The OpsCenter DVD contains OpsCenter software for all available platforms. verify if OpsCenter is running UNIX” on page 96. you should wait for some time before installing other OpsCenter components. See “Installing Symantec OpsCenter on Windows” on page 91. The NetBackup media kit contains a separate DVD for each platform. See “Installing Symantec OpsCenter on See “Upgrading to OpsCenter on Windows and UNIX” on page 102. upgrade. Review the hardware / software requirements for OpsCenter Server and Agent hosts. Additionally after an installation is complete. Go through the firewall settings and port number information. See “Before you install or upgrade” on page 86. You may install OpsCenter from the OpsCenter DVD or from the NetBackup media kit. See “Clustering Symantec OpsCenter” on page 166. Installing Symantec OpsCenter on Windows Use the Installation Wizard to install OpsCenter on a Windows host. Review the Install/Upgrade checklists before installing OpsCenter.Installing Symantec OpsCenter Installing Symantec OpsCenter on Windows and UNIX 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. Note: You must not run any other installation while installing OpsCenter components. Different sections are available for fresh installation. type ‘D:\Browser. the Symantec DVD Browser appears. Click Next. Ignore this step if you install OpsCenter server software from the OpsCenter DVD. 3 4 On the Symantec DVD browser. The Symantec DVD Browser appears. Click the OpsCenter Server Installation link to install Symantec OpsCenter server. 2 ■ ■ If autorun is enabled. click the Installation link. On the Run dialog box. the installer runs in a Maintenance mode and lets you repair or remove the OpsCenter component that is installed on your system. click Start > Run. in the Open text box.92 Installing Symantec OpsCenter Installing Symantec OpsCenter on Windows and UNIX Installing Symantec OpsCenter Server on Windows Use the following procedure to install Symantec OpsCenter server on Windows hosts.exe’ and press Enter: Where D is the DVD drive. The Symantec OpsCenter Installation Wizard appears. The OpsCenter DVD contains OpsCenter software for all available platforms. check ‘I accept the terms of the license agreement’ and click Next. You may install OpsCenter from the OpsCenter DVD or from the NetBackup media kit. Read the license agreement. click OpsCenter Software Installation. Note: In case you try to install OpsCenter components on a system where OpsCenter is already installed. If autorun is not enabled. 5 6 7 . To install OpsCenter Server on Windows 1 On a Windows host where you want to install OpsCenter server. If you use the NetBackup media kit to install OpsCenter. The NetBackup media kit contains a separate DVD for each platform. insert the appropriate OpsCenter product DVD in the DVD drive. This option is enabled if you have Veritas Cluster Server (VCS) installed. you get an unlicensed version. 9 In the Installation Method section. . 10 On the License Keys screen.Installing Symantec OpsCenter Installing Symantec OpsCenter on Windows and UNIX 93 8 The following options are displayed: Install to this computer only Select this option to install OpsCenter Server on this host. Note: Click Custom if you want to change the default settings. The installer shows the summary of the settings that you have selected for installation. installation location. enter your demo or permanent key that you have received with the purchase of OpsCenter and click Add Key. Also compare the space that is required by the installation with the actual space available in the installation directory. You can also add the license keys later from the OpsCenter console. locations. Install a clustered OpsCenter Select this option to install OpsCenter Server on all Server selected nodes. Select Install to this computer only. See “Clustering Symantec OpsCenter on Windows” on page 167. Check Save Summary to field to save the installation summary. See “Clustering Symantec OpsCenter Server on UNIX” on page 173. Click Next. 11 Click Next. in a clustered mode. or port numbers. You need to install OpsCenter Server manually on each node of the cluster. click Typical to use the default settings. you cannot access the licensed features. See “About the license keys” on page 70. With the unlicensed version (Symantec OpsCenter). Click Browse to save the installation summary in your preferred location. If you do not enter a key. See “Managing licenses” on page 226. or port numbers. type ‘D:\Browser. 3 ■ ■ If autorun is enabled. 2 On a Windows host where you want to install OpsCenter Agent. Click Next. or a separate host. Note: The default OpsCenter database location on Windows is: C:\Program Files\Symantec\OpsCenter\server\db\data 13 After successful installation. Installing Symantec OpsCenter Agent on Windows Use the following procedure to install Symantec OpsCenter Agent on a Windows host. If you use the NetBackup media kit to install OpsCenter Agent. If autorun is not enabled. insert the appropriate OpsCenter product DVD in the DVD drive. review the information on Agent deployments. product host. The Symantec DVD Browser appears. click Start > Run. The installer starts installing the OpsCenter Server software. click OpsCenter Software Installation. The OpsCenter DVD contains OpsCenter software for all available platforms. The NetBackup media kit contains a separate DVD for each platform. 6 7 . To decide where you want to install the OpsCenter Agent. Click the OpsCenter Agent Installation link to install OpsCenter Agent. You may install OpsCenter Agent from the OpsCenter DVD or from the NetBackup media kit. click the Installation link. The Symantec OpsCenter Installation Wizard appears.exe’ and press Enter: Where D is the DVD drive. the Symantec DVD Browser appears. you can view the OpsCenter console or view installation logs.94 Installing Symantec OpsCenter Installing Symantec OpsCenter on Windows and UNIX 12 Click Install. To install OpsCenter Agent 1 You can install the OpsCenter Agent either on the OpsCenter Server host. in the Open text box. Ignore this step if you install OpsCenter Agent software from the OpsCenter DVD. On the Run dialog box. See “About OpsCenter Agent deployment” on page 81. 14 Click Finish. 4 5 On the Symantec DVD Browser. To install OpsCenter to a different directory. 13 Click Finish. insert the appropriate OpsCenter product DVD in the DVD drive. The installer starts installation of OpsCenter Agent. If autorun is not enabled. the Symantec DVD Browser appears. The NetBackup media kit contains a separate DVD for each platform. On the Run dialog box. Click Next. check ‘I accept the terms of the license agreement’ and click Next.exe’ and press Enter: Where D is the DVD drive. Check Save Summary to field to save the installation summary. The default installation location is C:\Program Files\Symantec. 3 On the Symantec DVD Browser. click Browse. 10 The installer shows the summary of the settings that you have selected for Agent installation. you can view Agent installation logs or open the readme file. 12 After successful installation. 11 Click Install. 2 ■ ■ If autorun is enabled. click the Installation link. Installing Symantec OpsCenter View Builder on Windows Use the following procedure to install Symantec OpsCenter View Builder. You may install OpsCenter from the OpsCenter DVD or from the NetBackup media kit. To install OpsCenter View Builder 1 On the OpsCenter Server host. . The OpsCenter DVD contains OpsCenter software for all available platforms. The Symantec DVD Browser appears.Installing Symantec OpsCenter Installing Symantec OpsCenter on Windows and UNIX 95 8 9 Read the license agreement. in the Open text box. type ‘D:\Browser. Click Browse to save the installation summary in your preferred location. click Start > Run. Note: The default installation location on a Windows 64-bit machine is C:\Program Files (x86)\Symantec. 13 Click Finish. Ignore this step if you install OpsCenter View Builder software from the OpsCenter DVD. The Symantec OpsCenter Installation Wizard appears. . Note: If installing OpsCenter on AIX. Symantec OpsCenter View Builder installation. You may install OpsCenter from the OpsCenter DVD or from the NetBackup media kit. 5 6 7 8 9 Select a new location and click Next.96 Installing Symantec OpsCenter Installing Symantec OpsCenter on Windows and UNIX 4 If you use the NetBackup media kit to install OpsCenter View Builder. On the Installation Location screen. Check Save Summary to field to save the installation summary. Note: The default installation location on a Windows 64-bit machine is C:\Program Files (x86)\Symantec. The NetBackup media kit contains a separate DVD for each platform. Click the OpsCenter View Builder Installation link to install Symantec OpsCenter View Builder. 10 The installer shows the summary of the settings that you have selected for 11 Click Install. Read the license agreement. click Browse if you want to change the default location for Symantec OpsCenter View Builder installation. Click Browse to save the installation summary in your preferred location. ensure that the XLC runtime version is 9. The installer starts installation of Symantec OpsCenter View Builder. Installing Symantec OpsCenter on UNIX This section provides you with the procedure to install OpsCenter on a UNIX host. you can view the installation logs or open the readme file. Click Next. 12 After successful installation. The OpsCenter DVD contains OpsCenter software for all available platforms.0 and higher. check ‘I accept the terms of the license agreement’ and click Next. click OpsCenter Software Installation. AT./install. Type the following command:. Press Enter. The OpsCenter DVD contains OpsCenter software for all available platforms. 6 The installer displays a list of components that get installed like PBX. Press Enter. navigate to the appropriate OpsCenter platform directory and then the Server directory on the DVD. cd OpsCenter/Server Type the following command:. Symantec Database etc. . To install OpsCenter Server on UNIX 1 2 Open a UNIX console and log on as root on the target host. The installer also examines the system for existing packages. Symantec WebGUI Server./installOpsCenterServer. Press Enter to continue. 3 Do one of the following: ■ If you use the OpsCenter DVD to install OpsCenter server software. navigate to the Server directory. It prompts you in case OpsCenter is already installed. The installer then checks if OpsCenter Server is installed on the system or not.Installing Symantec OpsCenter Installing Symantec OpsCenter on Windows and UNIX 97 Installing Symantec OpsCenter Server on UNIX Use the following procedure to install OpsCenter server software on UNIX hosts. Mount the OpsCenter product DVD for the appropriate platform on which you are installing. 4 5 The Welcome message is displayed. the installer also asks for installing Server or Agent if you are installing from OpsCenter DVD. Review this list and press Enter to continue. The NetBackup media kit contains a separate DVD for each platform. ■ If you use the NetBackup media kit to install OpsCenter. You may install OpsCenter from the OpsCenter DVD or from the NetBackup media kit. For Solaris Sparc. the following information is displayed: Directory "/var/symantec" does not exist. By default. In case the database installation directory (/var/symantec) does not exist on the host. To accept the default path (/opt).q] y Type y to confirm and press Enter. press Enter without typing a directory path. temporary files will be created in the database installation directory /var/Symantec/OpsCenterServer . 8 9 Type y to confirm the directory path and press Enter. Non default installation is not supported on AIX platform.n. press Enter without typing a directory path.98 Installing Symantec OpsCenter Installing Symantec OpsCenter on Windows and UNIX 7 The installer prompts you with the following question: Where do you want to install Symantec OpsCenter? </opt> Type a directory path where you want to install the Symantec OpsCenter Server packages and press Enter. the script creates the folder OpsCenterServer below your directory. The following information is displayed: The OpsCenter database server may require up to 1 GB of temporary space at runtime. Type a directory path under which to install the OpsCenter database and press Enter. If you create an alternate database directory. OpsCenter server is installed on the system. To accept the default database installation directory (/var/Symantec). Do you want to create the directory? [y. . 11 Review the installation options you selected.n. type y and press Enter.q] (n) To use the database installation directory for database server temporary space. The location of database directory and the database temp directory is also displayed.Installing Symantec OpsCenter Installing Symantec OpsCenter on Windows and UNIX 99 10 You are prompted with the following message: Would you like to use an alternate directory for database server temporary space? [y. 12 Type y and press Enter to confirm the selection and continue. press Enter without typing a directory path. To specify an alternate directory. Type a directory path for the database server temporary space and press Enter. Type n and press Enter to repeat the configuration steps and revise your selection. You are prompted with the following question: Do you want to restore data that has been backed up manually [y. To upgrade on a different server or platform.q] <n> If you have not been using NOM or VBR and are only installing OpsCenter for the first time. You can also add the license keys later from the OpsCenter console. 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. See “Managing licenses” on page 226. Installing Symantec OpsCenter Agent on UNIX Use the following procedure to install OpsCenter Agent on UNIX. you cannot access the licensed features. you get an unlicensed version.100 Installing Symantec OpsCenter Installing Symantec OpsCenter on Windows and UNIX 13 Configuration changes are made to the system. With the unlicensed version (Symantec OpsCenter).n. See “Upgrading to OpsCenter Server on a different UNIX system” on page 148. An example scenario is when NOM or VBR is running on Solaris 8 and you require the same data with OpsCenter on Solaris 10. More information on how to upgrade to OpsCenter server on a different system is available. The Backup.sh script is located in the Server directory of the OpsCenter DVD. 14 You are prompted for license information.sh script to back up your data on the NOM or VBR server and then copy it to the OpsCenter server. Use this option if you are upgrading from NOM or VBR to OpsCenter server software on a different UNIX system. See “About the license keys” on page 70. If you do not enter a key. . you do not need to restore any data. use Backup. Type n and then press Enter. The installer then checks if OpsCenter Agent is installed on the system or not./installOpsCenterAgent. navigate to the appropriate OpsCenter platform directory and then the Agent directory on the DVD. It prompts you in case OpsCenter Agent is already installed. If you use the NetBackup media kit to install OpsCenter Agent. Press Enter to continue. To configure OpsCenterAgent now. navigate to the following location: cd OpsCenter/Agent ■ Type the following command: .Installing Symantec OpsCenter Installing Symantec OpsCenter on Windows and UNIX 101 To install OpsCenter Agent on UNIX 1 2 Open a UNIX console and log on as root on the target host. Press Enter. Type the following command: . Press Enter. The OpsCenter DVD contains OpsCenter software for all available platforms. For Solaris Sparc. 4 Type the following command: . Mount the appropriate OpsCenter product DVD for the platform on which you are installing. 7 8 The installer displays a list of components that get installed like PBX./installOpsCenterAgent./install. The NetBackup media kit contains a separate DVD for each platform. Symantec WebGUI Agent etc. You may install OpsCenter from the OpsCenter DVD or from the NetBackup media kit. You may choose to configure OpsCenter Agent later either manually or by running . Press Enter. ./opt/VRTS/install/installOpsCenterAgent -configure command. 3 Do one of the following: ■ If you use the OpsCenter DVD to install OpsCenter Agent. 5 6 The Welcome message is displayed. type y and press Enter. It is optional to configure the OpsCenter Agent during installation. the installer also asks for installing Server or Agent if you are installing from OpsCenter DVD. Review this list and press Enter to continue. press Enter without typing a directory path. Data Movement etc. 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. Once the data collection is enabled. 11 The OpsCenter Agent is installed. 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. 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. . Type a directory path where you want to install the Symantec OpsCenter Agent packages and press Enter. The data for all these columns is shown after data collection for the master server is enabled during data migration.102 Installing Symantec OpsCenter Upgrading to OpsCenter on Windows and UNIX 9 Enter the location where you want to install OpsCenter Agent. this data is collected from the master server and shown on the OpsCenter console. and response files on the path mentioned. Upgrade considerations When you upgrade from Veritas Backup Reporter to OpsCenter Server and access the OpsCenter console. 10 Type y and then press Enter to confirm your installation options. summary. To accept the default path (/opt). You can view the installation log files. Owner. Parent. 2 ■ ■ If autorun is enabled. previous data is not collected from the master server. The NetBackup media kit contains a separate DVD for each platform. Note: You must not run any other installation while installing OpsCenter components. You may install OpsCenter from the OpsCenter DVD or from the NetBackup media kit. However for jobs and image.Installing Symantec OpsCenter Upgrading to OpsCenter on Windows and UNIX 103 Note: For most of the entities like policies. If autorun is not enabled. You can manually uninstall NOM after successfully migrating data and using Symantec OpsCenter for some time. To upgrade from NOM to Symantec OpsCenter on Windows 1 On a Windows host where you want to install OpsCenter server.exe’ and press Enter: .. you should wait for some time before installing other OpsCenter components. insert the appropriate OpsCenter product DVD in the DVD drive. devices etc. 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. It does not uninstall your existing NOM installation. all previous data is also collected once data collection is enabled. Upgrading from NetBackup Operations Manager to Symantec OpsCenter on Windows Use the following procedure to upgrade to OpsCenter server on Windows. During upgrade. the Symantec DVD Browser appears. The OpsCenter installer only stops the existing NOM services. click Start > Run. the older NOM database is saved and started. 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 and UNIX The OpsCenter Installation Wizard automatically detects an older NOM installation. Note that a saved copy of the NOM database is used for upgrade. The OpsCenter DVD contains OpsCenter software for all available platforms. On the Run dialog box. in the Open text box. You can access the data migration status page from the OpsCenter logon page. type ‘D:\Browser. OpsCenter server is installed. Additionally after an installation is complete. media. After you successfully upgrade to Symantec OpsCenter. locations. click OpsCenter Software Installation. If you use the NetBackup media kit to install OpsCenter. or port numbers. 7 8 9 Click Next. Ignore this step if you install OpsCenter server software from the OpsCenter DVD. click the Installation link. installation location. 3 4 On the Symantec DVD Browser. you can manually uninstall NOM. The Installation Wizard detects an existing installation of NetBackup Operations Manager on the system. or port numbers.5 5 6 Before you upgrade to Symantec OpsCenter. Click the OpsCenter Server Installation link to install Symantec OpsCenter server. The Symantec OpsCenter Installation Wizard appears. On the Installation Choice section. 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. Click Next. For example. check ‘I accept the terms of the license agreement’ and click Next. The Symantec DVD Browser appears. all existing NOM services are stopped automatically. Also compare the space that is required for installing OpsCenter server and the actual space that is available. Read the license agreement. . Note: Click Custom if you want to change the default settings.104 Installing Symantec OpsCenter Upgrading to OpsCenter on Windows and UNIX Where D is the DVD drive. click Typical to use the default settings. enter your demo or permanent key that you have received with the purchase of OpsCenter and click Add Key.Installing Symantec OpsCenter Upgrading to OpsCenter on Windows and UNIX 105 10 Specify a location for saving the old NOM database. 16 Click Finish. If you do not enter a key. Check Save Summary to option to save the installation summary. . 13 Click Next. Note: Ensure that the database location has adequate space by going through the Disk space requirements section on this page. Click Browse to save the installation summary in your preferred location. enter a port number on which the old NOM database can be started. 14 Click Install. The installer installs OpsCenter Server software. With an unlicensed version. you can view the OpsCenter console or view installation logs. 12 On the License Keys screen. Upgrading from NetBackup Operations Manager to OpsCenter on UNIX Use the following procedure to upgrade from NOM to OpsCenter on UNIX. A green checkmark appears in the Required column if there is adequate disk space. See “Monitoring data migration from NOM to Symantec OpsCenter” on page 120. See “About the license keys” on page 70. The installer shows the summary of the settings that you have selected for installation. you get an unlicensed version (Symantec OpsCenter). The default port number is 13799. Click Next. The default location is C:\Program Files\Symantec\OpsCenter\SavedData. you cannot access the licensed features. 11 On the Upgrade Settings page. Data migration from the old NOM database to the OpsCenter database starts once the Symantec OpsCenter Server service is started while installing OpsCenter server. 15 After successful installation. You can also access the data migration status from the OpsCenter console. Click Browse to specify a different location. You may install OpsCenter from the OpsCenter DVD or from the NetBackup media kit.q] y To upgrade to Symantec OpsCenter. 3 Do one of the following: ■ If you use the OpsCenter DVD to install OpsCenter. go to the following directory: cd OpsCenter/Server ■ 4 5 6 Type the following command:./installOpsCenterServer. Press Enter to continue. Do you want to upgrade from NOM <version> to Symantec OpsCenter [y. The Welcome message is displayed. Press Enter. AT. Symantec Database etc. If using the NetBackup media kit. go to the appropriate OpsCenter platform directory and then the Server directory. 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.n. It displays the following message when NOM is installed: NetBackup Operations Manager (NOM) <version> is installed on <hostname>. 7 The following message is displayed: The existing NOM database and configuration files must be backed up before upgrading to Symantec OpsCenter. Symantec WebGUI Server. press Enter. Review this list and press Enter to continue.106 Installing Symantec OpsCenter Upgrading to OpsCenter on Windows and UNIX To install OpsCenter Server on UNIX 1 2 Open a UNIX console and log on as root on the target host. type y and then press Enter. Mount the OpsCenter product DVD for the appropriate platform on which you are installing. The NetBackup media kit contains a separate DVD for each platform. (/var/symantec) Type the directory name in which the NOM database and configuration files can be saved and then press Enter. The OpsCenter DVD contains OpsCenter software for all available platforms. 8 The installer displays a list of components that get installed like PBX. To accept the default directory path (/var/symantec). The installer then checks for an existing NOM installation. . /var/Symantec/OpsCenterServer 12 You are prompted with the following message: Would you like to use an alternate directory for database server temporary space? [y.Installing Symantec OpsCenter Upgrading to OpsCenter on Windows and UNIX 107 9 Type a directory path where you want to install the Symantec OpsCenter Server packages and press Enter. 11 OpsCenter server is installed on the system. 10 Type y to confirm the directory path and press Enter. the script creates the folder OpsCenterServer below your directory. 14 Type y and press Enter to confirm the selection and continue. The following information is displayed: The OpsCenter database server may require up to 1 GB of temporary space at runtime. Type n and press Enter to repeat the configuration steps and revise your selection. press Enter without typing a directory path. . temporary files will be created in the database installation directory. 13 Review the installation options you selected. press Enter without typing a directory path. press Enter without typing a directory path. To use the database installation directory for database server temporary space. If you create an alternate database directory. To accept the default database installation directory (/var/Symantec).q] (n) Type a directory path for the database server temporary space and press Enter. By default. The location of database directory and the database temp directory is also displayed. To accept the default path (/opt). Type a directory path under which to install the OpsCenter database and press Enter.n. OpsCenter 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 after you successfully upgrade to OpsCenter. 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. You are prompted with the following message: The old database will be started separately to migrate its data to the OpsCenter database. Note that a saved copy of the VBR database is used for upgrade.108 Installing Symantec OpsCenter Upgrading to OpsCenter on Windows and UNIX 15 Configuration changes are performed. you get an unlicensed version (Symantec OpsCenter). Location of install log. You cannot access the licensed features by using the unlicensed version. . and response files. summary. You can manually uninstall VBR after upgrading successfully to Symantec OpsCenter. Note: Ensure that the port number that you enter is free and not used by any application. The OpsCenter installer only stops the existing VBR services. press Enter only. To accept the default port number (13799). It does not uninstall your existing VBR installation. 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. 16 You are prompted with the following message: Please enter a Symantec OpsCenter Analytics license key or press <Return>: To use a permanent key or a demo key. The following information is also displayed: ■ ■ ■ Web URL to access OpsCenter console. During upgrade. 17 All the OpsCenter services are started. If you do not enter any key and press Enter. type the license key and press Enter. Click the OpsCenter Server Installation link to install Symantec OpsCenter Server. Note: You must not run any other installation while installing OpsCenter components. Additionally after an installation is complete. and View Builder respectively. type ‘D:\Browser. 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. Upgrading from Veritas Backup Reporter to OpsCenter Analytics on Windows Use the following procedure to upgrade from Veritas Backup Reporter Server. Agent. If you use the NetBackup media kit to install OpsCenter. and View Builder to Symantec OpsCenter Server. The data migration process may take time depending on the data that has to be migrated. click OpsCenter Software Installation. Ignore this step if you install OpsCenter server software from the OpsCenter DVD. click the Installation link. You can also view the data migration process from the OpsCenter logon page. insert the appropriate OpsCenter product DVD in the DVD drive. On the Run dialog box. The Symantec DVD Browser appears. you should wait for some time before installing other OpsCenter components. 3 4 On the Symantec DVD Browser.exe’ and press Enter: Where D is the DVD drive. in the Open text box. Agent. the Symantec DVD Browser appears. The NetBackup media kit contains a separate DVD for each platform. To upgrade to OpsCenter Server on Windows 1 On a Windows host where you want to install OpsCenter server. If autorun is not enabled. The OpsCenter DVD contains OpsCenter software for all available platforms. You may install OpsCenter from the OpsCenter DVD or from the NetBackup media kit. 2 ■ ■ If autorun is enabled. 5 .Installing Symantec OpsCenter Upgrading to OpsCenter on Windows and UNIX 109 The data migration process happens for each master server. click Start > Run. Note: Click Custom if you want to change the default settings. The Installation Wizard detects an existing installation of Veritas Backup Reporter on the system. Click Browse to specify a different location. 10 Specify a location for saving the old VBR database. Read the license agreement. Click Next. you must manually uninstall VBR server software.110 Installing Symantec OpsCenter Upgrading to OpsCenter on Windows and UNIX 6 The Symantec OpsCenter Installation Wizard appears. 11 Click Next to continue. or port numbers. installation location. . Also compare the space that is required for upgrading to OpsCenter and the actual space that is available. A green checkmark appears in the Required column if there is adequate disk space. all existing VBR server services are stopped automatically. On the Installation Choice section. After you successfully upgrade to Symantec OpsCenter. Based on your installed VBR version. locations. 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. The default location is C:\Program Files\Symantec\OpsCenter\SavedData. or port numbers. Note: Ensure that the database location has adequate space by going through the Disk space requirements section on this page. check ‘I accept the terms of the license agreement’ and click Next. 7 8 9 Click Next to continue. click Typical to use the default settings. The license type is also shown along with the key. 13 On the License Keys screen. you must install OpsCenter Agent if you want to collect data from other backup products. Data migration from the old VBR database to the OpsCenter database starts once the Symantec OpsCenter Server service is started while installing OpsCenter server. 17 Click Finish. The installer upgrades VBR server to OpsCenter Server software. 16 After successful installation. 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. The license keys that are already installed on the system are also displayed in the box that is shown on this screen. You can also access the data migration status from the OpsCenter console. enter the demo or permanent key that you have received with the purchase of OpsCenter and click Add Key. 15 Click Install. If you do not enter a license key. Note: Ensure that the port number that you enter is free and not used by any other application. . Check Save Summary to field to save the installation summary. you can view the OpsCenter console or view installation logs. Click Browse to save the installation summary in your preferred location. your existing license keys are used. enter a port number on which the old VBR database can be started. The installer shows the summary of the settings that you have selected for installation. However.0 or PureDisk. The default port number is 13799. See “About the license keys” on page 70. See “Monitoring data migration from VBR to Symantec OpsCenter Analytics” on page 134. 14 Click Next. You do not require an OpsCenterAgent to collect data from NetBackup 7. Click Next.Installing Symantec OpsCenter Upgrading to OpsCenter on Windows and UNIX 111 12 On the Upgrade Settings page. exe’ and press Enter: Where D is the DVD drive. 7 8 Click Next to continue. 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. By default. To upgrade to OpsCenter Agent on Windows 1 On a Windows host where you want to install OpsCenter Agent. you must manually uninstall Veritas Backup Reporter Agent. If you use the NetBackup media kit to install OpsCenter Agent. click Start > Run. insert the appropriate OpsCenter product DVD in the DVD drive. . all Veritas Backup Reporter services are stopped automatically. in the Open text box. the VBR Agent uses port number 7806. click OpsCenter Software Installation. The OpsCenter DVD contains OpsCenter software for all available platforms. The Symantec DVD Browser appears. On the Run dialog box. The NetBackup media kit contains a separate DVD for each platform. Based on your installed VBR Agent version. The Installation Wizard detects an existing installation of Veritas Backup Reporter Agent on the system. You may install OpsCenter Agent from the OpsCenter DVD or from the NetBackup media kit.112 Installing Symantec OpsCenter Upgrading to OpsCenter on Windows and UNIX Note: Once you upgrade your VBR Agent to the OpsCenter Agent. type ‘D:\Browser. Read the license agreement. If autorun is not enabled. 3 4 On the Symantec DVD Browser. The Symantec OpsCenter Installation Wizard appears. the Symantec DVD Browser appears. check ‘I accept the terms of the license agreement’ and click Next. Ignore this step if you install OpsCenter Agent software from the OpsCenter DVD. click the Installation link. After you successfully upgrade to Symantec OpsCenter Agent. Click the OpsCenter Agent Installation link to install Symantec OpsCenter Agent. the port number that the VBR Agent uses is not required in OpsCenter. 2 ■ ■ If autorun is enabled. in the Open text box. click Browse if you want to change the default location for Symantec OpsCenter Agent installation. Check Save Summary to field to save the installation summary. 2 ■ ■ If autorun is enabled. the Symantec DVD Browser appears. 12 Click Install. 14 Click Finish. you can view the installation logs or open the readme file. insert the appropriate OpsCenter product DVD in the DVD drive. You may install OpsCenter from the OpsCenter DVD or from the NetBackup media kit. 13 After successful installation. 11 The installer shows a summary of the settings that you have selected for Symantec OpsCenter Agent installation. On the Run dialog box. 3 On the Symantec DVD Browser. The Symantec DVD Browser appears. click the Installation link. A green checkmark appears in the Required column if there is adequate disk space. 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 1 On the OpsCenter View Builder host. The OpsCenter DVD contains OpsCenter software for all available platforms. If autorun is not enabled.Installing Symantec OpsCenter Upgrading to OpsCenter on Windows and UNIX 113 9 On the Installation Location screen. 10 Select a new location and click Next. The NetBackup media kit contains a separate DVD for each platform. type ‘D:\Browser.exe’ and press Enter: Where D is the DVD drive. Click Browse to save the installation summary in your preferred location. The installer starts installation of Symantec OpsCenter Agent. Note: Ensure that the installation directory that you specify has adequate space by going through the Disk space requirements section on this page. click Start > Run. . Veritas Backup Reporter: <version> In order to upgrade to a newer version. check ‘I accept the terms of the license agreement’ and click Next.114 Installing Symantec OpsCenter Upgrading to OpsCenter on Windows and UNIX 4 If you use the NetBackup media kit to install OpsCenter View Builder. the existing Veritas Backup Reporter View Builder will be removed. 12 After successful installation. 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. 7 8 Read the license agreement. Click the OpsCenter View Builder Installation link to install Symantec OpsCenter View Builder. 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. 13 Click Finish. . On the Installation Location screen. A green checkmark appears in the Required column if there is adequate disk space. Ignore this step if you install OpsCenter View Builder software from the OpsCenter DVD. Symantec OpsCenter View Builder installation. click Browse if you want to change the default location for Symantec OpsCenter View Builder installation. The Symantec OpsCenter Installation Wizard appears. Check Save Summary to field to save the installation summary. 5 6 Click Next to continue. click OpsCenter Software Installation. 9 Select a new location and click Next. Click Browse to save the installation summary in your preferred location. you can view the installation logs or open the readme file. Note: Ensure that the installation directory that you specify has adequate space by going through the Disk space requirements section on this page. You may install OpsCenter from the OpsCenter DVD or from the NetBackup media kit. If using the NetBackup media kit. .n. To upgrade from VBR Server to OpsCenter Server on UNIX 1 2 Open a UNIX console and log on as root on the target host. 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. The Welcome message is displayed. Press Enter. go to the appropriate OpsCenter platform directory and then the Server directory. type y and then press Enter./installOpsCenterServer. Mount the OpsCenter product DVD for the appropriate platform on which you are installing. Do you want to upgrade from VBR <version> to Symantec OpsCenter [y. Press Enter to continue. go to the following directory: cd OpsCenter/Server ■ 4 5 6 Type the following command:. The installer then checks for an existing VBR installation.q] y To upgrade to Symantec OpsCenter. The NetBackup media kit contains a separate DVD for each platform. 3 Do one of the following: ■ If you use the OpsCenter DVD to install OpsCenter. It displays the following message when VBR is installed: Veritas Backup Reporter (VBR) <version> is installed on <hostname>.Installing Symantec OpsCenter Upgrading to OpsCenter on Windows and UNIX 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. The OpsCenter DVD contains OpsCenter software for all available platforms. press Enter without typing a directory path. press Enter without typing a directory path.116 Installing Symantec OpsCenter Upgrading to OpsCenter on Windows and UNIX 7 The following message is displayed: The existing VBR database and configuration files must be backed up before upgrading to Symantec OpsCenter. Symantec WebGUI Server. The script creates the folder OpsCenterServer below the directory that you specify. By default. Type a directory path under which to install the OpsCenter database and press Enter. 9 10 Type y to confirm the installation directory path and press Enter. If any older version of packages like VRTSpbx is detected. (/var/symantec) Type the directory name in which you want to save the VBR database and configuration files and then press Enter. Review this list and press Enter to continue. To accept the default database installation directory (/var/Symantec). The following information is displayed: The OpsCenter database server may require up to 1 GB of temporary space at runtime. AT. To save the VBR database and configuration files in the default directory path (/var/symantec). temporary files will be created in the database installation directory. press Enter only. Symantec Database etc. 8 The installer displays a list of components that get installed like PBX./var/Symantec/OpsCenterServer . it is automatically uninstalled and the required version is installed. Type a directory path where you want to install the Symantec OpsCenter Server packages and press Enter. To accept the default path (/opt). 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. 11 OpsCenter server is installed on the system. Installing Symantec OpsCenter Upgrading to OpsCenter on Windows and UNIX 117 12 You are prompted with the following message: Would you like to use an alternate directory for database server temporary space? [y. Note: Ensure that the port number that you enter is free and not used by any application. 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. . type the license key and press Enter. Type y and then press Enter. 15 All the OpsCenter processes are started. Location of install log. To use the database installation directory for database server temporary space. Review the installation options that you selected (database and database temp directory locations). The following information is also displayed: ■ ■ Web URL to access OpsCenter console. and response files. Do you want to enter a new key?<Enter one key at a time if there are multiple keys: To use a new key. press Enter only. To accept the default port number (13799). 13 Configuration changes are performed. 14 You are prompted with the following message: An older license key has been detected. summary. Specify the directory location when prompted. Type y and then press Enter. press Enter only.q] (n) Type y and press Enter to specify an alternate directory for the database server temporary space. press Enter without typing a directory path. To use the existing key. Press <Return> to use the existing key. You are prompted with the following message: The old database will be started separately to migrate its data to the OpsCenter database. Review the installation options that you selected (database and database temp directory locations).n. 0 or PureDisk. However./installOpsCenterAgent. you must install OpsCenter Agent if you want to collect data from other backup products. Press Enter to continue. the port that the VBR Agent uses is not required in OpsCenter. The NetBackup media kit contains a separate DVD for each platform. go to the appropriate OpsCenter platform directory and then the Agent directory. Note: Once you upgrade your VBR Agent to the OpsCenter Agent. 5 6 The Welcome message is displayed. The installer displays a list of components that get installed like PBX. Review this list and press Enter to continue. 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. If using the NetBackup media kit. You may install OpsCenter from the OpsCenter DVD or from the NetBackup media kit. You do not require an OpsCenterAgent to collect data from NetBackup 7.118 Installing Symantec OpsCenter Upgrading to OpsCenter on Windows and UNIX ■ 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. Mount the appropriate OpsCenter product DVD for the platform on which you are installing OpsCenter software. The OpsCenter DVD contains OpsCenter software for all available platforms. . go to the following directory: cd OpsCenter/Agent ■ 4 Type the following command: . Symantec WebGUI Agent etc. 3 Do one of the following: ■ If you use the OpsCenter DVD to install OpsCenter. Press Enter. log file. 9 Type y and then press Enter to confirm your installation options. 10 The OpsCenter Agent is installed. For example. or removed columns or constraints from the VBR database tables.Installing Symantec OpsCenter Upgrading to OpsCenter on Windows and UNIX 119 7 It is optional to configure OpsCenter Agent during installation. press Enter without typing a directory path. 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. To configure OpsCenterAgent now. You can view the installation log files. This file is located in <INSTALL_PATH>\OpsCenter\server\logs directory on Windows and /<INSTALL_PATH>/SYMCOpsCenterServer/logs directory on Solaris. Troubleshooting database inconsistency issues during upgrade The upgrade process may fail due to database inconsistency when you upgrade from VBR to OpsCenter server. 8 Enter the location where you want to install OpsCenter Agent. modified. you must manually undo the modifications that you have made to the database so that the database schema is similar to the released version. type y and press Enter. To accept the default path (/opt). Type a directory path where you want to install the Symantec OpsCenter Agent packages and press Enter. You may choose to configure OpsCenter Agent later either manually or by running . . summary. Additional information may be displayed in the ServerService_<timestamp>./opt/VRTS/install/installOpsCenterAgent -configurecommand. and response files on the path mentioned. To resolve this issue. It does not uninstall your existing NOM installation.log file.db and ccsvc.4 database is then upgraded to the OpsCenter database. Review the following considerations for data migration to Symantec OpsCenter: ■ For NOM versions less than 6. The following sections describe the data migration process from NOM to Symantec OpsCenter in detail. Monitoring data migration from NOM to Symantec OpsCenter When you upgrade from NOM to OpsCenter server.120 Installing Symantec OpsCenter Upgrading to OpsCenter on Windows and UNIX To resolve database inconsistency errors 1 Modify the database as per the message in the ServerService_<timestamp>. 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. ■ .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 2 3 Upgrade to OpsCenter server again. the older NOM database is saved and started. You can manually uninstall NOM after successfully migrating data and using Symantec OpsCenter for some time.5. The data migration process may take time depending on the volume of data that has to be migrated. This file is located in <INSTALL_PATH>\OpsCenter\server\logs directory on Windows and /<INSTALL_PATH>/SYMCOpsCenterServer/logs directory on Solaris. During upgrade.5. the database is first upgraded to NOM 6.4 and later versions. 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. the database is upgraded directly to the OpsCenter database.4 database. the OpsCenter Installation Wizard automatically detects an older NOM installation. the OpsCenter server is installed. For NOM 6.4.5. The NOM 6.5. See “Upgrading from Veritas Backup Reporter to OpsCenter Analytics on Windows and UNIX” on page 108. The OpsCenter installer only stops the existing NOM services. Copy the modified ccsvc. In the first stage. ■ A normal NOM user is the Administrator in OpsCenter.5. domains. 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. Users of other NOM domains can continue using their respective domains in OpsCenter. Note: You must create new alert policies in OpsCenter only after alert migration is complete. ■ A read-only NOM user is the Operator in OpsCenter. Table 2-8 NOM data migration Data in OpsCenter Metadata about the managed master servers from NOM is migrated to OpsCenter. data that is specific to NOM is migrated to the OpsCenter database.4 to the OpsCenter database occurs in three stages. The NOM data comprises of alerts. users. alert policies. you can view this data from Settings > Configuration > NetBackup page in the OpsCenter console. Once this data has been migrated to OpsCenter. Table 2-8 gives details about the NOM data that is migrated and how it appears in OpsCenter.Installing Symantec OpsCenter Upgrading to OpsCenter on Windows and UNIX 121 The data migration from NOM 6. . server groups etc. Once this data has been migrated to OpsCenter. you can view this data from the Settings > Users page in the OpsCenter console. ■ 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. you can view this data from the Settings > Recipients page (both Email and SNMP subtabs) in the OpsCenter console. three trees are created . A small group of master servers. The OpsCenter console displays all views in the drop-down list of the View Pane.122 Installing Symantec OpsCenter Upgrading to OpsCenter on Windows and UNIX Table 2-8 NOM data migration (continued) Data in OpsCenter All recipients and recipient groups are migrated from NOM to OpsCenter. or client node is mapped to the ALL MASTER SERVERS view. or clients are nodes in OpsCenter. Once the recipients have been migrated to OpsCenter.PrivateTree_Server. A single host. PrivateTree_Client. For each NOM user. . policy. policies. Even though recipient groups are migrated to the OpsCenter database. NOM data that is migrated Email and trap recipients Note: Recipient groups are not supported in OpsCenter. or client is an object in the View Pane. the OpsCenter console does not display recipient groups. Public and Private groups are migrated as nodes. and PrivateTree_Policy trees. policy. Public and Private Groups The main (root) server. Installing Symantec OpsCenter Upgrading to OpsCenter on Windows and UNIX 123 Table 2-8 NOM data migration (continued) Data in OpsCenter NOM data that is migrated Saved Reports . For example if you migrate a Skipped Files details for client report for a specific client like nom-ut6 from NOM. All private graphical reports in NOM become tabular in OpsCenter. User-created reports in NOM (both Public and Private) are migrated as custom SQL queries. these reports get default values for filters in OpsCenter. The concept of saving a report in NOM is different than OpsCenter. you can view them from Reports > My Dashboard in the OpsCenter console. before you save a report in OpsCenter.124 Installing Symantec OpsCenter Upgrading to OpsCenter on Windows and UNIX Table 2-8 NOM data migration (continued) Data in OpsCenter The following reports (and the schedules that are created for these reports) from NOM are not migrated to OpsCenter: ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ NOM data that is migrated 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. In NOM. User must provide values for all the filters like Client Name. Policy Name etc. then in OpsCenter . Once these reports have been migrated. you can directly edit SQL queries for these reports. you must have a licensed version of OpsCenter (OpsCenter Analytics). If you edit these reports in OpsCenter. Hence after migration is complete. a user provides values for filters while running a report. Note: To edit custom SQL reports in OpsCenter. 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 . Shortcuts to reports are not migrated. In the second stage. After the NOM data has been migrated. data is migrated per master server. You must create new alert policies in OpsCenter only after alert migration is complete.Installing Symantec OpsCenter Upgrading to OpsCenter on Windows and UNIX 125 Table 2-8 NOM data migration (continued) Data in OpsCenter the report is configured to run on all the clients (instead of only nom-ut6). See “Viewing the data migration status” on page 128. The WHERE clause of the OpsCenter SQL query has "IS NOT NULL" value. Shortcuts to reports are not supported in OpsCenter. the second stage of data migration begins. You need to manually configure My Portal again using OpsCenter reports. NOM data that is migrated Alert Policies and alerts All alert policies and alerts are migrated from NOM to OpsCenter. To see if alert policies have been migrated. see the Data Migration Status page. Note that in the second stage of data migration. data collection is not enabled automatically after migration. . At this point. The status for the specific master server is shown as Last 30 Days Jobs Migrated on the Data Migration status page. In such a case. data collection for each master server is enabled automatically. Note: If data collection for a master server was disabled in NOM. In the third stage of data migration. See “Viewing the data migration status” on page 128. then data collection for the specific master server remains disabled after you upgrade to OpsCenter.126 Installing Symantec OpsCenter Upgrading to OpsCenter on Windows and UNIX ■ ■ ■ ■ ■ ■ 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. fresh data collection from the master server begins and you can start using the Monitor and Manage tabs of the OpsCenter console. the following data is migrated: Jobs older than 30 days Jobs data older than 30 days is migrated for each master server. Example. Restore Job Summary etc.Installing Symantec OpsCenter Upgrading to OpsCenter on Windows and UNIX 127 Report Schedules The concept of report schedules is different in NOM and OpsCenter. Schedules for composite reports are not migrated. Full Media Capacity. We can have the following upgrade scenarios: . You can work in the OpsCenter console while this data is migrated in the background. ■ In case a standard report is scheduled in NOM. if a standard report like Available Media is scheduled in NOM. like network issues. SORD value etc. What happens when data migration is interrupted Data migration can be interrupted due to many reasons. For example. 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. 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). are not migrated to OpsCenter. you provide the schedule details as well as filter values. stopping services on the OpsCenter server etc. However when you create a schedule in NOM. While creating schedule for a report in OpsCenter. you only need to specify the schedule details like time etc. Note: All NOM user preferences like column settings. the report is first saved under Reports > My Reports and then the schedule is attached to it. 4 to the OpsCenter the last checkpoint automatically.4) is restarts from the beginning.5. Table 2-9 Scenario What happens when data migration is interrupted Migration status Data migration is interrupted when a NOM In this case.do <host.5.5.Recipient. report schedules. ■ Based on the upgrade scenarios. Note: The data migration for the following entities does not resume from the last checkpoint and needs to be migrated again . data migration automatically database (NOM version lower than 6. Data migration is interrupted when data is In this case.5.4 and later versions.128 Installing Symantec OpsCenter Upgrading to OpsCenter on Windows and UNIX ■ For NOM versions less than 6.5.4 database. the database is upgraded directly to the OpsCenter database.4 database to the OpsCenter database is in progress. Viewing the data migration status You can also view the data migration status using the OpsCenter console. The NOM 6.domain>/opscenter/dbUpgradeStatus.5. Robot.5. Groups. For NOM 6. DSM. the database is first upgraded to NOM 6.5.4.4 database is in progress (this happens when a NOM version less than 6. and alert policy.domain> is the FQDN (Fully Qualified Domain Name) or IP address of the OpsCenter Server host. Services. To view the data migration status 1 Access the data migration status page by doing any of the following: ■ In the Web browser address bar. enter the following: http://<host. Reports. data migration resumes from migrated from NOM 6.5.4 is being upgraded to OpsCenter) or when upgrade from NOM 6. License feature history. the data migration process can either be interrupted when upgrade to NOM 6. being upgraded to the NOM 6. that had already been migrated does not need to be migrated again. Table 2-9 explains the specific scenarios and what happens when data migration is interrupted in these scenarios.4 database. User.5. The data database.4 database is then upgraded to the OpsCenter database. . The link is located at the bottom of the logon page on the right-hand side.sh -status on UNIX hosts. The data migration status is displayed as shown in the following figure: . run the configurePorts utility. For example. ■ On the OpsCenter logon page. then use http://<server-host>:8181/opscenter/dbUpgradeStatus. This link automatically disappears when the data migration is complete.do. use the Click here to see migration status link as shown in the following figure.Installing Symantec OpsCenter Upgrading to OpsCenter on Windows and UNIX 129 Note: By default. OpsCenter tries to run on port 80 (HTTP). if OpsCenter uses HTTP port 8181.bat -status on Windows hosts or /opt/SYMCOpsCenterWebGUI/bin/goodies/configurePorts. If port 80 is not available. You can also use the URL that is presented at the end of the OpsCenter server installation and append /dbUpgradeStatus. Run INSTALL_PATH\OpsCenter\gui\bin\goodies\configurePorts. To know the HTTP and HTTPS port that OpsCenter uses.do after the URL to access the data migration page at any point in time. OpsCenter can use a different port. 130 Installing Symantec OpsCenter Upgrading to OpsCenter on Windows and UNIX The data migration status comprises Entity Migration Status and Master Server Entity Migration Status. Policy data (number of records) that are being migrated to OpsCenter. Alert Policy. 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 . Total Records . The total number of records of an entity that need to be migrated from NOM to Symantec OpsCenter. Also the number of migrated recipients includes recipients as well as recipient groups. This is shown in the following figure: . For example. However. ■ 2 Click the Master Server Entity Migration Status tab to view the details of entities that are migrated per master server. recipient groups are not shown on the OpsCenter console as they are not supported by OpsCenter. NOM standard reports like Cycle Dashboard and also schedules for such standard reports (if any) are shown as skipped records. ■ NOM data that is not migrated is also shown as Skipped Records.Installing Symantec OpsCenter Upgrading to OpsCenter on Windows and UNIX 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. Such records are collected once the OpsCenter server starts. For example. 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. the migrated records for policies include policies as well as policy versions that are associated with it. 132 Installing Symantec OpsCenter Upgrading to OpsCenter on Windows and UNIX This page shows the number of records that have been migrated for each master server. 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. It also shows the time that is required for migrating those many records. . . This status indicates that entities like policies. You can start using the Monitor and Manage views of the OpsCenter console at this point. 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. 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. then data collection for the specific master server remains disabled after migration.Installing Symantec OpsCenter Upgrading to OpsCenter on Windows and UNIX 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. Note: If data collection for a master server was disabled in NOM. Total Records The total number of records for each master server that need to be migrated from NOM to Symantec OpsCenter. the OpsCenter server starts collecting fresh data from the specific master server. media. Because data collection has been enabled. Also the number of migrated recipients includes recipients as well as recipient groups. The OpsCenter installer only stops the existing VBR services. . You can manually uninstall VBR after successfully migrating data and using Symantec OpsCenter for some time. ■ Monitoring data migration from VBR to Symantec OpsCenter Analytics When you upgrade from VBR to OpsCenter Analytics. This does not necessarily mean that these many records for the specific entity will be shown on the OpsCenter console. NOM standard reports like Cycle Dashboard and also schedules for such standard reports (if any) are shown as skipped records. However. For example. Such records are collected once the OpsCenter server starts. recipient groups are not shown on the OpsCenter console as OpsCenter does not support recipient groups. the OpsCenter server is installed and the older VBR database is saved and started. as of now Note: Migrated records are the number of rows in tables. During upgrade. 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. For example. 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. the migrated records for policies include policies as well as policy versions that are associated with it. ■ NOM data that is not migrated is also shown as Skipped Records. It does not uninstall your existing VBR installation.134 Installing Symantec OpsCenter Upgrading to OpsCenter on Windows and UNIX Migrated Records Number of records for each master server that have been migrated to Symantec OpsCenter. the OpsCenter Installation Wizard automatically detects an older VBR installation. The following sections describe the data migration process from VBR to OpsCenter Analytics. The VBR 6. media history.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.1. For VBR 6. TSM. and 6. Second stage in which Symantec Enterprise Vault archive data and report data is migrated. The VBR metadata comprises of data related to alert policies. .6 database is then upgraded to the OpsCenter database. media. ■ ■ Table 2-10 gives details about the VBR metadata that is migrated in the first stage and how it appears in OpsCenter. and images.5. SMTP server.6 and later versions. the database is first upgraded to the VBR 6.Installing Symantec OpsCenter Upgrading to OpsCenter on Windows and UNIX 135 The data migration process may take time depending on the amount of data that has to be migrated. views. devices etc. domains. Legato Networker) is migrated from VBR to OpsCenter for each master server. For entities like jobs.6 database. ■ The data migration from VBR 6. Review the following considerations for data migration: ■ For VBR 6. Backup Exec. data for the last 30 days is migrated in this stage.1. 6.1 versions.5.5. scheduled jobs. The backup data consists of entities like policy. Third stage in which backup data older than 30 days (for NetBackup. users. 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. PureDisk. the database is upgraded directly to the OpsCenter database. and data purge settings etc. media servers. .136 Installing Symantec OpsCenter Upgrading to OpsCenter on Windows and UNIX 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. and clients that have job data are migrated to OpsCenter. and EV archive-related information like vault server . clients. Exchange Server is migrated to OpsCenter. Note: Only those master servers. Once this data has been migrated to OpsCenter. 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. the NetBackup agents and NetBackup data collectors can be viewed from Settings > Configuration > NetBackup in the OpsCenter console. media servers. file systems. Note: Recipient groups are not supported in OpsCenter.Installing Symantec OpsCenter Upgrading to OpsCenter on Windows and UNIX 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. Once this data has been migrated to OpsCenter. All settings of the default admin user are now associated with the admin user of OpsCenterUsers(vx) domain. you can view this data from the Settings > Users page in the OpsCenter console. the recipient groups are not displayed in the OpsCenter console. ■ A normal VBR user is the Reporter in OpsCenter. Even though recipient groups are migrated to the OpsCenter database. you can see these views in the View Pane of the OpsCenter console. 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. 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. Views All views from VBR are migrated to OpsCenter as client-type views. Once this data has been migrated to OpsCenter. ■ VBR data that is migrated User information and domains The users on the cc_users@hostname domain can continue using the same domain in OpsCenter. . The following data is migrated as a part of backup data for each master server: ■ ■ ■ ■ Policy Devices (tape libraries .) 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. fresh data collection from the master server begins and you can start using the Monitor. At this point. data collection for each master server is enabled automatically. EMC Legato Networker) is migrated per master server.138 Installing Symantec OpsCenter Upgrading to OpsCenter on Windows and UNIX 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. In such a case. Disk pools etc. VBR data that is migrated Alert Policies Note: Alerts from VBR are not migrated to OpsCenter. then data collection for the specific master server remains disabled after upgrading to OpsCenter Analytics. The status for the specific master server is shown as Last 30 Days Jobs Migrated on the Data Migration status page. Note: If data collection for a master server was disabled in VBR. To see if alert policies have been migrated. backup data (for NetBackup. and Reports tabs of the OpsCenter console. See “Viewing the data migration status” on page 142. IBM TSM. data collection is not enabled automatically after migration. Tape drives.Manage. After the VBR metadata is migrated. Backup Exec. . PureDisk. see the Data Migration Status page. .Installing Symantec OpsCenter Upgrading to OpsCenter on Windows and UNIX 139 After the first stage of data migration is complete. the second stage of data migration begins. In the second stage of data migration. 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. Table 2-11 gives details about the report data that is migrated and how it appears in OpsCenter. report data is migrated in the second stage. Symantec Enterprise Vault archive data is migrated followed by report data. the third stage of data migration begins. the chargeback variables and formulae can be viewed from Settings > Chargeback view in the OpsCenter console. Client Count Success Rate vs. The following VBR reports are not migrated to OpsCenter: ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ VBR data that is migrated Reports Master Server Count NetBackup Storage Lifecycle Map Success Rate vs. In the third stage of data migration. the My Backup Reports folder was under My Saved Reports folder. The following data is migrated in the third stage for each master server: ■ Media History (Older than 30 days) . you can view the My Backup Reports folder under Private Reports tree. Report schedules All report schedules are migrated from VBR to OpsCenter. After the second stage of data migration is complete. Job Count Success Rate vs. Earlier in VBR.140 Installing Symantec OpsCenter Upgrading to OpsCenter on Windows and UNIX Table 2-11 VBR report data migration in the second stage Data in OpsCenter Analytics After migration is complete. 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. Amount Backed Up Success Rate vs. Custom SQL and Stored Custom SQL reports are not migrated to Symantec OpsCenter. the backup data that remains to be migrated in the first stage (data older than 30 days) is migrated for each master server. Once this data has been migrated. like network issues.5. What happens when data migration is interrupted Data migration can be interrupted due to many reasons.6 to OpsCenter Analytics. .6 database.6 database is then upgraded to the OpsCenter database. the data migration process can either be interrupted when upgrade to VBR 6.6) is being upgraded to the VBR 6. and 6.6 database.5.6 database to the OpsCenter database is in progress. We can have the following upgrade scenarios: ■ For VBR 6.1 versions. The VBR 6. ■ Based on the upgrade scenarios. For VBR 6. the database is first upgraded to the VBR 6. What happens when data migration is interrupted Migration status In this case. you need to configure the following after data migration is complete: ■ SMTP server settings.1. Table 2-12 Scenario Data migration is interrupted when a VBR database (VBR version lower than 6. data migration automatically restarts from the beginning. accidental shutdown of OpsCenter server. the database is upgraded directly to the OpsCenter database. 6.6 and later versions.6 database is in progress (this happens when a VBR version less than 6. Table 2-9 explains the specific scenarios and what happens when data migration is interrupted in these scenarios. The VBR SMTP server settings are not migrated to OpsCenter.1.Installing Symantec OpsCenter Upgrading to OpsCenter on Windows and UNIX 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.5. stopping services on the OpsCenter server etc.6 is upgraded to OpsCenter Analytics) or when upgrade from VBR 6. bat -status on Windows hosts or /opt/SYMCOpsCenterWebGUI/bin/goodies/configurePorts. OpsCenter tries to run on port 80 (HTTP).sh -status on UNIX hosts.domain>/opscenter/dbUpgradeStatus. Note: The data migration for the following entities does not resume from the last checkpoint and is migrated again . This link automatically disappears when the data migration is complete. reports. Data migration is interrupted when data is being migrated from VBR 6. The data that had already been migrated does not need to be migrated again. if OpsCenter uses HTTP port 8181.list of clients and file systems.domain> is the FQDN (Fully Qualified Domain Name) or IP address of the OpsCenter Server host. The link is located at the bottom of the logon page on the right-hand side. For example.do to access the data migration page at any point in time. If port 80 is not available. . ■ On the OpsCenter logon page. enter the following: http://<host.domain>:8181/opscenter/dbUpgradeStatus. To view the data migration status 1 Access the data migration status page by doing any of the following: ■ In the Web browser address bar.do after the URL to access the data migration page at any point in time. run the configurePorts utility. Viewing the data migration status You can also view the data migration status using the OpsCenter console. use the Click here to see migration status link as shown in the following figure.do <host. then use http://<host.6 to the OpsCenter database. To know the HTTP and HTTPS port that OpsCenter uses. data migration resumes from the last checkpoint automatically. You can also use the URL that is presented at the end of the OpsCenter server installation and append /dbUpgradeStatus.142 Installing Symantec OpsCenter Upgrading to OpsCenter on Windows and UNIX Table 2-12 Scenario What happens when data migration is interrupted (continued) Migration status In this case. OpsCenter can use a different port. Run INSTALL_PATH\OpsCenter\gui\bin\goodies\configurePorts. Note: By default. Installing Symantec OpsCenter Upgrading to OpsCenter on Windows and UNIX 143 The data migration status is displayed as shown in the following figure: . The Entity Migration Status tab shows the following columns (along with the migration summary): Entity Displays the name of the database entity. The total number of records of an entity that need to be migrated from VBR to Symantec OpsCenter Analytics.144 Installing Symantec OpsCenter Upgrading to OpsCenter on Windows and UNIX The data migration status contains Entity Migration Status and Master Server Entity Migration Status tabs. such as Alert Policy. Jobs etc. Disk Pool. Total Records . that is being migrated to OpsCenter Analytics. Policy. This does not necessarily mean that these many records for the specific entity will be shown on the OpsCenter console. Such records are collected once the OpsCenter server starts (if they are present in the NetBackup host) . 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. For example. the migrated records for policies include policies as well as policy versions that are associated with it. as of now Note: Migrated records are the number of rows in tables. However. ■ 2 Click the Master Server Entity Migration Status tab to view the details of entities that are migrated for each master server. Also the number of migrated recipients includes recipients as well as recipient groups. ■ VBR data that is not migrated is also shown as Skipped Records. recipient groups are not shown on the OpsCenter console as they are not supported in OpsCenter. For example. The following figure shows a sample view of the Master Server Entity Migration Status tab: . VBR alerts are shown as skipped records.Installing Symantec OpsCenter Upgrading to OpsCenter on Windows and UNIX 145 Migrated Records Number of records of an entity that have been migrated to Symantec OpsCenter. such as master server .146 Installing Symantec OpsCenter Upgrading to OpsCenter on Windows and UNIX This page shows the number of records that have been migrated for each master server. Policy data (number of records) that has been migrated to OpsCenter. 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. . Alert Policy. Last 30 Days Jobs Migrated: This means that the first stage of data migration is complete for the specific master server. . Because data collection has been enabled. You can start using the Monitor and Manage views of the OpsCenter Analytics console at this point. This status indicates that entities like policies. 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. 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. In Progress: Entities for this master server are being migrated from VBR to OpsCenter Analytics. then data collection for the specific master server remains disabled after migration. Total Records The total number of records for each master server that need to be migrated to Symantec OpsCenter Analytics from VBR.Installing Symantec OpsCenter Upgrading to OpsCenter on Windows and UNIX 147 Status The migration status for the respective master server. media. Note: If data collection for a master server was disabled in VBR. The following migration status are possible for a master server: Not Started: The data migration process for the master server has not started. the OpsCenter server starts collecting fresh data from the specific master server. For example. 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. you can upgrade from Solaris 8 to Solaris 10 but you cannot upgrade from a Windows platform to Solaris 10. For example. recipient groups are not shown on the OpsCenter console as OpsCenter does not support recipient groups. However. 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. Such records are collected once the OpsCenter server starts (if they are present in the NetBackup host). as of now Note: Migrated records are the number of rows in tables. For example.148 Installing Symantec OpsCenter Upgrading to OpsCenter on Windows and UNIX Migrated Records Number of records for each master server that have been migrated to Symantec OpsCenter. This does not necessarily mean that these many records for the specific entity will be shown on the OpsCenter console. the migrated records for policies include policies as well as policy versions associated with it. ■ VBR data that is not migrated is also shown as Skipped Records. Note: Manual upgrades are not supported for Windows platforms. 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. Also the number of migrated recipients includes recipients as well as recipient groups. . The procedure basically involves the following steps: ■ Back up your NOM or VBR database and configuration files using Backup. You may install OpsCenter from the OpsCenter DVD or from the NetBackup media kit. Copy this data from the old server to the server where you plan to install OpsCenter server.sh utility on your old NOM or VBR server. 3 Do one of the following: ■ If you use the OpsCenter DVD. Mount the appropriate OpsCenter product DVD for the platform on which you are installing OpsCenter software. To back up the NOM or VBR database 1 2 Go to the NOM or VBR server and log on as root. go to the following directory: cd OpsCenter/Server ■ .Installing Symantec OpsCenter Upgrading to OpsCenter on Windows and UNIX 149 Use the following procedure to upgrade to OpsCenter server software on a different UNIX system. ■ 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. See “Backing up your data on the NOM or VBR server” on page 149. go to the appropriate OpsCenter platform directory and then the Server directory. Install the OpsCenter server software and restore the NOM or VBR data using the OpsCenter installer. The NetBackup media kit contains a separate DVD for each platform. See “Upgrading to OpsCenter server on the new system” on page 150. The OpsCenter DVD contains OpsCenter software for all available platforms. If you use the NetBackup media kit. sh 5 The script detects that you have NOM or VBR installed and prompts you for the backup location: You have <product> installed.sh script. navigate to the appropriate OpsCenter platform directory and then the Server directory on the DVD. ■ . Please specify the backup location.150 Installing Symantec OpsCenter Upgrading to OpsCenter on Windows and UNIX 4 Run Backup. This script backs up the NOM or VBR database and configuration files on this system./Backup. 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. 4 Do one of the following: ■ If you use the OpsCenter DVD to install OpsCenter server software. press Enter. The NetBackup media kit contains a separate DVD for each platform. To back up the <product> data in the default directory (/var/symantec). navigate to the Server directory. Mount the OpsCenter product DVD for the appropriate platform on which you are installing. type a backup location and press Enter. You may install OpsCenter from the OpsCenter DVD or from the NetBackup media kit. 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. If you use the NetBackup media kit to install OpsCenter. The OpsCenter DVD contains OpsCenter software for all available platforms. Copy the backed up NOM or VBR data (OpsCenter_save folder) from the older NOM or VBR server to this server. . 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. The installer also examines the system for existing packages. The installer then checks if OpsCenter Server is installed on the system or not.Installing Symantec OpsCenter Upgrading to OpsCenter on Windows and UNIX 151 cd OpsCenter/Server 5 6 7 Type the following command:. Symantec WebGUI Server. The Welcome message is displayed. The installer displays a list of components that get installed like PBX./installOpsCenterServer. It prompts you in case OpsCenter is already installed. To accept the default path (/opt). AT. 10 Type y to confirm the directory path and press Enter. Symantec Database etc. . press Enter without typing a directory path. Press Enter. The installer prompts you with the following question: Where do you want to install Symantec OpsCenter? </opt> 8 9 Type a directory path where you want to install the Symantec OpsCenter Server packages and press Enter. Press Enter to continue. Review this list and press Enter to continue. 13 Review the installation options you selected. By default. The location of database directory and the database temp directory is also displayed. Do you want to create the directory? [y. . press Enter without typing a directory path.152 Installing Symantec OpsCenter Upgrading to OpsCenter on Windows and UNIX 11 OpsCenter server is installed on the system. the script creates the folder OpsCenterServer below your directory.n. type y and press Enter. To accept the default database installation directory (/var/Symantec). temporary files will be created in the database installation directory /var/Symantec/OpsCenterServer 12 You are prompted with the following message: Would you like to use an alternate directory for database server temporary space? [y.n.q] y Type y to confirm and press Enter. the following information is displayed: Directory "/var/symantec" does not exist. To specify an alternate directory. If you create an alternate database directory. In case the database installation directory (/var/symantec) does not exist on the host. Type a directory path under which to install the OpsCenter database and press Enter. The following information is displayed: The OpsCenter database server may require up to 1 GB of temporary space at runtime. 14 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.q] (n) To use the database installation directory for database server temporary space. Type a directory path for the database server temporary space and press Enter. press Enter without typing a directory path. press Enter. 17 You are prompted with the following: The old database will be started separately for migrating its data to the OpsCenter database. Otherwise enter any other port that is available and press Enter. You can also add the license keys later from the OpsCenter console. 16 You are prompted for the location of the backed up directory: Please specify the directory that contains the backed up data. Post-installation tasks The following sections explain how to start using OpsCenter and includes some performance tuning tips for OpsCenter. Specify a port number on which the old database can be started <13799> To start the old database on port 13799. you get an unlicensed version. . See “Managing licenses” on page 226. 18 You are prompted for license information.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. See “About the license keys” on page 70. <var/symantec> Specify the location where you have copied the backed up data and press Enter. you cannot access the licensed features. With the unlicensed version.q] <n> Type y and then press Enter.n. If you do not enter a key. the installer may prompt 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 Analytics and press Enter. Depending on whether older license keys are detected or not. 154 Installing Symantec OpsCenter Post-installation tasks 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 1 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. 2 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. Installing Symantec OpsCenter Post-installation tasks 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 Installing Symantec OpsCenter Post-installation tasks 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 1 Open OpsCenterServerService.xml file from the following location on the OpsCenter server: INSTALL_PATH\OpsCenter\server\bin 2 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 1 Open startserver file from the following location: /opt/SYMCOpsCenterServer/bin 2 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 Installing Symantec OpsCenter Post-installation tasks 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 1 Open OpsCenterGUIService.xml file from the following location on the OpsCenter server: INSTALL_PATH\OpsCenter\gui\bin\OpsCenterGUIService.xml 2 Modify the Xmx1024m value in the following string. <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: INSTALL_PATH\OpsCenter\server\bin\opsadmin.bat stop INSTALL_PATH\OpsCenter\server\bin\opsadmin.bat start To adjust the heap size on UNIX servers 1 Open startGUI file from the following location: /opt/SYMCOpsCenterGUI/bin 2 Modify the Xmx1024m value in the following string. JAVA_OPTS="-d64 -Xms512M -Xmx1024m... For example, replace -Xmx1024 with -Xmx1400 to increase the maximum heap size from 1024 MB to 1400 MB. 158 Installing Symantec OpsCenter Post-installation tasks 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: /opt/SYMCOpsCenterServer/bin/opsadmin.sh stop /opt/SYMCOpsCenterServer/bin/opsadmin.sh start 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 1 Open OpsCenterAgentService.xml file from the following location on the OpsCenter server: INSTALL_PATH\OpsCenter\Agent\bin 2 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 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. 5 Select Control Panel > Administrative Tools > Services and start the Symantec OpsCenter Agent Service. Installing Symantec OpsCenter Post-installation tasks 159 To adjust the heap size on UNIX servers 1 Open startagent file from the following location: /opt/SYMCOpsCenterAgent/bin 2 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 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 Installing Symantec OpsCenter Post-installation tasks To set the cache size using the -c server option on Windows servers 1 Open the install_path\OpsCenter\server\db\conf\server.conf file. For example, to increase the cache size to 512 MB, add -c 512M -cs to 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. 2 Stop and restart the OpsCenter services, as follows: INSTALL_PATH\OpsCenter\server\bin\opsadmin.bat stop INSTALL_PATH\OpsCenter\server\bin\opsadmin.bat start Installing Symantec OpsCenter Post-installation tasks 161 To set the cache size using the -c server option on UNIX servers 1 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: /opt/SYMCOpsCenterServer/bin/opsadmin.sh stop /opt/SYMCOpsCenterServer/bin/opsadmin.sh start 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. 3 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 4 VBR 5 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. 3 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 4 Log on to the NOM or VBR console. In case domains are not visible on the logon page and you cannot log on to NOM, you must reinstall Symantec Product Authentication Service that was 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 Installing Symantec OpsCenter Uninstalling Symantec OpsCenter on Windows and UNIX 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 Installing Symantec OpsCenter Uninstalling Symantec OpsCenter on Windows and UNIX 165 3 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. 4 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 3 Type the following command and press Enter: ./uninstallopscenteragent The Uninstall Script checks the components installed on the system. 4 When asked to confirm if you want to uninstall OpsCenter Agent, 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. 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. Installing Symantec OpsCenter Clustering Symantec OpsCenter 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. 2 Make sure that you have met all prerequisites. 3 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 Installing Symantec OpsCenter Clustering Symantec OpsCenter ■ 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 Administrator’s Guide for details. Verify that all VCS services are up and running on all the nodes in the cluster. Verify that OpsCenter installation is carried out with the domain 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. Installing Symantec OpsCenter Clustering Symantec OpsCenter 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 1 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 Installing Symantec OpsCenter Clustering Symantec OpsCenter 7 Create a principal user on the AT host using the following command: AT_INSTALL_DIR/bin/vssat addprpl --prplname <principal name> --password <principal name password> --pdrtype ab --domain broker --prpltype service --is_broker_admin --is_domain_admin AT_INSTALL_DIR is the directory where AT is installed. The default location on 32-bit Windows platforms is: %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 1 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. 2 ■ ■ 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. 3 On the Symantec OpsCenter Installation Wizard, click the Installation link. Installing Symantec OpsCenter Clustering Symantec OpsCenter 171 4 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 9 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 Installing Symantec OpsCenter Clustering Symantec OpsCenter 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 15 Click Next. The installer shows the summary of the settings that you have 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. Installing Symantec OpsCenter Clustering Symantec OpsCenter 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 17 After successful installation, you can view the OpsCenter console or view 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 Installing Symantec OpsCenter Clustering Symantec OpsCenter 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. 3 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. 4 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. ■ ■ ■ ■ Note: OpsCenter does not support clustered AT. To establish a connection between AT host and OpsCenter Server host. For more information about installing AT. ping the IP address and verify that the IP address is not plumbed. before OpsCenter can be clustered. Use the credentials of this user when installing OpsCenter Server. Note: Symantec Product Authentication Service is installed when you install Veritas Cluster Server. navigate to the following directory: D:/ICS/Authentication D is DVD drive. . as OpsCenter does not support clustered AT. ■ ■ Verify that you can mount the disk.Installing Symantec OpsCenter Clustering Symantec OpsCenter 175 Also. You must upgrade to the version of authentication service that is shipped with OpsCenter. You should not cluster the AT service. ensure that Symantec authentication service (AT) Server is installed separately in a non-clustered mode. 2 In the product DVD. Verify that you have the OpsCenter installation program and a valid license key. Clustered OpsCenter Server uses this authentication broker. AT can be installed in Root + AB or AB mode. you need to create a principal user on the AT host. Before installing OpsCenter Server. You must install the version of AT Service that is shipped with OpsCenter. Symantec Product Authentication Service can be installed in the following ways: To install AT 1 Logon to the host where you want to install AT. see the Symanetc Infrastructce Core Services Installation Guide. You can either configure AT in root + authentication broker (Root + AB) mode or authentication broker (AB) mode. Verify that OpsCenter Server installation is carried out with the domain admin account. ■ ■ Installing Symantec Product Authentication Service on UNIX OpsCenter Server requires that Symantec Product Authentication Service (AT) is installed on a standalone host. with VxVM” on page 176.in HP-UX with logical volume manager ” on page 178.---------------------------------------. Preinstallation checklist for a Symantec OpsCenter Server installation The OpsCenter Server requests certain cluster related information during installation.------------------------------------------------------------------------------.176 Installing Symantec OpsCenter Clustering Symantec OpsCenter 3 Invoke the . 4 Select 1 to install AT. Scenario 1 .---------------------------------------. The following information is required for all VCS cluster configurations.------------------------------------------------------------------------------. See “Scenario 4 .with VxVM The following information is required if you use VCS with VxVM. . Fill out the checklist before you begin installation./installics script .---------------------------------------- About installation of Symantec OpsCenter with VCS The following information is required if you use VCS. See Symantec Infrstructure Core Services Installation Guide for more details on usinginstallics script. See “Scenario 3 . Note: The configuration utility unless specified. See “Scenario 2. See “Scenario 1 . Virtual Name for NetBackup: IP address : Subnet mask Node Name IP address ---------------------------------------------------------------------------------------------------------------------Network device name (NIC) ---------------------------------------. Theinstallics menu is displayed. Review the scenario that fits your configuration.with AIX LVMVG” on page 177. treats all attribute values globally.with no Volume Manager” on page 177.---------------------------------------. Resource Mount point : -----------------------------------Block device: ----------------------------------FS type: -----------------------------------------Mount option: ---------------------------------Fsck option: ------------------------------------Example /opt/VRTSnbu /dev/dsk/clt1dos3 vxfs (optional) (if you add other options.with no Volume Manager The following information is required if you use VCS with a disk only and no Volume Manager. Resource LVMG resource: Example .Installing Symantec OpsCenter Clustering Symantec OpsCenter 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 3 . -y is also required) Scenario 2.with AIX LVMVG The following information is required if you use VCS in an AIX environment with LVMVG. 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.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 . . you must install and configure OpsCenter in a clustered mode. 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.178 Installing Symantec OpsCenter Clustering Symantec OpsCenter Volume group : ---------------------------------Major number: ---------------------------------- opsvg 58 Disks: ---------------------------------------------. -y is also required) (optional) (optional) (optional) Scenario 4 . The OpsCenter DVD contains OpsCenter software for all available platforms. navigate to the Server directory. Press Enter.Installing Symantec OpsCenter Clustering Symantec OpsCenter 179 Note: To install OpsCenter Server in clustered mode. The NetBackup media kit contains a separate DVD for each platform. navigate to the appropriate OpsCenter Server platform directory and then theServer directory on the DVD. Hence configurePortsutility has to be run on each node. 2 3 Open a UNIX console and log on as root on the target host. If applicable. See “Preinstallation checklist for a Symantec OpsCenter Server installation” on page 176. cd OpsCenter/Server ■ 6 7 8 Type the following command:. you need to install OpsCenter Server manually on all the nodes. Note: Tomcat is not clustered or installed in the shared drive. The installer also examines the system for existing packages. unmount the OpsCenter shared mount point./installOpsCenterServer. The Welcome message is displayed. Also. 4 Make sure that the shared disk is not mounted on any node in the cluster. first install the OpsCenter Server on the active node and then on the passive nodes. To install a OpsCenter Server in clustered mode on UNIX 1 Fill out the checklist for all configurations and the checklist for your specific environment. You may install OpsCenter Server from the OpsCenter DVD or from the NetBackup media kit. If you are using the NetBackup media kit to install OpsCenter Server. . 5 Do one of the following: ■ If you are using the OpsCenter DVD to install OpsCenter Server software. Mount the OpsCenter product DVD for the appropriate platform on which you are installing. It prompts you in case OpsCenter is already installed. The installer then checks if OpsCenter Server is installed on the system or not. Stop the volume the mount point is on and deport the disk group for that volume on all nodes of the cluster. Press Enter to continue. Caution: When you are prompted. you are prompted to confirm creation of a OpsCenter Server cluster. a single node cluster resource group for OpsCenter is created and brought online. Review this list and press Enter to continue. To accept the default path (/opt). Symantec WebGUI Server. you must provide the same virtual cluster name that you provided during the installation. 12 When OpsCenter Server is installed on the clustered setup a confirmation prompt is displayed.180 Installing Symantec OpsCenter Clustering Symantec OpsCenter 9 The installer displays a list of components that are installed like PBX. You are prompted to join the group. information of already created NetBackup cluster group is displayed. ■ When installing OpsCenter Server on the first node. Symantec Database etc. 14 Allow OpsCenter to be installed in a cluster. This name is case sensitive and must be in same format (FQDN/short) on all the nodes. Type Yes to set up OpsCenter in HA mode. On the other nodes. When a OpsCenter Server is installed: ■ On the first node. 10 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. ■ 13 When you are prompted for cluster specific configuration details. press Enter without typing a directory path. 11 Type y to confirm the directory path and press Enter. the installed node is added to the cluster resource group. Use the virtual name for the NetBackup server name. When installing OpsCenter Server on the subsequent nodes. refer to the checklist and provide details accordingly. ■ . which resides in the root directory of the product DVD and also in /opt/VRTS/install directory. Change to the following directory: /opt/VRTS/install 3 Type the following command and press Enter: . it displays a summary of the uninstall./uninstallopscenterserver The Uninstall Script checks the components that are installed on the system. When the uninstall is complete. ■ Type n and press Enter to cancel the uninstall procedure. The Uninstall Script stops all processes and then uninstalls the component packages. including the location of the uninstall log files.Installing Symantec OpsCenter Clustering Symantec OpsCenter 181 Uninstalling OpsCenter Server from the cluster Use the Uninstall Script. . 4 When you are asked to confirm if you want to uninstall OpsCenter Server. To unistall OpsCenter Server on UNIX 1 2 Open a UNIX console and log on as root on the target host. do one of the following: ■ Type y and press Enter to start the uninstall process. to uninstall OpsCenter from a node on a UNIX host. 182 Installing Symantec OpsCenter Clustering Symantec OpsCenter . OpsCenter depends on these services. These topics assume you already installed OpsCenter on a server. If any of these services fail to start. If you have not installed OpsCenter. review the installation chapter. . the following services should be active. About services used by OpsCenter on Windows After you install OpsCenter server and Agent on Windows. OpsCenter does not start.Chapter 3 Administering Symantec OpsCenter This chapter includes the following topics: ■ ■ ■ ■ ■ ■ ■ 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. . This service is not an OpsCenter service.exe Controlling the services Use the following procedure to verify if these services are running or not. OpsCenter uses this service to authenticate users of OpsCenter. Check the Status column for each service.exe server Service Symantec Private Branch Exchange pbx_exchange. start. It also interacts with NetBackup through NBSL to get data regularly.exe Symantec Product Authentication Service vxatd. By default. The OpsCenter server interacts with the OpsCenter GUI and provides the data that is requested by the GUI from the OpsCenter database. OpsCenter uses this service to host the OpsCenter Console. This service manages the OpsCenter databases. Symantec Private Branch Exchange allows all socket communication to take place through a single port. To control these services 1 2 3 Use Start > Settings > Control Panel > Administrative Tools > Services. From the Status column. This service is not an OpsCenter service. but it is a component used by OpsCenter.exe Service Symantec OpsCenter Server Service java. This service is not an OpsCenter service. the following processes should be active. About processes used by OpsCenter on UNIX After you install OpsCenter server and Agent on UNIX.exe Symantec OpsCenter Database Server dbsrv11. the OpsCenter Agent Service starts whenever you boot your Agent host. Symantec OpsCenter Agent java.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.exe Symantec OpsCenter Web java. Table 3-1 Service Name Service Services used by OpsCenter on Windows Description This service is for the Symantec OpsCenter Agent. and restart the OpsCenter services and Symantec shared services. you can verify if a service is running or not. running reports and so on. The Services panel can also be used to stop. Table 3-2 describes the processes that OpsCenter uses on UNIX. This process must be running on the OpsCenter server during all normal operations like viewing reports. Symantec OpsCenter Server Symantec /opt/SYMCOpsCenterDatabase/bin/dbsrv11 OpsCenter Database Server Symantec OpsCenter Web Server java Symantec Private Branch Exchange /opt/VRTSpbx/bin/pbx_exchange Symantec Product Authentication Service /opt/VRTSat/bin/vxatd About OpsCenter server scripts on Windows and UNIX The following scripts are used within OpsCenter. By default. OpsCenter uses this process to host the OpsCenter Console. It also interacts with NetBackup to get data regularly. OpsCenter uses this process to authenticate users of OpsCenter. but it is a component used by OpsCenter. This process is not an OpsCenter process. running reports and so on. the OpsCenter Agent process starts whenever you boot your Agent host.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/. This process manages the OpsCenter databases. This process must be running on the OpsCenter server during all normal operations like viewing reports. This process is not an OpsCenter process. This process is not an OpsCenter process. Use the -h option for help about these scripts. /opt/SYMCOpsCenterServer/bin/. The OpsCenter administrator may use many of these scripts. PBX allows all socket communication to take place through a single port. Table 3-3 lists the OpsCenter server scripts on Windows.OpsCenterServerd The OpsCenter server interacts with the OpsCenter GUI and provides the data that the GUI requests from the OpsCenter database. . Many Symantec Web consoles share this component.OpsCenterAgentd This process is for the Symantec OpsCenter Agent. Table 3-4 lists the OpsCenter server scripts on UNIX. 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 OpsCenter Administrator OpsCenter Administrator dbdefrag. 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.bat runStoredQuery. opsadmin .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.186 Administering Symantec OpsCenter About OpsCenter server scripts on Windows and UNIX Table 3-3 Script startserver.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 INSTALL_PATH\OpsCenter\server\bin Runs saved custom SQL and OpsCenter Administrator generates output in the desired format.bat and stopdb.bat opsadmin. dbbackup. To start all OpsCenter server services ◆ Enter the following command: INSTALL_PATH\OpsCenter\server\bin\opsadmin.d This script is used OpsCenterServer internally for clustering. or restarts the OpsCenter database. stops. 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.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. The script starts. and OpsCenter Web server (Tomcat). OpsCenter Server.Administering Symantec OpsCenter About OpsCenter server scripts on Windows and UNIX 187 Table 3-4 Script OpsCenterServers OpsCenter server scripts on UNIX (continued) Function Invokes or Is Invoked by Location Solaris: /etc/init.bat start . 188 Administering Symantec OpsCenter About OpsCenter server scripts on Windows and UNIX To stop all OpsCenter server services ◆ Enter the following command: INSTALL_PATH\OpsCenter\server\bin\opsadmin. . 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 server service ◆ Select Control Panel > Administrative Tools > Services and start or stop the Symantec OpsCenter Server Service. 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 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 Agent service ◆ Select Control Panel > Administrative Tools > Services and start or stop the Symantec OpsCenter Agent Service. 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.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. Controlling the Symantec OpsCenter Agent Service The following procedure describes how you can control the Symantec OpsCenter Agent service on Windows servers. 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 start To stop all OpsCenter server processes ◆ Enter the following command to stop all OpsCenter server processes: /opt/SYMCOpsCenterServer/bin/opsadmin.Administering Symantec OpsCenter About OpsCenter server scripts on Windows and UNIX 189 Controlling all Symantec OpsCenter server processes on UNIX servers using opsadmin. stop.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 all OpsCenter server processes ◆ Enter the following command to start all OpsCenter server processes: /opt/SYMCOpsCenterServer/bin/opsadmin.sh script The following procedure describes how you can start. To start the database server ◆ Enter the following command: /opt/SYMCOpsCenterServer/bin/startdb To stop the database server ◆ Enter the following command: /opt/SYMCOpsCenterServer/bin/stopdb . and monitor all OpsCenter server processes using the opsadmin script. To start the OpsCenter Web server ◆ Enter the following command: /opt/SYMCOpsCenterGUI/bin/startgui.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. To start the OpsCenter server ◆ Enter the following command: /opt/SYMCOpsCenterServer/bin/startserver To stop the OpsCenter server ◆ Enter the following command: /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. .sh To stop the OpsCenter Web server ◆ Enter the following command: /opt/SYMCOpsCenterGUI/bin/stopgui.190 Administering Symantec OpsCenter About OpsCenter server scripts on Windows and UNIX Controlling the Symantec OpsCenter server process on UNIX servers The following procedure describes how you can control the OpsCenter server process on UNIX servers. Administering Symantec OpsCenter About OpsCenter server scripts on Windows and UNIX 191 To start the OpsCenter Agent ◆ Enter the following command: /opt/SYMCOpsCenterAgent/bin/startagent To stop the OpsCenter Agent ◆ Enter the following command: /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. and removed by NBSL. Note: Not all nbproxy processes on the master server are managed by NBSL. storage lifecycle policies). For example. you may find one or more nbproxy processes running on the master server. An nbproxy process runs to retrieve the following NetBackup data for OpsCenter: ■ ■ ■ ■ Policies Catalogs Storage lifecycle policies LiveUpdate . About nbproxy processes on NetBackup master servers When OpsCenter is connected to a master server. Most of the nbproxy processes are started. then the OpsCenter server also stops. some of the nbproxy processes are managed by nbjm and nbpem. You may also see nbproxy processes when NetBackup-Java GUI or NetBackup-Windows GUI request certain data from NetBackup (like LiveUpdate . This section talks about the nbproxy processes that NBSL manages. managed. See “Defragmenting the OpsCenter database” on page 194. dbdefrag dbbackup . More information about Sybase database is available. Table 3-5 lists the commands that are available. The database is located on the OpsCenter server. See “Backing up the OpsCenter database ” on page 200. all nbproxy processes are stopped immediately. Running OpsCenter commands OpsCenter provides some useful commands to help manage the OpsCenter database.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. Table 3-5 Command changeDbPassword Commands available with OpsCenter Reference See “Changing the OpsCenter database administrator password” on page 193. See “Restoring the OpsCenter database” on page 203. the nbproxy process is removed within an hour. If NetBackup is stopped (and NBSL is already killed). See http://www. ■ ■ ■ 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. all nbproxy processes are stopped immediately. These utilities also let you change the authentication server parameters and provide user help. If NBSL crashes (or is abruptly closed).sybase. all nbproxy processes exit within 10 minutes.com/support/manuals. If OpsCenter crashes (or is abruptly closed). ^ | < > . OpsCenter uses the Sybase SA (Server Anywhere) database to store data. The database administrator user ID is DBA and the initial password is SQL (password is case sensitive). . Note: This utility is not used to change the logon password for OpsCenter. ‘ ! $ % & . { } $ " ~ [ ] \\ Contains the ASCII characters that are less than 32 or ASCII characters that are greater than 127. The OpsCenter database administrator password cannot have the following characteristics: ■ ■ ■ ■ Exceed 30 characters. Review the rules for forming a new database password. . To change the existing logon password. Contain any bracket [ ] characters. See “Changing your password” on page 225. you must use the OpsCenter console. Contain consecutive black slash characters. Begin with White space and a single quote character.Administering Symantec OpsCenter About OpsCenter database administration 193 Table 3-5 Command Commands available with OpsCenter (continued) Reference See “Configuring authentication server parameters” on page 194. These characters have special meaning in Windows or in shell scripts. End with White space. See “About user access rights” on page 235. 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: Information about role-based access in Symantec OpsCenter is available. You require a user name and a password to access the data that is stored in the database. Contain any of the following characters. run the following command: /opt/SYMCOpsCenterServer/bin/dbdefrag. You are prompted for a new database administrator password.194 Administering Symantec OpsCenter About OpsCenter database administration To change the database administrator password on Windows and UNIX 1 Enter the following command on Windows: INSTALL_PATH\OpsCenter\server\bin\changeDbPassword. Enter the old database password. Defragmentation helps to increase data access and retrieval speed. This procedure is not applicable when Symantec Product Authentication Service is installed on the local machine.bat To defragment the OpsCenter database on UNIX. To defragment the OpsCenter database on Windows and UNIX ◆ To defragment the OpsCenter database on Windows.sh 2 3 You are prompted for the old database administrator password. Note: This procedure is applicable only for OpsCenter clusters where the authentication broker is remote. . run the following command: INSTALL_PATH\OpsCenter\server\bin\dbdefrag. Defragmenting the OpsCenter database You can defragment the OpsCenter database using the dbdefrag command. defragment the OpsCenter databases periodically and after a purge operation.bat Enter the following command on UNIX: /opt/SYMCOpsCenterServer/bin/changeDbPassword. Enter the new password.sh Configuring authentication server parameters The authentication server parameters can be configured using the changeVxATProperties utility. Note: OpsCenter does not work during the time when the OpsCenter database is defragmented. For optimum performance. Saving the OpsCenter database and database logs on separate hard disks To improve OpsCenter performance. . You must restart the OpsCenter services for these changes to be effective. the value of the parameter does not change. The last two procedures are for moving the database log files.sh The authentication server parameters appear one by one. Answer y to restart the OpsCenter services. Use the following procedures to move the OpsCenter database and log files to a different hard disk. Symantec also recommends that you not store the database files on the hard disk that contains your operating system files. If you do not enter a new value for a parameter.bat Enter the following command on UNIX: /opt/SYMCOpsCenterServer/bin/changeVxATProperties. The default location for the OpsCenter database can also be changed after OpsCenter has been installed. The current values of the parameters are specified in brackets. The first two procedures are for moving the OpsCenter database files on Windows or UNIX. You can specify a custom location (non-default location) for the OpsCenter database during OpsCenter installation. You can store the OpsCenter database files on one hard disk and the log files on another hard disk.Administering Symantec OpsCenter About OpsCenter database administration 195 To configure authentication server parameters 1 Enter the following command on Windows: INSTALL_PATH\OpsCenter\server\bin\changeVxATProperties. 2 3 Enter the new values next to the respective parameter. OpsCenter database files and the log files that are associated with the OpsCenter database should be stored on separate hard disks. # etc. Copy vxpmdb. . For example.db" Make sure that you specify the path in double quotes. @.bat stop 2 Open the databases.196 Administering Symantec OpsCenter About OpsCenter database administration To move the OpsCenter database to a different hard disk on Windows 1 Stop all OpsCenter server services. Enter the following command: INSTALL_PATH\OpsCenter\server\bin\opsadmin.db" This path specifies the default location of the OpsCenter database.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.bat start You should run and monitor OpsCenter for a certain period after moving the database. To restart all OpsCenter services. enter the following command: INSTALL_PATH\OpsCenter\server\bin\opsadmin. !.db from the default location (INSTALL_PATH\OpsCenter\server\db\data). If OpsCenter works as expected. &. Also the directories in the specified path should not contain any special characters like %.conf file. 4 5 Copy the database file to the new location. replace the contents of the file with the following: "E:\Database\vxpmdb. ^. you can delete vxpmdb. do not specify a path like E:\Database%. ~. Restart all OpsCenter server services. 3 To move the database to a custom location like E:\Database. Save the databases.db from INSTALL_PATH\OpsCenter\server\db\data to a location like E:\Database. $. To move the database to a custom location like /usr/mydata. you can delete vxpmdb.db from /opt/SYMCOpsCenterServer/db/data.enter the following command: mv /opt/SYMCOpsCenterServer/db/data /usr/mydata 3 Create a symbolic link to /usr/mydata in /opt/SYMCOpsCenterServer/db/data. Enter the following command: /opt/SYMCOpsCenterServer/bin/opsadmin. If OpsCenter works as expected.sh stop 2 The default location of the OpsCenter database in UNIX is /opt/SYMCOpsCenterServer/db/data. enter the following command: ln -s /usr/mydata /opt/SYMCOpsCenterServer/db/data 4 Restart all OpsCenter server processes by entering the following command: /opt/SYMCOpsCenterServer/bin/opsadmin.Administering Symantec OpsCenter About OpsCenter database administration 197 To move the OpsCenter database to a different hard disk on UNIX 1 Stop all OpsCenter server processes.sh start You should run and monitor OpsCenter for a certain period after moving the database. To create a symbolic link. . Enter the following command: INSTALL_PATH\OpsCenter\server\bin\opsadmin. enter the following command: INSTALL_PATH\OpsCenter\server\bin\opsadmin.log database_path\vxpmdb.bat start To move the database log files to a different hard disk on UNIX 1 Stop all OpsCenter server processes. Enter the following command: /opt/SYMCOpsCenterServer/bin/opsadmin. This command moves the log file that is associated with the OpsCenter database to the new directory (directory_path). 3 Restart all OpsCenter server services.log as the name of the log file.198 Administering Symantec OpsCenter About OpsCenter database administration To move the database log files to a different hard disk on Windows 1 Stop all OpsCenter server services. It is recommended to use vxpmdb.sh stop 2 Set the path of the LD_LIBRARY_PATH variable in the following manner: LD_LIBRARY_PATH=/opt/SYMCOpsCenterDatabase/lib:$LD_LIBRARY_PATH export LD_LIBRARY_PATH .bat stop 2 Navigate to the following location: INSTALL_PATH\OpsCenter\server\db\WIN32 Enter the following commands: dblog -t directory_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. To restart all OpsCenter services. See “About OpsCenter log files on Windows servers” on page 215.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).sh start About database troubleshooting Security information about the OpsCenter database is available./dblog -t directory_path/vxpmdb. 4 Restart all OpsCenter server processes by entering the following command: /opt/SYMCOpsCenterServer/bin/opsadmin. Backing up OpsCenter The sequence of steps gives an overview about the steps that need to be followed to back up OpsCenter. Information about the log files on Windows and UNIX servers is available. See “About OpsCenter log files on UNIX servers” on page 217.log as the name of the log file.Administering Symantec OpsCenter About backup and restore of OpsCenter and OpsCenter Analytics 199 3 Navigate to the following location: /opt/SYMCOpsCenterDatabase/bin Enter the following commands: .log database_path/vxpmdb. It is recommended to use vxpmdb. See “About OpsCenter Web GUI/OpsCenter server to Sybase database communication” on page 211. 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. In this case. The script backs up or restores the vxpmdb. Note: You can also create schedules for taking regular database and authentication profile backups.db and vxpmdb. the user information that Symantec Product Authentication Service manages must be saved in a directory or by using a NetBackup backup policy.log file (if it exists). On UNIX as well as Windows platforms. 2 Along with the OpsCenter database. See the NetBackup Administrator’s Guide. Volume I for more information on how to configure a policy and schedule. See “Backing up the OpsCenter database ” on page 200.200 Administering Symantec OpsCenter About backup and restore of OpsCenter and OpsCenter Analytics To back up OpsCenter in case of a disaster 1 Take a hot backup of the OpsCenter database (vxpmdb) using the dbbackup script. which is referred to as hot backup. The database files are as follows: vxpmdb. you also need to back up the database password file. Backing up the OpsCenter database OpsCenter is shipped with a database backup script that performs backup of the database without interrupting its operations. This script can be run whenever you need to back up your OpsCenter database. Note: Regular file system backups are not sufficient for backing up the OpsCenter database. See “Backing up the OpsCenter database password file” on page 202. You must schedule periodic hot backups for the OpsCenter database to avoid losing any important data. . 3 If you want to change the OpsCenter database password. the script overwrites existing database (db) files before backing up or restoring the database. See “Saving the OpsCenter user profiles managed by Symantec Product Authentication Service” on page 201.db and vxpmdb.log. NetBackup policies can be created to back up the specified directories that contain OpsCenter database snapshots and the authentication service user configuration files. 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 systemprofile folder. 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.Administering Symantec OpsCenter About backup and restore of OpsCenter and OpsCenter Analytics 201 To back up the OpsCenter database 1 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. Create a NetBackup job policy to back up the authentication service profile folder.db and vxpmdb. Specify one of the following backup directories depending on your platform: Windows INSTALL_PATH\OpsCenter\server\bin\dbbackup. Run the backup script that is appropriate for your platform. . 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.log (if it exists) in the backup directory that you specified.sh /my_db_backup_dir UNIX The backup script creates vxpmdb.bat C:\MyDbBackupFolder /opt/SYMCOpsCenterServer/bin/dbbackup. See “Restoring the OpsCenter database” on page 203. This limitation involves authentication service credentials (host name and IP address) which are stored on the server. See “Restoring the OpsCenter user profiles managed by Symantec Product Authentication Service” on page 205. Copy the db. Stop all OpsCenter server services. 4 If you saved a copy of the OpsCenter database password file. 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. To back up the OpsCenter database password file on Windows ◆ Back up the db. 5 .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. Note: The following procedures assume that you have OpsCenter database snapshots and the authentication service user profiles saved in folders.202 Administering Symantec OpsCenter About backup and restore of OpsCenter and OpsCenter Analytics 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).conf file to INSTALL_PATH/OpsCenter/server/config directory on Windows or /opt/SYMCOpsCenterServer/config directory on UNIX. Restore the OpsCenter database snapshot files and authentication service user profiles from the backup image. The sequence of steps gives an overview about the steps that need to be followed to restore OpsCenter.conf file that is located in INSTALL_PATH/OpsCenter/server/config directory. copy the file to the corresponding location on the newly installed OpsCenter server. To back up the OpsCenter database password file on UNIX ◆ Back up the db. Restart all OpsCenter server services. log.log file (if it exists). The dbbackup script overwrites existing database (db) files before backing up or restoring the database. The database files are as follows: vxpmdb. .Administering Symantec OpsCenter About backup and restore of OpsCenter and OpsCenter Analytics 203 Restoring the OpsCenter database After you back up the database. and restarts the database.db and vxpmdb. restores the backup database files. The script backs up or restores the vxpmdb. the restore operation automatically stops the database. you can restore it. On Windows and UNIX hosts.db and vxpmdb. Do you wish to continue ? [y/n] (n) .204 Administering Symantec OpsCenter About backup and restore of OpsCenter and OpsCenter Analytics To restore a backed up OpsCenter database 1 On the OpsCenter server whose backup data you want to restore. do one of the following: Windows Type the following command and press Enter. The script prompts you with a message similar to the following: WARNING: this operation will overwrite the active OpsCenter data on this host. and <restoreDir> is the location of the current OpsCenter database. you must specify the restoreDir option. INSTALL_PATH\OpsCenter\server\bin\dbbackup. 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).sh <backupDir> -restore <restoreDir> where backupDir is the directory where the backed up database resides. If not used. Windows Open a Windows command prompt and log on as an administrator or user in the Administrators group. restoreDir is optional. 2 To restore the backed up database.bat <backupDir> -restore <restoreDir> UNIX Type the following command and press Enter. Open a UNIX console and then log on as root. These paths may different for your site if the database was installed anywhere other than the default location. /opt/SYMCOpsCenterServer/bin/dbbackup. 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. UNIX All the paths that are shown in the steps that follow are the default database install paths. type y on UNIX hosts. 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. The dbbackup script automatically stops and restarts the database.bat stop 2 3 Copy or overwrite the folder containing the authentication service user profiles to INSTALL_PATH\VERITAS\Security\Authentication\systemprofile. Enter the following command: INSTALL_PATH\OpsCenter\server\bin\opsadmin. To restore the authentication user profiles on Windows 1 Stop all OpsCenter server services.bat start To restore the authentication user profiles on UNIX 1 Stop all OpsCenter server processes. press Enter on Windows hosts. To continue with the restore. Enter the following command: INSTALL_PATH\OpsCenter\server\bin\opsadmin. . Enter the following command: /opt/SYMCOpsCenterServer/bin/opsadmin.sh start About communication and firewall considerations Figure 3-1 shows the key OpsCenter components and the communication ports that are used.sh stop 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: /opt/SYMCOpsCenterServer/bin/opsadmin.Administering Symantec OpsCenter About communication and firewall considerations 205 3 To continue with the restore. Start all OpsCenter server services. . Port 8282 and Port 8553.are installed The following table shows the default port settings for OpsCenter. The SNMP trap recipient ports can also be configured from the OpsCenter console (using Settings > Recipients > SNMP). PureDisk etc. PureDisk etc. are installed NetBackup Master Server without NBAC Hosts where backup products like Backup Exec. and. SMTP recipient ports can be configured from the OpsCenter console (using Settings > Configuration > SMTP Server).206 Administering Symantec OpsCenter About communication and firewall considerations 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 8181 and Port 8443..Port 80 and Port 443. 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. Table 3-6 lists the communication ports that are used by key OpsCenter components. See “About OpsCenter Web GUI to OpsCenter server software communication” on page 210. PBX port number configuration is not supported. 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. 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.Administering Symantec OpsCenter About communication and firewall considerations 207 If these ports are changed then the appropriate hardware ports have to be opened. 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: 1 80 (HTTP) and 443 (HTTPS) 8181 (HTTP) and 8443 (HTTPS) 8282 (HTTP) and 8553 (HTTPS) Sybase database Allow between source and destination. Authentication Service (vxatd) 2 3 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. .208 Administering Symantec OpsCenter About communication and firewall considerations Table 3-6 Communication ports used by key OpsCenter components (continued) Usage (Process Port Configuration Name) Allow from all hosts on network. Backup Exec. TSM etc. Symantec Allow between source and destination in case Product NBAC is enabled on NetBackup master server. Table 3-7 lists the ports that must be opened on OpsCenter Agent to collect data from various backup products. PureDisk. (dbsrv11) Some hardened servers and firewall configurations may block this port. 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 EMC Legato Networker 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.exe bpimagelist.exe bpretlevel. These protocols use TCP/IP. 13782 port should be used to connect to the NetBackup master server and 13724 port should be used to respond to the Agent host. .Administering Symantec OpsCenter About communication and firewall considerations 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. specific ports are checked for availability in a particular sequence and the first available port is used by default. 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. For HTTP. 8282 8553 Port 8282 and Port 8553 are checked for availability. some other application like a Web server uses one or both ports. ■ In case. If port 8181and port 8443 are available. ■ In case. ■ 2. port 80 is used as the default HTTP port and port 443 is used as the default HTTPS port. . The default port is 1556. port 8181 is used as the default HTTP port and port 8443 is used as the default HTTPS port. then the next port combination is checked for availability. The PBX port is opened for input and output traffic. ■ 3. 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. These HTTP and HTTPS ports are opened only for input and are configurable using the command lines. Default HTTP and HTTPS ports HTTPS port number 443 HTTP port number 80 Description Port 80 and Port 443 are checked for availability. 1. No.210 Administering Symantec OpsCenter About communication and firewall considerations Table 3-8 lists how the default HTTP and HTTPS ports are selected. 8181 8443 Port 8181 and Port 8443 are checked for availability. If port 80 and port 443 are available. then the next port combination is checked for availability. Table 3-8 Sr. See configurePorts on page 566. some other application like VRTSWeb installed with VCS or any other product uses one or both ports. 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 initial data load happens serially for each data type. you can configure the same in OpsCenter while adding or editing a master server. The Sybase database server port is closed to all inbound connections. 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.Administering Symantec OpsCenter About communication and firewall considerations 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 default PBX port that is used is 1556. As soon as the initial data load is complete. 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. the OpsCenter server software listens to notifications sent by NBSL for any change in NetBackup data. See “Adding a master server” on page 278. The port number is 162. If you change the PBX port on the NetBackup master server. when data collection for a master server is enabled or when a master server is added to OpsCenter. About OpsCenter Web GUI to OpsCenter server email communication SMTP email server protocol is used for outgoing mail. the OpsCenter server starts collecting all the available data from NetBackup master server into the OpsCenter database using NBSL. About SNMP traps SNMP trap protocol is used for outbound UDP traffic and requires a port that opens for output. The database is available only to resident OpsCenter components on the OpsCenter server. and updates the OpsCenter database. The port number is defined when the user specifies the SMTP server port (see Settings > Configuration > . The port is opened for output only. collects information about any data collection problems.zip file. To gather troubleshooting data with the support script on Windows 1 Run the following commands to execute the support scripts for server and agent respectively: INSTALL_PATH\OpsCenter\server\bin\opsCenterSupport. you can use the supportscript to gather troubleshooting information for OpsCenter server and OpsCenter Agent. The script collects server and agent logs. Adding log files and OpsCenter database files can increase the file size of the resulting Support. This file can serve as a first-level information for the Support team in case of an issue with OpsCenter.zip. to this zip file. captures the current agent configuration. 3 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 4 After the zip file is created. 2 This script stops all the OpsCenter services and then collects system information and OpsCenter configuration information. Gathering troubleshooting data with the support script If you are running OpsCenter on UNIX or Windows. You can also choose to add log files. the script starts all the OpsCenter services. . and compresses the results into a zip file. It then compresses all this information in a file that is called Support.212 Administering Symantec OpsCenter Gathering troubleshooting data with the support script SMTP Server in the OpsCenter console to specify this port).bat Note: The following are the default directory locations on Windows machines. OpsCenter database files etc.bat INSTALL_PATH\OpsCenter\Agent\bin\opsCenterAgentSupport. . Adding log files and OpsCenter database files can increase the file size of the resulting Support. Table 3-9 shows the originator IDs used by OpsCenter and key shared components. and other log file formats. legacy. 2 This script stops all the OpsCenter processes and then collects system information and OpsCenter configuration information.sh Note: The following are the default directory locations on UNIX machines. OpsCenter components create most log messages in VxUL format.sh /opt/SYMCOpsCenterServer/bin/opsCenterAgentSupport. performance. See “About OpsCenter log files on Windows servers” on page 215. and other issues.zip. About VxUL log files The VxUL log file creates log file names and messages in a format that is standardized across all Symantec components. 3 This zip file is stored in the following directories: For OpsCenter Server: /opt/SYMCOpsCenterServer/temp/support For OpsCenter Agent: /opt/SYMCOpsCenterAgent/temp/support 4 After the zip file is created.zip file. It then collates all this information in a Support. OpsCenter writes log files using Veritas Unified Logging (VxUL). About OpsCenter log files OpsCenter creates log files that you can use to troubleshoot installation. These messages use VxUL IDs (a product ID and an originator ID) that identify the component that wrote the log message. You can also choose to add log files. to this zip file. OpsCenter database files etc. See “About OpsCenter log files on UNIX servers” on page 217. the script automatically starts all the OpsCenter processes.Administering Symantec OpsCenter About OpsCenter log files 213 To gather troubleshooting data with the support script on UNIX 1 Run the following commands to execute the support scripts for server and agent respectively: /opt/SYMCOpsCenterServer/bin/opsCenterSupport. The following OID values must be used for OpsCenter server. OpsCenter writes VxUL logs to the following directory: INSTALL_PATH\OpsCenter\server\logs In UNIX. To configure the verbosity level (default value is 1) INSTALL_PATH\OpsCenter\server\bin\vxlogcfg. OpsCenter writes VxUL logs to the following directory: /opt/SYMCOpsCenterServer/logs You can control how OpsCenter writes log files for OpsCenter Server.exe -a -p 58330 -o <OID> -s DebugLevel=1 . and OpsCenter Web GUI. OpsCenter Agent. and the 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.214 Administering Symantec OpsCenter About OpsCenter log files 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 Agent. . 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. 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. About OpsCenter log files Table 3-12 shows details about the OpsCenter log files.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.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.Administering Symantec OpsCenter About OpsCenter log files 215 Table 3-10 Control Logging Control logging on Windows (continued) Command To configure the diagnostic INSTALL_PATH\OpsCenter\server\bin\vxlogcfg. log platforms: %ProgramFiles% vssconfig.log Troubleshooting purpose OpsCenter Sybase database activity.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.log These log files for system. Table 3-13 Log file directory Log files for Symantec Product Authentication Service Log file Troubleshooting purpose Authentication activity.216 Administering Symantec OpsCenter About OpsCenter log files Table 3-12 Log file directory INSTALL_PATH\ OpsCenter\server\ logs\ OpsCenter log files Log file Troubleshooting purpose ServerService_timestamp. vxpmdb. .err and system. On 32-bit Windows vxatd. OpsCenter Sybase database transaction files.out of OpsCenter server service. 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. About log files associated with Symantec Product Authentication Service Table 3-13 lists the log files that are associated with Symantec Product Authentication Service.log Note: Do not change this log file. Table 3-16 Log files for OpsCenter Troubleshooting purpose stdout and stderr for the OpsCenterServer daemon.log /opt/SYMCOpsCenterServer/logs/ purge-status.log Agent activity.log logs\ INSTALL_PATH\ OpsCenter\Agent\logs INSTALL_PATH\ OpsCenter\gui\logs\ INSTALL_PATH\ OpsCenter\server\logs 51216-146-*. 51216-147-*.Administering Symantec OpsCenter About OpsCenter log files 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. Table 3-15 Log file directory Log files associated with VxUL and other components Log file Troubleshooting purpose PBX activity.log /var/VRTS/install/logs/ (directory) Provides a trace for any installation issues. 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.log INSTALL_PATH\VERITAS\NetBackup\ 51216-132-*.log OpsCenter server activity. Shows the details of purge operations.log OpsCenter Web GUI activity. OpsCenter log file /opt/SYMCOpsCenterServer/logs/ OpsCenterServer_out. 58330-148*. INSTALL_PATH\VERITAS\VxPBX\bin\ 50936-103-*. 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. NBSL activity. About log files associated with OpsCenter database Table 3-18 lists the log files that are associated with the OpsCenter database.log Note: Do not change this log file.218 Administering Symantec OpsCenter About OpsCenter log files About log files for Symantec Product Authentication Service Table 3-17 lists the log files that are associated with Symantec Product Authentication Service.log . OpsCenter log file /opt/VRTSpbx/log/50936-103-*. About log files associated with OpsCenter Web server Table 3-19 lists the log files that are associated with the OpsCenter Web server.log /opt/SYMCOpsCenterServer/db/data/ OpsCenter Sybase database transaction files. Table 3-20 Log files associated with VxUL and other components Troubleshooting purpose PBX activity. NBSL activity.log Log files for Symantec Product Authentication Service Troubleshooting purpose Authentication activity. vxpmdb. Table 3-17 Log file /var/VRTSat/vxatd. 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-19 Log files associated with the OpsCenter Web server Troubleshooting purpose OpsCenter Web GUI application activity (stdout). OpsCenter log file /opt/SYMCOpsCenterServer/db/log/ dbserver. Table 3-18 Log files associated with OpsCenter database Troubleshooting purpose OpsCenter Sybase database activity.log /opt/openv/logs/51216-132-*. OpsCenter server activity.Administering Symantec OpsCenter About OpsCenter log files 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 OpsCenter Web GUI activity.log /opt/SYMCOpsCenterGUI/logs/ 51216-147-*.log /opt/SYMCOpsCenterServer/logs/ 558330-148*. 220 Administering Symantec OpsCenter About OpsCenter log files . Chapter 4 Understanding OpsCenter settings This chapter includes the following topics: ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ 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 . An OpsCenter Admin can configure these settings using the OpsCenter console. See “ Adding license keys” on page 226.222 Understanding OpsCenter settings About the settings in OpsCenter About the settings in OpsCenter This section describes the various OpsCenter settings. Agent License Manage permanent or demo license keys. Object Merger Configure OpsCenter to merge the objects See “Merging objects (hosts) that represent the same backup client. ” on page 231. Following are the various settings that you can configure in OpsCenter. collection for NetBackup” on page 270. which the OpsCenter Admin has set. Configure Symantec ThreatCon feature in OpsCenter. Table 4-1 Name of the setting Settings in OpsCenter Lets you. See “Managing OpsCenter Agents” on page 264. but registered as separate objects . Specify when you want to purge the data See “Configuring data purge that is collected from various products. Reference topic User Preferences Add user-specific details and create user See “Setting user profiles. Create Agent and Data Collectors to collect data from non-NetBackup products. settings” on page 227. See “Adding host aliases” on page 230. See “Configuring Symantec ThreatCon feature in OpsCenter” on page 229. through emails. Data Purge SMTP Sever ThreatCon Host Alias Add aliases for hosts. preferences” on page 223.. The normal users can view or access the information that is relevant only to their profiles. NetBackup Add NetBackup master servers and their See “Configuring data properties to collect data from it. Configure the SMTP server details that See “Configuring SMTP you need while sending reports or alerts server” on page 228.. The Symantec ThreatCon feature is used to show how secure or vulnerable your network is. location” on page 233.. You can select a currency currency for cost reports” from the global currency list and set it as on page 249. See “Copying user profiles” on page 232. Recipients Manage Email and SNMP recipients. 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.. See “Managing cost estimation” on page 255. Currency Settings Manage the currency settings that appear See “Setting a default in cost reports. See “Managing cost formulae” on page 254. Views Create and manage OpsCenter views.Understanding OpsCenter settings Setting user preferences 223 Table 4-1 Name of the setting Tape Library Settings in OpsCenter (continued) Lets you. such as email ID or name. Cost Variables Cost Formulae Create cost formulae. You can also change your password using the User Preferences tab. if your user account belongs to the OpsCenterUsers domain. such as default locale or time zone and personal details. Cost Estimation Manage cost estimation Setting user preferences In OpsCenter. See “Managing Cost Variables” on page 251. See “Managing users” on page 235. Users Manage users and user groups. See “Managing Object Types” on page 233. See “Managing views” on page 311. . Add new object types and attributes. See “Managing recipients” on page 243. you can set your preferences. default. Modify tape library information Reference topic See “Merging objects (hosts) ” on page 231. Create cost variables. Select a preferred time zone . all OpsCenter GUI screens use English as a default language. Report data is grouped depending on this start time. The user preferences options are organized in the General and My Profile tabs. the auto-refresh option is enabled. By default. Enter the time that is used as the start time of a day in reports. OpsCenter displays time on the GUI screens according to the selected time zone. if you want to refresh the OpsCenter GUI to show updated data after every 5 minutes. Click the General tab to set the following user preferences: Default Locale Select a locale of your choice from the drop-down list. enter five in the Auto Refresh Interval text box. Select this check box if you do not want to automatically refresh the OpsCenter GUI. if you select English as a default locale. Data Display Time Zone Start 24 Hour Day at Disable Auto Refresh 3 Click Save.224 Understanding OpsCenter settings Setting user preferences To set user preferences 1 2 In the OpsCenter console. For example. click Settings > User Preferences.either OpsCenter Server time zone or any other time zone from the Other drop-down list. Auto Refresh Interval (Minutes) Enter auto-refresh interval in minutes. For example. . Understanding OpsCenter settings Setting user preferences 225 4 Click the My Profile tab to view the following options: You can modify some of the options. 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. 5 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. Displays the work number of the user. Displays the mobile number of the user. User Name Password Displays the user name. click the Change Password link. The users that belong to the “OpsCenterUsers” domain can change their passwords after logging on . Displays the pager number of the user. To change password. The OpsCenter security admin sets a default password for each user when it creates the profiles. See “Changing your password” on page 225. In the My Profile dialog box. In the Change Password dialog box. . See “ Deleting license keys” on page 227. click Settings > My Profile. click Change Password. 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. To use the advanced features that are not available in Symantec OpsCenter. ■ 4 Click Save. Passwords are case sensitive and must contain at least five characters. you need to use a license key and enable Symantec OpsCenter Analytics. Click Add. Type your new password again in the Confirm New Password text box. Click the License tab. See “ Adding license keys” on page 226. enter a license key and click OK.226 Understanding OpsCenter settings Managing licenses To change the password with which you log on to OpsCenter 1 2 3 In the OpsCenter console. See “ Viewing license keys” on page 227. In the console. See “About Symantec OpsCenter” on page 19. To addOpsCenterlicense keys 1 2 3 4 5 Logon to the OpsCenter server host as admin. On the Add License Key pop-up screen. Type the new password in the New Password field. do the following: ■ ■ Type the existing password in the Old Password field. Managing licenses This section provides procedures to manage license keys from the OpsCenter. You can add one or more OpsCenter license keys. click Settings > Configuration . which is located in the OpsCenter server logs directory. . In the console. Click the License tab. Configuring data purge settings You can configure the OpsCenterServer retention periods for the data types that are logged. To configure data purge period on the OpsCenterServer 1 2 3 Log on to the OpsCenter console as admin. Click Delete. To view OpsCenter license keys 1 2 3 Logon to the OpsCenterServer host as admin. Policy. click Settings > Configuration. By default. In the OpsCenter click Settings > Configuration. and Skipped Files. Click the License tab. Select the check box in front of the license key that you want to delete. data purge is enabled. click Settings > Configuration. Click the Data Purge tab.log file. such as Job. Note: The details of the purged data are stored in the purge-status. In the OpsCenter console. To delete Symantec OpsCenter Analytics license keys 1 2 3 4 5 Log on to the OpsCenter Server host as admin.Understanding OpsCenter settings Configuring data purge settings 227 Viewing license keys You can view the license keys that are installed on the OpsCenterserver host. on which you are connected as an administrator. Deleting license keys You can remove one or more Symantec OpsCenter Analytics license keys from the OpsCenter Server. the corresponding logs are collected again. enter the time of day (in 24-hour clock format) When you want to purge the data. 5 6 In the Time of Purge text box. Note: If logs are purged but the respective jobs are not purged.228 Understanding OpsCenter settings Configuring SMTP server 4 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 backup jobs are set to be purged after 10 days. logs can be purged earlier than their respective jobs. or they can be purged at the same time. click Settings > Configuration. In the OpsCenter console. . The backup logs are purged after five days but the related jobs are still present. For example: The data purge setting for backup jobs is set to 10 days and for Backup Logs are five days. For example. Backup Log Set the number of days after which you want to purge the backup logs. Alert data older than this number is purged from the OpsCenter database. In other words. Click Save. The number of days set for backup logs should be less than or equal to the number of days set for backup jobs. To configure SMTP server settings for OpsCenter 1 2 Logon to the OpsCenter server as admin. the logs of such jobs are collected again by the OpsCenter Agent. Thus. Configuring SMTP server This section provides the procedure to configure the SMTP server that you can use for sending emails and alerts. Because. 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. . Enter the password for this user account. Enter the user name. The Symantec ThreatCon feature is used to show how secure or vulnerable your network is. SMTP server port Enter the SMTP (Simple Mail Transfer Protocol) Server port number. Notifications of alerts that are generated in OpsCenter are sent using this SMTP server. uncheck the box next to Enable ThreatCon Collection . Some SMTP servers may require user name and password credentials to send email. To disable ThreatCon. Use the following procedure to enable or disable the Symantec ThreatCon feature. Backup Reporting Department Specify the email ID to receive any replies to alerts or the reports that were sent by OpsCenter.Understanding OpsCenter settings Configuring Symantec ThreatCon feature in OpsCenter 229 3 Click SMTP Server. 4 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. The ThreatCon feature is enabled by default. Configuring Symantec ThreatCon feature in OpsCenter This section provides information on how to configure the Symantec ThreatCon feature in OpsCenter. Sender Display Name Sender Display Email Address Server User Name 5 Click Save.See “About the Symantec ThreatCon pane” on page 53. Server User Password Some SMTP servers may require user name and password credentials to send email. OpsCenter uses these global server settings to send email notifications using the SMTP server that you specify. For example. Enter the name that is associated with the email ID. . Server Name Note: The proxy server configuration is not mandatory. Port User Name Password Enter the port number to connect to the proxy server. For example. In the OpsCenter. Click ThreatCon. the explorer stops collecting information from the OpsCenter host and instead attempts to collect data from a host with the alias name. Set the password for the user account that you use to connect to the proxy server. click Settings > Configuration.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. Polling Interval Set the minutes for Polling Interval. Edit the following default information: Enable ThreatCon Collection Disable or enable the ThreatCon data collection using this check box. if the default network is down. Adding host aliases This section provides the procedures to add aliases for hosts. if you use an alias that is unknown to OpsCenter. The host’s primary alias is displayed in all console functions and reports. 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. 5 Click Save. Other host aliases are used when you are search in OpsCenter or gather and collate data. Enter the proxy server name. Enter the user name of the proxy server. Enter the following proxy server details if you want to use it for accessing the latest ThreatCon ratings. click Settings> Configuration > Host Alias. From the drop-down list select a host name or type a host name. but registered as separate objects (hosts). Click Validate Object Merging. Using the OpsCenter UI. All the existing aliases are displayed. and Click Show Alias. To modify the Source Host or Target Host click Back. Select the Host Type: Master Server. Enter the alias name for the host that you have selected from the drop-down list. In the OpsCenter console. media server. at a time. click Save Merging objects (hosts) OpsCenter provides a facility to merge objects (hosts) that represent the same master server. Select the Source Host from the drop-down list. you can merge only one object into other.Understanding OpsCenter settings Merging objects (hosts) 231 To add a host alias 1 2 In the OpsCenter console. To merge two objects 1 2 3 4 5 6 7 Logon to the OpsCenter Server host with administrator privileges. An auto-suggest feature is available. or Client. Media Server. In OpsCenter. You can view the snapshot of the selection that you have made earlier. backup client. Caution: Object merging is not reversible. To begin the merge click Start Merge Repeat these steps if you want to merge more objects. . you can merge objects (hosts) representing the same backup client. click Settings > Configuration > Object merger. Select the Target Host from the drop-down list. 3 4 5 Click Add Alias. An auto-suggest feature is available. Click Tape Library. slot count of the tape drives the data collector uses. click Settings > Configuration > Copy User Profile Select the source user account from the From User drop-down list. Copying user profiles Most user-definable content. Copy user profile 1 2 3 4 5 6 Logon to the Symantec OpsCenter Server with administrator privileges. click Settings > Configuration. Edit the following information: Type Serial Number Manufacturer Alias Slot Count Select the type of tape library from the drop-down list. Enter the slot count you want for the tape library. for example reports or cost rates and formulae. manufacturer. Select the target user account from the To User drop-down list. is accessible only by the user who has created it.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. alias. you can edit the serial number. To modify tape library information in OpsCenter 1 2 3 4 5 Log on to the OpsCenterServer with administrator privileges. In the OpsCenter console. cost variables. for which you want to edit the information. Using the copy user profile functionality. Enter the serial number of the tape library Enter the manufacturer of the tape library. Using the OpsCenter UI. Select the check box next to tape library. 6 Click Save. Click Next . You can view the list of the tape libraries in OpsCenter. select the items you want to copy. In the Copy Items options. In the OpsCenter. and cost formulas. you can copy information from one user account to another. Enter the alias for the tape library. such as reports. Click Save. To set reports for exporting 1 2 3 4 Log on to the Symantec OpsCenter Server with administrator privileges. the associated cost formula and variables are implicitly copied. the associated cost variables are implicitly copied. Data from exported reports is stored in a default directory. If you copy a cost report. click Settings > Configuration > Report Export Location In the Report Export Location box type the directory where you want to save the reports. See “Adding attributes” on page 234.Understanding OpsCenter settings Setting report export location 233 7 Select reports or cost rates and formulae to be copied to this user profile. 8 Click Copy Setting report export location In OpsCenter you can configure exporting of reports to a predefined location. See “Modifying object types” on page 234. click Settings > Configuration > Object Types. . Click OK. To add an object type 1 2 3 4 5 Logon to the Symantec OpsCenter Server with administrator privileges In the OpsCenter console. See “Deleting object types” on page 234. If you copy a cost formula. You can also add new object types and attributes for those new object types. Click Add. Enter the name in the Add Object Type pop-up screen. if you have not defined any location. See “Deleting attributes” on page 235. In the OpsCenter console. Managing Object Types In OpsCenter you can add or edit attributes of predefined object types. You cannot modify the name of the predefined objects in the drop-down list. In the OpsCenter console. To modify an object type name 1 2 3 Logon to the Symantec OpsCenter Server with administrator privileges. Select the object type from the drop-down list and in Attributes section. Add Deleting object types You can only delete an object type that you have created. To delete object types 1 2 3 4 Logon to the Symantec OpsCenter Server with administrator privileges In the OpsCenter console. You cannot delete predefined object types. click Settings > Configuration > Object Type. To add attributes 1 2 3 4 Logon to the Symantec OpsCenter Server with administrator privileges In the OpsCenter console. Enter the name of the attribute and click OK. You cannot delete the predefined objects in the drop-down list. Select the object type from the drop-down list. 4 5 Click Add. click Settings > Configuration > Object Types. click Add. You can delete the object types that you have created. You cannot rename the predefined object types.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 can rename the object types that you have created. click Settings > Configuration > Object Types. Select the object type that you want to modify from the drop-down list. . Click Delete Adding attributes You can add attributes to all object types. select the check box in front of the attribute you want to delete. Table 4-2 OpsCenter UI functions OpsCenterfunctions Tasks User Management The User Management function includes the following tasks: ■ ■ ■ ■ Create. In the Attributes section. update. NIS. or private domains.Understanding OpsCenter settings Managing users 235 Deleting attributes You can delete attributes that are added to an object type. See “Resetting user password” on page 240. The Symantec Product Authentication Service validates credentials of OpsCenter users based on Windows. To delete attributes 1 2 3 4 Logon to the Symantec OpsCenter Server with administrator privileges In the OpsCenter console. you need to create user accounts. See “About user access rights” on page 235. delete users Create. delete user groups Add. About OpsCenter UI functions Table 4-2 provides details of the OpsCenter UI functions that you can perform. remove roles to users and user groups . Select the object type from the drop-down list. About user access rights This section provides information on OpsCenter users and the functions that they can perform in the OpsCenter GUI. See “ Adding new users” on page 239. click Settings > Configuration > Object Types. See “Adding user groups” on page 242. remove users from user groups Assign. Managing users After you install Symantec OpsCenter. update. Click Delete. Delete Master Server Add.236 Understanding OpsCenter settings Managing users Table 4-2 OpsCenter UI functions (continued) OpsCenterfunctions Tasks OpsCenterManagement The OpsCenter Management function includes the following tasks: ■ ■ ■ Add. folders. 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. Delete OpsCenter Agents Set default currency. Media and Devices. application (Oracle. Update. 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. update Dashboard . Update. delete NetBackup entities: Host Properties. update. and Exchange Server) Views Management The Views Management function includes the following tasks: ■ ■ Create. 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. SQL Server. Freeze. Policy. SNMP. SMTP server NetBackup Configuration Management The NetBackup Configuration Management function includes the following tasks: ■ Add. update. The OpsCenter Security Administrator can create. Policy. delete custom SQL reports Monitoring Monitoring includes the following tasks: ■ View entities ( Dashboards. Operator This user is not involved in activities that are related to managing users. Alerts. Drives. The OpsCenter Administrator cannot create. OpsCenter Server.Understanding OpsCenter settings Managing users 237 Table 4-2 OpsCenter UI functions (continued) OpsCenterfunctions Tasks Custom Reports This function includes the following tasks: ■ ■ Create. Administrator This user can perform all OpsCenter functions except for user management. edit. Note: An Administrator in VBR (Veritas Backup Reporter) or NOM (NetBackup Operations Manager) is a Security Administrator in OpsCenter. Note: A NOM user becomes an Administrator in OpsCenter. delete alert policies Assign. or delete users. Others Alert Management The Alert Management function includes the following tasks: ■ ■ Create. update. update. Media. 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. acknowledge. or delete users. delete custom reports Make custom reports public and/or private Custom SQL Reports This function includes the following tasks: ■ Create. and NetBackup configuration. update. Note: A NOM read-only user becomes an Operator in OpsCenter. Summary. . Details): Job. edit. such as user management or backup & recovery. This user cannot perform functions. 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. Note: A VBR user becomes a Reporter in OpsCenter. Note: A VBR read-only admin becomes an Analyst in OpsCenter. 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 Y Y N N N Y Y N N N Y Y Y N N Y Y Y N N Y Y Y 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 Y Y Y Restricted to only permitted entities .238 Understanding OpsCenter settings Managing users Analyst The role of this user is to mainly analyze the operational and business-level reports. Reporter The role of this user is to mainly generate the operational and business-level reports for further analysis. The Analyst has the Read permission on all views. name. In the Symantec OpsCenter console. which means that the users of this role can perform this particular OpsCenter function. 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. Viewing the list of existing users You can view a list of OpsCenter users and their information such as. access level. . To add a new user to OpsCenter 1 2 3 Log on to the OpsCenter host with administrator privileges. In the OpsCenter console. On the Users tab. authentication domain. click Settings > Users. “N” represents “No”. 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. Click Users to view the list of users. user name. click Settings > Users.Understanding OpsCenter settings Managing users 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 N N Y Y Y Y Y Y Y Y Y Y “Y” represents “Yes”. The user information is arranged in a tabular format. click Add . which means that the users of this role can perform this particular OpsCenter function. and so on. last name. Resetting user password This section describes how to reset a user password. domain name. If you have selected the Existing Domain User option. and User Role See “About OpsCenter user roles” on page 237. . Editing users You can edit the existing users. specify the password. user role. 6 Click Save. and contact details. first name. 6 Click Save. Click Edit. cost center. department.240 Understanding OpsCenter settings Managing users 4 5 Select the user creation type: New User or Existing Domain User. The Reset Password functionality is applicable only for OpsCenter users. You cannot modify the domain of the user. The following user information is mandatory: User Name. If you have selected the New User option. See “Resetting user password” on page 240. Modify the user information. work number. email ID. To edit an existing user 1 2 3 4 5 Logon to the OpsCenter host with administrator privileges. Enter the following general and demographic details of the user: User name. In the OpsCenter console. and enter it once again for confirmation. click Settings > Users. Confirm Password. mobile number. On the Users tab. click the check box in front of the user that you want to edit. You can also reset passwords of the OpsCenter users using this page. Password. you do not have to enter Password and Confirm Password. To delete a OpsCenter user account 1 2 3 4 5 Logon to the OpsCenter host with administrator privileges. In the Symantec OpsCenter console. Edit. On the Reset Password page. click Reset Password. click the check box in front of the user for whom you want to reset the password. click Settings > Users. . Viewing user groups This section provides the procedure to view the existing user groups.Understanding OpsCenter settings Managing users 241 To reset a user password 1 2 3 4 5 6 7 Logon to the OpsCenter host with administrator privileges. enter the new password and confirm password for the selected user. Note: The default OpsCenter user admin cannot be deleted. Click User Groups to view the list of user groups. To view a user group 1 2 3 Logon to the Symantec OpsCenter host with administrator privileges. click Settings > Users. Click Users. Click Delete. In the OpsCenter console. Check the box next to the user account you want to delete. Click Save. On the Users tab. In the General Details pane. Deleting users You can delete the user accounts that do not need to be maintained. In the OpsCenter console. Warning: Do not inadvertently delete all your administrator accounts. click Settings > Users. Add or delete the users using the List of Users pane and Add Users pop-up screen. On the User Groups tab. In the OpsCenter console. click Add to open the Add Users pop-up screen. enter the name of the group and description. Deleting user groups You can delete a user group that you no longer need. Click User Groups . To edit a Symantec OpsCenter user group 1 2 3 4 5 6 7 8 Logon to the OpsCenter Server host with administrator privileges. Select the check box in front of the user group that you want to edit. In the List of Users pane. click Settings > Users. Click Save. click Settings > Users. Click Add. Click OK. On the User Group tab. Editing user groups You can modify an existing 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. . The same access rights on views are attributed to all users in the user group . click Save. select the users that you want to add to this user group. In the OpsCenter console. Modify the user group name or description. Click Edit. Click User Groups. add them to a single user group. On the Add Users pop-up screen.242 Understanding OpsCenter settings Managing users Adding user groups If you want to give the same privileges to multiple users. Managing recipients You can specify the recipients to whom you want to send alert notifications or email reports.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. See “Configuring SMTP server” on page 228. Viewing email recipients This section provides the procedure to view the available email recipients. See “Creating email recipients” on page 245. Click User Groups. Note: Make sure that the mail server is configured to send emails. In the OpsCenter console. Click Delete. See “Creating SNMP trap recipients” on page 247. click Settings > Users. . Select the check box next to the user groups that you want to delete. To view the SNMP trap recipients 1 2 3 Log on to the OpsCenter Server host. Description Description about the email recipient Viewing SNMP trap recipients This section provides the procedure to view the available SNMP trap recipients. Click SNMP. click Settings > Recipients. 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. 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. click Settings >Recipients. when alert policies are configured. Description Description about the trap recipient . the Email tab is selected. All email recipients are displayed on this tab. it is not available for selection on the Adding Email Recipients pop-up screen.244 Understanding OpsCenter settings Managing recipients To view the email recipients 1 2 Logon to the OpsCenter Server host. In the OpsCenterconsole. it is not available for selection on the Adding Trap Recipients pop-up screen. when emails are sent. In the OpsCenterconsole. By default. In the Email tab. . click Settings > Recipients. In the OpsCenter console.Understanding OpsCenter settings Managing recipients 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. click Add to create new email recipients. Enter the maximum number of notifications that you want to receive within the specified Delivery Time Span. Maximum Number of Messages is reset and the Notification Manager starts sending notifications for the specified Delivery Time Span. Select this check box to activate the Alert Notification Delivery Limit settings. Delivery Time Span. Once this time period is over. Alert Manager once again starts sending messages until message count reaches 10. minutes. and Reset Message Count After Time = 2 Hours. Enter the email ID of the official. Once it has sent 10 messages. . Enter a short description about the alert or report so that recipients can understand. If you do not select this check box. or seconds. Maximum Number of Messages. Time during which notifications are blocked if the message count has reached Maximum Number of Messages. 5 Click Save. or seconds. Alert Manager sends messages until message count reaches 10 in 30 Minutes. Enter the time duration in hours. Delivery Time Span = 30 Minutes. and Reset Message Count After Time are not taken into account when notifications are send. it blocks the delivery of new messages for next two Hours. during which notifications are sent. minutes. Email Address Active Description Activate Delivery Limit Maximum Number of Messages Delivery Time Span Reset Message Count After Enter the time period in hours. Once the message count reaches Maximum Number of Messages. Note: For example. After two hours. if Maximum Number of Messages = 10. 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. Select this check box if you want the recipient to receive alert notifications and reports by emails. to which alert notifications or reports are sent.246 Understanding OpsCenter settings Managing recipients 4 Enter the following information: Email Recipient Name Enter the name of the official whom you want to notify about an alert or send reports. For more details. To create SNMP recipients 1 2 3 4 5 Log on to the OpsCenter Server host with administrator privileges. For example. A trap recipient is a host that receives notifications in the form of SNMP traps when an alert condition is met. Click SNMP. click Settings > Recipients.Understanding OpsCenter settings Managing recipients 247 Creating SNMP trap recipients Traps. Click Add In the SNMP Attributes page enter the following information: . are signals sent to inform the programs that an event has occurred. In the OpsCenter console. refer to the About using SNMP with OpsCenter section. In OpsCenter. traps are the notifications that are sent to a specified SNMP host or group of hosts when a condition is met. (interrupts). a trap is sent after an alert was generated as a result of failure of communication between the OpsCenter Agent and Server. Reset Message Count After Time 7 Click Save. See “Creating SNMP trap recipients” on page 247. Maximum Number of Messages is reset and Alert Manager starts sending notifications for the specified Delivery Time Span. . Maximum Number of Messages Delivery Time Span Enter a maximum number of notifications that can be sent within the specified Delivery Time Span. Once the message count reaches Maximum Number of Messages. to which you want to send traps. The notifications are sent as soon as alerts are generated. and Reset Message Count After Time are not taken into account when notifications are send. Enter an SNMP host. Enter the time duration in hours. minutes. or seconds. during which notifications are blocked if the message count has reached Maximum Number of Messages. 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. See “Creating email recipients” on page 245. Once this time period is over. during which notifications are sent. Enter a short description about the traps. or seconds. Enter the port number on the SNMP host where you want to send traps.248 Understanding OpsCenter settings Managing recipients 6 Recipient Name SNMP Host SNMP Port Enter the name of the SNMP trap recipient. Enter the time period in hours. Modifying Email or SNMP recipient information Only OpsCenter administrator can modify email / trap recipient information. minutes. Delivery Time Span. Maximum Number of Messages. Select this check box if you want the recipient to receive notifications by SNMP traps. 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. click Settings > Recipients. Managing cost analysis and chargeback for OpsCenter Analytics This feature is accessible only to Symantec OpsCenter Analytics users. one of which can be set as default currency. You cannot access the Settings > Chargeback feature if you do not have Symantec OpsCenter Analytics. You can set the cost variable. This feature is disabled for unlicensed OpsCenter version. To delete Email or SNMP trap recipient 1 2 3 4 In the OpsCenter console. select email / trap recipient from the table. select email / trap recipient from the table. change email / trap recipient attributes and Alert Notification Delivery Limit Settings. In the Email Recipients tab or SNMP Recipients tab. 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. Click Save. that you want to delete. See “Creating email recipients” on page 245. If you have OpsCenter administrator privilege. . ClickDelete. Click Save.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. In the Email Recipients tab or SNMP Recipients tab. Deleting Email or SNMP recipient Only OpsCenter administrator can delete email or trap recipient. and cost estimation that you want to run the cost reports. cost formulae. On the modify email / trap recipient page. In OpsCenter Analytics. you can choose the currency that you want to be displayed on cost reports. click Settings > Recipients. you can set multiple global currencies. that you want to edit. 3 On the Currency Settings tab. If you have not entered the Symantec OpsCenter Analytics license key. See “Editing currency list” on page 250. which appears on chargeback reports. In the console. click Settings > Chargeback. This feature is disabled for unlicensed OpsCenter version. To edit currency list 1 2 Log on to the OpsCenter Server with administrator privileges. For example. However. Select a currency from the drop-down list. Select the Display Currency Option in Cost Reports check box to show the default currency on the cost reports. click Settings > Chargeback. for US dollar currency. 4 Select the Currency Display Mode: Currency Code or Currency Symbol. OpsCenter does not support conversion of currencies.250 Understanding OpsCenter settings Managing cost analysis and chargeback for OpsCenter Analytics Note: Setting the default currency gives you the flexibility of displaying cost report values in the currency of your choice. . This feature is disabled for unlicensed OpsCenter version. 5 6 Editing currency list This section provides the procedure to edit the global currency list. You cannot access the Settings > Chargeback feature if you do not have Symantec OpsCenter Analytics. 3 On the Currency Settings tab. you cannot access the Settings > Chargeback feature. in the Default Currency drop-down list. Click Save. you can either select a currency code USD or symbol $. click Edit Currency List. In the console. all global currencies that are set by the administrator are available for selection. which is made available when a default currency is selected to be displayed on OpsCenter cost reports. To set the default currency 1 2 Logon to the OpsCenter Server with administrator privileges. which you want to make available for selection in the Default Currency drop-down list on the Currency Settings tab. 5 Click Add to add the selected currencies to the User Currency list. select currencies from the Global Currency list.00 per backup job. Remove. Managing Cost Variables You can create cost variables based on various parameters to determine cost of various services. In the console. For example. See “Modifying cost variables” on page 253. you must create a cost variable with the Protected Job Size (GB) metric. 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. You can use Add. you need to create the variables that define the cost of various services. See “Setting a default currency for cost reports” on page 249. Click Cost Variable. Add All. for example $1. . See “Deleting cost variables” on page 253. 6 Click OK.25 per backup job starting on 1 January 2005. To set up OpsCenter to run cost reports. each service is represented by one variable that reflects the cost of the service. However. click Settings > Chargeback. Note: To generate deduplication savings reports. See “Creating cost variables” on page 251. To create a cost variable 1 2 Log on to the OpsCenter Server with administrator privileges.00 per backup job until 31 December 2004 and the rate of $1. a single variable can incorporate the rate of $1. Typically. Creating cost variables Cost reports in OpsCenter Analytics are based on the user-defined variables that define the cost of various services. and Remove All options to alter the User Currency list.Understanding OpsCenter settings Managing cost analysis and chargeback for OpsCenter Analytics 251 4 On the Edit Currency List pop-up screen. Add at least one date range.252 Understanding OpsCenter settings Managing cost analysis and chargeback for OpsCenter Analytics 3 4 5 On the Cost Variable tab. Job Storage Type Measure cost for a specific storage type for example. and MS-Exchange-Server. Measure costs for the jobs that use a specific policy type. Job Type Measure costs for a specific type of job. which enables you to select disk as a storage type. Job Size. Select any of the following variable metrics from the drop-down list: ■ ■ ■ ■ Daily Occupancy Job Count Job Size Protected Job Size 6 If necessary. click Add. for example Backup or Restore. For Job Count. Sybase. and Time and by typing a cost per service unit (such as backup jobs or backed-up GB) in the Rate field. . the types of backups that can be performed on the clients. the policy type determines the type of clients that can be part of the policy and. The default option is All. 7 Add one or more date ranges and associated rates using the drop-down lists for Month. Day. in some cases. The default option is All. select additional parameters to refine the metric you selected. LAN (Local Area Network) or SAN (Storage Area Network). The default policy type is All. The default option is All. Year. when a cost variable is created. tape or disk. Examples include DB2. Job Policy Type Job Transport Type Measure cost for a specific transport type for example. In NetBackup. OpsCenter supports NetBackup's disk-based data protection feature. Enter the variable name. and Protected Job Size select the following: The following fields are not applicable for the Daily Occupancy variable metric. ClickDelete. You can now use the variable you created to build the formulas that form the basis for cost reports. Select the check box in front of the cost variable that you want to delete. and you must update any formulas that use the variable. You can also modify the variable later to add or delete date ranges as costs change. date ranges and rates of a variable to reflect changing conditions in your enterprise. This can be useful for defining multiple date ranges to represent historical or future changes in service costs. Click Cost Variables. Deleting a cost variable removes it permanently from the database. To restore a deleted variable. click Settings > Chargeback. click Settings > Chargeback. For example. To delete a cost variable 1 2 3 4 5 Log on to the OpsCenter Server with administrator privileges. click Add New Range. you must recreate the variable manually. Click Edit. To modify a cost variable 1 2 Logon to the OpsCenter Server with administrator privileges. Modifying cost variables You can update cost variables and formulas without having to recreate the reports that rely on them. 3 4 5 6 Select the check box in front of the variable name that you want to modify. Deleting cost variables You can variables you no longer need. See “Creating cost formulae” on page 254. In the console. .Understanding OpsCenter settings Managing cost analysis and chargeback for OpsCenter Analytics 253 8 Optionally. 9 Click OK . Modify the cost variable details. Click Cost Variables. Click OK. In the console. you can modify the name. to add more date ranges. You need to select at least one cost variable. See “Deleting a cost formulae” on page 255. For example. Select a cost variable from the drop-down list. . In the console. See “Modifying cost formulae” on page 254. You can also modify the formulae later to add or delete variables. click Add new cost variable. Enter the name of the formula. 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. to define formulae containing more than one variable. 7 Click OK. create the formula that define the cost of various services to run cost reports. Creating cost formulae After you create cost variables.254 Understanding OpsCenter settings Managing cost analysis and chargeback for OpsCenter Analytics Managing cost formulae Based on cost variables you can create the cost formulas that you can use to generate cost reports. 3 4 5 On the Cost Formulae tab. See “Creating cost formulae” on page 254. click Add. You can update chargeback formulas without having to recreate the reports that rely on them. 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. Select a different variable from the nes drop-down list. To create a cost formula 1 2 Logon to the OpsCenter Server with administrator privileges. 6 Optionally. Modifying cost formulae You can modify the name and variables of a cost formula that you have created. click Settings > Chargeback. Click Cost Formulae. click Settings > Chargeback. On the confirmation dialog box. To delete cost formulae 1 2 Logon to the OpsCenter Server with administrator privileges. 3 4 5 On the Cost Formulae tab. . 3 4 5 6 On the Cost Formulae tab. Deleting a cost formulae You can also delete formulae that you no longer need. click Settings > Chargeback. Click Cost Formulae. select the cost formulae that you want to delete. Click Delete. For example.000 over the next year to provide backup services throughout your enterprise. By inserting the metric Daily Occupancy into the tool. Managing cost estimation The Formula Modeling Tool offers an easy way to estimate baseline rates for the IT services you provide.Understanding OpsCenter settings Managing cost analysis and chargeback for OpsCenter Analytics 255 To modify a cost formulae 1 2 Logon to the OpsCenter Server with administrator privileges. Modify the details of the cost formula. Using historical data. Click Cost Formulae. See “Creating cost formulae” on page 254. Click Edit. Deleting a cost formula removes it permanently from the database. In the console. See “Creating cost variables” on page 251. Click OK. In the console. click OK. you can obtain an estimate per kilobyte that is based on the backup activity you performed last year. select the cost formulae that you want to modify. suppose you anticipate spending $500. along with the amount $500000. it provides you with an estimate of how much it costs your organization to provide a specific kind of service. or category of service. Examples: $50000. or $10000. Click Cost Estimation. click Settings > Chargeback. In the console. Example: Daily Occupancy Amount Specify the total amount of money. you expect to charge for service within that category in a given time frame. $10000. 3 4 Select a Report Grouping parameter to define the model’s scope: Use the following Metric Selection parameters to specify the metric whose rate you want to estimate: Metric Select a metric.256 Understanding OpsCenter settings Managing cost analysis and chargeback for OpsCenter Analytics To estimate baseline (chargeback) costs using the Formula Modeling Tool 1 2 Logon to the OpsCenter Server with administrator privileges. in dollars.00 5 Use the following Time Frame parameters to define the time intervals for which data is modeled: . 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.M. You can choose either absolute dates.M. meaning that the estimate’s contents remains static whenever you display it. ■ 6 Click Run Model to input different values into the model. The estimate reflects the data that is collected within the specified time period. Select one of the following: Click Absolute to configure an absolute time frame.M. meaning that the estimate always reflects data that is collected over the most recent time interval. up to the current time. . ■ Click Relative to configure a relative time frame. or relative dates. and a stop time using the To drop-down lists. day. Then select a time interval using the Last drop-down lists. year. Example: From MAR 1 2004 12:00 A. The estimate reflects data from the time period between the start and the end dates. or to run a new model.Understanding OpsCenter settings Managing cost analysis and chargeback for OpsCenter Analytics 257 Time Frame Defines the beginning and end of the time interval the estimate must cover. to APR 30 2004 12:00 A. Then select a start time (month. Example: Unbounded to APR 30 2004 12:00 A. and time of day) using the From drop-down lists. Such estimates always reflect the data that is collected over the most recent time interval. 258 Understanding OpsCenter settings Managing cost analysis and chargeback for OpsCenter Analytics . Chapter 5 Understanding data collection This chapter includes the following topics: ■ ■ ■ ■ ■ ■ ■ ■ ■ 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. Note: Only one OpsCenter Agent can be installed on a single host. An OpsCenter Agent comprises product-specific data collectors that collect data from point products and return it to the OpsCenter Server. . you can do advanced reporting from the data that is collected from all of these products. . you need to install the OpsCenter Agent on a Windows host. you cannot collect data from third-party products like IBM Tivoli Storage Manager (TSM) and EMC Legato NetWorker. Table 5-1 lists the backup and archiving products that OpsCenter supports. IBM Tivoli Storage Manager (TSM) EMC Legato Networker ■ ■ ■ ■ See “Configuring data collection for NetBackup” on page 270. Symantec NetBackup PureDisk Symantec Enterprise Vault (Windows only) Note: To collect archive data from Enterprise Vault. 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. you need to install the OpsCenter Agent on a Windows host. The release notes for your release of OpsCenter also include any restrictions or limits for OpsCenter.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. With the unlicensed version. 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. 2008 (SP2 & R2) Symantec Enterprise Vault 7. .2. 11d. 8. 6.0 MP7 and higher versions.0) by remote agent Note: NBU 7.5 All supported TSM platforms by remote agent Native agent for backup server on Windows 2003 (SP2 & R2).3 Native agent on backup servers on Windows 2003 (SP2 & R2).5 All supported Symantec Backup Note: OpsCenter does not Exec platforms by remote agent. 6. 6. 7. 12.6 PureDisk supported platform (PDOS) by remote agent 10d.2. support Symantec Backup Native agent on backup servers on Exec running on NetWare. 2008 (SP2 & R2).5 and higher versions.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).0 Backup or Archiving product Symantec NetBackup Support level All supported NetBackup platforms (except 7.3. 12.5.4. and Solaris 9. 2008 (SP2 & R2) and Solaris 9/10 Data collection is possible only with a licensed version of OpsCenter. IBM Tivoli Storage Manager (TSM) 5. 2008 (SP2 & R2) and Solaris 9/10 Data collection is possible only with a licensed version of OpsCenter.5. 6. 10 Symantec NetBackup PureDisk Symantec Backup Exec 6. EMC Legato NetWorker 7. Windows 2003 (SP2 & R2).1. 5. 6.0.0 does not require any Agent.Understanding data collection About data collection in OpsCenter 261 Table 5-1 Backup and archiving products supported by Symantec OpsCenter Versions 6. Windows 2008 (SP2 & R2). Native agent for Windows 2003 (SP2 & R2).5.2. 5. log About Data Collectors The OpsCenter data collectors.262 Understanding data collection About data collection in OpsCenter About OpsCenter Agents The OpsCenter Agent collects data from various Symantec and third-party backup and archiving products. You can collect PureDisk data only through the OpsCenter Integrated Agent. refer to the Installing Symantec OpsCenter chapter. These products can reside on the OpsCenter Agent host or on remote hosts. Enterprise Vault. To collect PureDisk data. which you can use to collect only PureDisk data. These data collectors collect the specified data type as specified in the configuration. such as Backup Exec. collect data from backup and archiving product hosts. or EMC Networker. You can configure multiple data collectors on a single OpsCenter Agent host. You cannot delete the Integrated Agent. You can create data collectors to communicate with the various products. Policy and Schedule. Media. 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. Note: When you install the OpsCenter Server. For example. you do not need to manually install or configure OpsCenter Agent. By default the InstallPath is: C:\Program Files Naming convention for the OpsCenter Agent log file: 5*-146-*. . Job. Backup Exec data collector can collect Tape Drive Usage. Each data collector collects data from a single product host.log An example of the OpsCenter Agent log file name: 58330-146-2567491850-091129-0000000000.OpsCenter Integrated Agent is also installed and configured. For more details on OpsCenter Agent installation and deployment scenarios. You can specify to collect all or some of the data types for that product. or Image. Understanding data collection About data collection in OpsCenter 263 Note: Error logs and skipped files are collected as part of job data. Table 5-3 Backup product Symantec Backup Exec Data types collected Data type collected by OpsCenter Tape Drive Information. See “Collecting data from IBM Tivoli Storage Manager” on page 303. Collector (Windows only) See “Collecting data from Backup Exec” on page 287. Create this data collector to collect data from TSM. 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. NetBackup PureDisk Data Collector Create this data collector to collect data from NetBackup PureDisk. To collect PureDisk data. Table 5-2 lists the data collectors that you can configure in OpsCenter. Legato Networker Data Collector Create this data collector to collect data from Legato Networker. Job Symantec NetBackup PureDisk . Media. See “Collecting data from EMC Legato Networker” on page 305. Job Policy and Schedule. you need to create a data collector for the Integrated Agent. Table 5-3 lists data types that are collected by OpsCenter data collectors from various products. You can enable or disable a data collector. Table 5-2 Data collector types Description Data Collector type Symantec Backup Exec Data Create this data collector to collect data from Backup Exec. See “Collecting data from PureDisk” on page 288. Policy and Schedule. Note: You can collect the PureDisk data only through the OpsCenter Integrated Agent that is installed with the OpsCenter server. Viewing Agent status Use this section to view general details and status of an OpsCenter Agent that you have configured in OpsCenter. Target. Policy and Schedule. Job Symantec Enterprise Vault IBM Tivoli Storage Manager EMC Legato Networker Managing OpsCenter Agents This section provides procedures to view. See “About the OpsCenter Agent” on page 29. select an Agent to view its status at the bottom of the page. Job Tape Drive Information. click Settings > Configuration > Agent. On the Agent list. Archive Tape Drive Information. modify. See “Configuring an OpsCenter Agent” on page 265. Media. To view Agent status 1 2 In the OpsCenter console. create. Media. which you have specified when you created this Agent. Policy and Schedule. Agent Summary by Data Type Status. 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 3 Click Agent Summary by Data Collector Status. . or Agent Summary by Data Collector Count tab to view the relevant details.264 Understanding data collection Managing OpsCenter Agents Table 5-3 Backup product Data types collected (continued) Data type collected by OpsCenter Archive Policy. By default the General tab is selected that displays the following details. Vault Store. and delete an OpsCenter Agent configuration. 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. From the list of agents. Click Save. Deleting Agents This section provides the procedure to delete an OpsCenter Agent. To modify an OpsCenter Agent 1 2 3 4 5 In the OpsCenter console. using which you want to connect to the OpsCenter Server Agent Operating System Family PBX Port OpsCenter Server Network Address 3 Click Save. click Settings > Configuration > Agent. On the Edit Agent page. Click Create Agent.Understanding data collection Managing OpsCenter Agents 265 Configuring an OpsCenter Agent This section provides the procedure to configure an OpsCenter Agent. modify PBX port or OpsCenter Server Network Address. click Settings > Configuration > Agent. Modifying an Agent This section provides the procedure to modify an OpsCenter Agent information. . Click Edit Agent. To configure an OpsCenter Agent 1 2 In the OpsCenter console. select the check box in front of the Agent that you want to modify. 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. modify. configure.266 Understanding data collection Managing Data Collectors To delete an OpsCenter Agent 1 2 3 In the OpsCenter console. From the list of agents. select the check box in front of the Agent that you want to delete. expand an Agent to view the Data Collectors that are configured for this Agent. click Settings > Configuration > Agent. click Settings > Configuration > Agent. To view data collector status 1 2 In the OpsCenter console. Click Delete. and delete a data collector. Managing Data Collectors This section provides procedures to view. On the Agent list. Viewing Data Collector status Use this section to view general details and status of a Data Collector that you have configured for an Agent. . By default the General tab is selected displaying the following Data Collector details. The OpsCenter Agent contains product-specific data . Failed. for which this Data Collector is configured For example: Symantec Backup Exec Product Host Status Displays the name of the target host. which you have specified when you created this Data Collector. See “ Configuring a Data Collector” on page 267. the data is not collected from the target host. 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. Agent. Product Displays the name of the product type. The collection status of the data collector for each data type. 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. and a console. OpsCenter consists of Server. Java View Builder. 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. such as Complete.Understanding data collection Managing Data Collectors 267 3 Select a Data Collector to view its details and status at the bottom of the page. 4 Select the Data Collection Status tab. For example. On the Create Data Collector: Product Selection page. Configuration Settings. Symantec Backup Exec. for which you want to configure a Data Collector. enter the following information: Select Product Select the name of the product from which you want to collect data. You need to specify the product name when you create the data collector. configure the data collectors. By default. Target host name Data Collector Status . You can disable the data collection by changing the status. 6 Verify or modify the default Target Details: Product Displays the name of the product from which this data collector collects data. For example: Symantec Backup Exec Displays the name of the product host from which this data collector collects data. Target host name Enter the name of the product host from which you want to collect backup or archiving data. See “Configuring an OpsCenter Agent” on page 265. Click Create Data Collector. 5 Click Next. You can generate various business reports on this backup / archiving data. On the Create Data Collector: Details page. After you install and configure an OpsCenter Agent. On the Agent list. To configure a data collector 1 2 3 4 In the OpsCenter console. and Data Collection details are displayed. You need to specify the product name when you create the data collector. the data collector status is Enabled. click Settings > Configuration > Agent.268 Understanding data collection Managing Data Collectors collectors collecting data from the products and returning it to the OpsCenter Server. 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. the Target Details. select a check box in front of the Agent. and days. See “Collecting data from Enterprise Vault” on page 292. 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. . refer to the respective data collector settings. The next data collection starts at 11:15 A. See “Collecting data from EMC Legato Networker” on page 305. For product specific configuration settings. Lists the data types that can be collected from a product host. See “Viewing Agent status” on page 264. hours. 8 Enter the following data collector settings: Blackout Period Start Time Select the start time of a blackout period. See “Collecting data from Backup Exec” on page 287. These settings vary depending on the data collector type you configure. Select this check box to collect the associated data type. See “Collecting data from IBM Tivoli Storage Manager” on page 303. Modifying a Data Collector configuration This section provides procedure to modify configuration of a Data Collector. The first data collection starts at say 9:00 A. Collection Interval (sec) Enter the collection interval in minutes. The data is not collected during the time that is specified in Blackout Period Start Time and Blackout Period End Time. Blackout Period End Time Configuration Status Collectible Data Type 9 Click Save.M.Understanding data collection Managing Data Collectors 269 7 Enter the data collector configuration settings. Last Successful Data Load States whether last data load was successful or not. The data types vary depending on the product that you are collect data from. till all archive records are collected and ends at 11:00 A.M. See “About Data Collectors” on page 262. after 15-minutes interval . Collection interval is the time interval that you want to set between the two consecutive data collections.M. For example: You have set the Collection Interval to 15 Minutes. In the OpsCenter console. expand an Agent to view Data Collectors that are configured for this Agent. 10 Click Save. Click Edit Data Collector. Deleting Data Collectors This section provides procedure for deleting Data Collector configurations from an Agent. delete. About the NetBackup data collection view This view is displayed when you select Settings > Configuration > NetBackup from the OpsCenter console. To delete a Data Collector configuration 1 2 3 4 5 Log on to the OpsCenter Server. and control data collection for a master server. Modify data collection configuration settings.. click Settings > Configuration > Agent. Modify collection interval. . It also describes how you can add. edit. modify the Target Details. On the Agent list. Select check boxes in front of the Data Collectors that you want to delete. expand an Agent to view Data Collectors that are configured for this Agent. These settings vary depending on the product. On the Edit Data Collector: Details page.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 console. On the Agent list. Click Delete Data Collector. Modify blackout period settings. This view shows details of master servers. Configuring data collection for NetBackup This section describes how OpsCenter collects data from NetBackup. Select a check box in front of the Data Collector that you want to modify. click Settings > Configuration > Agent. which this data collector collects data from. NetBackup Service Layer (NBSL) components are included as a part of NetBackup on master and media servers. The Last Contact column does not necessarily represent the last time that OpsCenter collected information from the master server. Note: OpsCenter only uses the NBSL on master servers for data collection. manage. clients. Though NBSL is also included on media servers. To perform the monitoring. Backup product and version from where the data is collected.0 release of NetBackup. and policies. The NetBackup data collection and management logic that OpsCenter uses is built into NetBackup master servers. How OpsCenter collects data from NetBackup OpsCenter is used to monitor. and reporting functions. and report on NetBackup master and media servers. The last time that OpsCenter successfully initiated contact with the particular master server. You must not add any media servers to the OpsCenter console. . OpsCenter collects data from the NetBackup master servers. OpsCenter does not use it. This logic is included in the NetBackup Service Layer (NBSL). Starting with the 6.Understanding data collection Configuring data collection for NetBackup 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. 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. Operating system of the master server. You must add only master servers to the OpsCenter console. management. and change events. OpsCenter gets affected. See the NetBackup Administrator’s Guide. an OpsCenter Agent must be installed if you want to collect specific data like image.) from the NetBackup master server and insert it into the OpsCenter database. and scheduled jobs.0 master servers. it may take some time for the OpsCenter server to collect all data (such as media. . OpsCenter uses NBSL for all NetBackup monitoring. managing.272 Understanding data collection Configuring data collection for NetBackup NBSL provides a single point of access to key NetBackup data. OpsCenter may not capture any changes that were made to the NetBackup configuration. If NBSL service stops running on a managed NetBackup server. However. OpsCenter correctly recaptures the latest state. error log. or when the data collection for a master server is enabled after a long time. error log. If NBSL stops. For NetBackup 7. jobs. As soon as the initial data load is complete. OpsCenter Agents do not need to be installed on the NetBackup 7. In earlier master server versions. when data collection for a master server is enabled or when a master server is added to OpsCenter. images. NBSL runs as a service or daemon and has local configuration information.0. The initial data load happens serially for each data type. the OpsCenter server starts collecting all the available data from NetBackup master server into the OpsCenter database using NBSL. and scheduled jobs from a master server whose version is less than 7. the VBR agents collected the data for image. OpsCenter server software listens to the notifications from NBSL for any change in NetBackup data. and updates the OpsCenter database. but no local database. In this case. When NBSL restarts. objects. drives etc. See “About the data collection status of a master server” on page 274. Note: A NetBackup 7. Volume II for more information about NBSL. Note: Consider a scenario when you add a master server or when OpsCenter server software starts after a long time. The OpsCenter server software collects data from NBSL in the following ways: ■ ■ Initial data load Listening for change notifications Whenever OpsCenter server software starts.0 master servers. and control functions. The NetBackup UI also uses NBSL. this data is collected automatically by the OpsCenter Server.0 master server does not require any OpsCenter Agent or data collector for data collection. Viewing master server details and data collection status Use the following procedure to view the details for a master server. About NetBackup versions that OpsCenter can monitor and manage OpsCenter can monitor and manage all NetBackup versions between 6. 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.0 release of NetBackup. The NetBackup master servers that OpsCenter manages are referred to as managed NetBackup servers. See “Adding a master server in the OpsCenter console” on page 282. Once you add the master server in the OpsCenter console. To begin data collection from the master server. the OpsCenter server can start collecting data from the master server. In this case.0 MP7 and 7. 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. The details for the master server are shown at the bottom of the Settings > Configuration > NetBackup view under the following tabs: . 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. Starting with the 6. Also review the OpsCenter sections of the NetBackup release notes before using OpsCenter for monitoring NetBackup clusters. OpsCenter can also be used to monitor a NetBackup cluster. you must delete the master server from the OpsCenter console and then add the master server again. and you uninstall and then reinstall NetBackup on the master server. 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. See NetBackup High Availability Administrator's Guide for more details on setting up a NetBackup cluster environment.0. Each managed NetBackup master server that OpsCenter manages must have NBSL present and in operation. See “About the OpsCenter database” on page 28.Understanding data collection Configuring data collection for NetBackup 273 Consider a scenario where a master server is already added on the OpsCenter console. when data collection last happened. and the exception message if the data collection failed for any of the data types. 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. The Data Collection Status tab is shown by default when you select Settings > Configuration > NetBackup. Figure 5-1 shows a sample data collection status view for a master server. select Settings > Configurations > NetBackup. See “About the data collection status of a master server” on page 274. This tab displays the collection status for each of the data types. Data Collection Status To view the details and the data collection status for a master server 1 2 In the OpsCenter console. Click the name of the master server (link) from the Network Name column. Figure 5-1 Sample Data Collection Status view . The details for the master server are shown at the bottom of this view. It also lists details like the time when the data load was last successful.274 Understanding data collection Configuring data collection for NetBackup General This tab displays the contents of many of the columns that are displayed in the table. ) by using NBSL. services. and devices. This data is stored in the OpsCenter database. This column lists the last exception message if data collection failed for a data type. For changes such as job. Table 5-4 Column Data Type Data Collection Status view Description The type of data that is collected from NetBackup.Understanding data collection Configuring data collection for NetBackup 275 Table 5-4 gives a description of the contents in the Data Collection Status tab. Collection Status Last Exception Message About NetBackup data types and collection status OpsCenter collects data for many NetBackup data types (such as jobs. policy. This column lists the date and time when data collection was attempted. the notification also contains the changed data. 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. storage unit etc. This column provides the status of each data load activity that OpsCenter requests. policy. The following are the collection status for the different data types and their description: . For most operations and changes in NetBackup. media server. service. See “About NetBackup data types and collection status” on page 275. NBSL sends notifications to OpsCenter. 0 does not support disk. Not Started The data collection for the specific data type has not started. FT data types. NetBackup 6. This may happen when you initially add a master server or when you start the OpsCenter server. See “Adding a master server in the OpsCenter console” on page 282.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. For example.276 Understanding data collection Configuring data collection for NetBackup Not Applicable This status may come when the master server version does not support the specific data type. The data collection for the specific data type is queued. This status also comes when your master server version is lower than 7. See “Editing a master server” on page 286. Queued Running Completed . The data collection for the specific data type is in progress. The data collection for the specific data type is complete. If data collection for a particular data type fails. This is because data collection can fail.Understanding data collection Configuring data collection for NetBackup 277 Failed The data collection for the specific data type has 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. Note: Data collection can fail. This is normal behavior. If data collection for a particular data type fails. 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. fails. Not Licensed This status is seen when the specific data type like FT is not licensed in NetBackup. it should be automatically started again within 10 minutes. and then start after some time. device. Partially Connected . For example. disk etc. and then start after some time. This is normal behavior. When the data collection fails. it should be automatically started again within 10 minutes. you can see the exception message from the Last Exception Message column. data collection for catalog data type is Completed but data collection for client. All the functionality other than the functionality of the failed data type can be used normally while collection for a data type fails. All the functionality other than the functionality of the failed data type can be used normally while collection for a data type fails. Master servers may show as Partially Connected temporarily for some time. . All the functionality other than the functionality of the failed data type can be used normally while collection for a data type fails. it should be automatically started again within 10 minutes. Note: A single OpsCenter Server should monitor only one NetBackup Master Server. OpsCenter can monitor the master servers which have NetBackup Access Control (NBAC) configured and also those servers that do not have NBAC configured. After configuring the master server. Disabled The master server is Disabled when the data collection for the selected master server is disabled. This may be when there is a network issue because of which OpsCenter is not able to connect and collect data from NetBackup. See “Configuring a master server for server access and data collection by OpsCenter” on page 280. Adding a master server To allow OpsCenter to communicate with a managed NetBackup server and collect data requires some security configuration. Use the following steps to add a master server. If data collection for a particular data type fails. you must add the master server to the OpsCenter console so that it can be monitored. To add a master server 1 Configure your managed master server to allow server access and data collection by OpsCenter. Note that you must first configure the master server to allow server access and data collection by OpsCenter. This is normal behavior. Note: Data collection can fail.278 Understanding data collection Configuring data collection for NetBackup Not Connected The master server is Not Connected when the data collection for all data types fails. and then start after some time. you must add this server to the OpsCenter console so that it can be monitored. See “Adding a master server in the OpsCenter console” on page 282. 2 After configuring the master server. This command also establishes a trust relationship from the authentication broker of NetBackup master server to the authentication broker of OpsCenter Server. In case of a clustered NetBackup setup. To add a NetBackup 7.0 master server Use the following procedure to add a NetBackup 7. .conf file.0.0 master server to the OpsCenter console. In addition. a new entry that is called OPS_CENTER_SERVER_NAME has been added to the bp. This procedure can be used for both NBAC and non-NBAC servers. This procedure can be used for both NBAC and non-NBAC servers. use this procedure for each node of the cluster.0 master server” on page 279.Understanding data collection Configuring data collection for NetBackup 279 Note: You can use an alternate procedure to add a NetBackup 7. The nbregopsc command registers OpsCenter with the current master server and adds this master server to OpsCenter.0 master server to OpsCenter. a command that is called nbregopsc has been added to NetBackup 7. Adding 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 3 Run the following command on the master server: nbregopsc -add <Name of the OpsCenter Server> As a part of usability enhancements. See “Adding a NetBackup 7. Once you perform this procedure. This procedure applies to both NBAC and non-NBAC master servers. the master server is automatically added to the OpsCenter console. 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. a trust relationship must be established from the authentication broker of the OpsCenter server to the authentication broker(AB) of the NetBackup master server. . Note: In case running the nbregopsc command fails. See “Adding a master server in the OpsCenter console” on page 282. In case of a clustered NetBackup setup. However if the master server is NBAC-enabled. use this procedure on each node of the cluster. run the following command: vssat setuptrust --broker <MasterServerhost:2821> --securitylevel high Note that <MasterServerhost> is the name of the master server. 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.280 Understanding data collection Configuring data collection for NetBackup 4 Ignore this step for master servers for which NBAC is not configured. 5 Restart all the NetBackup services (processes). OpsCenter cannot monitor NetBackup servers if the trust relationship has not been set up between OpsCenter and NetBackup server. To establish the trust relationship. you must manually add the master server to the OpsCenter console. Double-click the master server name to view its properties. . Ensure that the OpsCenter server name that you add is reachable from the NetBackup server. Expand NetBackup Management > Host Properties > Master Servers.0. 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. it is recommended that the following procedure be used for NetBackup 7.Understanding data collection Configuring data collection for NetBackup 281 Note: This procedure applies to all master server versions including 7. However.0 servers. From the Master Server Properties dialog box. click Add. See “Adding a master server in the OpsCenter console” on page 282. 8 9 Click Close. The Master Server Properties dialog box appears. To add the OpsCenter server to the server list. click OK. The Add a New Server Entry dialog box appears. In the Master Server Properties dialog box. Type the OpsCenter server name in the field and click Add to add the server to the list. select the Servers tab to display the server list. Start the NetBackup Administration Console. To set up these trust relationships. 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). use the vssat command in Symantec Product Authentication Service. See “Adding a master server in the OpsCenter console” on page 282. 11 Restart all the NetBackup services. 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. select Settings > Configurations > NetBackup . run the following command: vssat setuptrust --broker <OpsCenterABhost:2821> --securitylevel high where <OpsCenterABhost> is same as the host where OpsCenter server is installed. . Use the following procedure to add a master server. Similarly. Click Add. Adding a master server in the OpsCenter console You must add a master server to the OpsCenter console so that it can be monitored. then <OpscenterAB> is the host name that is provided as the remote authentication broker host during the OpsCenter installation. However if OpsCenter is installed in a clustered mode. To add a master server 1 2 In the OpsCenter console. On the NetBackup master server host. 12 Add this master server to the OpsCenter console so that it can be monitored. Run this command from %Program Files%\Veritas\Security\Authentication\bin directory in Windows or /opt/VRTSat/bin in UNIX. However if the master server is NBAC-enabled.282 Understanding data collection Configuring data collection for NetBackup 10 Ignore this step for master servers on which NBAC is not configured. 0 master servers. and scheduled jobs is used in OpsCenter reports. this data is collected automatically by NBSL and OpsCenter Agents do not need to be installed on the master servers. Enter the following details under Advanced Data Collection Properties section: . error log. enter the virtual name of the master server. The display name is used for the master server on all views of the OpsCenter console.Understanding data collection Configuring data collection for NetBackup 283 3 Enter the following detailsforthemasterserverunderGeneralPropertiesandAdvancedPropertiessections: Network Name Enter a host name or an IP address. The data for image. NetBackup PBX port The NetBackup PBX port allows all socket communication to take place while connecting through a single port. The Advanced Data Collection Properties section is applicable if your NetBackup master server version is lower than 7. Display Name Enter an alternate name for the server. Note that this field is required. OpsCenter uses the address that you select to connect to the master server. For NetBackup 7. In earlier master server versions. OpsCenter's Preferred network address The OpsCenter server may have multiple network interface cards (NIC). This field is required.0. You can select a preferred network address from the drop-down list. error log. the VBR agents collected the data for image. Note that this field is required. In case the master server is clustered. The default NetBackup PBX port is 1556. and scheduled jobs. In case of remote data collection. no agent is configured. 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. Enable Error Log data Collection . Click the checkbox if you want to enable error log data collection from the master server.284 Understanding data collection Configuring data collection for NetBackup Agent Select an agent from the drop-down list. Install Directory The directory path on the OpsCenter Agent host where the NetBackup application is installed. In case. click Configure Agent. You can create an OpsCenter Agent from Settings > Configuration > Agent > Create Agent. this is the path on the OpsCenter Agent host where RAC (Remote Admin Console) 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. See “Configuring an OpsCenter Agent” on page 265. Note: The Username field is disabled if Enable Scheduled Job Data checkbox is unchecked. ■ If you want to collect the scheduled jobs data remotely.Understanding data collection Configuring data collection for NetBackup 285 Enable Scheduled Job Data Collection Click the checkbox if you want to enable scheduled job data collection from the master server. Note: Username and Password is not needed if the agent is installed on NBU master server. An error appears if OpsCenter cannot connect to the NetBackup master server on the network. 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. set the Future Scheduled Jobs option to Enable. Password Enter the password of the NetBackup user account. Note that you must enter the value in Username and Password fields so that scheduled job data can be collected. 5 . This is required if you enable scheduled job data collection. using the nbpemreq CLI. A user name is required if you enable scheduled job data collection. and specify valid NetBackup admin credentials. Alternately. Note: The Password field is disabled if Enable Scheduled Job Data checkbox is unchecked. Username Enter the user name to access the NetBackup master server. 4 Click Locate to check if OpsCenter can connect to the master server. Click Save to add the master server. you can click Cancel to exit. Use the checkbox to select a master server from the Network Name column. See “Adding a master server in the OpsCenter console” on page 282.286 Understanding data collection Configuring data collection for NetBackup 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. To delete a master server 1 2 3 4 In the OpsCenter console. Note that you cannot edit the Network Name for the master server. Deleting a master server You can delete one or more master servers using the following procedure. select Settings > Configurations > NetBackup . 5 Click Save. Click Delete. The following warning message appears: Deletion of the selected master server(s) will delete all related data. Click Edit. You can change the data that is shown for General Properties. and Advanced Data Collection Properties sections. A description of the fields present in these sections is available. 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. Advanced Properties. Use the checkbox to select one or more master servers from the Network Name column. Do you want to proceed? Click OK. The Network Name field falls under the General Properties section. Edit the information that is displayed on the Edit Master Server page. select Settings > Configurations > NetBackup. . Note: If you disable data collection it may appear to be a loss of data in OpsCenter.microsoft. To disable data collection for a master server 1 2 3 In the OpsCenter console. select Settings > Configurations > NetBackup. select Settings > Configurations > NetBackup . Microsoft Visual C++ 2005 SP1 Redistributable Package (x86) that is vcredist_x86. Use the checkbox to select one or more master servers from the Network Name column.exe VC Redistributable Package is available at: http://www.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. Click Disable Data Collection. to collect data properly. Caution: The Backup Exec data collector requires the following component to be installed on the OpsCenter Agent host. Collecting data from Backup Exec This section describes data collection from Backup Exec. For example. a drive may have the same status until you enable OpsCenter data collection again.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. Use the checkbox to select one or more master servers from the Network Name column.com/downloads/details. To enable data collection for a master server 1 2 3 In the OpsCenter console. Click Enable Data Collection. data types to be collected.x. Collecting data from PureDisk OpsCenter supports collection of data from Symantec NetBackup PureDisk. Password Version 8 Select blackout period details. select a check box in front of the Agent. The collected data is stored in the OpsCenter database. 11. Select the version of the Symantec Backup Exec server .x . On the Create Data Collector: Details page.x. and collection interval. for which you want to configure a Data Collector. Enter the password of this user account.from which you want to collect data. 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 . or 12. OpsCenter can collect Policy & Schedule and Job data types from PureDisk Storage Pool Authority (PureDisk SPA). from which you want to collect data. refer to the Symantec NetBackup PureDisk documentation. 9 Click Save.10. On the Create Data Collector: Product Selection page.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 . refer to the following section: See “ Configuring a Data Collector” on page 267. based on which you can generate reports. Click Next. On the Agent list. Click Create Data Collector. For more details on PureDisk. . enter the Backup Exec Server host name. In the Target Host Name text box. and other data collector settings. For more details on collection interval. select Symantec Backup Exec from the Select Product drop-down list. 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. which you can use to collect only PureDisk data. Table 5-5 describes the steps that you need to carry out to collect data from PureDisk.Understanding data collection Collecting data from PureDisk 289 PureDisk SPA and its components that run on the PureDisk operating system (PDOS). from OpsCenter. PureDisk determines whether multiple instances of the file are present on hosts across the network. which it backs up only once. To collect PureDisk data.OpsCenter Integrated Agent is also installed and configured. PureDisk identifies files and the data segments that contain identical data and treats them as a single instance of a file. Using the OpsCenter console. you do not need to manually install or configure OpsCenter Agent. Attributes of identical files. While backing up a file. You cannot delete the Integrated Agent. configure PureDisk See “Configuring data collector for the Integrated Agent. SPA host and OpsCenter AB host” This is a pre-requisite for PureDisk data collection on page 290. This lets you save storage space. 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. cannot be deleted Note: You can collect PureDisk data only through the OpsCenter Integrated Agent. including remote hosts. PureDisk data collector” on page 291. Note: When you install OpsCenter server. such as name and date of modification can vary. By using the deduplication technology. 3 . PureDisk stores only one instance of the file. The Single Instance Storage (SIS) or deduplication technology of NetBackup PureDisk is unique in storage and backup industry. conf This section provides the manual steps that you need to carry out on the PureDisk SPA host. 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. However.conf On UNIX: /opt/SYMCOpsCenterServer/config/security. logon as root and run the following command: su www-data 2 As a “www-data” user. The OpsCenter AB hostname is stored in the vxss. then the OpsCenter AB host is the host name that was provided as the remote authentication broker host during the OpsCenter installation. This is a pre-requisite for PureDisk data collection from OpsCenter.hostname parameter in the following file: On Windows: C:\Program Files\Symantec\OpsCenter\server\config\security. if OpsCenter is installed in a clustered mode. To set up a trust between PureDisk SPA host and OpsCenter AB host 1 On the PureDisk SPA host. the following message is displayed: setuptrust ------------------------------------------Setup Trust With Broker: OpsCenterABhost .290 Understanding data collection Collecting data from PureDisk 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. Note: OpsCenter AB host is the host where the OpsCenter server is installed. to setup trust between the PureDisk SPA host and the OpsCenter authentication broker host. from which you want to collect data. On the Create Data Collector: Product Selection page. To collect PureDisk data. In the Target Host Name text box. you do not need to manually install or configure OpsCenter Agent. Configuring PureDisk data collector This section provides the procedure to configure NetBackup PureDisk data collector on the OpsCenter UI. select Symantec NetBackup PureDisk from the Select Product drop-down list.Understanding data collection Collecting data from PureDisk 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. . When you install OpsCenter server. Click Next.OpsCenter Integrated Agent is also installed and configured. To configure NetBackup PureDisk data collector 1 2 Click Settings > Configuration > Agent . On the Agent list. 3 4 5 6 Click Create Data Collector. which you can use to collect only PureDisk data. You can collect PureDisk data only through the OpsCenter Integrated Agent. select a check box in front of the Integrated Agent. enter the PureDisk SPA Server host name. 6 For more details on collection interval.2. 6.2. and collaborative environments.292 Understanding data collection Collecting data from Enterprise Vault 7 On the Create Data Collector: Details page. 8 Click Save. and other data collector settings. specify the following PureDisk configuration settings: Product Version Select any of the following Symantec NetBackup PureDisk versions from the drop-down list: 6. you need to do it manually. 6. 6.1. refer to the following section: See “ Configuring a Data Collector” on page 267. Refer to the "Setting up a trust between the OpsCenter AB host and PureDisk SPA host" in the OpsCenter Administrator's Guide. .1. Collecting data from Enterprise Vault This section provides information about Enterprise Vault Data Collector configuration. It is supported only on Windows platform. file systems. refer to Enterprise Vault documentation.5. If it is not successful. 6.5.1. About Enterprise Vault Symantec Enterprise Vault software application provides a flexible framework for archiving emails.2. 6.5. Setting up a trust between the OpsCenter authentication broker host and PureDisk SPA host is accomplished automatically after PureDisk data collector is configured.2. 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. 6.0. 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. OpsCenter collects Policy and Retention Category data from Enterprise Vault database and stores it as Archive Policy data type. Table 5-6 lists the data types in OpsCenter that represent type of data that is collected from Enterprise Vault. Table 5-6 Enterprise Vault data types Data in Enterprise Vault Policy and Retention Category Vault Store and Vault Store Partition Mailbox. . as per the specified schedule.Understanding data collection Collecting data from Enterprise Vault 293 About data collected from Enterprise Vault OpsCenter categorizes the data that is collected from Enterprise Vault database into various data types. Figure 5-2 shows the hierarchy of archive data in Enterprise Vault. . For example. See “Configuring Enterprise Vault data collector” on page 302. The data collector collects the information from Enterprise Vault that is associated with the selected data types. vault partitions).Archives -----------------------------. See “About OpsCenter reports” on page 457.294 Understanding data collection Collecting data from Enterprise Vault Figure 5-2 Representation of Enterprise Vault data in OpsCenter reports Archive Site Exchange Server Enterprise Vault Server Vault Store Provisioning Group Vault Partition ----------------. Using OpsCenter archive reports you can determine the details about both archiving activities and archival storage. OpsCenter reports present archive data in the following two ways: . and Enterprise Vault Servers.Archive Storage ------------- An archive site is a logical group of hosts that need to be archived (Exchange Servers. storage media (vault stores. depending on which path you follow to drill down the site information. It is at the highest level in the Enterprise Vault data hierarchy. Provisioning Groups). in which OpsCenter Agent and MS SQL Server are installed on different hosts. and so on. original size of data that has been archived. 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. and so on. or how many emails were archived per Enterprise Vault Server. Storage of archived data A few archive reports show details about the storage of archived data.5. 8. . Enterprise Vault Microsoft SQL Server 7. OpsCenter supports local as well as remote archive-data collection. you need to configure OpsCenter Agent and data collector using the OpsCenter console. For example: details of vault stores and vault partitions where the archive data has been stored. Symantec recommends the remote data collection method. These are all archiving activities. For example: Details of mailboxes to be archived.0 2005. It supports all versions of Microsoft SQL Server that the Enterprise Vault supports. the number of mailboxes that exceed their warning limits per Exchange Server or Provisioning Group.Understanding data collection Collecting data from Enterprise Vault 295 Archiving activities A few archive reports show details about archiving activities. About versions supported by OpsCenter OpsCenter supports the following versions of Enterprise Vault. Note: Mailboxes are referred to as targets and an individual email is referred to as an item. To collect the archive metadata from Microsoft SQL Server. However. OpsCenter archive reports show only Exchange Server data. These archiving activity reports are available in the ‘Exchange’ report folder of Archive reports. 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. which you can view reports for. 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. to collect archive data remotely: deployment mode” on page 297. where the Enterprise Vault data resides. See “About creating a user in standalone deployment mode” on page 299. 4 Install MS SQL Server JDBC driver on the OpsCenter Agent host. Note: Symantec recommends that to collect See “About standalone Enterprise Vault data. . This can be an existing user. 2 3 Depending on the deployment mode of the OpsCenter Agent. configure the OpsCenter Agent to run in the context of the user or group that has access to MS SQL Server. which you want to use for integrated logon between Agent host and MS SQL Server host. add a user in the appropriate domain or workgroup. you deploy the deployment mode” OpsCenter Agent in single-domain mode. See “Installing MS SQL Server JDBC driver” on page 301. 5 For integrated logon. where the archive data resides. depending on the OpsCenter Agent deployment mode. rights on the MS SQL Server. ■ Single-domain mode See “About multi-domain ■ Multi-domain mode deployment mode” ■ Standalone mode on page 297.296 Understanding data collection Collecting data from Enterprise Vault 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. See “ About creating a user in multi-domain deployment mode” on page 299. See “ About creating a user in single-domain deployment mode” on page 299. See “Configuring the OpsCenter Agent properties for integrated logon” on page 300. on page 297. or you can create a new user in MS SQL Server and give required access rights. the OpsCenter Agent host and the MS SQL Server host (Enterprise Vault database instance) do not share the same Windows domain. Symantec does not recommend the multi-domain or standalone deployment of the OpsCenter Agent. Symantec does not recommend the multi-domain or standalone deployment of the OpsCenter Agent. depending on your setup. See “Configuring Enterprise Vault data collector” on page 302. The OpsCenter Agent host is in a domain different than the SQL Server domain. In this deployment mode. In this deployment mode. You can deploy the OpsCenter Agent on MS SQL Server host or OpsCenter Server host. the OpsCenter Agent host and the MS SQL Server host (Enterprise Vault database instance) do not share the same Windows domain. This section mainly talks about the remote agent deployment modes. The OpsCenter Agent host is installed on a standalone host. However. . About multi-domain deployment mode In addition to single-domain mode. About standalone deployment mode In this deployment mode. you can deploy the OpsCenter Agent in multi-domain mode. About single-domain deployment mode Symantec recommends that you deploy the OpsCenter Agent in single-domain mode to collect Enterprise Vault data. About OpsCenter Agent deployment modes This section describes various deployment modes in which you can deploy OpsCenter Agent.Understanding data collection Collecting data from Enterprise Vault 297 You need to configure the Enterprise Vault data collector using the OpsCenter console and schedule data collection. Note: To collect Enterprise Vault data. Note: To collect Enterprise Vault data. the OpsCenter Agent host and the MS SQL Server host (Enterprise Vault database instance) share the same Windows domain. Enterprise Vault also supports local Agent deployment. You need to add the user to these databases and give the required access rights on these databases. where the archive data resides. in the Object Explorer. Right-click the user name . 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.with which you want to perform integrated logon on the Agent host and MS SQL Server host. . expand the Security folder. For example. in the Select a page pane. make sure that the user has ‘datareader’ rights to access the desired database.for example ‘OpsDomain\localadmin’ with the password ‘pass’ . 7 8 9 10 Additionally. create a user with credentials ‘localadmin’ and ‘pass’. 3 4 5 6 In the MS SQL Server admin console.298 Understanding data collection Collecting data from Enterprise Vault Accessing MS SQL Server host This section describes how to give the required rights to a user to access MS SQL Server. select the ‘public’ check box. Note: To report on Enterprise Vault / archive data. Click Properties. select Server Roles. using SQL Server Management Studio Express or any other MS SQL Server client. On the logon Properties screen. Expand the logons folder. on which you want the access rights. Add this Windows domain user (local admin) to the MS SQL Server. Add this user (local admin) to the Enterprise Vault databases. In the Server roles pane at the right-hand side. To give rights to a user to access MS SQL Server 1 2 Create a Windows domain user on the MS SQL Server host. Open the MS SQL Server admin console. The user local admin in the OpsDomain (OpsDomain\localadmin) now has the rights to access MS SQL Server. OpsCenter Agent needs access to the Enterprise Vault directory and storage databases. where the archive data resides. Use credentials of this user (User name: 'localadmin' and Password: 'pass') when you configure the Agent properties for integrated logon. See “Accessing MS SQL Server host” on page 298. If you have deployed the OpsCenter Agent in the multi-domain mode. or you can create a new user with these credentials in MS SQL Server and give required access rights. About creating a user in multi-domain deployment mode Make sure that the user whose credentials (for example. where the archive data resides. See “Accessing MS SQL Server host” on page 298. (User name: 'localadmin' and Password: 'pass') in the Agent host domain that is the Windows domain. create a user. User name: 'localadmin' and Password: 'pass') you use for the integrated logon has required access rights on the MS SQL Server. 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.Understanding data collection Collecting data from Enterprise Vault 299 Depending on the OpsCenter Agent deployment mode. the procedure to create a logon user varies. See “About multi-domain deployment mode” on page 297. 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. 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. See “About single-domain deployment mode” on page 297. 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. The user 'localadmin' can be an existing user. User name: 'localadmin' and Password: 'pass') you use for the integrated logon has required access rights on the MS SQL Server. See “Configuring the OpsCenter Agent properties for integrated logon” on page 300. About creating a user in single-domain deployment mode Make sure that the user whose credentials (for example. In the Run dialog box. If you have deployed the OpsCenter Agent in the standalone mode.msc. To configure OpsCenter Agent properties 1 2 3 On the OpsCenter Agent host (Windows system). 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. However. On the Symantec OpsCenter Agent Properties screen. See “Configuring the OpsCenter Agent properties for integrated logon” on page 300. right-click the Symantec OpsCenter Agent service. on the Log On tab. click Start > Run. See “Accessing MS SQL Server host” on page 298. or you can create a new user with these credentials in MS SQL Server and give required access rights. Note: Make sure that this user has required rights to access MS SQL Server See “Accessing MS SQL Server host” on page 298.300 Understanding data collection Collecting data from Enterprise Vault The user 'localadmin' can be an existing user. This opens the Select User dialog box. Alternatively.who has the rights to access the MS SQL Server. create a user for example (User name: 'localadmin' and Password: 'pass') in the appropriate workgroup. See “About standalone deployment mode” on page 297. select the “This account” option.for example 'localadmin' with the password 'pass' . 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. click Browse. enter services. . On the right-click menu. 4 5 6 7 On the Services screen. The Windows Services screen is displayed. in the Open text box. on the services list. click Properties. Click Enter. where the Enterprise Vault archive data resides. Enter the credentials of the user . Use credentials of this user (User name: 'localadmin' and Password: 'pass') when you configure the Agent properties for integrated logon. 4 5 Click Save to save the . The SQL Server 2005 JDBC Driver is JDBC 3. Unzip the file.Understanding data collection Collecting data from Enterprise Vault 301 8 Enter a user name in the text box.zip file to a desired location. application server. This user should have access rights on MS SQL Server.0 compliant and runs on the Java Runtime Environment (JRE) 1. 9 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). The Agent requires the JDBC driver to communicate with the MS SQL Server. Click Check Names to check whether the user name that is specified is present in the Windows domain or not.2 page.4 and later versions. 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). . To install MS SQL Server JDBC driver 1 Click the following link: Download Microsoft SQL Server 2005 JDBC Driver 1. select the following: I Accept and I want to download the Microsoft Windows version The File Download dialog box is displayed. On the MICROSOFT SOFTWARE LICENSE TERMS page.2 2 3 On the Microsoft SQL Server 2005 JDBC Driver 1. click Download. you require the SQL Server JDBC driver that is installed on the OpsCenter Agent host. 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. or Java-enabled applet. and provides access to SQL Server 2000 and SQL Server 2005 from any Java application. Click OK. Click Create Data Collector. select Symantec Enterprise Vault from the Select Product drop-down list. Microsoft SQL Server 2005 JDBC Driver 7 Restart the Agent service. To collect archive data. 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.2\enu\auth\x86\sqljdbc_auth.302 Understanding data collection Collecting data from Enterprise Vault 6 Copy sqljdbc_1. Enter the following Configuration Settings: Database Instance Name This is the database instance name. select a check box in front of the Agent for which you want to configure the Data Collector. Click Next. Enter the name of the host.dll and sqljdbc_1. See “Configuring the OpsCenter Agent properties for integrated logon” on page 300. Database port number Enter the port number that is used to connect to the MS SQL Server. To configure Enterprise Vault data collector 1 2 3 4 5 6 7 In the OpsCenter console. On the Agent list. from where you want to collect the archive data. The default port number is 1433. By default this field is left blank. On the Create Data Collector: Product Selection page.2\enu\sqljdbc. . click Settings > Configuration > Agent . 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.jar files to the following location on the Agent host. 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. Archive Policy. See “Configuring the OpsCenter Agent properties for integrated logon” on page 300. You have specified the collection interval within which you want to collect the archive data. 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. You have entered the appropriate information for Enterprise Vault data collector variables. and Archive 10 Select collection interval. The SQL Server services are running. that is the MS SQL Server.Understanding data collection Collecting data from IBM Tivoli Storage Manager 303 8 9 Specify blackout period details. refer to the following section: See “ Configuring a Data Collector” on page 267. 11 Click Save. ■ ■ ■ ■ ■ ■ 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: . and other data collector settings. Select the data types that you want to collect. For more details on collection interval. Vault Store. See “Configuring Enterprise Vault data collector” on page 302. You can collect the following data types from an Enterprise Vault set up: Target. The OpsCenter Agent service is running. 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. You have selected the data types / events to be collected from the Enterprise Vault database. ) (Windows only) The TCP port on the TSM server through which the data collector establishes a connection. The path of TSM administrative client (dsmadmc). (The default password is admin.sys (Solaris and AIX). The path where files to be run dsmadmc reside. For example. 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. TSM ID TSM Password TSM Server Port dsmConfig dsmDir dsmadmc Location The path to the dsm.sample.) An administrator-level logon that is used to connect to the Tivoli Storage Manager server. Note: The TSM product environment variables DSM_CONFIG and DSM_SYS point to the dsmadmc required files dsm. product host is the value that you can use with the dsmadmc -tcpserveraddress option. . (The default is admin.domain.) The password for the account (specified in tsmId) for connecting to the TSM server.com Host assuming that Host can be fully qualified. The Solaris data collector uses only product host settings. the following entries are valid for product host: Host. In short. The TSM Server Port has no effect on Solaris. For more information. refer to your TSM documentation.opt and dsm. (This variable can be left blank.304 Understanding data collection Collecting data from IBM Tivoli Storage Manager Home Directory The home directory for the Tivoli Storage Manager installation.opt file. In short.255 SERVERNAME MYHOST. and other data collector settings. The following is a sample dsm.mycompany. To increase the efficiency of the Networker data collector.255. The directory path for the log file containing group-complete messages. or relative to homeDirectory The directory path of the nsradmin CLI.COM TCPSERVERADDRESS 255. or relative to homeDirectory Location of messages file Location of nsradmin.exe .exe The directory path of the mminfo command-line interface (CLI). and point messagesFile to this log Location of mminfo. for tag SErvername (note the case).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. 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.sys file.sys file: ***************************************** SErvername server_a COMMmethod CoMMmethod TCPip TCPPort 1500 TCPServeraddress 255. The default file name is messages.255. product host is the value that you can use with the dsmadmc -se option.Veritas.255 NODENAME myhost. configure Networker to create a log that contains only group complete messages. absolute.255. refer to the following section: See “ Configuring a Data Collector” on page 267. absolute.255. This path may be absolute or relative to homeDirectory.com ****************************************** For more details on collection interval. Location of nsr file Location of mminfo file Output of mminfo(Optional) For more details on collection interval.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. . refer to the following section: See “ Configuring a Data Collector” on page 267. and other data collector settings. nsrFile. and mminfoFile even though these variables are optional and only advanced users must set them. . You can create views in Java View Builder and make them available in the OpsCenter console.Chapter 6 Managing OpsCenter views This chapter includes the following topics: ■ ■ ■ 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. Figure 6-1 shows the details that are displayed on the Views tab in the OpsCenter console. you can identify the locations or departments with hosts storing business critical data. In a OpsCenter view.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. . or applications. you cannot modify its attributes because you do not have the write permissions for that view. An OpsCenter Reporter has the Read permissions on the views only if it has the required permissions. business units.create. they cannot manage . an OpsCenter Analyst and Reporter need to have the required rights assigned to them through Java View Builder. Note: To manage views. IT assets that are scattered across organization can be arranged according to their locations. or delete . You can generate various OpsCenter reports that are filtered by views. An OpsCenter Analyst has the Read permissions on all views. If they do not have these rights. edit. With these reports. However.views using the OpsCenter GUI. See “About user access rights” on page 235. 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. As Media reports run only on 'Master Server view'. which are then stored in the database. Note: To run the Java View Builder. objects are made available for assigning to that view. Note: All Veritas Backup Reporter (VBR) views are migrated to OpsCenter as Client views. In a view hierarchy. each view is associated with a view type. The Java View Builder makes these IT assets available when a view is created. you need Java Runtime Environment (JRE) installed on the host. only backup clients are available to be assigned to the view. you need to once again create the Master Server views to run the Media reports with views. Master server Policy . If you create a view of type Policy. About view types In OpsCenter. only policies are available to be assigned to the view. only Master Servers are available to be assigned to the view.Managing OpsCenter views About OpsCenter views 309 After you install and run the OpsCenter Server and the OpsCenter Agent. You can create views of the following types: Client If you create a view of type Client. OpsCenter detects theIT assets. Depending on the type of the view. If you create a view of type Master Server. between top and bottom levels you can create a number of user-defined levels. An OpsCenter view is a homogeneous one. after upgrade from VBR. it cannot have hosts and file systems in the same tree. A view can either be public or private. See “Modifying view level alias” on page 314. Figure 6-2 shows an example of a view comprising multiple nodes and objects. You can add multiple nodes to a view at different levels.310 Managing OpsCenter views About OpsCenter views Enterprise Vault server If you create a view of type Enterprise Vault server. Between the top level and the bottom level. About view levels A newly created view has only one level. About nodes and objects An OpsCenter view comprises nodes and view objects. Only view owner and OpsCenter admin can access private views. A node is a logical entity that you add to create a hierarchical structure of a view. you can specify the access rights for that view. If you create a view of type File System. If you create a view of type Exchange server. to create a hierarchical structure in the view. only vaults are available to be assigned to the view. You can add alias for each of these view levels. Public view Private view All OpsCenter users can access public views. Exchange server Vault File System About accessing OpsCenter views While creating an OpsCenter view. you can create multiple intermediate levels to organize view objects into logical groups. clients. See “Creating views” on page 312. or policies are always at the lowest levels in a view. Master server hosts. you can add multiple nodes. only file systems are available to be assigned to the view. only Exchange servers are available to be assigned to the view. . Between the first level (the view name itself) and the last level (actual view object). only EV servers are available to be assigned to the view. If you create a view of type Vault. 2 To check the details of a view. edit. See “Creating views” on page 312. See “Modifying views” on page 313.Managing OpsCenter views Managing views 311 Figure 6-2 View nodes and objects Managing views This section provides procedures to add. Viewing OpsCenter views and their details This section provides the procedure to view OpsCenter views. See “About OpsCenter views ” on page 307. A list of views that you have already created is displayed. To view OpsCenter views 1 In the OpsCenter console. . or delete OpsCenter views. click Settings > Views. select the view from the views list. The details are displayed in the lower section of the page. 312 Managing OpsCenter views Managing views Alias View Levels tab This tab shows the details of view level aliases of the selected view. click Settings > Views. See “Modifying view level alias” on page 314. . To create a view 1 2 In the OpsCenter console. Level 2. and so on. Default view level aliases are as follows: Level 1. Click Add. 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. if you have not added any nodes or objects to the selected view. You can modify the view level aliases. The Alias View Levels tab does not contain any data. All users can access public views. . specify the following view details: Name View type Enter the view name Select the view type: Client. To modify views 1 2 3 In the OpsCenter console. If you do not select this check box. Description Enter description about the view. Policy. or Exchange Server See “About view types” on page 309. 4 Click OK. select a view that you want to modify. Master Server. Enterprise Vault Server. Modifying views This section provides the procedure to modify view details. Click Edit. See “About accessing OpsCenter views” on page 310. and North America. Europe. click Settings > Views. For example: This is a geographical view that comprises of master servers located in Asia Pacific. From the list of views. Make the View Public Select the check box if you want to make the view public.Managing OpsCenter views Managing views 313 3 On the Add View dialog box. Users other than you and OpsCenter admin cannot access this view. the view becomes private. Select the check box if you want to make the view public. If you delete a view. . Click Delete. Click Edit Alias View Levels. click Settings > Views.314 Managing OpsCenter views Managing views 4 On the Edit View dialog box. To modify alias view levels 1 2 3 In the OpsCenter console. See “Adding nodes to a view” on page 315. click Settings > Views. Modifying view level alias This section provides the procedure to modify alias of view levels. See “About accessing OpsCenter views” on page 310. From the list of views. Deleting views This section provides the procedure to delete views. it cannot be recovered. From the list of views. select a view that you want to delete. all its nodes are deleted and the objects are moved to the unassigned tree. you can modify the following view details: Name Description Make the View Public Modify the view name Modify the view description. Note: Once you have deleted a view. All users can access public views. select a view for which you want to modify view level alias. 5 Click OK. To delete views 1 2 3 In the OpsCenter console. Managing OpsCenter views Managing nodes and objects 315 4 On the Alias View Levels dialog box. Alias Level 2 as Country. For example. 6 Managing nodes and objects This section provides procedures to create. . click Settings > Views. and delete nodes and objects of a view. and Alias Level 3 as Region. On the Add dialog box. For example. enter the node name. select the view to which you want to add a node. Click OK. select a view to which you want to add nodes and objects. Click Manage Nodes and Objects. if the selected view has three levels. To add nodes to a view 1 2 3 4 5 6 7 In the OpsCenter console. if the selected view has only one level. you can rename the levels as follows: rename Alias Level 1 as Geography. From the list of views. modify. On the view tree. See “About nodes and objects” on page 310. the Alias View Levels dialog box appears as follows: 5 Rename the available levels. text boxes for entering aliases for all available view levels appear. Adding nodes to a view This section provides the procedure to add a node to a view. Click Add. Click OK. On the view tree. From the list of views. To delete a node 1 2 3 4 5 6 7 In the OpsCenter console.316 Managing OpsCenter views Managing nodes and objects Modifying node details This section provides the procedure to modify the information of a view node. To modify node information 1 2 3 4 5 6 7 8 In the OpsCenter console. See “Adding nodes to a view” on page 315. . click Settings > Views. Select the node that you want to modify. modify the name of the node. On the view tree. Click Edit. expand the view to see the associated nodes. On the confirmation dialog box. click OK. click Settings > Views. On the Edit dialog box. Select the node that you want to delete. expand the view to see the associated nodes. From the list of views. Click Delete. See “Adding nodes to a view” on page 315. select a view to modify the information of associated nodes. Deleting nodes This section provides the procedure to delete the nodes from a view. Click Manage Nodes and Objects. Click Manage Nodes and Objects. Click OK. select a view from which you want to delete nodes. Adding objects to a view node This section provides the procedure to add objects to a view or a node within a view. The available objects list varies depending on the view type. 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. select the view name or a view node from which you want to delete an object. Click Add to Node. From the list of views. On the view tree. Click Manage Nodes and Objects. From the list of views. select the Unassigned Objects tab. See “Working with view filters” on page 318.Managing OpsCenter views Managing nodes and objects 317 To add an object to a view node 1 2 3 4 5 In the OpsCenter console. The Unassigned Objects tab contains all objects that have not yet been assigned to the selected view or view node. 6 7 Select the check boxes in front of the view objects that you want to add to the selected view or view node. The objects that are assigned to this view or the view node are displayed on the Objects on Node tab. only client hosts are available on the Unassigned Objects tab for selection. select the view name or a view node to which you want to add an object. 5 Select the check boxes in front of the view objects that you want to delete. In the right-hand-side pane. On the view tree. 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 Manage Nodes and Objects. For example: If the view is of type Client. click Settings > Views. click Settings > Views. The added view objects are removed from the Unassigned Objects tab and appear on the Objects on Node tab. select the view to which you want to add objects. select the view from which you want to delete objects. Solaris Clients. select the view to which you want to assign objects. Active Policies. For example: If the view is of type Client. From the list of views. 6 Click the Create Filter icon. Not Connected Servers. Other Servers All Policies. Windows Clients. To create a view object filter 1 2 3 4 5 In the OpsCenter console. The list of objects that is displayed varies depending on the view type.318 Managing OpsCenter views Managing nodes and objects 6 7 Click Delete from Node. Solaris Servers. select the view name or the view node to which you want to assign view objects. 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. In the right-hand-side pane. select the Unassigned Objects tab. Other Clients All Servers. click OK. Catalog Policies. Inactive Policies. Table 6-1 lists the default filters available for various view types. You can also create your own filters and apply them to view the required list of view objects. Other Policies Master Server Policy Creating a view object filter This section provides the procedure to create user-defined view object filters. Table 6-1 View type Client Default filters Default filters All Clients. On the confirmation dialog box. Windows Policies. Connected Servers. Linux Servers. On the view tree. Partially Connected Servers. See “Working with view filters” on page 318. Standard Policies. Windows Servers. . Click Manage Nodes and Objects. The default set of filters vary depending on the view type. Linux Clients. only client hosts are available on the Unassigned Objects tab for selection. click Settings > Views. 8 Click OK. ■ Use the links appearing in the Link as follows: Click Add to add a new row for specifying new filter criteria. This user-defiled filter is now added in the Filter drop-down list on the Unassigned Objects tab. ■ The following figure shows an example of creating a filter. with which you want to filter the available view objects. See “Deleting view object filters” on page 320. ■ And . This lets you specify multiple filter criteria. 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. which you can modify or delete. ■ Click Remove to remove the respective row from the filter criteria.Select an operator to form a filter criteria.Enter the value for the selected column. See “Modifying view object filters” on page 320.Select And or Or as appropriate. ■ Value .Managing OpsCenter views Managing nodes and objects 319 7 On the dialog box. ■ Operator . . select the Unassigned Objects tab. For example: If the view is of type Client. Click Manage Nodes and Objects. select the view name or a view node to which you want to assign view objects. On the view tree. Click OK. Deleting view object filters You can delete user-defined view object filters. On the view tree. Select the Edit Filter icon. the Edit Filter icon is disabled. See “Creating a view object filter” on page 318. To delete view object filters 1 2 3 4 In the OpsCenter console. 8 9 On the dialog box. select the view to which you want to assign objects. If you have selected a default filter. only client hosts are available on the Unassigned Objects tab for selection. You cannot modify the default filters. select the view name or a view node to which you want to assign view objects. In the right-hand-side pane. You cannot delete the default filters. select the view to which you want to assign objects. . modify name or definition of the filter. From the list of views. 6 7 From the Filter drop-down list. To modify view object filters 1 2 3 4 5 In the OpsCenter console. select the user-defined filter that you want to modify.320 Managing OpsCenter views Managing nodes and objects Modifying view object filters You can modify definition of user-defined view object filters. See “Creating a view object filter” on page 318. Click Manage Nodes and Objects. From the list of views. click Settings > Views. click Settings > Views. 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. The list of objects that is displayed varies depending on the view type.Managing OpsCenter views Managing nodes and objects 321 5 6 In the right-hand-side pane. select the Unassigned Objects tab. the Delete Filter icon is disabled. . If you have selected a default filter. 322 Managing OpsCenter views Managing nodes and objects . . media. hosts. and alerts. services. devices.Chapter 7 Monitoring NetBackup using Symantec OpsCenter This chapter includes the following topics: ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ 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. policies. you can view detailed information about your NetBackup environment including jobs. 3 About timeframe selection You can also view data for the last 24. Ensure that other master servers are unchecked. In addition to using the default view i. or 72 hours for some of the Monitor views by clicking Last 24 Hours. you can also create your own views from Settings > Views or by using Java View Builder. you can create a view like Geography to view details about master servers in a particular region like Europe. . select ALL MASTER SERVERS from the drop-down list in the View pane. Note that by default data for the last 24 hours is shown in these views. Last 48 Hours. To view details of all master servers ◆ In the OpsCenter console. select ALL MASTER SERVERS from the drop-down list in the View pane. These options are located on the top-right corner of specific Monitor views. Click Apply Selection. Use the following procedure to view details of all master servers or specific master servers. or Last 72 Hours respectively. For example. 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. ALL MASTER SERVERS. 48. Deselect the checkbox next to ALL MASTER SERVERS and select the specific master servers from the list of master servers. 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.e. To view details of specific master servers 1 2 In the OpsCenter console. More information about how to create views by using the Settings > Views is available.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. This view gives an overview of your NetBackup environment. you can also customize the timeframe selection by clicking Customize and specifying an absolute timeframe or relative timeframe.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. you can view data for any timeframe that you want like you can view jobs data for the previous three weeks. Top 7 Job Error Log Summary. you can use links to drill down and access detailed information about many aspects of your NetBackup environment. Using the Customize option. The pie segments are also links to more details for the monitoring category. From this view. Job Summary by Exit Status. 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. The Customize option is located on the top-right corner of specific Monitor views. This view contains the different sections which display specific information about your NetBackup environment. 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 . Top 7 Policies by Failed Jobs. Pie charts for most monitoring categories appear. and Alert Summary by Severity sections) Monitor > Jobs Monitor > Alerts Monitor > Policies (Summary View) ■ ■ ■ In addition. Or Click a colored section of the pie chart that corresponds to a particular job state. do either of the following: ■ Click on the number of jobs (link) for a particular job state from the table. select Monitor > Overview. A pie chart with different colors represents media distribution in this section. click on the number that is shown for Done jobs. To view jobs by job state 1 2 In the OpsCenter console. ■ 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. click on the yellow section of the pie chart to view details for Queued jobs. queued. Pointing on the pie chart gives the number and percentage of media with a particular media . 22 jobs. You can drill down from this section to see details for failed. or 42% jobs in your environment are in a queued state. See “Controlling the scope of Monitor views” on page 324. incomplete. For example. You can also view the color code summary in this section to know the colors that represent different media status. 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 data for the last 48 hours or 72 hours.326 Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup using the Overview subtab ■ 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. For example. This information is shown in a pie chart as well as a table. A pie chart with different colors represents the job distribution. This information is shown in a pie chart as well as a table. Data for the last 24 hours is shown by default. Pointing on the pie chart gives the number and percentage of jobs in a particular job state in your NetBackup environment. For example. Each color of the pie chart represents how media are distributed in your environment as per the media status. pointing on the yellow color in the pie chart shows that in the last 24 hours. active jobs etc. In the Job Summary by State section. You can also view the color code summary in this section to know the colors that represent different job states. Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup using the Overview subtab 327 status in your NetBackup environment. Data for the last 24 hours is shown by default. select Monitor > Overview. To view media by media status 1 2 In the OpsCenter console. Or Click a colored section of the pie chart that corresponds to a particular media status. For example. pointing on the red color in the pie chart shows that four media or 2% media in your environment are frozen. For example. The total number of running and stopped NetBackup services are shown in a table. See “Controlling the scope of Monitor views” on page 324. click on the red section of the pie chart to view details for Frozen media. The content that is shown in this section is based on the current View pane selection. ■ 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. click the number for Frozen media. You can also view data for the last 48 hours or 72 hours. The table that appears in the section lists the top seven exit status codes responsible for maximum job failure and also lists the number of failed jobs for each exit status in the selected timeframe. In the Media Summary by Status section. you can quickly analyze the reasons behind maximum job failures in your environment. Note that the failed jobs that are shown in the Failed Job Count column are arranged in descending order in the table. do either of the following: ■ Click the number of media (link) for a particular media status from the table. 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. . For example. You can drill down from this section to see details for media with different status like details for frozen and active media. You can drill down from the links in this table to see details for running or stopped services. By viewing this section. In the Master Server Summary section. To view the master servers that are connected 1 2 In the OpsCenter console. To view all master servers 1 2 In the OpsCenter console. 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. select Monitor > Overview. To view details of the master servers that are not connected 1 2 In the OpsCenter console. click the number that is shown in the Total column. click the number that is shown in the Service Count column of the table. You can also see details of the clients that do not have a backup policy configured for them. In the Master Server Summary section. In the Master Server Summary section. . 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. For example. In the Service Summary section. click on the number that is shown for Running services to view details for the services that are running.328 Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup using the Overview subtab To view running or stopped services 1 2 In the OpsCenter console. select Monitor > Overview. click the number that is shown in the Connected column. click the number that is shown in the Not Connected column. select Monitor > Overview. select Monitor > Overview. Data for the last 24 hours is shown by default. For example. do either of the following: ■ Click the number of jobs (link) corresponding to a particular exit status from the table. click the number that is shown in the Clients at Risk column. or 42% jobs in your environment failed. Each color of the pie chart represents how jobs are distributed in your environment as per the exit status. For example. Note that the drop-down list is located on the top-right corner of the page. In the Job Summary by Exit Status section. A pie chart with different colors represents the job distribution by exit status in the selected timeframe. successful. partially successful. select Monitor > Overview. You can also view the color code summary in this section to know the colors that represent different exit status. Or Click a colored section of the pie chart that corresponds to a particular exit status. In the Master Server Summary section. You can also view data for the last 48 hours or 72 hours. To view jobs by exit status 1 2 3 In the OpsCenter console.Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup using the Overview subtab 329 To view details of the clients that are at risk 1 2 In the OpsCenter console. Pointing on the pie chart gives the total number and percentage of successful. pointing on the red color in the pie chart shows that in the last 24 hours. or partially successful jobs. 72 jobs. a table also shows the amount of data that has been backed up for the selected view and timeframe. In addition. See “Controlling the scope of Monitor views” on page 324. 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. You can drill down from this section to see details for failed. select Monitor > Overview. and failed jobs in your NetBackup environment. Select Summary View from the drop-down list. This information is also listed in a tabular format. This information is shown in a pie chart as well as a table. ■ . click on the red section of the pie chart to view details for failed jobs. down. do either of the following: ■ Click the number of drives (link) for a particular drive status from the table. . The table that is shown in the section lists the top seven policies which have maximum failed jobs associated with them. This information is shown in a pie chart as well as a table. or mixed drives. From this section you can quickly view the policies which have the maximum failed jobs associated with them. For example. For example. You can drill down from this section to see details of all drives including up. You can also view the color code summary in this section to know the colors that represent different exit status. pointing on the green color in the pie chart shows that 5 drives or 100% drives in your environment are up. You can also view data for the last 48 hours or 72 hours. In the Drive Summary by Status section. Each color of the pie chart represents how drives are distributed in your environment as per the drive status. A pie chart with different colors represents the distribution of drives by drive status in the selected timeframe. Data for the last 24 hours is shown by default. click on the green section of the pie chart to view details for the drives that are up. Pointing on the pie chart provides the number and percentage of drives with up or down status in your NetBackup environment. select Monitor > Overview. For example. Note that the failed jobs (shown in Total Number of Failed Jobs column) are arranged in descending order in the table. To view drives by drive status 1 2 In the OpsCenter console. The table also shows the number of failed jobs for each policy. ■ 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.330 Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup using the Overview subtab 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. See “Controlling the scope of Monitor views” on page 324. click the number for Up drives Or Click a colored section of the pie chart that corresponds to a particular drive status. or 17% alerts in your environment are critical. click on the red section of the pie chart to view details for critical alerts. select Monitor > Overview. do either of the following: ■ Click the number of alerts (link) for a particular alert severity from the table. In the Alert Summary by Severity section. Or Click a colored section of the pie chart that corresponds to a particular alert severity. You can also view data for the last 48 hours or 72 hours. Pointing on the pie chart gives the number and percentage of alerts with a particular severity in your NetBackup environment. A pie chart with different colors represents the alert distribution by severity in this section. This information is shown in a pie chart as well as a table. You can also view the color code summary in this section to know the colors that represent different severity. For example. Each color of the pie chart represents how alerts are distributed in your environment as per the alert severity. pointing on the green color in the pie chart shows that in the last 24 hours. Data for the last 24 hours is shown by default. 200 alerts. You can use the following views to see NetBackup job information: . For example. click on the number that is shown for Critical alerts. You can drill down from this section to see details for alert categories. ■ Monitoring NetBackup jobs The Monitor > Jobs view provides details of NetBackup jobs. See “Controlling the scope of Monitor views” on page 324.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. To view alerts by severity 1 2 In the OpsCenter console. For example. Using the List View for monitoring jobs This view is displayed when you select Monitor > Jobs. The table that appears in this view shows the following columns by default: . Summary View The Summary View contains the different sections which show the NetBackup job distribution by exit status. Data for the last 24 hours is shown by default. This view displays detailed information about jobs based on the current View pane and timeframe selection. Hierarchical View The Hierarchical View shows all parent-child jobs in a hierarchical fashion based on the current View pane and timeframe selection. See “Using the List View for monitoring jobs” on page 332. job state. This view displays detailed information for jobs for the current View Pane and timeframe selection. The List View is shown by default. This information is shown in pie charts and tables. Note: You can only view jobs data for the last 30 days from the Hierarchical View. The drop-down list is located at the top-right corner of the page. See “Controlling the scope of Monitor views” on page 324. You can also view data for the last 48 hours or 72 hours. See “Using the Hierarchical View for monitoring jobs” on page 343. and job type 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. Note: You can select these views from the drop-down list. See “Using the Summary View for monitoring jobs” on page 340.332 Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup jobs List View This view is shown by default when you select Monitor > Jobs. Note: You can only view jobs data for the last 30 days from the List View. time. Exit status of the job. This column lists the current NetBackup job state like whether the job is Queued. time. This column lists the date. This column lists the job type like whether the job is a DB Backup or an Image Cleanup job. This column lists the number of files that have been backed up by this job. Done etc. This column lists the time that is taken by the job. The link provides status description and details on troubleshooting in case it failed. For a running job. and year when the job ended.) End Time This column lists the date. This column lists the name of the client on which the job is run. You can click on the link to view details for the master server. This column shows the name of the master server (link) associated with the job. Elapsed Time is the difference between the current time and Start time. Waiting for Retry. This column lists the name of the policy that is associated with the job.Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup jobs 333 Job ID This column shows the unique ID associated with the job (link). The Elapsed Time is the difference between End Time and Start Time values. This column lists the size of the job. and year when the job started. Job Size Files . 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. 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 . Not all columns are displayed in the table by default. More columns can be added to your view by clicking the Table Settings icon.334 Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup jobs % Complete This column lists the percentage of job that has been completed. The Attempts tab shows details of the attempts that have been made to complete a job.Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup jobs 335 ■ ■ ■ ■ Reconciliation Reason Data Reduction Savings (%) Priority State Details See the online NetBackup Administration Console Help for a detailed description of these fields. The File List tab shows the files that have been backed up by the job and also their location. Click the ID (link) for a job from the Job ID column of the table. Attempts File List To view details for a single NetBackup job 1 2 In the OpsCenter console. It also includes the contents of all the available columns that can be viewed from the table. The Details pane has the following tabs: General The General tab of the Details pane displays all information available for the job. 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. See “About using tables” on page 58. The Details pane is located at the bottom of the Monitor > Jobs view. . More information about how to customize tables and view specific columns is available. Viewing the details for a single NetBackup job All the details that are associated with a job can be viewed from the Details pane. select Monitor > Jobs. You can also enable or disable data collection for the master server from this page. Most of the policy details are listed. A separate page appears that shows policy information on the following tabs: General This tab is shown by default. Click the server name (link) associated with the job in the Master Server column of the table. Select this filter to view only active jobs . The built-in job filters are the following: All Jobs (default filter) Active Jobs Select this filter to view details of all the jobs. Click the policy name (link) for the job in the Policy column of the table. To view policy information for a job 1 2 3 In the OpsCenter console. select Monitor > Jobs. Schedules This tab displays the properties of schedules that are associated with the policy. The details of the master server are shown on a separate page. Viewing policy information for a job Use the following procedure to view the details for the policy that is associated with a job. Click on the master server link to view details of the master server that is associated with the policy. select Monitor > Jobs.336 Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup jobs To view information for the master server that is associated with a job 1 2 In the OpsCenter console. 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. Select this filter to view the jobs that failed. Note that the drop-down list is located on top of the table. See “Using filters to customize your views” on page 62. Select this filter to view the jobs that have been suspended. Select this filter to view the jobs that are undefined. Select this filter to view the jobs that have been canceled. you can also create your own custom filters. Select this filter to view the jobs that are incomplete. To view details by job state 1 2 Select Monitor > Jobs. Before you perform these tasks. resume. Note: These tasks are not visible if you log on with an Analyst or a Reporter role. Select this filter to view the jobs that are successful.Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup jobs 337 Queued Jobs Done Jobs Suspended Jobs Select this filter to view only queued jobs. 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. Select this filter to view only Done jobs. Select this filter to view the jobs that are partially successful. . manually refresh your Web browser to obtain an updated view for all jobs. or restart a job. suspend. Controlling NetBackup jobs Use the following procedure to cancel. Select a filter from the drop-down list. Select this filter to view the jobs that are waiting for retry. 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. By using the Reconcile option and selecting a reason. In the Reconcile Jobs dialog box. 6 Click OK. . select a reason for reconciling the job from the drop-down list. Note: The Reconcile option is disabled in the unlicensed version (Symantec OpsCenter). These buttons are located on top of the table. You may select one or more jobs.338 Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup jobs To control a job 1 2 3 4 In the OpsCenter console. Ensure that List View is selected in the drop-down list. select Monitor > Jobs. Suspend. Note that you can select Un-Reconcile from the drop-down list to undo a reconciliation. Note that the drop-down list is located on the top-right corner of the page. You can select one or more jobs. host cannot be reached etc. Select a job from the table. Restart. Note that the drop-down list is located on the top-right corner of the page. Click Cancel. Reconciling NetBackup jobs You can use the Reconcile option to prevent the jobs that failed due to reasons like user terminating a job. Select a job from the table. from being billed. 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. Ensure that List View is selected in the drop-down list. Resume. From the More drop-down list. The OpsCenter console may take some time to show the updated status once you perform the tasks. select Monitor > Jobs. select Reconcile. Note that the drop-down list is located on the top-right corner of the page. select Monitor > Jobs. Click Finish. Ensure that List View is selected in the drop-down list. set the job priority to a particular value. From the More drop-down list. To change the job priority 1 2 3 4 5 6 7 In the OpsCenter console. Click OK. Note: Logs are not available for all job types. select Monitor > Jobs. Priority can be changed only for jobs from the master servers that are running NetBackup 6. Note that the drop-down list is located on the top-right corner of the page. Before exporting a log file. Note: The Export Job Logs option is not visible if you log on with an Analyst or a Reporter role. In the Change Priority dialog box. select Change Job Priority. You can also increment or decrement the job priority.Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup jobs 339 Changing the job priority You can change the priority that is associated with a job. Select an active job or a queued job from the table. You can view or save the exported log files in an Excel format. ensure that the NetBackup master server is Connected and the selected job logs are enabled. The OpsCenter console may take some time to show the updated status once you perform this task.2 or higher versions. To export the NetBackup log files for a job 1 2 In the OpsCenter console. Exporting NetBackup job logs You can export the log files that are 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. Ensure that List View is selected in the drop-down list. .5. . See “Controlling the scope of Monitor views” on page 324. Data for the last 24 hours is shown by default. The drop-down list is located at the top-right corner of the page. These sections show NetBackup job information in a table as well as a pie chart. Data for the last 24 hours is shown by default. You can also view data for the last 48 hours or 72 hours. select Export Job Logs. You can also view data for the last 48 hours or 72 hours. The Summary View contains the different sections which display specific information about NetBackup jobs. See “Controlling the scope of Monitor views” on page 324. You can export only one job log at a time. The data that is shown in this view is based on the current View pane and timeframe selection. 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.340 Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup jobs 3 Select a job from the table. 4 5 From the More drop-down list. 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 table and the pie charts include links to filtered detail views. Click Open or Save from the dialog box to view or save the log file in an Excel format. 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 content that is shown in the Summary View is based on the current View Pane and timeframe selection. This information is shown in a pie chart as well as a table. Each color of the pie chart represents how jobs are distributed in your environment as per the job state. Pointing on the pie chart gives the number and percentage of jobs with a particular exit status in your NetBackup environment. A pie chart with different colors represents the job distribution by job state. ■ 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. You can also view the color code summary in this section to know the colors that represent different job states. 22 jobs. For example. the jobs that are waiting for retry. click on the red section of the pie chart to view details for failed jobs. You can drill down from this section to see details for the jobs that failed. or 42% jobs in your environment are in a queued state. Or Click a colored section of the pie chart that corresponds to a particular exit status. To view jobs by exit status 1 2 3 In the OpsCenter console. You can also view data for the last 48 hours or 72 hours. Note that the drop-down list is located on the top-right corner of the page. For example. pointing on the red color in the pie chart shows that in the last 24 hours.Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup jobs 341 A pie chart with different colors represents the job distribution by exit status in this section. select Monitor > Jobs. Pointing on the pie chart gives the number and percentage of jobs in a particular job state in your NetBackup environment. 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. This information is shown in a pie chart as well as a table. do either of the following: ■ Click the number of jobs (link) corresponding to a particular exit status from the table. See “Controlling the scope of Monitor views” on page 324. 72 jobs or 42% jobs in your environment failed. Data for the last 24 hours is shown by default. For example. partially successful. . In the Job Summary by Exit Status section. pointing on the yellow color in the pie chart shows that in the last 24 hours. Select Summary View from the drop-down list. queued or active jobs etc. You can drill down from this section to see details for successful. and failed jobs. For example. You can drill down from this section to see details for different job types like DBBackup. click on the number that is shown for Done jobs. Note that the drop-down list is located on the top-right corner of the page. You can also view the color code summary in this section to know the colors that represent different job types. Each color of the pie chart represents how jobs are distributed in your environment as per the job type. In the Job Summary by State section. do either of the following: ■ Click the number of jobs (link) corresponding to a particular job type from the table. For example. Or . A pie chart with different colors represents the job distribution by job type in this section.342 Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup jobs To view jobs by job state 1 2 3 In the OpsCenter console. For example. pointing on the red color in the pie chart shows that in the last 24 hours. click on the number that is shown for DBBackup jobs. Select Summary View from the drop-down list. 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. select Monitor > Jobs. 22 jobs or 42% jobs in your environment are DBBackup jobs. To view jobs by job type 1 2 3 In the OpsCenter console. Data for the last 24 hours is shown by default. Image Cleanup etc. You can also view data for the last 48 or 72 hours. click on the yellow section of the pie chart to view details for Queued jobs. See “Controlling the scope of Monitor views” on page 324. do either of the following: ■ Click the number of jobs (link) in a particular job state from the table. ■ 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. Pointing on the pie chart gives the number and percentage of jobs of a particular job type in your NetBackup environment. select Monitor > Jobs. For example. This information is shown in a pie chart as well as a table. Or Click a colored section of the pie chart that corresponds to a particular job state. A child job is indented to the right-hand side in the Job ID column. All tasks that apply to the parent job are also applicable to its child jobs.Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup jobs 343 ■ Click a colored section of the pie chart that corresponds to a particular job type. then + sign also appears before the job ID of the child job. You can view details of only the top level. the current selected sort order is applied to child jobs. You can also view data for the last 48 or 72 hours. child jobs are not considered at all. The data that is shown in this view is based on the current View pane and timeframe selection. Note the following things about the related jobs that are shown in the Hierarchical View: ■ The filters are applied only to parent jobs. Neither is there a + sign before the job ID of such a job nor this job is indented to the right-hand side. The sorting feature in the Hierarchical View applies to both parent jobs and child jobs. For example. Only parent jobs or unrelated jobs (jobs that are not related to any other job) with partially successful status are considered. In the Hierarchical View. If some of the child jobs are parent jobs. When you expand a parent job. if a job does not have a relationship with any other job (meaning it is neither a parent nor a child job). Note: You can only view jobs data for the last 30 days from the Hierarchical View. click on the red section of the pie chart to view details for DBBackup jobs. All parent jobs have a +sign before the job ID. Data for the last 24 hours is shown by default. parent job in this view with the ability to expand and drill into the details of child jobs if there are failures. all related jobs can be grouped and you can see all parent-child jobs in a hierarchical fashion. However. For example. it is represented only by its job ID in the Job ID column. The filters are not applied to child jobs. The Hierarchical View shows details of all jobs and also highlights the parent-child relationship between jobs wherever applicable. 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. if you apply the Partially Successful Jobs filter. You can click the + sign to see all child jobs. See “Controlling the scope of Monitor views” on page 324. ■ ■ . Click the ID (link) for a job from the Job ID column of the table. It also includes the contents of all the available columns that can be viewed from the table. The Details pane has the following tabs: General The General tab of the Details pane displays all information available for the job. The Attempts tab shows details of the attempts that have been made to complete a job. 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. View the job details in the Details pane. You can also enable or disable data collection for the master server from this page. The details of the master server are shown on a separate page. The File List tab shows the files that have been backed up by the job and also their location. Click the server name (link) associated with the job in the Master Server column of the table. select Monitor > Jobs. The drop-down list is located at the top-right corner of the view. . Select Hierarchical View from the drop-down list. The Details pane is located at the bottom of the Monitor > Jobs view. To view information for the master server that is associated with a job 1 2 3 In the OpsCenter console. Attempts File List To view details for a single NetBackup job 1 2 3 4 In the OpsCenter console.344 Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup jobs Viewing the details for a single NetBackup job All the details that are associated with a job can be viewed from the Details pane. 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 this filter to view only active jobs Select this filter to view only queued jobs. select Monitor > Jobs. 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. 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. To view policy information for a job 1 2 3 4 In the OpsCenter console. Note: You can also view policy information from the List View. Clients Selection Filtering on NetBackup job state You can filter by using any of the following built-in job filters. 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 shows the files that are to be backed up. Select Hierarchical View from the drop-down list. Select this filter to view only Done jobs. Select this filter to view the jobs that have been suspended. Click the policy name (link) for the job in the Policy column of the table. The drop-down list is located at the top-right corner of the view.Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup jobs 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 that the drop-down list is located on the top-right corner of the page. Select this filter to view the jobs that are incomplete. To view details by job state 1 2 3 In the OpsCenter console. The drop-down list is located at the top-right corner of the view. select Monitor > Jobs. Note: These tasks are not visible if you log on with an Analyst or a Reporter role. Select Hierarchical View from the drop-down list. Before you perform these tasks. Note that the drop-down list is located on top of the table. you can also create your own custom filters. or restart a job. Controlling NetBackup jobs Use the following procedure to cancel. See “Using filters to customize your views” on page 62. To control a job 1 2 In the OpsCenter console. Select this filter to view the jobs that failed. suspend. Select a filter from the drop-down list. Incomplete Jobs Undefined Jobs Canceled Jobs Successful Jobs Partially Successful Jobs Failed Jobs In addition to using the built-in filters.346 Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup jobs 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 successful. manually refresh your Web browser to obtain an updated view for all jobs. Select this filter to view the jobs that are partially successful. select Monitor > Jobs. resume. Select this filter to view the jobs that have been canceled. Select this filter to view the jobs that are undefined. Select Hierarchical View from the drop-down list. Changing the job priority You can change the priority that is associated with a job.Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup jobs 347 3 4 Select a job from the table. By using the Reconcile option and selecting a reason. host cannot be reached etc. 6 Click OK. Click Cancel. from being billed. Note: The Reconcile option is disabled in the unlicensed version (Symantec OpsCenter). Resume. Note that you can select Un-Reconcile from the drop-down list to undo a reconciliation. You may select one or more jobs. Note that the drop-down list is located on the top-right corner of the page. In the Reconcile Jobs dialog box. You can select one or more jobs. 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. Restart. Before you perform this task. Select a job from the table. select Reconcile. Suspend. 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. Select Hierarchical View from the drop-down list. From the More drop-down list. The OpsCenter console may take some time to show the updated status once you perform these tasks. The Reconcile option is not visible if you log on with an Analyst or a Reporter role. select a reason for reconciling the job from the drop-down list. Reconciling NetBackup jobs You can use the Reconcile option to prevent the jobs that failed due to reasons like user terminating a job. . select Monitor > Jobs. Review the following points before changing the job priority: ■ Priority can be changed only for the jobs that are in Active or Queued state. 2 or higher versions. Click OK. Select an active job or a queued job from the table. Monitoring NetBackup services This view is displayed when you select Monitor > Services. In the Change Priority dialog box. You can also increment or decrement the job priority. select Monitor > Jobs. Note that the drop-down list is located on the top-right corner of the page. From the More drop-down list. The OpsCenter console may take some time to show the updated status once you perform this task. or Service Layer Service Type . 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. This column lists the name of the master server or media server where the service or daemon is present. Select Hierarchical View from the drop-down list. Note: The Change Job Priority option is not visible if you log on with an Analyst or a Reporter role. select Change Job Priority. To change the job priority 1 2 3 4 5 6 7 In the OpsCenter console. set the job priority to a particular value. Click Finish. This column lists the NetBackup service type. Device Manager. Example: Vault Manager. The table that appears in this view has the following columns: Name Host Name This column lists the name of the service. This view contains detailed information for services.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. you can also create your own custom filters. This status can be Stopped. See “Using filters to customize your views” on page 62. Select this filter to view details of all other services like Not Licensed. Select this filter to view details of running services.Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup services 349 Status The operational status of the service or daemon. or Other. This may be because the license for these services is either not installed or configured for a specific media or master server. Start Pending. You can perform the following tasks from this view: Use filters to view specific services See “Filtering on NetBackup service type” on page 349. These filters are available from the drop-down list which is present on top of the table. Not Licensed. Stop Pending. or Unknown. . Select this filter to view details of the services that have been stopped. Unknown (not recognized by OpsCenter). Running. The built-in filters are the following: All Services (default filter) Select this filter to view details of all the services. Restart Pending. Control NetBackup services Filtering on NetBackup service type You can filter by using any of the four built-in filters. Note: The status for some services may show as Stopped on the Monitor > Services page in the OpsCenter console. Failed. or Not Applicable (some services may not be applicable to earlier versions). See “Controlling NetBackup services” on page 350. Other can be Not Installed. Stopped Services Running Services Other Services In addition to using the built-in filters. Click Start. or Restart. You can select one or more services. Note: NetBackup service layer (nbsl) cannot be controlled from OpsCenter. Stop. Note: These tasks are not visible if you log on with an Analyst or a Reporter role. For instance. Note that the drop-down list is located on top of the table. Running. Note that these tasks are located on top of the table. Select a filter from the drop-down list. Stop. Select a service from the table. In the OpsCenter console. or Restart Pending appears in the Status column until the selected action completes. Monitoring NetBackup policies The Monitor > Policies view provides details of NetBackup policies. If you start or stop a service that has a dependency on another service. You can use the following views to see NetBackup policy information: . To control a service 1 2 3 4 Refresh your Web browser to obtain an updated state for all services. NetBackup ensures that any dependent services are also started or stopped.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. The OpsCenter console may take some time to show the updated status once you perform these tasks. one OpsCenter user stops a service while another user tries to start the same service. Controlling NetBackup services Under certain circumstances there may be issues among multiple OpsCenter users. select Monitor > Services. Note: You can select these views from the drop-down list. This view shows detailed information about NetBackup policies based on the current View pane selection. Name of the master server that is associated with the policy. 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. Click the link to view details about the policy. See “Using the List View for monitoring NetBackup policies” on page 351. Master Server Type Storage . Storage that is associated with the policy. the Policy type determines the type of clients that can be backed up by this policy. The table that appears in this view has the following columns: Name Name of the policy. Oracle. This view contains detailed information about policies.Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup policies 351 List View The List View is shown by default when you select Monitor > Policies. Vault etc. See “Controlling the scope of Monitor views” on page 324. See “Using the Summary View for monitoring policies” on page 357. The data that is shown in this view is based on the current View pane selection. This column is the policy type. Click the link to view details of master server. Using the List View for monitoring NetBackup policies This view is displayed when you select Monitor > Policies. These sections show specific policy information in a table as well as a pie chart. Sybase. Usually. Click the link to view details for storage. NBU-Catalog. The drop-down list is located at the top-right corner of the page. Example: DB2. Priority that you have defined for the policy. The total number of jobs that are associated with the policy. Zero means the lowest priority. Interval (in minutes) between two checkpoints in NetBackup. CheckPoint Interval Jobs/Policy Priority Active Not all of the available columns appear initially in this view. Click the link to view details of volume pool.352 Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup policies Volume Pool Volume pool that is associated with the policy. The following columns do not appear. This column determines whether the policy is Active or not. 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 . 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 “About using tables” on page 58. Active Policies . These filters are available from the drop-down list which is present on top of the table.Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup policies 353 ■ ■ Keyword Phrase Policy Domain Name See the online NetBackup Administration Console Help for a detailed description of these fields. 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. See “Managing a job policy” on page 356. Select this filter to view details of the policies that are active. 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 “Viewing the history for a single job policy ” on page 357. The built-in filters are the following: All Policies (default filter) Select this filter to view details of all NetBackup policies. Filtering on NetBackup policy type You can filter by using any of the seven built-in filters. More information about how to customize tables and view specific columns is available. See “Starting a manual backup” on page 356. 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. See “Using the Summary View for monitoring policies” on page 357. The Details pane is located at the bottom of the Monitor > Jobs view. you can also create your own custom filters. Clients . select Monitor > Policies. Select a filter from the drop-down list.354 Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup policies Inactive Policies Select this filter to view details of the policies that are inactive. Viewing details for a single NetBackup policy All the details that are associated with a policy can be viewed from the Details pane. SAP policies. You can also click the master server name (link) to get details of the master server. Select this filter to view details of all other policies like DB2 policies. Select this filter to view details of all policies that apply to Windows clients. Select this filter to view details of Standard policies. Schedules The Schedules tab displays details of the schedules that are associated with the policy. Use the following procedure to view details by type of policy. The Clients tab shows details of clients to be backed up by the policy. To view details by type of policy 1 2 In the OpsCenter console. Windows Policies Catalog Policies Standard Policies Other Policies In addition to using the built-in filters. See “Using filters to customize your views” on page 62. The Details pane has the following tabs: General The General tab of the Details pane displays all information available for the policy. OS2 policies etc. Select this filter to view details of catalog policies. It also includes contents of all the columns that can be viewed from the table. Note that the drop-down list is located on top of the table. To view details for a single NetBackup policy 1 2 3 In the OpsCenter console. select Monitor > Policies. select Monitor > Policies. 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. 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. The details of the volume pool are shown on a separate page. To view information for the volume pool that is associated with a policy 1 2 In the OpsCenter console. To view information for the master server that is associated with a policy 1 2 In the OpsCenter console. 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. The details of the master server are shown on a separate page. select Monitor > Policies. View the policy details in the Details pane. Click the server name (link) associated with the policy from the Master Server column of the table.Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup policies 355 Selections The Selections tab shows the files that have been backed up by the policy and also their location. You can also enable or disable data collection for the master server from this page. 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 storage that is associated with a policy 1 2 In the OpsCenter console. Click the volume pool name (link) associated with the policy from the Volume Pool column in the table. select Monitor > Policies. You can also view details for the master server from this page. . Click the name (link) for a policy from the Name column of the table. Click Activate or Deactivate. select Monitor > Policies. Select a policy from the table. NetBackup backs up all scheduled clients. manually refresh your Web browser to obtain an updated view of all policies. Starting a manual backup Use the following procedure to start a manual backup. or only select a schedule or a client. 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. If you do not select a schedule. manually refresh your Web browser to obtain an updated view of all policies. NetBackup uses the schedule with the highest retention level. The OpsCenter console may take some time to show the updated status once you perform these tasks. Before you perform this task. To activate or deactivate a policy 1 2 3 In the OpsCenter console. Select a job policy from the table. select Monitor > Policies. Before you perform these tasks. To start a manual backup 1 2 3 4 In the OpsCenter console. You can select only one policy and it must be an active policy. Note: This task is not visible if you log on with an Analyst or a Reporter role. Note that these options are located on top of the table.356 Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup policies Managing a job policy Use the following procedure to activate or deactivate a policy. The OpsCenter console may take some time to show the updated status once you perform this task. If you do not select a client. Click Manual Backup. . Note: These tasks are not visible if you log on with an Analyst or a Reporter role. The Summary View contains the different sections which display specific information about NetBackup policies. See “Controlling the scope of Monitor views” on page 324. To view the history for a policy 1 2 3 4 In the OpsCenter console. These sections show specific policy information in a table as well as a pie chart. 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. You must select two versions from the Retirement Date column to compare versions. You can use these links to drill down and access detailed information about NetBackup policies. Note that this option is located on top of the table. Data for the last 24 hours is shown by default. 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. select Monitor > Policies. The changes are highlighted in red color.Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup policies 357 Viewing the history for a single job policy Use the following procedure to view the history for a policy. 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. You can also view data for the last 48 or 72 hours. click the View Differences tab. The table and the pie charts include links to filtered detail views. To view only the differences between the versions. The drop-down list is located at the top-right corner of the page. Click View History. The Compare Policies tab displays the policy versions. Select a job policy from the table. Note: This task is not visible if you log on with an Analyst or a Reporter role. of Jobs section . Data for the last 24 hours is shown by default. The table also shows the data that is backed up for each policy. See “Controlling the scope of Monitor views” on page 324. of Jobs section lists seven policies which have the maximum number of jobs. Data for the last 24 hours is shown by default. you can quickly view the policies which have the maximum failed jobs associated with them. Note that the data that is backed up (shown in Volume (Bytes) column) is arranged in descending order in the table. Data for the last 24 hours is shown by default.358 Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup policies 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. See “Controlling the scope of Monitor views” on page 324. See “Controlling the scope of Monitor views” on page 324. Note: This section can also be viewed from Monitor > Overview. About Top 7 Policies by No. You can also view data for the last 48 or 72 hours. You can also view data for the last 48 or 72 hours. The table that is shown in the section lists the top five policies which have maximum data backed up. 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. of Jobs section The Top 7 Policies by No. you can . The table that is shown in the section lists the policies which have maximum number of jobs. 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 jobs for each policy. The table also shows the total number of failed jobs for each policy. you can quickly view the policies which have the maximum data backed up. Note that the failed jobs (shown in Total Number of Jobs column) are arranged in descending order in the table. From this section. From this section. You can also view data for the last 48 or 72 hours. From this section. 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. This data is based on the current View pane and timeframe selection. The drop-down list is located at the top-right corner of the page. Suspended Media Count etc. 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. Summary View The Summary View displays the volume pool available for each master server for the current View pane selection. See “Using the Hierarchical View by Volume Pool for monitoring media” on page 365. 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. Note: You can select these views from the drop-down list. This view shows detailed information about NetBackup media for the current View pane selection.Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup media 359 quickly view the policies which have the maximum number of jobs associated with them. It also shows other media details that are associated with the master server like Frozen Media Count. . See “Using the Hierarchical View by Volume Group for monitoring media” on page 366. Monitoring NetBackup media The Monitor > Media view provides details of NetBackup media. See “Using the List View for monitoring NetBackup media” on page 360. 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. The following columns do not appear. Zero (0) indicates unlimited mounts. Capacity that has been used. Current media status like Frozen. tl8 etc. Unique. Specifies the robot type of the robot to inventory. Active etc. 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. Type of media like 8mm. The number of times that the volume has been mounted. Slot in the robot that contains the volume. The most recent time NetBackup used the volume for backups. Name of the master server that is associated with the media. This view contains detailed information for media. Date when the images on the volume expire. logical identification number for the robot to inventory. Master Server Media Type Robot Type Robot Number Slot Mounts Time Assigned Max. Click the link to view details of master server. The date when the volume was assigned for use. 4mm etc. Click the link to view details about the media. The maximum number of mounts (or cleanings) that are allowed for the volume. Example: tl4. This data is based on the current View pane selection. Mounts Data Expiration Last Written Media Status Used Capacity Not all of the available columns appear initially in this view.360 Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup media Using the List View for monitoring NetBackup media This view is displayed when you select Monitor > Media. but can be added to your view by clicking the Table Settings icon: ■ Last Write Host . Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup media 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. . select Monitor > Media. See “Controlling media” on page 363. Click a drilldown link from the Media ID column. 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. you can also click the master server link to see details about the master server that is associated with the media. For example. 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. The Details pane is located at the bottom of the view. See “About using tables” on page 58. To view the details for a particular media 1 2 In the OpsCenter console. To view the details for a master server associated with a media 1 2 In the OpsCenter console.362 Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup media More information about how to customize tables and view specific columns is available. From the Details pane. you can create and apply a filter that displays full media . 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. Control media Viewing the details for NetBackup media All the details that are associated with a media can be viewed from the Details pane. 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. select Monitor > Media. View the media properties from the Details pane. The details of the master server are shown on a separate page. Click the server name (link) associated with the media in the Master Server column of the table. you can create your own custom filters. Select this filter to view details of the media that are suspended. Note that the drop-down list is located on top of the table. These filters are available from the drop-down list which is present on top of the table. Select a filter from the drop-down list. You can filter by using any of the built-in filters. select Monitor > Media. or unsuspend specific media. Select this filter to view details of cleaning media. unfreeze. .Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup media 363 only. Controlling media Use the following procedure to freeze. Select this filter to view details of media with Active status. Unassigned Media Frozen Media Full Media Suspended Media Other Media Active Media Cleaning Media In addition to the built-in filters. Select this filter to view details of all other media like Multi Retention Level media. BE media etc. The media is assigned if there is a date in the Time Assigned column. Use the following procedure to view details by type of 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 frozen. See “Using filters to customize your views” on page 62. The built-in filters are the following: All Media (default filter) Assigned Media Select this filter to view details of all media. Note that to perform these tasks the media must be assigned to NetBackup. suspend. Select this filter to view details of the media that are full. To view details by type of media 1 2 In the OpsCenter console. Select this filter to view details of the media that are unassigned. 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. Click Freeze. It also shows other media details that are associated with the master server like Frozen Media Count. Total number of all other media like Multi Retention Level media.364 Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup media Note: These tasks are not visible if you log on with an Analyst or a Reporter role. Frozen Media Count Suspended Media Count Full Media Count Active Media Count Other Media Count . or Unsuspend. The data that is shown in this view is based on the current View pane selection. BE media etc. Select a media ID from the table (use the check box). Note that these options are present on top of the table. The table that appears in this view displays the volume pool available for each master server. that are associated with the master server . Total number of active media associated with the master server. To perform media tasks 1 2 3 In the OpsCenter console. 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. Suspended Media Count etc. Total number of the full media associated with the master server. The drop-down list is located at the top-right corner of the page. select Monitor > Media. See “Controlling the scope of Monitor views” on page 324. Unfreeze. Suspend. The OpsCenter console may take some time to show the updated status once you perform these tasks. Total number of the suspended media that is associated with the master server. See “Controlling the scope of Monitor views” on page 324. Control media See “Controlling media” on page 366. The details for the volume pool are shown in the General tab at the bottom of this view. Click a volume pool (link) from the Media ID column. The sorting feature in this view applies only to media in the volume pool. Note that a volume pool has a + sign on the left side.Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup media 365 Available Media Count Total number of the media that are available for the master server. 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. The drop-down list is located at the top-right corner of the page. select Monitor > Media. Each volume pool that is shown in the Media ID column has a +sign before it. To view details for a volume pool 1 2 3 In the OpsCenter console. Select Hierarchical View by Volume Pool from the drop-down list. Viewing the details for volume pool Use the following procedure to view the details for a volume pool. You can expand a volume pool to see all media that are a part of this volume pool. View details for the media that are a part of See “Viewing the details for media” a specific volume pool on page 366. The Hierarchical View by Volume Pool shows details of all media and also groups media by volume pool. . The drop-down list is located at the top-right corner of the page. the current selected sort order is applied to media in the pool. The data that is shown in this view is based on the current View pane selection. 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. Note that the media are indented to the right-hand side in the Media ID column. When you expand a volume pool. Note that the media are indented to the right-hand side Click the media ID (link). The OpsCenter console may take some time to show the updated status once you perform these tasks. The drop-down list is located at the top-right corner of the page. select Monitor > Media. This shows the media that are a part of the volume pool. The drop-down . Unfreeze. Note that these tasks are present on top of the table. Expand a volume pool from the Media ID column. Note: These tasks are not visible if you log on with an Analyst or a Reporter role. Expand a volume pool from the Media ID column. The media is assigned if there is a date in the Time Assigned column. 4 Controlling media Use the following procedure to freeze. To perform media tasks 1 2 3 In the OpsCenter console. or unsuspend specific media. The drop-down list is located at the top-right corner of the page. Click Freeze. suspend. This shows the media that are a part of the volume pool. or Unsuspend. Select Hierarchical View by Volume Pool from the drop-down list. Select Hierarchical View by Volume Pool from the drop-down list. select Monitor > Media. Note that the media are indented to the right-hand side Select a media ID (use the check box). Suspend. unfreeze.366 Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup media Viewing the details for media Use the following procedure to view details for the media that are part of a specific volume pool. 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. Note that to perform these tasks the media must be assigned to NetBackup. To view the details for media 1 2 3 In the OpsCenter console. Details for the media are shown in the General tab at the bottom of the view. 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. Viewing the details for a volume group Use the following procedure to view the details for a specific volume group. The sorting feature in this view applies to media in the volume group. View details for the media that are part of a See “Viewing the details for media” specific volume group on page 367. Click a volume group (link) from the Media ID column. select Monitor > Media. 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. See “Controlling the scope of Monitor views” on page 324. Note that the media are indented to the right-hand side in the Media ID column. To view the details for media 1 2 In the OpsCenter console. Note that a volume group has a + sign on the left side. the current selected sort order is applied to media in that group. The drop-down list is located at the top-right corner of the page. To view details for a volume group 1 2 3 In the OpsCenter console. Control media See “Controlling media” on page 368. select Monitor > Media. The details for the volume group are shown in the General tab at the bottom of this view. The data that is shown in this view is based on the current View pane selection. The Hierarchical View by Volume Group shows details of all media and also groups media by volume group. The drop-down list is located at the top-right corner of the page.Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup media 367 list is located at the top-right corner of the page. Select Hierarchical View by Volume Group from the drop-down list. . When you expand a volume group. Viewing the details for media Use the following procedure to view details for media that are part of a specific volume group. Select Hierarchical View by Volume Group from the drop-down list. 4 Controlling media Use the following procedure to freeze. Suspend. Expand a volume group from the Media ID column. Note that the media are indented to the right-hand side Select a media ID (use the check box). 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. The OpsCenter console may take some time to show the updated status once you perform these tasks. This shows the media that are a part of the volume group. This view contains the following two tabs: . or Unsuspend. unfreeze. Click Freeze. Unfreeze. The drop-down list is located at the top-right corner of the page. Note that to perform these tasks the media must be assigned to NetBackup. Select Hierarchical View by Volume Group from the drop-down list. Note that these options are present on top of the table. suspend. The media is assigned if there is a date in the Time Assigned column. or unsuspend specific media. 4 5 Monitoring NetBackup devices This view is displayed when you select Monitor > Devices.368 Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup devices 3 Expand a volume group from the Media ID 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. 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. Type of drive like 4mm. Device Host Master Server Drive Type Robot Type Enabled . If multiple drive paths are configured. See “Using the Summary view to monitor drives” on page 373. This view contains detailed information for drives. The data that is shown in this view is based on the current View pane selection. The contents of the Drives tab are shown by default. this column contains Multiple. Contains Yes if the path is enabled. The name of the device host where the drive is connected. 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. Contains No if the path is not enabled. See “Controlling the scope of Monitor views” on page 324. 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. The type of robot that contains this drive. 8mm etc. See “Monitoring NetBackup disk pools” on page 374. Name of the master server that is associated with the drive. Using the List View for monitoring drives This view is displayed when you select Monitor > Devices > Drives.Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup devices 369 Drives This tab is shown by default when you select Monitor > Devices. but can be added to your view by clicking the Table Settings icon: ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ 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 . The following columns do not appear.370 Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup devices Not all of the available columns appear initially in this view. The List View is shown by default. See “Filtering on NetBackup drive category” on page 372. 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. 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. Click the drilldown link from the Drive Name column. . See “About using tables” on page 58. More information about how to customize tables and view specific columns is available. 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. From the General tab. The drive information can be viewed from the General and Paths tab of the Details pane. To view the details for a single drive 1 2 Select Monitor > Devices > Drives. See “Viewing the details for a master server associated with a drive” on page 371.Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup devices 371 ■ ■ ■ ■ Total Time User Name VM Host Write Enabled See the online NetBackup Administration Console Help for a detailed description of these fields. you can also click the master server link to see details about the master server that is associated with the drive. The Details pane is located at the bottom of the view. See “Controlling drives” on page 372. Controlling drives See the NetBackup Administrator's Guide. For mixed drives. . To view details by type of drives 1 2 In the OpsCenter console. Select this filter to view only those drives that are up. Use the following procedure to view details by type of drives. The following built-in filters are available: All Drives The All Drives filter is the default filter. Up Drives Down Drives Mixed Drives In addition to the built-in filters.372 Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup devices To view the details for a master server associated with a drive 1 2 Select Monitor > Devices > Drives. all drive paths are up. Select this filter to view mixed drives. For down drives. select Monitor > Devices > Drives. The List View is shown by default. Select a filter from the drop-down list. These filters are available from the drop-down list which is present on top of the table. See “Using filters to customize your views” on page 62. Volume I for information on drive states and how to control drives. The master server information can be viewed from a separate page. you can apply a filter that displays only those drives that are up. Select this filter to view all drives. you can create your own custom filters. some drive paths are up and some drive paths are down. Click the drilldown link from the Master Server column. 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. all drive paths are down. You can filter by using any of the built-in filters. Ensure that List View is selected in the drop-down list. Note that the drop-down list is located on top of the table. For example. For up drives. Select this filter to view only those drives that are down. or Reset. you also ensure that the drive is not involved in any tasks by other users. . Each color of the pie chart represents how drives are distributed in your environment as per the drive status. manually refresh your Web browser to obtain an updated view of all drives. select Monitor > Devices > Drives. When you refresh. Down. The OpsCenter console may take some time to show the updated status once you perform these tasks. Select a drive from the Drive Name column in the table. For example. 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. Click Up. This information is shown in a pie chart as well as a table. Pointing on the pie chart gives the number and percentage of drives with up or down status in your NetBackup environment.Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup devices 373 Before you perform these tasks. Note that these buttons are located on top of the drive details table. pointing on the green color in the pie chart shows that 5 drives or 100% drives in your environment are up. The List View is displayed by default. You can also view the color code summary in this section to know the colors that represent different exit status. 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. 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. Note: The Drive Summary by Status section can also be viewed from Monitor > Overview. ) When the capacity of the disk pool returns to the low water mark. ■ Monitoring NetBackup disk pools This view is displayed when you select Monitor > Devices > Disk Pools. The table that appears in this view shows the following information: Name Server Type Name of the disk pool The storage server type. do either of the following: ■ Click the number of drives (link) for a particular drive status from the table. select Monitor > Jobs. click the number for Up drives Or Click a colored section of the pie chart that corresponds to a particular drive status. (The default is 80%. The low water mark for the disk pool. To view drives by drive status 1 2 In the OpsCenter console. The data that is shown in this view is based on the current View pane selection. The estimated amount of disk space available for storage after file metadata overhead is taken into account. For example.374 Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup devices You can drill down from this section to see details of the drives that are up or down. NetBackup again assigns jobs to the storage unit. In the Drive Summary by Status section. The total raw. See “Controlling the scope of Monitor views” on page 324. unformatted size of the storage in the disk pool. Number of disk volumes in the disk pool. This view displays detailed information about the disk pools that are configured for use by NetBackup. Number of Volumes Used Capacity Raw Size Usable Size Low Watermark (%) . the server type depends on the vendor name. For example. click on the green section of the pie chart to view details for the drives that are up. For OpenStorage. The amount of storage space in use. Monitoring NetBackup hosts This view is displayed when you select Monitor > Hosts. To view the details for a single disk pool 1 2 In the OpsCenter console. The Details pane is located at the bottom of the view. More information about how to customize tables and view specific columns is available.Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup hosts 375 Not all of the available columns appear initially in this view. 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. The following columns do not appear. but can be added to your view by clicking the Table Settings icon: ■ ■ ■ ■ High Water Mark(%) Master Server State Imported See the online NetBackup Administration Console Help for a detailed description of these fields. From the General tab. 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 disk pool information can be viewed from the General and Disk Volume tab of the Details pane. you can also click the master server link to see details about the master server that is associated with the disk pool. See “About using tables” on page 58. This view contains the following subtabs: . Click the drilldown link from the Name column. select Monitor > Devices > Disk Pools. Backup Exec etc. 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. See “Monitoring NetBackup clients” on page 378. See “Controlling the scope of Monitor views” on page 324. The display name that you have chosen for the master server. See “Monitoring NetBackup media servers” on page 378. Operating system of the master server. Monitoring NetBackup master servers This view shows details of master servers. Media Server This view displays detailed information about NetBackup media servers based on the current View pane selection. This view displays detailed information about NetBackup master servers based on the current View pane selection. See “Monitoring NetBackup master servers” on page 376. The data that is shown in this view is based on the current View pane selection.376 Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup hosts Master Server This tab is shown by default when you select Monitor > Hosts. Display Name Operating System Product Last Contact . This does not necessarily represent the last time that OpsCenter collected information from the master server. Client This view displays detailed information about NetBackup clients based on the current View pane selection. The last time when OpsCenter successfully initiated contact with the master server. Back up product from where the data is being collected like PureDisk. Select this filter to view details of those master servers that are connected. Select this filter to view details of Linux servers. 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. HP-UX servers etc. Select this filter to view details of Windows servers. Use the following procedure to view details by type of master server. you can create your own custom filters.Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup hosts 377 State Shows the current state of the master server like Connected. See “Using filters to customize your views” on page 62. Select this filter to view details of those master servers that appear as not connected. you can apply a filter that displays Windows servers only. . For example. Connected Servers Partially Connected Servers Not Connected Servers Windows Servers Solaris Servers Linux Servers Other Servers In addition to the built-in filters. Select this filter to view details of Solaris servers. 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 all other servers like AIX servers. 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. Select this filter to view details of those master servers that are partially connected. Not Connected etc. These filters are available from the drop-down list which is present on top of the table. select Monitor > Hosts > Media Servers. 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. See “Controlling the scope of Monitor views” on page 324. Note that the drop-down list is located on top of the table. The table that appears in this view shows the following columns: . Select a filter from the drop-down list. See “Controlling the scope of Monitor views” on page 324. The data that is shown in this view is based on the current View pane selection. Click the drilldown link from the Master Server column. To view the details of a master server that is associated with a media server 1 2 In the OpsCenter console. The table that appears in this view shows the following columns: Name Master Server Name of the media server. select Monitor > Hosts > Master Server. Name of the master server that is associated with the media server. 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. Monitoring NetBackup clients This view shows details of NetBackup clients.378 Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup hosts To view details by type of master server 1 2 In the OpsCenter console. The data that is shown in this view is based on the current View pane selection. Monitoring NetBackup media servers This view shows details of media servers. Hardware of the client machine like PC. 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. Name of the master server that is associated with the client. 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. HP-UX etc. The data that is shown in this view is based on the current View pane and timeframe selection. To view the details for a single master server 1 2 In the OpsCenter console. You can also view data for the last 48 hours or 72 hours. See “Controlling the scope of Monitor views” on page 324. Data for the last 24 hours is shown by default. You can use the following views to see NetBackup alert information: . Monitoring NetBackup alerts The Monitor > Alerts view provides details of NetBackup alerts. Note: The OpsCenter console displays active alerts by default (these are the alerts that have not been cleared). Click the drilldown link in the Master Server column. select Monitor > Hosts > Client.Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup alerts 379 Client Name Master Server Name of the client that is to be backed up. Operating system on the client like Linux. See “Using the Summary View for monitoring NetBackup alerts” on page 386. This view also lets you view detailed information about all NetBackup alerts and also filter. 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. See “Controlling the scope of Monitor views” on page 324. This information is shown in a pie chart as well as a table. The List View shows active alerts by default. Name of the policy that is associated with the alert. See “Using the List View for monitoring NetBackup alerts” on page 380. 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. This view provides tools to view and filter alerts. Using the List View for monitoring NetBackup alerts The List view is displayed when you select Monitor > Alerts. You can also view data for the last 48 hours or 72 hours. Severity Alert Policy . respond to alerts. The severity of the alert. Summary View The Summary View only displays active alerts (these are the alerts that have not been cleared). The severity type helps you determine how quickly you want to respond. This view contains detailed information for alerts. and to track user responses to alerts.380 Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup alerts List View The List View is shown by default when you select Monitor > Alerts. The Summary View shows how active alerts are distributed in your environment as per the alert severity. 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. 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. Cleared etc. More information about how to customize tables and view specific columns is available. . date. Time. but can be added to your view by clicking the Table Settings icon. Current status of the alert like Active. date. and year when the alert was modified. See “Responding to alerts ” on page 383. See “Filtering by alert type” on page 382. Time. The Assignment State column does not appear. and year when the alert was raised.Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup alerts 381 Alert Condition Status The alert condition that is used for the alert. Name of the individual who last modified the alert. Name of the individual to whom the alert has been assigned. See “About using tables” on page 58. Assigned To Time Raised Last Update Time Updated by Not all of the available columns appear initially in this view. The Details pane is located at the bottom of the view. See “Viewing the details of the alert policy associated with an alert” on page 382. This does not include the alerts that have been cleared. Select this filter to only view the alerts whose severity is Informational. Click a drill-down link from the Alert ID column. In addition to the information that is shown in the table. Click the drill-down link from the Alert Policy column. select Monitor > Alerts. You can filter using any of the following nine built-in alert filters. the General tab also shows master server. Select this filter to only view the alerts whose severity is Warning. policy name. you can create and apply a filter that only displays the alerts that are acknowledged. The alert details are shown under General and Comments tabs of the Details pane. Active (default filter) Select this filter to view Active alerts. To view the details of alert policy associated with the alert 1 2 In the OpsCenter console. Select this filter to only view the alerts whose severity is Critical. Select this filter to only view the alerts whose severity is Major. job ID. The Comments tab shows comments on the alert (if any). Filtering by alert type Since the Monitor > Alerts view can include large numbers of alerts. These filters are available from the drop-down list which is present on top of the alert details table. You can use this filter to limit the types of alerts that appear. For example.382 Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup alerts To view the details of a single alert 1 2 In the OpsCenter console. and exit status information. the time these comments were given and the individual who last updated the alert. a filter is available. You can filter on various severity levels or status settings. 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. Critical Major Warning Informational . select Monitor > Alerts. which lets you focus on only the specific alerts that interest you. You can also clear or acknowledge an alert. 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. To view details by type of alert 1 2 In the OpsCenter console. This includes both active and cleared alerts. Use the following procedure to view details by type of alerts. OpsCenter allows multiple users to process or take action on an alert. select Monitor > Alerts. See “Using filters to customize your views” on page 62. For example. See “Responding to alerts ” on page 383. Cleared alerts do not appear in the alert view by default.Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup alerts 383 Unassigned Select this filter to only view the alerts that have not been assigned to anybody. More information on cleared alerts is available. Select this filter to only view the alerts that have been assigned to other OpsCenter users. Select a filter using the Filter drop-down list. Select this filter to only view the alerts that have been cleared. If you clear an alert. Assigned Acknowledged Cleared All Alerts Select this filter to view the details of all alerts. you inform other users who see the alert that action on the alert occurred. an OpsCenter user comments on an alert while another OpsCenter user tries to clear the same alert. For instance. Select this filter to only view the alerts that have been acknowledged by an OpsCenter user. assign or acknowledge). you can create your own custom filters. Note: Under certain circumstances there may be issues among multiple OpsCenter users. you cannot perform any further activity on the alert (for example. . When you acknowledge an alert. In addition to the built-in filters. select All Alerts to view details of both active and cleared alerts. 384 Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup alerts The OpsCenter console displays active alerts by default (these are the alerts that have not been cleared). Drive is Down) are cleared automatically when the condition is resolved. Some alerts (for example. 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 . 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. Select an alert from the table. select Monitor > Alerts. Select an alert from the table. See “Configuring data purge settings” on page 227. 3 Click More and then select Edit Policy from the drop-down list. . Click Acknowledge or Clear. Click Assign. To change the policy that is associated with an alert 1 2 In the OpsCenter console. You can add a comment as a reminder to yourself or for other users. Any purged data is deleted permanently. Select an alert from the table. select Monitor > Alerts. Click More and then select Clear from the drop-down list. You can assign an alert to a user for their action or information. select Monitor > Alerts. To acknowledge an alert 1 2 3 In the OpsCenter console. Click Add Comment. This option is useful if you see OpsCenter performance degrade when there is a high number of alerts in the OpsCenter database. Select an alert from the table. To add a comment for an alert 1 2 3 In the OpsCenter console. select Monitor > Alerts. To assign an alert to an individual 1 2 3 In the OpsCenter console. 4 5 Select a user to whom you want to assign the alert. Click OK. To clear an alert 1 2 3 In the OpsCenter console.Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup alerts 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. Select an alert from the table. select Monitor > Alerts. The Alert Policy Wizard is also used to create a policy. For example. do either of the following: ■ Click the number of alerts (link) for a particular alert severity from the table. You can drill down from this section to see details for alert categories. You can also view the color code summary in this section to know the colors that represent different severity. In the Alert Summary by Severity section. Pointing on the pie chart gives the number and percentage of alerts with a particular severity in your NetBackup environment. A pie chart with different colors represents the alert distribution by severity in this section. Select Summary View from the drop-down list. click on the red section of the pie chart to view details for critical alerts. 200 alerts. 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. See “Controlling the scope of Monitor views” on page 324. For example. Each color of the pie chart represents how alerts are distributed in your environment as per the alert severity. ■ . For example. Note: The Summary View only displays active alerts (these are the alerts that have not been cleared). click on the number that is shown for Critical alerts. select Monitor > Alerts. Or Click a colored section of the pie chart that corresponds to a particular alert severity. pointing on the green color in the pie chart shows that in the last 24 hours. Using the Summary View for monitoring NetBackup alerts The Summary View gives an overall summary of alerts by severity. This information is shown in a pie chart as well as a table. You can also view data for the last 48 hours or 72 hours. Note: The Alert Summary by Severity section can also be viewed from Monitor > Overview. Data for the last 24 hours is shown by default.386 Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup alerts See “Understanding alert counts in the Monitor view” on page 406. To view alerts by severity 1 2 3 In the OpsCenter console. or 17% alerts in your environment are critical. The drop-down list is located at the top-right corner of the page. Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup alerts 387 See “Understanding alert counts in the Monitor view” on page 406. . 388 Monitoring NetBackup using Symantec OpsCenter Monitoring NetBackup alerts . and displays it on demand. (Network. which also include OpsCenter alert policies. storage. and devices. stores it in a database. . or browser refresh settings can affect how quickly it appears). The OpsCenter server collects data from NetBackup master servers. NBSL sends a notification to OpsCenter. system delays. This data is collected mainly using notifications.Chapter 8 Managing NetBackup using Symantec OpsCenter This chapter includes the following topics: ■ ■ ■ ■ ■ 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. See “How OpsCenter collects data from NetBackup” on page 271. Most of the data is sent by NetBackup and appears almost instantaneously after it changes. For most operations and changes in NetBackup. Use the following procedure to view details of all master servers or specific master servers. ALL MASTER SERVERS. 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.e. 3 Managing alert policies This view is displayed when you select Manage > Alert Policies. More information about how to create views using Settings > Views is available. select ALL MASTER SERVERS from the drop-down list in the View pane. See “About OpsCenter views ” on page 307. you can also create your own views from Settings > Views or by using Java View Builder. 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. See the online Symantec OpsCenter Java View Builder Help to know how you can create views using Java View Builder. Click Apply Selection. you can create a view like Geography to view details about master servers in a particular region like Europe.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. . See “Controlling the scope of Manage views” on page 390. This view displays detailed information for OpsCenter alert policies for the current View pane selection. For example. In addition to using the default view i. Ensure that other master servers are unchecked. To view details of all master servers ◆ In the OpsCenter console. Deselect the checkbox next to ALL MASTER SERVERS and select specific master servers from the list of master servers. Example: Hung Job. This column lists the description for the alert policy. Explains how to filter and view the alert policies that are of interest to you. See “Filtering on type of alert policy” on page 393. This column lists the severity that is associated with the alert policy.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. Also explains the License Capacity alert policy. Explains how to view the details for an alert policy. See “Viewing the details for a single alert policy” on page 393. This column lists the alert condition that is used for the alert policy. High Frozen Media etc. Topic contents and description Description Explains the concept of alert policies. See “Creating (or changing) an alert policy” Explains how to create an alert policy using on page 394. This column lists the OpsCenter user who last modified the alert policy. Table 8-1 Topic See “About OpsCenter alert policies” on page 392. 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. Job Finalized. the Alert Policy Wizard. 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. Click the link to view details about the policy. . Enabled This column determines whether the alert policy is enabled or not. This column lists the severity of the email or trap that is sent when the alert is cleared. See “About alert conditions” on page 394. When a NetBackup system event triggers an alert (based on your alert policies). an OpsCenter user changes a policy while another user tries to remove the same policy. The License Capacity alert is generated for a capacity-based licensed NetBackup feature if the used capacity exceeds the licensed capacity. The OpsCenter console displays views to help you track and manage these alerts. the following occurs: ■ OpsCenter sends email or SNMP notices to any recipients that are configured in the policy. or deactivating an alert policy. major.392 Managing NetBackup using Symantec OpsCenter Managing alert policies Table 8-1 Topic Topic contents and description (continued) Description See “Managing an alert policy ” on page 407. See “Viewing the alerts associated with an alert policy” on page 407. OpsCenter helps you manage your NetBackup server network by generating alerts or sending email and trap notifications (or both). Alert policies are defined as informational. warning. Explains how you can view the alerts that are associated with an alert policy. activating. copying. For instance. When certain events or conditions occur in your environment. Alert policies help you manage your NetBackup environment by providing constant monitoring of your NetBackup systems. This alert is automatically cleared for the licensed feature if the used capacity is less than licensed capacity. deleting. This includes tasks like editing. or critical. About the License Capacity alert policy OpsCenter contains an internal predefined alert policy that is called the License Capacity Alert. About OpsCenter alert policies OpsCenter provides tools to create and manage alert policies and handle any resulting alerts that the policies generate. Under certain circumstances there may be issues among multiple OpsCenter users. If an alert is generated for a licensed feature and the alert has not been cleared for 7 days (i. which lets administrators focus on other job responsibilities. the used capacity is more than the licensed capacity . ■ You can specify email or SNMP notification in response to an alert. Explains the tasks that are available for managing a single alert policy. Administrators do not need to monitor a terminal continuously.e. See “Managing an alert policy ” on page 407.Managing NetBackup using Symantec OpsCenter Managing alert policies 393 for seven days after the alert is generated). The alert policy details are shown at the bottom of this view under the General tab. you can disable (or enable) the License Capacity alert policy if you do not want to receive these alerts. select Manage > Alert Policies. Click a drill-down link from the Name column.776 bytes. . All capacity values for this alert are calculated based on the definition that 1 terabyte=1. You can filter using any of the following three built-in filters. All Alert Policies Enabled Alert Policies Select this filter to view all alert policies.099.627. Note: The License Capacity alert is not generated for the capacity-based licenses for OpenStorage Disk option. Select this filter to view the alert policies that are disabled. Select this filter to view the alert policies that are enabled. 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. The General tab displays all the details that are shown in the table. It is internal to OpsCenter and cannot be modified. 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. To view the details of a single alert 1 2 In the OpsCenter console. See “Using filters to customize your views” on page 62. Disabled Alert Policies You can also create your own filters which let you focus on only the specific alert policies that interest you. a new alert is generated and the old alert is cleared automatically. These filters are available from the drop-down list which is present on top of the table. The License Capacity alert is an informational alert. and Virtual Tape option. PureDisk Storage option. However.511. and descriptions. You can receive these alerts by logging on to OpsCenter. you can create a policy to alert you when a job fails on a specific master server. You can create policies to automate responses to key events in your enterprise. OpsCenter periodically retrieves data from NetBackup based on notifications and a wait time (of up to 15 minutes). 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. Alert conditions can be divided into the following categories: Event-based alert conditions For these alert conditions. You can specify email and SNMP recipients while creating an alert policy. For these alert conditions. alert category. This time delay between the NetBackup Activity Monitor and the OpsCenter console can mean that many intermediate job states may be lost. For example. OpsCenter retrieves data from NetBackup based on a wait time (of up to 15 minutes). select Manage > Alert Policies. OpsCenter retrieves data from NetBackup based on notifications from NBSL. Select a filter from the drop-down list. You can monitor for frozen media and email the operator when the number of frozen media exceeds a threshold value.394 Managing NetBackup using Symantec OpsCenter Managing alert policies To view details by type of alert policy 1 2 In the OpsCenter console. You can then take corrective action. . Periodic alert conditions Table 8-2 lists the alert conditions. The alerts help you to anticipate and handle problems before they occur. 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. and also by email or SNMP traps. Periodic .Managing NetBackup using Symantec OpsCenter Managing alert policies 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. and the job completes (job duration = 33) before the fourth check. For example. since the job has executed for 26 minutes (11 + 15 minutes). but an alert is not raised. Alert condition Job finalized Events-based . an alert is raised at the third check.396 Managing NetBackup using Symantec OpsCenter Managing alert policies Table 8-2 Alert Type 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. This also includes the time for which a job is in a queued state. OpsCenter considers the start time of a job by default. While checking the Hung Job condition. a job may first be in a queued state before it becomes active. suppose a policy is created with a job threshold of 25 minutes. This is a total execution of 33 (5 + 15 + 13) minutes. Due to unavailability of resources. the policy is checked four times. If a job starts at 4 minutes after a first check. Depending upon when a job starts within a check cycle. an alert may not occur. In this case. you can configure OpsCenter to ignore the time for which a job is in a queued state. Note that the active start time of the first attempt is considered. 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. A job starts 10 minutes after a first check cycle and ends 13 minutes after the third check cycle is done. For Hung Job alert. The job was not yet started during the first check. The Hung Job condition is checked every 15 minutes. was running less than the threshold during the second (job duration = 5 minutes) and third checks (job duration = 20 minutes). A job may not always be in an active state after it starts. Low available media High suspended media Periodic High frozen media Periodic . Alert condition Media Frozen media Events-based An alert is generated when any of the selected media is frozen. An alert is generated when the percentage of suspended media exceeds the predefined threshold value. Exceeded max media mounts Media required for restore Events-based An alert is generated when a media exceeds the threshold number of mounts. Suspended media Events-based An alert is generated when any of the selected media is suspended. Periodic An alert is generated when the number of available media becomes less than the predefined threshold value. The restore operation may require a specific media which contains the specific image to be restored.Managing NetBackup using Symantec OpsCenter Managing alert policies 397 Table 8-2 Alert Type Alert conditions in OpsCenter (continued) Alert Category Description An alert is generated when a job of specified type. An alert is generated when the percentage of frozen media exceeds the predefined threshold value. Events-based An alert is generated when a restore operation requires media. of the specified policy or client ended in the specified status. you can specify the threshold value for a particular policy in percentage. This does not necessarily mean that if you do not receive this alert.398 Managing NetBackup using Symantec OpsCenter Managing alert policies Table 8-2 Alert Type Alert conditions in OpsCenter (continued) Alert Category Description An alert is generated when space available for catalogs becomes less than the threshold value or size. 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. bytes. terabytes (TB) or petabytes (PB) and generate alerts. an alert is generated for every master server within the group that satisfies this criteria. An alert is generated when no cleaning tapes are left. The alert is not generated if no catalog backup policy exists for a master server. For Catalog Space low condition. kilobytes (KB). megabytes (MB). the catalog backup was successful. Tape Mount Request Events-based An alert is generated on a media mount request. 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. gigabytes (GB). No Cleaning Tape Periodic Zero Cleaning Left Events-based An alert is generated when a cleaning tape has zero cleaning left. . 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. Events-based An alert is generated when the selected disk volume(s) is down. 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.Managing NetBackup using Symantec OpsCenter Managing alert policies 399 Table 8-2 Alert Type Disk. An alert is generated when the percentage of down drives exceeds the predefined threshold value. An alert is generated when a disk volume capacity is running below the threshold limit. High Down Drives Periodic . Alert conditions in OpsCenter (continued) Alert Category Description Alert condition Disk Pool Full Events-based An alert is generated when a disk pool(s) reaches the high water mark. Job Policy Change Events-based Symantec ThreatCon . this alert is automatically cleared when the communication is re-established. It does not necessarily mean that NetBackup backups are not working. 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. Lost Contact with Events-based An alert is generated when OpsCenter loses Media Server contact with the media server. For example. Master Server Unreachable Events-based An alert is generated when OpsCenter loses contact with the master server.400 Managing NetBackup using Symantec OpsCenter Managing alert policies Table 8-2 Alert Type 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. The Symantec ThreatCon alerts are cleared automatically when the ThreatCon level becomes less than the threshold level that you have specified. Service Stopped Events-based An alert is generated when the selected service stops on any of the selected servers in the selected view. This alert condition means that the connection between OpsCenter and the managed NetBackup master server is lost. By default. To create the alert policy. select the Symantec ThreatCon alert condition and then specify the threshold ThreatCon rating. Events-based An alert is generated when the Symantec ThreatCon level is equal to or more than the threshold level that you specify. If you select a particular job policy.Managing NetBackup using Symantec OpsCenter Managing alert policies 401 Table 8-2 Alert Type Alert conditions in OpsCenter (continued) Alert Category Description 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. 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 . If you do not select any job policy. only the selected job policy is monitored for change. 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. Click Add. The required information and the required number of screens vary depending on the alert condition you choose. To add an alert policy 1 2 In the OpsCenter console. . select Manage > Alert Policies. you can skip the optional screens. Note: The Alert Policy Wizard is also used when you edit an alert policy.402 Managing NetBackup using Symantec OpsCenter Managing alert policies 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 alert Policy Wizard appears. For some alert conditions. Select an alert condition from the list of alert conditions that are available. For example. all the master servers that are currently in the view or node are automatically selected. The name must be unique. You may also select only specific objects of a particular view or node to be checked for the alert condition. master servers that you may add later to this view or node will also be automatically selected and hence verified for the alert condition. For example. and in addition if you have selected a view or node that also contains server B. you can select the default view ALL MASTER SERVERS to be checked for the alert condition. Description Alert Condition Enter a description for the alert policy. This is a required field. Consider a scenario where there are two objects server A and server B in a particular view like ALL MASTER SERVERS.Managing NetBackup using Symantec OpsCenter Managing alert policies 403 3 Enter the following details in the Alert Policy Wizard : Name Enter a name for the alert policy. you may select only a specific master server(s) under the default view ALL MASTER SERVERS to be checked for the alert condition. In addition. server B will not be verified for the alert condition even though it is a part of the . You may also deselect a specific master server from a view by selecting the view and then deselecting the specific master server. 4 Specify attributes for the alert condition that you selected. for the Job Finalized condition). See “About alert conditions” on page 394. The attributes differ for each alert condition. 5 Select the view that should be verified for the alert condition. Click Next. In case. These attributes define and limit the alert. You can select a view and a node that contains a group of master servers and also specific objects. first deselect the view or node that contains the master server and then select the master server. you have selected the ALL MASTER SERVERS view and then specifically deselected server B . you may need to enter threshold attributes and other required or optional attributes. You may click Cancel to exit the Wizard at any stage. When you select a view like ALL MASTER SERVERS or a node that contains a group of master servers. To select a specific master server. Click Next to continue. For many alert conditions (for example. which is also part of another selected view. for the Job Finalized alert condition. Click Next to continue. 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. you can select the view as well as the specific policies and clients that should be checked for the alert. robot number. This is because you have specifically deselected server B from the ALL MASTER SERVER view. the deselection or exclusion is given a higher priority because of which the master server is not verified for the alert condition. These attributes are located under the applicable views or nodes for specific alert conditions. . on expanding the views and nodes from this page (wherever applicable). Note that you can also view and select additional attributes like policies. drive IDs etc. or view from this page. clients. you can select email or SNMP recipients (or both) to receive the alert notification. For this reason. This is because the Symantec ThreatCon alert condition does not depend on any views or master servers. When you specifically deselect a master server from a view. See “Adding email recipients” on page 405. client name. media server name. node. For example. media servers etc. it is recommended that you do not repeat a master server across groups. You can view the applicable attributes like policy name.404 Managing NetBackup using Symantec OpsCenter Managing alert policies selected view or node. You must select at least one object. 6 Optionally in the Email Recipients and Trap Recipients sections. the policy will be active once you create it. Cc. you can configure the severity for an email or trap that is sent when an alert is cleared. See “Managing an alert policy ” on page 407. select the specific recipients from the Recipient Name column and click To. As a result. Click Finish once the policy is successfully created. With Severity of email/trap sent for cleared alert option. When this Hung Job alert gets cleared. Note that you can configure the severity only for email or trap. Deselect the Activate Condition option if you want to deactivate the policy. do the following: ■ Select a severity level from the Alert Severity drop-down list. In the Severity section. The default severity level is Informational. Adding email recipients While creating an alert policy using the Alert Policy Wizard. or Bcc from the Email Recipients section. click To. You can now configure the severity for this email or trap from Critical to some other severity like “Informational” while creating the alert policy. go to the Actions screen. (If this alert occurs. Whenever this alert is cleared. In the Add Email Recipients dialog box. Cc. you receive Hung Job alert with Critical severity. This means that by default. you receive an email or trap that informs you that the alert has been cleared. the alert is displayed in the Monitor > Alerts view. On the Actions screen. ■ ■ 7 8 Click Save to save the alert policy. You can always activate or deactivate the policy later from the OpsCenter console. In OpsCenter. the alert is still displayed in the Monitor > Alerts view. For example. you may have created an alert policy for a Hung Job alert condition with a Critical severity. Click OK . an alert is raised with the severity specified in the alert policy.Managing NetBackup using Symantec OpsCenter Managing alert policies 405 See “Adding SNMP trap recipients” on page 406. Note that if you create an alert policy and do not define any recipients. 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.) Select an appropriate severity level from the Severity of email/trap sent for cleared alert drop-down list. The Activate Condition option is checked by default. or Bcc based on your requirements. This is the default behavior. This email or trap also has a Critical severity. Since this master server is present in the view. for example High Job Failure Rate apply across groups. For example. you select an alert condition of type of Frozen Media. 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. In the Add Trap Recipients dialog box. An alert is not generated for every master server that is a part of the group. In this case. the alert is listed when you select the specific server as well as the specific view from the View Pane. the alert is listed only when you select the server group on which alert policy is created (or a parent group of that group).406 Managing NetBackup using Symantec OpsCenter Managing alert policies Adding SNMP trap recipients While creating an alert policy using the Alert Policy Wizard. 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. But some types of alerts. On the Actions screen. Click OK Understanding alert counts in the Monitor view Alerts apply only to the object (master server) where the corresponding alert policy is created. go to the Actions screen. select the specific recipients from the Recipient Name column and click To. Therefore. When alerts are raised for that policy they are raised on the selected object. the alert is raised on the server since the server is the selected object. jobs from all of the master servers in the selected group are used to calculate the job failure rate. The alert can also be viewed if all the nodes or views that contain the master server are selected. click To from the Trap Recipients section. 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 . 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. If you create this type of alert policy for a single managed server. Click Delete. Click Edit. select Manage > Alert Policies. In the Copy Alert Policy dialog box. or deactivate an alert policy. enter the new name for the alert policy. select Manage > Alert Policies. . Select an alert policy from the Name column in the table.Managing NetBackup using Symantec OpsCenter Managing alert policies 407 Managing an alert policy Use the following procedure to edit. The copy of the alert policy is available in the alert policy details table where you can make changes to it. Click OK. Select an alert policy from the Name column in the table. select Manage > Alert Policies. activate. Select an alert policy from the Name column in the table. You can copy and use an alert policy on another managed master server. Select an alert policy from the Name column in the table. Viewing the alerts associated with an alert policy Use the following procedure to view the alerts that are associated with an alert policy. To delete an alert policy 1 2 3 In the OpsCenter console. Click More and then click Enable or Disable from the drop-down list. The Alert Policy Wizard is used to create or edit a policy. Click More and then click Copy from the drop-down list. To enable or disable an alert policy 1 2 3 In the OpsCenter console. To edit an alert policy 1 2 3 In the OpsCenter console. delete. copy. To copy an alert policy 1 2 3 4 5 In the OpsCenter console. select Manage > Alert Policies. See “Adding an alert policy” on page 402. The copy of the alert policy is available in the alert policy details table where you can make changes to it. 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. See “Controlling the scope of Manage views” on page 390. Using these subtabs you can view detailed information about NetBackup storage for the current View pane selection. See “Managing Storage Unit Groups” on page 410. Explains the capabilities that are available using the Manage > Storage > Storage Unit view. Explains the capabilities that are available using the Manage > Storage > Storage Unit Group view. Managing Storage Units This view is displayed when you select Manage > Storage > Storage Unit. 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 Lifecycle Policy view. and Storage Lifecycle Policy. This view shows the details for a storage unit for the current View pane selection. Storage Unit Group. See “Controlling the scope of Manage views” on page 390. Included in this view are subtabs for Storage Unit. Click More and then select View Alerts from the drop-down list. Managing NetBackup storage This view is displayed when you select Manage > Storage. select Manage > Alert Policies. Table 8-3 lists the topics on how to manage NetBackup storage. Select an alert policy from the Name column in the table. The table that appears in this view shows the following columns by default: . There is one row in the table for each storage unit for the current selection in the View pane. See “Managing storage lifecycle policy” on page 411. The following columns do not appear. . This column specifies the absolute path to a file system or a volume available for disk backups.Managing NetBackup using Symantec OpsCenter Managing NetBackup storage 409 Name This column lists the name of the storage unit. but can be added to your view by clicking the Table Settings icon: ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Storage Unit Type Capacity Free Space High Water Mark Max. This column specifies the type of robot (if any) that the storage unit contains. logical identification number for the robotic library. This happens only when a policy or schedule is explicitly configured to use this storage unit. This column lists the density of the storage unit. Concurrent Jobs Staging Low Water Mark Can Exist On Root NDMP Host Enable Block Sharing Transfer Throttle Master Server Last Seen Time Host . This column specifies a unique. This column specifies whether the storage unit is available exclusively on demand. Robot Type Robot Number Density On Demand Path Not all of the available columns appear initially in this view. Click the link to view details about the storage unit. This view shows the details for a storage unit group for the current View pane selection. This tab displays many of the available columns of the table. To view details for a single storage unit 1 2 In the OpsCenter console. Click a storage unit name (drilldown link) from the Name column in the table. See “Controlling the scope of Manage views” on page 390. 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. See “About using tables” on page 58. Viewing the details for a single storage unit Use the following procedure to view the details for a single storage unit. The table that appears in this view shows the following columns by default: . The storage unit details are shown at the bottom of this view under the General tab. More information about how to customize tables and view specific columns is available.410 Managing NetBackup using Symantec OpsCenter Managing NetBackup storage ■ ■ ■ ■ ■ ■ 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. Managing Storage Unit Groups This view is displayed when you select Manage > Storage > Storage Unit Group. select Manage > Storage > Storage Unit. The table contains one row for each storage unit group for the current selection in the View pane. This tab shows the details of the storage units that are a part of the storage unit group. Viewing the details for a single storage unit group Use the following procedure to view the details for a storage unit group. This column specifies the date and time when the storage unit group was last seen. Click the link to view details about the storage unit group. Storage Unit To view details for a single storage unit group 1 2 In the OpsCenter console. 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. 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. .Managing NetBackup using Symantec OpsCenter Managing NetBackup storage 411 Name This column lists the name of the storage unit group. Click the name of a storage unit group (drilldown link) from the Name column in the table. This view shows the storage lifecycle policy details for the current View pane selection. This column specifies the order that storage units are selected when they are included in a group. Managing storage lifecycle policy This view is displayed when you select Manage > Storage > Storage Lifecycle Policy. See “Controlling the scope of Manage views” on page 390. A storage lifecycle consists of one or more storage units. . select Manage > Storage > Storage Unit Group. The table contains one row for each Storage lifecycle policy for the current selection in the View pane. Click the link to view details about the storage lifecycle Policy.412 Managing NetBackup using Symantec OpsCenter Managing NetBackup storage The table that appears in this view shows the following columns by default: Name This column lists the name of the storage lifecycle policy. 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. Click the link to view more details about the master server. the data might be classified as gold or silver. This column lists the master server that is associated with the storage lifecycle Policy. This column lists the data classification that has been selected for the storage lifecycle. Viewing the details for a single storage lifecycle policy Use the following procedure to view the details for a single storage lifecycle Policy. the lowest priority possible. This column specifies the priority that a policy has for backup resources. Any policy with a priority greater than zero has priority over the default setting. For example. 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. The default for all policies is 0. Storage Destinations . . 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. which applies to all of the storage units in the lifecycle. This tab shows the details of the storage destinations that are a part of the storage lifecycle policy. The details are shown on a separate page. select Manage > Storage > Storage Lifecycle Policy. See “Managing robots” on page 418. Managing NetBackup devices Under certain circumstances there may be issues among multiple OpsCenter users managing devices. select Manage > Storage > Storage Lifecycle Policy. Topic contents and descriptions Description Explains the capabilities that are available using the Manage > Devices > Drive view. Table 8-4 Topic See “Managing drives” on page 414. Click the name of the master server (drilldown link) from the Master Server 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. . Click the name of a storage lifecycle policy (drilldown link) from the Name column in the table. Explains the capabilities that are available using the Manage > Devices > SAN Client view. Explains the capabilities that are available using the Manage > Devices > Robot view. See “Managing SAN clients” on page 422. To view the details for a master server associated with a storage lifecycle Policy 1 2 In the OpsCenter console. a user brings a drive down while another user tries to bring up the same drive. Explains the capabilities that are available using the Manage > Devices > Disk Pool view.Managing NetBackup using Symantec OpsCenter Managing NetBackup devices 413 To view the details for a storage lifecycle policy 1 2 In the OpsCenter console. Table 8-4 lists the topics on how to manage NetBackup devices. See “Managing disk pools” on page 420. using the Manage > Devices > FT Server view. For instance. See “Managing Fibre Transport (FT) servers” Explains the capabilities that are available on page 423. but can be added to your view by clicking the Table Settings icon: ■ ■ ■ ■ ■ ■ Serial Number Cleaning Frequency Shared Inquiry Information Volume Header Path ACS . This view shows details for the drives that are configured for use by NetBackup for the current View pane selection. Click the link to view details about the drive. The column contains 'No' if the path is not enabled. this column contains 'Multiple'. Robot Type This column specifies the type of robot that contains this drive. If the drive is configured as a shared drive (SSO). If multiple drive paths are configured. The table that appears in this view shows the following columns by default: Drive Name This column lists the configured name of the drive. This column specifies the type of drive. this column contains Multiple. The following columns do not appear. this column contains Multiple. This column lists the name of the device host (media server) where this drive is attached. See “Controlling the scope of Manage views” on page 390. If multiple drive paths are configured. Device Host Master Server Drive Type Not all of the available columns appear initially in this view. This column lists the name of the master server that is associated with the drive. Enabled This column contains 'Yes' if the path is enabled.414 Managing NetBackup using Symantec OpsCenter Managing NetBackup devices Managing drives This view is displayed when you select Manage > Devices > Drive. Example: hcart2. TLD. hcart3. Example: TL4. 4MM. . More information about how to customize tables and view specific columns is available.Managing NetBackup using Symantec OpsCenter Managing NetBackup devices 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. 416 Managing NetBackup using Symantec OpsCenter Managing NetBackup devices See “About using tables” on page 58. Details for the specific master server are shown on a separate page. See “Controlling drives” on page 417. You can filter by using any of the built-in filters. . 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. Detailed properties and status for the drive are shown at the bottom of the view under the General tab. 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. For example. To view the details for a single drive 1 2 In the OpsCenter console. These filters are available from the drop-down list which is present on top of the table. Click the name of the drive (drilldown link) from the Drive Name column in the table. select Manage > Devices > Drive. 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. To view the details for a master server 1 2 In the OpsCenter console. 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. you can apply a filter that displays only those drives that are up. Click the name of the drive (drilldown link) from the Master Server column in the table. See “Viewing the details for a master server associated with a drive” on page 416. See “Filtering on NetBackup drive category” on page 416. select Manage > Devices > Drive. The Paths tab shows the paths that were configured for the drive. Select this filter to view only those drives that are up. select Manage > Devices > Drive. To view details by type of drive 1 2 In the OpsCenter console. To control drives 1 2 3 In the OpsCenter console. some drive paths are up and some drive paths are down. See “Using filters to customize your views” on page 62. Select Up Drive. Note: These tasks are not visible if you log on with an Analyst or a Reporter role. For mixed drives. . Before you perform these tasks. you can also create your own custom filters. Select a drive from the Drive Name column in the table (use the check box). For up drives. Select this filter to view all drives. or Reset Drive. Controlling drives Use the following procedure to control drives. Select this filter to view only those drives that are down. manually refresh your Web browser to obtain an updated view of all drives. For down drives. all drive paths are up. Select a filter from the drop-down list. The OpsCenter console may take some time to show the updated status once you perform these tasks. select Manage > Devices > Drive. all drive paths are down. Note that the drop-down list is located on top of the table. Up Drives Down Drives Mixed Drives In addition to using the built-in filters. Down Drive. Select this filter to view mixed drives.Managing NetBackup using Symantec OpsCenter Managing NetBackup devices 417 The following built-in filters are available: All Drives All Drives is the default filter. Media Server This column lists the media server that is associated with the robot. The following columns do not appear. This column contains the robot serial number. The table that appears in this view shows the following columns by default: Robot Name This column contains the name of the robot. This view shows details for the robots that are configured for use by NetBackup for the current View pane selection. The robot name contains the type and number of the robot. This column lists the master server that is associated with the robot. Click the link to view details about the robot. but can be added to your view by clicking the Table Settings icon: ■ ■ ■ ■ ■ ■ Robot Type Robot Number Inquiry Information Last Seen Time Max Drive Max Slot . If the robot is controlled by a remote host. Device Host This column lists the name of the device host where this robot is attached. Serial Number Robot Control Host Master Server Not all of the available columns appear initially in this view. See “Controlling the scope of Manage views” on page 390. Click the link to view details about the master server. for example TLD(3). Click the link to view details about the media server.418 Managing NetBackup using Symantec OpsCenter Managing NetBackup devices Managing robots This view is displayed when you select Manage > Devices > Robot. this column contains the name of the host that controls the robot. See “Viewing the details for a media server associated with a robot” on page 420. 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. 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. Detailed properties for the robot are shown at the bottom of the view under the General tab.Managing NetBackup using Symantec OpsCenter Managing NetBackup devices 419 ■ ■ Remote ID VM Host See the online NetBackup Administration Console Help for a detailed description of these fields. Detailed properties for the master server are shown on a separate page. Click the name of the robot (drilldown link) from the Robot Name column in the table. The Paths tab shows the paths that were configured for the robot. Click the name of the master server (drilldown link) from the Master Server column in the table. See “Viewing the details for a master server associated with a robot” on page 419. More information about how to customize tables and view specific columns is available. To view the details for a master server associated with a robot 1 2 In the OpsCenter console. 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. select Manage > Devices > Robot. See “About using tables” on page 58. . To view the details for a single robot 1 2 In the OpsCenter console. select Manage > Devices > Robot. For OpenStorage. Detailed properties for the media server are shown on a separate page. To view the details for a media server associated with a robot 1 2 In the OpsCenter console. This column lists the estimated amount of disk space available for storage after file metadata overhead is taken into account. the server type depends on the vendor name.420 Managing NetBackup using Symantec OpsCenter Managing NetBackup devices 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. This column lists the amount of storage space in use. Managing disk pools This view is displayed when you select Manage > Devices > Disk Pool. select Manage > Devices > Robot. (The default is 80%. This view shows details for the disk pools that are configured for use by NetBackup in the current View pane selection. Click the name of the media server (drilldown link) from the Media Server column in the table. NetBackup again assigns jobs to the storage unit. See “Controlling the scope of Manage views” on page 390. Number of Volumes Used Capacity Raw Size Usable Size Low Watermark (%) . unformatted size of the storage in the disk pool. 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.) When the capacity of the disk pool returns to the low water mark. This column lists the total raw. This column lists the low water mark for the disk pool. This column lists the number of disk volumes in the disk pool. Click the master server link to view details about the master server that is associated with the disk pool. More information about how to customize tables and view specific columns is available. The following columns do not appear.Managing NetBackup using Symantec OpsCenter Managing NetBackup devices 421 Not all of the available columns appear initially in this view. but can be added to your view by clicking the Table Settings icon: ■ ■ ■ ■ High Water Mark (%) Master Server State Imported See the online NetBackup Administration Console Help for a detailed description of these fields. . 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. This tab shows details about the disk volumes 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. The details are shown at the bottom of this view. Viewing the details for a disk pool Use the following procedure to view the details for a disk pool. 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. Click the name of the disk pool (drilldown link) from the Name column in the table. select Manage > Devices > Disk Pool. This tab shows details about the storage servers that are associated with the disk pool. The number of minutes to wait for an FT media server for a backup operation. Usage Preference This column determines when to use the FT media server. disabled etc. 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. This view shows details for the SAN clients that are configured for use by NetBackup in the current View pane selection. View the details of a master server that is associated with a SAN client .422 Managing NetBackup using Symantec OpsCenter Managing NetBackup devices Managing SAN clients This view is displayed when you select Manage > Devices > SAN Client. 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. See “Viewing the details for a master server associated with a SAN client” on page 423. but can be added to your view by clicking the Table Settings icon. The number of minutes to wait for an FT media server for a restore operation. No. The different states can be active. See “Controlling the scope of Manage views” on page 390. This column lists the master server that is associated with the SAN client. This column lists the state of the FT device on the SAN client. The table that appears in this view shows the following columns by default: Name State This column lists the name of the SAN client. of FT Media Servers Backup Wait Period Restore Wait Period Master Server The Version column does not appear. The details are shown at the bottom of this view. Click the master server link to view details about the master server that is associated with the SAN client. This view shows details for the FT media servers that are configured for use by NetBackup for the current View pane selection. Click the name of the master server (drilldown link) from the Master Server column in the table. 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. 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. select Manage > Devices > SAN Client. To view the details for a master server associated with a SAN client 1 2 In the OpsCenter console. 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. This tab shows the FT target devices information for the selected SAN client. The table that appears in this view shows the following columns by default: . select Manage > Devices > SAN Client. FT device To view the details for a SAN client 1 2 In the OpsCenter console. See “Controlling the scope of Manage views” on page 390.Managing NetBackup using Symantec OpsCenter Managing NetBackup devices 423 Viewing the details for a SAN client Use the following procedure to view the details of a SAN client. Click the name of the SAN client (drilldown link) from the Name column in the table. Click the link to view details about the robot. FT device To view the details for an FT server 1 2 In the OpsCenter console. State This column lists the state of the FT media server. This column lists the master server that is associated with the 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. This tab shows the FT target devices information for the selected 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. 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. This column specifies the number of FT connections to allow to a media server. select Manage > Devices > FT 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. 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. See “Viewing the details for a master server associated with an FT server” on page 424.424 Managing NetBackup using Symantec OpsCenter Managing NetBackup devices Name This column contains the name of the FT media 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.Managing NetBackup using Symantec OpsCenter Managing NetBackup devices 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. . 426 Managing NetBackup using Symantec OpsCenter Managing NetBackup devices . making the operation easier to perform. .Chapter 9 Using Guided Recovery This chapter includes the following topics: ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ 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. because the operation does not create new file paths during the process.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. You do not need access to the original database to perform the cloning operation. 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.428 Using Guided Recovery Setting up for cloning ■ OpsCenter retrieves information for you such as databases and control files. ■ . Ensure that the user has write access to these paths. The cloning operation does not support offline tablespaces or raw tablespaces. shortening the Oracle clone setup time. 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. A validation process increases the rate of successfully completing the cloning operation. Ensure that the Oracle metadata parameter in the client's bp. Examples are Solaris 9 to Solaris 10 and Oracle 11 to Oracle 11. For example: # bpsetconfig -h myoracleclient ORACLE_METADATA=YES ■ Set up all destination file paths before you run 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. On Oracle 9 for Windows. ■ ■ ■ ■ ■ ■ Performing a cloning operation You need to log onto OpsCenter. perform an alternate restore procedure. you must change what the permissions of the backup image are to be at backup time. More information is available for the 'BKUP_IMAGE_PERM' variable. See “Select Source Database screen” on page 431. Along the top of the screen. and date. By default. More information is available on this screen. To use a different user or a different group for the clone. Shut down the source database to successfully complete the operation. The default condition is to display all databases that are backed up in the default date range. then click Go. use the drop-down menu to select the master server that you want to work with. click Manage > Oracle Cloning. To perform a cloning operation on an Oracle database in OpsCenter 1 2 When you log onto OpsCenter. . an error indicating the database cannot be mounted in exclusive mode appears. OpsCenter is the Web GUI that you use to perform all guided recovery operations. On Oracle 10G systems and later. See “Select Master Server screen” on page 431. the user must have write access to some directories such as DBS. If the NetBackup client service runs as the Oracle user.Using Guided Recovery Performing a cloning operation 429 ■ The cloning operation does not support Oracle Automatic Storage Management (ASM). If the cloning user shares an existing Oracle home. run the Oracle service under the Oracle user account. you can run under the local system. then that user needs to be granted the right to "Replace a process level token". Otherwise. Add the 'BKUP_IMAGE_PERM=ANY' to the send commands during the backup of the source database. the first screen that appears is the Monitor Overview screen. host name. to perform a cloning operation. it runs under the local system. Click Show Databases. On the Select Master Server screen. database version. 3 The Select Source Database screen lets you filter the list of databases by database name. platform. If the destination client is different than the source client. 7 The Define Destination Parameters screen appears.430 Using Guided Recovery Performing a cloning operation 4 The databases appear under the filtering part of the same screen. The default is the latest backup selected. Select the database on which you want to perform a cloning operation by clicking option at the left side of the desired database entry. See “Select Control File Backup screen” on page 431. See “Destination Parameters screen” on page 433. Then click Next>. More information is available about these links. and restore options. For operating system authentication. The Select Control File Backup screen shows a timeline view of the control file backups. The five tabs on this screen are used to change database attributes. data files. the destination paths of control files. The lower left corner of the screen lists three links. See “Destination host and login screen” on page 432. enter a user name. Then click Next>. password (Windows). If the icon represents multiple backups. Select the icon for the desired control file backup from the timeline view. . After you have changed the destination parameters. click Next>. Enter the destination host name in the text box that is provided or click Browse and select from a list of available hosts. you can hover over the icon to display all versions of the backup for that time periods. 5 6 The Destination Host and Login screen contains parameters for the destination of the clone to be created. A NetBackup client must be installed. A compatible version of Oracle must be installed. You can hover over the icon to display the control file details. and domain (Windows). Then click Next>. Note the following prerequisites concerning the destination host: ■ ■ ■ The platform type of the source and destination must be the same. Click on the icon of the control file backup you want to restore for the clone of the selected database. Additional information is available to verify that you have selected the correct control file. and redo logs. Multiple filter parameters can be used at the same time. If a directory path does not already exist. click Launch Cloning Process. Select Source Database screen When the Select Source Database screen first appears. Then select the dates from the calendar icons. Then click Show Databases to display the new filtered list of databases. 9 The Pre-clone Check screen lets you validate the database attributes and the file paths. so that the cloning operation does not overwrite the file. The upper portion of the screen shows parameters for filtering the list of databases. If the list is long. See “Selection summary screen” on page 433. See “Pre-clone check screen” on page 434. To validate. database version. The timeline displays an icon for each control file that is associated with the backed up database. host name. When you are satisfied with the summary information. When you are ready to launch the cloning operation. you can filter what databases appear by database name. the validation check flags the error. If a file already exists. When you first enter this screen. click Next>. select the NetBackup master server that collected the backup information to be used for the cloning operation. the latest backup control file is already selected . For example. A display appears that is similar to the NetBackup Activity Monitor. and date range. Select Master Server screen From the pulldown menu. 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 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.Using Guided Recovery Select Master Server screen 431 8 The SelectionSummary screen lets you scan the information you have entered on the previous screens. the validation check also flags the error. select Solaris from the Platform: pulldown menu. Links to the recovery sets and destination database attributes let you view and verify any changes you have made. click the underlined word here. to show only the Solaris databases that are backed up between 11/05/2009 and 11/12/2009. . To view all the instances of control files. This set is generated only for the files that are backed up as part of an incremental strategy. 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. etc. and its size. hover over the icon. View Datafiles Recovery Set shows the data file backups to be used for the restore process. For Windows. A compatible version of Oracle must be installed. For UNIX and Linux. the clone still completes successfully. the clone still completes successfully. user name. A popup lists each control file in table format. If multiple control files were backed up during a single timeline unit. Click option next to the desired control file. or years. you are asked for the domain name. Even though files that are backed up as part of a full backup do not appear in this list. you are asked only for the user name.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. It shows several items including the backup name and the type of media. the size of the backup. It also shows the backup and image information that is displayed for each data 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. A NetBackup client must be installed. If the image spans media. weeks. Even though files that are backed up as part of a full backup do not appear in this list. and password. . 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. Multiple control files may be displayed on the timeline. You can display the timeline in days. a different icon appears representing more than one control file (for example. ■ ■ Destination host and login screen The Select Destination Parameters screen lets you enter the destination host and the Oracle logon information. you may need to increase the scope of the timeline. if the database was backed up twice in an hour). To select from among these files. It shows how the database is laid out by listing each data file name. ■ View Database Schema shows the schema of the selected control file. months. only the first media is shown in the list. The data file recovery set is generated only for the files that are backed up as part of an incremental strategy. tablespace name. When you change a path. The database recovery set and the archived log recovery set. a highlight bar appears around the text window as a visual indicator that this path has changed. Data File Paths. a highlight bar appears around the text window as a visual indicator that this path has changed. This pane appears when you first enter the Database Attributes screen. This pane displays the source path and the destination path for all redo logs. All the changes that are made in this screen are temporary and are active only for the cloning session. Each attribute name has identical source and destination attributes. Control File Paths. and press the Apply option. Enter the path in the text window provided. You can also click Browse to navigate to the desired path. ■ . and database home. Redo Log Paths. database name. The Destination Parameters screen contains the following tabs: ■ Database Attributes. This pane displays the source path and the destination path for each control file. Note that the instance name is case sensitive while the database name is not case sensitive. You can change the destination attribute of the instance name. click Next>. Selection summary screen The following information appears on this screen: ■ ■ The selected master server and the source database attributes. ■ ■ ■ ■ When you are done making changes on this screen. then select the data files on which to apply it. You can change a control file destination path by clicking in the associated text window and entering the new path. This pane lets you change the destination path for one or more data files. You can type in a new destination path or click Browse to navigate to the desired path. Restore Options. When you change a path. The date and time of the selected control file backup. and the backup media type. All the information from the previous screen is saved in preparation for the cloning operation. The option that is displayed on this pane is Number of parallel streams for restore and recover.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. This pane displays restore options. You can modify these values if not appropriate for the destination database. from the <$ORACLE_HOME>/DBS directory. the validation check flags the error. shut down the database. ■ ■ If the cloning operation fails. use the dbca utility to delete the database. all previously used troubleshooting steps . do the following cleanup: ■ ■ ■ If the database is active. Job Details screen The Job Details screen is intended to reflect the NetBackup Activity Monitor. If a file already exists. so when the cloning process completes. You can also specify an email address. Post-clone operations Perform the following after the cloning operation has completed: ■ On UNIX systems. If a file path does not already exist. To validate. More information is available on the Activity Monitor. Remove all data files.ora. If the cloning operation fails. so that the cloning operation does not overwrite the file. Troubleshooting Guided Recovery Guided Recovery operations are in addition to the normal NetBackup for Oracle operations. and any other files associated with the SID being used. an email is sent to you that gives you the status of the cloning operation along with other pertinent information. dbca sometimes removes directories. See the NetBackup Administrator's Guide. click the underlined word here.ora. update the oratab file with the appropriate instance information. Pre-clone check screen The Pre-clone Check screen lets you validate the database attributes and the file paths.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. Remove init<SID>. Volume I. If problems are encountered. spfile<SID>. so verify before retrying the operation. the validation check also flags the error. New Client Framework ncforautil unified logs. OID 348. Database Agent Request Service From the NetBackup master server: ■ netbackup/logs/bprd legacy logs . 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. OID 362. On UNIX and Linux systems. Database Agent Request Service Troubleshooting files for Guided Recovery validation operations From the Oracle client host: ■ ■ ■ netbackup/logs/vnetd legacy logs ncf unified logs. New Client Framework NetBackup Client Services From the NetBackup master server: ■ ■ ■ netbackup/logs/vnetd legacy logs nbars unified logs. gather them at General=2. OID 362. OID 363. Verbose=5. New Client Framework ncfnbcs unified logs.Using Guided Recovery Troubleshooting Guided Recovery 435 and evidence are also relevant. On Windows systems. OID 360. OID 309. The following sections detail the additional key information that is required to troubleshoot Guided Recovery when it fails. OID 366. NetBackup Agent Request Service dars unified logs. 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. New Client Framework Oracle Utility ncforaclepi. gather all legacy logs at VERBOSE=5. and Database=5. OID 309. OID 363.) ncf unified logs. NetBackup Agent Request Service dars unified logs. All unified logs should be gathered at DebugLevel=6 and DiagnosticlLevel=6. OID 147 (The default location is <SYMCOpsCenterGUI>/logs) ■ Troubleshooting files for Guided Recovery cloning operations From the Oracle client host: ■ netbackup/logs/bphdb legacy logs (Includes the obk_stdout and obk_stderr logs.conf file opscenterserver unified logs. OID 362. NetBackup Agent Request Service dars unified logs. OID 147 (The default location is <SYMCOpsCenterGUI>/logs) ■ .conf file opscenterserver unified logs. NetBackup Agent Request Service dars unified logs. Database Agent Request Service From the Symantec OpsCenter server: ■ ■ <SYMCOpsCenterServer>/config/log. OID 363.) netbackup/logs/bpdbsbora legacy logs netbackup/logs/dbclient legacy logs (The directory must be writable by the Oracle users. OID 363.) A tar of netbackup/logs/user_ops (UNIX/Linux) A compress of NetBackup\Logs\user_ops (Windows) ■ ■ ■ ■ From the NetBackup master server: ■ ■ ■ ■ netbackup/logs/vnetd legacy logs netbackup/logs/bprd legacy logs nbars unified logs. OID 148 (The default location is <SYMCOpsCenterServer >/logs) opscentergui unified log. Database Agent Request Service From the Symantec OpsCenter server: ■ ■ <SYMCOpsCenterServer>/config/log.436 Using Guided Recovery Troubleshooting Guided Recovery ■ ■ nbars unified logs. OID 362. OID 148 (The default location is <SYMCOpsCenterServer >/logs) opscentergui unified log. 50/7.symantec.entsupport. .com/docs/295691 Note: The term MOM refers specifically to MOM 2005.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. 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. By detecting and alerting you on critical conditions. 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.Chapter 10 Understanding OpsCenter alert policies and alerts This chapter includes the following topics: ■ ■ 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. http://seer. entsupport. By detecting and alerting you on critical conditions.50/7. is a next-generation performance and event-monitoring product from Microsoft. this Management Pack helps prevent possible service outages.com/docs/295154 More information about OpsCenter alerts is available.symantec. The SCOM Management Pack for NetBackup and the documentation is available for download on the Symantec Support Web site. You can download and use the cc_trapd. a management solution that is shipped with NetBackup. cc_trapd. HP OpenView Network Node Manager (NNM) can help you to prevent possible service outages. formerly Microsoft Operations Manager (MOM). By using cc_trapd.50 or 7. NetBackup Operations Manager (OpsCenter). Note: The term HP OpenView Network Node Manager (NNM) in this section refers specifically to HP OpenView Network Node Manager 7.conf file to monitor and manage NetBackup alerts using HP OpenView Network Node Manager 7. By detecting and alerting you on critical conditions. NNM can be used for the centralized management of NetBackup alerts.conf file and configuring NNM and OpsCenter.51. NNM can receive the SNMP traps that have been configured in OpsCenter. 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). can generate and monitor NetBackup alerts.entsupport. See “About alert conditions” on page 394.50 or 7.symantec. .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). As a result.51.51 on Windows. Currently.conf file and the documentation is available for download on the support site.51 on Windows You can monitor and manage NetBackup alerts using HP OpenView Network Node Manager 7.50 or 7. http://seer. http://seer.com/docs/305573 About managing OpsCenter alerts using HP OpenView Network Node Manager 7. The versions of SNMP protocol are as follows: ■ SNMPv1 The SNMPv1 version is the first version of the protocol. A numeric tag or object identifier (OID) is used to distinguish each variable uniquely in the MIB and in SNMP messages. and protocol operations. and plan for network growth. ■ ■ ■ The original SNMPv2 (SNMPv2p) Community-based SNMPv2 (SNMPv2c) . such as point status or description. The manager and agent use a Management Information Base (MIB) and a relatively small set of commands to exchange information. The agent provides the interface between the manager and the physical devices being managed. This document replaces the earlier versions that were published as RFC 1067 and RFC 1098. The key enhancements to SNMPv2 are focused on the SMI. a database of management information. SNMP enables network administrators to manage network performance. SNMP is based on the manager and agent model consisting of a manager. being represented as leaves on the branches. find and solve network problems. SNMPv2c combines the Community-based approach of SNMPv1 with the protocol operation of SNMPv2 and omits all SNMPv2 security features. SNMPv2 It was created as an update of SNMPv1 adding several features. Security is based on community strings. About SNMP versions Many versions of SNMP are available. It is part of the Transmission Control Protocol/Internet Protocol (TCP/IP) protocol suite. and is defined by RFC 1157.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. managed objects. The manager provides the interface between the human network manager and the management system. and the network protocol. an agent. The MIB is organized in a tree structure with individual variables. About SNMP The Simple Network Management Protocol (SNMP) is an application layer protocol that facilitates the exchange of management information between network devices. manager-to-manager capability. Each object and characteristic has a unique object identifier (OID) that is associated with it.440 Understanding OpsCenter alert policies and alerts About using SNMP with OpsCenter ■ ■ ■ User-based SNMPv2 (SNMPv2u) SNMPv2 star (SNMPv2*). .6. 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. The MIB then serves as a data dictionary that is used to assemble and interpret SNMP messages. RFC 2261. RFC 2264. Each OpsCenter trap contains 2 standard object identifiers and 12 OpsCenter-specific object identifiers. Table 10-1 shows the name-value pairs that the traps pass to the SNMP manager. The security is based on that found in SNMPv2u and SNMPv2*. 1.1. RFC 1906. and support for proxies. RFC 2262. These OIDs form a tree. 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.1).2682.1. RFC 1905. About SNMP traps This section explains the content of an SNMP trap that is sent from Symantec OpsCenter.4. An object identifier (or OID) is a numeric string that is used to uniquely identify an object.3. SNMPv3 This version of the protocol is a combination of user-based security and the protocol operations and data types from SNMPv2p. RFC 2263. Each OID consists of the numbers that are separated by decimal points (for example. The MIB associates each OID with a readable label and various other parameters that are related to the object. ccTrapDefinitionsBranch.2.1.6.ccTrapVarsBran ch.1.3.12.ccTrapDefinitionsBranc Alert ID (Alert Status) Alert Summary h.alertDescription) This field is the alert description.0 This field is the unique identifier for this trap.1 This field is the alert recipient name.1.4.10.ccTrapVarsBranch.1.private.4.6. Example: 1173792454 1.1.3. Example: 1.6.ccTrapVarsBran ch.enterprises. and alert summary in the (iso.1.10.org.3.3.p following format: roducts.3.1.private.1.veritascc.1. (iso.1302.1.dod.3.dod.2.1302.enterprises.1302.p roducts.3.12.private.12. See Request for Comment (RFC) 1905 and 2576 for a detailed definition.3. alert status.1.3.1.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.10.4.veritascc.internet.1302.1.3.Understanding OpsCenter alert policies and alerts About using SNMP with OpsCenter 441 Table 10-1 Name 1.4.6.6.alertSummary) Example: 100 (Active) Job Completed with Exit Status 0 1.p Example: Nancy Nieters roducts. ccTrapDefinitionsBranch.internet.4 1.1. Example: Alert Raised on: Tue Mar 13 18:57:33 IST 2007 Job: {DAFB3333-B3ED-46F0-974A-948DC68967 70}.org.3.12.4.3 (iso.veritascc.1.6.alertRecipients) 1.1.2 This value specifies the alert ID.dod.1.0.1.6.enterprises.3.10. See RFC 1905 and RFC 2576 for a detailed definition.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 .internet.org. internet.12.private.ccTrapDefinition sBranch.1.5 (iso.1.12.1.ccHost) 1.internet.org.collectorNam e) 1.10.10.1.dod.3.10.objectType) 1.products.ccTrapVarsBranch.veritascc.4.enterprises.1302.dod.org. 1.6.1.212.v eritas.3.sampleData) This field is the IP address of the OpsCenter server.ccTrapVarsBran ch.6.6.products.4.veritascc.enterprises.10.internet.ccTrapDefinition sBranch.4.org.12.v eritas.3.internet. This field is blank and not used.sourceId) 1.veritascc.internet.4.442 Understanding OpsCenter alert policies and alerts About using SNMP with OpsCenter Table 10-1 Name OpsCenter trap binding (continued) Value This field is blank and not used.12.3.products.private.1302.enterprises.1.12.10.1302.enterprises.4 (iso.6 (iso.private.1.ccTrapDefinition sBranch.1.veritascc.1.12.org.p roducts.1.internet.12.policyName) 1.3.1.6.3.org.3. ccTrapDefinitionsBranch.org.private.1.v eritas.10.veritascc.1.1.6.1302.ccTrapDefinition sBranch.products.3.internet.ccObject) 1.ccTrapVarsBranch.1.9 (iso. (iso.ccTrapVarsBranch.1302.148 sBranch. This field is blank and not used.products.1.v eritas.ccTrapDefinition sBranch.3.ccTrapVarsBranch.3.8 (iso.4.dod.ccTrapDefinition Example: 10.ccTrapVarsBranch.1.enterprises.v eritas.veritascc.1.7 This field is blank and not used.org.dod.1. This field is blank and not used.products.enterprises.3.1.dod. This field is blank and not used.3.private.10 (iso.12.4.3.private.enterprises.1302.1.3.dod.4.1302.private.10.dod.veritascc.v eritas.6.6. .ccTrapVarsBranch. 1.10.10.1.ccTrapVarsBranch.1. 1.org.1. As per SNMPv2c trap definition.ccAlertSeveri ty) 1.10.dod.3.1.3.3.products.3.3.4.1.veritascc.1.dod.ccTrapDefinition Example: Informational sBranch. Most of the alert information in OpsCenter is sent as OID 1.12.12.ccTrapVarsBranch.12. Note: 1.1 to 1.1302.Understanding OpsCenter alert policies and alerts About using SNMP with OpsCenter 443 Table 10-1 Name OpsCenter trap binding (continued) Value This field shows the alert severity level.private.10.12.1.10.1302.12.products.12 are OpsCenter OIDs. The other OIDs starting from 1.1302.3.4.10.1.4.3.1.private.3.1.10.ccAlertTime) This field shows the time when the alert gets cleared.1.6.12. Table 10-2 shows the content that each OpsCenter alert sends as OID 1.6.4.6.3 represents iso.1302.org.1.6.1.3.12.1.org.alertDescription. However.1302.3. ccTrapDefinitionsBranch.v eritas.3.3.1. The first two OIDs listed in the table are standard SNMP OIDs.3.internet.4.enterprises.1302. the two standard OIDs are not defined in the OpsCenter MIB files.internet.1.3.1.ccTrapVarsBranch.1.11 (iso.1.veritascc.1.1302.6.3.3.v eritas.internet.4.12. All the 12 OpsCenter OIDs are defined in the OpsCenter MIB files.10.1.6.12 (iso.1. the two standard SNMP OIDs must be present as part of every trap.3.6.1.1302.dod. About alert description This section shows the content that is sent for each OpsCenter alert as OID 1.6.enterprises.4.3.3.veritascc.4.products.ccTrapDefinition Example: 13-10-2008 06:57:34 00 sBranch. .enterprises.private. 2009 5:00 PM Tree Type : Policy Nodes : Root Node % Failed Jobs: 100. 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.444 Understanding OpsCenter alert policies and alerts About using SNMP with OpsCenter Table 10-2 Alert type Job Alert conditions in OpsCenter Alert condition High job failure rate Description (Example) Alert Raised on: September 5.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 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 . 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 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.Understanding OpsCenter alert policies and alerts About using SNMP with OpsCenter 445 Table 10-2 Alert type Media Alert conditions in OpsCenter (continued) Alert condition Frozen media Description (Example) Alert Raised on: August 17. 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 . 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.446 Understanding OpsCenter alert policies and alerts About using SNMP with OpsCenter Table 10-2 Alert type Alert conditions in OpsCenter (continued) Alert condition Description (Example) Alert Raised on: December 4.0 Alert Policy: high percentage suspended media OpsCenter Server: localhost Severity: Warning High frozen media . 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:40 AM Tree Type : Policy Nodes: node1 Suspended Media: 1 % Suspended Media: 25. 2008 10:24 AM Tree Type : Policy Nodes: node1 Frozen media: 6 % Frozen Media: 66 Alert Policy: highfrozenmedia OpsCenter Server: winfor11 Severity: Warning .Understanding OpsCenter alert policies and alerts About using SNMP with OpsCenter 447 Table 10-2 Alert type Alert conditions in OpsCenter (continued) Alert condition Description (Example) Alert Raised on: December 8. 448 Understanding OpsCenter alert policies and alerts About using SNMP with OpsCenter Table 10-2 Alert type Catalog Alert conditions in OpsCenter (continued) Alert condition Catalog Space low Description (Example) Alert Raised on: December 8. 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. 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 3:44 PM Tree Type : Server Nodes : ccs-win-qe-1 Alert Policy: Catalog Backup Disabled OpsCenter Server: ccs-sol-qe-17 Severity: Warning . 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 .Understanding OpsCenter alert policies and alerts About using SNMP with OpsCenter 449 Table 10-2 Alert type Tape Alert conditions in OpsCenter (continued) Alert condition Mount Request Description (Example) Alert Raised on: September 7.Volume Group: 000_00000_TLD Request Time: February 4. 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: . 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 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.450 Understanding OpsCenter alert policies and alerts About using SNMP with OpsCenter Table 10-2 Alert type Disk Alert conditions in OpsCenter (continued) Alert condition Disk Pool Full Description (Example) Alert Raised on: August 20.VS640. 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 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.000 Drive Number: 1 Robot Number: 0 Alert Policy: drive down-individual alert Device Path: /dev/nst0 OpsCenter Server: localhost Severity: Critical . 2009 10:39 AM Media server : omlinux2 Drive Name: BNCHMARK. Understanding OpsCenter alert policies and alerts About using SNMP with OpsCenter 451 Table 10-2 Alert type Alert conditions in OpsCenter (continued) Alert condition High Down Drives Description (Example) Alert Raised on: August 12.0 Alert Policy: high down drives OpsCenter Server: localhost Severity: Major . 2009 3:13 PM Drive Number: 1 % Down Drive Paths: 100. 2009 12:20 AM Alert Policy: MasterServer Unreachable OpsCenter Server: CCSQAWINSP1 Severity: Major Lost Contact with Media Server Alert Raised on: February 18. 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 .452 Understanding OpsCenter alert policies and alerts About using SNMP with OpsCenter Table 10-2 Alert type Host Alert conditions in OpsCenter (continued) Alert condition Description (Example) Agent Server Agent Host Name : pinacolada Communication break Server Host Name : PINACOLADA Severity: Warning Master Server Unreachable Alert Raised on: October 23. 2008 1:33 PM Master server : pmsun22 Media server : pmsun22 Alert Policy: lcm OpsCenter Server: pmwin9 Service Stopped Alert Raised on: August 31. Use the following procedures to configure the SNMP trap community name on Windows and UNIX.bat stop 2 Navigate to INSTALL_PATH\OpsCenter\server\config directory and open the nm. stop all the OpsCenter server services.conf file after making the changes. Symantec OpsCenter uses a public community named Opscenter. 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.trapCommunity=OpsCenter Modify the value of nm.bat start . INSTALL_PATH\OpsCenter\server\bin\opsadmin. The file shows the following entry: nm. Public community implies a read-only access to SNMP traps. To configure the SNMP trap community name for OpsCenter traps on Windows 1 On the OpsCenter server host. 3 4 Save the nm.trapCommunity from OpsCenter to some other name.Understanding OpsCenter alert policies and alerts About using SNMP with OpsCenter 453 Table 10-2 Alert type Alert conditions in OpsCenter (continued) Alert condition Description (Example) Alert Raised on: September 7. Restart all OpsCenter services.conf file. the SNMP trap community name string is OpsCenter by default. INSTALL_PATH\OpsCenter\server\bin\opsadmin. stop all the OpsCenter services.trapCommunity from OpsCenter to some other name.sh start Configuring the SNMP version for sending SNMP traps The default SNMP version through which SNMP traps are sent in OpsCenter is SNMPv2c.conf file after making the changes. 3 4 Save the nm.bat start .454 Understanding OpsCenter alert policies and alerts About using SNMP with OpsCenter To configure the SNMP trap community name for OpsCenter traps on UNIX 1 On the OpsCenter server host.sh stop 2 Navigate to /opt/SYMCOpsCenterServer/config directory and open the nm. /opt/SYMCOpsCenterServer/bin/opsadmin.bat stop 2 Navigate to INSTALL_PATH\OpsCenter\server\config directory and open the nm. Restart all OpsCenter services: INSTALL_PATH\OpsCenter\server\bin\opsadmin. However.trapCommunity=OpsCenter Modify the value of nm.trapVersion from v2c to v1 (for SNMPv1) or v3 (for SNMPv3). The file shows the following entry: nm. 3 4 Save the nm. The following procedure explains how to configure the default SNMP version on Windows and UNIX.conf file. INSTALL_PATH\server\bin\opsadmin. /opt/SYMCOpsCenterServer/bin/opsadmin. stop all the OpsCenter services. The file shows the following entry: nm.conf file after making the changes. To configure the SNMP version for sending SNMP traps on Windows 1 On the OpsCenter server host. Restart all OpsCenter services. this SNMP version can be changed by modifying a configuration file.trapVersion=v2c Modify the value of nm.conf file. The file shows the following entry: nm.trapVersion from v2c to v1 (for SNMPv1) or v3 (for SNMPv3).conf file.notifyOnAutoClear parameter setting. Make sure that the am.autoClear Set this parameter to “true”. if you want to send notification after an alert was automatically cleared. you can customize a few alert settings using the am.conf <INSTALL_DIR>/SYMCOpsCenterServer/config/am.conf file after making the changes.Understanding OpsCenter alert policies and alerts About using SNMP with OpsCenter 455 To configure the SNMP version for sending SNMP traps on UNIX 1 On the OpsCenter server host. am. Set this parameter to “true”.notifyOnAutoClear .conf configuration file. Restart all OpsCenter services: /opt/SYMCOpsCenterServer/bin/opsadmin. am. stop all the OpsCenter services: /opt/SYMCOpsCenterServer/bin/opsadmin.sh start About customizing alert settings In OpsCenter.conf The alert configuration settings are described as follows: Note: By default all alert configuration parameters are set to “true”. if you want to automatically clear the alerts.trapVersion="v2c" Modify the value of nm. 4 5 Save the nm.autoClear parameter is set to “true”.sh stop 2 Navigate to the OpsCenter configuration directory: cd /opt/SYMCOpsCenterServer/config 3 Open the nm. to apply the change in the am. The am.conf configuration file is located at the following default location: Windows UNIX <INSTALL_DIR>\OpsCenter\server\config\am. . and SNMPv3. Is the OpsCenter SNMP community name configurable? Yes. OpsCenter assumes it as “false”. but the community name is maintained as "OpsCenter". Frequently asked SNMP questions What are the default versions of SNMP that are supported in OpsCenter? SNMPv1. What is SNMPv2c? How it is different from SNMPv2? See “About SNMP versions” on page 439. but still considered public because of certain attributes? Generally. if you want to send notifications after manually clearing alerts. SNMPv2c.notifyOnManualClear Set this parameter to “true”. How is the OpsCenter community related to the public community? Is the default community name of "OpsCenter" just a name for the community. Note: If you set an alert configuration parameter to a value other than “true” or “false”. See “Configuring the SNMP trap community name for OpsCenter” on page 453. Public community means read-only access to SNMP traps. The "OpsCenter" community used by OpsCenter is public.456 Understanding OpsCenter alert policies and alerts About using SNMP with OpsCenter am. the "default read community string" for the public community is "public". By using OpsCenter. multi-level views of backup and archive resources and customizable reports for tracking service usage and expenditures. . OpsCenter displays customizable.Chapter 11 Reporting in OpsCenter This chapter includes the following topics: ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ 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. you can track the effectiveness of data backup and archive operations by generating comprehensive business-level reports. line-of-business managers. IT architects. change the relative timeframe to four weeks (default timeframe is two weeks) and generate a new Client Count report. Use this section to view the saved reports or modify the parameters of the saved reports and generate new reports out of them. and capacity planning teams. . which you can select and publish on My Dashboard tab. The audiences include IT (Information Technology) managers. You can modify the default parameter values of a Report Template as required and generate a new report of that kind. application owners. You can see all clients that are backed up over the last four weeks. See “About Report Templates” on page 459. external customers. My Reports tab You can save generated reports for your future use. you can create multiple dashboard section containing a number of reports. IT finance teams. These saved reports are stored in the My Reports tab. external compliance auditors. You can also delete the saved reports using the My Reports tab. You can select multiple reports and add them in the same dashboard section. 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. Thus. See “Managing My Reports” on page 470. For example. My Dashboard tab Your saved reports are preserved in My Reports tab.458 Reporting in OpsCenter About OpsCenter reports It also contains tools for defining cost metrics and chargeback formulas or handling alerts. use the existing Backups > Client Count Report Template . See “Saving a report” on page 463. A wide range of audiences benefit from the reporting and the management capabilities of OpsCenter. See “Managing My Dashboard” on page 474. legal teams. the Report Templates home page is displayed. which guide you through the entire report creation procedure. when you click the Reports tab. . ■ ■ About Report Templates This section provides details of the Report Templates that are available in OpsCenter. or delete schedules using this tab. Manage Folders tab Use this tab to manage folders where you have saved your reports. See “Creating a custom report” on page 468. About report creation wizards OpsCenter provides wizards. click Create New Report. To create a report. Create a custom report. See “Managing folders” on page 476. Click any of the Report Template to view the respective report with default parameter values.Reporting in OpsCenter About OpsCenter reports 459 Schedules tab This tab contains all report schedules. See “About schedules” on page 478. The following report creation options are available: ■ Create a report using an existing Report Template . You can create. See “About Report Templates descriptions” on page 487. Create a report using SQL Query. 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 on the Reports tab. See “Creating a report using SQL query” on page 469. See “Creating a report using a Report Template ” on page 462. edit. Figure 11-1 shows various components of a report that is generated using a template. In the OpsCenter console. Time filters Report area Report views About custom reports Apart from generating reports using the existing templates. Use these time filters to view the data for a specific period of time. See “Creating a custom report” on page 468. or Ranking.460 Reporting in OpsCenter About OpsCenter reports 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. Distribution. . Use these options to change the current report view. export. OpsCenter reports are displayed here. Reports can be viewed in different forms or views. or email the generated report. Manage report options Manage report toolbar Use this toolbar to save. you can also create custom reports in OpsCenter by changing the report parameters as required. Historical. such as success rate. Report Templates are categorized as follows: Archive These reports are generated based on the archive data that is collected from Enterprise Vault. See “Creating a report using SQL query” on page 469. The chargeback reports provide details of the backup services expenditures. You can also run stored procedures using this feature. This category also includes recovery reports. Client reports Backups Catalog reports Chargeback reports .Reporting in OpsCenter Working with Report Templates 461 About custom SQL query In OpsCenter. you do not need to go through multiple parameter selections. you can create reports by directly running SQL queries. OpsCenter reports help you to have a good visibility into your data protection environment. 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. and protected bytes. Working with Report Templates Symantec OpsCenter provides a set of Report Templates or standard or canned reports that have parameters set to default values. Note: You can create only tabular reports bu running SQL queries. Using these reports you can track the backup and the recovery usage and the associated cost. You can use modify the default parameters and generate reports to view the required data. You can calculate the cost of data protection management and chargeback to customers and business units. Using this report creation option. These reports provide details about the catalogs. job status. The backup reports show the information that is related to backups. you can determine the number of jobs that are successful. These reports provide details about vault media. or partially successful and so on. NetBackup Storage Lifecycle Map These are the job status reports. you need to use the ‘status’ filter. To view this specific data. performance of clients on LAN or SAN. . By setting this filter to ‘Successful’ while generating the Job Count report. These reports provide media data. Creating a report using a Report Template This section provides the procedure to create a report using an existing Report Template . OpsCenter provides a number of filters that you can use to view the required data. About report filters There can be hundreds of records or thousands of MB of the data that you may not be concerned about. Job reports Media reports Policy reports Vault reports See “About Report Templates” on page 459. such as tape count or usage These reports show all details about the backup job policies in NetBackup. Using this report category. For example. you can view all jobs that were successful. For each report category there is a different set of filters. you want to view only those jobs that were successful.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. retain the default selection that is ‘Create a report using an existing Report Template ’ and click Next. click Reports. To view a report output of a template. On the Report Templates list. 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. These reports are saved in the OpsCenter database. On the Reports Template tab. ■ ■ Saving a report You can save a standard report. By clicking the Create New Report button. Emailing a report See “Emailing a report” on page 467. 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. You can use this set of filters to regenerate the reports with the current time selections. Modify display options and click Next. You cannot modify any of the report parameters. This saves the filters that you have selected while generating a report. expand a report category to see the Report Templates within it. which you can view using the My Reports tab. Select time frame and other filters as required and click Next. The report output is as per the default parameter values. Select the Report Template that you want to create a report from and click Next. . 3 4 On the Report Wizard. click Create New Report. select a template in the reports tree. Exporting a report See “Exporting a report” on page 466.Reporting in OpsCenter Managing reports 463 To create a report using an existing Report Template 1 2 In the OpsCenter console. click Reports > Standard Reports. . This opens the Save Report pop-up screen. In the report view area at the right-hand side. select the standard report that you want to save. To save a report 1 2 3 In the OpsCenter console. From the Reports tree.464 Reporting in OpsCenter Managing reports See “Managing My Reports” on page 470. click the Save As Report icon. In the Folder tree. Depending on the folder type that you have selected . Note: Report name should be unique across the report tree. select a folder where you want to save the report. Create New Click this button to create a new public or private folder.public or private . with respect to the current time. all other OpsCenter users can view it. Clicking on this button changes the view of Folder. Enter the folder name and click OK. Description Sharing Enter the short description for the report. enter the following information: Report name Enter the report name. if you have generated the Job Count standard report with the group by option selected as Policy Type. If you save the report in a public folder. Folder .the folders displayed for selection vary. Select this newly created folder where you want to save the report. Select Public or Private from this drop-down list. only you can view it. and report view as Historical. For example.Reporting in OpsCenter Managing reports 465 4 On the Save Report screen. the report is displayed with the saved filters and in the report view that were selected when the reports were saved. you can name this report as: NumberofJobsbyPolicies When you select this report on the Saved Reports tab. If you save the report in a private folder. This folder is made available in the Folder tree for selection. or Ranking. In the report view area at the right-hand side. CSV. select the standard report that you want to export. such as Adobe Reader CSV (comma-separated Use with spreadsheet programs. You can open the exported file using other applications. such as MS Excel. select the export options that you want to export the report with: File format. click the Export Report icon. 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. 5 Click OK. This opens the Export Report pop-up screen. such as Distribution. On the Export Report pop-up screen. My Reports tab is displayed with this report selected. The system displays the export options pertaining to the file format you have selected. click Reports > Standard Reports. values) . To export a report 1 2 3 4 In the OpsCenter console. After a successful save. Click OK. you can preserve report data in files or print the data. 5 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. or XML and content or report view. Exporting a report Using OpsCenter.466 Reporting in OpsCenter Managing reports Overwrite if file exists Select this check box if you want to overwrite the existing report with the same name in the same folder. Select those options and export the report. a confirmation message is displayed before you overwrite the existing report. such as PDF. From the Reports tree. such as a spreadsheet program or a text editor. See “ About file formats available in OpsCenter” on page 466. Historical. and Bcc text boxes. See “Adding email recipients” on page 467. you can add existing email recipients. Adding email recipients This section provides information on how to add email recipients to whom you want to send emails. click the Email Report icon. You can email a report in a number of different file formats. This opens the Email Report pop-up screen. 5 6 7 8 Enter the subject of the email.Reporting in OpsCenter Managing reports 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. such as PDF. to which you want to send emails. they are automatically added to the database. See “ About file formats available in OpsCenter” on page 466. Historical. click Reports > Standard Reports. Enter email IDs in To. To email a report 1 2 3 4 In the OpsCenter console. you can email report data to the selected recipients. Cc. select the email options: File format. select the standard report that you want to email. Click OK. Enter the message that may be a short description regarding the report data that you want to email. On the Email Report pop-up screen. Alternatively. or XML and content or report view. or Ranking. From the Reports tree. If these email IDs do not already exist. such as Distribution. CSV. In the report view area at the right-hand side. . Select a range of value. 2 Click OK. Creating a custom report This section provides the procedure to create a custom report.. About report conditions In the Conditions section of the Custom Report Wizard. specify conditions for notification. ■ When the specified condition is met. click Create New Report. click Reports. select the check boxes in front of the email recipients to whom you want to send emails. Cc. To create a custom report 1 2 3 4 5 6 In the OpsCenter console. You can set a . depending on where you want to add the selected recipients. This feature is accessible only to the Symantec OpsCenter Analytics users. select the ‘Create a custom report’ option and click Next. Select the report category and view type and click Next. Select low threshold and high threshold values... such as Success Rate or Total Backup Job Size.. 7 Click Next. for example an unusually high percentage of backup job failures or an unusually low quantity of data being backed up. Select time frame and other filters as required and click Next. On the Report Wizard. Add conditions as follows: ■ ■ ■ Select a report column. Select an operator. or Bcc. Conditions represent potential problems. a notification is sent to the concerned person. On the Report Templates tab. Each exception condition is defined by assigning threshold values for a particular metric. Click Add. See “About report conditions” on page 468. click To..468 Reporting in OpsCenter Creating a custom report To add email recipients 1 On the Add Email Recipients screen. This option is disabled in the unlicensed OpsCenter version. On the Report Templates tab.Reporting in OpsCenter Creating a report using SQL query 469 low threshold. enter the following SQL query: select * from domain_masterserver 5 Click Next. On the SQL Query page. to view all NetBackup master servers that are monitored and managed by OpsCenter. ■ 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. Caution: Make sure about the impact that the entered SQL query has on the OpsCenter database before running it. Select a condition while generating a custom report. click Reports. See “About user access rights” on page 235. You can view all master server details that are stored in the ‘domain_masterserver’ database table. On the Report Wizard. Total Backup Job Size: Low threshold 500 GB. enter an SQL query to view the required data. 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. or both. an alert is triggered or an email notification is sent. For example. To create a report using SQL query 1 2 3 4 In the OpsCenter console. . select the ‘ Create a report using SQL Query’ option and click Next. click Create New Report. high threshold 1000 GB The condition is met whenever the total size of backed-up data falls outside the range of 500-1000 GB. a high threshold. Note: OpsCenter Analyst and Reporter do not have access to the custom SQL query option. so that when a condition is true. See “Creating a custom report” on page 468. Click Delete. To delete a saved report 1 2 3 4 In the OpsCenter console. Creating a report using My Reports tab This section provides the procedure to create a report using My Reports tab. You can create a report in any of the following ways: See “Creating a report using a Report Template ” on page 462. click Create New Report. click Reports > My Reports. from the reports list. from the reports list. On the My Reports tab. Select the check box in front of the report name. To create a report 1 2 In the OpsCenter console. On the My Reports tab. click Reports > My Reports. click Reports > My Reports. Use this section to view the saved reports or modify the parameters of the saved reports and generate new reports out of them. See “Creating a report using SQL query” on page 469. You can also delete the saved reports using the My Reports tab. Select the saved report that you want to view. To view a saved report 1 2 In the OpsCenter console. Deleting a saved report This section provides the procedure to delete a saved report. Viewing a saved report You can view the saved reports using the My Reports tab. These saved reports are stored in the My Reports tab.470 Reporting in OpsCenter Managing My Reports Managing My Reports You can save generated reports for your future use. expand a report folder to view the reports that are saved within it. expand a report folder to view the reports that are saved within it. On the My Reports tab. . Reporting in OpsCenter Managing My Reports 471 Editing a saved report You can edit a saved report. You can edit the report details. expand a report folder to view the reports that are saved within it. click the Save As Report icon. Select the saved report that you want to edit. 3 . In the report view area at the right-hand side. To edit a saved report 1 2 In the OpsCenter console. This opens the Save Report pop-up screen. such as the report name or the folder where you want to save the edited report. On the My Reports tab. from the reports list. click Reports > My Reports. If you do not select any folder. You need to either overwrite the existing report or save it with a different name. Folder 5 Click OK. the report is saved on the root. Clicking on this button changes the view of Folder. all other OpsCenter users can view it. the system displays an alert message. When you select this report on the Saved Reports tab.472 Reporting in OpsCenter Managing My Reports 4 On the Save Report screen. Overwrite if file exists Select this check box if you want to overwrite the existing report with the new changes. with respect to the current time. only you can view it. Depending on the folder type that you have selected .the folders displayed for selection vary. In the Folder tree. Create New Click this button to create a new public or private folder.public or private . Enter the folder name and click OK. select a folder where you want to save the report. If you save the report in a private folder. Description Sharing Enter short description for the report. Select this newly created folder where you want to save the report. Select Public or Private from this drop-down list. . If you do not select this check box and attempt to save the report with the existing report name. enter the following information: Report name Enter a new name for the report. This folder is made available in the Folder tree for selection. If you save the report in a public folder. the report is displayed with the saved filters and in the report view that were selected when you saved the reports. or Ranking. you can preserve saved report data in files or print the data. Select the saved report that you want to export. you can email the saved report data to the selected recipients. from the reports list. On the Export Report pop-up screen. You can email a report in a number of different file formats. This opens the Export Report pop-up screen. such as Adobe Reader CSV (comma-separated Use with spreadsheet programs. click Reports > My Reports. In the report view area at the right-hand side. Select those options and export the saved report. The system displays the export options pertaining to the file format you have selected. or XML and content or report view. such as PDF. such as a spreadsheet program or a text editor. click the Export Report icon. CSV. On the My Reports tab. such as MS Excel. See “ About file formats available in OpsCenter” on page 466.Reporting in OpsCenter Managing My Reports 473 Export a saved report Using OpsCenter. Select file format. such as Distribution. Historical. expand a report folder to view the reports that are saved within it. To export a saved report 1 2 In the OpsCenter console. select the export options that you want to export the report with. Click OK. 3 4 5 Email a saved report Using OpsCenter. You can open the exported file using other applications. 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 . You can email the report in the following file formats: PDF (Portable Document Format) Can be viewed using a PDF reader. You can add only 10 reports in a dashboard. . and Bcc text boxes. Cc. such as Distribution. See “Deleting a dashboard section” on page 475. See “Adding reports to a dashboard” on page 474. to which you want to send emails.474 Reporting in OpsCenter Managing My Dashboard To email a report 1 2 In the OpsCenter console. Enter the subject of the email. expand a report folder to view the reports that are saved within it. See “Refreshing My Dashboard” on page 476. which you can select and publish on My Dashboard tab. On the Email Report pop-up screen. Adding reports to a dashboard This section provides the procedure to add reports to a dashboard. Historical. See “Modifying a dashboard section” on page 475. click Reports > Saved Reports. This opens the Email Report pop-up screen. you can create multiple dashboard sections containing a number of reports. See “Emailing dashboard sections” on page 476. Thus. from the reports list. Enter email IDs in To. On the My Reports tab. CSV. click the Email Report icon. 3 4 5 6 7 8 Managing My Dashboard Your saved reports are preserved in My Reports tab. Enter the message that may be a short description regarding the report data that you want to email. You can select multiple reports and add them in the same dashboard section. In the report view area at the right-hand side. such as PDF. or Ranking. Click OK. select the email options: File format. or XML and content or report view. Select the saved report that you want to email. Click Edit. click Reports > My Dashboard. Click OK. On the Delete Dashboard Section pop-up screen. select the dashboard section from the drop-down list. which you want to publish on or remove from this dashboard section.Reporting in OpsCenter Managing My Dashboard 475 To add reports to a dashboard 1 2 3 4 5 6 In the OpsCenter console. which you want to publish on the dashboard. To delete a dashboard section 1 2 3 4 In the OpsCenter console. On the Edit Dashboard Section pop-up screen. To modify a dashboard 1 2 3 4 5 6 7 In the OpsCenter console. Select the check boxes in front of the report names. Click Add. Deleting a dashboard section This section provides the procedure to delete a dashboard section. Click OK. Click OK. click Reports > My Dashboard. 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. Click Delete. Select or clear the check boxes in front of the report names. . Expand the Private or Public Reports folder to view existing reports. click Reports > My Dashboard. Modifying a dashboard section This section provides the procedure to modify dashboard section. On the Add Dashboard Section pop-up screen. that you want to delete. enter the section name. . You can also select reports in a particular folder and delete them using this tab. To email a dashboard 1 2 3 4 In the OpsCenter console. which are added into the database.. Click OK. To refresh My Dashboard 1 2 In the OpsCenter console. and Bcc. edit names of the existing folders. Managing folders OpsCenter provides a way to manage folders where you have saved your reports. Cc. click Reports > My Dashboard. Click the Refresh icon. 5 6 Enter the email subject and message.476 Reporting in OpsCenter Managing folders Emailing dashboard sections You can email your dashboards. Using the Manage Folders tab in the Reports section. you can add new report folders. Select email recipients from the To. On the Email Dashboard pop-up screen. See “Deleting folders” on page 478. select the format in which you want to send the email. click Reports > My Dashboard. See “Deleting reports from a folder ” on page 478. enter new email recipients.. . Alternatively. or delete them. Refreshing My Dashboard This section provides the procedure to refresh My Dashboard. as appropriate.. See “Adding a folder” on page 476. See “Editing a folder” on page 477.. They can be both private or public reports. Adding a folder This section provides a procedure to add a report folder. Click the Email Dashboard icon. Click Edit.Reporting in OpsCenter Managing folders 477 To add a folder 1 2 In the OpsCenter console. 4 5 Enter the folder name. 3 Click Add. select a check box in front of a private or public folder node in which you want to create a new folder. This folder is added in the selected node. 4 5 Edit the folder name. Make sure that you have selected only one folder. To edit a folder 1 2 3 In the OpsCenter console. Click OK. click Reports > Manage Folders. On the Reports tree. If multiple folders are selected. On the Reports tree. Click OK. This displays the Edit folder name pop-up window. click Reports > Manage Folders. . If multiple folders are selected. select a check box in front of a private or public folder that you want to edit. the Edit button is disabled. This displays the Create new folder pop-up window. the Add button is disabled. Make sure that you have selected only one folder. Editing a folder This section provides a procedure to edit a report folder. This is a suggested flow of steps. select the check boxes in front of the reports that you want to delete. select a check boxes in front of private or public folders that you want to delete. See “Creating a report schedule” on page 481. click Reports > Manage Folders. you can email or export reports at a scheduled time. If you delete a report folder. select a private or public folder from which you want to delete the reports. To delete reports from a folder 1 2 In the OpsCenter console.478 Reporting in OpsCenter About schedules Deleting folders This section provides a procedure to delete a report folder. From the list of reports. On the Reports tree. OpsCenter provides a wizard to create a report schedule. Each report schedule is associated with a time schedule at which it emails or sends the specified reports. . To delete folders 1 2 3 In the OpsCenter console. This displays a list of reports that are saved in the selected folder. The following table describes the steps that you need to carry out to email or export a report on a specific schedule. Deleting reports from a folder This section provides a procedure to delete reports that are saved in a public or private folder. See “Managing time schedules” on page 485. click Reports > Manage Folders. Click Delete. 3 4 About schedules Using report schedules. Click Delete. all reports that are saved in that folder are deleted. On the Reports tree. at the right-hand side of the page. 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. Managing report schedules NetBackup OpsCenter provides you a way with which you can export or email a report on a specific schedule. This section describes how to create and manage report schedules. ■ Select the reports that you want to export or email on a specific schedule. See “Creating a report schedule” on page 481. Viewing report schedule details This section provides information on viewing the list of report schedules. 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. . See “Managing time schedules” on page 485. Step number Step 1 Create a time schedule. OpsCenter provides a wizard to create a report schedule. ■ Specify details of export or email options. A single time schedule can be associated with multiple report schedules.Reporting in OpsCenter Managing report schedules 479 Table 11-1 Creating a report schedule Reference topic See “Creating a time schedule” on page 485. Each report schedule can be associated with a single time schedule. 2 Create a report 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. Note: You can select only saved reports in a schedule. You can select the appropriate conditions. 2 On the Report Schedules tab. To view a report schedule 1 In the OpsCenter console. the list of applicable conditions is shown on the last page of the wizard. 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 . An email notification is sent to the relevant recipients if the selected condition is satisfied. click Reports > Schedules. the Report Schedules tab is selected. view the following report schedule details.480 Reporting in OpsCenter Managing report schedules If you have applied conditions for the selected report. By default. Select a file format in which you want to export or email report the associated reports. click Reports > Schedules.Reporting in OpsCenter Managing report schedules 481 Creating a report schedule To create a report schedule 1 2 In the OpsCenter console. Select Format . 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. On the Report Schedules tab. See “ About file formats available in OpsCenter” on page 466. This is a mandatory field. If you have selected Create new time schedule. See “Creating a time schedule” on page 485. the system takes you to the Time Schedule creation wizard. 4 Click Next. The following page appears: Select the Use existing schedule option if you want to run this schedule on any existing time schedule. select Create new time schedule. After creating a time schedule you can select the export and the email report options.482 Reporting in OpsCenter Managing report schedules 3 Click Next. . If you want to create a new time schedule for this report schedule. Select email IDs to add in the Cc list of email. For example: Daily Job Count Report Type any other related information. or both options. See “ About file formats available in OpsCenter” on page 466. Overwrite if file exists Email To Cc Bcc Subject Message 6 Click Next. Select email IDs to which you want to email reports. Select email IDs to add in the Bcc list email. Select this check box if you want to email the reports that are associated with this schedule. Location Enter a directory path where you want to save the exported report or click Browse to select the desired location. the Configure Export / Email Report Settings page. Select this check box if you want to overwrite a file that already exists at the specified location.Reporting in OpsCenter Managing report schedules 483 5 If you have selected the Use existing schedule option in the previous step. Type the email subject. Export Select this check box if you want to export the reports that are associated with this schedule. Email. . specify the following details: You can either select Export. Click Edit. 8 Click Save. These reports should be saved.484 Reporting in OpsCenter Managing report schedules 7 Select the reports that you want to export or email on this schedule. click Reports > Schedules. the Report Schedules tab is selected. Click Save. select a report schedule from the list that you want to edit. By default. Click Back if you want to change the previous selections. 2 3 4 5 On the Report Schedules tab. Deleting a report schedule This section describes how to delete a report. Editing a report schedule This section describes how to edit report schedule details. . To edit a report schedule 1 In the OpsCenter console. Edit the report schedule details using the wizard. 2 3 On the Report Schedules tab. the Report Schedules tab is selected. By default. .Reporting in OpsCenter Managing time schedules 485 To delete a report schedule 1 In the OpsCenter console. Click Time Schedules. Viewing time schedule details This section provides a procedure to view the details of time schedules. Managing time schedules This section provides procedures to create and manage a report schedule. To view a time schedule 1 2 In the OpsCenter console. Click Delete. select a report schedule from the list that you want to delete. 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. Each report schedule can be associated with only a single time schedule. click Reports > Schedules. click Reports > Schedules. click Reports > Schedules. A single time schedule can be associated with multiple report schedules. See “Managing report schedules” on page 479. Click Time Schedules. Click Time Schedules. specify the following details: Schedule Name Time of Report Generation Enter name of the time schedule. Select a pattern with which you want this schedule to be run. Editing a time schedule To edit a time schedule 1 2 3 4 5 6 In the OpsCenter console. On the Create Time Schedule page. Click Edit. On the Time Schedules tab. options change. from the table. select the time schedule that you want to edit. Enter the time when the schedule runs and the associated reports are exported or emailed. Edit the time schedule details. 5 Click OK. click Reports > Schedules.486 Reporting in OpsCenter Managing time schedules 3 4 On the Time Schedules tab. . click Create. The following schedule patterns are available: ■ ■ ■ ■ ■ ■ Schedule Pattern One Time Daily Weekly Monthly Quarterly Yearly Depending on the pattern selected. Click OK. select the time schedules that you want to delete. . A few important notes on the OpsCenter Report Templates : ■ The Week at a glance. See “About vault reports” on page 522. See “About policy reports” on page 520. Drive Throughput. A report in the HTML format is sent as an inline message in email. Click Time Schedules. See “ About Disk Based Data Protection ” on page 510. See “ About media reports” on page 514.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. Reports in the PDF. and Drive Utilization reports can be exported and emailed only in the HTML format. the default view that is selected is All_Master_Server. See “About chargeback reports” on page 505. For the OpsCenter admin. TSV. or CSV formats are sent as email attachments. ■ ■ ■ ■ ■ See “About archive reports” on page 488. Sorting for HTML based reports (for example. On the Time Schedules tab. Click Delete. click Reports > Schedules. See “About performance reports” on page 517. A tabular report that is scheduled for emailing can have up to 4000 rows. About Report Templates descriptions This section provides descriptions of all Report Templates available in OpsCenter. See “About catalog reports” on page 504. See “About client reports” on page 505. Drive Utilization) is not supported. See “ About job reports” on page 511. from the table. See “About backup reports” on page 489. using the report. The Archived Size report is available in the Archive Storage report category. There are three types of Mailbox Quota reports: . The Original Size Vs Archived Size report depicts the difference between the two size of Exchange Server data.488 Reporting in OpsCenter About Report Templates descriptions About archive reports This section provides descriptions of archive Report Templates available in OpsCenter. it implies that data was archived in a very efficient way and thus. you can determine how much was the original size of the data that was archived later. 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 more efficient is your archival process. Use this report if you want to determine the archived size of the Exchange Server data that was archived. The more the difference. The difference between original size and archived size is termed as savings. Storage Report . 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. The Original Size Vs Archived Size report is available in the Exchange report category. If the savings are more. which have exceeded a particular mailbox size limit. Original Size Vs Archived Size report This report provides the comparison between original size and archived size of Exchange Server data. Exchange > Mailbox Quota The Mailbox Quota report displays the top mailboxes in Exchange Server. Archived Size This report is available only in the Archive Storage report category. This report is available in the Ranking report view.Tabular The Storage Details report shows details of archive the data that is stored in various Vault Stores and Vault Partitions. lesser storage space was required. Target Server is selected as the Report On parameter. If size of your mailbox exceeds the Receive limit. The Warning limit is a limit set for mailboxes. About backup reports This section provides descriptions on all backup Report Templates available in OpsCenter.Reporting in OpsCenter About Report Templates descriptions 489 By Warning Limit This report shows the mailboxes that have exceeded the Warning limit set in Exchange Server. Activity Planning –> Capacity Planning -> Historical Size This report shows the historical supply vs. By Send Limit This report shows the mailboxes that have exceeded the Send limit set in Exchange Server. If size of a mailbox exceeds this limit. 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% . 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. emails cannot be sent from this mailbox. For example: The Warning limit for mailboxes is set to 256 MB. you cannot receive any emails. That average is then used for the predicted size of all other tapes that are not full of the same type. Supply (yellow line) is defined as all available free space on all the backup media in the backup application. 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. The Send limit is a limit set for mailboxes. 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. which is greater than the Warning limit. demand. which decides how much data mailboxes can contain. For tape this number is calculated by taking the average size of all full media of the same tape type. By Receive Limit This report shows the mailboxes that have exceeded the Receive limit. The Mailbox Quota reports are available in the Exchange report category. This is necessary since tapes do not have an exact capacity and are written to until the end of tape mark. The By Warning Limit report displays all mailboxes that have exceeded 256 MB of data. For disk this is an exact calculation of remaining free capacity. schedules. Activity Planning -> Scheduled Jobs -> Scheduled Jobs report This report is available in ranking report view. 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 –> Capacity Planning -> Forecasted Size Similar to the previous report this shows the supply vs. or master servers. which depicts how many jobs have been scheduled to run in future. 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. To change the report parameters 1 2 3 On the Scheduled Jobs report. . from the Report On drop-down list. This can be easily done by clicking on “edit” at the top of the report. policy. Activity Planning -> Forecast -> Job Count This report shows you the total number of backup jobs for each day in the past two weeks. demand historically but now also adds a forecast line for both supply and demand that can show when in the future they may meet. click the Edit link. or client. which would suggest that more capacity doesn’t need to be purchased. Note: By default. For example: Client. On the Report Wizard. master server. change the report parameters. In the above example the supply is by far outgrowing the demand. or Schedule Name. Master Server. select a Scheduled Job attribute. Policy. The point that these two lines intersect would be the date that new capacity (more disk or more backup tapes) needs to be added. If you want to view the job count for clients.490 Reporting in OpsCenter About Report Templates descriptions capacity than others. Click Run. 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. You can view the Scheduled Jobs per schedule. the Scheduled Jobs report shows job count per policy. The report essentially shows the comparison between Scheduled (Future) Job Count and Actual Job Count. or schedule. On the Report Wizard. 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.Reporting in OpsCenter About Report Templates descriptions 491 Note: To view job count for a specific client. Using this report you can determine whether the jobs that were scheduled to run in future have been run on schedule. click the Edit link. Use this report to determine whether your backup windows are appropriate and are properly used. policies. To exclude manual jobs from the Actual Job count. 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. in the Filter Options section. during the backup window. select “Yes” from the Exclude Manual Jobs drop-down list. or schedule. The report essentially shows the comparison between Scheduled (Future) Job Count and Actual Job Count. click Show Advanced Filters and select name of the client. policy. and view only those jobs that have execution type as ‘Scheduled’. which were initiated manually by NetBackup admin. and schedules. . for each day. policy. 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. master server. By default the Actual Job Count includes manual jobs. for which you want to view job count. do the following: To exclude manual jobs from the actual jobs 1 2 3 On the Job Count-Scheduled Vs Actual report. Click Run. master server. Activity Planning -> Scheduled Jobs -> All Jobs This canned report shows jobs in a tabular form. in the Define Viewable Columns section. the Job Count Details-Scheduled Vs Actual report shows job count per policy. or schedule. in the Filter Options section. The Actual Job count includes Manual Jobs. To change the report parameters 1 2 3 4 On the Job Count Details-Scheduled Vs Actual report. click the Edit link. which do not have any schedule time associated with them as they are initiated manually. If you want to view the job count per client or master server. and view only the jobs that are of execution type ‘Scheduled’. On the Report Wizard. or schedule. To exclude manual jobs from the actual jobs 1 2 3 On the Job Count Details-Scheduled Vs Actual report. select Yes from the Exclude Manual Jobs drop-down list. The Job Count Details-Scheduled Vs Actual report shows comparison between Scheduled Job count and Actual Job count. which include the following: . select a column name (Client or Master Server) from the Available Columns list. On the Report Wizard.492 Reporting in OpsCenter About Report Templates descriptions Note: By default. click the Edit link. Click Run. Click >> button. Note: To view job count for a specific client. for which you want to view job count. By default the jobs that were run (Actual Job Count) include manual jobs. master server. master server. Click Run. change the filter parameters. policy. click Show Advanced Filters and select name of the policy. You can exclude manual jobs from the actual job count. 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. and schedule time. policy. OpsCenter stores this information historically. 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. Scheduled Jobs These jobs are scheduled to run in future. Thus. Each Scheduled Job when run on the specified schedule time becomes an actual job of execution type ‘Scheduled’. 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’. Note: While generating the Job Count-Scheduled Vs Actual report. 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. The yellow line is the axis on the right . This report shows results only for NetBackup. This particular Scheduled Job can be identified by the unique combination of client. This report shows results only for NetBackup. by NetBackup admin at his or her discretion. policy.Reporting in OpsCenter About Report Templates descriptions 493 Manual Jobs These jobs are initiated manually. 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. and schedule time. Each Scheduled Job information comprises a client. 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. a Scheduled Job has a corresponding actual job entry in OpsCenter database. See “Activity Planning -> Scheduled Jobs -> Job Count-Scheduled Vs Actual” on page 491. This report shows results only for NetBackup. these jobs do not have schedule time associated with them. Therefore. schedule. schedule. 5 for 50% since half of the backup images are copies. Bars outside of the yellow window represent the activity that occurred outside of the backup window. 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. 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. 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.66 or 66%. 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. 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. 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. 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. This is a particularly useful report for situations where you want to make certain there is always more than 1 backup copy.494 Reporting in OpsCenter About Report Templates descriptions and it shows the percentage of backup images that are copies. 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. 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 . 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. 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. The same situation for 3 copies would be a blue bar height of 2 and a yellow line percentage of . Activity Planning -> Backup Window –> File Count This report shows the number of files that were backed up for each hour of the day. . The report can also be used to see what hours may have capacity to add more backups while still remaining in the backup window. 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. 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. The report can give you an idea of your top consumers and whether those consumers are what you expected. Unexpected variations in this report between your day-to-day incremental or between full backup cycles can indicate problems. . 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.Reporting in OpsCenter About Report Templates descriptions 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 ->Job Size-> Distribution This report gives you a breakdown by each media server of the total gigabytes they’ve backed up over the past two weeks. 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. Activity Planning ->Job Size-> Historical This report shows you the total gigabytes backed up for each day in the last 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 they’ve taken to be backed up 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. 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. 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. 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. 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 -> 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. Unexpected variations in this report between you're day-to-day incremental or between full backup cycles can indicate problems. 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. 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).496 Reporting in OpsCenter About Report Templates descriptions 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 your day-to-day incremental or between full backup cycles can indicate problems. or even AdvancedDisk pools. 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 report groups the total number of bytes saved per host being backed up to show the top five hosts in terms of deduplication savings. PureDisk deduplication option storage. Deduplication -> Protected Files vs. TB etc. Deduplication -> Protected Size vs. The “Size Savings” and “Size Factor” report folders shows the difference between the bars and lines or the deduplication ratio respectively. 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.Reporting in OpsCenter About Report Templates descriptions 497 Deduplication -> Size Factor -> Rankings This deduplication report ranks the top hosts in terms of which ones have the best deduplication ratio in bytes. .5 and above which introduced “Disk Pools” as a type of Storage Unit. Deduplication -> Size Savings -> Historical This report is similar to the file factor report but instead shows the total number of bytes that don’t need to be backed up because of deduplication. These hosts have the least amount of change and therefore you get the best benefit from deduplication.5 Disk Pools which would include OpenStorage Devices. 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. Backed Up Size Similar to the previous report this shows the numbers in bytes instead of files. Disk Pools -> NetBackup Disk Pool Capacity This report is specific to NetBackup 6. There is no calculation or ratio in this number. The basic version of this report shows the total amount of space that is occupied by backups across all NetBackup 6.) that have not changed since the last backup and therefore don’t need to be backed up. SharedDisk. GB. 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 don’t have to be backed up due to deduplication. Along with usage the average of the high and the low water mark is taken for each disk pool and drawn on the graph. it is the number of bytes (MB. a PureDisk Deduplication system. The lines represent the percentage full each disk pool is. So this report can help identify how much disk space is used for backups. 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 “specified period of time” is user. You can also filter the report to show activity for a limited sample set. You can edit the report to show or hide the columns you are interested in. 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. days. In actual usage this report should be filtered on a specific Disk Pool to show the exact high and low water mark.5 and above which has new devices and storage units called “Disk Pools”. which ones are nearing capacity and how the backup environment is load balancing across disk storage.498 Reporting in OpsCenter About Report Templates descriptions Since this is an average it should not be used for planning purposes but rather estimation. Percentage Full This report is specific to NetBackup 6. which pools are the largest. or months . Finally the forecast is shown so that it can be determined when capacity needs to be added or backups expired to maintain operations.5 and above which features Fibre Channel connected clients called “SAN Clients”. weeks. or a group of local or network disk volumes that are pooled together. such as one or more policies or clients. Disk Pools -> NetBackup Disk Pool Size vs. 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. Disk Pools -> NetBackup SAN Client Performance This report is specific to NetBackup 6. 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. A Disk Pool may be an OpenStorage device. This report helps identify what ratio of LAN to SAN traffic for backups are run and what performance benefit is gained by doing so.definable along with several other variables for filtering purposes. The report is interpreted as all client or policy combinations that have gone x hours. 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. SharedDisk. 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. Risk Analysis -> Recovery Point Objective . The client “Is Active” filter allows for those hosts that are not actively backed up to be omitted. DNS listings or any other authoritative source of what hosts should be backed up. Job success rate is derived from all jobs and separated out by first. 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 . all and last and a specific client can have a job success rate that can range between 0% and 100%.RPO Recovery Point Objective (RPO) and Recovery Time Objective (RTO) have emerged as generally accepted metrics for client recoverability. the level of granularity is the client level and thus clients with multiple backup policies are represented by the policy with most recent success. 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. This report ranks all clients by the amount of time that is elapsed since their last successful backup.tsv.Reporting in OpsCenter About Report Templates descriptions 499 without a successful backup. 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. 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. 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 list can come from a content management database (CMDB). all and last job. This it is recommended that this report not be used for multi-policy clients. End-user and customer typically get Last Job Success for job and client whereas back up architects and . The report is effective in its graphical rankings format placing the clients with longest elapsed time at the top. Thus a client is either 0% or 100% and no intermediate state. The elapsed time in the report is always between now and the last successful backup. 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. 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. In contrast to the Client Risk Analysis report. 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. OS. It can be reported on against any view or level within a view along with any of the key backup infrastructure components (backup server. policy type. product. product. transport type). media server) and attributes (policy. The primary use case of the report is verification of trends and the days that are exception to the norm.500 Reporting in OpsCenter About Report Templates descriptions administrators examine all three. policy type. this report is the same as “all jobs” as no distinction on whether the failed job was first or last one is made. Status -> All Failed Backups This report is one of three using the advanced success or failure calculation logic around the notion of first. Status -> Failed Job Count This report aggregates failed jobs and shows these across a timeline. The report is highly effective for presenting long-term historical data on one of the most fundamental metrics of managing a backup operation. 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. schedule. schedule. these reports . transport type). Additionally. OS. Status -> Partially Successful Job Count This report aggregates partially successful jobs and shows these across a timeline. It provides visualization of whether a problematic trend exists. OS. Filtering is available on all components and attributes. In reality. The primary use case of the report is verification of whether actions taken to correct persistent failures produce results and reversing 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. Filtering is available on all components and attributes. product. It provides a visualization of job volume trends. These reports work well with views and can be reported on at any level with robust filtering capabilities. Filtering is available on all components and attributes. schedule. Status -> Successful Job Count This report aggregates successful jobs and shows these across a timeline. transport type). It provides a visualization of job volume trends that skip the files that are open during the backup job. media server) and attributes (policy. 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. They require schedule and window parameters enabling a precise definition of timeframes. policy type. all and last job. Reporting in OpsCenter About Report Templates descriptions 501 have aggregation levels of job and client. It can be reported on against any view or level within a view along with any of the key backup infrastructure components (backup server. Operating Systems and Business Classifications. Status -> Consecutive Failures This report is the second of three using the advanced success or failure calculation logic around the notion of first. Backup Level. media server) and attributes (policy. or year across any timeframe. Size etc. the client or the policy combo should also appear on the risk report as not having a successful backup in 72 or more hours. The symbols are the blue (Success) and yellow (Partial Success) men and failures that are denoted by a red “X”. day. As failed jobs are rerun one or more times. yellow (partial success) and green (success) displayed in stacked bar format that is grouped by hour. The simplicity of the presentation helps easily identify both positive and negative trends as well as one-off deviations. all and last job. This report produces the details of the failed jobs based on which one of the three (first or all or last) methods is chosen. This report can be best verified through the Client Risk Analysis report where if 3 consecutive failures with 24 hour windows were chosen. Start/End Time. Transport Types. OS. The report is a count of jobs for each of the three outcomes. jobs can be configured for x many attempts before you exit with a status.) is provided. For NetBackup environments. policy type.e Job ID. Backup and Media Servers. Filtering is available on all components and attributes. product. week. transport type). month. Policies. A drill-down capability to the job level details (i. the report can also be generated where attempts rather than jobs are counted. The report is highly . 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. It applies intricate logic to pick off the last failed job and in turn to determine that the last job failures are indeed consecutive. The report can be filtered across a selection that includes Views. 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. Schedules. In NetBackup. 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. Status -> Job Status -> Historical A job status report in red (failure). schedule. the “last job” represents the last of the reruns within the window. The main use case is the calculation of 2 or more consecutive failures based around Last Job Success/Failure. Jobs can be configured for x many attempts before exiting with a status. this translates into a 50% attempt rate and 100% job success rate. and Business Classifications. 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. A target .502 Reporting in OpsCenter About Report Templates descriptions effective as it provides a visualization of job status for the most current data and how that compares to the previous six days. This metric is only supported for backup applications in which attempt level data is available. Schedules. Jobs can be configured for x many attempts before you exit with a status.First Attempts This report shows success rate as it’s aggregated at the attempt (known as “try”) level. it zooms in on the measurement of the first attempt for each job.e. Backup and Media Servers.e. A target line is also supported providing for an effective visual presentation on when the target is exceeded. third etc. Transport Types. Meaning as long as one job is successful despite any number of retries. Policies. it is a 100% success. 1+ months) management level reporting requiring high-level status summaries. The main use cases of the report are typically short-term verification (i. Filtering is available on all components and attributes. Success Rate -> Success Rate . 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. A 100% on this report indicates that everything was backed up even though it may have taken a number of retries. The report is a count of jobs for each of the three outcomes. Backup Level. Success Rate -> Success Rate –> All Attempts This report shows success rate as it’s aggregated at the attempt ( “try”) level. The report can be filtered across a selection that includes Views. If for example the attempt setting is two and success is attained on the second attempt. This is typically a report to show overall exposure to someone outside the backup team. last 24 – 48 hours) of backup job status and long term (i. attempts. Operating Systems. Status -> Job Status -> Distribution A job status report in red (failure). Specifically. yellow (partial success) and green (success) displayed in pie chart format. This metric is only supported for backup applications in which attempt level data is available. 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. the report enables several methods by which an individual tapes capacity is determined. The report uses the “heat map” concept and depicts ranges of speeds (slow to fast) through configurable shades of green. The averaging is done at an image fragment level ensuring granularity and precision in calculations. It can be reported on against any view or level within a view along with any of the key backup infrastructure components (backup server. Drive Type. 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. Media Server. A libraries’ capacity is calculated by multiplying Slot Count by Slot Capacity. Media Server. Main use case is long-term historical data on one of the key performance indicators. OS. the minimum and the average size of full tapes to determine tape capacity. Tape Devices-> Drive Throughput This report shows the speed (KB/Sec) at which data backups flows through tape drives. The . The report extrapolates out the trend line through the forecast period using classic linear regression and also plots the libraries capacity. Tape Devices-> Library Capacity Forecast This report provides a capacity forecast of Tape Libraries. schedule. Drive Type. These consist of using the maximum. Filtering is available on all components and attributes. Advanced logic is used to determine the utilization values for each cell in the report. Advanced averaging logic is used to determine the throughput values for each cell in the report. At the date in which the library capacity line intersects the capacity forecast line is when the libraries capacity is reached. The sort options allow for intuitive presentation of voluminous data. As no standard exists for measuring library capacity. Logical Drive and Physical Drive levels. The reports can be aggregated and filtered at the Tape Library. The reports can be aggregated and filtered at the Tape Library. user-defined capacity for tape types is available in the report parameter selection UI. Reports are based on either Hour-Of-Day or Day-of-Week. The report uses the “heat map” concept and depicts ranges of utilization (low to high) through configurable shades of blue. 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. Reports are based on either Hour-Of-Day or Day-ofWeek. transport type). product. policy type. Slot capacity is the capacity of the tape in the slot. Logical Drive and Physical Drive levels.Reporting in OpsCenter About Report Templates descriptions 503 line is also supported providing for an effective visual presentation on when the target is exceeded. media server) and attributes (policy. Additionally. 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. The reports list the libraries name. and used or available or total capacity. 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. 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. The table in the report also lists the media that NetBackup uses for the backups for each master server. . These reports are important sources of information for performance analysis and capacity planning activities.504 Reporting in OpsCenter About Report Templates descriptions sort options allow for intuitive presentation of voluminous data. Alternatively you can click on Show Table option to obtain the same information in the tabular format. “Infinite” means that backup media is never used again for backups unless it is manually expired. used/available/total slot count. About catalog reports This section describes catalog reports. Tape Devices-> Library Summary This report provides a current point in time inventory of library capacity. Tool tips in the bar chart show the report name and backup count. 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 Retention Level (Distribution) This report is a pie chart that shows the percent of backup media at each retention level. Media -> Tape Count -> By Volume Pool (Distribution) This report shows the percentage of the media in each volume pool. 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. Volume DB Server. About the Cost Tabular report This report shows the chargeback of your backup services in a tabular form. About the Savings report This report shows the savings that is achieved because of the deduplication technology. which is called Chargeback. You need to have a cost formula created to generate this report. as 20 MB of data is duplicate data. This results in saving 20 MB of data. and start and end times. The deduplication technology can identify files and the data segments that contain identical data and treats them as a single instance of the file. You can generate the Savings report that shows the amount you have saved using deduplication. To generate this report. Therefore. Historical. For example. PureDisk has backed up 100-MB data . but the actual data that is backed up by PureDisk is 80 MB. the data that is protected is 100 MB. OpsCenter provides organizations with a tool to evaluate the cost of the IT services they consume. The table in the report contains information. and Ranking views. PureDisk protects the same data but eliminates the duplicity using deduplication. About the Chargeback report This report shows the chargeback of your backup services in Historical and Ranking views. About client restore report This report provides restore job details for a specified client. in which 20 MB of data is duplicate or identical. such as. About client reports This section describes client reports. . you need to have a cost variable of Protected Job Size. The Savings report is available in Distribution.Reporting in OpsCenter About Report Templates descriptions 505 About chargeback reports This section provides descriptions of OpsCenter chargeback reports. To generate the Cost report you need to have a cost formula created. which it backs up only once. master and media server names. You can create cost variables and the formulas that enable you to run the reports that show costs of backup services. Oracle. About job success by client report This report shows the rate of success for client jobs. Number of Successful Jobs. Windows NT and so on. The table is organized by master server and client. job type. and date of the last successful backup. partially successful. You can filter by type of policy like SharePoint. The report shows details like policy name. exit status. You can determine if all jobs of a policy and client combination have failed or have not been initiated during the reporting period. schedule name. and media server name. 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. and failed jobs for each client for the selected server or server group. and Number of Failed Jobs columns provide drill down links to more detailed reports.506 Reporting in OpsCenter About Report Templates descriptions 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. The bar chart shows totals for successful. and the job success rate). The Client Name. Tool tips in the bars show these job counts. The table includes details such as. The table in the report summarizes job information (including the number of successful and partial successful jobs. . Number of Partially Successful Jobs. This drilldown report uses the run time parameters that are passed from the main report. 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. The tool tips for each client also include links to a drill-down report showing details for all job types. 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. 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. IP address. You can use drilldown links to view client detail reports for many of the columns in the table. 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. This drilldown report uses the run time parameters that are passed from the main report. This drill-down report uses the run time parameters that are passed from the main report. 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.Reporting in OpsCenter About Report Templates descriptions 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. 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. This drilldown report uses the run time parameters that are passed from the main report. and throughput (KB/sec). schedule name. Any jobs with an exit status other than 0 or 1 are considered to be failed jobs. and operating system type? How much volume for a client is backed up? How many successful. The drilldown reports provide information about the client and answer the following questions: ■ ■ ■ ■ ■ What is the server name. . and job duration. job type. 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. such as. This drilldown report uses the run time parameters that are passed from the main report. an Oracle policy type implies an Oracle application.508 Reporting in OpsCenter About Report Templates descriptions 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. schedule name. and job duration. The report lists job details. start and end times. job type. This drilldown report uses the run time parameters that are passed from the main report. . such as. The report lists job details. job type. client. The report then lets you see all Oracle backups. This drilldown report uses the run time parameters that are passed from the main report. and job duration. Any jobs with an exit status other than 0 or 1 are considered to be failed jobs. such as. policy name. The table in this report organizes jobs in the table by server. The Application (policy type) column provides a drilldown link to job details for the respective application. and application and includes the backup size in MBs and the number of files. For example. policy name. start and end times. About restore jobs for client report This drilldown report from the Number of Restore Jobs column lists restore job details for the selected client. About jobs by application report This report uses the NetBackup policy type to simulate an application level report. start and end times. The report lists job details. 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. and throughput (KB/sec). This drilldown report uses the run time parameters that are passed from the main report. policy name. It provides details like policy name. You can also drill down in this report to see the job details of a specific virtual client. But they can be identified by their UUIDs. you can report on the virtual clients that need to be protected. 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. This drilldown report uses the run time parameters that are passed from the main report. Using this report. UUID is a unique identifier of a virtual client. exit status. job ID. 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. Multiple virtual clients may have the same IP address. Virtual Client Summary The Virtual Client Summary report shows details of all virtual clients of a NetBackup Master Server. and a count of files. The table includes job details such as. such as VMware or Hyper-V. you can determine whether these virtual clients were backed up by NetBackup or not. 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. Thus. such as VMware or Hyper-V . Backup Proxy Name Note: Click the virtual client name link to view its job details. and job start and end times.Reporting in OpsCenter About Report Templates descriptions 509 About job application details report This drilldown report from the Application column lists all the jobs for the selected client and policy type. 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. 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.510 Reporting in OpsCenter About Report Templates descriptions Server Name Name of the NetBackup Master Server. From the Feature Name column of the report table. This drilldown report uses the run time parameters that are passed from the main report. . you can drill down to view a report that shows the used capacity for your licensed capacity usage features. it means that this client should be backed up and be protected. This report shows if you are in compliance with the license rules or if you need to purchase more licenses. 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. 14 days).511. About Disk Based Data Protection This section describes DBDP (disk based data protection) reports. If it shows “No”. This report shows all of the capacity based licenses and the actual usage per disk type at your site. This report can warn you about approaching license limit expiration. 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. All capacity values for this report are calculated based on the definition that 1 terabyte=1.627.099. this field displays “Yes”. 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.776 bytes. The main report that is organized by master server. 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. The table in the report is organized by job ID. 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. Partially successful jobs have an exit status of 1. displays clients and policies. About skipped files summary report The information in this report is presented using a set of linked reports. and client name. server name. ■ ■ About job reports About partially successful job details report This report provides details for all NetBackup partially successful jobs. 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. thus reducing the throughput? A list of all the FT media servers A list of all the SAN clients. .Reporting in OpsCenter About Report Templates descriptions 511 About current disk usage report This report shows the master servers that have disk pools configured. and the corresponding number of files that were skipped. 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. policy and schedule type combination is shown with the actual variation. and failed jobs per a given date. This drilldown report uses the run time parameters that are passed from the main report. and schedule type. partially successful. . 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). You can use this report to provide trend information. the client.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. 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. About skipped file details for policy and client report This drilldown report from the No. client. and schedule type. Size variance is calculated using the following formula: (the last backup size . About job summary by status report This report summarizes NetBackup jobs based on the job exit status for a specified time interval. The bar chart shows a count of successful. If any variation calculation is greater than the selected value of variance when the report is run. policy. This report calculates the backup size variation of the last good backup with the average backup size per a client. You can detect any anomalies if the variation is too high. of Skipped Files column provides the names of all skipped files. You can detect any anomalies if the variation is too high. 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.512 Reporting in OpsCenter About Report Templates descriptions This drilldown report uses the run time parameters that are passed from the main report. About Backup duration variance report This report provides an indication of how backup time varies from the average backup time. The Client Name column of the report provides a drilldown link to back up job details for the specified time frame. This report calculates the backup time variation of the last good backup with the average backup time per client. The Client Name column of the report provides a drilldown link to back up job details for the specified time frame. policy. You can detect any anomalies if the variation is too high. and schedule type combination is shown with the actual variation. and schedule type. the client. and schedule type. policy. policy. a file server backup is successful.Reporting in OpsCenter About Report Templates descriptions 513 This report calculates the backup throughput variation of the last good backup with the average backup throughput per a server. the server. client. For example. . If any variation calculation is greater than the selected value of variance when the report is run. and schedule. policy. but contains fewer files than usual for a full backup. If any variation calculation is greater than the selected value of variance when the report is run. If any variation calculation is greater than the selected value of variance when the report is run. About file count variance report This report lets you investigate why a particular full backup is different than usual. and schedule type combination is shown with the actual file count variation. policy. and schedule. the client. client. The report shows NetBackup jobs with significant differences in file counts from the average count for a master server. policy and schedule type combination is shown in the table with the actual variation. The table provides the percent variance (in file counts) for each good job from the average for that server. policy. 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. About job exit status detail report This report provides information about the completion status for a NetBackup job. but their related child jobs (client data backup jobs) were partially or fully successful. offsite. The table in the report is organized by job ID. This drilldown report uses the run time parameters that are passed from the main report. About media reports This section describes media reports. The report table provides a count of jobs having a particular exit status on a particular day. such as job type and policy name. Media state can be frozen. About restore job details report This report provides details for restore jobs. The table is organized by server name and date. active. The table includes all jobs having a particular exit status on a given day. . and client. master server name. This job type starts one or more dependant jobs to back up the client data. About media state report This report displays the media status and count (per media type) for each master server and media server combination. About job details report This report provides detailed information about NetBackup jobs. the job backs up BMR (Bare Metal Restore) client configuration. This report shows all jobs that failed to completely back up a BMR client configuration. 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. and so on.514 Reporting in OpsCenter About Report Templates descriptions About BMR client configuration backup failures report If a NetBackup policy has the Collect BMR Info flag set. These are the tapes that NetBackup marked as full. media status. This drilldown report uses the run time parameters that are passed from the main report. number of tapes and images. 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. This report displays media status. the last written date. The report table provides information.Reporting in OpsCenter About Report Templates descriptions 515 About available media report This report lists the media that is available for use by NetBackup for each master server that is selected. Invalid. The name of the media server is also a drilldown link to a detailed report for media. About media summary by media server report For each media server. Media status can be Active. The report table is organized by server. and the time assigned. drive name and type. and shows the size and number of images on the tape. and amount of data on tapes. About media details of media status for a media server report This drilldown report from the Media Status column provides media details for the selected media server and selected media status. the last written date. The report table provides details for the drive. . robot type. and assigned host. About drives in use report This report shows the drive usage for the selected server. media type and count. Full. Frozen. media server. 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. or Suspended. volume group and pool. this report provides the number of tapes and images. and amount of data on the tapes. The bar chart depicts the amount of data (in kilobytes) per media type. such as. This drilldown report uses the run time parameters that are passed from the main report. robot number and type. for example. Using this report you can determine what media will be available for reuse. and Media Barcode listed make it easy to locate the media. The table in the report is organized by date and server. and shows counts for each media state. . unassigned. About media utilization report The stacked bar chart in this report shows the number of media in use for a server per date. About media expiration schedule report This report gives graphical representation of the expiration schedule for media. and the amount of data on tape. expiration date. Different colors are used in the bars for the different media types. volume pool. or suspended media states. Tool tips for the bar segments provide the media type and count of the media that is available on that day. The data for today reflects in the report that you generate tomorrow. full. Tool tips in the chart show the count for each media state. So the report shows the summary till the previous date. 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. number of images. Media ID. This time frame can be changed to show more in to the future. Media -> Tapes expiring Now This report lists the media that are about to expire. The data for this report is only calculated once in a day. last written date. frozen. type. 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. The stacked bars represent the number of media of a specific type that are expired on a particular day. The report predicts the availability of media based on the expiration date of the media. The segments in the bars show assigned. month or any future time window desirable. offsite. 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.516 Reporting in OpsCenter About Report Templates descriptions The report displays media ID. The Volume Pool Name . 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. A drilldown detail link from each server pie slice for job details is provided. The pie chart displays the breakdown of jobs that are run across the selected master servers. The first column of each row of the report table lists a storage unit. The rest of the cells indicate whether the storage unit was in use or not during the time slot. The Storage unit column of the report table is a link to a drilldown throughput report. It shows job count and job success rate. The table of this report displays throughput and job success information for each server in the selected server context. The rest of the row provides details such as. total volume processed (KB). This drilldown report uses the run time parameters that are passed from the main report. The storage unit name is also a drilldown link to a detailed report. . average throughput (KB/sec).Reporting in OpsCenter About Report Templates descriptions 517 About performance reports This section describes performance reports. About storage unit throughput report This drilldown report from the Storage Unit column shows the data transfer rate (throughput) of the selected storage unit. The media server name in the second column is also a drilldown link. and enables you to compare throughputs of different servers to identify any servers that are performing poorly. About storage unit usage report This report shows storage unit usage for a selected master server and time frame. About master server job throughput report This report provides a tool to compare performance of various master servers. total number of jobs. duration of activity and percentage of utilization in terms of duration. . The report details include exit status. and file counts. This drilldown report uses the run time parameters that are passed from the main report. duration in seconds. and throughput. and start time. and job status. 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. It is a useful tool to compare performance of the media servers that are present in your NetBackup environment. 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. You can compare the load on each media server present in the environment. The pie chart provides a breakdown of the volume of data that is processed for each media server. job type. The report details includes details like job type and status. This drilldown report uses the run time parameters that are passed from the main report. The table in the report shows the throughput of all the media servers present in the selected server context. About job details for client and master server report This drill-down report from the client name column provides details for a given client. This drilldown report uses the run time parameters that are passed from the main report. A drilldown detail link for throughput details is provided from each volume pie slice. The table also contains drilldown links to detail reports for the media servers and their throughput. volume. About media server job throughput This report provides details of data that is backed up by NetBackup media servers and shows server throughput. policy and schedule names. volume in KB. 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. number of total and successful jobs columns are also provided. start time. The report provides details like job type.518 Reporting in OpsCenter About Report Templates descriptions Drilldown links for the server name. policy and schedule names. In the report. job type. total number of jobs. total volume processed (KB). duration of activity. 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. schedule type. start time. average throughput (KB/sec). The throughput is represented by a bar for each day of the reporting period. About job details for client and media server report This drilldown report from the client name column provides details for a given client. This name is also a drilldown link to a detailed report for the client and the media server. full or incremental) and unique icons indicate the job exit status and job type. exit status. job status. and backup size. and duration in seconds. and media server.Reporting in OpsCenter About Report Templates descriptions 519 This drilldown report uses the run time parameters that are passed from the main report. day on which the job run. job type. The Disk and Media Server Name columns of the table contain drilldown links to detailed throughput and disk usage reports. The report details include job ID. About disk usage report This report shows disk usage for the selected server and time frame. and percentage utilization in terms of duration. The tool tips for each icon also show client name. This drilldown report uses the run time parameters that are passed from the main report. the first cell in each row represents the client name. This drilldown report uses the run time parameters that are passed from the parent report. job type. The color of each cell indicates job schedule type (for example. The table in the report provides details such as. The other cells in a row indicate the details for each job. . 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 drill-down report uses the run time parameters that are passed from the main report. client name.520 Reporting in OpsCenter About Report Templates descriptions 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. number of jobs and files. 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. such as. The table includes information. and failed jobs per policy type. The tool tip also shows the volume of data in MBs. The table in the report displays job information. and volume of data. server. The rest of the cells indicate whether the disk was in use or not during the time slot. The report table includes information. job type. such as. and job policy type. partially successful. This drilldown report uses the run time parameters that are passed from the main report. The bar chart shows the count of successful. About policy reports This section describes policy reports. The report shows the job success rate for clients. . This drilldown report uses the run time parameters that are passed from the main report. The tool tips in the colored bars provide job counts and also are drilldown links to view the details for the policy. The Disk cell in each row of the report table is a link to a drill-down report. Drilldown links from the bar chart (tool tips) and the table in the report provide details for the selected policy. 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. About job success rate by policy type report This report provides a quick view of the status of jobs by policy type. and the success rate. client name. 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. policy type. and volume in KB. exit status. such as. The table for failed jobs also includes a column for the job exit status.Reporting in OpsCenter About Report Templates descriptions 521 Note: This report may not show appropriate data for duplication jobs that are associated with SLP policy. Number of Partially Successful Jobs. These reports are similar and provide details for all jobs for a selected client and policy type. or Number of Failed Jobs columns. 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. About successful. start and end times. and count of files. This is because the duplication jobs do not have a policy type. volume in KB. 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. and duration for the 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. policy and schedule name. The table in the report displays the count of changes that were made to each policy for each server.) Tool tips in the chart provide a count of the changes. The pie chart shows the number of policy changes (a policy can change multiple times) for each master server. exit status. and failed job details for policy type report There are three drilldown reports from the Number of Successful Jobs. The table in this report provides details like. such as. This drilldown report uses the run time parameters that are passed from the main report. (Each different server appears in a different color in the chart. partially successful. The job batches duplication of images that are created from possibly different policies and policy types. client name. The job exit status is used as a filter for the reports. . This drilldown report uses the run time parameters that are passed from the main report. The table includes information. a line chart and a table. This report helps understand your offsite media trends. and counts for job exit status. job count. job volume in MB. Successful Jobs. and duration of the job. About vault reports This section provides descriptions of vault reports. Partial Jobs. 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? . or Failed Jobs columns provide an overview of all jobs for the selected policy name. server. 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. The report consists of two component reports. This drilldown report uses the run time parameters that are passed from the main report. 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. About drilldown reports These drilldown reports from the Total Jobs. and time frame based on the job exit status. start times.522 Reporting in OpsCenter About Report Templates descriptions About policy summary dashboard report This report acts as a dashboard of NetBackup activities that are summarized by your policies. The table provides details like schedule name. 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. About vault media usage report This report shows offsite media trends for selected vaults and current offsite media count. expiration date. offsite slot number. While running the report you select the vaults for which you want to run this report. When you run the report you specify the vault names. This chart is a good indication of how the offsite media count varies over the period of time. . The report provides important media details like media ID. The report shows a weekly line trend for selected vault. container ID. The report table provides the details of vaulted media for the selected vaults. You can compare the media counts of different vaults to see which vault is consuming more media and how it is varys.Reporting in OpsCenter About Report Templates descriptions 523 The line chart shows the weekly trend of offsite media counts for selected vaults. and so on. bar code. 524 Reporting in OpsCenter About Report Templates descriptions . there can be two types of OpsCenter . On a broader level.Appendix A 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.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 ■ . . the AT root broker is common. you need to set up a bi-directional trust between the OpsCenter AB host and PureDisk SPA host. the AT root broker is common. Figure A-1 Common root broker . You do not need to carry out any additional steps for PureDisk data collection. You need to establish trust between the authentication brokers of OpsCenter and PureDisk SPA for secure communication. 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. See “Scenario 2: Different Root Brokers” on page 527. Thus for both product hosts. This set up is a pre-requisite for PureDisk data collection from OpsCenter. Thus for both product hosts.526 About additional information on PureDisk data collection About AT configuration scenarios specific to PureDisk backup product Note: In this type of configuration. Thus for both product hosts.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.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. 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. Figure A-2 Common root broker . the AT root broker is common. . This set up is a pre-requisite for collecting PureDisk data from OpsCenter. you need to set up a bi-directional trust between the OpsCenter AB host and the PureDisk SPA host. If it is not successful.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. Refer to the “Setting up a trust between PureDisk SPA host and OpsCenter AB host” section. you need to do it manually. Note: Setting up trust between the PureDisk SPA host and OpsCenter AB host is a manual process. 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. See “Setting up a trust between the OpsCenter AB host and PureDisk SPA host” on page 529. Note: If OpsCenter and PureDisk have different AT root broker configurations.About additional information on PureDisk data collection About AT configuration scenarios specific to PureDisk backup product 527 Figure A-3 Common root broker . Setting up trust between the OpsCenter Authentication Broker host and PureDisk SPA host is accomplished automatically after PureDisk data collector is configured. 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. 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. you need to set up a trust between the two root broker hosts. .528 About additional information on PureDisk data collection About AT configuration scenarios specific to PureDisk backup product 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. that is between Host A and Host B. Note: OpsCenter AB host is the host where the OpsCenter server is installed. the OpsCenter AB host is the host name that was provided as the remote AB host during the OpsCenter installation.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 Host C: AT Root Broker 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. . If OpsCenter is installed in a clustered mode. Figure A-7 Local root broker for OpsCenter server and remote for PureDisk Host C: AT Root Broker 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. the following message is displayed: setuptrust ------------------------------------------Setup Trust With Broker: PureDiskSPAhost . 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 trust is not successfully established at this stage. carry out the manual steps as follows. If the AT root broker is configured with another port number. run the following command depending on the OpsCenter server operating system : These are the default directory paths. To set up a trust between the OpsCenter AB host and PureDisk SPA host ◆ On the OpsCenter AB host. contact your security administrator for more information.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. After successfully setting up a trust between the OpsCenter AB host and PureDisk SPA host. Table B-1 Data Attributes Backup Job Attributes Agent Server host. You can select these attributes while generating custom reports.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 .Appendix B 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. Table B-1 lists all NetBackup attributes that OpsCenter collects. Meaning that for every 321 files that were backed up only one file was actually stored. only 44 were stored since the saving was 456. This marking of a job as ignored is done in the "Reports > Explorers" section.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. Note that this number is not actually stored since it is before deduplication. If it is ignored it does not count towards things like success rate or time since last successful backup. Meaning that if 500 files were targeted for backup. Within Backup Reporter there is the ability to mark a job as ignored (yes/no). (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. The size in byes of a PureDisk backup job before deduplication. The number of files that are processed in a PureDisk backup. 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 . SAN Job Attempt Count 4 Job Client backup-client. Sybase Backup job Transport Type LAN. ALL_LOCAL_DRIVES . NDMP. The number of KB's not needing to be backed up for every backup job in PureDisk because they were already stored with deduplication. File System. 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.com Job Directory C:\. MS Exchange.symantec. the savings of 345KB means only 1 KB was needed to be stored.Attributes of NetBackup data About backup data attributes 533 Table B-1 Data Attributes NetBackup data attributes (continued) Sample Data 567 Explanation The deduplication size factor for each PureDisk backup job. /var. Meaning that if 346KB were backed up. Each directory under a job and it's type of backup. Meaning that for every 567KB that were backed up only 1KB was stored. 534 Attributes of NetBackup data About backup data attributes Table B-1 Data Attributes Job Duration NetBackup data attributes (continued) Sample Data 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 Attributes of NetBackup data About backup data attributes 535 Table B-1 Data Attributes Job Secondary ID NetBackup data attributes (continued) Sample Data 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 Attributes of NetBackup data About backup data attributes Table B-1 Data Attributes Job Throughput (Kbytes/sec) NetBackup data attributes (continued) Sample Data 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 Oracle Backup Policy, User Backup Policy, File System Backup Policy 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 Attributes of NetBackup data About backup data attributes 537 Table B-1 Data Attributes 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 Attributes of NetBackup data About backup data attributes Table B-1 Data Attributes Original Job ID NetBackup data attributes (continued) Sample Data Explanation 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 Attributes of NetBackup data About backup data attributes 539 Table B-1 Data Attributes NetBackup data attributes (continued) Sample Data 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 Attributes of NetBackup data About backup data attributes Table B-1 Data Attributes Backup Image File Count NetBackup data attributes (continued) Sample Data 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 Attributes of NetBackup data About backup data attributes 541 Table B-1 Data Attributes Backup Image Is Currently Expired NetBackup data attributes (continued) Sample Data 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 Attributes of NetBackup data About backup data attributes Table B-1 Data Attributes Data Classification Master Server NetBackup data attributes (continued) Sample Data 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 Attributes of NetBackup data About backup data attributes 543 Table B-1 Data Attributes Attempt Status NetBackup data attributes (continued) Sample Data 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 Attributes of NetBackup data About backup data attributes Table B-1 Data Attributes NetBackup data attributes (continued) Sample Data 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 1 Skipped File Reason File is open by another process Skipped File Name C:\Windows\an_open_file.dll Backup Policy Attributes com Master Server Backup Policy Name Oracle Backup Policy. 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 . The name of a backup policy that exists in the backup application. In the case of NetBackup this is the master server. 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. File System Backup Policy Backup Policy Type Standard (UNIX). User Backup Policy.Attributes of NetBackup data About backup data attributes 545 Table B-1 Data Attributes NetBackup data attributes (continued) Sample Data Explanation The host name of the backup application host that contains the backup policy. 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. The type of backup Exchange policy that exists in the backup application. Oracle. Windows-NT.example. ‘Business Critical’ or ‘Business Support’ .546 Attributes of NetBackup data About backup data attributes Table B-1 Data Attributes NetBackup data attributes (continued) Sample Data Explanation 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’. Filesystem Type Host Attributes Host Architecture SPARC. POWER. Explanation A user defined field for an object ID of the file system. NTFS. etc. UFS. Host: Misc Info Pete's server Host: OID asset123. EXT3 A user-defined field (this is not collected automatically) of what type of file system was backed up. x86 User defined field (this is not automatically collected) for filling in architecture type such as x86. x86-64. Hostname hostname. ZFS. 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.Attributes of NetBackup data About backup data attributes 547 Table B-1 Data Attributes File System: OID NetBackup data attributes (continued) Sample Data asset123 etc. 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. PA-RISC. SPARC.example.com . Value here per sample is either the free capacity if the media is active. Usually grouped with Operating System name since this will have values like ‘10’ (i.000. or 0 otherwise. or 0 otherwise. 10 Explanation The version of the operating system.e. Value here per sample is either the total capacity if the media is active.e.548 Attributes of NetBackup data About backup data attributes Table B-1 Data Attributes O. This can be longer than the 6 characters used by a NetBackup Media. or ‘2003’ (i. Solaris 10).com The name of the OpsCenter agent that collected the media information.S. Windows 2003) The operating system name of the host Operating System Windows.000KB Backup Media Barcode JFP000L2 .000 KB Backup Media Available Total Capacity 19. The date/time that a piece of media was first allocated or had it's first backup written to it. Total capacity of the tape in KB. The full barcode as ready by the physical robot.example. Version NetBackup data attributes (continued) Sample Data 2003. Backup Media Allocation Time Mon 3/4/2008 3:34:34 Backup Media Available Free Capacity 500. Once the media expires it will have a new allocation date/time when it is reused How much is left on tape in KB. Solaris Backup Media Attributes Agent Server ops-agent. This number may be estimated using an algorithm. A yes/no property of a particular tape indicating whether it can still be written to. A yes/no property of a particular tape indicating whether the tape has been sampled in the last two collections.Attributes of NetBackup data About backup data attributes 549 Table B-1 Data Attributes Backup Media Expiration Time NetBackup data attributes (continued) Sample Data 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.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 . 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. 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.550 Attributes of NetBackup data About backup data attributes Table B-1 Data Attributes Backup Media Is Imported NetBackup data attributes (continued) Sample Data Yes/No Explanation A yes/no property of if the backup media was imported. 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 . A yes/no property of if the physical media is expired or not. Since capacity of a tape is often estimated using an algorithm. 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. It also is commonly used to import Backup Exec media to NetBackup. This specifies whether it was actually calculated. Imported media simply means that this paticular backup domain did not originally write the data to the media. or provided exactly by the DP product. Multiple expiration dates means that the whole tape can not be reused until the last backup has expired on the media. 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 .Attributes of NetBackup data About backup data attributes 551 Table B-1 Data Attributes Backup Media Last Write Time NetBackup data attributes (continued) Sample Data 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. 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. 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. Tape Type Backup Media Total Capacity 19. This is used to match what drives the media can go in for a mixed media environment. The density or type of media. DLT. 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.00. The number of images that are unexpired on a given piece of media Backup Media Snapshot Time Backup Media Storage Disk. 2. 1209600. 8MM etc.000.00 The retention level of the media in number of seconds. Backup Media Unexpired Image Count 1. The type of storage for a given piece of media (disk or tape) Total capacity of the tape in KB.000 KB Backup Media Type HCART.552 Attributes of NetBackup data About backup data attributes Table B-1 Data Attributes NetBackup data attributes (continued) Sample Data Explanation 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. . 31536000. 3 etc.00. History is kept so a history of the state of all media can be determined. This number may be estimated using an algorithm. 000 KB Explanation Amount in KB used up in the tape.Attributes of NetBackup data About backup data attributes 553 Table B-1 Data Attributes NetBackup data attributes (continued) Sample Data 500. Specific to NetBackup 6. This value is provided by the DP product and is NOT estimated. Path C:\disk_staging\ The path on disk where backup images are stored.5 .5 .this is the high water mark that is set for a Flexible Disk pool. 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% . 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’. OpenStorage disk pool or PureDisk backend storage pools. 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. OpenStorage disk pool or PureDisk backend storage pools. Specific to NetBackup 6. 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/.this is the low water mark that is set for a Flexible Disk pool. this tells if the disk pool is UP meaning it is usable and can be used or DOWN meaning it is not usable. Disk Pool Raw Size 69.990. DOWN . Disk Pool Name netappfi::fas3050-1a.example. SharedDisk Disk Pool Snapshot Time Mon 3/4/2008 3:34:34 Disk Pool Status UP. 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.com 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. 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. When in the DOWN state jobs will not attempt to use the disk pool. DDPool.40 Disk Pool Server Type AdvancedDisk.554 Attributes of NetBackup data About backup data attributes Table B-1 Data Attributes Disk Pool Master Server NetBackup data attributes (continued) Sample Data nbu-master. etc. 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.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. 2. Optical media header size of a backup image The Media ID for a given piece of media.208. For NetBackup this is a 6-digit ID. etc. Disk Pool Usable Size Disk Pool Volume Count 4 Media Density HCART. usually a subset of the barcode. 1. Media Hsize 1024 Media ID JFP000 Media Image Count 54 Media L Offset 2048 Media Restore Count 0. 3. DLT.Attributes of NetBackup data About backup data attributes 555 Table B-1 Data Attributes NetBackup data attributes (continued) Sample Data 1. For NetBackup this is also called the ‘density’ and specifies what types of drive the tape can go in. Media Ssize 1024 . Optical media sector size of a backup image. 8MM etc. etc. 3. Things like Scratch Pools or onsite/offsite pools are typically also used and these all have unique volume pool ID's. 4 etc. If on side A of a platter this would show Side B The backup product that this piece of media belongs to Product NetBackup. 1. Active meaning it is being used at a given point in time. Suspended. The default is NetBackup but many others are typically created to segment tapes in to groups Volume Pool ID Volume Pool Name NetBackup. The volume pool ID which automatically starts at 1 for the default pool "NetBackup". Scratch. Frozen The status of a given piece of media. TSM Status Active. CatalogBackup. etc. Frozen meaning errors have occurred on the tape media and it is no longer being used for backups. Non-active. 2. 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. WORM. MSEO.556 Attributes of NetBackup data About backup data attributes Table B-1 Data Attributes Partner NetBackup data attributes (continued) Sample Data A/B Explanation The ID of the opposite side of a optical platter. . example. The device database server that is controlling the particular library. The serial number.com Explanation The name of the Volume Database (pre-NetBackup 6. Tape Library Attributes Tape Library Agent Product NetBackup.com Tape Library Manufacturer STK. This is the Enterprise Media Manager server (EMM) in NetBackup 6.com Tape Library Device Database Server NBU-device-host.) or EMM server (NetBackup 6.Attributes of NetBackup data About backup data attributes 557 Table B-1 Data Attributes Volume/EMM Database Server NetBackup data attributes (continued) Sample Data nbu-master. to each tape library The total number of slots that exist in a tape library Tape Library Agent Server ops-agent. 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 Serial Number ADIC203100468_LL0 Tape Library Slot Count 40. 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. Quantum.0+ or the device control host in 5. The manufacturer as determined by the SCSI inquiry string in the backup application. IBM etc. 360 .1 and below. unique.0+). 120.example.example. Number 0.ULTRIUM-TD2. 2. Tape Library Unique ID Tape Drive Attributes Name IBM. This ID is put together with the library type in the NBU GUI to show TLD(0). Tape Library 8MM. 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. 1. 2 etc. TLD(1) etc. TLM. 8MM. The type of tape library Tape Library ACS (TLD. 3 etc. Shared true/false Tape Drive Device Host NBU-device-host. 4MM.example.com . TLH etc) 0.000 The name of a tape drive as given by the backup application. 1. ACS.558 Attributes of NetBackup data About backup data attributes Table B-1 Data Attributes Tape Library Type NetBackup data attributes (continued) Sample Data Explanation Tape Library DLT. The unique number given to each tape library in the EMM database. 5. DOWN-ACS etc. 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.com Tape Drive Control TLD. 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. 3. hcart2. 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 . 4. DOWN-TLD. 6 etc.example. For NetBackup this is also called the ‘density’ and specifies what types of tape can go in the drive. dlt. Tape Drive Unique ID for Library Tape Usage Attributes Storage Unit Group Name 1.Attributes of NetBackup data About backup data attributes 559 Table B-1 Data Attributes NetBackup data attributes (continued) Sample Data 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. 2. ACS. 8mm etc. com Backup Log Daemon Name bptm. 2008 22:57:17 Backup Log Attributes Backup Log Agent Server ops-server.example.example. nbpem.example. ndmpagent.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.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.560 Attributes of NetBackup data About backup data attributes Table B-1 Data Attributes NetBackup data attributes (continued) Sample Data 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. bpbrm . Version 1. 2. Agent Monitoring Agent Configuration ID 1. that is to group the jobs in some way that is useful in reporting. 3. Type Code 1. TSM Severity Code 1. 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. Note:The secondary ID and the Group ID are basically intended for the same purpose. 4 etc. 3.Attributes of NetBackup data About backup data attributes 561 Table B-1 Data Attributes NetBackup data attributes (continued) Sample Data Explanation The group ID that can be specified by the backup product to group them in a certain way. 4 etc. 2. 4 etc. 2. 3. 3. 2. 4 etc. A unique number for each data collection agent under the OpsCenter server . 562 Attributes of NetBackup data About backup data attributes Table B-1 Data Attributes Agent Host NetBackup data attributes (continued) Sample Data ops-agent.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.example. 2008 10:52:28 Server ops-server.example.com Time Since Agent Last 44 Heartbeat . Appendix C Man pages for CLIs . --restoreDefault Resets all passwords to default passwords. since the server needs to retrieve the password it cannot be stored with a one-way hash. 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. This is supported only for DBA user and not for guest and server passwords. Thus. The password is encrypted before it is stored in the configuration file. The dba account is required by the database queries that are used to update the database schema or upgrade to a new product version. OPTIONS --setDBAPassword Changes the database DBA password. the system administrator is advised to check the permissions on the configuration file to ensure that only an administrator can read the file. When the tool changes the dba password. When the tool is run. . The following database user account is shipped with OpsCenter: dba The database administrator account.564 Man pages for CLIs changeDbPassword changeDbPassword changeDbPassword – This script changes the OpsCenter database password. However. it updates a configuration file on the file system so that the server can still access the database. --h|-?|--help Shows the CLI usage statement and exits. someone could obtain the password. Man pages for CLIs changeVxATProperties 565 changeVxATProperties changeVxATProperties – This script configures the Symantec Product Authentication Service (AT) Server parameters. SYNOPSIS changeVxATProperties 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 . xml of Tomcat -httpsPort <httpsPort> Modifies the httpsPort to the new value in web. https and Tomcat shutdown ports This option is to be used exclusive of other attributes.sh [-status]|[-httpPort <httpPort>][-httpsPort <httpsPort>][-shutdownPort <shutdownPort>] DESCRIPTION The configurePorts script is used for the following purposes: ■ ■ For configuring http.566 Man pages for CLIs configurePorts configurePorts configurePorts – This script is used to configure Web server ports on Unix or Linux systems. SYNOPSIS configurePorts.xml of Tomcat . run the following command: /opt/SYMCOpsCenterWebGUI/bin/goodies/configurePorts.bat -status On UNIX. run the configurePorts utility. https and Tomcat shutdown ports For querying the current values for the above ports OPTIONS -status Queries the current values for http. run the follwoing command: INSTALL_PATH\OpsCenter\gui\bin\goodies\configurePorts. -httpPort <httpPort> Modifies the httpPort to the new value in web.xml of Tomcat NOTES To know the HTTP and HTTPS port that OpsCenter uses.shutdownPort <shutdownPort> Modifies the shutdownPort to the new value in web. On Windows.sh -status . you perform backups with the dbbackup.db and vxpmdb. starting and stopping the data space file is not required. OPTIONS backupDir (Required) backupDir is the directory where the OpsCenter database is backed up to.log Data spaces are started when the main database is started. restore restoreDir (Optional) restoreDir is the directory where the OpsCenter database is restored. EXAMPLES The following command backs up the OpsCenter database to the my_db_backups directory: /opt/SYMCOpsCenterServer/bin/dbbackup /my_db_backups . If logfile is unspecified. restoreDir should be an absolute path.bat batch file. NOTES On Windows. dbbackup restores the database to the default data directory (/var/symantec/OpsCenterServer/data). output is written to the current directory. If not included. The backup script creates the following files in the backup directory: vxpmdb. therefore. or restored from. -o logfile Record backup and restore actions to a log file.Man pages for CLIs dbbackup 567 dbbackup dbbackup – This script backus up the OpsCenter database. backupDir should be an absolute path. SYNOPSIS dbbackup {backupDir | -restore [restoreDir]} [-o [logfile]] DESCRIPTION dbbackup is a script used for backing up the OpsCenter database. OPTIONS Not applicable NOTES To defragment the OpsCenter database run the following commands. On Windows: INSTALL_PATH\OpsCenter\server\bin\dbdefrag. SYNOPSIS dbdefrag DESCRIPTION The dbdefrag script is used to defragment the OpsCenter database.bat On UNIX: /opt/SYMCOpsCenterServer/bin/dbdefrag.568 Man pages for CLIs dbdefrag dbdefrag dbdefrag – This script defragments the OpsCenter database.sh . EXAMPLES EXAMPLE 1 The following command starts all OpsCenter services: /opt/SYMCOpsCenterServer/bin/opsadmin. This includes OpsCenter database. OPTIONS start Starts all OpsCenter services. stop Stops all OpsCenter services. OpsCenter server and Web server services.sh {start|stop|monitor} DESCRIPTION The opsadmin script is used for monitoring/starting/stopping the OpsCenter services. This includes OpsCenter database. OpsCenter server and Web server services.sh resides by default in the /opt/SYMCOpsCenterServer/bin directory.sh start EXAMPLE 2 The following command monitors OpsCenter services: . monitor Monitors all OpsCenter services and also AT (Symantec Product Authentication Service) and PBX (Symantec Private Branch Exchange)services NOTES opsadmin opsadmin.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. 570 Man pages for CLIs opsadmin /opt/SYMCOpsCenterServer/bin/opsadmin.sh monitor . C:\Program Files\Symantec\OpsCenter\Agent\bin> .. This will be deleted. SYNOPSIS opsCenterAgentSupport DESCRIPTION The opsCenterAgentSupport script collects OpsCenter Agent configuration files and logs for troubleshooting..sh You can view the following statuses on the command prompt: Stopping the OpsCenter Agent Service..Man pages for CLIs opsCenterAgentSupport 571 opsCenterAgentSupport opsCenterAgentSupport – This script collects OpsCenter Agent configuration files and logs. Created Support Directory.zip Starting the OpsCenter Agent..zip file from C:\PROGRA~1\Symantec\OPSCEN~1\Agent\temp\support.. Please collect Support..bat On UNIX: /opt/SYMCOpsCenterServer/bin/opsCenterAgentSupport.. Zipping Support Folder. OPTIONS Not applicable NOTES Run the following commands to execute the support scripts for OpsCenter Agent: On Windows: INSTALL_PATH\OpsCenter\Agent\bin\opsCenterAgentSupport..... Support Directory Deleted.. Support Directory Exists. ... This will be deleted...bat You can view the following statuses on the command prompt: Stopping the OpsCenter Web Console Service.. Created Support Directory.sh On Windows: INSTALL_PATH\OpsCenter\server\bin\opsCenterSupport. Support Directory Deleted.. SupportDir=E:\OPSCEN~1\OPSCEN~1\server\temp\support Collecting Installed Paths Collecting System Properties Collecting Memory & Processor Properties .. OPTIONS Not applicable NOTES Run the following command to collect OpsCenter server configuration information: On UNIX: /opt/SYMCOpsCenterServer/bin/opsCenterSupport. SYNOPSIS opsCenterSupport DESCRIPTION opsCenterSupport is a script used for collecting OpsCenter server configuration files and logs for troubleshooting..572 Man pages for CLIs opsCenterSupport opsCenterSupport opsCenterSupport – This script collects OpsCenter server configuration files and logs for troubleshooting.. Stopping the OpsCenter database. Support Directory Exists. Stopping the OpsCenter Server... Please collect Support......log file......Man pages for CLIs opsCenterSupport 573 Collecting Disk Allocation for OpsCenter Installed Drive Collecting Directory Structure for OpsCenter Collecting version file Collecting Version File..zip file from E:\OPSCEN~1\OPSCEN~1\server\temp\support. Starting the OpsCenter Server..zip Starting the OpsCenter Database.. Do you want to Collect db Log files [y/n]: (y)y Collecting db logs. If this is an install scenario Do you want to Collect Installation Logs [y/n]: (y)y Zipping Support Folder.. Do you want to Collect WebServer Log files [y/n]: (y)y Collecting WebServer logs. 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.... Getting Customized Collections. Do you want to Collect Database files [y/n]: (y)y Collecting vxpmdb file. Collecting vxpmdb. . Do you want to Collect OpsCenter Server(148) Log files [y/n]: (y)y Collecting 148 files. Collecting upgrade logs...... 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 setEnv file [y/n]: (y)y Collecting setenv file..... C:\Documents and Settings> .574 Man pages for CLIs opsCenterSupport Starting OpsCenter Web Console Service... 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 . OPTIONS Not applicable NOTES Enter the following command to start the OpsCenter Agent process on a UNIX machine: /opt/SYMCOpsCenterAgent/bin/startagent .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. enter the following command: /opt/SYMCOpsCenterServer/bin/startdb . OPTIONS Not applicable NOTES To start the database server.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. sh script by default resides in the /opt/SYMCOpsCenterGUI/bin directory. SYNOPSIS startgui.578 Man pages for CLIs startgui startgui startgui – This script is used to start the OpsCenter Web server service on Unix or Linux systems.sh .sh DESCRIPTION The startgui script is used for starting the OpsCenter Web server service. The following command starts the OpsCenter WebServer service: /opt/SYMCOpsCenterGUI/bin/startgui. OPTIONS Not applicable NOTES The startgui. OPTIONS Not applicable NOTES Run the following command to start the OpsCenter Server: /opt/SYMCOpsCenterServer/bin . SYNOPSIS startserver DESCRIPTION The startserver script is used to start the OpsCenter Server.Man pages for CLIs startserver 579 startserver startserver – This script starts the OpsCenter Server. OPTIONS Not applicable NOTES Run the following command to stop the OpsCenter Agent: /opt/SYMCOpsCenterAgent/bin/stopagent .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 database: /opt/SYMCOpsCenterServer/bin/stopdb .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. 582 Man pages for CLIs stopgui stopgui stopgui – used to stop the OpsCenter Web server service on Unix or Linux systems.sh . The following command stops the OpsCenter Web server service: /opt/SYMCOpsCenterGUI/bin/stopgui.sh DESCRIPTION The stopgui script is used for stopping the OpsCenter Web server service. SYNOPSIS stopgui.sh resides by default in the /opt/SYMCOpsCenterGUI/bin directory. OPTIONS Not applicable NOTES stopgui. OPTIONS Not applicable NOTES Run the following command to stop the OpsCenter Server. SYNOPSIS stopserver DESCRIPTION The stopserver script is used to stop the OpsCenter Server. /opt/SYMCOpsCenterServer/bin/stopserver .Man pages for CLIs stopserver 583 stopserver stopserver – This script stops the OpsCenter Server. 584 Man pages for CLIs stopserver . The generated alerts are stored in the Symantec OpsCenter database. a console area in which to display and run reports saved by the user. which help them take corrective actions. displaying and managing reports. 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. You can view them using the Alerts section in the Symantec OpsCenter console. In Symantec OpsCenter.usually an alarming situation .occurs in the system. managing workflow.Glossary Agent Alerts See Symantec OpsCenter Agent An alert is a warning that the Symantec OpsCenter application generates when a specific condition . A component that is used by the Symantec products to provide user authentication. and other tasks. Data collector is a part of Symantec OpsCenter Agent that collects data from various products. cost metrics and chargeback Alert Manager Data Collector event My Reports Symantec Product Authentication Service Symantec Private Branch Exchange Symantec OpsCenter console Symantec OpsCenter database . client connections sent to the exchange's port are redirected to an extension associated with the Symantec OpsCenter Server. Sybase SA (SQL Anywhere) database management system containing data related to backup /archive service usage and expenditure. You can notify the concerned officials about the alerts by sending an email or an SNMP trap. A notification that indicates when an action. A graphical user interface that displays reports and other information for users of Symantec OpsCenter through a standard Web browser. In the PBX exchange. 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. has occurred for one or more objects in the data center. The console provides a central point to manage cost analysis and chargeback for services. A common Symantec component that uses socket passing to reduce the number of ports required to be open across a firewall. such as an alert or a change in state. 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. such as Symantec NetBackup. and alerts. Symantec OpsCenter formats the information collected from these applications and displays it through the Symantec OpsCenter console. This normalized data is used for reporting on backup related information. Symantec OpsCenter The unlicensed version of OpsCenter is called Symantec OpsCenter. Symantec Backup Exec. is a Web application that normalizes backup or archive data collected from various applications. Symantec OpsCenter Server. Symantec OpsCenter is a Web-based software application that helps organizations by providing visibility into their data protection environment. EMC Legato Networker. Symantec OpsCenter Server Symantec OpsCenter View Builder Views . Symantec OpsCenter Analytics lets you do advanced business-level reporting. or Entreprise Vault. You can create views in Java View Builder and make them available in the Symantec OpsCenter console.586 Symantec OpsCenter Glossary formulas.. modifies. Symantec OpsCenter views are logical groups of IT assets (hosts or file systems) organized in a hierarchical manner. Symantec OpsCenter lets you do operational reporting Symantec OpsCenter Analytics Symantec OpsCenter Agent The licensed version of OpsCenter is called Symantec OpsCenter Analytics. The following view details appear in the Symantec OpsCenter console. The Symantec OpsCenter Java View Builder is an application in which an administrator creates. and manages access to the Symantec OpsCenter views that users see in the console. the core of the architecture. Symantec OpsCenter database is installed silently when you install Symantec OpsCenter Server. A Symantec OpsCenter component that collects information from discoverable applications residing on remote host systems. 0 master server 279 adding existing user 239–240 new user 239–240 adding host alias 230 adding licenses 226 adding users 235 Agent deploying 81 overview 29 Agent deployment 81 agent. 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 .Index A about Symantec OpsCenter 19 about Symantec OpsCenter Analytics 20 access OpsCenter console 34 ActiveX 33 add master server 278 NetBackup 7. 253 chargeback (continued) formulae 254 modeling 255 cluster 166.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. 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 239–240 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 .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 239–240 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. 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 . 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.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. 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. 211. 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 .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. 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. 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.Index 591 OpsCenter user profiles 201 OpsCenter View Builder. 260 supported backup products 23 supported platforms 74 supported upgrade paths 81 Sybase cache size adjusting 159 Symantec Java Web Server (SymcOpsCenterWebServer) 68 . 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 .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. Index 593 Windows (continued) uninstalling OpsCenter 163 .