You are on page 1of 790

Symantec OpsCenter Administrator's Guide

Windows and UNIX

Release 7.1

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.1

Legal Notice
Copyright © 2011 Symantec Corporation. All rights reserved. Symantec and 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

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 support 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/or Web-based support that provides rapid response and up-to-the-minute information Upgrade assurance that delivers software upgrades Global support purchased on a regional business hours or 24 hours a day, 7 days a week basis Premium service offerings that include Account Management Services

■ ■

For information about Symantec’s support offerings, you can visit our Web site at the following URL: www.symantec.com/business/support/ All support services will be delivered in accordance with your support agreement and the then-current enterprise technical support policy.

Contacting Technical Support
Customers with a current support agreement may access Technical Support information at the following URL: www.symantec.com/business/support/ 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/business/support/

Customer service
Customer service information is available at the following URL: www.symantec.com/business/support/ Customer Service is available to assist with non-technical questions, such as 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 support contracts Information about the Symantec Buying Programs Advice about Symantec's technical support options Nontechnical presales questions Issues that are related to CD-ROMs or manuals

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

Contents

Technical Support ............................................................................................... 4 Chapter 1 Getting started using Symantec OpsCenter .................. 23
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 in Symantec OpsCenter 7.1 .................................... 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 Alert Summary pane ................................................. Using the content pane ........................................................... About the OpsCenter status bar ................................................ About status icons and colors in the console ................................ About using tables .................................................................. About quickly performing common tasks in OpsCenter ....................... 23 24 24 26 26 26 28 32 33 35 38 39 40 40 41 51 54 54 55 58 59 60 61 61 61 65 66 66 67 69 70 71 76

8

Contents

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

Chapter 2

Installing Symantec OpsCenter 7.1 ................................. 79
Planning an OpsCenter installation ................................................. 79 About the software components that OpsCenter uses .................... 79 About the OpsCenter licensing model ........................................ 81 About Symantec OpsCenter DVD's ............................................ 85 About OpsCenter platform compatibility .................................... 86 About OpsCenter compatible backup and archiving products ..................................................................................... 89 About managed NetBackup master server considerations .............. 91 Design your OpsCenter Server .................................................. 92 About supported upgrade paths ................................................ 95 About OpsCenter Agent deployment .......................................... 95 Before you install or upgrade .................................................. 101 Installing Symantec OpsCenter on Windows and UNIX ...................... 106 Installing Symantec OpsCenter 7.1 on Windows ......................... 107 Installing Symantec OpsCenter 7.1 on UNIX .............................. 111 Installing Symantec OpsCenter silently on Windows ................... 115 Upgrading to OpsCenter on Windows and UNIX ............................... 136 Upgrading from OpsCenter 7.0 or 7.0.1 to OpsCenter 7.1 .............. 136 Upgrading from NetBackup Operations Manager to Symantec OpsCenter 7.1 on Windows and UNIX ................................. 144 Upgrading from Veritas Backup Reporter to OpsCenter Analytics 7.1 on Windows and UNIX ................................................ 152 Monitoring data migration from NOM to Symantec OpsCenter ..................................................................... 169 Monitoring data migration from VBR to Symantec OpsCenter Analytics 7.1 .................................................................. 186 Upgrading to OpsCenter Server on a different Windows system .......................................................................... 201 Upgrading to OpsCenter Server on a different UNIX system ......... 206 Post-installation tasks ................................................................ 211 Verifying that Symantec OpsCenter is running properly .............. 211 About starting to use OpsCenter .............................................. 212 About the start-up tasks that OpsCenter performs ...................... 213 Tuning OpsCenter for more performance .................................. 213 Using an earlier NOM or VBR installation after upgrade .................... 229 Uninstalling Symantec OpsCenter on Windows and UNIX .................. 230 Uninstalling Symantec OpsCenter 7.1 on Windows ..................... 231 Uninstalling Symantec OpsCenter 7.1 on UNIX ......................... 231

Contents

9

Clustering Symantec OpsCenter .................................................... About a Symantec OpsCenter cluster ........................................ Supported OS and cluster solutions ......................................... About running commands on the active node ............................ Connecting Symantec Product Authentication Service and Symantec Private Branch Exchange ................................... Clustering Symantec OpsCenter on Windows ............................. Uninstalling Symantec OpsCenter 7.1 from the Windows cluster .......................................................................... Clustering Symantec OpsCenter Server on Solaris ...................... Upgrading from OpsCenter 7.0 (or 7.0.1) cluster to OpsCenter 7.1 cluster ..................................................................... Uninstalling OpsCenter Server completely from the Solaris cluster ..........................................................................

233 233 233 234 235 237 247 248 254 257

Chapter 3

Administering Symantec OpsCenter ............................. 259
About OpsCenter services and processes used by OpsCenter ............... Services used by OpsCenter on Windows ................................... OpsCenter server scripts on Windows and UNIX .............................. Commands to control OpsCenter services and processes .............. About dependency of services ................................................. About nbproxy processes on NetBackup master servers ............... About OpsCenter database administration ...................................... OpsCenter database commands ............................................... Moving the OpsCenter database and database logs to a different hard disk ...................................................................... About database troubleshooting .............................................. Configuring remote authentication service in OpsCenter ................... About backup and restore of OpsCenter and OpsCenter Analytics ............................................................................ Backing up OpsCenter in case of a disaster ................................ Restoring OpsCenter ............................................................. About communication and firewall considerations ........................... Communication ports used by key OpsCenter components .... 2 8 5 Ports required to communicate with backup products ................. 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 ................................................................ 259 260 263 264 266 266 267 267 272 276 276 278 278 281 284

287 288 289 290 290

10

Contents

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 ................................

290 290 291 294 294 296 298

Chapter 4

Understanding OpsCenter settings ............................... 301
OpsCenter settings ..................................................................... Setting user preferences .............................................................. Settings > User Preferences options ......................................... Changing your OpsCenter password ......................................... About managing licenses ............................................................. Settings > Configuration > License options ................................ Adding OpsCenter license keys ............................................... Viewing OpsCenter license keys .............................................. Deleting OpsCenter license keys .............................................. Configuring the data purge period on the OpsCenter Server ............... Settings > Configuration > Data Purge options ........................... Restarting the OpsCenter service after upgrading to Server 7.1 ............................................................................... Configuring SMTP server settings for OpsCenter .............................. Settings > Configuration > SMTP Server options ........................ Configuring Symantec ThreatCon feature in OpsCenter ..................... Settings > Configuration > ThreatCon options ........................... Adding host aliases in OpsCenter .................................................. Settings > Configuration > Host Alias options ............................ Merging objects (hosts) in OpsCenter ............................................. Settings > Configuration > Object Merger options ....................... Modifying tape library information in OpsCenter ............................. Settings > Configuration > Tape Libary options .......................... Copying a user profile in OpsCenter ............................................... Settings > Configuration > Copy User Profile options .................. Setting report export location in OpsCenter .................................... Settings > Configuration > Report Export Location options .......... About managing Object Types in OpsCenter .................................... Settings > Configuration > Object Type options .......................... Adding object types in OpsCenter ............................................ Deleting object types in OpsCenter .......................................... 302 304 304 307 307 307 308 308 308 309 309 310 311 311 312 313 313 314 315 315 316 316 317 318 318 318 319 319 319 320

Contents

11

Modifying object types in OpsCenter ........................................ Adding attributes to object types in OpsCenter ........................... Deleting attributes from object types in OpsCenter ..................... About managing Symantec OpsCenter users ................................... Settings > Users > Users options ............................................. User access rights and UI functions in OpsCenter ....................... Viewing OpsCenter user account information ............................ Adding new users to OpsCenter ............................................... Editing OpsCenter user information ......................................... Resetting a OpsCenter user password ....................................... Deleting OpsCenter users ....................................................... Viewing OpsCenter user groups .............................................. Settings > Users > User Groups options .................................... Adding OpsCenter user groups ................................................ Editing OpsCenter user groups ................................................ Deleting OpsCenter user groups .............................................. About managing recipients in OpsCenter ........................................ Viewing email recipients in OpsCenter ..................................... Settings > Recipients > Email options ....................................... Viewing SNMP trap recipients in OpsCenter .............................. Settings > Recipients > SNMP trap recipient options ................... Creating OpsCenter email recipients ........................................ Settings > Recipients > Email > Add Email Recipient options ......................................................................... Creating OpsCenter SNMP trap recipients ................................. Settings > Recipients > SNMP > Add SNMP trap recipient options ......................................................................... Modifying OpsCenter Email or SNMP recipient information ......... Deleting OpsCenter Email or SNMP trap recipient ...................... About managing cost analysis and chargeback for OpsCenter Analytics ............................................................................ Setting the default currency for OpsCenter cost reports .............. Settings > Chargeback > Currency Settings options .................... Editing the OpsCenter global currency list ................................ Settings > Chargeback > Currency Settings > Edit Currency List options ......................................................................... Settings > Chargeback > Cost Variable options ........................... Creating cost variables in OpsCenter ........................................ Modifying cost variables in OpsCenter ...................................... Deleting cost variables in OpsCenter ........................................ Settings > Chargeback > Cost Formulae options ......................... Creating cost formulae in OpsCenter ........................................ Modifying cost formulae in OpsCenter .....................................

320 320 321 321 322 322 326 327 327 328 328 329 329 329 330 330 330 331 331 332 332 333 333 334 335 336 336 337 337 338 338 339 339 340 342 342 343 343 343

12

Contents

Deleting a cost formulae in OpsCenter ...................................... 344 Estimating chargeback costs using the OpsCenter Formula Modeling Tool ................................................................ 344 Settings > Chargeback > Cost Estimation options ....................... 345

Chapter 5

Understanding data collection ....................................... 347
About data collection in OpsCenter ................................................ About OpsCenter Agents ........................................................ About OpsCenter Agent logs ................................................... OpsCenter Data Collector types ............................................... Backup and archiving products supported by Symantec OpsCenter 7.1 ................................................................ About managing OpsCenter Agents ................................................ Settings > Configuration > Agent options .................................. Viewing OpsCenter Agent status ............................................. Configuring an OpsCenter Agent ............................................. Settings > Configuration > Agent > Create Agent or Edit Agent options ......................................................................... Modifying an OpsCenter Agent ............................................... Deleting OpsCenter Agents .................................................... About managing OpsCenter Data Collectors .................................... Viewing OpsCenter Data Collector status .................................. Configuring an OpsCenter Data Collector .................................. Data Collector Wizard settings ................................................ Modifying an OpsCenter Data Collector configuration ................. Deleting OpsCenter Data Collectors ......................................... About configuring data collection for NetBackup .............................. Settings > Configuration > NetBackup options ........................... NetBackup data collection view ............................................... How OpsCenter collects data from NetBackup ............................ About the Breakup Jobs option ................................................ About NetBackup versions that OpsCenter 7.1 can monitor and manage ........................................................................ Viewing master server details and data collection status .............. Data collection status of a master server ................................... NetBackup data types and collection status ............................... Master server states in OpsCenter ........................................... Adding a master server in OpsCenter ....................................... Adding a NetBackup 7.0 or later master server ........................... Configuring a master server for server access and data collection by OpsCenter ................................................................. 347 348 349 349 351 353 354 355 355 356 356 357 357 357 358 359 360 361 361 362 363 364 366 372 372 373 374 376 377 377 379

Contents

13

Settings > Configuration > NetBackup > Add Master Server options ......................................................................... Adding a master server in the OpsCenter console ....................... Editing a master server in OpsCenter ....................................... Deleting a master server in OpsCenter ...................................... Controlling data collection for a master server in OpsCenter ..................................................................... Configuring Backup Exec data collector .......................................... Collecting data from PureDisk ...................................................... Setting up a trust between the PureDisk SPA host and OpsCenter AB host ......................................................................... Configuring PureDisk data collector ......................................... About collecting data from Enterprise Vault .................................... About Enterprise Vault .......................................................... About data collected from Enterprise Vault ............................... Versions supported by OpsCenter ............................................ Planning the Enterprise Vault data collector deployment ............. OpsCenter Agent deployment modes ........................................ Accessing MS SQL Server host ................................................ About creating a user for integrated logon ................................ Configuring the OpsCenter Agent properties for integrated logon ............................................................................ Installing MS SQL Server JDBC driver ...................................... Configuring Enterprise Vault data collector ............................... IBM Tivoli Storage Manager data collector variables and details ......... EMC NetWorker data collector variables .........................................

381 385 386 387 387 388 389 390 391 392 393 393 396 396 398 398 399 401 402 403 405 406

Chapter 6

Managing OpsCenter views

............................................ 409 409 411 412 413 413 414 414 414 415 415 415 416 416 417

About OpsCenter views ................................................................ Settings > Views options ........................................................ OpsCenter view types ............................................................ About accessing OpsCenter views ............................................ About OpsCenter view levels ................................................... About nodes and objects ........................................................ About managing OpsCenter views ................................................. Settings > Views > Manage Nodes and Objects options ................ Viewing OpsCenter views and their details ................................ Creating OpsCenter views ...................................................... Modifying OpsCenter views .................................................... Deleting OpsCenter views ...................................................... Modifying alias view levels in OpsCenter .................................. About managing nodes and objects in OpsCenter ..............................

14

Contents

Adding nodes to a view in OpsCenter .............................................. Modifying node details in OpsCenter .............................................. Deleting nodes in OpsCenter ......................................................... Adding objects to a view node in OpsCenter ..................................... Deleting objects from a view node in OpsCenter ............................... View filters in OpsCenter ............................................................. Creating a view object filter in OpsCenter .................................. Modifying view object filters in OpsCenter ................................ Deleting view object filters in OpsCenter ...................................

417 418 418 419 419 420 420 421 422

Chapter 7

Monitoring NetBackup using Symantec OpsCenter .....................................................................
About the Monitor views .............................................................. Controlling the scope of Monitor views ........................................... About time frame selection .................................................... About monitoring NetBackup using the Overview tab ........................ Viewing the Job Summary by State .......................................... Viewing the Media Summary by Status .................................... About Top 7 Job Error Log Summary ........................................ Viewing the Services Summary ............................................... Viewing the Master Server Summary ....................................... Viewing the Job Summary by Exit Status ................................... Viewing the Drive Summary by Status ...................................... About Top 7 Policies by Failed Jobs section ................................ Viewing the Alert Summary by Severity ................................... About monitoring NetBackup jobs ................................................. Monitor > Jobs List View options ............................................. About monitoring jobs using the List View ................................ Viewing the details for a single NetBackup job ........................... Viewing the details for a master server associated with a job ............................................................................... Viewing policy information for a job ........................................ Filtering on NetBackup job state .............................................. Controlling NetBackup jobs .................................................... Reconciling NetBackup jobs .................................................... Changing the job priority ....................................................... Change Job Priority dialog box options ..................................... Exporting NetBackup job logs ................................................. About using the Summary View for monitoring jobs ................... Viewing the Job Summary by Exit Status ................................... Viewing the Job Summary by State .......................................... Viewing the Job Summary by Type ...........................................

423 425 425 426 427 427 428 429 429 429 430 431 432 432 433 434 437 437 438 438 438 439 440 441 441 442 442 443 444 445

Contents

15

About the Group Component Summary table ............................. About using the Hierarchical View for monitoring jobs ................ Viewing the details for a single NetBackup job ........................... Viewing the details for a master server associated with a job ............................................................................... Viewing policy information for a job ........................................ Filtering on NetBackup job state .............................................. Monitor > Services view ............................................................... Filtering on NetBackup service type ......................................... Controlling NetBackup services ............................................... About monitoring NetBackup policies ...................................... Monitor > Policies List View ................................................... About using the List View to monitor NetBackup policies ............. Filtering on NetBackup policy type .......................................... Monitor > Policies page ......................................................... Viewing details for a single NetBackup policy ............................ Viewing the details for a master server associated with a policy ........................................................................... Viewing the details for a volume pool associated with a policy ........................................................................... Activating or deactivating a job policy ...................................... Starting a manual backup ...................................................... Viewing the history for a single job policy ................................ Monitor > Policies Summary View ........................................... About Top 5 Policies by Data Backed up section ......................... About Top 7 Policies by Failed Jobs section ................................ About Top 7 Policies by No. of Jobs section ................................ About monitoring NetBackup media ........................................ Monitor > Media List View options ........................................... About using the List View to monitor NetBackup media ..................... Viewing the details for NetBackup media ........................................ Viewing the details for a master server associated with the media ................................................................................. Filtering on NetBackup media type ................................................ Controlling media ....................................................................... Monitor > Media Summary View options ........................................ About using the Hierarchical View by Volume Pool for monitoring media ................................................................................. Viewing the details for volume pool ............................................... Viewing the details for media ....................................................... Controlling media ....................................................................... About using the Hierarchical View by Volume Group for monitoring media .................................................................................

445 447 448 449 449 450 451 452 452 453 454 456 456 457 458 458 458 459 459 460 460 461 461 461 462 463 465 465 466 466 467 468 468 469 469 470 470

............. Viewing the details of a master server that is associated with a media server ... Monitoring Audit Trails .......................... Monitor > Hosts > Media Servers view ................................. About monitoring NetBackup alerts .......................................................... Monitor > Devices > Disk Pools options ................................ Viewing the details for a single disk pool ............................ Monitor > Alerts List View ................................ Viewing the details for media ......................................................................................... About Audit Trails ...................................... Monitoring NetBackup devices ....... Viewing the Drive Summary by Status ........................................................................................................................................................................................ About the Audit Trails report ........................ About using the List View to monitor NetBackup alerts ............................................................................................................................................................. About using the List View for monitoring drives ............................................................................................................... 471 471 472 472 473 475 475 476 476 477 477 478 478 480 480 481 481 482 483 483 484 484 485 486 486 487 487 488 491 491 492 492 493 493 494 494 ............................16 Contents Viewing the details for a volume group .. About OpsCenter features for Audit Trails ......................................................................... Responding to alerts ... Monitor > Hosts > Master Servers view ......................................................... About monitoring NetBackup hosts ............................................................................ Viewing the details for a master server associated with a drive ........ Viewing the details for a single drive ...................................................................... Managing Audit Trails settings .......................... Viewing the details for a single alert . About using the Summary View for monitoring NetBackup alerts ......................................... Controlling drives .. Filtering by alert type ............................................ Monitor > Devices > Drives List View options .................................................................... Viewing alerts by severity ...... Controlling media in OpsCenter ............................................................................................... Viewing the details for a single master server ............................. Monitor > Hosts > Clients view ...... Monitoring Audit Trails .......................................................... Filtering on NetBackup drive category ...................................... Filtering by NetBackup master server type and status ..... Monitor > Devices > Drives Summary View ....... Viewing the details of the alert policy associated with an alert .............................................................................................................................

............ Compiling data for the report ................................................................................................. 545 About Guided Recovery ... Manage > Storage > Storage Lifecycle Policy view ..... Pre-operation checks ........................... About creating (or changing) an alert policy ... Selection summary screen ....................................... Managing an alert policy ..................................................... Manage > Devices > FT Server view ................... Job Details screen ........................ About possible Capacity License report issues ............. 545 546 547 547 549 549 549 550 551 552 552 552 ...............Contents 17 Chapter 8 Managing NetBackup using Symantec OpsCenter ..................................... Performing a cloning operation .......... Manage > Devices > Robot view ................................................................................................................................................................................................................................................................................ Pre-clone check screen ..... Select Master Server screen ....................................................................................................................................................................................................................... Setting up for cloning .............................. About managing NetBackup devices .................................................................................. Viewing the alerts associated with an alert policy .............................................................................................. 497 497 498 499 499 500 500 501 517 518 518 519 521 522 523 524 528 530 532 533 535 535 536 536 537 537 543 Chapter 9 Guided Recovery ....................................... Generating a Capacity Licensing report ..................................... About managing NetBackup storage ........... Manage > Devices > Disk Pool view ............................................................ Manage > Devices > Drive view ....... Managing Audit Trails settings ............................. Destination Parameters screen ...................................................... About managing NetBackup Deployment Analysis ...................... About the Manage views ............................................................. About Capacity License report ......................................... Select Source Database screen ...................... Manage > Devices > SAN Client view ....................................... Manage > Storage > Storage Unit view ..................................... Destination host and login screen ................... Filtering on type of alert policy ... Manage > Storage > Storage Unit Group view .................. About OpsCenter alert policies ................. About managing alert policies ................................................................... Select Control File Backup screen ............................................. Controlling the scope of Manage views ......................................... About managing NetBackup Hosts .......................................................................... Viewing the details for a single alert policy ........................................................................................................................

..............51 on Windows ....................... About report filters in OpsCenter ................................... Configuring the SNMP trap community name for OpsCenter ................................ About SNMP versions ............................................... 552 553 553 554 554 Chapter 10 Understanding and configuring OpsCenter alerts ................................ Configuring the SNMP version for sending SNMP traps ........ Save report and email report dialog boxes ....................................................... 579 About OpsCenter reports .... Alert descriptions in OpsCenter ................................................. About managing reports in OpsCenter ............................... Troubleshooting Guided Recovery ........ About managing OpsCenter alerts using Microsoft System Center Operations Manager 2007 ........................18 Contents Post-clone operations ........................... About SNMP ............ SNMP traps ....................................................... OpsCenter reports UI ........................................ Report creation wizards in OpsCenter ... Creating an OpsCenter report using a Report Template .......................................................................................................................... Reports > Report Templates ......................................................................................................... About custom reports in OpsCenter ........................ 557 557 558 558 559 559 559 562 574 575 576 577 577 578 Chapter 11 Reporting in OpsCenter .................................... About managing OpsCenter alerts using HP OpenView Network Node Manager 7.................................................................................. Report Templates in OpsCenter ...... About custom SQL query in OpsCenter ........................... Troubleshooting files for Guided Recovery validation operations ......................................................... Troubleshooting files for Guided Recovery cloning operations ......... 579 580 581 581 582 582 583 584 585 586 586 588 ............................................................................ About using SNMP with OpsCenter ................................................................................................................................................................. Frequently asked SNMP and OpsCenter questions .............................................................................................................50/7....................... Saving an OpsCenter report ..................... Troubleshooting files for metadata collection operations at the time of the backup .................. SNMP versions supported in OpsCenter ........................................... About the Management Information Base (MIB) and OpsCenter support ........................ Alert configuration settings in OpsCenter ..................................................................................................................................................................................

................................................................................................................. Creating a custom report in OpsCenter ........................... Editing a saved report using the My Reports tab ................................................ Viewing time schedule details .......................................... About managing My Reports ....... Adding email recipients to an OpsCenter report mailing ...................... Creating a report using the My Reports tab ............... Viewing a saved report using the My Reports tab .. Add email recipients dialog box options .................. Reports > Schedules > Create or Edit Time Schedule options .................. Creating a time schedule .......... Enabling or disabling a report schedule .................. Editing a time schedule ....................................................................... Deleting reports from a folder in OpsCenter ............................. About OpsCenter report conditions ................................................................................ File formats available in OpsCenter ............... Adding a reports folder in OpsCenter ............... Emailing a saved report ........................................................................ Adding reports to a dashboard ......................... Reports > Manage Folders options .............. Reports > My Dashboard options . Viewing report schedule details in OpsCenter .................................................................................................................................... Report Schedule Wizard ................. Modifying a dashboard section ..................................................................................................................................................... Reports > Schedules options .............Contents 19 Exporting an OpsCenter report ..................... 588 589 589 590 590 591 591 592 593 593 594 594 594 595 595 596 597 597 597 598 598 599 599 599 599 600 601 601 601 603 604 605 605 607 609 610 610 610 610 611 611 612 .............. About managing report schedules in OpsCenter ....................................................................................................................... About managing time schedules in OpsCenter ............................ Deleting a report schedule in OpsCenter ............................................................ Using report schedules in OpsCenter .................................................... Deleting a saved report using the My Reports tab .................................. Emailing dashboard sections ........................ Editing a reports folder in OpsCenter .................................................................. Refreshing My Dashboard .. Creating an OpsCenter report using SQL query ............................................. Creating a report schedule in OpsCenter ............... About managing My Dashboard ................................................................ About managing reports folders in OpsCenter ........................................................................................... Deleting a dashboard section . Editing a report schedule in OpsCenter ...................................... Deleting reports folders in OpsCenter .............. Exporting a saved report .................................. Emailing a report in OpsCenter ................................................................................

........................................................................................................................... About Policy reports in OpsCenter ........................ dbbackup ................................................................................................... 709 Backup data attributes ............... changeVxATProperties ................................. About Scenario 1: Common Root Broker ..... 742 744 745 746 747 748 750 751 753 754 755 ........................................................... Setting up a trust between the OpsCenter AB host and PureDisk SPA host ........ dbdefrag ........................................................................................................................................... Workload Analyzer ........................................................................................................... About Backup reports in OpsCenter .......................................................20 Contents Deleting a time schedule ................................. 709 Man pages for CLIs .............. 741 changeDbPassword ................................................................................ About Client reports in OpsCenter .......................................................... About Restore reports in OpsCenter ........................ opsCenterSupport .................................... 6 4 4 About Media reports in OpsCenter ........................................ startdb ................................................. About Report Templates descriptions ........................................................................................... configurePorts .......... About Performance reports in OpsCenter .............. 703 About AT configuration scenarios specific to PureDisk backup product ........................................................................................................................................................................................................................ startagent .............. About Scenario 2: Different Root Brokers ...... 612 612 613 616 617 636 637 638 647 651 654 657 657 693 Appendix A Additional information on PureDisk data collection ..................................................................................................... About Enterprise Vault Archiving reports in OpsCenter ........................................................................... runstoredquery .......................................................................................................................................... About Chargeback reports in OpsCenter . About Disk and Tape Device Activity reports in OpsCenter ......................................................... About Audit reports ..... About Storage Lifecycle Policy reports ................ About Catalog reports in OpsCenter ................................. 703 704 705 707 Appendix B Appendix C Attributes of NetBackup data ............................ opsCenterAgentSupport .......................................... opsadmin ...........................................

Contents

21

startgui .................................................................................... startserver ................................................................................ stopagent .................................................................................. stopdb ...................................................................................... stopgui ..................................................................................... stopserver .................................................................................

756 757 758 759 760 761

Appendix D

Creating views using CSV, TSV, and XML files ............ 763
About using CSV, TSV, and XML files to create views ........................ About creating CSV files .............................................................. About creating TSV files .............................................................. About creating XML files ............................................................. XML DTD structure ..................................................................... DTD elements ........................................................................... DTD <application> element .......................................................... DTD <objects> and <object> elements ............................................ DTD <attribute> elements ............................................................ DTD <view> element ................................................................... DTD <node> elements ................................................................. DTD <aliaslevel> elements ........................................................... Examples of XML files ................................................................ Example 1: Adding an object ......................................................... Example 2: Adding a view ............................................................. Example 3: Updating an object ...................................................... Example 4: Merging objects .......................................................... 764 764 766 769 770 771 771 771 773 773 774 774 775 775 776 777 778

Symantec OpsCenter Glossary ..................................................................... 781 Index ................................................................................................................... 783

22

Contents

Chapter

1

Getting started using Symantec OpsCenter
This chapter includes the following topics:
■ ■ ■ ■ ■ ■ ■ ■ ■

About Symantec OpsCenter About what's new in Symantec OpsCenter 7.1 About OpsCenter components About using the OpsCenter console About starting the OpsCenter console About OpsCenter console components About quickly performing common tasks in OpsCenter About using Web browser bookmarks About OpsCenter documentation

About Symantec OpsCenter
Symantec OpsCenter is a Web-based software application that helps organizations by providing visibility into their data protection environment. By using Symantec OpsCenter, you can track the effectiveness of backup and archive operations by generating comprehensive reports. OpsCenter is a convergence of NetBackup Operations Manager (NOM) and Veritas Backup Reporter (VBR) and is available in the following two versions:

24

Getting started using Symantec OpsCenter About Symantec OpsCenter

Symantec OpsCenter

This OpsCenter version does not require any license. Symantec OpsCenter provides single deployment configuration and user interface for monitoring, alerting, and reporting functionality. These features were previously available in NOM and VBR. Symantec OpsCenter Analytics is the licensed version of OpsCenter. In addition to the features available in the unlicensed OpsCenter version, Analytics offers report customization, chargeback reporting and support for third-party data protection products. These features were available in VBR.

Symantec OpsCenter Analytics

Note: OpsCenter 7.1 supports upgrades from NOM and VBR. For details on OpsCenter upgrade from NOM and VBR and data migration, refer to the Installing Symantec OpsCenter 7.1 chapter.

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

Monitor NetBackup setups Manage or administer NetBackup set up Note that OpsCenter can only monitor and manage NetBackup. It cannot monitor or manage other products like Symantec NetBackup PureDisk, Symantec Enterprise Vault etc. Generate alerts depending on conditions that you have defined Provide operational reporting on the following Symantec products:
■ ■ ■ ■

■ ■

Symantec NetBackup Symantec NetBackup PureDisk Symantec Backup Exec Symantec Enterprise Vault

About Symantec OpsCenter Analytics functions
The licensed version of OpsCenter is called Symantec OpsCenter Analytics. Symantec OpsCenter Analytics can perform the following functions:

Monitor NetBackup setups

Getting started using Symantec OpsCenter About Symantec OpsCenter

25

Manage or administer NetBackup setups See “ About monitoring and managing NetBackup” on page 26. Note that Symantec OpsCenter Analytics can only monitor and manage NetBackup. It cannot monitor or manage other products like Symantec NetBackup PureDisk, Symantec Enterprise Vault, Symantec Backup Exec etc. Generate alerts depending on conditions that you have defined See “About alerting in OpsCenter” on page 26. Create and customize views using Java View Builder Provide 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 NetWorker IBM Tivoli Storage Manager

Provide chargeback, custom, and custom SQL reports

Symantec OpsCenter Analytics displays customizable, multi-level views of backup and archive resources and customizable reports for tracking service usage and expenditures. It also contains tools for defining cost metrics and chargeback formulas or handling alerts. A wide range of audiences can benefit from the reporting and management capabilities of Symantec OpsCenter Analytics. The audiences include IT (Information Technology) managers, application owners, IT finance teams, external compliance auditors, legal teams, line-of-business managers, external customers, IT architects, and capacity planning teams. The primary objectives of Symantec OpsCenter Analytics are as follows:

Help organizations assess their compliance with business standards by allowing them to accomplish the following:

Help organizations to establish the service level agreements by reporting on them Report to legal departments, auditors, IT managers, and administrators Verify compliance with internal as well as external business-level regulations Identify risks in terms of shortfall of backup resources

■ ■

26

Getting started using Symantec OpsCenter About Symantec OpsCenter

■ ■

Assess recovery of clients and applications

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

Estimate future backup requirements with the help of backup trend analysis Calculate the cost of data protection management and chargeback to customers and business units Note: You can generate cost reports only for backup data. Cost reports for archive data are not available.

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

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

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

Getting started using Symantec OpsCenter About Symantec OpsCenter

27

See “About OpsCenter reports” on page 579.

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

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

Symantec NetBackup Symantec BackupExec Symantec NetBackup PureDisk

28

Getting started using Symantec OpsCenter About what's new in Symantec OpsCenter 7.1

■ ■ ■

Symantec Enterprise Vault IBM Tivoli Storage Manager EMC 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. The detailed, drill-down OpsCenter reports help you determine the applications, databases, or business departments that are the heaviest consumers of backup resources. For example, in an environment running 20 instances of Oracle applications, you can generate a report showing resource consumption by department, server, or location. Depending on this information, organizations can provide appropriate resource planning in advance. Symantec OpsCenter Analytics offers you a set of chargeback reports that detail backup service expenditures. By using these reports, you can track the backup and recovery use and the associated cost. By using the chargeback function, you can define pricing models for backup service delivery and allocate costs to customers based on these models. For example, you can create a formula that determines charges based on kilobytes of backed up data over a period of time. Using this chargeback data, you can then present itemized invoices to internal customers, export chargeback tables to third-party billing systems, or use the data to analyze and justify expenditures. Note: You can generate cost reports only for backup data. Cost reports for archive data are not available.

About reporting on archive data
The Enterprise Vault Archiving report category contains a number of reports that are generated based on the archive data collected from Enterprise Vault. You can report on the number of messages that are archived across mailboxes or the size of these messages before and after the archive operation.

About what's new in Symantec OpsCenter 7.1
OpsCenter 7.1 offers the following enhancements or new functions.

OpsCenter 7.1 helps you to monitor, manage, and report on the audit trail information for NetBackup 7.1 master servers. An audit trail is a record of all the user-initiated activities. An audit trail consists of the changes that are made in the NetBackup environment.

Getting started using Symantec OpsCenter About what's new in Symantec OpsCenter 7.1

29

You can monitor audit trail information from the Monitor > Audit Trails page in the OpsCenter console. You can also edit audit settings from the Manage > Hosts > Master Server page. New data collectors have been added in OpsCenter 7.1 for collecting audit trail data. A new service called NetBackup Audit Manager (nbaudit) has been added and can be viewed from the Monitor > Services page. See “Monitoring Audit Trails” on page 492. See “Managing Audit Trails settings” on page 535.

The following new report categories have been added under Reports > Report Templates.
Audit Reports The Audit Reports in OpsCenter 7.1 report on the audit trails information. An audit trail is a record of all the user initiated activities. An audit trail consists of the changes that are made in the NetBackup environment. See “Audit Reports > Audit Trails Report” on page 616. Storage lifecycle Policy The SLP reports in OpsCenter 7.1 show an end-to-end view of the SLP process that includes backup to import of a duplicated image into different NetBackup domains (master servers). The SLP reports help you to verify if each step in the SLP is executed and also identify the possible bottlenecks. See “About Storage Lifecycle Policy reports” on page 657. Workload Analyzer The Workload Analyzer reports give information about the activities that are done across a period of seven days. The activities are number of jobs running at a given period of time and the amount of data that is transferred during this period. The report contains 168 data points of analysis in terms of the activities that are done for each hour for a period of seven days. See “About Workload Analyzer reports” on page 694.

30

Getting started using Symantec OpsCenter About what's new in Symantec OpsCenter 7.1

OpsCenter 7.1 helps you to report on the capacity license data that is protected for a client. You can find information about capacity licenses from the Manage > Deployment Analysis page in the OpsCenter console. See “About managing NetBackup Deployment Analysis” on page 536. A new option that is named Enable Breakup Job Data Collection is now available when you add a master server. This option appears under the Advanced Data Collection Properties section when you add a master server (earlier than 7.1) from Settings > Configuration > NetBackup. For 7.1 master servers, the breakup jobs data collection happens automatically using NBSL. New data collectors have been added in OpsCenter 7.1 for collecting breakup jobs data. See “About the Breakup Jobs option” on page 366. OpsCenter 7.1 can monitor and manage all NetBackup master server versions between 6.0 MP7 and 7.1. OpsCenter 7.1 can collect data from NetBackup 7.1 master servers that are running on AIX 7.1 and Red Hat Linux 6.0. Note that OpsCenter 7.1 is not supported on AIX 7.1 and Red Hat Linux 6.0. OpsCenter 7.1 now supports Symantec NetBackup PureDisk 6.6.1 and Symantec Backup Exec 2010 R2. In addition, OpsCenter 7.1 supports Symantec Backup Exec on 64-bit platforms. See “About OpsCenter compatible backup and archiving products ” on page 89. In OpsCenter 7.1, the following infrastructure components have been upgraded to higher versions:

The Apache Tomcat Web server in OpsCenter 7.1 has been upgraded to version 6.0.29 (from version 6.0.20.0). The Web server has been upgraded to address the security vulnerabilities in the earlier version. Sybase ASA database has been upgraded to 11.0.1.2472 for Windows and 11.0.1.2468 for UNIX platforms. These versions are the same as NetBackup. In large setups, the OpsCenter database may hang when it runs for a long time. The Sybase version upgrade helps to prevent such performance issues.

OpsCenter 7.1 cluster can now be installed on Windows 2008 R2. See “Supported OS and cluster solutions” on page 233. You can access OpsCenter 7.1 using Internet Explorer 7.x and 8.0. You cannot access OpsCenter 7.1 using IE 6.x. You can also access OpsCenter 7.1 using Mozilla Firefox 3.0 and later versions. See “About Web browsers supported by OpsCenter 7.1” on page 41. In OpsCenter 7.1, performance enhancements have been made in the following areas like upgrading directly from NOM and VBR to OpsCenter 7.1, improving the performance of certain reports, and feature parity with VBR.

Getting started using Symantec OpsCenter About what's new in Symantec OpsCenter 7.1

31

The list of reports whose performance has been improved in OpsCenter 7.1 are the following:
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Success Rate Report Client Risk Analysis Exit Status Summary (Job Count by Exit Code -Distribution) Job Size Historical Forecasting - Job Size Drive Utilization Drive Throughput Pre vs. Post De-duplication Size Throughput Variance Report Media Summary by Media Server Disk Usage Report Throughput Report Top 10 Policies using most space Virtual Client Summary Scheduled Job Versus Actual

The following enhancements have been made in OpsCenter 7.1 with respect to VBR parity. This functionality was also earlier available with Veritas Backup Reporter (VBR).

You can enable or disable report schedules from the Reports > Schedules page in the OpsCenter console. This can be done by selecting a report schedule and clicking Enable or Disable. A new filter called Host is available when you edit custom reports and some Client reports. Using the Host filter, you can view data for active clients in the specific reports. This filter has been added in the custom reports and the following Client reports:
■ ■

Recovery Point Objective Client Risk Analysis

These reports can be accessed from the Reports > Report Templates page by selecting Client Reports > Risk Analysis folder.

You can now remove a host alias from Settings > Configuration > Host Alias. You can clear and save the alias for removing the specific alias.

32

Getting started using Symantec OpsCenter About OpsCenter components

You can search for clients by clicking Search Clients from the Monitor > Hosts > Clients page. You can search using absolute host names or substrings. A new Report On parameter called Backup Job Database Instance Name is available when you edit custom reports. Using the Backup Job Database Instance Name parameter, you can view data for a specific MS-SQL database instance in a custom report.

You can now upgrade from NOM or VBR to OpsCenter 7.1 Server software on a different Windows system. An example scenario is when NOM or VBR is running on Windows 2000 and you require the same data with OpsCenter 7.1 on Windows 2003. In OpsCenter 7.0, upgrading from NOM or VBR to OpsCenter 7.0 Server software on a different Windows system was not supported. See “Upgrading to OpsCenter Server on a different Windows system” on page 201. In OpsCenter 7.0 or 7.0.1, you can export a tabular report as PDF in only the default Portrait format. With OpsCenter 7.1, you can export a tabular report in any of the following PDF formats from Settings > User Preferences > General:
Portrait Displays a maximum of seven columns of data per page . Displays a maximum of ten columns of data per page. Displays data in the Portrait format for data up to seven headers and Landscape format for more than seven headers. Displays the entire data across a single page.

Landscape

Portrait for less than eight headers

Expand to fit

About OpsCenter components
This section describes the following OpsCenter components:
■ ■ ■

See “About the OpsCenter Server” on page 33. See “About the OpsCenter Agent” on page 35. See “About the OpsCenter Java View Builder ” on page 38.

Getting started using Symantec OpsCenter About OpsCenter components

33

About the OpsCenter Server
The OpsCenter Server, the core of the architecture, is a Web application that normalizes backup and archive data that it collects from various applications. This normalized data is used for reporting on backup-related information. OpsCenter Server is supported on Windows and UNIX platforms. Note: You must install OpsCenter Server, Agent, and View Builder of the same versions. For example, Server 7.1 is compatible only with Agent 7.1 and View Builder 7.1. The OpsCenter Server comprises the following components:
OpsCenter database A Sybase SA (SQL Anywhere) database management system containing data related to backup and archive service usage and expenditure, cost metrics and chargeback formulas, and alerts. See “About the OpsCenter database” on page 34. Symantec Product Authentication Service (AT) A set of common authentication runtime libraries and processes that enable users to log on once to access multiple products. AT validates identities based on external name spaces like Active Directory or other LDAP servers, UNIX identities based on password files, NIS/NIS+ repositories or any identities that can be authenticated through PAM (Pluggable Authentication Module). It also provides a private user repository for service identities. See “About the Symantec Product Authentication Service ” on page 35. Alert Manager A component that provides policy-based alert management, including notification, custom actions, and SNMP management capabilities. A common Web server (that uses Java Server Pages) and a JRE to serve the OpsCenter console. A common Veritas Licensing Module and API used to add, change, and remove Veritas product license keys. A common component that uses socket passing to reduce the number of ports required to be open across a firewall. Symantec Private Branch Exchange uses a paradigm similar to that of a telephone switchboard in which calls placed to a switchboard are redirected to a known extension. In the PBX exchange, client connections that are sent to the exchange’s port are redirected to an extension associated with the OpsCenter Server.

Symantec Web Server and Java Runtime Environment (JRE) Veritas Licensing Manager

Symantec Private Branch Exchange

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

34

Getting started using Symantec OpsCenter About OpsCenter components

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

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

Getting started using Symantec OpsCenter About OpsCenter components

35

OpsCenter uses a Sybase SQL Anywhere 11 (Sybase 11) database installation that is separate from the NetBackup database. Except for a very small number of system settings, all information that is in the Web user interface is contained in the OpsCenter database, which consists of a single cross-platform database file. The OpsCenter database is completely embedded and requires no additional installation steps. The Sybase database is also self tuning and does not require a database administrator to maintain it. OpsCenter 7.1 supports upgrades from NOM and VBR.

About the Symantec Product Authentication Service
The OpsCenter Server relies on Symantec Product Authentication Service (AT) for user authentication for connections between, OpsCenter Server, Agent, and Java View Builder. The Symantec Product Authentication Service is referred to as AT. Symantec Product Authentication Service is a shared component and is used to perform the following actions:

Authenticate users to the OpsCenter console based on external authentication systems such as Active Directory, NIS, NIS+, LDAP and even standard UNIX passwords. Provide for a secure transport of data between OpsCenter Agents and the OpsCenter server. Enable trust between OpsCenter and other Symantec products that also use AT.

Note: For more details on AT, refer to the ICS documentation that is shipped with the NetBackup documentation set. When the Symantec Product Authentication Service library authenticates a user for OpsCenter, it returns a credential that OpsCenter passes along when cross-linking to other Symantec products such as NetBackup Operations Manager. The Web credential provides a limited form of user authentication so that products do not prompt the user to log on again.

About the OpsCenter Agent
The OpsCenter Agent collects data from various Symantec and third-party backup and archiving products. These products can reside on the OpsCenter Agent host

36

Getting started using Symantec OpsCenter About OpsCenter components

or on remote hosts. The OpsCenter Agent relies on the Java Runtime Environment (JRE) to perform its functions. The OpsCenter Agent also requires embedded AT (Symantec Product Authentication Service) to authenticate itself with the OpsCenter Server. Both JRE and AT libraries are installed automatically with the Agent installation. OpsCenter Agent is supported on Windows and Solaris platforms. Note: You must install OpsCenter Server, Agent, and View Builder of the same versions. For example, Server 7.1 is compatible only with Agent 7.1 and View Builder 7.1. OpsCenter formats the information collected from the following target products and displays it through the OpsCenter console:

Symantec NetBackup Note: For NetBackup 6.5.x master servers, you need to have OpsCenter Agent only if you want to collect image, error log, scheduled job, or breakup jobs data. For NetBackup 6.0.x master servers, you need to have OpsCenter Agent only if you want to collect image or error log data. For NetBackup 7.0.x master servers, you need to have OpsCenter Agent only if you want to collect breakup jobs data. Symantec Backup Exec (Windows only) Symantec Enterprise Vault (Windows only) EMC NetWorker IBM Tivoli Storage Manager

■ ■ ■ ■

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

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

The OpsCenter Agent can reside on the same host as the OpsCenter server, or can be installed on a remote host. All OpsCenter data collectors are configured on every Agent. Configure and run only these data collectors for the target product on which you want to monitor or report. A number of combinations of OpsCenter Agent and Server installations are possible. For example, you can install an Agent on the OpsCenter Server host and configure the NetBackup data collector to collect data from a remote NetBackup

Getting started using Symantec OpsCenter About OpsCenter components

37

master server. Alternatively, you can install an agent on the NetBackup master server host and configure the NetBackup data collector to collect data from the local NetBackup master server. Note: The EMC NetWorker data collector does not support remote data collection. Therefore, the Agent must be installed on the EMC NetWorker server host. The core of the OpsCenter Agent is a Java virtual machine (JVM) on which you run different data collectors. The OpsCenter Agent communicates with the OpsCenter Server, schedules backup and archive data collection data types, and receives commands through the CORBA API. Because the OpsCenter Server relies on Symantec Product Authentication Service to authenticate connections betwen the OpsCenter Agent and OpsCenter Server, the Symantec Product Authentication Service client libraries reside on the Agent host. The OpsCenter Agent comprises scheduler, CORBA Client/Server, and data collectors that collect backup data from all available backup applications. The Scheduler and CORBA form the agent core. These parts of the agent are described in the following topics: See “About the scheduler” on page 37. See “About the CORBA Client/Server ” on page 37. See “About data collectors” on page 38.

About the scheduler
The scheduler performs three basic functions for the OpsCenter Agent:
■ ■

Checks and queues the data collection schedules of all running data collectors. Sends periodic heartbeat messages to the OpsCenter server to ensure the reliability of communications between the Agent and the Server. Monitors modifications made to the Agent configuration using the OpsCenter console, which are stored on the OpsCenter Server.

About the CORBA Client/Server
The OpsCenter Agent implements a CORBA server that listens on a configurable port that allows the OpsCenter console to get the runtime status of the Agent. (The default port is 7806.) When you send a request to get the Agent status through the OpsCenter user interface, the OpsCenter Server sends the request to theCORBA Server to receive the requested information.

38

Getting started using Symantec OpsCenter About OpsCenter components

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

About data collectors
The data collectors convert the data specific to backup or archive products into a format that can be used by the OpsCenter Server. Each data collector must conform to an interface that defines its interaction with the OpsCenter Agent. The data collector is implemented in a way that suits the underlying backup or archive product. Data collector configurations consist of general parameters, such as log configurations and data collection event definitions, which are shared by all data collectors, and product-specific values. You must configure a data collector on the OpsCenter Agent host that collects data from a backup or archive product host.

About Agent configuration and logging
Agent configuration settings are stored in the OpsCenter database. The OpsCenter Agent also caches the latest version of the configuration settings in the agent.conf file. The agent compares the local agent.conf file with the one stored in the database when the agent process is started. If the agent process has already started, any changes made to the local agent.conf file do not take place until the agent is restarted. Note: You should not modify the agent.conf file. You should change the agent configuration settings using the OpsCenter Agent configuration user interface. Any changes that you make to the Agent configuration settings are reflected after the next heartbeat. A heartbeat is a request that the OpsCenter Agent sends to the OpsCenter Server to check for any new changes in the configuration settings. By default, a heartbeat is sent every minute. Logging for the agent core and individual data collector is administered in the same fashion but written to different log files.

About the OpsCenter Java View Builder
The OpsCenter Java View Builder is an application in which an administrator creates, modifies, and manages access to the OpsCenter views that users see in the console.

Getting started using Symantec OpsCenter About using the OpsCenter console

39

Note: To create or customize views using Java View Builder, you must install the licensed version of OpsCenter called Symantec OpsCenter Analytics. The Java View Builder relies on the AT client libraries which is installed automatically to communicate properly with the OpsCenter Server. To use the Java View Builder, you need to provide login credentials as you do while logging onto the OpsCenter console. See “Logging on to the Symantec OpsCenter console” on page 51. When you run the Java View Builder .exe file, it is directly connected to the OpsCenter Server. The View Builder fetches the existing object view definitions from the OpsCenter database and displays them in the OpsCenter console. The actions that you perform using the View Builder console are then stored in the OpsCenter database. Note: You must install OpsCenter Server, Agent, and View Builder of the same versions. For example, Server 7.1 is compatible only with Agent 7.1 and View Builder 7.1.

About using the OpsCenter console
The following sections describe how to access and use OpsCenter. They include how to log on and log off and how the console works. For information on how to understand and use the various OpsCenter views and related tasks, see the OpsCenter online Help. Context-sensitive help is available for all console views, task dialog boxes, and wizard task screens. To access the online Help, use the Help option in most dialog boxes and wizard screens. You can also use the Help option on the title bar of OpsCenter views. The OpsCenter online documentation assumes that the user has a good working knowledge of NetBackup and its concepts and components. Portions of the online Help may refer the user to other NetBackup documentation for descriptions of NetBackup fields and components. The following NetBackup documents are referenced in the OpsCenter online Help:
■ ■ ■ ■

NetBackup Administration Console Help NetBackup Administrator’s Guide for Windows, Volume I NetBackup Administrator’s Guide for UNIX and Linux, Volume I NetBackup Troubleshooting Guide for UNIX, Windows, and Linux

40

Getting started using Symantec OpsCenter About starting the OpsCenter console

About starting the OpsCenter console
The OpsCenter server is the focal point for centralized management of the NetBackup servers (version 6.0 MP7 and later) in your backup environment. When you install Symantec OpsCenter, you select the computer that serves as the OpsCenter server. When you start the OpsCenter console to manage and monitor your NetBackup environment, you open a connection to the OpsCenter Web interface.

About Web browser considerations
Consider the following recommendations and requirements for the Web browser to be able to access the OpsCenter console. The following requirements and recommendations should be considered for the Web browser:

The OpsCenter console uses pop-up menus. If you use pop-up blockers with your Web browser, some of these menus may not display properly. You must disable pop-up blocking or add the OpsCenter Web address to the list of acceptable sites in your browser. The Web browser should have active scripting (ActiveX and JavaScript) enabled. Ensure that the character encoding for the browser is Unicode (UTF 8) before you access the OpsCenter console. Open the Internet Explorer browser and select View > Encoding > Unicode (UTF-8). Open the Mozilla Firefox browser and select View > Character Encoding > Unicode (UTF 8). On some server systems, you may see a blank page when you try to access OpsCenter using Internet Explorer 7.0 and above versions. This issue is caused due to high security level in server systems. If you encounter this issue, open Internet Explorer and click Tools > Internet Options. Click the Security tab and select 'Internet' icon as the zone. Click Custom Level.... In the Security Settings dialog box, browse to Miscellaneous > Allow META REFRESH and select Enable. Click Yes to confirm that you want to change the security settings for the zone, and then click OK. Note: In case you do not want to change your security settings, you must manually append /opscenter to the OpsCenter URL. This must be done every time you access OpsCenter and face this issue.

■ ■

Getting started using Symantec OpsCenter About starting the OpsCenter console

41

On some server-class systems, an enhanced security configuration can cause some pages to not display properly in Internet Explorer. If you encounter this issue, add the OpsCenter URL to the Trusted-sites list and lower the security setting. To resolve this issue, open Internet Explorer and select Tools > Internet Options > Security to configure the Trusted-sites list and lower the security level. If you use Internet Explorer 8.0 to access the OpsCenter console, security certificate warnings appear when you access a pop-up menu. Select Continue to this website (not recommended) to open the pop-up menu. Once you select this option, the security certificate warnings do not appear on the pop-up menus. The Web browser cache must be cleared.

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

Web browsers supported by OpsCenter 7.1 Supported Versions
7.x, 8.0

Notes
IE 7.0 and later versions may display a security certificate warning page when you access OpsCenter. See “Disabling security certificate warnings permanently from browsers” on page 43.

Note: OpsCenter 7.1 does
not support IE 6.x.

Mozilla Firefox

3.0, 3.5, 3.6

Mozilla Firefox may display an Untrusted Connection page when you access OpsCenter. See “Disabling the Untrusted Connection page in Mozilla Firefox” on page 42.

About accessing the OpsCenter console
Before accessing the OpsCenter console, review the following section thoroughly. See “About Web browser considerations” on page 40.

42

Getting started using Symantec OpsCenter About starting the OpsCenter console

On a system that has a network connection to the OpsCenter server, start a Web browser. In the Web browser address bar, enter the following: http://host.domain/opscenter
host.domain is the fully qualified domain name of the OpsCenter server and can

also be an IP address. Note: By default, OpsCenter tries to run on port 80 (HTTP). If port 80 is not available, OpsCenter can use a different port. To know the HTTP and HTTPS port that OpsCenter uses, run the configurePorts utility. Run INSTALL_PATH\OpsCenter\gui\bin\goodies\configurePorts.bat -status on Windows hosts or /opt/SYMCOpsCenterWebGUI/bin/goodies/configurePorts.sh -status on UNIX hosts. For example, if OpsCenter uses HTTP port 8181, then use http://host.domain:8181/opscenter. You can also use the URL that is presented at the end of the OpsCenter server installation to access OpsCenter. You must supply logon credentials on the OpsCenter login screen. For an administrator initial logon, the user name is admin and the password is password or any custom password that you chose during the installation. Select OpsCenterUsers(vx) from the Domain drop-down list and click Log On. See “Logging on to the Symantec OpsCenter console” on page 51.

Disabling the Untrusted Connection page in Mozilla Firefox
When you access OpsCenter in Mozilla Firefox, you may see the following Untrusted Connection page.
-------------------------------------------------------------This Connection is Untrusted You have asked Firefox to connect securely to <OpsCenterhost.domain>, but we can't confirm that your connection is secure. Normally, when you try to connect securely, sites will present trusted identification to prove that you are going to the right place. However, this site's identity can't be verified. What Should I do? If you usually connect to

Getting started using Symantec OpsCenter About starting the OpsCenter console

43

this site without problems, this error could mean that someone is trying to impersonate the site, and you shouldn't continue. Technical Details I Understand the Risks --------------------------------------------------------------

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

1 2 3 4 5

On the Untrusted Connection page, expand I Understand the Risks section and click Add Exception. In the Add Security Exception dialog box, click Get Certificate. Ensure that the Permanently store this exception option is checked. This option is checked by default. Click Confirm Security Exception. Restart your browser for the changes to take effect.

Disabling security certificate warnings permanently from browsers
When you log on to the OpsCenter console, you may see security certificate warnings on Mozilla Firefox and Internet Explorer browsers. When you access OpsCenter using http://<host.domain>/opscenter, you are automatically redirected to HTTPS (hypertext transfer protocol secure) which is a secure protocol and requires a certificate. If you do not want to use HTTPS, you can disable the security certificate warnings for the OpsCenter console. However, if you disable the automatic redirection to HTTPS, you lose the encryption and secure identification of the server that HTTPS provides.

44

Getting started using Symantec OpsCenter About starting the OpsCenter console

To disable security warnings and HTTPS redirection

1

Open the web.xml configuration file in a text editor from the following locations:
For Windows: For UNIX: INSTALL_PATH\OpsCenter\gui\webserver\conf\web.xml /opt/SYMCOpsCenterGUI/webserver/conf/web.xml

Note: Before you proceed, take a backup of the web.xml file.

2

In the web.xml file, locate the security constraint string (located towards the end of the file):
<security-constraint> <display-name>Security Constraint</display-name> <web-resource-collection> <web-resource-name>Protected Area</web-resource-name> <url-pattern>/*</url-pattern> </web-resource-collection> <user-data-constraint> <transport-guarantee>CONFIDENTIAL</transport-guarantee> </user-data-constraint>

Getting started using Symantec OpsCenter About starting the OpsCenter console

45

3

Comment this portion from the web.xml file by adding <!-- in the beginning and --> in the end. You can also add your comments inside. For example:
<!-- 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 interface service on Windows. Select Control Panel > Administrative Tools > Services and restart (stop and then start) the Symantec OpsCenter Web Server Service.

5

Restart the OpsCenter Web interface service on UNIX. Enter the following command:
Stop service Start service /opt/SYMCOpsCenterGUI/bin/stopGUI /opt/SYMCOpsCenterGUI/bin/startGUI

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

46

Getting started using Symantec OpsCenter About starting the OpsCenter console

Table 1-2 Issue and Cause

OpsCenter console access issues, causes, and solution Solution

You cannot connect to the Web interface. Your Web browser displays a "page cannot be displayed" or "connection was refused."message. This issue happens when the OpsCenter Web interface (the OpsCenter console) is not running or is inaccessible on the network.

Verify that the Symantec OpsCenter Web server Service is running. You can check the status of all OpsCenter processes on UNIX by entering the following command: /opt/SYMCOpsCenterServer/bin/opsadmin.sh monitor 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

Note: To know the HTTP and HTTPS port that
OpsCenter uses, run the configurePorts utility. Run INSTALL_PATH\OpsCenter\gui\bin\goodies\configurePorts.bat -status on Windows hosts or /opt/SYMCOpsCenterWebGUI/bin/goodies/configurePorts.sh -status on UNIX hosts.

Your Web browser ■ Locate the opscenter.sh start ■ ■ . ■ Start all the OpsCenter Server services by using the following command: INSTALL_PATH\OpsCenter\server\bin\opsadmin.bat start ■ Use the following steps on UNIX: ■ Locate the opscenter. use the following command: /opt/SYMCOpsCenterServer/bin/opsadmin monitor Start all the OpsCenter Server processes by using the following commands: /opt/SYMCOpsCenterServer/bin/opsadmin.war file in the following directory to verify that the OpsCenter application is installed: /opt/SYMCOpsCenterGUI To verify that all OpsCenter Server processes are running. INSTALL_PATH\OpsCenter\gui\webserver\webapps Verify that all the OpsCenter server services are running. causes.Getting started using Symantec OpsCenter About starting the OpsCenter console 47 Table 1-2 Issue and Cause OpsCenter console access issues.war file in the following displays an "HTTP STATUS 404" error. directory to verify that the OpsCenter application is This issue happens when the OpsCenter console installed: application is not loaded. but the Use the following steps on Windows: OpsCenter console is not available. and solution (continued) Solution The OpsCenter Web interface is running.

browse to Miscellaneous > Allow META REFRESH and select Enable. ■ Click Yes to confirm that you want to change the security settings for the zone. On the Tools menu. Without the changes to the security settings. causes. ■ Note: If you do not want to change your security settings. and solution (continued) Solution You see a blank page when you try to access OpsCenter Use the following steps to resolve this issue: using Internet Explorer 7. click the Internet. ■ In the Security Settings dialog box. ■ Open Internet Explorer . .0 and later versions. click Internet Options.48 Getting started using Symantec OpsCenter About starting the OpsCenter console Table 1-2 Issue and Cause OpsCenter console access issues. you must manually append /opscenter to the OpsCenter URL. ■ Click the Security tab. icon and then click Custom Level. Under Select a Web content zone to specify its security settings. and then click OK. the issue recurs every time that you accessOpsCenter. and you must add /opscenter to the URL.

click the Start button and then click Search.Getting started using Symantec OpsCenter About starting the OpsCenter console 49 Table 1-2 Issue and Cause OpsCenter console access issues. . causes. and solution (continued) Solution You get the following error when you access OpsCenter by clicking Start > Programs > Symantec OpsCenter > WebUI Login on Windows: Windows cannot find 'https://<MACHINE_NAME>:<PORT_NUMBER>/opscenter'. and then try again. To search for a file. Make sure you typed the name correctly.

Note: Editing the registry incorrectly can damage your system. In the Edit File Type window. the "Use DDE" box is still checked but the "DDE Message" box will be cleared) Repeat for Extension: "(NONE)" File Type: "URL:HyperText Transfer Protocol with Privacy" (and any other protocols you want to fix) Repeat for Extension: "(NONE)" File Type: "Firefox URL" Repeat for Extension: "HTM" (or "HTML") File Type: "Firefox Document" 7 8 9 Note that the "File Types" user interface that allows you to uncheck the "Use DDE" option. Click OK for that dialog and the next one (afterwards. so you will need to edit the registry to remove the "ddeexec" key. as described above. Do not attempt these steps if you are inexperienced or uncomfortable using the Registry Editor.50 Getting started using Symantec OpsCenter About starting the OpsCenter console Table 1-2 Issue and Cause OpsCenter console access issues. select Open and click Edit. Uncheck "Use DDE" (the dialog should then hide the lower part). is not available in Windows Vista. and solution (continued) Solution Use the follwing resolution for Windows XP and Windows 2000: 1 2 3 4 5 6 Open Windows Explorer (or My Computer). You will need to manually edit the registry in Windows Vista or in cases where the File Types listing is missing certain entries such as "URL:HyperText Transfer Protocol" (HTTP) and "URL:HyperText Transfer Protocol with Privacy" (HTTPS). Go to Tools > Folder Options > File Types Select Extension: "(NONE)" anf File Type: "URL:HyperText Transfer Protocol" Click Advanced. causes. Use the following resolution on Windows Vista or in cases where the File Types listing is missing certain entries such as "URL:HyperText Transfer Protocol" (HTTP) and "URL:HyperText Transfer Protocol with Privacy" (HTTPS): .

Use the directory tree hierarchy to navigate to "HKEY_CLASSES_ROOT\HTTP\shell\open\ddeexec". and solution (continued) Solution 1 2 3 4 Go to Start > Run. Repeat for "HKEY_CLASSES_ROOT\FirefoxURL\shell\open\ddeexec". 5 6 Logging on to the Symantec OpsCenter console You must supply logon credentials on the OpsCenter login screen. Repeat for "HKEY_CLASSES_ROOT\FirefoxHTML\shell\open\ddeexec". then type regedit and click OK.Getting started using Symantec OpsCenter About starting the OpsCenter console 51 Table 1-2 Issue and Cause OpsCenter console access issues. Delete the "ddeexec" registry key. . Repeat for "HKEY_CLASSES_ROOT\HTTPS\shell\open\ddeexec" (and any other protocols you want to fix). causes.

After initial logon. . change the user name and password. and domains of the users that are added to the OpsCenter console. If OpsCenter does not support this language. use Settings > User Preferences > My Profile view in the OpsCenter console. OpsCenter saves your settings and preferences and uses these settings when you restart the console again. the user name is admin and the password is password or any custom password that you chose during the installation. OpsCenter uses the default language of the Web browser. Select OpsCenterUsers(vx) from the Domain drop-down list. Note: The first time you log on. you can specify a default language or locale from Settings > User Preferences > General. The domains that appear in the Domain drop-down list include the OpsCenterUsers(vx) domain. a monitoring overview of the NetBackup master servers appears. domains that are migrated if you upgraded to OpsCenter from NOM or VBR. and select a domain from the Domain drop-down list. OpsCenter uses the Web browser language (or English). If you do not set a default. See “Setting user preferences” on page 304. 2 Click Log On. After the initial log on. To change existing passwords.52 Getting started using Symantec OpsCenter About starting the OpsCenter console To log on to the Symantec OpsCenter console 1 Enter a user name and password. When you log off from the console. it uses English. For administrator initial logon. About possible OpsCenter console logon issues Table 1-3 describes the issues you may find when you log on to the console and their solution. Initially. See “Changing your OpsCenter password” on page 307.

If problem persists contact your system administrator. See 'Controlling OpsCenter services and processes' section in the Administration chapter of the Symantec OpsCenter Administrator's Guide. Ensure that the Symantec Product Authentication Service is started and running properly. The login server is not screen displays the message running. The login screen displays the message "User authentication failed. The login screen displays the message "Please enter valid user name and password. "Error occurred while connecting to the OpsCenter Server. are valid. You cannot connect to the The OpsCenter OpsCenter server. The hosts file is located in C:\WINDOWS\system32\drivers\etc directory on Windows. . The login screen displays the message "This user is not authorized to use OpsCenter." The entered user name is not a registered OpsCenter user. Either the user name or password or both have not been entered.Getting started using Symantec OpsCenter About starting the OpsCenter console 53 Table 1-3 Issue OpsCenter console logon issues Cause The Symantec Product Authentication Service cannot validate the user name and password for the selected domain. password. You can start the authentication service by running net start vrtsat' on Windows and /opt/VRTSat/bin/vxatd on UNIX. Solution Enter a valid user name." Start the Symantec OpsCenter Server Service and verify that it is running properly. Please ensure that the server is running. Enter a valid user name and password. Please enter valid user name and password. You have a user authentication error. but the user was not added to the list of users for OpsCenter. Verify that the hosts file has the correct IP address to host name mapping." The user name Log on as the OpsCenter admin user and and domain add the user to the list of OpsCenter users. Check your network configuration. " Username and/or password has not been specified. Please contact the OpsCenter Administrator for adding this user. and domain.

locate the session-timeout parameter: <session-config> <session-timeout>30</session-timeout> </session-config> . You can connecting to the Symantec start the authentication service by running Product Authentication net start vrtsat on Windows or Service (AT).xml configuration file in a text editor from the following locations: For Windows: For UNIX: INSTALL_PATH\OpsCenter\gui\webserver\conf\web.xml /opt/SYMCOpsCenterGUI/webserver/conf/web. users are automatically logged out of the OpsCenter console when a session is left inactive for 30 minutes. OpsCenter saves most of the settings and changes you make in an OpsCenter session.xml 2 In the web. However." Logging out of the OpsCenter console When you log out from the console. that the AT service is running.54 Getting started using Symantec OpsCenter About starting the OpsCenter console Table 1-3 Issue OpsCenter console logon issues (continued) Cause Solution Authentication service is Authentication Verify that the Symantec Product down "Error occurred while service is down Authentication Service is running.xml file. To configure the session timeout interval 1 Open the web. the session timeout interval can be reconfigured. Configuring the OpsCenter session timeout interval When left at its default value. Please ensure /opt/VRTSat/bin/vxatd on UNIX. To log out from Symantec OpsCenter ◆ Click Logout located on the right side of the title bar.

change 30 to the desired value). An in the OpsCenter console application. 4 Stop the OpsCenter services. displays the OpsCenter login screen. Issues when you use OpsCenter console Solution Log on again.bat stop /opt/SYMCOpsCenterServer/bin/opsadmin. you then return to the OpsCenter view that you last visited. See “Configuring the OpsCenter session timeout interval” on page 54. An internal error occurs in This error results from an internal issue the OpsCenter console.sh start About possible OpsCenter console issues Table 1-4 describes the issues you may find when you use the console. Table 1-4 Issue Your OpsCenter console session times out. The login screen appears when you try to change views or refresh the current view. You receive the message "An unknown error has occurred. You can also configure the session timeout interval. " Click the link in the message and try to login again. Cause After 30 minutes of inactivity.sh stop 5 Restart the OpsCenter services. Click here to log on and retry. This value is set in minutes. Enter the following command: Windows UNIX INSTALL_PATH\OpsCenter\server\bin\opsadmin.bat start /opt/SYMCOpsCenterServer/bin/opsadmin. After successful logon. the OpsCenter user automatically logs out of the console. exception error message appears in the OpsCenter console. Enter the following command: Windows UNIX INSTALL_PATH\OpsCenter\server\bin\opsadmin.Getting started using Symantec OpsCenter About starting the OpsCenter console 55 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. Any attempt to use OpsCenter. .

to use this application. You receive the message Active scripting is disabled in the Web "Active scripting is required browser. Enable active scripting in the browser." . You must enable it to use OpsCenter.56 Getting started using Symantec OpsCenter About starting the OpsCenter console Table 1-4 Issue Cause Issues when you use OpsCenter console (continued) Solution Enable active scripting in the Web browser.

mozilla. In the Location bar. If you still receive the prompt (or if you want to see it again). ■ An unresponsive script error Various causes. type about:config and press Enter. you may no longer receive the prompt.Getting started using Symantec OpsCenter About starting the OpsCenter console 57 Table 1-4 Issue Cause Issues when you use OpsCenter console (continued) Solution To let the script run longer: In the Location bar. I promise!.max_script_run_time If you set scripts to run for longer times. . type 0. search for the preference dom. ■ You may see a warning message stating that this action may void your warranty. ■ ■ Click I'll be careful. set the preference back to the default value. ■ At the Enter integer value prompt. is displayed on Mozilla Firefox Note: Either 0 or any negative value imply infinite time. ■ Press OK.max_script_run_time.max_script_run_time. I promise!. search for the preference dom.org /Dom. Click I'll be careful.com /en-US/kb/Warning+Unresponsive+script http://kb. The following URLs contain more information: http://support. ■ In the about:config page. and double-click it. In the about:config page. ■ You may see a warning message stating that this action may void your warranty. Right-click and choose Reset.mozillazine. type about:config and press Enter.

When you change the settings and preferences they are saved and if you log out and log on again these settings are used. Figure 1-2 OpsCenter console components Tabs and subtabs Change Table Title bar Settings icon links Content pane List View View Pane Task Pane (whole left pane) Minimize icons Symantec ThreatCon pane Quick links Alert Summary Pane Maximize icon Details pane Minimize icon Table page controls Table 1-5 lists the topics that describe the main elements of the console in greater detail.shows the OpsCenter console components. Table 1-5 Topic Use the links available from the title bar. You can view the console by using a Web browser. The following is an example view that shows the OpsCenter console components.58 Getting started using Symantec OpsCenter About OpsCenter console components About OpsCenter console components This section provides information on the panes and navigation features available in the OpsCenter console. Topics covered in this section Description See “About using the links on the title bar” on page 59. When you log on initially. . such as Logout and Help. the Monitor > Overview view appears.

To adjust the screen space that is used by the tabs and subtabs. Overview about the View pane. Use the main data display pane that OpsCenter uses. Use the pane that displays a quick visual summary of See “Using the Alert Summary pane” on page 66. Overview about quick links in the task panes. select rows. and use filters. To display the remaining subtabs in a drop-down list. About using the links on the title bar On the title bar of the OpsCenter console. You can select the following options: Small Only the selected tab and subtab are shown in a single row. Control the frequency that the OpsCenter console refreshes to reflect changes in your backup environment. See “Using the quick links in the Task pane” on page 66. Use the status bar at the bottom of the OpsCenter console. click the arrow next to the selected tab. See “About using tables” on page 71. The tabs and subtabs appear in two separate rows. To display the remaining tabs in a drop-down list. See “Using the Task pane” on page 61. Overview about the tabs and subtabs available in the console.Getting started using Symantec OpsCenter About OpsCenter console components 59 Table 1-5 Topic Topics covered in this section (continued) Description See “About using tabs and subtabs” on page 60. Use tables. The tabs and subtabs appear in two separate rows. See “Using the content pane” on page 67. See “About status icons and colors in the console” on page 70. the Logged in as value shows the user name that is logged on to the OpsCenter server. Overview about the Task pane. The tabs do not have any icons above them. click the Customize Tabs drop-down list. See “About the View pane” on page 61. Use the visual keys that OpsCenter uses to help you understand displayed information. See “About the OpsCenter status bar” on page 69. any current alerts. See “About refreshing the OpsCenter console” on page 61. Medium Large . click the arrow next to the selected subtab. The tabs have icons placed above them.

you can customize the OpsCenter server. click About. policies. services. To access Symantec OpsCenter help. Manage Reports Note: You can use custom report functionality only with a licensed OpsCenter version (OpsCenter Analytics). media. You can also display and respond to any OpsCenter alerts. To disconnect from the OpsCenter server to end your session. add master servers. you can manage alert policies. From this tab. set up email and SNMP recipients. click Logout. Table 1-6 Tab Monitor Tabs and subtabs in the OpsCenter console Description From this tab. add OpsCenter users. storage units. ■ About using tabs and subtabs Table 1-6 describes the main tabs that provide access to the major areas of the OpsCenter console. See “About OpsCenter documentation ” on page 77. create and run custom reports. and dialog boxes is available. More information about online Help is available. the Monitor tab includes subtabs such as Overview. and devices. define user preferences. From this tab. See “Logging out of the OpsCenter console” on page 54. and schedule reports. Your selection on the View pane determines what data that is shown in OpsCenter views. . and Policies. and so on. Context-sensitive help for all views. you can monitor the status of NetBackup jobs. More information about the View pane is available. Services. click Help. wizards. Jobs. For example. You can also restore data. you can view standard OpsCenter reports.60 Getting started using Symantec OpsCenter About OpsCenter console components Use the links available in the title bar at the top of the console for the following tasks: ■ ■ To see OpsCenter product version and copyright information. devices. Under each main tab is a series of subtabs. view chargeback settings. and hosts. add and configure views. NetBackup job policies. Settings From this tab. The contents of these subtabs vary depending on the current view and represent the views accessible from each main tab.

you can create a view named Geography to display details about master servers in a particular region. click the Collapse Task Panel icon between the Task pane and the Content pane. Using OpsCenter views.Getting started using Symantec OpsCenter About OpsCenter console components 61 See “About the View pane” on page 61. Using the Task pane In many views in the console. the status of your backup environment is likely to change. a specific view type. You cannot resize the Task pane from the Monitor > Overview page. About the View pane The View pane is a key navigation and configuration tool in Symantec OpsCenter. a Task pane is available. To change the Task pane 1 2 3 To enlarge the Task pane. media usage fluctuates. and Quick Links at the bottom. This pane lets you select the views to control the scope of your console views. click the Collapse Task Panel icon again. and so on. Devices go online and offline. About refreshing the OpsCenter console As you use Symantec OpsCenter. To show all panes after you enlarged the Task pane. ALL MASTER SERVERS is the default view in the View pane. The minimize or maximize settings are applicable only for the current session. The Task pane is located on the left side of the console and contains the View pane. OpsCenter generates alerts. . drag the line separating the Task pane and the Content pane. You can create views from Settings > Views or by using the Java View Builder. You can also create client or policy views. you can view NetBackup information for your entire management domain (with the ALL MASTER SERVERS view). such as Europe. You can change the refresh setting from Settings > User Preferences > General view in the OpsCenter console. or an individual server. You can control when the information in the console refreshes to reflect the changes in your backup environment. To resize the Task pane. For example. the Symantec ThreatCon pane. See “Setting user preferences” on page 304.

See “About OpsCenter views” on page 409. See “About making multiple or single-click selections in the View pane” on page 63.62 Getting started using Symantec OpsCenter About OpsCenter console components More information about how to create views from Settings > Views is available. The View pane is one method that you can use to determine the scope of information that you view. As you navigate within the OpsCenter console. It uses unique icons and colors to convey operational states. It lets you access and change the views that you monitor or manage. See “About selecting views from the View pane when the multiple selection option is checked” on page 64. The View pane has the following features: ■ ■ It is available in any OpsCenter view where you can change the view. Figure 1-3 View pane description . an icon with a red-dashed-circle represents a managed server that is Not Connected. Similarly. your view selection applies for any subsequent screens until you select a different view. See the online Java View Builder Help for more informaiton about creating views using Java View Builder. See “About status icons and colors in the console” on page 70. ■ Figure 1-3 shows a sample View pane in which ALL MASTER SERVERS view is selected. For example. a disabled master server is shown as a gray-colored icon.

The Allow Multiple Selection In View Pane option governs how you can make selections in the View pane. See “About the Group Component Summary table” on page 445. You can make selections in the View pane in the following ways. To view data for multiple master servers and nodes. To see the Allow Multiple Selection In View pane option. The Allow Multiple Selection in View Pane option is checked by default. click Settings > User Preferences > General in the OpsCenter console. You can click a node or a view object to view data for the respective node or view object. you can select multiple nodes or view objects from the View pane. you can only select a single node or view object from the View pane. you can click a master server in the View pane to view data for the specific master server. (The NetBackup Operations Manager (NOM) used this method. check the corresponding check boxes and click Apply Selection. Figure 1-4 shows how you can check the Allow Multiple Selection In View Pane option and make multiple selections. You also see a check box next to each master server or node in the View pane. . For example.Getting started using Symantec OpsCenter About OpsCenter console components 63 About making multiple or single-click selections in the View pane You can make either multiple selections or single-click selections in the View pane. Uncheck Allow Multiple Selection In View Pane option With the multiple-selection option unchecked. based on whether you check or uncheck the multiple selection option: Check Allow Multiple Selection In View Pane option With the multiple-selection option checked.) Each node or a view object is a link. Note: When you uncheck the multiple-selection option. a Group Component Summary table is displayed when you click Monitor > Jobs > Summary View. The multiple-selection option is checked by default.

When you select a view such asALL MASTER SERVERS or a node that contains a group of master servers. ALL MASTER SERVERS. For example. you can select a view and a node that contains a group of master servers and also specific objects. you can select the default view. Each master server is a link About selecting views from the View pane when the multiple selection option is checked From the View pane.64 Getting started using Symantec OpsCenter About OpsCenter console components Figure 1-4 Making multiple selections in the View pane You can select multiple master servers by selecting the check-box Figure 1-5 shows how you can uncheck the Allow Multiple Selection in View Pane option and make single-click selections. all the master servers . Figure 1-5 Making single-click selections in the View pane You can select only one master server.

The master servers that you may add later to this view or node are also automatically selected. . Then. Consider a scenario in which server A and server B exist in a particular view. This level is the same as the ThreatCon level which is shown on the following Web site: http://www.Getting started using Symantec OpsCenter About OpsCenter console components 65 that are currently in the view or node are automatically selected. and that master server is also part of another selected view. Figure 1-6 Symantec ThreatCon pane in the OpsCenter console Click the More Info link in the Symantec ThreatCon pane to see details about the ThreatCon level. To select a specific master server. About the Symantec ThreatCon pane The Symantec ThreatCon pane shows the current ThreatCon level in the OpsCenter console. When you specifically deselect a master server from a view. You may also deselect a specific master server from a view by selecting the view and then deselecting the specific master server. you select a node that also contains server B. For example.symantec. you may select only specific master servers under the default view ALL MASTER SERVERS. In this case.com/security_response/threatcon The Symantec ThreatCon pane is available in the OpsCenter console on the left side. Figure 1-6 shows the Symantec ThreatCon pane in the OpsCenter console. It is not considered because you specifically excluded server B from the ALL MASTER SERVER view. first deselect the view or node that contains the master server and then select the master server. You also have the option to select only specific objects of a particular view or node. For this reason. even though server B is part of the selected view or node. it is recommended that you do not repeat a master server across groups. it is not considered. Suppose that you select the ALL MASTER SERVERS view and then specifically deselect server B. the exclusion (the deselection) has a higher priority. such as ALL MASTER SERVERS.

there are quick links to the most common tasks in OpsCenter. You can configure the polling interval. The Symantec ThreatCon feature is enabled by default. Using the quick links in the Task pane In many views in the console. but you can disable it (or re-enable it). At the bottom of the Task pane. Click the maximize icon (the up arrow) again to view the quick links. and informational alerts for the NetBackup master servers to which you are connected. 2 Using the Alert Summary pane The Alert Summary pane provides a visual summary of the critical.66 Getting started using Symantec OpsCenter About OpsCenter console components OpsCenter periodically polls the ThreatCon Web service and updates the data that is shown in the Symantec ThreatCon pane. This pane is available in the Monitor view and Manage view of . Note: The quick links are shown by default in a maximized state. Only the icons for quick link tasks are visible when the quick links are minimized. Table 1-7 Quick Link Oracle Cloning Alert Policies NetBackup Data Collection Views Users Quick links and their destinations Destination Manage > Oracle Cloning Manage > Alert Policies Settings > Configuration > NetBackup Settings > Views Settings > Users > Users To minimize or maximize the quick links 1 Click the minimize icon (the down arrow) located on top of the quick links. The minimize or maximize settings are applicable only for the current session. a Task pane is available. major. See “Configuring Symantec ThreatCon feature in OpsCenter” on page 312. warning. Table 1-7 shows the quick links available in OpsCenter and where they take you when you click them.

Using the List. . and the time frame. Summary View. You can view information about your NetBackup environment in any of the available views. Use the drop-down list on the top-right corner of the OpsCenter console to switch these views. Note: Not all viewing modes are available for all Monitor views and Manage views. and Hierarchical View. Using the content pane When you initially log on to Symantec OpsCenter. click the Collapse Task Panel icon again.Getting started using Symantec OpsCenter About OpsCenter console components 67 the OpsCenter console. The minimize or maximize settings are applicable only for the current session. Summary. Note: You cannot resize the Content pane from Monitor > Overview page. The number of alerts that you see is based on your View pane selection. This view is a shortcut to the Monitor > Alerts view. and Details views Most of the OpsCenter Monitor views and Manage views present information in three main viewing modes: List View. To change the Content pane size 1 2 3 To enlarge the Content pane. Hierarchical. drag the line separating the Task pane and the Content pane. To resize the Content pane. If the viewing modes are available. Initially. A filtered detail view for that alert category appears. To view outstanding alerts quickly ◆ Click any of the four available alert counts. click the Collapse Task Panel icon between the Task pane and the Content pane. Information in the content pane varies and is context sensitive to current selections in the View pane. a monitoring overview appears (Monitor > Overview). To show all panes after you enlarged the Content pane. the drop-down list is displayed. the content pane displays a summary of information for all master servers in the OpsCenter console. the tabs and subtabs.

68 Getting started using Symantec OpsCenter About OpsCenter console components List View Drop-down list The Summary View presents information in a graphical format as pie charts. Manage views. The List View and Hierarchical View present information in tabular formats. . and Settings views. ■ ■ A Details view is available on some of the Monitor views. For example. click Hierarchical View. clickList View To view a summary of all NetBackup jobs for a master server in the form of pie charts. you can show any of the following views on the Monitor > Jobs page: ■ To view details about all NetBackup jobs for a master server in a tabular format. The following figure shows the Details view. To view details about all NetBackup jobs and relationships between jobs for a master server in a tabular format. click Summary View.

click the icon (the up arrow) between the Details view and the upper part of the Content pane. The view presents details on the displayed information and on the available information for the specific entity. To maximize the Details view. click the icon (the down arrow) between the Details view and the upper part of the Content pane. The Page generated value shows the date and time on the OpsCenter server . Information in the Details view can be viewed from tabs available in the view. 3 To resize the Details view. The Details view presents detailed information about an entity and shows contents of all the tabular columns for the specific entity. The minimize or maximize settings are applicable only for the current session.Getting started using Symantec OpsCenter About OpsCenter console components 69 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. For example. About the OpsCenter status bar The status bar at the bottom of the OpsCenter console shows a Page generated value. To change the Details view 1 2 To minimize the Details view. drag the line separating the upper part of the Content pane and Details view.

More information on how to specify your time zone is available. or informational conditions. Tool tips provide brief descriptions of the tool and the status icons that appear in OpsCenter views. blue-gray server icon means that the managed server is connected. A managed server icon with a line through it denotes that the server is partially connected. warning. A server icon that has a red circle with a line drawn through it means that the connection to the managed server is lost. Table 1-8 Icon Icons used for managed master servers Description A normal. OpsCenter uses status icons and color.70 Getting started using Symantec OpsCenter About OpsCenter console components to which you logged on. Together. For a partially connected master server. This value updates when the view changes or refreshes. About status icons and colors in the console To help you understand the information it presents. For example. The icons use colors to represent critical. When OpsCenter detects a condition for a managed NetBackup server. you see a status icon. the Monitor > Jobs view contains green icons for running jobs. or drive path. the icons and colors let you quickly determine the status of a particular area in your NetBackup environment. A gray server icon means that data collection for the managed server was disabled by the user. Unique icons appear in the drive details view for shared drives available with the NetBackup Shared Storage option (SSO). The date and time are adjusted to match your time zone. OpsCenter tries to connect again after 10 minutes. Table 1-8 lists the icons that are used for managed NetBackup master servers in the View pane. Icons also appear for shared drives where the drive status is mixed (operating on some servers and not operating on other servers that share the drive). OpsCenter tries to reconnect to NBSL every 10 minutes in order to collect data for the data types that have a Failed collection status. job. See “Setting user preferences” on page 304. OpsCenter uses the following colors in the interface: . These icons represent the shared drives that are operating on all servers that share the drive. A tool tip appears when you place the mouse over an icon. drive.

Investigate critical conditions immediately. ■ ■ About using tables OpsCenter collects information about aspects of your NetBackup environment and presents much of this information in tables. 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. while gray indicates conditioned such as disabled or unassigned. Blue-gray generally indicate conditions such as enabled or assigned. Figure 1-7 Create. Green indicates a normal condition.Getting started using Symantec OpsCenter About OpsCenter console components 71 ■ Red indicates a critical condition that may cause the system to be unable to perform an important function. Figure 1-7 shows the task options for tables. This section describes how to change the tables to display the information you want to see. Edit. result. You can perform the following operations to a table: . The following is a sample table showing task icons. or operation.

See “Selecting rows in tables” on page 74. individual requirements Choose the number of rows and columns to See “Choosing the number of table rows that display appear per page” on page 73. See “Changing the width of a column” on page 73. Configure pagination Select rows in tables The table refreshes after the operation and shows the changes you made. Sort columns in ascending or descending order Change the widths of columns See “Sorting the contents of a table column” on page 73. Moving a column Use the following procedure to move columns in a table. some OpsCenter tables do not show all available columns. select the column in the Available Columns list and click Add. Initially. select the column in Selected Columns and click Remove. Each user can have different customized table settings. OpsCenter saves and reloads your customized settings when you log on to the OpsCenter server again.72 Getting started using Symantec OpsCenter About OpsCenter console components Add or remove columns See “Specifying which columns appear in a table” on page 72. To add any columns that currently do not appear. . See “Accessing multiple pages of data in tables” on page 73. Added columns appear as the last column in the table. To remove columns you do not want to appear. To specify which columns appear in a table 1 2 Click the Change Table Settings icon at the top-right corner of the table. Specifying which columns appear in a table Use the following procedure to specify which columns appear in a table. Rearrange the order of the columns for your See “Moving a column” on page 72. For these operations. To view any of these columns. you may first have to remove one or more columns from the table and then add the missing columns.

To change the number of rows that are displayed. the table contains multiple pages. click the column name. To sort in descending order. OpsCenter tables display 10 rows at one time by default. Select Apply To All Tables if you want the Rows Per Page setting to apply to all tables in OpsCenter. Accessing multiple pages of data in tables Much of the monitoring information appears in a table format. To sort the contents of a column or multiple columns ◆ In a table. The column sorts in ascending order by default. click the column name again. Choosing the number of table rows that appear per page Use the following procedure to choose the number of table rows that appear per page. When you have more data to display than can fit in a table.Getting started using Symantec OpsCenter About OpsCenter console components 73 To move a column 1 2 3 Click the Change Table Settings icon at the top of the table. To change the width of a column 1 2 Select the edge of the column heading and hold down the left mouse button. Select a number from the Rows Per Page drop-down list . Drag the edge of the column heading to the right or left. The setting applies to reports also. Click Move Up to move the column to the left in the table. Sorting the contents of a table column Use the following procedure to sort the contents of a column or multiple columns. To choose the number of table rows that appear per page 1 2 3 Click the Change Table Settings icon at the top of the table. Click Move Down to move the column to the right in the table. Changing the width of a column Use the following procedure to change the width of a column. Use the table page controls that are located below the table to help you navigate the pages. . Select the name of the column in Selected Columns. use the Change Table Settings icon.

74 Getting started using Symantec OpsCenter About OpsCenter console components To display the next 10 rows or to return to a previous set of rows in large tables. To create a custom filter 1 2 Select the Create Filter icon. filtering icons appear above the table. you can save it. you must select a row or rows to enable the tasks. The following procedures describe how you can create. Type a name for the filter in the Name field. To select all rows on the current page of the table ◆ Click the check box in the header row of the table. Selecting rows in tables For many tables in OpsCenter. apply. or by using the predefined (ready-to-use) filters. Once you create a filter. In the views that allow filtering. To go to the previous or the next page ◆ Click the left arrow or the right arrow. or remove it. edit. 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. edit it. To select a row in a table ◆ Click the check box for that row. or remove a filter. Click the check box again to deselect the selected row. A filter screens information that is based on a set of conditions that you define. To go to the first or the last page ◆ Click the double left arrow or the double right arrow. To go to a specific page ◆ Click the page number. use the table page controls. Click the check box again to deselect all selected rows. .

To apply a filter ◆ From the drop-down list. click Remove to remove the clause from the query. 5 To continue building the filter. select And or Or to build the filter query. Note: You cannot modify the predefined OpsCenter filters. For Link. 6 Click OK when you finish building the filter. select a custom filter or a OpsCenter built-in filter. select a custom filter. See “To create a custom filter” on page 74. 4 From the drop-down list. 2 3 Click the Edit filter icon. You can only modify custom filters. The view remains in effect until you change it by selecting another filter. Your new filter is available in the filter drop-down list.Getting started using Symantec OpsCenter About OpsCenter console components 75 3 For Column. Repeat 3 and 4. Make your changes and click OK. select another column. If you select Start Time or End Time for Column. enter or select a value. Use != if you do not want to match a specific value. select an operator. For Value. a calendar icon appears for Value. click Add to add another clause to the query. . If the clause is not what you want. This lists the instructions for using the dialog to edit a filter. For Operator. Click the calendar icon to choose a date and time and then click OK. select the column name that you want to filter on from the drop-down list. OpsCenter filters the table according to the criteria you specify. To edit a custom filter 1 From the drop-down list.

Set up user preferences Configure the SMTP server and OpsCenter alert retention settings Set up recipients for alert and report notification Configuring OpsCenter views Create OpsCenter alert policies for your See “About creating (or changing) an alert policy” site on page 501. See “Setting user preferences” on page 304. View and respond to OpsCenter alerts See “Managing an alert policy ” on page 517. See “About monitoring NetBackup policies” on page 453.76 Getting started using Symantec OpsCenter About quickly performing common tasks in OpsCenter To remove a custom filter 1 From the drop-down list. Table 1-9 To learn how to Add master servers in the OpsCenter console Add authorized OpsCenter users Quick links to the OpsCenter documentation Go to this topic See “Adding a master server in OpsCenter” on page 377. About quickly performing common tasks in OpsCenter Table 1-9 lists common tasks and corresponding links to the documentation. See “Creating OpsCenter views” on page 415. 2 3 Click the Delete filter icon. View the details for a NetBackup job See “About monitoring NetBackup jobs” on page 433. select a custom filter. See “About managing Symantec OpsCenter users ” on page 321. Click OK to remove the filter. View NetBackup job policies Control NetBackup job policies . See “Activating or deactivating a job policy” on page 459. Note: You cannot delete the predefined filters. See “About managing recipients in OpsCenter” on page 330. See “Configuring SMTP server settings for OpsCenter” on page 311.

Schedule when you want a report to run See “About managing report schedules in OpsCenter” on page 604. see the Symantec NetBackup Hardware and Software Compatibility List.1.1 Release Notes. licensed (Symantec OpsCenter Analytics version of the product.1 Release Notes for any last-minute changes to the information that is presented in this . It also provides details on the new enhancements in OpsCenter 7. to generate alerts. The list is regularly updated on the Symantec Support Web site: http://www. You can use the bookmark to return to the same view when you log onto the console again. About using Web browser bookmarks Use your Web browser to add a bookmark for any view in the OpsCenter console and return to it as needed. Export NetBackup job log files Control NetBackup services Understand and use OpsCenter reports See “About OpsCenter reports” on page 579. Create custom reports for your needs See “Creating a custom report in OpsCenter” Note: This feature is available with the on page 591.1 and also how you can install OpsCenter 7. See “Monitor > Services view” on page 451. Always refer to the OpsCenter sections of the NetBackup 7. to collect data from Symantec products as well as third-party products.1 in Symantec NetBackup 7.com/business/support You can find more information about OpsCenter 7. and to create various reports. Note: For the latest support information about supported products and operating systems. About OpsCenter documentation The Symantec OpsCenter Administrator's Guide (NetBackup_AdminGuide_OpsCenter.symantec.pdf) provides information on how to use OpsCenter. It includes information about how to monitor and manage NetBackup.Getting started using Symantec OpsCenter About using Web browser bookmarks 77 Table 1-9 To learn how to Quick links to the OpsCenter documentation (continued) Go to this topic See “Exporting NetBackup job logs” on page 442.

click Monitor > Jobs. OpsCenter 7.com/docs/DOC3412 In addition to this Symantec OpsCenter Administrator's Guide PDF.symantec.78 Getting started using Symantec OpsCenter About OpsCenter documentation document. . The Release Notes also include any restrictions or limits for OpsCenter 7. To access the Help. To access the Help. Java View Builder Context-sensitive Help This Help provides information about all Java View Builder procedures and dialog boxes. Table Settings Help This Help provides information on how to change the settings of a table in the OpsCenter console. You can access the Release Notes from the following URL: http://www. To access the Help. It provides context-sensitive help pages for all screens. Click a status code link in the jobs table to view its details. click Help in a dialog box in the Java View Builder console.1 is also shipped with the following online Help documents: OpsCenter Context-sensitive This Help provides information about the OpsCenter user Help interface. NetBackup Status Codes Help This Help provides descriptions of NetBackup status codes and possible actions to take when a code appears.1. click Help on the Table Settings pop-up dialog box.

About components shared with other Symantec applications OpsCenter used the following components that are also shared with other Symantec applications: . About the software components that OpsCenter uses Along with OpsCenter-specific components.1 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 The following topics provide information on concepts to understand and steps to take before you install or upgrade OpsCenter. OpsCenter uses some Symantec components that are shared.Chapter 2 Installing Symantec OpsCenter 7.

The NetBackup Authentication Service (NBAC) does not need to be configured on your managed NetBackup master servers. OpsCenter uses VxUL to configure and view logs. View Builder. which reduces the required number of open ports in firewalls. AT is required for secure communication among the OpsCenter Agent. The OpsCenter Server needs to be a legitimate server that can communicate with NetBackup. Sybase database ■ ■ . It is also used for secure communication between NetBackup master servers and the OpsCenter Server. OpsCenter does not require that you install the Symantec Product Authorization Service. Symantec Product Authentication Service (AT) The AT service is primarily used for user logon authentication. and user interface. See the NetBackup Troubleshooting Guide for more information about VxUL logs. JRE (Java Runtime Environment ) The Symantec OpsCenter Web server and the OpsCenter application require this component. Because PBX is an independent component. OpsCenter may fail. PBX also integrates with the Symantec Product Authentication Service to allow for authenticated connections and non-authenticated connections.1 Planning an OpsCenter installation ■ Symantec Private Branch Exchange (PBX) PBX lets applications share a common TCP/IP port. Note: If you change the PBX port number on the OpsCenter server. See the NetBackup Security and Encryption Guide for information about authentication services and about NBAC. it must be on the NetBackup server list. its port number can be changed using PBX configuration files. ■ ■ About Symantec OpsCenter components OpsCenter used the following components that are not shared with other Symantec applications: ■ Apache Tomcat Web server The OpsCenter user interface runs under the Apache Tomcat Web server. Veritas Unified Logging (VxUL) VxUL is installed with the OpsCenter Server and the Agent.80 Installing Symantec OpsCenter 7. Server.

the charges are based on the number of backup clients. For example.com/support/manuals About the OpsCenter licensing model OpsCenter requires no license. The charges for Symantec OpsCenter licenses are based on how many entities you require reports on. The product name is visible from the title bar and logon page of the OpsCenter console. The unlicensed version of OpsCenter is called Symantec OpsCenter. More information about the Sybase component is available at the following location: http://www. You compare the configured number of mailboxes or backup clients with the license limit. You must purchase a license that allows reporting for 100 backup clients and 500 mailboxes. the charges are based on the number of mailboxes. For Symantec Enterprise Vault environments. You also run Enterprise Vault and have 500 mailboxes. The licensed version of OpsCenter is called Symantec OpsCenter Analytics. .1 Planning an OpsCenter installation 81 OpsCenter uses a Sybase SQL Anywhere 11 (Sybase 11) database installation that is separate from the NetBackup database.sybase. If you install the Archive Mailbox option. you must add the appropriate license key. The Symantec Enterprise Vault license is option called Archive Mailbox is added. If you have a license for 1000 mailboxes. assume that your NetBackup environment contains 100 clients to back up. To enable additional functionality you can add a license key to enable Symantec OpsCenter Analytics. it is added as 'Archive Mailbox' as shown in the figure. Examine the Value column and the Usage column on the Settings > Configuration > License page. ■ Note: If you want to enable custom reporting on Enterprise Vault data. it is visible in the OpsCenter console on the Settings > Configuration > License page.Installing Symantec OpsCenter 7. as follows: ■ For backup environments.

With Symantec OpsCenter Analytics. delete. . Permanent key You can access the licensed features with both demo keys and permanent keys. The demo key lets you try the product before you purchase it. or view license keys after installation from the OpsCenter console.82 Installing Symantec OpsCenter 7. and collect data from third-party products such as IBM Tivoli Storage Manager and EMC Networker. You can also add. See “About managing licenses” on page 307. you can perform advanced reporting. These entries show that the actual usage of Archive mailbox license option is 0 while the licensed value is 1000. create custom reports. About Symantec OpsCenter Analytics license keys Symantec OpsCenter Analytics has two types of license keys: Demo key The demo key is valid for 60 days from the day the key is generated. See “About the Symantec OpsCenter Analytics licensed features” on page 83.1 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. A permanent key does not have an expiry date.

Symantec OpsCenter lets you do operational reporting. Symantec OpsCenter Analytics lets you perform advanced. More information about the licensed features is available. business-level reporting. You cannot create or customize views using Java View Builder. Symantec OpsCenter Analytics lets you create and customize multi-level views using Java View Builder. Table 2-1 Differences between Symantec OpsCenter and Symantec OpsCenter Analytics Symantec OpsCenter Analytics Symantec OpsCenter Analytics is visible from the title bar and logon page of the OpsCenter console. and how they appear in the unlicensed version. . Symantec OpsCenter Symantec OpsCenter is visible from the title bar and logon page of the OpsCenter console. See “About the Symantec OpsCenter Analytics licensed features” on page 83. About the Symantec OpsCenter Analytics licensed features Table 2-2 shows the list of licensed features. With Symantec OpsCenter Analytics.1 Planning an OpsCenter installation 83 Symantec OpsCenter and Symantec OpsCenter Analytics differences Table 2-1 lists the differences between Symantec OpsCenter and Symantec OpsCenter Analytics. where they are located in the OpsCenter console. you have an additional reporting functionality that includes (but is not limited to) the following: ■ ■ ■ ■ Creating custom reports Creating reports using SQL queries Running or configuring charge back reports Viewing report data for any previous date You can also collect data from third-party products such as IBM TSM and EMC Networker.Installing Symantec OpsCenter 7.

back Reports Settings > Charge back Charge back settings are disabled. TSM and EMC Networker options are disabled. Report Reports > My Reports > Create a New Report > Create a Custom Report Create a report using SQL query Reports > Report Templates > Create Create a report using SQL query a New Report > Create a report using option is disabled.84 Installing Symantec OpsCenter 7. Control charge back settings Create or edit data collectors for IBM Settings > Configuration > Agent > TSM and EMC Networker Create Data Collector In the Data Collector Wizard.1 Planning an OpsCenter installation Table 2-2 Licensed feature Create a Custom Report Licensed features in Symantec OpsCenter Analytics Access on the Symantec OpsCenter Analytics console Access on the unlicensed Symantec OpsCenter console Reports > Report Templates > Create Create a custom report option is a New Report > Create a Custom disabled. SQL query Reports > My Reports > Create a New Report > Create a report using SQL query Run or view charge back reports Report > Report Templates > Charge Charge back reports are disabled. in the Select Product drop-down list. Settings > Configuration > Agent > Edit Data Collector . You cannot create or edit data collectors for third-party products.

1 is shipped with three OpsCenter DVD's.) Reports > My Reports > Create New Report (Relative and Absolute Time frame window on the Select Parameters page. Table 2-3 describes the contents of each DVD. About Symantec OpsCenter DVD's Symantec OpsCenter 7.1 Planning an OpsCenter installation 85 Table 2-2 Licensed feature Full control over report time frame selection. Time frame window on the Select Parameters page. Settings > Edit View level Alias The Edit View level Alias tab is disabled. You can view report data for any previous date. click Edit Report and then Relative and Absolute Time frame window.) Report > Report templates (Run a report.) Reports > My Reports (Run a report.Installing Symantec OpsCenter 7. Three OpsCenter DVD's are available and are a part of the NetBackup media kit. Licensed features in Symantec OpsCenter Analytics (continued) Access on the Symantec OpsCenter Analytics console Access on the unlicensed Symantec OpsCenter console Report > Report Templates > Create You cannot view data older than 60 New Report (Relative and Absolute days. click Edit Report and then Relative and Absolute Time frame window. The Object Types tab is disabled. . Edit View level Alias tab Object Types Settings > Configuration > Object Types View Builder You cannot log on to the View Builder.) Reconcile Task Monitor > Jobs. The Reconcile option The Reconcile option is disabled. under the More drop-down list is disabled.

See “About the OpsCenter licensing model” on page 81. You can either install an unlicensed version.1 Planning an OpsCenter installation Table 2-3 DVD OpsCenter (1 of 3) OpsCenter 7.1 DVD contents Platform OS Windows (x86 and x64) Contents ■ ■ ■ ■ 32-bit Windows platforms (x86) 64-bit Windows platforms (x64) ICS directory for each platform OpsCenter documentation RedHat SUSE Solaris x86 ICS directory for each platform OpsCenter documentation AIX64 HP-UX IA Solaris SPARC64 ICS directory for each platform OpsCenter documentation OpsCenter (2 of 3) UNIX ■ ■ ■ ■ ■ OpsCenter (3 of 3) UNIX ■ ■ ■ ■ ■ Note: OpsCenter 7. This document is posted at the following URL: http://www.com/docs/TECH59978 . 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. With the demo version. or purchase a Symantec OpsCenter Analytics license key and install the licensed version. About OpsCenter platform compatibility This section provides information about OpsCenter platform compatibility. you can access the Symantec OpsCenter Analytics features for 60 days (starting from the day you install the demo key).1 software is not a part of the NetBackup DVD's. a demo version.86 Installing Symantec OpsCenter 7.symantec.

32-*) where * is the kernel-smp version No Yes No No No No .1 Planning an OpsCenter installation 87 Table 2-4 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 No Yes No Yes* See Note No Yes* See Note Solaris 9 SPARC Solaris 10 x64 Solaris 10 SPARC HP Itanium 11.0 Linux SUSE 10 Linux SUSE 11 ( 2.9-*.27-*.6. 2.0. 2.6.6.5-*. 2.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.3 AIX 6.6. 2.31 AIX 5.Installing Symantec OpsCenter 7. No 5.6.18-*.16-*.6. 2.

Important notes on operating systems: ■ If installing OpsCenter on AIX. OpsCenter deployment limitations: ■ You must install Server. The OpsCenter installer automatically sets the maximum heap size to 1024 MB.ibm.0 or higher.88 Installing Symantec OpsCenter 7. ensure that you install the applicable patch for AIX from the IBM site: http://www-01. Your system may require a lesser max heap size to properly run all applications. with Veritas Cluster Server (VCS). If installing OpsCenter on AIX 6.1. Ensure that the system on which the OpsCenter server is installed has valid values for the following OS parameters: ■ ■ ■ ■ ■ ■ Display language Location Check your operating system documentation for more information on these parameters.1 Planning an OpsCenter installation Note: ‘*’ signifies 32-bit binaries working on 64-bit architecture. and View Builder of the same versions. About operating systems and OpsCenter deployment limitations This section provides important notes regarding the supported operating systems and limitations that you need to address during OpsCenter deployment. For example.1 and View Builder 7.com/support/docview. Server 7.1 is only compatible with Agent 7. ensure that the XLC runtime version is 9. OpsCenter Server and Agent are supported in a VMware virtual machine guest operating system environment.wss?uid=isg1fixinfo105097 OpsCenter Server is not supported on non-global Solaris zones. The OpsCenter Agent and View Builder are not supported on VCS. See “Adjusting the heap size for OpsCenter components” on page 221. Note: OpsCenter components are not supported if Windows or Linux OS is installed on IA-64 architecture. ■ ■ .1. Agent. Only the OpsCenter Server can be installed in a clustered mode on UNIX and Windows.

With the unlicensed version. If the OpsCenter server and the product host are in the same time zone. If 8. Ensure that the customized location that you provide does not contain spaces or special characters like %. you can perform advanced reporting from the data that is collected from all of these products. If the OpsCenter server and product host are in different time zones. For example.3 file name creation is disabled on a Windows host. ■ About OpsCenter compatible backup and archiving products This section lists the backup and archiving products that OpsCenter supports. both the OpsCenter server and the product host must show the same time. Enterprise Vault host etc. if the OpsCenter server and the product host are in the CST time zone.Installing Symantec OpsCenter 7. A backup product host or an archive product host means a supported product host that is connected to OpsCenter. ■ Ensure that the OpsCenter Server hostname does not contain any underscores like opshost. then you must do the following: ■ ■ Install OpsCenter components on a customized (non-default) location like D:\Favorites.T.T and the managed host shows and 6:00 P. you cannot collect data from third-party products like IBM TSM and EMC Networker. ). if the OpsCenter server shows 8:00 P. Examples of a backup product host or an archive product host are PureDisk host. OpsCenter may not display accurate data in the reports or in the Monitor tab and Manage tab. If you install or upgrade to OpsCenter components on a Windows host where 8. C. P.S..M.M. they must translate to the same GMT time (such as GMT -6). but show different times.M. ensure that both time zones convert to the same GMT time. it is recommended that you enable it and restart the Windows host before installing or upgrading to OpsCenter components. Note that with the licensed version of OpsCenter. NetBackup master server. Ensure that the time on the OpsCenter Server and the backup product host or the archive product host is in sync based on the time zone they are deployed in.M. Backup Exec host.3 file name creation is disabled.S. Table 2-5 lists the backup and archiving products that OpsCenter supports.1 Planning an OpsCenter installation 89 ■ Installing OpsCenter components in a location that is mounted from a remote host is not supported on UNIX. For example. such as 8:00 P. . The default installation location of OpsCenter components is C:\Program Files\Symantec. and 9:00 P.

0.1 Backup or Archiving product Symantec NetBackup Support level All supported NetBackup platforms (except 7.0. 2008 (SP2 & R2) and Solaris 9/10 Data collection is possible only with a licensed version of OpsCenter. 10 Symantec NetBackup PureDisk 6.2. 6. Symantec Backup Exec 10d. EMC NetWorker 7. 6. You can use the inbuilt Agent of the OpsCenter Server for data collection. (SP2 & R2) Symantec Enterprise Vault 7.3. 7. and Solaris 9.5.0.2. .1.2. select the Agent that is installed as Integrated Agent. You do not need a separate Agent to collect data from PureDisk.0.6. To create or configure the data collector. 2010.1 Versions 6. Windows 2008 (SP2 & R2).3 Native agent on backup servers on Windows 2003 (SP2 & R2). Native agent for Windows 2003 (SP2 & R2).5. 11d.1 Planning an OpsCenter installation Table 2-5 Backup and archiving products supported by Symantec OpsCenter 7. 6. 6.1 does not require any Agent.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). Note: OpsCenter does not Native agent on backup servers on support Symantec Backup Windows 2003 (SP2 & R2).6.0. 8. 2008 (SP2 & R2).6.0 MP7 and higher versions.1) by remote agent Note: NBU 7. 6. 2008 Exec running on NetWare.6.0.1. 6. 12.1.5 and higher versions. 6.6. 6. 6. 7. All supported Symantec Backup 2010 R2 Exec platforms by remote agent.90 Installing Symantec OpsCenter 7.5.5.1 PureDisk supported platform (PDOS) by the OpsCenter integrated Agent. 7. 12.2.

3. The OpsCenter server should be configured as a fixed host with a static IP address. it is recommended that you upgrade OpsCenter Server before upgrading the NetBackup master server. By upgrading OpsCenter Server before the NetBackup ■ ■ ■ ■ ■ . OpsCenter 7. To monitor more than one master server. 2008 (SP2 & R2) and Solaris 9/10 Data collection is possible only with a licensed version of OpsCenter. If you plan to upgrade both NetBackup master server and the OpsCenter Server..Installing Symantec OpsCenter 7. Symantec recommends that any NetBackup master server is monitored by only one OpsCenter server. An example is the master server on which the OpsCenter server software is installed. 5.1 (continued) Versions 5. About managed NetBackup master server considerations Consider the following recommendations and requirements for your managed NetBackup master servers.5 Backup or Archiving product IBM Tivoli Storage Manager (TSM) Support level All supported TSM platforms by remote agent Native agent for backup server on Windows 2003 (SP2 & R2).1. The following recommendations and requirements should be considered for your managed master servers: ■ Installation of OpsCenter server software on a NetBackup master server or media server is possible if you want to monitor only one master server. More information on sizing guidelines is available.1 Planning an OpsCenter installation 91 Table 2-5 Backup and archiving products supported by Symantec OpsCenter 7. See “About OpsCenter sizing guidelines” on page 94. For example. OpsCenter does not collect data from the managed servers that are configured within a network address translation (NAT) network.1 can monitor all NetBackup master server versions between 6. Symantec recommends that you install the OpsCenter server software on a separate standalone server. The OpsCenter Server must be at an equal or higher version than the NetBackup master server version that it monitors.0 MP7 and 7. 5.4.

1 does not require any Agent or data collector for data collection. For a 7. For a 6. for a 6. When NBSL restarts.0. review the recommendations and requirements that are listed in the earlier sections. NBSL components are included as a part of NetBackup on master and media servers. See “Adding a master server in the OpsCenter console” on page 385. and breakup jobs data. The OpsCenter server uses the NetBackup Service Lay (NBSL) to collect the data from a NetBackup 7.x master server. OpsCenter uses NBSL to collect all the other data automatically from the master server. . About using NBSL to collect data from NetBackup master servers A NetBackup master server with version 7.5. OpsCenter uses NBSL to collect all the other data automatically from the master server. More information about adding managed NetBackup servers in OpsCenter is available. an Agent must be installed if you want to collect image data.92 Installing Symantec OpsCenter 7.0. you do not need to install an Agent. scheduled jobs data. See NetBackup High Availability Administrator's Guide for more details on setting up a NetBackup cluster environment. If NBSL stops. Beginning with NetBackup version 6. OpsCenter may not capture any changes that were made to the NetBackup configuration. If you do not want to collect such data. OpsCenter requires NBSL for all NetBackup monitoring. OpsCenter correctly recaptures the latest state. you do not need to install an Agent. an Agent must be installed if you want to collect breakup jobs data. error log data. See “About managed NetBackup master server considerations” on page 91.x master server.1 Planning an OpsCenter installation master server. If you do not want to collect the breakup jobs data. an Agent must be installed if you want to collect image data or error log data.0.x master server. ■ OpsCenter can be used to monitor a NetBackup cluster. OpsCenter is affected if NBSL stops running on a managed NetBackup server. and control functions. OpsCenter can start collecting data from the master server once it is added. Similarly. managing. Design your OpsCenter Server Before setting up an OpsCenter Server.1 master server.

The following NetBackup objects determine the characteristics of the OpsCenter Server: ■ ■ ■ ■ ■ 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. This data can be policy data. or media data. 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 Number of media data records ■ The rate of OpsCenter database growth depends on the quantity of managed data.1 Planning an OpsCenter installation 93 Sizing considerations The size of your OpsCenter server depends largely on the number of NetBackup objects that OpsCenter manages. Information is available on how to adjust database values for better OpsCenter performance. job data. . See “Tuning OpsCenter for more performance” on page 213. Note the following: ■ After you configure OpsCenter. The database is installed as part of the OpsCenter server installation.Installing Symantec OpsCenter 7. the following OpsCenter Server components should be sized accordingly: ■ ■ ■ Disk space (for installed OpsCenter binary + OpsCenter database) Type and number of CPUs RAM About the OpsCenter database The Sybase database that OpsCenter uses is similar to the database that NetBackup uses. OpsCenter disk space depends on the volume of data initially loaded on the OpsCenter server from the managed NetBackup servers.

000 6000 – 10. 20-40 8 GB RAM 8 Logical 40-60 Processors. 8 GB RAM 16 Logical Processors.1 Planning an OpsCenter installation About OpsCenter sizing guidelines Table 2-6 lists the minimum hardware requirements and recommended settings for installing the OpsCenter Server. See “Tuning OpsCenter for more performance” on page 213.00.000 10.000 2000 – 4000 1000 – 10.000 – 40.000 60. Table 2-6 OpsCenter server sizing guidelines Number of alerts Number of Number of job policies media Number of jobs per day System Number of configuration NetBackup master servers to be monitored 2 Processors. Information is available on how you can tune OpsCenter for better performance. .94 Installing Symantec OpsCenter 7. You can install the OpsCenter server on a NetBackup master or media server if you want to monitor only the master server in the configuration.10. 0-20 8 GB RAM 4 Processors.000 40.000 20.000 – 1. 16 GB RAM 60-100 0 .000 50.000 Note: Some of the data in this table has been interpolated.50.000 – 50.00.000 0 – 2000 0 – 1000 0 – 20.000 1. If the number of NetBackup jobs that run daily on the master server is more than 5000.000 60. Symantec recommends that the memory of the system where you install OpsCenter Server is 8 GB or more.000 4000 – 6000 60. If NetBackup and the OpsCenter Server are installed on the same system.000 40. Symantec recommends that you install OpsCenter server software on a separate standalone system . Symantec recommends that you run no more than 5000 NetBackup jobs daily.000 40.000 – 1.000 10.000 – 60.

1 to OpsCenter 7. . Server 7.1 NOM 6.1 NOM 6.0.1 Note: If you have an earlier version of NOM or VBR. It helps you decide how to deploy the Agent in your environment. Note: You must install OpsCenter Server.Installing Symantec OpsCenter 7.2 to OpsCenter 7.6. first upgrade to a supported version. a Backup Exec host.1 Planning an OpsCenter installation 95 About supported upgrade paths OpsCenter supports direct upgrades from the following versions: ■ ■ ■ ■ ■ ■ OpsCenter 7. The deployment that you choose depends on the product that you want to collect data from and its operating system. or an Enterprise Vault host).1 is only compatible with Agent 7.1. For example. Agent. You can also deploy the OpsCenter Agent on a separate host.6. You can deploy the OpsCenter Agent on the OpsCenter Server host or the product host (for example.1 VBR 6.1.1 and View Builder 7. which is referred to as a Remote Agent. See the product documentation for details on how to upgrade.5.6 to OpsCenter 7. About OpsCenter Agent deployment This topic describes the deployment scenarios for the OpsCenter Agent.1 OpsCenter 7.1 VBR 6.4 to OpsCenter 7. and View Builder of the same version.0 to OpsCenter 7. a NetBackup master server whose version is earlier than 7.1 to OpsCenter 7.5.

x or a 6. an Agent must be installed if you want to collect data image data or error log data.0.1 Planning an OpsCenter installation Note: A NetBackup version 7. error log data. For a 7. OpsCenter uses NBSL to collect all the other data automatically from the master server. A single Agent can have multiple data collectors configured that collect data from different product hosts. OpsCenter uses NBSL to collect all the other data automatically from the master server. You can install only one Agent on a single host. you need separate OpsCenter Agents to collect data from servers with different versions. If you do not want to collect such data. The OpsCenter Server uses NBSL to collect the data automatically from the NetBackup master server. scheduled jobs data. If you do not want to collect the breakup jobs data. See “About OpsCenter compatible backup and archiving products ” on page 89.1 master server not require any Agent for data collection. .x master server that runs an earlier version than 7. Note: For NetBackup servers and EMC Networker hosts. and breakup jobs data. you must manually uninstall it. Hence for a 6.0. See “About data collection in OpsCenter” on page 347. you do not need to install an Agent. About Agent deployment for different product versions The following topic describes what how to deploy the OpsCenter Agent to collect data from different product versions.5.96 Installing Symantec OpsCenter 7. Note that for a 6.x master server. an Agent must be installed if you want to collect breakup jobs data.0. Note: You do not require an OpsCenter Agent to collect data from PureDisk. you do not need to install an Agent. (Data collectors were formerly called Agent Modules.0 MP7 master server. If you installed the VBR Agent only to collect PureDisk data. it can have multiple data collectors configured.0 MP7 master server. For a 6.) See “Installing Symantec OpsCenter on Windows and UNIX” on page 106. an Agent must be installed if you want to collect image data. you cannot collect scheduled jobs and breakup jobs data.

Backup Exec You can use the same Agent to collect data from Backup Exec servers with different versions. PureDisk PureDisk data collection does not require a separate Agent. NetBackup binaries (such as the Remote Administration Console for Windows and a UNIX media server) that you install on the Agent host must match the version of the NetBackup master server . manually uninstall the VBR Agent. scheduled jobs. Note: You do not require an OpsCenterAgent to collect data from PureDisk. The OpsCenter Agent needs to be installed on the EMC Networker server host. error log. You can use the Integrated Agent of the OpsCenter Server for data collection.x Install an Agent if you want to collect data for image or error logs.1 Planning an OpsCenter installation 97 NetBackup You need separate Agents to collect data from different versions of NetBackup master servers. To create or configure the data collector. you need to install the Agent on a compatible Windows host. EMC Networker . ■ Note: A NetBackup master server with version 7. You need different OpsCenter Agents for EMC Networker servers with different versions. You can configure an Agent to collect the following data from master server versions below 7. ■ 6.Installing Symantec OpsCenter 7. IBM TSM You can use the same OpsCenter Agent to collect data from TSM servers with different versions. See “Configuring PureDisk data collector” on page 391.0. select the Agent that is installed as the Integrated Agent.0. Note: To collect data from a Backup Exec server host.x Install an Agent if you want to collect data for breakup jobs.1 does not require any Agent for data collection.5. ■ 7.x Install an Agent if you want to collect data for image.1: 6. If you installed the VBR Agent only to collect PureDisk data. or breakup jobs.

About installing the OpsCenter Agent on a product host The OpsCenter Agent can be installed on a product host. The different host may be the OpsCenter Server host or a separate host. this is sometimes called a Remote Agent. . which can affect the backup application host’s performance. The OpsCenter Agent must be compatible with the operating system of the backup application host. because you only service one host. The following products support local Agent installation: ■ ■ ■ ■ ■ Symantec Enterprise Vault Symantec NetBackup Symantec Backup Exec IBM TSM EMC Networker Note: EMC Networker does not support remote OpsCenter Agent installation. Minimal intrusion on backup hosts. Installing the Agent on a remote backup application host has the following advantages: ■ ■ Ease of maintenance for upgrades.98 Installing Symantec OpsCenter 7. A disadvantage of installing the OpsCenter Agent on a remote backup application host is that the Agent may use significant system resources. Note: To collect Enterprise Vault archive data. Installing the OpsCenter Agent little affect on the backup environment. you must install the OpsCenter Agent on a Windows host. About installing the OpsCenter Agent on a host other than a product host The OpsCenter Agent can be installed on a host different than the product host. You must install the Agent on the EMC Networker host. because only one agent is installed on a backup host.1 Planning an OpsCenter installation Enterprise Vault You can use the same OpsCenter Agent to collect Enterprise Vault data from Microsoft SQL Servers with different versions.

1 Planning an OpsCenter installation 99 You should deploy a Remote Agent in the following situations: ■ When the OpsCenter Agent is not compatible with the operating system of the product (such as HP-UX). UNIX platforms do not support the Remote Administration Console. you need to have a backup application client executable on the Agent host to collect data remotely. or a media server installed. ensure that the Remote Agent host has the NetBackup Remote Administration Console. ■ In such situations.Installing Symantec OpsCenter 7. The following products support Remote Agent installation: ■ ■ ■ Symantec Enterprise Vault Symantec NetBackup Symantec NetBackup PureDisk Note: PureDisk does not support local Agent installation. a master server. Symantec Backup Exec IBM TSM ■ ■ Note: To collect data from a NetBackup master server. ■ Disadvantages of installing the OpsCenter Agent on the Server host include the following: . The PureDisk Server and OpsCenter Agent cannot reside on the same host. See “About collecting data from Enterprise Vault” on page 392. For backup products other than Symantec Backup Exec. Advantages of installing the OpsCenter Agent on the Server host or a different host include the following: ■ You do not have to install additional software on backup application hosts. the Agent should remotely communicate with backup products. because OpsCenter does not support the PureDisk operating system. because the backup data is gathered remotely. which avoids the maintenance that might otherwise be involved in upgrading the agent. When the product host system has insufficient resources to support co-location of the OpsCenter Agent and the backup application. You need to maintain only one host for both the OpsCenter Agent and the Server.

■ ■ ■ ■ .5 Remote Administration Console or the NetBackup master server on OpsCenterHost1 and configure a data collector to collect data from ProdHost1. You install Agent A1 on AgentHost1 and install Agent A2 on AgentHost2. the master server. You install the OpsCenter Server on OpsCenterHost1. A NetBackup 6.100 Installing Symantec OpsCenter 7. and you install another NetBackup 6. the NetBackup 6.0 Remote Admin Console or 6. and you install the NetBackup master server and the OpsCenter Agent on ProdHost1 Configure a data collector on OpsCenterHost1 to collect data from ProdHost1. a backup application license key is required for the component that is installed on the OpsCenter Server host. Install the NetBackup 6. You install the OpsCenter Server on OpsCenterHost1.0 master server exists on ProdHost1 and you install a NetBackup 6. or the media server) on the Agent host that match the version of the NetBackup master server. Install a NetBackup 6. In some situations.5 master server is on ProdHost1. You need to install NetBackup binaries (the Remote Administration Console for Windows. the following OpsCenter deployment scenarios are valid: ■ You install the OpsCenter Server on OpsCenterHost1. Install either the Remote Administration Console or master server on OpsCenterHost1 and configure two data collectors: one to collect data from ProdHost1 and another to collect data from ProdHost2.5 master server on ProdHost2.0 master server on AgentHost1 and configure a data collector to collect data from ProdHost1.5 Remote Administration Console or NetBackup master server on AgentHost1 and configure a data collector to collect data from ProdHost1. You install theOpsCenter Server and Agent on OpsCenterHost1 and install the NetBackup master server on ProdHost1. assume that you need separate OpsCenter Agents to collect data from different versions of NetBackup master servers. install the Agent on AgentHost1. You install the OpsCenter Server and Agent on OpsCenterHost1.5 master server is installed on ProdHost1. and install a NetBackup 6. ■ Examples of OpsCenter Agent deployment in a NetBackup environment In a NetBackup environment.1 Planning an OpsCenter installation ■ You must install a component of the backup application on the OpsCenter Server host.5 master server on ProdHost2. Install the NetBackup 6. For example.

OpsCenter install and upgrade checklist for Windows Task Ensure that you install OpsCenter software on a compatible platform.3 name creation is disabled. For a new OpsCenter installation.5 Remote Administration Console or 6. the database grows in size. it is recommended that you enable it and restart the Windows host before installing or upgrading to OpsCenter components. Table 2-7 Item 1. 6. 2.3 file name creation is disabled on a Windows host. . Note that after you install and start using OpsCenter.5 master server on the AgentHost2 and configure a data collector to collect data from ProdHost2 Before you install or upgrade Review the following checklists before installing OpsCenter and before upgrading from NetBackup Operations Manager (NOM) or Veritas Backup Reporter (VBR) to OpsCenter. The default installation location of OpsCenter components is C:\Program Files\Symantec. Ensure that your OpsCenter server is configured as a fixed host with a static IP address.1 Planning an OpsCenter installation 101 Install a NetBackup 6. See “About OpsCenter platform compatibility” on page 86. then you must do the following: ■ Install OpsCenter components on a customized (non-default) location like D:\Favorites. Ensure that no other installation is in progress while you install OpsCenter. and requires more space. Ensure that the fully qualified domain name (FQDN) of your OpsCenterServer has no more than 44 characters. ensure that the database directory has at least 20 MB of available space. 3. % etc. 7.Installing Symantec OpsCenter 7. Ensure that the antivirus software is disabled before you install OpsCenter. See “Design your OpsCenter Server” on page 92. ■ 4. The customized location that you provide should not contain spaces or special characters like ( . 5. Table 2-7 lists the things you must check before you install OpsCenter or upgrade from NOM or VBR to OpsCenter on a Windows server. If you install or upgrade to OpsCenter components on a Windows host where 8. If 8.

For example. @.1 is only compatible with Agent 7. install OpsCenter on the NetBackup master server or media server (recommended). 10. OpsCenter install and upgrade checklist for Windows (continued) Task If you plan to upgrade both NetBackup master server and the OpsCenter Server. Ensure that the name of the folder in which you are installing OpsCenter does not contain any special characters such as %. first upgrade to one of the compatible versions. Agent. See “About communication and firewall considerations” on page 284.4 NOM 6.5. 12. Ensure that the necessary ports are opened before you install OpsCenter on a hardened server. and View Builder of the same versions.1. If you are upgrading from NOM to OpsCenter 7.1 and View Builder 7.1 Planning an OpsCenter installation Table 2-7 Item 8. Install OpsCenter Server. $. !.102 Installing Symantec OpsCenter 7. 13 Display language Location Check your respective OS documentation for more information on these parameters. rename or delete the file before you install OpsCenter.1. NOM 6. ~. &. By upgrading OpsCenter Server before the NetBackup master server. See the NOM documentation for details on how to perform this upgrade. . If you need to monitor a single master server. Server 7. ensure that you have one of the following NOM versions installed: ■ ■ 15. or #.5.6 If you are upgrading from a NOM version that is not supported. it is recommended that you upgrade OpsCenter Server before upgrading the NetBackup master server. OpsCenter can start collecting data from the master server once it is added. 14. 9. Ensure that the system on which the OpsCenter server is installed has valid values for the following OS parameters: ■ ■ 11. If a file called program exists in the C: folder of your OpsCenter Server. ^.

1. 19. ccsvc) or databsase port numbers for VBR. if your NOM database or VBR database is 1 GB. See the VBR documentation for details on how to perform this upgrade. run DataBackupUtility.EXE from the Server directory of the OpsCenter DVD to back up the necessary data. and requires more space. .1 and have changed the default database passwords (dba. For example. OpsCenter install and upgrade checklist for UNIX Task Ensure that you install OpsCenter software on a supported platform.1 VBR 6. See “Upgrading to OpsCenter Server on a different Windows system” on page 201.2 If you are upgrading from a VBR version not supported. If you are upgrading from VBR to Symantec OpsCenter Analytics 7. OpsCenter install and upgrade checklist for Windows (continued) Task If you are upgrading from VBR to Symantec OpsCenter Analytics 7. Table 2-8 lists the things you must check before you install OpsCenter or before you upgrade from NOM or VBR to OpsCenter on a UNIX server. ensure that the OpsCenter database directory has three times as much space as your NOM database or VBR database. During the OpsCenter installation. first upgrade to one of the compatible versions.6. See “About upgrading from VBR to OpsCenter Server 7.1 Planning an OpsCenter installation 103 Table 2-7 Item 16.Installing Symantec OpsCenter 7. Table 2-8 Item 1. you must reset these to the default values before upgrading to OpsCenter 7. If you upgrade from NOM or VBR to OpsCenter on a different system (such as when you upgrade from a platform not compatible with OpsCenter). See “About OpsCenter platform compatibility” on page 86. ensure that you have one of the following VBR versions installed: ■ ■ VBR 6. Note that once you install and start using OpsCenter. the database grows. See “Design your OpsCenter Server” on page 92.6. the OpsCenter database directory must have at least 3 GB of available space. the backed up data can be restored on the compatible OpsCenter platform. 18.1. If you are upgrading from VBR or NOM. 17. guest.1 if you use customized database passwords or port numbers in VBR” on page 154.

OpsCenter install and upgrade checklist for UNIX (continued) Task Ensure that no other installation is in progress while you install OpsCenter. $. Note that once you install and start using OpsCenter. 4. Ensure that the fully qualified domain name (FQDN) of your OpsCenter Server has no more than 44 characters.1 and View Builder 7. See “About communication and firewall considerations” on page 284. Agent. 12. If you plan to upgrade both NetBackup master server and the OpsCenter Server. 10. See “Design your OpsCenter Server” on page 92. !. Server 7.1 is only compatible with Agent 7. Ensure that the OpsCenter Server does not have a symbolic link to the /opt directory. Ensure that the system on which the OpsCenter server is installed has valid values for the following OS parameters: ■ ■ 9. and View Builder of the same versions. &.1 Planning an OpsCenter installation Table 2-8 Item 2. . ensure that the database directory has at least 20 MB of available space. If you need to monitor a single master server. install OpsCenter on the NetBackup master server or media server (recommended). and requires more space. By upgrading OpsCenter Server before the NetBackup master server.104 Installing Symantec OpsCenter 7. 3. Ensure that your OpsCenter Server is configured as a fixed host with a static IP address.1. Install OpsCenter Server. 11. 5. it is recommended that you upgrade OpsCenter Server before upgrading the NetBackup master server. 8. ~. OpsCenter can start collecting data from the master server once it is added. 7. Ensure that the necessary ports are opened before you install OpsCenter on a hardened server. or #. For a new OpsCenter installation. 6. Display language Location Check your respective OS documentation for more information on these parameters. Ensure that the name of the folder in which you are installing OpsCenter does not contain any special characters such as %. @. the database grows in size. For example. ^.

6. 15.Installing Symantec OpsCenter 7. 17. ensure that you have one of the following NOM versions installed: ■ ■ NOM 6. the database grows. If you are upgrading from VBR to Symantec OpsCenter Analytics 7.2 If you are upgrading from a VBR version that is not supported. If you upgrade from VBR or NOM. first upgrade to one of the supported versions. ccsvc) or databsase port numbers for VBR. you must reset these to the default values before upgrading to OpsCenter 7. this backed up data can be restored on the compatible OpsCenter platform.5.5.6 If you are upgrading from a NOM version that is not supported. Note that after you install and start using OpsCenter. if your NOM database or VBR database is 1 GB. See “Upgrading to OpsCenter Server on a different UNIX system” on page 206. 16. run the Backup. If you upgrade from NOM or VBR to OpsCenter on a different system (such as when you upgrade from a platform not compatible with OpsCenter such as Solaris 9). and requires more space. See “About upgrading from VBR to OpsCenter Server 7.1 Planning an OpsCenter installation 105 Table 2-8 Item 13. guest.1. During the OpsCenter installation.sh script from the Server directory of the OpsCenter DVD to back up the necessary data.4 NOM 6. OpsCenter install and upgrade checklist for UNIX (continued) Task If you upgrade from NOM to OpsCenter. See the VBR documentation for details on how to perform this upgrade.1 if you use customized database passwords or port numbers in VBR” on page 154. See the NOM documentation for details on how to perform this upgrade.6. See “Design your OpsCenter Server” on page 92.1 VBR 6. first upgrade to one of the compatible versions. If you upgrade from VBR to Symantec OpsCenter Analytics. For example.1 and have changed the default database passwords (dba. the OpsCenter database directory requires at least 3 GB of available space. 14. ensure that you have one of the following VBR versions installed: ■ ■ VBR 6. . ensure that the OpsCenter database directory has three times as much space as your NOM database or VBR database.

carefully. Make sure that you satisfy the operating system requirements. and clustering. See “Installing Symantec OpsCenter 7. See “Upgrading to OpsCenter on Windows and UNIX” on page 136. See “About communication and firewall considerations” on page 284. Table 2-9 provides steps to install OpsCenter components.106 Installing Symantec OpsCenter 7. You can install OpsCenter 7. See “Installing Symantec OpsCenter 7.1 in a clustered mode. VBR.1 Installing Symantec OpsCenter on Windows and UNIX Installing Symantec OpsCenter on Windows and UNIX This section describes the procedures for fresh installation of OpsCenter 7. See “About OpsCenter platform compatibility” on page 86.1 on Windows” on page 107. . Go through the Agent deployment section.1 on Windows and UNIX hosts. See “About OpsCenter Agent deployment” on page 95. See “Clustering Symantec OpsCenter” on page 233. or OpsCenter installation. You can also upgrade from an earlier NOM. See “Before you install or upgrade” on page 101. Table 2-9 Step number Step 1 Review the hardware / software requirements for OpsCenter Server and Agent hosts. upgrade. upgrade. properly. You can use this table as a checklist while installing Symantec OpsCenter. 2 Go through the appropriate installation section. Different sections are available for fresh installation. See “Clustering Symantec OpsCenter” on page 233. verify if OpsCenter is running on UNIX” on page 111. See “Upgrading to OpsCenter on Windows and UNIX” on page 136.1 Note: After installation. Review the Install/Upgrade checklists before installing OpsCenter. and cluster Symantec OpsCenter Reference topic See “Planning an OpsCenter installation” on page 79. Go through the firewall settings and port number information. Steps to install.

enable it and restart the Windows host before installing or upgrading to OpsCenter components. 3 4 On the Symantec DVD browser. You must not run any other installation while installing OpsCenter components. Additionally after an installation is complete. ■ ■ If autorun is enabled. If autorun is not enabled. Review the following considerations before installing OpsCenter components on Windows: ■ Symantec recommends that you enable 8. click the Installation link. the Symantec DVD Browser appears. insert the OpsCenter product DVD in the DVD drive. The Symantec DVD Browser appears. Note: In case you try to install OpsCenter 7. type ‘D:\Browser.3 file name creation is disabled.1 server on Windows hosts.1 components on a system where OpsCenter 7. you should wait for some time before installing other OpsCenter components.Installing Symantec OpsCenter 7. in the Open text box. On the Run dialog box. ■ Note: Symantec recommends that you do not cancel or interrupt the installation process once it is started.1 Installing Symantec OpsCenter on Windows and UNIX 107 Installing Symantec OpsCenter 7.3 file name creation before installing OpsCenter components. .1 software for all available platforms. Installing Symantec OpsCenter Server on Windows Use the following procedure to install Symantec OpsCenter 7. The three OpsCenter DVD's contain OpsCenter 7.1 is already installed. click Start > Run. Click the OpsCenter Server Installation link to install Symantec OpsCenter server.1 on Windows Use the Installation Wizard to install OpsCenter on a Windows host. the installer runs in a Maintenance mode and lets you repair or remove the OpsCenter component that is installed on your system.exe’ and press Enter: Where D is the DVD drive. If 8. To install OpsCenter Server on Windows 1 2 On a Windows host where you want to install OpsCenter server.

Read the license agreement. Under Custom. Click Custom if you want to change the default settings. installation location.1 server software on a different Windows system. See “About managing licenses” on page 307. locations. Click Next. check ‘I accept the terms of the license agreement’ and click Next. enter your demo or permanent key that you have received with the purchase of OpsCenter and click Add Key. . See “About Symantec OpsCenter Analytics license keys” on page 82.1 Installing Symantec OpsCenter on Windows and UNIX 5 6 7 The Symantec OpsCenter Installation Wizard appears. You can also add the license keys later from the OpsCenter console. The following options are displayed: Install to this computer only Select this option to install OpsCenter Server on this host.1 on Windows 2008. See “Clustering Symantec OpsCenter Server on Solaris” on page 248. click Typical to use the default settings. Select this option if you are upgrading from NOM or VBR to OpsCenter 7.108 Installing Symantec OpsCenter 7. Click Next. An example scenario is when NOM or VBR is running on Windows 2000 and you require the same data with OpsCenter 7. See “Clustering Symantec OpsCenter on Windows” on page 237. you do not need to restore any data. Also compare the space that is required by the installation with the actual space available in the installation directory. Install a clustered OpsCenter Select this option to install OpsCenter Server on all Server selected nodes. or port numbers. 9 On the License Keys screen. 8 In the Installation Method section. or port numbers. This option is enabled if you have Veritas Cluster Server (VCS) installed. Select Install to this computer only. you can also select the Upgrade using a backed up VBR or NOM database on a different system option. If you have not been using NOM or VBR and are only installing OpsCenter for the first time. You need to install OpsCenter Server manually on each node of the cluster. in a clustered mode.

To install OpsCenter Agent 1 You can install the OpsCenter Agent either on the OpsCenter Server host. Check Save Summary to field to save the installation summary. Click the OpsCenter Agent Installation link to install OpsCenter Agent.1 Installing Symantec OpsCenter on Windows and UNIX 109 10 Click Next. ■ ■ If autorun is enabled. in the Open text box. The Symantec OpsCenter Installation Wizard appears. you can view the OpsCenter console or view installation logs. type ‘D:\Browser. . Installing Symantec OpsCenter Agent on Windows Use the following procedure to install Symantec OpsCenter Agent on a Windows host. check ‘I accept the terms of the license agreement’ and click Next. 13 Click Finish. 11 Click Install.exe’ and press Enter: Where D is the DVD drive. To decide where you want to install the OpsCenter Agent. review the information on Agent deployments. click the Installation link. The installer shows the summary of the settings that you have selected for installation. the Symantec DVD Browser appears. The installer starts installing the OpsCenter Server software. insert the OpsCenter product DVD in the DVD drive. On the Run dialog box. Click Browse to save the installation summary in your preferred location. See “About OpsCenter Agent deployment” on page 95. or a separate host. The Symantec DVD Browser appears. Note: The default OpsCenter database location on Windows is: C:\Program Files\Symantec\OpsCenter\server\db\data 12 After successful installation. Read the license agreement. product host. 2 3 On a Windows host where you want to install OpsCenter Agent. If autorun is not enabled. click Start > Run.Installing Symantec OpsCenter 7. Click Next. 4 5 6 7 On the Symantec DVD Browser.

Installing Symantec OpsCenter View Builder on Windows Use the following procedure to install Symantec OpsCenter View Builder. 11 After successful installation. The Symantec DVD Browser appears. type ‘D:\Browser. To install OpsCenter to a different directory. ■ ■ If autorun is enabled. insert the OpsCenter product DVD in the DVD drive. If autorun is not enabled. click the Installation link. 9 The installer shows the summary of the settings that you have selected for Agent installation. click Browse. Click Next. 3 4 5 6 On the Symantec DVD Browser. 12 Click Finish. The Symantec OpsCenter Installation Wizard appears. Note: The default installation location on a Windows 64-bit machine is C:\Program Files (x86)\Symantec. The installer starts installation of OpsCenter Agent.110 Installing Symantec OpsCenter 7. To install OpsCenter View Builder 1 2 On the OpsCenter Server host. Click the OpsCenter View Builder Installation link to install Symantec OpsCenter View Builder. check ‘I accept the terms of the license agreement’ and click Next.exe’ and press Enter: Where D is the DVD drive. you can view Agent installation logs or open the readme file. 10 Click Install. Click Browse to save the installation summary in your preferred location. in the Open text box.1 Installing Symantec OpsCenter on Windows and UNIX 8 The default installation location is C:\Program Files\Symantec. the Symantec DVD Browser appears. . click Start > Run. Check Save Summary to field to save the installation summary. Click Next. Read the license agreement. On the Run dialog box.

11 After successful installation.1 on UNIX This section provides you with the procedure to install OpsCenter on a UNIX host. Click Browse to save the installation summary in your preferred location. you can view the installation logs or open the readme file. Installing Symantec OpsCenter Server on UNIX Use the following procedure to install OpsCenter Server 7. The installer shows the summary of the settings that you have selected for Symantec OpsCenter View Builder installation.1 on UNIX 1 2 Open a UNIX console and log on as root on the target host. Select the appropriate OpsCenter DVD based on the platform on which you are installing. 8 9 Select a new location and click Next. 10 Click Install.one for Windows and two for UNIX. To install OpsCenter Server 7. . You can install OpsCenter components from the OpsCenter DVD's. 12 Click Finish. Note: The default installation location on a Windows 64-bit machine is C:\Program Files (x86)\Symantec. The installer starts installation of Symantec OpsCenter View Builder.1 software on UNIX hosts.Installing Symantec OpsCenter 7. Note: Symantec recommends that you do not cancel or interrupt the installation process once it is started. Mount the appropriate OpsCenter product DVD on the computer where you are installing OpsCenter 7.1 Installing Symantec OpsCenter on Windows and UNIX 111 7 On the Installation Location screen. Check Save Summary to field to save the installation summary. Installing Symantec OpsCenter 7. click Browse if you want to change the default location for Symantec OpsCenter View Builder installation. Three DVD's for OpsCenter are available .1.

It prompts you in case OpsCenter Server is already installed. Press Enter to continue. OpsCenter Server. 4 5 The Welcome message is displayed./install. If you are installing OpsCenter on Solaris Sparc. The installer then checks if OpsCenter Server is installed on the system or not. Review this list and press Enter to continue. To accept the default path (/opt).1 Installing Symantec OpsCenter on Windows and UNIX 3 Type the following command: . . OpsCenter GUI etc. 8 Type y to confirm the directory path and press Enter. select Server from the displayed options (Server and Agent). The installer prompts you with the following question: Where do you want to install Symantec OpsCenter? </opt> 6 7 Type a directory path where you want to install the Symantec OpsCenter Server packages and press Enter. press Enter without typing a directory path. The installer displays a list of components that get installed like PBX.112 Installing Symantec OpsCenter 7. Press Enter to install OpsCenter Server. Press Enter. The installer also examines the system for existing packages. AT.

press Enter without typing a directory path. the script creates the folder OpsCenterServer below your directory.q] (n) To use the database installation directory for database server temporary space. To specify an alternate directory. the following information is displayed: Directory "/var/symantec" does not exist. press Enter without typing a directory path. The following information is displayed: The OpsCenter database server may require up to 1 GB of temporary space at runtime. . By default. 11 Review the installation options you selected.Installing Symantec OpsCenter 7. Type a directory path for the database server temporary space and press Enter. A directory named 'OpsCenterServer' will be created within the directory that you specify. The installer prompts for the following information: Specify a location for the Symantec OpsCenter database. temporary files will be created in the database installation directory /var/Symantec/OpsCenterServer 10 You are prompted with the following message: Would you like to use an alternate directory for database server temporary space? [y. To accept the default database installation directory (/var/Symantec). (/var/symantec/) Type a directory path under which to install the OpsCenter database and press Enter. The location of database directory and the database temp directory is also displayed. type y and press Enter.1 Installing Symantec OpsCenter on Windows and UNIX 113 9 OpsCenter Server is installed on the system.n. If you create an alternate database directory.n. In case the database installation directory (/var/symantec) does not exist on the host.q] y Type y to confirm and press Enter. Do you want to create the directory? [y.

To upgrade on a different server or platform. Type n and then press Enter.sh script [y.1 on Solaris 10.114 Installing Symantec OpsCenter 7. See “About Symantec OpsCenter Analytics license keys” on page 82.q] <n> If you have not been using NOM or VBR and are only installing OpsCenter for the first time. use Backup. 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.sh script to back up your data on the NOM or VBR server and then copy it to the OpsCenter 7. You are prompted with the following question: Do you want to restore data that has been backed up manually using Backup. With the unlicensed version (Symantec OpsCenter). 14 You are prompted for license information.sh script is located in the Server directory of the OpsCenter DVD. Type n and press Enter to repeat the configuration steps and revise your selection. The Backup.n. 13 Configuration changes are made to the system. Use this option if you are upgrading from NOM or VBR to OpsCenter 7. Installing Symantec OpsCenter Agent on UNIX Use the following procedure to install OpsCenter Agent on UNIX. you do not need to restore any data.1 server software on a different UNIX system. See “About managing licenses” on page 307. See “Upgrading to OpsCenter Server on a different UNIX system” on page 206. you get an unlicensed version. . If you do not enter a key.1 Installing Symantec OpsCenter on Windows and UNIX 12 Type y and press Enter to confirm the selection and continue. An example scenario is when NOM or VBR is running on Solaris 8 and you require the same data with OpsCenter 7.1 server. You can also add the license keys later from the OpsCenter console. More information on how to upgrade to OpsCenter server on a different system is available. you cannot access the licensed features.

4 5 6 7 8 Select Agent from the displayed options (Server and Agent). The Welcome message is displayed. summary. The installer displays a list of components that get installed like PBX. The installer then checks if OpsCenter Agent is installed on the system or not. You may choose to configure OpsCenter Agent later either manually or by running /opt/VRTS/install/installOpsCenterAgent -configure command. 10 Type y and then press Enter to confirm your installation options. press Enter without typing a directory path. To configure OpsCenterAgent now. Press Enter. Installing Symantec OpsCenter silently on Windows This section lists the procedure on how you can install the OpsCenter components silently on Windows platform. To accept the default path (/opt). It is optional to configure the OpsCenter Agent during installation.1 Installing Symantec OpsCenter on Windows and UNIX 115 To install OpsCenter Agent on UNIX 1 2 3 Open a UNIX console and log on as root on the target host. Note: The installOpsCenterAgent acript is also present in the Solaris_Sparc64/Agent directory of the DVD. Press Enter to install OpsCenter Agent. and response files on the path mentioned. Type a directory path where you want to install the Symantec OpsCenter Agent packages and press Enter./install.Installing Symantec OpsCenter 7. It prompts you in case OpsCenter Agent is already installed. You can view the installation log files. 9 Enter the location where you want to install OpsCenter Agent. Type the following command: . It also lists how you can track the progress of silent installation and some troubleshooting tips. Press Enter to continue. Review this list and press Enter to continue. 11 The OpsCenter Agent is installed. Symantec WebGUI Agent etc. . type y and press Enter. Mount the appropriate OpsCenter product DVD on the computer where you are installing OpsCenter Agent.

Insert the appropriate OpsCenter product DVD in the DVD drive. Silent installation of OpsCenter is not supported on clusters. check ‘I accept the terms of the license agreement’ and click Next. You must create a response file first and then use the file to perform a silent installation.1 Installing Symantec OpsCenter on Windows and UNIX Installing OpsCenter silently A silent installation avoids the need for interactive input. Navigate to <DVD Drive>\<Architecture>\Server directory. You can also edit the response file if required. Use a silent installation when you need to perform an identical installation on several servers. 5 6 The Welcome screen of the Symantec OpsCenter Installation Wizard appears.EXE -NoInstall Note that the switch -NoInstall is case sensitive. Note that the Installation Wizard creates the response file based on your inputs and does not install the product. The procedure for creating a response file requires that you run through the Installation Wizard.116 Installing Symantec OpsCenter 7. This command starts the Installation Wizard where you can specify your preferences. See “About editing the response file” on page 133. . Read the license agreement. A silent installation uses a response file to automate OpsCenter installation. To install OpsCenter server software silently 1 2 3 Log on as administrator to the system where you want to install OpsCenter server software. The values that you specify in the Wizard pages are saved to the response file. Note the following points about silent installation: ■ ■ Silent installation of OpsCenter is only supported on Windows platforms. Open the command prompt on your system. Click Next. Example: D:\x86\Server 4 Enter the following command: SETUP.

. you get an unlicensed version. With the unlicensed version (Symantec OpsCenter). 9 The installer shows the summary of the settings that you have selected for installation. or port numbers. Click Finish. installation location.XML is created at the following location: ‘%TEMP%\Symantec\OpsCenter This XML file can be used to install OpsCenter Server software on multiple machines. 10 The Installation Status screen is displayed. 12 On the command prompt. In the Installation Method section. If you do not enter a key. ensure that you are in the directory where SETUP. locations. Check Save Summary to field to save the installation summary. Note: Click Custom if you want to change the default settings. enter your demo or permanent key that you have received with the purchase of OpsCenter and click Add Key. Click Next. Click Next.Installing Symantec OpsCenter 7.EXE is located. 8 On the License Keys screen. Also compare the space that is required by the installation with the actual space available in the installation directory. Click Browse to save the installation summary in your preferred location. click Typical to use the default settings. See Symantec OpsCenter Administrator's Guide for licensing details. or port numbers.1 Installing Symantec OpsCenter on Windows and UNIX 117 7 Select Install to this computer only on the Installation Choice screen. you cannot access the licensed features. 11 A response file named Server-<DD-MM-YY-HH-MIN-SS>. Click Install. Note that clicking Install does not install the product.

Example: D:\x86\Agent 4 Enter the following command: SETUP. Open the command prompt on your system. To install OpsCenter Agent silently 1 2 3 Log on as administrator to the system where you want to install OpsCenter Agent software. Read the license agreement. After successful installation. 5 6 The Symantec OpsCenter Installation Wizard appears. check ‘I accept the terms of the license agreement’ and click Next. See “About tracking the progress of silent installation and troubleshooting tips” on page 134.xml Note that the switches -Silent and -RespFile are case sensitive. This command starts the Installation Wizard where you can specify your preferences.1 Installing Symantec OpsCenter on Windows and UNIX 13 Enter the following command to run the silent installation: SETUP -Silent -RespFile <path of the response file> Example: Setup -Silent -RespFile C:\Server-07-12-09-06-11-31. Click Next. Insert the appropriate OpsCenter product DVD in the DVD drive.118 Installing Symantec OpsCenter 7. Navigate to <DVD Drive>\<Architecture>\Agent directory. Note that the Installation Wizard creates the response file based on your inputs and does not install the product. 14 The installation logs are generated at the following location: %ALLUSERSPROFILE%\Symantec\OPSCENTER\INSTALLLOGS See the following section to track the progress of the installation. you can see Symantec OpsCenter Server in Add/Remove Programs. .EXE -NoInstall Note that the switch -NoInstall is case sensitive.

9 10 The Installation Status screen is displayed.XML is created at the following location: %TEMP%\Symantec\OpsCenter This XML file can be used to install OpsCenter Agent software on multiple machines. 14 The installation logs are generated at the following location: %ALLUSERSPROFILE%\Symantec\OPSCENTER\INSTALLLOGS See the following section to track the progress of the installation.EXE is located.1 Installing Symantec OpsCenter on Windows and UNIX 119 7 The default installation location is C:\Program Files\Symantec. Click Browse to save the installation summary in your preferred location. Note that clicking Install does not install the product. 12 On the command prompt. click Browse. . 11 A response file named Agent-<DD-MM-YY-HH-MIN-SS>. Check Save Summary to field to save the installation summary. After successful installation. Click Install.xml Note that the switches -Silent and -RespFile are case sensitive. you can see Symantec OpsCenter Agent in Add/Remove Programs. Note: The default installation location on a Windows 64-bit machine is C:\Program Files (x86)\Symantec. 13 Enter the following command to run the silent installation: SETUP -Silent -RespFile <path of the response file> Example: Setup -Silent -RespFile C:\Agent-07-12-09-06-11-31. Click Finish. ensure that you are in the directory where SETUP. Click Next.Installing Symantec OpsCenter 7. 8 The installer shows the summary of the settings that you have selected for Agent installation. To install OpsCenter to a different directory. See “About tracking the progress of silent installation and troubleshooting tips” on page 134.

Note: The default installation location on a Windows 64-bit machine is C:\Program Files (x86)\Symantec. Click Browse to save the installation summary in your preferred location. Click Next. click Browse. Click Next. This command starts the Installation Wizard where you can specify your preferences. . 9 Click Install.EXE -NoInstall Note that the -NoInstall switch is case sensitive.XML is created at the following location: ‘%TEMP%\Symantec\OpsCenter This XML file can be used to install OpsCenter View Builder software on multiple machines. Open the command prompt on your system. To install OpsCenter View Builder to a different directory. Note that clicking Install does not install the product. Check Save Summary to field to save the installation summary.1 Installing Symantec OpsCenter on Windows and UNIX To install View Builder silently 1 2 3 Log on as administrator to the system where you want to install OpsCenter View Builder software.120 Installing Symantec OpsCenter 7. Example: D:\x86\ViewBuilder 4 Enter the following command: SETUP. Click Finish. Insert the appropriate OpsCenter product DVD in the DVD drive. Read the license agreement. Navigate to <DVD Drive>\<Architecture>\ViewBuilder directory. 8 The installer shows the summary of the settings that you have selected for Symantec OpsCenter View Builder installation. check ‘I accept the terms of the license agreement’ and click Next. 5 6 7 The Symantec OpsCenter Installation Wizard appears. 10 The Installation Status screen is displayed. The default installation location is C:\Program Files\Symantec. 11 A response file named ViewBuilder-<DD-MM-YY-HH-MIN-SS>. Note that the Installation Wizard creates the response file based on your inputs and does not install the product.

Insert the appropriate OpsCenter DVD in the DVD drive. .1 Installing Symantec OpsCenter on Windows and UNIX 121 12 On the command prompt.xml Note that the switches -Silent and -RespFile are case sensitive.EXE is located. 14 The installation logs are generated at the following location: %ALLUSERSPROFILE%\Symantec\OPSCENTER\INSTALLLOGS See the following section to track the progress of the installation. ensure that you are in the directory where SETUP. 13 Enter the following command to run the silent installation: SETUP -Silent -RespFile <path of the response file> Example: Setup -Silent -RespFile C:\ViewBuilder-07-12-09-06-11-31.1 Server 1 2 3 Log on as administrator to the NOM system or VBR system where you want to install OpsCenter server software. Navigate to <DVD Drive>\<Architecture>\Server directory. This command starts the Installation Wizard where you can specify your preferences. After successful installation. Upgrading silently from NOM and VBR to OpsCenter Use the following procedures to upgrade to OpsCenter components silently. Note that the Installation Wizard creates the response file based on your inputs and does not install the product. See “About tracking the progress of silent installation and troubleshooting tips” on page 134.Installing Symantec OpsCenter 7. you can see Symantec OpsCenter View Builder in Add/Remove Programs. To upgrade silently from NOM or VBR to OpsCenter 7. Example: D:\x86\Server 4 Enter the following command: SETUP.EXE -NoInstall Note that the -NoInstall switch is case sensitive. Open the command prompt on your system.

or port numbers. or port numbers. locations. enter a port number on which the old NOM or VBR database can be started. all existing NOM services are stopped automatically. installation location. you can manually uninstall NOM.5’ Before you upgrade to Symantec OpsCenter. After you successfully upgrade to Symantec OpsCenter. The default location is C:\Program Files\Symantec\OpsCenter\SavedData. Also compare the space that is required for installing OpsCenter server and the actual space that is available. click Typical to use the default settings. Click Next. . Click Next. In the Installation Method section. check ‘I accept the terms of the license agreement’ and click Next. Click Next. Click Next.122 Installing Symantec OpsCenter 7. The default port number is 13799. Note: Click Custom if you want to change the default settings. Note: Ensure that the database location has adequate space by going through the Disk space requirements section on this page. Click Browse to specify a different location. For example. 6 7 Read the license agreement.1 Installing Symantec OpsCenter on Windows and UNIX 5 The Installation Wizard detects an existing installation of NetBackup Operations Manager or Veritas Backup Reporter on the system. 8 Specify a location for saving the old NOM or VBR database. 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. 9 On the Upgrade Settings page. A green checkmark appears in the Required column if there is adequate disk space.

14 On the command prompt. you get an unlicensed version (Symantec OpsCenter). Click Browse to save the installation summary in your preferred location. ensure that you are in the directory where SETUP.XML is created at the following location: %TEMP%\Symantec\OpsCenter This XML file can be used to install OpsCenter server software on multiple machines. Note that clicking Install does not install the product.1 Installing Symantec OpsCenter on Windows and UNIX 123 10 On the License Keys screen. Check Save Summary to option to save the installation summary. enter your demo or permanent key that you have received with the purchase of OpsCenter and click Add Key. The license keys that are already installed on the system are displayed in the box that appears on this screen. Click Install. Click Finish. 12 The Installation Status screen is displayed. you cannot access the licensed features. 11 The installer shows a summary of the settings that you have selected for installation. . Click Next.EXE is located. The license type information is also shown along with the key. your existing license keys are used.Installing Symantec OpsCenter 7. 13 A response file named Server-<DD-MM-YY-HH-MIN-SS>. If you are upgrading from NOM and you do not enter a key. With an unlicensed version. If you are upgrading from VBR and you do not enter a license key. See the Symantec OpsCenter Administrator’s Guide for more information about licenses.

Navigate to <DVD Drive>\<Architecture>\Agent directory. Open the command prompt on your system. Note that the Installation Wizard creates the response file based on your inputs and does not install the product. Insert the appropriate OpsCenter DVD in the DVD drive.1 Installing Symantec OpsCenter on Windows and UNIX 15 Enter the following command to run the silent installation: SETUP -Silent -RespFile <path of the response file> Example: Setup -Silent -RespFile C:\Server-07-12-09-06-11-31. 16 The installation logs are generated at the following location: %ALLUSERSPROFILE%\Symantec\OPSCENTER\INSTALLLOGS See the following section to track the progress of the installation. Example: D:\x86\Agent 4 Enter the following command: SETUP. After successful installation. .124 Installing Symantec OpsCenter 7. you can see Symantec OpsCenter Server in Add/Remove Programs.1 Agent 1 2 3 Log on as administrator to the VBR Agent system that you want to upgrade to OpsCenter server software. This command starts the Installation Wizard where you can specify your preferences.xml Note that the switches -Silent and -RespFile are case sensitive. To upgrade silently from VBR Agent to OpsCenter 7.EXE -NoInstall Note that the -NoInstall switch is case-sensitive. See “About tracking the progress of silent installation and troubleshooting tips” on page 134.

ensure that you are in the directory where SETUP.1 Installing Symantec OpsCenter on Windows and UNIX 125 5 The Symantec OpsCenter Installation Wizard appears. Click Install. After you successfully upgrade to Symantec OpsCenter Agent.EXE is located. Click Next to continue. following location: %TEMP%\Symantec\OpsCenter\ 10 A response file named Agent-<DD-MM-YY-HH-MIN-SS>. Based on your installed VBR Agent version. Ensure that the installation directory that you specify has adequate space by going through the Disk space requirements section on this page. 8 The installer shows a summary of the settings that you have selected for Symantec OpsCenter Agent installation. Click Browse to save the installation summary in your preferred location. click Browse if you want to change the default location for Symantec OpsCenter Agent installation. 6 7 Read the license agreement. 11 On the command prompt. . A green checkmark appears in the Required column if there is adequate disk space. On the Installation Location screen.Installing Symantec OpsCenter 7. The Installation Wizard detects an existing installation of Veritas Backup Reporter Agent on the system. 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>’ Before you upgrade to Symantec OpsCenter Agent. 9 The Installation Status screen is displayed. Select a new location and click Next. Note that clicking Install does not install the product. check ‘I accept the terms of the license agreement’ and click Next. Check Save Summary to field to save the installation summary. all Veritas Backup Reporter services are stopped automatically. Click Finish.XML is created at the This XML file can be used to install OpsCenter Agent software on multiple machines. you must manually uninstall Veritas Backup Reporter Agent.

In order to upgrade to a newer version.xml Note that the switches -Silent and -RespFile are case sensitive. . Open the command prompt on your system. This command starts the Installation Wizard where you can specify your preferences.1 View Builder 1 2 3 Log on as administrator to the VBR View Builder system that you want to upgrade to OpsCenter View Builder software. the existing Veritas Backup Reporter View Builder will be removed.1 Installing Symantec OpsCenter on Windows and UNIX 12 Enter the following command to run the silent installation: SETUP -Silent -RespFile <path of the response file> Example: Setup -Silent -RespFile C:\Agent-07-12-09-06-11-31. 13 The installation logs are generated at the following location: %ALLUSERSPROFILE%\Symantec\OPSCENTER\INSTALLLOGS See the following section to track the progress of the installation. Note that the Installation Wizard creates the response file based on your inputs and does not install the product.EXE -NoInstall Note that the -NoInstall switch is case sensitive. Example: D:\x86\ViewBuilder 4 Enter the following command: SETUP. Navigate to <DVD Drive>\<Architecture>\ViewBuilder directory. Insert the appropriate OpsCenter DVD in the DVD drive.126 Installing Symantec OpsCenter 7. To upgrade silently from VBR View Builder to OpsCenter 7. 5 The Symantec OpsCenter Installation Wizard appears.' Click Next to continue. The Installation Wizard detects an existing Veritas Backup Reporter View Builder and shows the following message on the Welcome page: ‘The Installation has detected that the following software is already installed on your system: Veritas Backup Reporter View Builder: <version>. After successful installation. See “About tracking the progress of silent installation and troubleshooting tips” on page 134. you can see Symantec OpsCenter Agent in Add/Remove Programs.

1 to OpsCenter 7.0. 11 Enter the following command to run silent installation: Setup -Silent -RespFile <path of the response file> Example: Setup -Silent -RespFile C:\ViewBuilder-07-12-10-06-11-31.xml Note that the switches -Silent and -RespFile are case sensitive. 10 On the command prompt.EXE is located. . Upgrading silently from OpsCenter 7. A green checkmark appears in the Required column if there is adequate disk space.1 Use the following procedures to upgrade to OpsCenter components silently. ensure that you are in the directory where SETUP. 8 The installer shows a summary of the settings that you have selected for Symantec OpsCenter View Builder installation. Click Browse to save the installation summary in your preferred location. click Browse if you want to change the default location for Symantec OpsCenter View Builder installation. 12 The installation logs are generated at the following location: %ALLUSERSPROFILE%\Symantec\OPSCENTER\INSTALLLOGS See the following section to track the progress of the installation.0 and 7. 9 A response file named ViewBuilder-<DD-MM-YY-HH-MIN-SS>. Select a new location and click Next. you can see Symantec OpsCenter View Builder in Add/Remove Programs. Click Install. See “About tracking the progress of silent installation and troubleshooting tips” on page 134.Installing Symantec OpsCenter 7.XML is created at the following location: %TEMP%\Symantec\OpsCenter\ This XML file can be used to install OpsCenter View Builder software on multiple machines. check ‘I accept the terms of the license agreement’ and click Next. After successful installation. On the Installation Location screen. Check Save Summary to field to save the installation summary.1 Installing Symantec OpsCenter on Windows and UNIX 127 6 7 Read the license agreement. Ensure that the installation directory that you specify has adequate space by going through the Disk space requirements section on this page.

This command starts the Installation Wizard where you can specify your preferences. the existing Symantec OpsCenter Server will be removed. installation location.1 to OpsCenter 7. the following message may be displayed on the Welcome screen: The Installation has detected that the following software is already installed on your system: Symantec OpsCenter Server: Version 7. click Typical to use the default settings. Insert the appropriate OpsCenter DVD in the DVD drive.EXE -NoInstall Note that the -NoInstall switch is case sensitive. Example: D:\x86\Server 4 Enter the following command: SETUP. . check ‘I accept the terms of the license agreement’ and click Next. Also compare the space that is required for installing OpsCenter server and the actual space that is available. For example.0 or 7. Open the command prompt on your system.0.1 system that you want to upgrade to OpsCenter 7.0. Note: You cannot customize the default settings. locations. Click Next.1. or port numbers while upgrading from OpsCenter 7.0 In order to upgrade to a newer version. Note that the Installation Wizard creates the response file based on your inputs and does not install the product. Navigate to <DVD Drive>\<Architecture>\Server directory.1 Server 1 2 3 Log on as administrator to the OpsCenter 7. 5 The Installation Wizard detects an existing installation of OpsCenter 7. Click Next.0.1. In the Installation Method section.1 Server to OpsCenter 7.0 or 7.0.128 Installing Symantec OpsCenter 7. 6 7 Read the license agreement.0 Server or OpsCenter 7.1 Installing Symantec OpsCenter on Windows and UNIX To upgrade from OpsCenter 7.1 on the system.0 or 7. or port numbers.

Click Browse to save the installation summary in your preferred location. you are prompted to create it. See “About Symantec OpsCenter Analytics license keys” on page 82. enter your demo or permanent key that you have received with the purchase of OpsCenter and click Add Key. Click Finish. In case the directory C:\Program Files\Symantec\OpsCenter_SavedData does not exist. ensure that you are in the directory where SETUP. A green checkmark appears in the Required column if there is adequate disk space. Click Yes to create the directory.EXE is located. Note: Ensure that the database location has adequate space by going through the Disk space requirements section on this page. 10 The installer shows a summary of the installation settings.1 database.0. . 13 On the command prompt.XML is created at the following location: %TEMP%\Symantec\OpsCenter This XML file can be used to upgrade OpsCenter Server software on multiple machines. 11 The Installation Status screen is displayed. 12 A response file named Server-<DD-MM-YY-HH-MIN-SS>. Click Install. 9 On the License Keys screen. Click Next.1 Installing Symantec OpsCenter on Windows and UNIX 129 8 Specify a location for saving the old OpsCenter 7. Note that clicking Install does not install the product.Installing Symantec OpsCenter 7. The default location is C:\Program Files\Symantec\OpsCenter_SavedData.0 or 7. Check Save Summary to option to save the installation summary. Click Browse to specify a different location.

0.0 In order to upgrade to a to a newer version. Click Next to continue.0 pr 7.1 Agent on the system. . The Installation Wizard detects an existing installation of OpsCenter 7.0 or 7. To upgrade silently from OpsCenter 7.1 in Add/Remove Programs. Open the command prompt on your system.1 Agent 1 2 3 Log on as administrator to the OpsCenter Agent system that you want to upgrade. After successful installation. you can see Symantec OpsCenter Server 7. Insert the appropriate OpsCenter DVD in the DVD drive.1 Agent to OpsCenter 7. Note that the Installation Wizard creates the response file based on your inputs and does not install the product.1 Installing Symantec OpsCenter on Windows and UNIX 14 Enter the following command to run the silent installation: SETUP -Silent -RespFile <path of the response file> Example: Setup -Silent -RespFile C:\Server-07-12-10-06-11-31. Example: D:\x86\Agent 4 Enter the following command: SETUP.130 Installing Symantec OpsCenter 7. See “About tracking the progress of silent installation and troubleshooting tips” on page 134. 5 The Symantec OpsCenter Installation Wizard appears. Navigate to <DVD Drive>\<Architecture>\Agent directory. 15 The installation logs are generated at the following location: %ALLUSERSPROFILE%\Symantec\OPSCENTER\INSTALLLOGS See the following section to track the progress of the installation.xml Note that the switches -Silent and -RespFile are case sensitive. This command starts the Installation Wizard where you can specify your preferences. the existing Symantec OpsCenter Agent will be removed. Based on your installed OpsCenter Agent version. the following message may be displayed on the Welcome screen: The Installation has detected that the following software is already installed on your system: Symantec OpsCenter Agent: Version 7.EXE -NoInstall Note that the -NoInstall switch is case-sensitive.0.

Click Browse to save the installation summary in your preferred location. See “About tracking the progress of silent installation and troubleshooting tips” on page 134. 11 Enter the following command to run the silent installation: SETUP -Silent -RespFile <path of the response file> Example: Setup -Silent -RespFile C:\Agent-07-12-09-06-11-31.1 View Builder 1 2 Log on as administrator to the OpsCenter View Builder system that you want to upgrade.xml Note that the switches -Silent and -RespFile are case sensitive. After successful installation.Installing Symantec OpsCenter 7. Note that clicking Install does not install the product. 8 9 The Installation Status screen is displayed.1 View Builder to OpsCenter 7. The installer shows a summary of the settings that you have selected for Symantec OpsCenter Agent installation.1 Installing Symantec OpsCenter on Windows and UNIX 131 6 7 Read the license agreement.0. check ‘I accept the terms of the license agreement’ and click Next.1 in Add/Remove Programs.0. Click Finish. you can see Symantec OpsCenter Agent 7.1 Agent software on multiple machines. 12 The installation logs are generated at the following location: %ALLUSERSPROFILE%\SYMANTEC\OPSCENTER\INSTALLLOGS See the following section to track the progress of the installation. Check Save Summary to field to save the installation summary. 10 On the command prompt. ensure that you are in the directory where SETUP.EXE is located. To upgrade silently from OpsCenter 7. Click Install.0 or 7.0 or 7.XML is created at the following location: %TEMP%\Symantec\OpsCenter\ This XML file can be used to upgrade OpsCenter 7. . A response file named Agent-<DD-MM-YY-HH-MIN-SS>. Insert the appropriate OpsCenter DVD in the DVD drive.

. 5 The Symantec OpsCenter Installation Wizard appears.EXE is located.0 In order to upgrade to a to a newer version. ensure that you are in the directory where SETUP. 6 7 Read the license agreement. The installer shows a summary of the settings that you have selected for Symantec OpsCenter View Builder installation. Note that the Installation Wizard creates the response file based on your inputs and does not install the product. the existing Symantec OpsCenter View Builder will be removed. Click Browse to save the installation summary in your preferred location.1 Installing Symantec OpsCenter on Windows and UNIX 3 Open the command prompt on your system. Navigate to <DVD Drive>\<Architecture>\ViewBuilder directory. The Installation Wizard detects an existing OpsCenter 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: Symantec OpsCenter View Builder: Version 7.132 Installing Symantec OpsCenter 7.EXE -NoInstall Note that the -NoInstall switch is case sensitive. Click Install. This command starts the Installation Wizard where you can specify your preferences.XML is created at the following location: %TEMP%\Symantec\OpsCenter\ This XML file can be used to upgrade OpsCenter View Builder software on multiple machines. Click Next to continue. check ‘I accept the terms of the license agreement’ and click Next. 9 On the command prompt. Example: D:\x86\ViewBuilder 4 Enter the following command: SETUP. Check Save Summary to field to save the installation summary. 8 A response file named ViewBuilder-<DD-MM-YY-HH-MIN-SS>.

you can modify the OpsCenter installation location.xml Note that the switches -Silent and -RespFile are case sensitive. For example. See “About tracking the progress of silent installation and troubleshooting tips” on page 134.<OpsCenter_Server> <InstallProperty Name="RAN_SETUP" Value="1" /> <InstallProperty Name="INSTALLDIR" Value="C:\Program Files\Symantec" /> <InstallProperty Name="BUSINESS_REP_LIC_KEYS"> <TagValue><License Key></TagValue> </InstallProperty> <Installproperty Name="SCMSTARTTYPE" Value="auto" /> <Installproperty Name="INSTALLPBX" Value="YES" /> <Installproperty Name="STARTSERVICE" Value="YES" /> <Installproperty Name="DATABASE_DATA_DIR" Value="C:\Program Files\Symantec\ </OpsCenter_Server> </XML_Install> For example.Installing Symantec OpsCenter 7. you can see Symantec OpsCenter View Builder in Add/Remove Programs. About editing the response file You can edit the response file to change any inputs that you provided to the Installation Wizard .<XML_Install> . To edit the response file. 11 The installation logs are generated at the following location: %ALLUSERSPROFILE%\Symantec\OPSCENTER\INSTALLLOGS See the following section to track the progress of the installation. After successful installation. license key information. or database directory in the response file. you can modify the OpsCenter installation location in this response file by changing the value of INSTALLDIR property from C:\Program .1 Installing Symantec OpsCenter on Windows and UNIX 133 10 Enter the following command to run silent installation: Setup -Silent -RespFile <path of the response file> Example: Setup -Silent -RespFile C:\ViewBuilder-07-12-10-06-11-31. The following are the contents of a sample response file: <?xml version="1. The silent installation is based on these inputs. open it and modify the Value field for the applicable install property.0" encoding="UTF-8" standalone="no" ?> .

Note: Symantec recommends that you do not change the value of RAN_SETUP.EXE process running in the Processes tab of the Windows Task Manager. You can also add a new license key by adding <TagValue>License key </TagValue> under <InstallProperty Name="BUSINESS_REP_LIC_KEYS" >.log file. About troubleshooting silent installation issues Use the following procedure to troubleshoot silent installation issues. To troubleshoot silent installation issues 1 After the silent installation ends. you will also find multiple msiexec. see 7. You can also track if a silent installation is in progress by checking the size of Vxinst. If OpsCenterInstallLog. Similarly you can edit the license key by changing the value of BUSINESS_REP_LIC_KEYS property. navigate to the following location: %ALLUSERSPROFILE%\SYMANTEC\OPSCENTER\INSTALLLOGS.1 Installing Symantec OpsCenter on Windows and UNIX Files\Symantec to D:\Symantec. This procedure must be performed after the silent installation ends. SCMSTARTTYPE. INSTALLPBX. 2 Check if a file named OpsCenterInstallLog. you can see SETUP.htm is not present. The size of Vxinst.exe processes running in the Task Manager.log file increases as silent installation progresses. Note that the text that you enter or modify in the response file is case sensitive. You must save the response file after you modify it. and STARTSERVICE properties. .log file is generated in %ALLUSERSPROFILE%\SYMANTEC\OPSCENTER\INSTALLLOGS. In addition. You can also modify the database directory by modifying the value of the DATABASE_DATA_DIR property.htm is present. About tracking the progress of silent installation and troubleshooting tips When a silent installation is in progress. The Vxinst.134 Installing Symantec OpsCenter 7.

xml" In this example. You must check the timestamp because OpsCenterInstallLog.1 Installing Symantec OpsCenter on Windows and UNIX 135 3 Open OpsCenterInstallLog.13:35:30: -Silent _RespFile "C:\Documents and Settings\Administrator\Agent-19-01-10-13-04-21. Agent.htm files that are present and do not find a valid OpsCenterInstallLog. the timestamp is 01-19-2010. search for the following keywords in the OpsCenterInstallLog.htm file: 01-19-2010. 5 To know the OpsCenter component the log file is associated with. This means that the log file is for OpsCenter Agent. You will find matches when you search for OpsCenter View Builder in the file.htm.htm and seeing the first line in the file. 4 You can check the timestamp by opening OpsCenterInstallLog. 13:35:30. the same OpsCenterInstallLog. .htm and check the timestamp and the OpsCenter component it is for to ensure that it is the appropriate log file. This means that the log file is for OpsCenter server.Installing Symantec OpsCenter 7. the following is the first line from a sample OpsCenterInstallLog. For example. or View Builder.htm file.htm may have been generated as a result of previous silent installations. see 7. In addition. This means that the log file is for OpsCenter View Builder.htm file is generated when you install OpsCenter server. Hence you must check the specific OpsCenter component that is associated with OpsCenterInstallLog. You will find matches when you search for OpsCenter Agent in the file. OpsCenter Agent OpsCenter View Builder Note: In case you have checked the timestamp and the OpsCenter component associated with all OpsCenterInstallLog.htm file: OpsCenter Server You will find matches when you search for OpsCenter Server in the file.

For example.13:35:30: -Silent _RespFile "C:\Documents and Settings\Administrator\Agent-19-01-10-13-04-21.htm file is present. Upgrading to OpsCenter on Windows and UNIX This section describes how you can upgrade from OpsCenter 7. Upgrading from OpsCenter 7.htm file to troubleshoot silent installation issues. .1 to OpsCenter 7.0 or 7.htm file and seeing the first line of the file. NOM.htm file to see if the installation was successful or to understand why the installation failed. Agent. You may also see a description about why the error occurred and troubleshoot accordingly.136 Installing Symantec OpsCenter 7. In OpsCenter<Product>InstallLog. Installation errors are flagged in this file in red color.1 on Windows and UNIX hosts. 9 Use the OpsCenter<Product>InstallLog. check if OpsCenter<Product>InstallLog. the timestamp is 01-19-2010. <Product> can be Server.1 Use the following procedure to upgrade OpsCenter 7.0 components to OpsCenter 7. or View Builder depending on the OpsCenter component that you are installing. You may also see a description about why the error occurred and troubleshoot accordingly. This file shows the installation status at the end. You can open the OpsCenter<Product>InstallLog. Open the OpsCenterInstallLog.htmfile. Always ensure that the OpsCenter<Product>InstallLog. the following is the first line from a sample OpsCenter<Product>InstallLog. 13:35:30. Installation errors are flagged in this file in red color.htm is not present or you cannot find a valid OpsCenterInstallLog.htm file is appropriate by checking the timestamp.0. 7 If OpsCenterInstallLog. Ignore the subsequent steps of this procedure.htm file to see if the installation was successful or to understand why the installation failed.1 on Windows and UNIX platforms. You can check the timestamp by opening the OpsCenter<Product>InstallLog. This file shows the installation status at the end.1.0. or VBR to OpsCenter 7.1 Upgrading to OpsCenter on Windows and UNIX 6 Use the OpsCenterInstallLog.0 or 7.xml" 8 In this example.htm file: 01-19-2010.htm file to troubleshoot silent installation issues.htm.

1 on Windows hosts.0 or 7.1 Upgrading to OpsCenter on Windows and UNIX 137 Note: If there are special characters in a report name like (/ \ * ? | ").1 is already installed. 3 4 On the Symantec DVD Browser. Review the following considerations before installing OpsCenter components on Windows: ■ Symantec recommends that you enable 8. . Upgrading from OpsCenter 7. In case you try to install OpsCenter 7. On the Run dialog box.1 to OpsCenter 7. Symantec recommends that you do not cancel or interrupt the installation process once it is started. click the Installation link. For example a media**summary report in OpsCenter 7. Click the OpsCenter Server Installation link to install Symantec OpsCenter Server. these special characters are replaced with an underscore '_' when you upgrade to OpsCenter 7.1 on Windows Use the following procedure to upgrade OpsCenter 7.1 components to OpsCenter 7.0.1. ■ ■ ■ To upgrade from OpsCenter Server 7. ■ ■ If autorun is enabled.3 file name creation is disabled. insert the appropriate OpsCenter product DVD in the DVD drive. Additionally after an installation is complete. you should wait for some time before installing other OpsCenter components. type ‘D:\Browser. If 8.1. click Start > Run.3 file name creation before installing OpsCenter components. You must not run any other installation while installing OpsCenter components.Installing Symantec OpsCenter 7.exe’ and press Enter: Where D is the DVD drive. the Symantec DVD Browser appears. in the Open text box.0.1 to OpsCenter Server 7.1 components on a system where OpsCenter 7. enable it and restart the WIndows host before installing or upgrading to OpsCenter components.1 component that is installed on your system.0 or 7.0 is renamed as media__summary report in OpsCenter 7. The Symantec DVD Browser appears.0. If autorun is not enabled.0 or 7.1 1 2 On a Windows host where you want to install OpsCenter Server. the installer runs in a Maintenance mode and lets you repair or remove the OpsCenter 7.

click Typical to use the default settings. Click Browse to specify a different location.0 (or 7. A green checkmark appears in the Required column if there is adequate disk space.138 Installing Symantec OpsCenter 7. installation location. Note: You cannot customize the default settings. Depending on the installed version. .1 Upgrading to OpsCenter on Windows and UNIX 5 The Welcome Page of the Installation Wizard appears. See “About Symantec OpsCenter Analytics license keys” on page 82. or port numbers. 6 7 Read the license agreement.1) on the system. In case the directory C:\Program Files\Symantec\OpsCenter_SavedData does not exist. enter your demo or permanent key that you have received with the purchase of OpsCenter 7. Click Next. or port numbers while upgrading from OpsCenter 7. 9 On the License Keys screen. locations. check ‘I accept the terms of the license agreement’ and click Next.1 and click Add Key.0 In order to upgrade to a newer version. The Installation Wizard detects an existing installation of OpsCenter Server 7. 8 Specify a location for saving the old OpsCenter database.1) to OpsCenter 7. Click Next to continue.0.1. the following message may be displayed on the Welcome screen: The Installation has detected that the following software is already installed on your system: Symantec OpsCenter Server: Version 7. Also compare the space that is required for installing OpsCenter Server and the actual space that is available. Note: Ensure that the database location has adequate space by going through the Disk space requirements section on this page. the existing Symantec OpsCenter Server will be removed.0 (or 7.0. The default location is C:\Program Files\Symantec\OpsCenter_SavedData. you are prompted to create it. Click Yes to create the directory. On the Installation Choice section.

1 Upgrading to OpsCenter on Windows and UNIX 139 10 The installer shows the summary of the installation settings.1 software and also migrates data from OpsCenter 7.Installing Symantec OpsCenter 7. click the Installation link.exe’ and press Enter: Where D is the DVD drive. the following message may be displayed on the Welcome screen: The Installation has detected that the following software is already installed on your system: Symantec OpsCenter Agent: Version 7. 3 4 5 On the Symantec DVD Browser.0. you can view the installation logs or view the Readme. in the Open text box.1) on the system. Click Next to continue. .1 1 2 On a Windows host where you want to install OpsCenter Agent. The installer installs OpsCenter Server 7.0 In order to upgrade to a to a newer version. The Symantec DVD Browser appears.0 (or 7.1 to OpsCenter Agent 7. type ‘D:\Browser.htm To upgrade from OpsCenter Agent 7. The installation logs are generated in the following location: %ALLUSERSPROFILE%\Symantec\OpsCenter\ INSTALLLOGS\OpsCenterServerInstallLog. Click Browse to save the installation summary in your preferred location. Click the OpsCenter Agent Installation link to install Symantec OpsCenter Agent 7. The Installation Wizard detects an existing installation of OpsCenter Agent 7. Click Install to begin the installation. click Start > Run.0 (or 7. On the Run dialog box.1. insert the OpsCenter product DVD in the DVD drive. 6 Read the license agreement. Click Finish.0 or 7. The Welcome Page of the Installation Wizard appears.1 database. the existing Symantec OpsCenter Agent will be removed. 11 After successful installation.1) to the OpsCenter 7. ■ ■ If autorun is enabled. the Symantec DVD Browser appears. check ‘I accept the terms of the license agreement’ and click Next. Check Save summary to option to save the installation summary. If autorun is not enabled.0. The database migration may take some time based on the size of your database. Depending on the installed version.0.

exe’ and press Enter: Where D is the DVD drive. the following message is displayed on the Welcome screen: The Installation has detected that the following software is already installed on your system: Symantec OpsCenter View Builder: Version 7. click the Installation link. Click Install to begin the installation. The Welcome Page of the Installation Wizard appears. ■ ■ If autorun is enabled. The Symantec DVD Browser appears. insert the OpsCenter product DVD in the DVD drive.0 (or 7. Depending on the installed version.0 In order to upgrade to a to a newer version. type ‘D:\Browser. click Start > Run.htm To upgrade from OpsCenter View Builder 7. If autorun is not enabled. check ‘I accept the terms of the license agreement’ and click Next. On the Run dialog box.1 Upgrading to OpsCenter on Windows and UNIX 7 The installer shows the summary of the installation settings. 3 4 5 On the Symantec DVD Browser. The installer installs OpsCenter Agent 7. Click the OpsCenter View Builder Installation link to install Symantec OpsCenter View Builder 7.0. Check Save summary to option to save the installation summary. Click Next to continue. Click Finish. Click Browse to save the installation summary in your preferred location.1. the existing Symantec OpsCenter View Builder will be removed.0 or 7.1) on the system. The installation logs are generated in the following location: %ALLUSERSPROFILE%\Symantec\OpsCenter\INSTALLLOGS\OpsCenterAgentInstallLog.1 software. The Installation Wizard detects an existing installation of OpsCenter View Builder 7. 8 After successful installation.1 to OpsCenter View Builder 7.1 1 2 On a Windows host where you want to install OpsCenter View Builder. 6 Read the license agreement.0. in the Open text box. . the Symantec DVD Browser appears.140 Installing Symantec OpsCenter 7. you can view the installation logs or view the Readme.

0 (or 7.1 to OpsCenter 7. Type the following command: .1 software. Click Browse to save the installation summary in your preferred location. Press Enter to continue. The installer then checks if OpsCenter Server is installed on the system or not.1 software on UNIX hosts.0.1 Upgrading to OpsCenter on Windows and UNIX 141 7 The installer shows the summary of the installation settings.0 or 7.1 on UNIX Use the following procedure to upgrade from OpsCenter 7. The installation logs are generated in the following location: %ALLUSERSPROFILE%\Symantec\OpsCenter\ INSTALLLOGS\OpsCenterViewBuilderInstallLog. The installer installs OpsCenter View Builder 7.0.Installing Symantec OpsCenter 7. Check Save summary to option to save the installation summary.htm Upgrading from OpsCenter 7. 8 After successful installation. Click Install to begin the installation.1) Server that you want to upgrade./install. Press Enter.0 or 7. Mount the OpsCenter product DVD on the OpsCenter 7. Click Finish. Note: Symantec recommends that you do not cancel or interrupt the installation process once it is started. It prompts you in case OpsCenter Server is already installed.1 to OpsCenter 7. you can view the installation logs or view the Readme.0 Server to OpsCenter 7.1 Server on UNIX 1 2 3 Open a UNIX console and log on as root on the target host. 4 5 The Welcome message is displayed. select Server from the displayed options (Server and Agent). If you are installing OpsCenter on Solaris Sparc. The installer also examines the system for existing packages. Press Enter to install OpsCenter Server. To upgrade from OpsCenter 7. .0.

1.0.0 was found on the system. but OpsCenter requires SYMCOpsCenterServer 7.0 was found on the system. the following message may be displayed: The following packages were found on the system.0. Depending on the installed packages. OpsCenter Server.1. .1 Server. AT. press Enter.0 The installer then uninstalls the older packages and installs OpsCenter 7. Are you sure you want to upgrade OPSCENTERSERVER? [y.0. but OpsCenter requires VRTSOpsCenterLegacyServer 7. Review this list and press Enter to continue.1 Upgrading to OpsCenter on Windows and UNIX 6 The following prompt is displayed: Where should the existing Symantec OpsCenter database and configuration files be backed up? An 'OpsCenterServer_backup' directory will be created within the directory that you specify to store these files. Configuration changes are made to the system.0 database and configuration files can be saved and then press Enter. (/var/symantec/) Type the directory name in which the existing OpsCenter 7.1. 7 The installer displays a list of components that will be installed or upgraded like PBX. The installer prompts you with the following question: installOpsCenterServer is now ready to upgrade OPSCENTERSERVER. SYMCOpsCenterServer 7. To accept the default directory path (/var/symantec). However the package versions are older than the ones required by OpsCenter.0 VRTSOpsCenterLegacyServer 7.n.q] (y) 8 Press Enter to continue and upgrade to OpsCenter 7.142 Installing Symantec OpsCenter 7.0 (or 7.1.0 SYMCOpsCenterGUI 7.1 Server is installed.1) packages that are installed. 10 OpsCenter 7. but OpsCenter requires SYMCOpsCenterGUI 7. OpsCenter GUI etc.0 was found on the system.0. 9 The installer displays the OpsCenter 7.

1 database. This may take some time based on the database size. Mount the OpsCenter product DVD on the OpsCenter Agent 7. You can view this file to check the database upgrade status. Press Enter to install OpsCenter Agent./db/log) after some time. Press Enter to continue.1 Agent on UNIX 1 2 3 Open a UNIX console and log on as root on the target host.Installing Symantec OpsCenter 7.0 (or 7.0 (or 7. The following information is also displayed: ■ ■ Web URL to access OpsCenter console Location of install log and summary files. data is migrated from the OpsCenter 7. You can view the installation log and summary files on the path mentioned.. To upgrade from OpsCenter 7.. Type the following command: . Symantec OpsCenter Agent etc. To know the upgrade status. Press Enter.1./install. You can check the status of database upgrade.1 Upgrading to OpsCenter on Windows and UNIX 143 11 The database upgrade process starts.1 Agent to OpsCenter 7. The following message is displayed: The database upgrade is in progress.1 packages.0.0.log file in the OpsCenter Server database logs directory (. 8 OpsCenter Agent 7. A file named dbManager_<timestamp>_. Press Enter to install or upgrade these packages to 7. 12 All the OpsCenter processes are started.1) computer that you want to upgrade to OpsCenter 7. In this process. see dbManager_<timestamp>_. The Welcome message is displayed.0.1 is installed.log is created after a few minutes in INSTALL_PATH/SYMCOpsCenterServer/db/log directory. It then uninstalls packages with older versions and installs 7. . The installer displays the packages that are installed like PBX.1) is installed. The database process may take time depending on your database size.0 (or 7.1) database to the OpsCenter 7.1.0 or 7. 4 5 6 7 Select Agent from the displayed options (Server and Agent).0. The installer displays that OpsCenter Agent 7. The installer checks if OpsCenter Agent is installed.

and Scheduled Jobs 1 2 On the OpsCenter console. These changes produce different values of jobs in NOM and OpsCenter so the values of throughput.1 The OpsCenter Installation Wizard automatically detects an older NOM installation.1 on Windows and UNIX The following upgrade paths are supported when you upgrade from NOM to OpsCenter 7.1. Error Logs. . The data migration process may take time depending on the volume of data that has to be migrated. job count calculation is based on the StartTime parameter where as in OpsCenter 7. Use the following procedure to resolve this issue.1: ■ ■ NOM 6. Breakup Jobs. The reason is that. Starting data collection when you configure OpsCenter Agent after upgrading from NOM to OpsCenter 7. SubJobs (or Breakup Jobs). This procedure must be repeated for all master servers. activity duration. click Settings > Configuration > NetBackup.1 Upgrading to OpsCenter on Windows and UNIX Upgrading from NetBackup Operations Manager to Symantec OpsCenter 7. and % utilization are different in both. It does not uninstall your existing NOM installation. the older NOM database is saved and started.5. Error Logs.1 and configure the OpsCenter Agent after upgrade. To start data collection for Images. About NOM upgrade considerations When you upgrade from NOM to OpsCenter 7.1 NOM 6. OpsCenter server is installed. the Disk Usage report displays a data mismatch in comparison to the report in OpsCenter. Note that a saved copy of the NOM database is used for upgrade. in NOM. SubJobs. During upgrade. data collection does not start for Images. You can access the data migration status page from the OpsCenter logon page. The data collection status for Image.1 When you upgrade from NOM to OpsCenter Server 7. The OpsCenter installer only stops the existing NOM services.144 Installing Symantec OpsCenter 7.4 -> OpsCenter 7. and Scheduled Jobs is shown as Not Started or Not Reported.1 the calculation is based on the EndTime parameter.5. Error Logs. You can manually uninstall NOM after successfully migrating data and using Symantec OpsCenter for some time. and Scheduled Jobs. Select the master server and click Edit. 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.6 -> OpsCenter 7.

Select the desired Agent from the Agent drop-down list.1 on Windows 1 2 On a Windows host where you want to install OpsCenter server. Click Save.1 Upgrading to OpsCenter on Windows and UNIX 145 3 4 5 6 In the Advanced Data Collection Properties section. deselect the Agent that is configured. select the master server again and click Edit.3 file name creation before installing OpsCenter components on Windows.1 on Windows Use the following procedure to upgrade to OpsCenter server on Windows. You must not run any other installation while installing OpsCenter components. the Symantec DVD Browser appears.1.Installing Symantec OpsCenter 7. . Click the OpsCenter Server Installation link to install Symantec OpsCenter Server 7. insert the appropriate OpsCenter DVD in the DVD drive. Click Save. ■ ■ To upgrade from NOM to Symantec OpsCenter 7. you should wait for some time before installing other OpsCenter components. in the Open text box. click the Installation link. The Symantec DVD Browser appears.exe’ and press Enter: Where D is the DVD drive. Upgrading from NetBackup Operations Manager to Symantec OpsCenter 7. click Start > Run. Symantec recommends that you do not cancel or interrupt the installation process once it is started. If autorun is not enabled. type ‘D:\Browser.3 file name creation is disabled. No Agent should be selected. enable it and restart the Windows host before installing or upgrading to OpsCenter components. 3 4 On the Symantec DVD Browser. If 8. Additionally after an installation is complete. ■ ■ If autorun is enabled. Review the following considerations before installing OpsCenter components on Windows: ■ Symantec recommends that you enable 8. On the Settings > Configuration > NetBackup page. On the Run dialog box.

Also compare the space that is required for installing OpsCenter Server and the actual space that is available. Note: Click Custom if you want to change the default settings. or port numbers. locations. . click Typical to use the default settings. you can manually uninstall NOM.4 Before you upgrade to OpsCenter 7. A green checkmark appears in the Required column if there is adequate disk space.5. 6 7 8 Click Next. After you successfully upgrade to OpsCenter 7. 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 NetBackup Operations Manager Release Update 4: Version 6. Read the license agreement. The default port number is 13799. Click Next.1 Upgrading to OpsCenter on Windows and UNIX 5 The Symantec OpsCenter Installation Wizard appears.1. installation location. Click Browse to specify a different location.1. The default location is C:\Program Files\Symantec\OpsCenter_SavedData. For example. Click Next. enter a port number on which the old NOM database can be started. Note: Ensure that the database location has adequate space by going through the Disk space requirements section on this page. 10 On the Upgrade Settings page. See “Reusing NOM after upgrading to OpsCenter on Windows” on page 147. you are prompted to create it. The Installation Wizard detects an existing installation of NetBackup Operations Manager on the system. all existing NOM services are stopped automatically. Information is available on how to configure and restart NOM. Click Yes to create the directory. On the Installation Choice section. check ‘I accept the terms of the license agreement’ and click Next. 9 Specify a location for saving the old NOM database.146 Installing Symantec OpsCenter 7. or port numbers. In case the directory C:\Program Files\Symantec\OpsCenter_SavedData does not exist.

See “About Symantec OpsCenter Analytics license keys” on page 82. In case you want to reuse NOM after upgrading to OpsCenter 7. 12 Click Next.Installing Symantec OpsCenter 7. you can view the OpsCenter console or view installation logs. 13 Click Install. The installer installs OpsCenter Server software. enter your demo or permanent key that you have received with the purchase of OpsCenter 7.1 and click Add Key. 14 After successful installation. See “Monitoring data migration from NOM to Symantec OpsCenter” on page 169. Data migration from the old NOM database to the OpsCenter database starts once the Symantec OpsCenter Server service is started while installing OpsCenter server. Check Save Summary to option to save the installation summary. The installer shows the summary of the settings that you have selected for installation. You can also access the data migration status from the OpsCenter console. the NOM processes are stopped.1 on Windows.1 Upgrading to OpsCenter on Windows and UNIX 147 11 On the License Keys screen. . 15 Click Finish. Reusing NOM after upgrading to OpsCenter on Windows After you upgrade from NOM to OpsCenter 7. Click Browse to save the installation summary in your preferred location.1. the following steps help you to restart NOM.

1 on UNIX. Press Enter. C:\Program Files\Veritas\Security\Authentication\bin>vssat deletepd --pdrtype ab --domain NOM_MACHINES@<system name> 3 Run the following command to delete the broker domain vx:domain name.1 on Windows 1 Run the following command to enable VxPBX. Type the following command: . you can start the NOM GUI. If you are installing OpsCenter on Solaris Sparc. . Restarting the services helps in restarting the NOM manager./installOpsCenterServer. Press Enter to continue.148 Installing Symantec OpsCenter 7. C:\Program Files\Veritas\Security\Authentication\bin>vssat deletebrokerdomain --domain vx:NOM_MACHINES@<system name> --broker <system name>:2821 Note: If the NOM services are still not up. Once the NOM manager is up.1. restart the pbx services and vxat services. Note: Symantec recommends that you do not cancel or interrupt the installation process once it is started. select Server from the displayed options (Server and Agent)./install. C:\Program Files\Veritas\Security\Authentication\bin>vssat setispbxexchflag -enable 2 Run the following command to delete the domain NOM_MACHINES from the system. 4 5 Type the following command:.1 on UNIX 1 2 3 Open a UNIX console and log on as root on the target host.1 Upgrading to OpsCenter on Windows and UNIX To restart NOM services after upgrading to OpsCenter 7. Upgrading from NetBackup Operations Manager to OpsCenter on UNIX Use the following procedure to upgrade from NOM to OpsCenter Server 7. The Welcome message is displayed. Mount the OpsCenter product DVD on the computer that you want to upgrade to OpsCenter 7. Press Enter. Press Enter to install OpsCenter Server. To upgrade from NOM to OpsCenter Server 7.

Note: In case you try to upgrade from an unsupported NOM version like 6. press Enter. Review this list and press Enter to continue.5.Installing Symantec OpsCenter 7. 10 Type y to confirm the directory path and press Enter. To accept the default path (/opt).5.q] (n) 7 The following message is displayed: The existing NOM database and configuration files must be backed up before upgrading to Symantec OpsCenter. It displays the following message when NOM is installed: NetBackup Operations Manager (NOM) <version> is installed on <hostname>. AT.n. . The installer prompts for the following information: Where do you want to install Symantec OpsCenter? (/opt) 9 Type a directory path where you want to install the Symantec OpsCenter Server packages and press Enter.n.1.1 Upgrading to OpsCenter on Windows and UNIX 149 6 The installer then checks for an existing NOM installation. press Enter without typing a directory path. Do you want to upgrade from NOM 6. type y and then press Enter. It is recommended that you upgrade to Symantec OpsCenter 7.q] y To upgrade to Symantec OpsCenter Server 7. OpsCenter GUI etc.3 to OpsCenter 7.4 or a higher version. 8 The installer displays a list of components that get installed like PBX.5.1. Do you want to upgrade from NOM <version> to Symantec OpsCenter [y.3 to Symantec OpsCenter 7. To accept the default directory path (/var/symantec). 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.1? [y.1 from NOM 6.3 is installed on <host>. OpsCenter Server.5. the installer displays the following message: NetBackup Operations Manager (NOM) 6. (/var/symantec) Type the directory name in which the NOM database and configuration files can be saved and then press Enter.

Do you want to create the directory? [y.150 Installing Symantec OpsCenter 7.q] y Type y to confirm and press Enter. To accept the default database installation directory (/var/Symantec). In case the database installation directory (/var/symantec) does not exist on the host. If you create an alternate database directory. the following information is displayed: Directory "/var/symantec" does not exist. . The following information is displayed: The OpsCenter database server may require up to 1 GB of temporary space at runtime. (/var/symantec/) Type a directory path under which to install the OpsCenter database and press Enter. By default.q] (n) Type a directory path for the database server temporary space and press Enter. /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.n. press Enter without typing a directory path. The location of database directory and the database temp directory is also displayed. the script creates the folder OpsCenterServer below your directory. press Enter without typing a directory path. 13 Review the installation options you selected. The installer prompts for the following information: Specify a location for the Symantec OpsCenter database. To use the database installation directory for database server temporary space. A directory named 'OpsCenterServer' will be created within the directory that you specify. temporary files will be created in the database installation directory.1 Upgrading to OpsCenter on Windows and UNIX 11 OpsCenter Server is installed on the system.

Installing Symantec OpsCenter 7. Type n and press Enter to repeat the configuration steps and revise your selection. type the license key and press Enter.1 Server” on page 152. You cannot access the licensed features by using the unlicensed version. If you do not enter any key and press Enter. you get an unlicensed version (Symantec OpsCenter). . summary. and response files. The following information is also displayed: ■ ■ ■ Web URL to access the OpsCenter console. Information is available on how to configure and restart NOM. Note: Ensure that the port number that you enter is free and not used by any application. Location of install log.1 Upgrading to OpsCenter on Windows and UNIX 151 14 Type y and press Enter to confirm the selection and continue. 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. 17 All the OpsCenter services are started. 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. See “Restarting NOM after upgrading to OpsCenter 7. The NOM processes are stopped after OpsCenter Server is installed. You are prompted with the following message: The old database will be started separately to migrate its data to the OpsCenter database. You can also access the data migration status from the OpsCenter console. Link on the OpsCenter logon page from where you can access the data migration status 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 Configuration changes are performed. press Enter only. To accept the default port number (13799).

com/business/support/index?page=content&id=TECH126226 . Do not uninstall VBR server after upgrading successfully to Symantec OpsCenter server software on a Windows platform.1 -> OpsCenter 7.1 on UNIX. Read the following TechAlert if you want to uninstall VBR on Windows: http://www.1: ■ ■ VBR 6. Restarting NOM after upgrading to OpsCenter 7.1 on Windows and UNIX The following upgrade paths are supported when you upgrade from VBR to OpsCenter 7. It does not uninstall your existing VBR installation. The OpsCenter installer only stops the existing VBR services./NOMAdmin -start_service Upgrading from Veritas Backup Reporter to OpsCenter Analytics 7. In case you still want to use NOM after upgrading to OpsCenter 7. use the following steps to start NOM on UNIX platforms.symantec.1 Server After you upgrade from NOM to OpsCenter 7. .d/init.2 -> OpsCenter 7.152 Installing Symantec OpsCenter 7. To restart NOM after upgrading to OpsCenter 7.1 on UNIX 1 Navigate to the following directory depending on the specific UNIX platform: Solaris Linux cd /etc/init.d cd /etc/rc.1 The OpsCenter Installation Wizard automatically detects an older VBR installation. the NOM processes are stopped.1.1 Upgrading to OpsCenter on Windows and UNIX See “Monitoring data migration from NOM to Symantec OpsCenter” on page 169.1 VBR 6.d/ 2 Run the following commands to restore the NOM server processes: mv vxnomd_NOM vxnomd mv vxnomweb_NOM vxnomweb 3 Navigate to the following directory: cd /opt/VRTSnom/bin/ 4 Run the following command to restart all NOM processes.6.6.

and so forth. To resolve this issue.1. This data is collected from the master server after the upgrade as part of the regular data collection. In case you have changed the default database passwords (dba. and Manage > Devices. If you uninstall VBR after upgrading from VBR to OpsCenter 7. only the names are provided from the job records. Note that a saved copy of the VBR database is used for upgrade. and Advanced Success Analysis reports display mismatched data when you apply the Full Window Parameter and Full for Duration of (In hours) filters. then after upgrade you must first configure the master servers to allow server access and data collection by OpsCenter. The data migration from the older VBR database to the new OpsCenter database starts after you successfully upgrade to OpsCenter. If a VBR server that collects NetBackup data through a remote VBR Agent is upgraded to OpsCenter 7.0.) The data is not displayed as VBR does not collect any monitoring data. data is not displayed under the Storage and Devices tabs in Monitoring. The default value for Full Window Parameter is 12 A. Robots. (Storage units. You can also view the data migration process from the OpsCenter logon page.1 Server: ■ After upgrading from VBR to OpsCenter 7.0. some reports display a data mismatch in comparison to the reports in OpsCenter. you must start the AT process manually by running /opt/VRTSat/bin/vxatd. or 7. Drives.1 Server.1 Upgrading to OpsCenter on Windows and UNIX 153 During upgrade. then you may not be able to log on to the OpsCenter console. ccsvc) or database port numbers for VBR.Installing Symantec OpsCenter 7. About VBR upgrade considerations Review the following considerations about upgrading from VBR to OpsCenter 7.1 to OpsCenter 7. ■ ■ ■ When you upgrade from VBR. The data migration process may take time depending on the data that has to be migrated.M. you must reset these to the default values before upgrading to OpsCenter 7. .1 Server. After a VBR upgrade. Success Rate Line. or 7. The reason for this mismatch is the filters applied to these reports. See “About upgrading from VBR to OpsCenter Server 7.1 if you use customized database passwords or port numbers in VBR” on page 154. The data migration process happens for each master server. Manage > Storage. See “Adding a master server in OpsCenter” on page 377.1 Server on Solaris. ■ The Consecutive Failures.1. guest. OpsCenter is installed and the older VBR database is saved and started. All Failed Backups. data is not displayed under Monitor > Devices. and for Full for Duration of (In hours).

0.0. when you apply the Schedule Type/Level filter with the value All.1. and Tape Count are affected as a result of additional the filters added in OpsCenter 7. Success Rate Line.1 displays a mismatch in comparison to the report in OpsCenter 7. VBR displays data for all the jobs that run for 24 hours. All Failed Backups. It does not consider the consecutive failures filter. The data displayed is incorrect as the report should display data only for Full and Incremental jobs. . as VBR does not list the clients when they are not backed up at least once or when client backup is not successful at least once.0 and 7. the forecast calculation in opscenter 7. The reports do not display the data for these parameters as implicit filters are added to the Media Type filter.0/7. For example. The media reports such as Tape Expiring Now. the report should display data for all the jobs that consecutively failed 3 times.0.1 was wrongly calculated. This issue is fixed for OpsCenter. For example.M. the report displays the data for the jobs that run between 12 A. guest password (guest). The report data however changes when you change the filter values. (15-hrs window ). The Client Risk Analysis report might display data mismatch. Though you specify the filter values. Optical Disk Worn. you may have changed the database admin password (dba). The reason for mismatch is that .1 if you use customized database passwords or port numbers in VBR In case you have changed the default database passwords or database port numbers for VBR. the report displays data for all jobs.1. TReport ignores data for Media types Backup to Disk. you must reset these to the default values before upgrading to OpsCenter Server 7. if you consider 12 A.1 Upgrading to OpsCenter on Windows and UNIX the value is 24 hrs. the report displays data for all types of jobs. In VBR. This issue is fixed for OpsCenter. and Advanced Success Analysis reports display mismatched data when you apply the Schedule Type/Level filter. ■ ■ ■ ■ About upgrading from VBR to OpsCenter Server 7. Optical Disk Readwriteable .154 Installing Symantec OpsCenter 7. When you use the default filters. This issue is fixed in OpsCenter. The Forecast report in OpsCenter 7. In OpsCenter the correct data is displayed but VBR displays incorrect data. ■ The Consecutive Failures. Blank Media . This issue is fixed for OpsCenter. for Full Window parameter and 15 hours for Full for Duration of (In hours) filters. Tape Expiring in the Future. However VBR report shows jobs that have failed only once.M.1. database passwords for members of the ccsvc_user account (ccsvc) or the database port number in VBR.M. For example. to 3 P. The Consecutive Failures report displays data mismatch as VBR miscalculates the data. if the filter value for consecutive failures is 3.

1 Upgrading to OpsCenter on Windows and UNIX 155 You must use the following procedure to reset all custom VBR database passwords and port numbers to default values. Review the following considerations before installing OpsCenter components on Windows: ■ Symantec recommends that you enable 8. If 8. The vbr_conf.3 file name creation is disabled. You must not run any other installation while installing OpsCenter components. Additionally after an installation is complete. .properties file is present at the following default location: Solaris: /opt/VRTSccsvs/conf Windows: \Program Files\Symantec\Veritas Backup Reporter\Server\conf Upgrading from Veritas Backup Reporter to OpsCenter Analytics on Windows Use the following procedure to upgrade from Veritas Backup Reporter Server. enable it and restart the WIndows host before installing or upgrading to OpsCenter components. Agent.Installing Symantec OpsCenter 7. To change VBR passwords and port numbers to default values 1 Reset all custom VBR database passwords and database port numbers to the default values. See the VBR documentation for more information.3 file name creation before installing OpsCenter components. 2 Clear the contents of vbr_conf. and View Builder respectively. and View Builder to Symantec OpsCenter Server. Symantec recommends that you do not cancel or interrupt the installation process once it is started.properties file. Agent. ■ ■ 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. you should wait for some time before installing other OpsCenter components.

On the Run dialog box. insert the appropriate OpsCenter DVD in the DVD drive. After you successfully upgrade to Symantec OpsCenter. in the Open text box. If autorun is not enabled. Read the license agreement. Read the following TechAlert if you want to uninstall VBR after upgrading to OpsCenter server: http://www.156 Installing Symantec OpsCenter 7.com/business/support/index?page=content&id=TECH126226 6 7 Click Next to continue.1 Before you upgrade to OpsCenter 7. 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 6. 3 4 5 On the Symantec DVD Browser. The Symantec OpsCenter Installation Wizard appears. click Start > Run. Note that you should not uninstall VBR server after upgrading successfully to Symantec OpsCenter server software.1 Upgrading to OpsCenter on Windows and UNIX To upgrade to OpsCenter Server on Windows 1 2 On a Windows host where you want to install OpsCenter server. the Symantec DVD Browser appears.1.6. you must manually uninstall VBR server software. ■ ■ If autorun is enabled. Click the OpsCenter Server Installation link to install Symantec OpsCenter Server. . For example. check ‘I accept the terms of the license agreement’ and click Next. type ‘D:\Browser.symantec. The Installation Wizard detects an existing installation of Veritas Backup Reporter on the system. click the Installation link. The Symantec DVD Browser appears. all existing VBR server services are stopped automatically.exe’ and press Enter: Where D is the DVD drive.

or port numbers. installation location. The license keys that are already installed on the system are also displayed in the box that is shown on this screen. or port numbers. 9 Specify a location for saving the old VBR database. If you do not enter a license key. Click Browse to specify a different location. The default location is C:\Program Files\Symantec\OpsCenter_SavedData. The license type is also shown along with the key. Click Next. The default port number is 13799. Note: Ensure that the database location has adequate space by going through the Disk space requirements section on this page. Note: Click Custom if you want to change the default settings. locations.1 Upgrading to OpsCenter on Windows and UNIX 157 8 On the Installation Choice section. your existing license keys are used. A green checkmark appears in the Required column if there is adequate disk space.Installing Symantec OpsCenter 7. Note: Ensure that the port number that you enter is free and not used by any other application. See “About Symantec OpsCenter Analytics license keys” on page 82. . 10 On the Upgrade Settings page. click Typical to use the default settings. you are prompted to create it. enter the demo or permanent key that you have received with the purchase of OpsCenter and click Add Key. Click Next to continue. enter a port number on which the old VBR database can be started. 11 On the License Keys screen. In case the directory C:\Program Files\Symantec\OpsCenter_SavedData does not exist.1 and the actual space that is available. Click Yes to create the directory. Click Next. Also compare the space that is required for upgrading to OpsCenter 7.

in the Open text box. . click Start > Run. type ‘D:\Browser.1 Upgrading to OpsCenter on Windows and UNIX 12 Click Next. You do not require an OpsCenter Agent to collect data from NetBackup 7. you must install OpsCenter Agent if you want to collect data from other backup products. ■ ■ If autorun is enabled. you can view the OpsCenter console or view installation logs. To upgrade to OpsCenter Agent on Windows 1 2 On a Windows host where you want to install OpsCenter Agent. See “Monitoring data migration from VBR to Symantec OpsCenter Analytics 7. If autorun is not enabled. The installer upgrades VBR server to OpsCenter Server 7. However. On the Run dialog box. 13 Click Install. You can also access the data migration status from the OpsCenter console.0 and later versions or PureDisk.exe’ and press Enter: Where D is the DVD drive.1. the port number that the VBR Agent uses is not required in OpsCenter. Click Browse to save the installation summary in your preferred location.1” on page 186.158 Installing Symantec OpsCenter 7. 14 After successful installation. By default. 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. Check Save Summary to field to save the installation summary. click the Installation link.1. Data migration from the old VBR database to the OpsCenter database starts once the Symantec OpsCenter Server service is started while installing OpsCenter Server 7. insert the appropriate OpsCenter DVD in the DVD drive. The Symantec DVD Browser appears. 15 Click Finish. Note: Once you upgrade your VBR Agent to the OpsCenter Agent. 3 On the Symantec DVD Browser. the VBR Agent uses port number 7806. The installer shows the summary of the settings that you have selected for installation. the Symantec DVD Browser appears.

1 from VBR 6. click Browse if you want to change the default location for Symantec OpsCenter Agent installation. After you successfully upgrade to Symantec OpsCenter Agent. 12 Click Finish. you must manually uninstall Veritas Backup Reporter Agent. A green checkmark appears in the Required column if there is adequate disk space. The Symantec OpsCenter Installation Wizard appears. 9 The installer shows a summary of the settings that you have selected for Symantec OpsCenter Agent installation. Check Save Summary to field to save the installation summary. Note: Ensure that the installation directory that you specify has adequate space by going through the Disk space requirements section on this page.1. 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> It is recommended that you upgrade to Symantec OpsCenter Agent 7. On the Installation Location screen. 6 7 8 Click Next to continue. check ‘I accept the terms of the license agreement’ and click Next. Read the license agreement.1 or a higher version Before you upgrade to Symantec OpsCenter Agent. Click Browse to save the installation summary in your preferred location. . 10 Click Install. Click Next. The installer starts installation of Symantec OpsCenter Agent 7. all Veritas Backup Reporter services are stopped automatically.Installing Symantec OpsCenter 7. The Installation Wizard detects an existing installation of Veritas Backup Reporter Agent on the system. 11 After successful installation. Based on your installed VBR Agent version.6.1 Upgrading to OpsCenter on Windows and UNIX 159 4 5 Click the OpsCenter Agent Installation link to install Symantec OpsCenter Agent. you can view the installation logs or open the readme file.

6 7 Read the license agreement. If autorun is not enabled. 3 4 5 On the Symantec DVD Browser. 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.6.1 Upgrading to OpsCenter on Windows and UNIX 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 7.1 from VBR 6. The Symantec OpsCenter Installation Wizard appears. check ‘I accept the terms of the license agreement’ and click Next. click Browse if you want to change the default location for Symantec OpsCenter View Builder installation. ■ ■ If autorun is enabled. On the Run dialog box. Note: Ensure that the installation directory that you specify has adequate space by going through the Disk space requirements section on this page. in the Open text box. A green checkmark appears in the Required column if there is adequate disk space. click the Installation link. The Symantec DVD Browser appears. On the Installation Location screen. insert the appropriate OpsCenter DVD in the DVD drive. the Symantec DVD Browser appears. click Start > Run.160 Installing Symantec OpsCenter 7. type ‘D:\Browser. Click the OpsCenter View Builder Installation link to install Symantec OpsCenter View Builder. .1 or a higher version Click Next to continue.exe’ and press Enter: Where D is the DVD drive.1 1 2 On the OpsCenter View Builder host. Veritas Backup Reporter: <version> It is recommended that you upgrade to Symantec OpsCenter View Builder 7.

Upgrading from Veritas Backup Reporter to OpsCenter 7. Type the following command: .1. Upgrading from Veritas Backup Reporter to OpsCenter Server 7. Press Enter to continue./install. Check Save Summary to field to save the installation summary.1 on UNIX 1 2 3 Open a UNIX console and log on as root on the target host. 4 The Welcome message is displayed. you can view the installation logs or open the readme file.1 on UNIX Use the following procedure to upgrade from Veritas Backup Reporter Server to Symantec OpsCenter Server on UNIX.Installing Symantec OpsCenter 7. 10 Click Install. Press Enter to install OpsCenter Server.1 Upgrading to OpsCenter on Windows and UNIX 161 8 9 Select a new location and click Next. select Server from the displayed options (Server and Agent).1 on UNIX Use the following procedure to upgrade from Veritas Backup Reporter Server and Agent to Symantec OpsCenter Server and Agent respectively. To upgrade from VBR Server to OpsCenter Server 7. 12 Click Finish. Mount the appropriate OpsCenter DVD on the computer that you want to upgrade to OpsCenter 7. . If you are installing OpsCenter on Solaris Sparc. Click Browse to save the installation summary in your preferred location. Note: Symantec recommends that you do not cancel or interrupt the installation process once it is started. 11 After successful installation.1. Press Enter. The installer shows a summary of the settings that you have selected for Symantec OpsCenter View Builder installation. The installer starts installation of Symantec OpsCenter View Builder 7.

OpsCenter Server. press Enter only. Note: In case you try to upgrade from an unsupported VBR version like 6. AT.1 or a higher version.6.6 is installed on <host>. (/var/symantec) Type the directory name in which you want to save the VBR database and configuration files and then press Enter.n.1 Upgrading to OpsCenter on Windows and UNIX 5 The installer then checks for an existing VBR installation.162 Installing Symantec OpsCenter 7.1. type y and then press Enter.n.6 to OpsCenter 7. Review this list and press Enter to continue.q] (n) 6 The following message is displayed: The existing VBR database and configuration files must be backed up before upgrading to Symantec OpsCenter. Where should the VBR database and configuration files be backed up? An OpsCenter_save directory will be created within the directory that you specify to store these files. Do you want to upgrade from VBR 6.1? [y. To save the VBR database and configuration files in the default directory path (/var/symantec). Do you want to upgrade from VBR <version> to Symantec OpsCenter [y. 7 The installer displays a list of components that get installed like PBX. To accept the default path (/opt). . The installer prompts for the following information: Where do you want to install Symantec OpsCenter? (/opt) 8 Type a directory path where you want to install the Symantec OpsCenter Server packages and press Enter. press Enter without typing a directory path.q] y To upgrade to Symantec OpsCenter. It is recommended that you upgrade to Symantec OpsCenter 7. the installer displays the following message: Veritas Backup Reporter (VBR) 6. OpsCenter GUI etc.1 from VBR 6.6 to Symantec OpsCenter 7. It displays the following message when VBR is installed: Veritas Backup Reporter (VBR) <version> is installed on <hostname>.

The script creates the folder OpsCenterServer below the directory that you specify./var/Symantec/OpsCenterServer . The following information is displayed: The OpsCenter database server may require up to 1 GB of temporary space at runtime. The installer prompts for the following information: Specify a location for the Symantec OpsCenter database. press Enter without typing a directory path.n. Do you want to create the directory? [y.Installing Symantec OpsCenter 7. To accept the default database installation directory (/var/Symantec).q] y Type y to confirm and press Enter. temporary files will be created in the database installation directory. the following information is displayed: Directory "/var/symantec" does not exist. it is automatically uninstalled and the required version is installed. In case the database installation directory (/var/symantec) does not exist on the host. 10 OpsCenter server is installed on the system. A directory named 'OpsCenterServer' will be created within the directory that you specify. If any older version of packages like VRTSpbx is detected.1 Upgrading to OpsCenter on Windows and UNIX 163 9 Review the installation directory path that you provided. By default. (/var/symantec/) Type a directory path under which to install the OpsCenter database and press Enter. Type y to confirm the installation directory path and press Enter.

13 You are prompted with the following message: An older license key has been detected.q] (n) Type y and press Enter to specify an alternate directory for the database server temporary space. Do you want to enter a new key?<Enter one key at a time if there are multiple keys: To use a new key. Review the installation options that you selected (database and database temp directory locations). press Enter only. . See “Restarting VBR after upgrading to OpsCenter 7. To accept the default port number (13799). 14 All the OpsCenter processes are started. press Enter without typing a directory path. type the license key and press Enter. To use the existing key.164 Installing Symantec OpsCenter 7. the OpsCenter Server processes must be restarted after the VBR uninstallation is complete. Note: Ensure that the port number that you enter is free and not used by any application. The VBR processes are stopped after OpsCenter Server is installed. Type y and then press Enter. press Enter only. Specify the directory location when prompted. If you uninstall Veritas Backup Reporter (VBR) from the OpsCenter host.1 Server” on page 165. Press <Return> to use the existing key. 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. Information is available on how to configure and restart VBR.n.1 Upgrading to OpsCenter on Windows and UNIX 11 You are prompted with the following message: Would you like to use an alternate directory for database server temporary space? [y. To use the database installation directory for database server temporary space. 12 Configuration changes are performed. You are prompted with the following message: The old database will be started separately to migrate its data to the OpsCenter database.

1 Server After you upgrade from VBR to OpsCenter 7. . Restarting VBR after upgrading to OpsCenter 7./vbrserver status Uninstalling VBR server from the OpsCenter host If you uninstall Veritas Backup Reporter (VBR) from the OpsCenter host. Link on the OpsCenter logon page from where you can access the data migration status Data migration from the old VBR database to the OpsCenter database starts once the Symantec OpsCenter Server service is started while installing OpsCenter Server 7./vbrserver start 5 Run the following command to check the status of VBR processes: .1. the OpsCenter Server processes must be restarted. and response files. summary.1 on Solaris 1 Navigate to the following directory: cd /etc/init.1 Upgrading to OpsCenter on Windows and UNIX 165 See “Uninstalling VBR server from the OpsCenter host” on page 165. To restart VBR after upgrading to OpsCenter 7.1” on page 186. In case you still want to use VBR after upgrading to OpsCenter 7.1.1 on Solaris.Installing Symantec OpsCenter 7.d/ 2 Run the following commands to restore the VBR server processes: mv vbrserver_VBR vbrserver mv vbrweb_VBR vbrweb 3 Navigate to the following directory: cd /opt/VRTSccsvs/bin/ 4 Run the following command to restart all VBR processes. perform the following procedure to start VBR. This must be done after the VBR uninstallation is complete. Location of install log. See “Monitoring data migration from VBR to Symantec OpsCenter Analytics 7. The following information is also displayed: ■ ■ ■ Web URL to access OpsCenter console. the VBR processes are stopped. . You can also access the data migration status from the OpsCenter console.

You do not require an OpsCenter Agent to collect data from NetBackup 7. Note: Once you upgrade your VBR Agent to the OpsCenter Agent./install.1 Upgrading to OpsCenter on Windows and UNIX To uninstall VBR server from OpsCenter 7.sh start Upgrading from Veritas Backup Reporter Agent to OpsCenter Agent 7. 4 5 Select Agent from the displayed options (Server and Agent). Press Enter to continue. . the port that the VBR Agent uses is not required in OpsCenter. See the product documentation for more information. To upgrade a VBR Agent to OpsCenter Agent on UNIX 1 2 3 Open a UNIX console and log on as root on the target host. Press Enter to install OpsCenter Agent.1 or PureDisk. However. Run the following command to restart all OpsCenter Server processes: /opt/SYMCOpsCenterServer/bin/opsadmin.1 on UNIX Use the following procedure to upgrade a VBR Agent to an OpsCenter Agent on UNIX. The default port that the VBR Agent uses is 7806. you must install OpsCenter Agent if you want to collect data from other backup products.1 host 1 2 Uninstall the VBR server software. Mount the appropriate OpsCenter DVD for the platform on which you are installing OpsCenter software. The Welcome message is displayed. Press Enter.166 Installing Symantec OpsCenter 7. Type the following command: .

n. The following prompt appears: Are you ready to configure OPSCENTERAGENT? [y.6 is installed on <host>.1 Upgrading to OpsCenter on Windows and UNIX 167 6 The following prompt is displayed: Veritas Backup Reporter (VBR) <version> is installed on <host>.6. Review this list and press Enter to continue.n.q] (y) To configure OpsCenterAgent now. Do you want to upgrade from VBR 6. Do you want to upgrade from VBR <version> to Symantec OpsCenter Agent ? [y. To accept the default path (/opt).6 to Symantec OpsCenter 7.n. type y and press Enter. the installer displays the following message: Veritas Backup Reporter (VBR) 6.1? [y.1 or a higher version.Installing Symantec OpsCenter 7. It is optional to configure OpsCenter Agent during installation.q] (n) 7 8 The installer displays a list of components that get installed like PBX. It is recommended that you upgrade to Symantec OpsCenter Agent from VBR 6. Note: The installOpsCenterAgent script is also present in the Solaris_Sparc64/Agent directory of the DVD. Symantec WebGUI Agent etc. type y and then press Enter. You may choose to configure OpsCenter Agent later either manually or by running /opt/VRTS/install/installOpsCenterAgent -configure command. The following prompt appears: Where should Symantec OpsCenter Agent packages be installed? (/opt) Type a directory path where you want to install the Symantec OpsCenter Agent packages and press Enter. . 9 Enter the location where you want to install OpsCenter Agent.1.6 to OpsCenter 7.q] (y) To upgrade to Symantec OpsCenter. press Enter without typing a directory path. Note: In case you try to upgrade from an unsupported VBR version like 6.

1 Server and access the OpsCenter console. the log file may display the following message: . Upgrade considerations When you upgrade from Veritas Backup Reporter to OpsCenter 7. This file is located in <INSTALL_PATH>\OpsCenter\server\logs directory on Windows and /<INSTALL_PATH>/SYMCOpsCenterServer/logs directory on Solaris. all previous data is also collected once data collection is enabled. summary. and response files on the path mentioned. Owner. Additional information may be displayed in the ServerService_<timestamp>. You can view the installation log files.log file. Parent. this data is collected from the master server and shown on the OpsCenter console.168 Installing Symantec OpsCenter 7. 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. previous data is not collected from the master server. 11 The OpsCenter Agent is installed. The data for all these columns is shown after data collection for the master server is enabled during data migration. For example. media. 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. Note: For most of the entities like policies.1 Upgrading to OpsCenter on Windows and UNIX 10 Type y and then press Enter to confirm your installation options. Data Movement etc. Once the data collection is enabled. However for jobs and image. Troubleshooting database inconsistency issues during upgrade The upgrade process may fail due to database inconsistency when you upgrade from VBR to OpsCenter server. devices etc..

It does not uninstall your existing NOM installation. 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. This file is located in <INSTALL_PATH>\OpsCenter\server\logs directory on Windows and /<INSTALL_PATH>/SYMCOpsCenterServer/logs directory on Solaris. The following sections describe the data migration process from NOM to Symantec OpsCenter in detail. To resolve this issue. The following table provides a list of NOM reports and whether they are migrated or not: .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 must manually undo the modifications that you have made to the database so that the database schema is similar to the released version.1 Upgrading to OpsCenter on Windows and UNIX 169 "Database schema is inconsistent with released schema <reason>" This message generally appears when you have modified the VBR database schema like added. modified. To resolve database inconsistency errors 1 Modify the database as per the message in the ServerService_<timestamp>. During upgrade.log file.1. or removed columns or constraints from the VBR database tables. the OpsCenter Installation Wizard automatically detects an older NOM installation. See “Upgrading from Veritas Backup Reporter to OpsCenter Analytics 7. Monitoring data migration from NOM to Symantec OpsCenter When you upgrade from NOM to OpsCenter server. the OpsCenter server is installed.1. When you upgrade from NOM to OpsCenter 7. all the SQL based reports are not migrated to OpsCenter 7.db and ccsvc. The data migration process may take time depending on the volume of data that has to be migrated. The OpsCenter installer only stops the existing NOM services.Installing Symantec OpsCenter 7. You can manually uninstall NOM after successfully migrating data and using Symantec OpsCenter for some time. Copy the modified ccsvc.1 on Windows and UNIX” on page 152.

170 Installing Symantec OpsCenter 7.1 Upgrading to OpsCenter on Windows and UNIX Table 2-10 NOM reports List of NOM reports and migration status Migrated when scheduled as standard report Yes Yes No Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes No No No No Yes No No Yes Yes Yes Migrated if its saved report (via copying) Yes No Yes Yes Yes No Yes Yes No No No No Yes No No No No No No No No Yes No Cold Catalog Backup Backup Duration Variance Job Summary Restore Job Details Job Exit Status Detail BMR Client Configuration Backup Failures Partially Successful Job Details Restore Job Summary Skipped Files Summary Throughput Variance File Count Variance Backup Job Size Variance Backup Window Failures Running Vs Queued Jobs Cycle Dashboard Cycle Dashboard by Job Type Cycle Dashboard by Media Server Job Details Job Summary by Status Jobs Scheduled to Run Media Expiration Schedule Available Media Report Media Summary by Media Server .

Installing Symantec OpsCenter 7.1 Upgrading to OpsCenter on Windows and UNIX 171 Table 2-10 NOM reports List of NOM reports and migration status (continued) Migrated when scheduled as standard report Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes No No No No Yes Yes Yes No Yes Yes Migrated if its saved report (via copying) Yes No Yes Yes Yes Yes No Yes No Yes Yes No Yes No No No No No No No No No Yes Full Media Capacity Drives in Use Media Utilization Media State Policy Change Top 10 Policies Using most Server Space Policy Summary Dashboard Job Success Rate by Policy Type Virtual Client Summary Client Restore Jobs by Application Client Summary Dashboard Job Success by Client Week at a glance Job Summary by Client Rolling 8 Day Summary Rolling 8 Day Summary by MediaServer Clients Not Backed up Current Disk Usage SAN Client Jobs License Capacity Media Server Job Throughput Master Server Job Throughput .

6 to the OpsCenter 7. domains. the database is upgraded directly to the OpsCenter 7.1 database occurs in three stages.1 Upgrading to OpsCenter on Windows and UNIX Table 2-10 NOM reports List of NOM reports and migration status (continued) Migrated when scheduled as standard report Yes No Yes No Yes Migrated if its saved report (via copying) No No No No No Disk Usage Drive Usage Storageunit Usage Window Utilization by Policy Vault Media Usage 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. For NOM 6. data that is specific to NOM is migrated to the OpsCenter database. server groups etc.5. Once this data has been migrated to OpsCenter.1 database. users.5. The NOM data comprises of alerts. Table 2-11 NOM data migration Data in OpsCenter Metadata about the managed master servers from NOM is migrated to OpsCenter. you can view this data from Settings > Configuration > NetBackup page in the OpsCenter console. In the first stage. NOM data that is migrated Master server metadata . Note: You must create new alert policies in OpsCenter only after alert migration is complete.4 or 6. alert policies. The data migration from NOM 6.6.4 and 6.172 Installing Symantec OpsCenter 7.5. Table 2-11 gives details about the NOM data that is migrated and how it appears in OpsCenter.5.

Even though recipient groups are migrated to the OpsCenter database. you can view this data from the Settings > Recipients page (both Email and SNMP subtabs) in the OpsCenter console. ■ A normal NOM user is the Administrator in OpsCenter. Email and trap recipients All recipients and recipient groups are migrated from NOM to OpsCenter. ■ NOM data that is migrated User information and domains The NOM admin user of NOM_BuiltIn@hostname domain must log on to OpsCenter using the OpsCenterUsers(vx) domain.Installing Symantec OpsCenter 7.1 Upgrading to OpsCenter on Windows and UNIX 173 Table 2-11 NOM data migration (continued) Data in OpsCenter The NOM users take the following user roles in OpsCenter: The admin user in NOM is the Security Administrator in Symantec OpsCenter. Once the recipients have been migrated to OpsCenter. Users of other NOM domains can continue using their respective domains in OpsCenter. Once this data has been migrated to OpsCenter. Note: Recipient groups are not supported in OpsCenter. the OpsCenter console does not display recipient groups. . ■ A read-only NOM user is the Operator in OpsCenter. you can view this data from the Settings > Users page in the OpsCenter console.

NOM data that is migrated Public and Private Groups . or clients are nodes in OpsCenter. or client node is mapped to the ALL MASTER SERVERS view. PrivateTree_Client. or client is an object in the View Pane. Public and Private groups are migrated as nodes.PrivateTree_Server. policy. three trees are created . For each NOM user. The OpsCenter console displays all views in the drop-down list of the View Pane.1 Upgrading to OpsCenter on Windows and UNIX Table 2-11 NOM data migration (continued) Data in OpsCenter The main (root) server. A single host. policy. A small group of master servers. and PrivateTree_Policy trees.174 Installing Symantec OpsCenter 7. policies.

1 Upgrading to OpsCenter on Windows and UNIX 175 Table 2-11 NOM data migration (continued) Data in OpsCenter NOM data that is migrated Saved Reports .Installing Symantec OpsCenter 7.

In NOM. If you edit these reports in OpsCenter. For example if you migrate a Skipped Files details for client report for a specific client like nom-ut6 from NOM. the user created public reports are not available for viewing. you must have a licensed version of OpsCenter (OpsCenter Analytics). then in OpsCenter the report is configured to run on all the clients (instead of only nom-ut6). All private graphical reports in NOM become tabular in OpsCenter. a user provides values for filters while running a report. User must provide values for all the filters like Client Name. Policy Name etc. you can directly edit SQL queries for these reports. The WHERE clause of the OpsCenter SQL query has "IS NOT NULL" value.176 Installing Symantec OpsCenter 7. Hence after migration is complete. you can view the private composite reports from Reports > My Dashboard in the OpsCenter console. Once these reports have been migrated.1 Table 2-10 User-created private and public composite reports in NOM are migrated as dashboard reports. For example a . NOM data that is migrated Note: To edit custom SQL reports in OpsCenter. these reports get default values for filters in OpsCenter. these special characters are replaced with an underscore '_' when you upgrade to OpsCenter 7. If there are special characters in a report name like (/ \ * ? | "). However. before you save a report in OpsCenter.1 Upgrading to OpsCenter on Windows and UNIX Table 2-11 NOM data migration (continued) Data in OpsCenter See the following table to know which NOM reports are migrated to OpsCenter 7.1. The concept of saving a report in NOM is different than OpsCenter. User-created reports in NOM (both Public and Private) are migrated as custom SQL queries.

1 Upgrading to OpsCenter on Windows and UNIX 177 Table 2-11 NOM data migration (continued) Data in OpsCenter media**summary report in NOM is renamed as media__summary report in OpsCenter 7. You must create new alert policies in OpsCenter only after alert migration is complete.Installing Symantec OpsCenter 7. the second stage of data migration begins. data is migrated per master server. After the NOM data has been migrated. You need to manually configure My Portal again using OpsCenter reports. Shortcuts to reports are not supported in OpsCenter. Note that in the second stage of data migration. the following data is migrated for each master server: ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Media server Client Storage Unit Volume group Volume Pool Robot Drives Services Catalog License Storage Service FSM DSM . In the second stage. Shortcuts to reports are not migrated. To see if alert policies have been migrated.1. NOM data that is migrated Alert Policies and alerts All alert policies and alerts are migrated from NOM to OpsCenter. see the Data Migration Status page.

data collection is not enabled automatically after migration. Note: If data collection for a master server was disabled in NOM. fresh data collection from the master server begins and you can start using the Monitor and Manage tabs of the OpsCenter console.1 Upgrading to OpsCenter on Windows and UNIX ■ ■ ■ ■ 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. In the third stage of data migration. the following data is migrated: Jobs older than 30 days Jobs data older than 30 days is migrated for each master server. then data collection for the specific master server remains disabled after you upgrade to OpsCenter. At this point. The status for the specific master server is shown as Last 30 Days Jobs Migrated on the Data Migration status page.178 Installing Symantec OpsCenter 7. . data collection for each master server is enabled automatically. In such a case.

Restore Job Summary etc. the report is first saved under Reports > My Reports and then the schedule is attached to it. like network issues. While creating schedule for a report in OpsCenter.1 database.1 Upgrading to OpsCenter on Windows and UNIX 179 Report Schedules The concept of report schedules is different in NOM and OpsCenter. You can work in the OpsCenter console while this data is migrated in the background. if a standard report like Available Media is scheduled in NOM. Schedules for composite reports are not migrated.5. the database is upgraded directly to the OpsCenter7. For NOM 6. 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. stopping services on the OpsCenter server etc. ■ In case a standard report is scheduled in NOM. are not migrated to OpsCenter. SORD value etc.Installing Symantec OpsCenter 7. However when you create a schedule in NOM.6. you provide the schedule details as well as filter values. Full Media Capacity. For example. you only need to specify the schedule details like time etc. What happens when data migration is interrupted Data migration can be interrupted due to many reasons. . then the standard report is saved in OpsCenter under Reports>MyReports view and the schedule is then attached to this report.4 and 6. Example.5. Note: Reports that come with NOM and are composite reports (containing more than one report). Note: All NOM user preferences like column settings.

if OpsCenter uses HTTP port 8181.6 database to the OpsCenter 7. DSM.6 to the OpsCenter 7. Viewing the data migration status You can also view the data migration status using the OpsCenter console.4 and 6. If port 80 is not available.4 or 6. You can also use the URL that is presented at the end of the OpsCenter server installation and append /dbUpgradeStatus.domain>/opscenter/dbUpgradeStatus.do. report schedules. User. enter the following: http://<host. Reports. then use http://<server-host>:8181/opscenter/dbUpgradeStatus.do <host. OpsCenter can use a different port. The data that had already been migrated does not need to be migrated again.domain> is the FQDN (Fully Qualified Domain Name) or IP address of the OpsCenter Server host.1 database is in progress. 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. data migration resumes from the last checkpoint automatically. Table 2-12 explains what happens when data migration is interrupted. run the configurePorts utility.5.bat -status on Windows hosts or /opt/SYMCOpsCenterWebGUI/bin/goodies/configurePorts. Groups.sh -status on UNIX hosts.5. License feature history. For example.1 Upgrading to OpsCenter on Windows and UNIX The data migration process can be interrupted when upgrade from NOM 6. To know the HTTP and HTTPS port that OpsCenter uses.Recipient.do after the URL to access the data migration page at any point in time.180 Installing Symantec OpsCenter 7.5.5. Run INSTALL_PATH\OpsCenter\gui\bin\goodies\configurePorts. Note: By default. .1 database. OpsCenter tries to run on port 80 (HTTP). Services. Note: The data migration for the following entities does not resume from the last checkpoint and needs to be migrated again . Table 2-12 Scenario Data migration is interrupted when data is migrated from NOM 6. and alert policy. Robot. What happens when data migration is interrupted Migration status In this case.

The link is located at the bottom of the logon page on the right-hand side. The data migration status is displayed as shown in the following figure: . This link is also located at the bottom of all OpsCenter console pages on the left-hand side.Installing Symantec OpsCenter 7. use the Click here to see migration status link as shown in the following figure.1 Upgrading to OpsCenter on Windows and UNIX 181 ■ On the OpsCenter logon page. This link automatically disappears when the data migration is complete.

like master server . The Entity Migration Status tab shows the following columns (along with the migration summary): Entity Displays the name of the database entity. Policy data (number of records) that are being migrated to OpsCenter.1 Upgrading to OpsCenter on Windows and UNIX The data migration status comprises Entity Migration Status and Master Server Entity Migration Status. The total number of records of an entity that need to be migrated from NOM to Symantec OpsCenter. Alert Policy. Total Records .182 Installing Symantec OpsCenter 7.

as of now Note: Migrated records are the number of rows in tables. recipient groups are not shown on the OpsCenter console as they are not supported by OpsCenter. However. For example. This is shown in the following figure: . the migrated records for policies include policies as well as policy versions that are associated with it. Such records are collected once the OpsCenter server starts. NOM standard reports like Cycle Dashboard and also schedules for such standard reports (if any) are shown as skipped records.1 Upgrading to OpsCenter on Windows and UNIX 183 Migrated Records Number of records of an entity that have been migrated to Symantec OpsCenter. Also the number of migrated recipients includes recipients as well as recipient groups. ■ 2 Click the Master Server Entity Migration Status tab to view the details of entities that are migrated per master server. This does not necessarily mean that these many records for the specific entity will be shown on the OpsCenter console. ■ NOM data that is not migrated is also shown as Skipped Records. 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. For example.Installing Symantec OpsCenter 7.

1 Upgrading to OpsCenter on Windows and UNIX This page shows the number of records that have been migrated for each master server. It also shows the time that is required for migrating those many records.184 Installing Symantec OpsCenter 7. . 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.

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. Note: If data collection for a master server was disabled in NOM. You can start using the Monitor and Manage views of the OpsCenter console at this point. Because data collection has been enabled. Total Records The total number of records for each master server that need to be migrated from NOM to Symantec OpsCenter. . media. the OpsCenter server starts collecting fresh data from the specific master server.1 Upgrading to OpsCenter on Windows and UNIX 185 Status The migration status for the respective master server. then data collection for the specific master server remains disabled after migration.Installing Symantec OpsCenter 7. 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. This status indicates that entities like policies. 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.

do not uninstall VBR server after upgrading to OpsCenter server software on a Windows platform. as of now Note: Migrated records are the number of rows in tables. recipient groups are not shown on the OpsCenter console as OpsCenter does not support recipient groups. the OpsCenter Installation Wizard automatically detects an older VBR installation. the migrated records for policies include policies as well as policy versions that are associated with it.com/business/support/index?page=content&id=TECH126226 . However. Such records are collected once the OpsCenter server starts. NOM standard reports like Cycle Dashboard and also schedules for such standard reports (if any) are shown as skipped records. It does not uninstall your existing VBR installation. The OpsCenter installer only stops the existing VBR services. For example. You can manually uninstall VBR after successfully migrating data and using Symantec OpsCenter for some time.1 When you upgrade from VBR to OpsCenter Analytics.1 Upgrading to OpsCenter on Windows and UNIX Migrated Records Number of records for each master server that have been migrated to Symantec OpsCenter. Read the following TechAlert if you want to uninstall VBR on Windows: http://www. 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. However. For example. ■ NOM data that is not migrated is also shown as Skipped Records. ■ Monitoring data migration from VBR to Symantec OpsCenter Analytics 7.186 Installing Symantec OpsCenter 7.symantec. This does not necessarily mean that these many records for the specific entity will be shown on the OpsCenter console. Also the number of migrated recipients includes recipients as well as recipient groups.

6.1 database. users. the database is upgraded directly to the OpsCenter 7. the OpsCenter server is installed and the older VBR database is saved and started. The data migration from the older VBR database to the new OpsCenter database starts once the Symantec OpsCenter Server Service is started while installing OpsCenter server. and data purge settings etc. PureDisk. EMC NetWorker) is migrated from VBR to OpsCenter for each master server. For entities like jobs. devices etc. The backup data consists of entities like policy. The following sections describe the data migration process from VBR to OpsCenter Analytics. The VBR metadata comprises of data related to alert policies. scheduled jobs. ■ ■ Table 2-13 gives details about the VBR metadata that is migrated in the first stage and how it appears in OpsCenter.Installing Symantec OpsCenter 7. .2 to the OpsCenter 7. Second stage in which Symantec Enterprise Vault archive data and report data is migrated. The data migration process may take time depending on the amount of data that has to be migrated. media.2.1 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.1 and 6. The data migration from VBR 6.6. SMTP server.6.1 or 6.1 Upgrading to OpsCenter on Windows and UNIX 187 During upgrade. and images. domains.1 database occurs in the following stages: ■ First stage in which VBR metadata and backup data is migrated from VBR to the OpsCenter database. views. TSM. data for the last 30 days is migrated in this stage.6. Third stage in which backup data older than 30 days (for NetBackup. media history. Backup Exec. About upgrading the VBR database to Symantec OpsCenter Analytics 7. For VBR 6.

and clients that have job data are migrated to OpsCenter. Exchange Server is migrated to OpsCenter. VBR data that is migrated Agent and Data Collectors Objects Data related to master servers. clients. and EV archive-related information like vault server . media servers. media servers. .188 Installing Symantec OpsCenter 7. The agents and data collectors for all products other than NetBackup can be viewed from Settings > Configuration > Agents in the OpsCenter console. the NetBackup agents and NetBackup data collectors can be viewed from Settings > Configuration > NetBackup in the OpsCenter console. Once this data has been migrated to OpsCenter.1 Upgrading to OpsCenter on Windows and UNIX Table 2-13 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. Note: Only those master servers. file systems.

the recipient groups are not displayed in the OpsCenter console. Once this data has been migrated to OpsCenter. Email and trap recipients All recipients and recipient groups are migrated from VBR to OpsCenter. Users of other domains can also continue using their respective domains. you can see these views in the View Pane of the OpsCenter console. Note: Only the VBR default user (admin@cc_users) must log on using OpsCenterUsers (vx) domain. All settings of the default admin user are now associated with the admin user of OpsCenterUsers(vx) domain.1 Upgrading to OpsCenter on Windows and UNIX 189 Table 2-13 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. you can view this data from the Settings > Recipients page (both Email and SNMP subtabs) in the OpsCenter console. Once this data has been migrated to OpsCenter. Note: Recipient groups are not supported in OpsCenter. . ■ A normal VBR user is the Reporter in OpsCenter. ■ A read-only VBR Administrator is the Analyst in OpsCenter.Installing Symantec OpsCenter 7. Views All views from VBR are migrated to OpsCenter as client-type views. you can view this data from the Settings > Users page in the OpsCenter console. Even though recipient groups are migrated to the OpsCenter database. ■ 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. Once this data has been migrated to OpsCenter.

. IBM TSM. The following data is migrated as a part of backup data for each master server: ■ ■ ■ ■ Policy Devices (tape libraries . data collection for each master server is enabled automatically. and Reports tabs of the OpsCenter console. In such a case. PureDisk. At this point. See “Viewing the data migration status” on page 195. After the VBR metadata is migrated.Manage. Backup Exec. The status for the specific master server is shown as Last 30 Days Jobs Migrated on the Data Migration status page. then data collection for the specific master server remains disabled after upgrading to OpsCenter Analytics. VBR data that is migrated Alert Policies Note: Alerts from VBR are not migrated to OpsCenter. see the Data Migration Status page. fresh data collection from the master server begins and you can start using the Monitor.) 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.1 Upgrading to OpsCenter on Windows and UNIX Table 2-13 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. data collection is not enabled automatically after migration. To see if alert policies have been migrated. backup data (for NetBackup. Note: If data collection for a master server was disabled in VBR. Disk pools etc. EMC NetWorker) is migrated per master server.190 Installing Symantec OpsCenter 7. Tape drives.

report data is migrated in the second stage.1 Upgrading to OpsCenter on Windows and UNIX 191 After the first stage of data migration is complete. the second stage of data migration begins.Installing Symantec OpsCenter 7. . 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. In the second stage of data migration. Table 2-14 gives details about the report data that is migrated and how it appears in OpsCenter. Symantec Enterprise Vault archive data is migrated followed by report data.

1 Upgrading to OpsCenter on Windows and UNIX Table 2-14 VBR report data migration in the second stage Data in OpsCenter Analytics VBR data that is migrated Reports .192 Installing Symantec OpsCenter 7.

these special characters are replaced with an underscore '_' when you upgrade to OpsCenter 7. Job Count Success Rate vs. Custom SQL and Stored Custom SQL reports are not migrated to Symantec OpsCenter. Custom chargeback reports that you have created in VBR are not migrated to OpsCenter.1 Upgrading to OpsCenter on Windows and UNIX 193 Table 2-14 VBR report data migration in the second stage (continued) Data in OpsCenter Analytics After migration is complete.Installing Symantec OpsCenter 7.Historical Job Duration .File Count Job Duration .Historical File Factor .Historical File Savings . The following VBR reports are not migrated to OpsCenter: ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ VBR data that is migrated Forecast .Ranking File Savings .Ranking Protected Files vs. Earlier in VBR. Amount Backed Up Success Rate vs. File Count File Factor . Client Count Success Rate vs.Distribution Master Server Count Active Job Count Skipped File Report Drive Throughput Success Rate vs.1. the My Backup Reports folder was under My Saved Reports folder. Backed Up Files NetBackup Storage Lifecycle Map Tape Count by Volume Pool (Bar Chart) Tape Count by Retention Level (Bar Chart) ■ Tape Used Capacity by Retention Level If there are special characters in a report name like (/ \ * ? | "). you can view the My Backup Reports folder under Private Reports tree. For example a media**summary report in VBR is renamed .

Report schedules All report schedules are migrated from VBR to OpsCenter. Once this data has been migrated. the third stage of data migration begins. the database is upgraded directly to the OpsCenter 7. you need to configure the following after data migration is complete: ■ SMTP server settings. For VBR 6. the backup data that remains to be migrated in the first stage (data older than 30 days) is migrated for each master server.1 database. The following data is migrated in the third stage for each master server: ■ ■ ■ ■ ■ Media History (Older than 30 days) Disk Pool history (Older than 30 days) Jobs (Older than 30 days) Scheduled jobs (Older than 30 days) Images (Older than 30 days) If you upgrade from VBR versions lower than 6. accidental shutdown of OpsCenter server.1 Upgrading to OpsCenter on Windows and UNIX Table 2-14 VBR report data migration in the second stage (continued) Data in OpsCenter Analytics as media__summary report in OpsCenter 7.6.1 and VBR 6. . In the third stage of data migration.194 Installing Symantec OpsCenter 7. Table 2-12 explains the scenario and what happens when data migration is interrupted. The VBR SMTP server settings are not migrated to OpsCenter.6 to OpsCenter Analytics. like network issues. What happens when data migration is interrupted Data migration can be interrupted due to many reasons.1.2. After the second stage of data migration is complete.6. the chargeback variables and formulae can be viewed from Settings > Chargeback view in the OpsCenter console. VBR data that is migrated Chargeback variables and formulas All VBR chargeback variables and formulae are migrated to OpsCenter. stopping services on the OpsCenter server etc.

■ On the OpsCenter logon page. Viewing the data migration status You can also view the data migration status using the OpsCenter console. For example. Run INSTALL_PATH\OpsCenter\gui\bin\goodies\configurePorts. reports.do after the URL to access the data migration page at any point in time. If port 80 is not available.1 and VBR 6.2 the last checkpoint automatically. You can also use the URL that is presented at the end of the OpsCenter server installation and append /dbUpgradeStatus. use the Click here to see migration status link as shown in the following figure.do <host. OpsCenter can use a different port. This link automatically disappears when the data migration is complete.bat -status on Windows hosts or /opt/SYMCOpsCenterWebGUI/bin/goodies/configurePorts. Note: The data migration for the following entities does not resume from the last checkpoint and is migrated again . then use http://<host. if OpsCenter uses HTTP port 8181. The data to the OpsCenter 7.list of clients and file systems.Installing Symantec OpsCenter 7.do to access the data migration page at any point in time. . run the configurePorts utility.domain>/opscenter/dbUpgradeStatus.6. The link is located at the bottom of the logon page on the right-hand side.domain>:8181/opscenter/dbUpgradeStatus. OpsCenter tries to run on port 80 (HTTP). This link is also located at the bottom of all OpsCenter console pages. To know the HTTP and HTTPS port that OpsCenter uses. enter the following: http://<host. Note: By default. data migration resumes from being migrated from VBR 6.domain> is the FQDN (Fully Qualified Domain Name) or IP address of the OpsCenter Server host.1 Upgrading to OpsCenter on Windows and UNIX 195 Table 2-15 Scenario What happens when data migration is interrupted Migration status Data migration is interrupted when data is In this case. 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.sh -status on UNIX hosts.6.1 database. that had already been migrated does not need to be migrated again.

1 Upgrading to OpsCenter on Windows and UNIX The data migration status is displayed as shown in the following figure: .196 Installing Symantec OpsCenter 7.

such as Alert Policy. Policy. The total number of records of an entity that need to be migrated from VBR to Symantec OpsCenter Analytics. Total Records . that is being migrated to OpsCenter Analytics. The Entity Migration Status tab shows the following columns (along with the migration summary): Entity Displays the name of the database entity. Jobs etc. Disk Pool.Installing Symantec OpsCenter 7.1 Upgrading to OpsCenter on Windows and UNIX 197 The data migration status contains Entity Migration Status and Master Server Entity Migration Status tabs.

However. For example. ■ VBR data that is not migrated is also shown as Skipped Records. VBR alerts are shown as skipped records. ■ 2 Click the Master Server Entity Migration Status tab to view the details of entities that are migrated for each master server.1 Upgrading to OpsCenter on Windows and UNIX Migrated Records Number of records of an entity that have been migrated to Symantec OpsCenter. Skipped Records Number of the records that were skipped during data migration because of the following possible reason: The data was in an inconsistent state during upgrade. Also the number of migrated recipients includes recipients as well as recipient groups. For example. 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. recipient groups are not shown on the OpsCenter console as they are not supported in OpsCenter. the migrated records for policies include policies as well as policy versions that are associated with it. This does not necessarily mean that these many records for the specific entity will be shown on the OpsCenter console. The following figure shows a sample view of the Master Server Entity Migration Status tab: .198 Installing Symantec OpsCenter 7.

such as master server . The Entity Migration Status tab shows the following columns (along with migration summary): Server Name Displays the name of the database entity. . Alert Policy. It also shows the time that is required for migrating those many records.Installing Symantec OpsCenter 7. Policy data (number of records) that has been migrated to OpsCenter.1 Upgrading to OpsCenter on Windows and UNIX 199 This page shows the number of records that have been migrated for each master server.

. This status indicates that entities like policies. Total Records The total number of records for each master server that need to be migrated to Symantec OpsCenter Analytics from VBR. media. the OpsCenter server starts collecting fresh data from the specific master server. 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. The following migration status are possible for a master server: Not Started: The data migration process for the master server has not started. Last 30 Days Jobs Migrated: This means that the first stage of data migration is complete for the specific master server. Note: If data collection for a master server was disabled in VBR. You can start using the Monitor and Manage views of the OpsCenter Analytics console at this point.1 Upgrading to OpsCenter on Windows and UNIX Status The migration status for the respective master server. then data collection for the specific master server remains disabled after migration. Completed: Entities for this master server have been migrated from VBR to OpsCenter Analytics Failed: Entities for this master server cannot be migrated from VBR to OpsCenter Analytics. In Progress: Entities for this master server are being migrated from VBR to OpsCenter Analytics.200 Installing Symantec OpsCenter 7. Because data collection has been enabled.

1 Server software on a different Windows system. as of now Note: Migrated records are the number of rows in tables. An example scenario is when NOM or VBR is running on Windows 2000 and you require the same data with OpsCenter 7.3 file name creation before installing OpsCenter components. For example. For example. VBR alerts are shown as skipped records.Installing Symantec OpsCenter 7. ■ Upgrading to OpsCenter Server on a different Windows system This section explains how you can upgrade from NOM or VBR to OpsCenter 7.1 on Windows 2003. the migrated records for policies include policies as well as policy versions associated with it. enable it and restart the WIndows host before installing or upgrading to OpsCenter components. 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. If 8. recipient groups are not shown on the OpsCenter console as OpsCenter does not support recipient groups. However. Such records are collected once the OpsCenter server starts (if they are present in the NetBackup host). This does not necessarily mean that these many records for the specific entity will be shown on the OpsCenter console. .1 Upgrading to OpsCenter on Windows and UNIX 201 Migrated Records Number of records for each master server that have been migrated to Symantec OpsCenter. 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.3 file name creation is disabled. Note: Symantec recommends that you enable 8.

■ Manual upgrade to OpsCenter 7. ■ .4 NOM 6.exe for the appropriate architecture on your old NOM or VBR server. See “Upgrading to OpsCenter Server on the new system” on page 208. However. See “Backing up your data on the NOM or VBR server” on page 207.1 VBR 6. Copy this data from the old server to the server where you plan to install OpsCenter Server. For example. The procedure basically involves the following steps: ■ Back up your NOM or VBR database and configuration files using DataBackupUtility.1 Server is supported from the following NOM versions: ■ ■ NOM 6.202 Installing Symantec OpsCenter 7.5. you can upgrade from Windows 2000 to Windows 2008 but you cannot upgrade from a Windows platform to Solaris 10.1 Upgrading to OpsCenter on Windows and UNIX Note the following points before you upgrade from NOM or VBR to OpsCenter 7.1 on Windows 2008 R2 (64-bit). manual upgrade from a 64-bit system to a 32-bit system is not supported.5.1 Server software on a different Windows system: ■ Manual upgrades are supported only within the Windows family. Install the OpsCenter Server software and restore the NOM or VBR data using the OpsCenter installer. you can upgrade from NOM running on Windows 2000 (32-bit) to OpsCenter 7.6.6. Manual upgrade is supported between the following systems: ■ ■ ■ ■ 32-bit to 64-bit systems 32-bit to 32-bit systems 64-bit to 64-bit systems For example.1 Server is supported from the following VBR versions: ■ ■ VBR 6.2 Use the following procedure to upgrade to OpsCenter Server software on a different Windows system.6 ■ Manual upgrade to OpsCenter 7.

Installing Symantec OpsCenter 7. After entering the backup location. type a backup location or browse for the appropriate location. VBR_Backup folder is created. The utility detects that you have NOM or VBR installed and prompts you for the backup location: To back up NOM or VBR database in a specific location. 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. Go to the appropriate OpsCenter platform directory (like x64 or x86) and then the Server directory. if you are backing up the VBR database. To back up the NOM or VBR database 1 2 3 4 5 Log on to the NOM or VBR server as Administrator. the utility creates a folder called <product>_Backup in the location that you specified. Run DataBackupUtility.EXE.1 Upgrading to OpsCenter on Windows and UNIX 203 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. Once the backup is complete. 6 After backing up the NOM or VBR database. This utility backs up the NOM or VBR database and configuration files on this system. Note: Symantec recommends that you do not cancel or interrupt the installation process once it is started. Click Start Backup. For example. the installer displays the following message: Backup completed successfully for <product> Click OK. Insert the appropriate OpsCenter product DVD in the DVD drive. review the available and required space that is displayed in the dialog box. .

in the Open text box. The Symantec OpsCenter Installation Wizard appears.204 Installing Symantec OpsCenter 7. The Symantec DVD Browser appears. ■ ■ If autorun is enabled. in a clustered mode. check ‘I accept the terms of the license agreement’ and click Next. See “Clustering Symantec OpsCenter on Windows” on page 237. Click the OpsCenter Server Installation link to install Symantec OpsCenter Server 7. click the Installation link. Select Install to this computer only. type ‘D:\Browser. 8 9 Read the license agreement.exe’ and press Enter: Where D is the DVD drive. See “Clustering Symantec OpsCenter Server on Solaris” on page 248. Insert the appropriate OpsCenter DVD in the DVD drive. the Symantec DVD Browser appears. If autorun is not enabled.1. 5 6 7 On the Symantec DVD Browser. This option is enabled if you have Veritas Cluster Server (VCS) installed. click Start > Run. Install a clustered OpsCenter Select this option to install OpsCenter Server on all Server selected nodes. The following options are displayed: Install to this computer only Select this option to install OpsCenter Server on this host. Click Next. Copy the backed up NOM or VBR data (<product>_Backup folder) from the older NOM or VBR server to this system. On the Run dialog box.1 Upgrading to OpsCenter on Windows and UNIX To upgrade to OpsCenter Server on the new system 1 2 3 4 Log on to the system where you want to install OpsCenter 7.1 Server as Administrator. . You need to install OpsCenter Server manually on each node of the cluster.

13 On the Customize Location screen. Check Upgrade using a backed up VBR or NOM database on a different system. 11 On the Manual Database Upgrade screen. The installer installs OpsCenter Server software. Enter the path where the OpsCenter database can be installed. Click Next. Click Next. enter the following information: Program destination folder Enter the path where OpsCenter Server can be installed.1 and click Add Key. 14 On the License Keys screen. The installer shows the summary of the settings that you have selected for installation. Click Next. enter a port number on which the old NOM or VBR database can be started. Database destination folder Review the information in the Disk space requirements table at the bottom of the screen. You can also click Browse to specify a location.Installing Symantec OpsCenter 7. Check Save Summary to option to save the installation summary. click Custom. 15 Click Next. enter your demo or permanent key that you have received with the purchase of OpsCenter 7. Click Browse to save the installation summary in your preferred location. The default port number is 13799. 16 Click Install. Click Next. . See “About Symantec OpsCenter Analytics license keys” on page 82. specify a location where you have saved the old NOM or VBR database.1 Upgrading to OpsCenter on Windows and UNIX 205 10 On the Installation Choice section. 12 On the Upgrade Settings screen.

10. For example.0. you can upgrade from Solaris 8 to Solaris 10 but you cannot upgrade from RHEL 4. Manual upgrade from NOM to OpsCenter server is supported from specific NOM platforms. 64-bit Solaris x86 10.0. 64-bit Solaris SPARC 9.0.1 Server software on a different UNIX system: ■ Manual upgrades are supported only within the UNIX family. Note the following points before you upgrade from NOM or VBR to OpsCenter 7. Manual upgrades are supported only within a particular OS family. ■ Manual upgrade from VBR to OpsCenter Server is supported on Solaris platforms. 64-bit For example. you can upgrade from NOM running on Solaris SPARC 9 (64-bit) to OpsCenter server running on Solaris SPARC 10 (64-bit). you can upgrade from Solaris 8 to Solaris 10 but you cannot upgrade from a Windows platform to Solaris 10.0. Data migration from the old NOM database to the OpsCenter database starts once the Symantec OpsCenter Server service is started while installing OpsCenter Server. See “Monitoring data migration from NOM to Symantec OpsCenter” on page 169. You can also access the data migration status from the OpsCenter console. For example. 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. you can view the OpsCenter console or view installation logs.1 Upgrading to OpsCenter on Windows and UNIX 17 After successful installation.206 Installing Symantec OpsCenter 7.0 to Solaris 10. Ensure that NOM is running on the following platforms: ■ ■ ■ ■ ■ Linux RHEL 4. .0. 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: Symantec recommends that you do not cancel or interrupt the installation process once it is started. For example. 18 Click Finish. 5. you can upgrade from VBR running on Solaris 8 to OpsCenter server running on Solaris 10.

Install the OpsCenter server software and restore the NOM or VBR data using the OpsCenter installer. ■ 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. . The procedure basically involves the following steps: ■ Back up your NOM or VBR database and configuration files using Backup.1 Upgrading to OpsCenter on Windows and UNIX 207 Use the following procedure to upgrade to OpsCenter server software on a different UNIX system. See “Backing up your data on the NOM or VBR server” on page 207. Copy this data from the old server to the server where you plan to install OpsCenter server. Mount the OpsCenter product DVD on the computer where you are installing OpsCenter software.Installing Symantec OpsCenter 7. Go to the appropriate OpsCenter platform directory and then the Server directory. To back up the NOM or VBR database 1 2 3 Go to the NOM or VBR server and log on as root.sh utility on your old NOM or VBR server. See “Upgrading to OpsCenter Server on the new system” on page 208.

Press Enter to install OpsCenter Server. A directory that is named OpsCenter_save is created in the backup location that you specify. 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.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. 5 6 The Welcome message is displayed. It prompts you in case OpsCenter is already installed. 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. Press Enter to continue.1 Upgrading to OpsCenter on Windows and UNIX 4 Run Backup. To upgrade to OpsCenter Server on the new system 1 2 3 4 Log on as root on the server where you want to install OpsCenter. Mount the OpsCenter product DVD where you want are installing OpsCenter Server.208 Installing Symantec OpsCenter 7. select Server from the displayed options (Server and Agent)./Backup. This script backs up the NOM or VBR database and configuration files on this system./install. Copy the backed up NOM or VBR data (OpsCenter_save folder) from the older NOM or VBR server to this server. If you are installing OpsCenter on Solaris Sparc. The installer also examines the system for existing packages. Press Enter. Type the following command: . type a backup location and press Enter. The installer then checks if OpsCenter Server is installed on the system or not. . Please specify the backup location. To back up the <product> data in the default directory (/var/symantec). press Enter.

To accept the default database installation directory (/var/Symantec).Installing Symantec OpsCenter 7. press Enter without typing a directory path. AT.q] y Type y to confirm and press Enter. In case the database installation directory (/var/symantec) does not exist on the host. By default. (/var/symantec/) Type a directory path under which to install the OpsCenter database and press Enter. 10 OpsCenter Server is installed on the system. A directory named 'OpsCenterServer' will be created within the directory that you specify. Symantec WebGUI Server. temporary files will be created in the database installation directory /var/Symantec/OpsCenterServer . Symantec Database etc. If you create an alternate database directory. 9 Type y to confirm the directory path and press Enter. the following information is displayed: Directory "/var/symantec" does not exist. The following information is displayed: The OpsCenter database server may require up to 1 GB of temporary space at runtime. To accept the default path (/opt). the script creates the folder OpsCenterServer below your directory. Do you want to create the directory? [y. The installer prompts you with the following question: Where do you want to install Symantec OpsCenter? </opt> 8 Type a directory path where you want to install the Symantec OpsCenter Server packages and press Enter. The installer prompts for the following information: Specify a location for the Symantec OpsCenter database. press Enter without typing a directory path.1 Upgrading to OpsCenter on Windows and UNIX 209 7 The installer displays a list of components that get installed like PBX.n. Review this list and press Enter to continue.

Type n and press Enter to repeat the configuration steps and revise your selection. Type a directory path for the database server temporary space and press Enter.210 Installing Symantec OpsCenter 7. <var/symantec> Specify the location where you have copied the backed up data and press Enter. 15 You are prompted for the location of the backed up directory: Please specify the directory that contains the backed up data. The location of database directory and the database temp directory is also displayed.n. . press Enter without typing a directory path. 14 Once the configuration changes are completed.1 Upgrading to OpsCenter on Windows and UNIX 11 You are prompted with the following message: Would you like to use an alternate directory for database server temporary space? [y. type y and press Enter.q] <n> Type y and then press Enter. To specify an alternate directory.q] (n) To use the database installation directory for database server temporary space. 13 Type y and press Enter to confirm the selection and continue.n. you are prompted with the following question: Do you want to restore data that has been backed up manually [y. 12 Review the installation options you selected.

. You can also add the license keys later from the OpsCenter console. Depending on whether older license keys are detected or not.1 Post-installation tasks 211 16 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. With the unlicensed version. perform a check to verify that OpsCenter is running properly. 17 You are prompted for license information. Verifying that Symantec OpsCenter is running properly After installing Symantec OpsCenter on either Windows or UNIX. Specify a port number on which the old database can be started <13799> To start the old database on port 13799. See “About Symantec OpsCenter Analytics license keys” on page 82. you cannot access the licensed features. If you do not enter a key. Post-installation tasks The following sections explain how to start using OpsCenter and includes some performance tuning tips for OpsCenter. you get an unlicensed version. See “About managing licenses” on page 307. press Enter. 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.Installing Symantec OpsCenter 7.

Table 2-16 lists the common tasks in OpsCenter and contains links to the corresponding topics and descriptions. The first time you log in.1 Post-installation tasks 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. it takes longer than usual time for the GUI to load. For administrator initial logon. Alternately type the following in the Web browser address bar: http://<server-host>/opscenter Note: By default. it is recommended that you change the user name and password. For example.sh -status on UNIX hosts. To know the HTTP and HTTPS port that OpsCenter uses. then use http://<host. Table 2-16 Task Topic Links to get you started with OpsCenter Topic Description This topic provides instructions on how to access the console and log on. After initial logon. and the authentication service are running. you are ready to start using the OpsCenter console.domain>:8181/opscenter. To access and log on to the See “About accessing the OpsCenter console. the user name is admin and the password is password if you have chosen to keep the default password during installation. .bat -status on Windows hosts or /opt/SYMCOpsCenterWebGUI/bin/goodies/configurePorts. Run INSTALL_PATH\OpsCenter\gui\bin\goodies\configurePorts. if OpsCenter uses HTTP port 8181. If port 80 is not available. the Web server.212 Installing Symantec OpsCenter 7. If the OpsCenter logon screen appears. OpsCenter console” on page 41. OpsCenter can use a different port. See “Changing your OpsCenter password” on page 307. To change the password for the administrator logon. 2 Log on as admin (user name) /password (password) on the private domain: OpsCenterUsers(vx) About starting to use OpsCenter After you complete the OpsCenter installation. OpsCenter tries to run on port 80 (HTTP). the OpsCenter Server. run the configurePorts utility. and provides solutions to possible issues.

use the OpsCenter online Help . then you should not add all of them at once. reporting. For example. and settings views and related tasks. wait until the initial data collection for these master servers is complete. Note: The information that is published in this section is based on the tests that have been performed in Symantec Lab in a controlled environment with expert users. When OpsCenter starts.Installing Symantec OpsCenter 7. and NOM_MACHINES are created when OpsCenter server is installed. Once you add the first five master servers. ■ Tuning OpsCenter for more performance The following settings can be tuned to improve OpsCenter performance. These can be used as guidelines and should not be used as 100% accurate benchmarks. The following domains namely OpsCenterUsers. various OpsCenter monitoring. About the start-up tasks that OpsCenter performs OpsCenter performs the following tasks when it starts for the first time. OpsCenter uses them.1 Post-installation tasks 213 Table 2-16 Task To learn about the OpsCenter console components. console” on page 39. Symantec recommends that you add five master servers at one time. About adding master servers to OpsCenter If you need to add multiple master servers to the OpsCenter console. if you have 20 master servers to be added. go to Settings > Configuration > NetBackup in the OpsCenter console and then click the Data Collection Status tab on the page. Topic See “About OpsCenter console components” on page 58.5+5+5+5. managing. OpsCenterServices. The data . Links to get you started with OpsCenter (continued) Topic Description This topic provides an overview of the console components. it performs the following tasks: ■ Creates and initializes the security domain that the authentication broker requires. If these security domains are present. To learn more about using See “About using the OpsCenter For instructions on understanding and using the the OpsCenter console. Creates the OpsCenter admin user in the OpsCenterUsers domain with the default password as 'password'. Symantec recommends that you add them in groups of five in the following manner . To view the data collection status for a master server.

Performance testing indicates that OpsCenter runs fastest on a Windows 64-bit platform as compared to other Windows or UNIX platforms.1 master server running Windows 2003 on a Xeon-64 processor that has 2 GB RAM and 1. This section describes important tuning parameters and settings that can result in improved performance.381 Kbps 2500 More than 10. . See “Moving the OpsCenter database to a different hard disk” on page 215. See “About OpsCenter platform compatibility” on page 86.25 times faster than Microsoft Internet Explorer. Average Bandwidth used by OpsCenter Number of jobs per day 4. About installing OpsCenter on a Windows 64-bit platform Symantec recommends that you install the OpsCenter server software on a supported Windows 64-bit platform for optimum performance. Performance testing indicates that Mozilla Firefox works 1.67 Kbps 10.0 GbE LAN connection. The following guidelines can help improve OpsCenter performance: ■ Install the OpsCenter database on a drive that is different from where OpsCenter server software and operating system is installed.1 Post-installation tasks collection status for a master server can be viewed from the Collection Status column.214 Installing Symantec OpsCenter 7. About performance tuning guidelines You may want to tune OpsCenter to obtain incremental performance gains. About using a Web browser to access OpsCenter Symantec recommends that you use Mozilla Firefox to access the OpsCenter console. About bandwidth utilization The following table lists the average bandwidth that is consumed when OpsCenter collects data from a master server.000 Note: The system that was used for testing was a NetBackup 7.

bat stop 2 Open the databases.1 Post-installation tasks 215 ■ Install the OpsCenter log files on a drive that is different from where OpsCenter server software and operating system is installed. To move the OpsCenter database to a different hard disk on Windows 1 Stop all OpsCenter server services. . See “About OpsCenter database defragmentation” on page 270. Purge the OpsCenter data periodically. Open the command line and enter the following command: INSTALL_PATH\OpsCenter\server\bin\opsadmin. Symantec recommends that you defragment the OpsCenter database periodically. Create report schedules such that the email or export happens in system idle time when OpsCenter is not accessed frequently. See “Saving the OpsCenter log files on a different drive” on page 217.db" This path specifies the default location of the OpsCenter database. ■ ■ ■ ■ ■ Moving the OpsCenter database to a different hard disk Use the following procedure to move the OpsCenter database to a different hard disk. See “Adjusting the heap size for OpsCenter components” on page 221. This should be done only if the logging level is greater than 1. You must perform defragmentation once in a month.Installing Symantec OpsCenter 7. See “About purging data periodically” on page 227.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. See “Adjusting the OpsCenter database cache size” on page 226. Increase the heap size of the OpsCenter Server in accordance with the RAM. Increase the database cache size in accordance with the RAM and database size.

sh stop 2 The default location of the OpsCenter database is /opt/SYMCOpsCenterServer/db/data. ~. Copy vxpmdb.db from the default location (INSTALL_PATH\OpsCenter\server\db\data). # etc. you can delete vxpmdb. @. For example.bat start 5 You should run and monitor OpsCenter for a certain period after moving the database. $. Restart all OpsCenter server services. If OpsCenter works as expected. Enter the following command: unlink /opt/SYMCOpsCenterServer/db/data .216 Installing Symantec OpsCenter 7.conf file. To move the OpsCenter database to a different hard disk on UNIX 1 Stop all OpsCenter server processes. Back up the OpsCenter database (/opt/SYMCOpsCenterServer/db/data) to some other location. enter the following command: INSTALL_PATH\OpsCenter\server\bin\opsadmin. To restart all OpsCenter services. Enter the following command: cp –R /opt/SYMCOpsCenterServer/db/data /backup/data 3 To move the database to a custom location like /usr/mydata. ^.db from INSTALL_PATH\OpsCenter\server\db\data to a location like E:\Database. replace the contents of the file with the following: "E:\Database\vxpmdb. do not specify a path like E:\Database%. !.db and symcOpscache. Save the databases. Enter the following command: /opt/SYMCOpsCenterServer/bin/opsadmin.enter the following command: mv /opt/SYMCOpsCenterServer/db/data/* /usr/mydata 5 Remove the symbolic link that exists for the OpsCenter database. 4 Copy the database file to the new location. Also the directories in the specified path should not contain any special characters like %. first create the new directory by entering the following command: mkdir -p /usr/mydata 4 To move the database to a custom location like /usr/mydata.db and symcOpscache. &.db" Make sure that you specify the path in double quotes.1 Post-installation tasks 3 To move the database to a custom location like E:\Database.

you can delete vxpmdb. If OpsCenter works as expected. Saving the OpsCenter log files on a different drive Symantec recommends that you install the OpsCenter log files on a drive that is different from where OpsCenter Server software and operating system is installed. and the OpsCenter Web GUI components. see the following section. See “Checking the debug level of logs” on page 217. See “Saving the log files to a different directory on UNIX” on page 220.1 Post-installation tasks 217 6 Create a symbolic link to /usr/mydata in /opt/SYMCOpsCenterServer/db/data.sh start You should run and monitor OpsCenter for a certain period after moving the database. The default debug level of OpsCenter logs is 1.Installing Symantec OpsCenter 7. This should be done only if the debug level of logs is greater than 1. See “Saving the log files to a different directory on Windows” on page 218. To know the debug level of your logs. enter the following command: ln -s /opt/SYMCOpsCenterServer/db/data /usr/mydata 7 Restart all OpsCenter server processes by entering the following command: /opt/SYMCOpsCenterServer/bin/opsadmin. You can control how OpsCenter writes log files for OpsCenter Server. To create a symbolic link. Checking the debug level of logs You can check the debug level of OpsCenter logs by using the following procedure.db and symcOpscache. . OpsCenter Agent.db from /backup/data.

By default.218 Installing Symantec OpsCenter 7. OpsCenter writes VxUL logs to the following directories: OpsCenter Server OpsCenter Agent OpsCenter View Builder INSTALL_PATH\OpsCenter\server\logs INSTALL_PATH\OpsCenter\Agent\logs INSTALL_PATH\OpsCenter\gui\logs .1 Post-installation tasks To check the debug level of logs 1 Navigate to the following location: Windows INSTALL_PATH\OpsCenter\server\bin\ or INSTALL_PATH\OpsCenter\Agent\bin\ UNIX /opt/SYMCOpsCenterServer/bin or /opt/SYMCOpsCenterAgent/bin 2 Enter the following command: vxlogcfg -l -p 58330 -o <OID> -q The following OID values must be used for OpsCenter components: OpsCenter Server OpsCenter Agent OpsCenter View Builder 148 146 147 Saving the log files to a different directory on Windows Use the following procedures to save the log files for OpsCenter components in a different directory.

To save the log files for OpsCenter Web GUI in a different location 1 Enter the following command to save log files to a different location: INSTALL_PATH\OpsCenter\server\bin\vxlogcfg -a –p 58330 -o 147 -s LogDirectory="<New log directory location>" Note: 58330 is the OpsCenter product ID. 2 3 Select Control Panel > Administrative Tools > Services and stop the Symantec OpsCenter Web Server Service.1 Post-installation tasks 219 To save the log files for OpsCenter server in a different location 1 Enter the following command to save log files to a different location: INSTALL_PATH\OpsCenter\server\bin\vxlogcfg -a –p 58330 -o 148 -s LogDirectory="<New log directory location>" Note: 58330 is the OpsCenter product ID. 2 3 Select Control Panel > Administrative Tools > Services and stop the Symantec OpsCenter Agent Service. 146 is the OID for OpsCenter Agent. 2 3 Select Control Panel > Administrative Tools > Services and stop the Symantec OpsCenter Server Service. 148 is the OID for OpsCenter server. . 147 is the OID for OpsCenter Web GUI.Installing Symantec OpsCenter 7. Select Control Panel > Administrative Tools > Services and start the Symantec OpsCenter Web Server Service. To save the log files for OpsCenter Agent in a different location 1 Enter the following command to save log files to a different location: INSTALL_PATH\OpsCenter\Agent\bin\vxlogcfg -a –p 58330 -o 146 -s LogDirectory="<New log directory location>" Note: 58330 is the OpsCenter product ID. Select Control Panel > Administrative Tools > Services and start the Symantec OpsCenter Server Service. Select Control Panel > Administrative Tools > Services and start the Symantec OpsCenter Agent Service.

146 is the OID for OpsCenter Agent. 2 Enter the following command to stop the OpsCenter server process: /opt/SYMCOpsCenterServer/bin/stopserver 3 Enter the following command to start the OpsCenter server process: /opt/SYMCOpsCenterServer/bin/startserver To save the log files for OpsCenter Agent in a different location 1 Enter the following command to save log files to a different location: /opt/SYMCOpsCenterAgent/bin/vxlogcfg -a -p 58330 -o 146 -s LogDirectory="<New log directory location>" Note: 58330 is the OpsCenter product ID. 148 is the OID for OpsCenter server.220 Installing Symantec OpsCenter 7. 2 Enter the following command to stop the OpsCenter Agent process: /opt/SYMCOpsCenterAgent/bin/stopagent 3 Enter the following command to start the OpsCenter server process: /opt/SYMCOpsCenterAgent/bin/startagent .1 Post-installation tasks Saving the log files to a different directory on UNIX Use the following procedures to save the log files for OpsCenter components in a different location. By default. OpsCenter writes VxUL logs to the following directories: OpsCenter Server OpsCenter Agent OpsCenter View Builder /opt/SYMCOpsCenterServer/logs /opt/SYMCOpsCenterAgent/logs /opt/SYMCOpsCenterGUI/logs To save the log files for OpsCenter server in a different location 1 Enter the following command to save log files to a different location: /opt/SYMCOpsCenterServer/bin/vxlogcfg -a -p 58330 -o 148 -s LogDirectory="<New log directory location>" Note: 58330 is the OpsCenter product ID.

sh Adjusting the heap size for OpsCenter components Use the following procedures to adjust the heap size for OpsCenter components.1 Post-installation tasks 221 To save the log files for OpsCenter Web GUI in a different location 1 Enter the following command to save log files to a different location: /opt/SYMCOpsCenterServer/bin/vxlogcfg -a -p 58330 -o 147 -s LogDirectory="<New log directory location>" Note: 58330 is the OpsCenter product ID. 2 Enter the following command to stop the OpsCenter Web server process: /opt/SYMCOpsCenterServer/bin/stopgui.sh 3 Enter the following command to start the OpsCenter Web server process: /opt/SYMCOpsCenterServer/bin/startgui. it may be helpful to increase the OpsCenter Server heap size. The OpsCenter Server default heap size can be increased from 2048 MB to a higher value (like 4096 MB) for 64-bit platforms. You can determine a higher value based on the physical (RAM) and virtual memory that is available on your system.Installing Symantec OpsCenter 7. 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). . 147 is the OID for OpsCenter Web GUI. The OpsCenter Server default heap size can be increased from 1024 MB up to 1400 MB for 32-bit platforms.

3 4 Save the OpsCenterServerService. replace -Xmx1024M with -Xmx1400M to increase the maximum heap size from 1024 MB to 1400 MB.bat stop INSTALL_PATH\OpsCenter\server\bin\opsadmin.1 Post-installation tasks To adjust the heap size on Windows servers 1 Open OpsCenterServerService. Enter the following commands to first stop and then start all OpsCenter server services as follows: INSTALL_PATH\OpsCenter\server\bin\opsadmin. <CmdArg value="-Xms512M -Xmx1024M For example. You must restart all OpsCenter server services for the changes to be effective.bat start To adjust the heap size on UNIX servers 1 Open startserver file from the following location: /opt/SYMCOpsCenterServer/bin 2 Modify the -Xmx2048M value in the following string: MAX_HEAP=-Xmx2048M For example. replace -Xmx2048 with -Xmx4096 to increase the maximum heap size from 2048 MB to 4096 MB. On 64-bit systems. modify the -Xmx2048M value in the following string: <CmdArg value="-Xrs -Xmx2048M For example. replace -Xmx2048M with -Xmx4096M to increase the maximum heap size from 2048 MB to 4096 MB.222 Installing Symantec OpsCenter 7.xml file from the following location on the OpsCenter server: INSTALL_PATH\OpsCenter\server\bin 2 Modify the Xmx1024M value in the following string. .xml file.

.1 Post-installation tasks 223 3 4 Save the startserver file. You must restart all OpsCenter server processes for the changes to be effective.xml file from the following location on the OpsCenter server: INSTALL_PATH\OpsCenter\gui\bin\OpsCenterGUIService. Note: This string may be listed twice in the OpsCenterGUIService.xml file to adjust the heap size. You can determine a higher value based on the physical (RAM) and virtual memory that is available on your system. The OpsCenter Web server default heap size can be increased from 1024 MB to a higher value (like 2048 MB) for 64-bit platforms.xml 2 Modify the Xmx1024m value in the following string.sh start 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.xml file.Installing Symantec OpsCenter 7. <EnvVar name="JAVA_OPTS" value="-Xrs -Xms512m -Xmx1024m For example. replace -Xmx1024m with -Xmx1400m to increase the maximum heap size from 1024 MB to 1400 MB. You can change the first occurrence of -Xmx1024m in the OpsCenterGUIService. To adjust the heap size on Windows servers 1 Open OpsCenterGUIService. 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.sh stop /opt/SYMCOpsCenterServer/bin/opsadmin. you should increase the Web server default. Enter the following commands to first stop and then start all OpsCenter server processes as follows: /opt/SYMCOpsCenterServer/bin/opsadmin.

3 4 Save the startGUI file. Note: The OpsCenter Agent runs as a 32-bit application on 64-bit Windows platforms. 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 1400 MB for Windows 64-bit platforms.xml file. Enter the following commands to first stop and then start all OpsCenter server processes as follows: /opt/SYMCOpsCenterServer/bin/opsadmin.224 Installing Symantec OpsCenter 7.sh stop /opt/SYMCOpsCenterServer/bin/opsadmin.bat stop INSTALL_PATH\OpsCenter\server\bin\opsadmin. Hence. JAVA_OPTS="-Xrs -d64 -Xms512M -Xmx1024m. Enter the following commands to first stop and then start all OpsCenter server services as follows: INSTALL_PATH\OpsCenter\server\bin\opsadmin.1 Post-installation tasks 3 4 Save the OpsCenterGUIService. You must restart all OpsCenter server services for the changes to be effective. replace -Xmx1024M with -Xmx1400M to increase the maximum heap size from 1024 MB to 1400 MB. . You must restart all OpsCenter server processes for the changes to be effective. For example..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.. The OpsCenter Agent default heap size can be increased from 1024 MB to a higher value (like 2048 MB) for 64-bit platforms. You can determine a higher value based on the physical (RAM) and virtual memory that is available on your system. it may be helpful to increase the OpsCenter Agent heap size.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).

replace -Xmx1024M with -Xmx1400M to increase the maximum heap size from 1024 MB to 1400 MB. Select Control Panel > Administrative Tools > Services and stop the Symantec OpsCenter Agent Service. You must restart the OpsCenter Agent process for the changes to be effective. 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. <CmdArg value="-Xms512M -Xmx1024M For example. 5 Select Control Panel > Administrative Tools > Services and start the Symantec OpsCenter Agent Service.xml file from the following location on the OpsCenter server: INSTALL_PATH\OpsCenter\Agent\bin 2 Modify the Xmx1024M value in the following string. Enter the following commands to first stop and then start OpsCenter Agent process as follows: /opt/SYMCOpsCenterAgent/bin/stopagent /opt/SYMCOpsCenterAgent/bin/startagent .xml file.Installing Symantec OpsCenter 7. To restart the OpsCenter Agent service. first stop and then start the Symantec OpsCenter Agent Service. MAX_HEAP=-Xmx1024M For example. You must restart the OpsCenter Agent service for the changes to be effective. 3 4 Save the startagent file. replace -Xmx1024M with -Xmx2048M to increase the maximum heap size from 1024 MB to 2048 MB.1 Post-installation tasks 225 To adjust the heap size on Windows servers 1 Open OpsCenterAgentService. 3 4 Save the OpsCenterAgentService.

2 Stop and restart the OpsCenter services. You can also set the cache size using the -c server option. to increase the cache size to 512 MB. After you install OpsCenter.bat stop INSTALL_PATH\OpsCenter\server\bin\opsadmin.conf file. add -c 512M -cs to the content of server.log " -c 512M -cs -m The -cs option logs the cache size changes for the database server. you should add -c 1G -cs to the content of the server.ServerPort=13786) -o "install_path\db\log\server. the database size can grow rapidly as you add more master servers.226 Installing Symantec OpsCenter 7.log" -m should be changed to -n OPSCENTER_<hostname> -x tcpip(BROADCASTLISTENER=0. to increase the cache size to 1 GB. 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.bat start . as follows: INSTALL_PATH\OpsCenter\server\bin\opsadmin. In the same manner. Sybase automatically adjusts the cache size for optimum performance.DOBROADCAST=NO.conf file: -n OPSCENTER_<hostname> -x tcpip(BROADCASTLISTENER=0.DOBROADCAST=NO.1 Post-installation tasks Adjusting the OpsCenter database cache size The amount of memory available for database server cache is an important factor in controlling OpsCenter performance. Symantec recommends that you adjust the Sybase cache size after installing OpsCenter.ServerPort=13786) -o "install_path\db\log\server.

Installing Symantec OpsCenter 7. The following: -n OPSCENTER_<hostname> -x tcpip(BROADCASTLISTENER=0.DOBROADCAST=NO. The OpsCenter database should be defragmented after a purge operation. See “Configuring the data purge period on the OpsCenter Server” on page 309. The -cs option logs the cache size changes for the database server. you can increase the Sybase cache size to 512 MB by changing the server. For example. 2 3 Save the server.DOBROADCAST=NO.) -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. See “Defragmenting the OpsCenter database” on page 271. as follows: /opt/SYMCOpsCenterServer/bin/opsadmin.ServerPort=13786. replace -c 25M -ch 500M -cl 25M with -c 1G -cs. Stop and restart the OpsCenter processes.1 Post-installation tasks 227 To set the cache size using the -c server option on UNIX servers 1 Open the /opt/SYMCOpsCenterServer/db/conf/server. In the same manner.conf file to increase the cache size to 512 MB.sh start About purging data periodically You should purge the OpsCenter data periodically.ServerPort=13786. The -ch and -cl server options are used to set the maximum and the minimum cache size respectively. .) -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.conf file content.conf file.conffile and change the value of the -c option.sh stop /opt/SYMCOpsCenterServer/bin/opsadmin. to increase the cache size to 1 GB.

Performance issues exist when the OpsCenter server software is installed on a Sun T1 server. Symantec does not recommend running OpsCenter on any server that lacks a dedicated floating-point unit. The issue of limited floating point capability on T1 servers has been resolved with the T2 servers. the calculations are handled in floating-point emulation. If you have configured report schedules. Symantec recommends that you install OpsCenter server software on a Sun T2 server. If the server's processor does not have a dedicated floating-point unit.228 Installing Symantec OpsCenter 7. The following is a list of procedure-based reports: ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Backup Job Size Variance Throughput Variance File Count Variance Backup Duration Variance BMR Client Configuration Backup Failures Clients Not Backed up Client Summary Dashboard Master Server Job Throughput Media Server Job Throughput Disk Usage Storage Unit Usage Media Summary by Media Server . Emulation mode slows down OpsCenter's performance. Reports are slow and take a longer time to run. the reports may reach later than the scheduled time. Procedure-based reports may not run before timeout happens (in 30 minutes).1 Post-installation tasks About OpsCenter performance and floating-point calculations Symantec OpsCenter performs certain calculations that require floating-point math. Symantec recommends that you schedule procedure-based reports in such a scenario. About known performance issues The following known issues may occur when the database size increases: ■ The performance of OpsCenter reports degrades.

Installing Symantec OpsCenter 7. In case you have not uninstalled NOM or VBR and want to use your existing NOM or VBR software. If you have not uninstalled NOM or VBR. you can use your older installation.1 server.1 on Windows” on page 231. the OpsCenter installer only stops the existing NOM or VBR services. To start using NOM or VBR on Windows 1 2 Log on to the OpsCenter server as an Administrator. Uninstall OpsCenter server software. When you upgrade from NOM or VBR to OpsCenter server. 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.1 Using an earlier NOM or VBR installation after upgrade 229 ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Virtual Client Summary Capacity Planning Historical Capacity Planning Forecasted Drive Throughput Drive Utilization Success Rate Line Daily Summary of Backup Activity All Failed Backups Consecutive Failures Report All Jobs Client Risk Analysis Client Coverage Using an earlier NOM or VBR installation after upgrade You can revert back to using your older NOM or VBR software even after upgrading to OpsCenter 7. See “Uninstalling Symantec OpsCenter 7. use the following procedure. It does not uninstall your existing NOM or VBR installation. .

Uninstall OpsCenter server software.1 Uninstalling Symantec OpsCenter on Windows and UNIX 4 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. You must remove OpsCenter. 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. you must reinstall Symantec Product Authentication Service that was shipped with your NOM version. the keys are not removed from Add or Remove Programs dialog box. In case domains are not visible on the logon page and you cannot log on to NOM.vbs VBR 5 Log on to the NOM or VBR console. . See the NOM documentation for more information. See the NOM documentation for more information. Use setup. the keys are not recreated to display an entry in Add or Remove Programs dialog box.230 Installing Symantec OpsCenter 7. See “Uninstalling Symantec OpsCenter 7. If a rollback occurs during an uninstall of OpsCenter. you must reinstall Symantec Product Authentication Service that was shipped with your NOM version. Uninstalling Symantec OpsCenter on Windows and UNIX This section describes uninstallation procedures for OpsCenter on Windows and UNIX. Note: After a rollback.1 on UNIX ” on page 231. To start using NOM or VBR on UNIX 1 2 Log on to the OpsCenter server as root.exe to remove OpsCenter. In case domains are not visible on the login page and you cannot log on to NOM.

1 on UNIX Use the Uninstall Script.Installing Symantec OpsCenter 7. click Symantec OpsCenter Server (64bit) and click Remove. Click Next to continue and remove Symantec OpsCenter Agent from your computer. ensure that NetBackup-Windows GUI is not running. . click Add/Remove Programs. Click Symantec OpsCenter Server and click Remove. In the Windows Control Panel.1 Uninstalling Symantec OpsCenter on Windows and UNIX 231 Uninstalling Symantec OpsCenter 7. For Windows 64-bit systems. Uninstalling Symantec OpsCenter 7. click Add/Remove Programs. Close any NetBackup-Windows GUI consoles that are open before uninstalling OpsCenter components. Click Symantec OpsCenter View Builder and click Remove. 4 Click Next to continue and remove Symantec OpsCenter Server from your computer. To uninstall Symantec OpsCenter Server on Windows 1 2 3 Log on to the target host as a user with administrator privileges.1 on Windows Use the Windows Add/Remove Programs utility to uninstall OpsCenter on a Windows host. which resides in the root directory of the product DVD and also in opt/VRTS/install directory. Note: Before uninstalling OpsCenter components. To uninstall Symantec OpsCenter View Builder on Windows 1 2 3 4 Log on to the target host as a user with administrator privileges. Click Symantec OpsCenter Agent and click Remove. In the Windows Control Panel. click Add/Remove Programs. to uninstall OpsCenter on a UNIX host. 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 Next to continue and remove Symantec OpsCenter View Builder from your computer.

do one of the following: ■ Type y.1 Uninstalling Symantec OpsCenter on Windows and UNIX Note: If you want to reinstall OpsCenter components. The VBR uninstaller (and not the OpsCenter uninstaller) must be used to remove the VRTSccsvs package.q. When you upgrade from VBR server to the OpsCenter Server and then uninstall OpsCenter Server. ■ Type n.232 Installing Symantec OpsCenter 7. Note: Symantec recommends that you do not cancel or interrupt the uninstallation process once it is started. 4 When asked to confirm if you want to uninstall OpsCenter Server. type n and press Enter./uninstallOpsCenterServer The Uninstall Script checks the components that are installed on the system. 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. Change to the following directory: /opt/VRTS/install . use the product DVD. When the uninstall is complete. You cannot reinstall OpsCenter components using the install scripts in the opt/VRTS/install directory. Change to the following directory: opt/VRTS/install 3 Type the following command and press Enter: . The Uninstall Script stops all processes and then uninstalls the component packages. Press Enter to cancel the uninstall procedure. To uninstall OpsCenter Server on UNIX 1 2 Open a UNIX console and log on as root on the target host. it displays a summary of the uninstall. including the location of the uninstall log files. Press Enter to start the uninstall process.n.?] (n) If you see this prompt. To uninstall OpsCenter Agent on UNIX 1 2 Open a UNIX console and log on as root on the target host.

You can install an OpsCenter 7. do one of the following: ■ Type y.Installing Symantec OpsCenter 7. Press Enter to start the uninstall process. In a cluster. 4 When asked to confirm if you want to uninstall OpsCenter Agent. Clustering Symantec OpsCenter The following sections describe how you can cluster OpsCenter 7. users experience only a short interruption in service. OpsCenter is shut down on the active node and starts on one of the failover nodes in the cluster. You can cluster only the OpsCenter Server. Symantec OpsCenter (OpsCenter) operates in an active or passive failover configuration.1 cluster on the following platforms: ■ Windows 2008 R2 x64 . If a node becomes unavailable./uninstallOpsCenterAgent The Uninstall Script checks the components that are installed on the system.1.1 Clustering Symantec OpsCenter 233 3 Type the following command and press Enter: . resources running on that node migrate to an available node. When the uninstall is complete. Press Enter to cancel the uninstall procedure. including the location of the uninstall log files. ■ Type n. OpsCenter Server must be installed on the active node and the passive (or failover nodes). Supported OS and cluster solutions An OpsCenter cluster is supported on Windows and Solaris platforms. This failover provides high availability for OpsCenter. it displays a summary of the uninstall. two or more nodes are linked in a network and work collectively as a single system. All nodes in a cluster are constantly aware of the status of resources on the other nodes. The Uninstall Script stops all processes and then uninstalls the component packages. About a Symantec OpsCenter cluster Clusters provide high availability of applications and data to users. When a failover occurs in an OpsCenter cluster. Installing OpsCenter in a clustered environment makes OpsCenter a highly available application. Each node can access the shared disks with the help of cluster software. During failover.

The command may fail to run and may sometimes result in an unexpected behavior. For more information about VCS. . running the dbbackup command on an inactive node may result in the following unexpected result: Command: E:\OpsCenter\server\bin>dbbackup. you must run commands on the active node.234 Installing Symantec OpsCenter 7.bat E:\temp Result: "Could not find Z:\OpsCenter\server\config\db. For example. see the Veritas Cluster Server User's Guide.1 Clustering Symantec OpsCenter ■ ■ ■ Windows 2008 x86 and x64 Windows 2003 x86 and x64 Solaris SPARC 10 For Symantec OpsCenter to be clustered. You may get unexpected results if you run a command on an inactive node. the OpsCenter service group may failover if the command requires restarting the OpsCenter services. and restart services on a different system when hardware or software fails. About running commands on the active node For a clustered OpsCenter server. Table 2-17 lists the supported versions of VCS. With VCS you can monitor systems and application services. Table 2-17 Platform VCS Windows VCS Solaris OpsCenter cluster support matrix Latest supported version Start of support 5. you must have Veritas Cluster Server (VCS) installed. Some OpsCenter commands or utilities like the support utility require restarting the services.1 4.conf file" In addition.1 5.3 VCS is a high-availability solution for cluster configurations. Note: Clustered OpsCenter is not supported on MSCS.2 RP2 4.

bat stop .Installing Symantec OpsCenter 7.exe showispbxexchflag This command gives the value of pbxexchflag. 2 Navigate to INSTALL_PATH\Security\Authentication\bin directory. you must stop all OpsCenter Server services. When pbxexchflag is set. its value is equal to 1 and this means that PBX and AT are connected. In case the value of pbxexchflag is 1. Verify if the value of pbxexchflag is 1. 3 Stop all the OpsCenter Server services by executing the following command: INSTALL_PATH\OpsCenter\server\bin\opsadmin. To connect Symantec Product Authentication Service and Symantec Private Branch Exchange 1 Open the command prompt and enter the following command: INSTALL_PATH\Security\Authentication\bin\vssat. Before setting the value of pbxexchflag. To check if AT and PBX are connected. you do not need to follow the remaining steps. Note: The information in this section applies to OpsCenter clusters only. Enter the following command at the bin directory to set the value of pbxexchflag: vssat. you need to set it to 1. If the value of pbxexchflag is 0. verify whether pbxexchflag of the authentication service is set or not. Use the following procedure to connect the authentication service and PBX components.exe setispbxexchflag --enable The value of pbxexchflag is set to 1. See step 1. Symantec Product Authentication Service and Symantec Private Branch Exchange. you must restart these services.1 Clustering Symantec OpsCenter 235 Connecting Symantec Product Authentication Service and Symantec Private Branch Exchange An OpsCenter cluster requires that the authentication service and PBX components that are installed on the remote host are connected. After setting the value of pbxexchflag to 1.

or Execute the following command in a command console: net start vrtsat 6 Restart all the OpsCenter Server services by performing the following steps: ■ ■ Navigate to INSTALL_PATH\OpsCenter\server\bin directory. . If the value of pbxexchflag is 0. you do not need to follow the remaining steps of this procedure. 2 Enter the following command at the bin directory to set the value of pbxexchflag: /opt/VRTSat/bin/vssat setispbxexchflag --enable The value of pbxexchflag is set to 1. Follow step 1 of this procedure to verify if the value of pbxexchflag is 1.bat start To connect Symantec Product Authentication Service and Symantec Private Branch Exchange on Solaris 1 Open the command console and enter the following command: /opt/VRTSat/bin/vssat showispbxexchflag This command gives the value of pbxexchflag.236 Installing Symantec OpsCenter 7. Restart all the OpsCenter Server services by executing the following command: opsadmin. In case the value of pbxexchflag is 1. or Execute the following command in a command console: net stop vrtsat 5 Restart Symantec Product Authentication Service by performing either of the following steps: ■ ■ Use the start option in the Windows Service pane. you need to set it to 1.1 Clustering Symantec OpsCenter 4 Stop Symantec Product Authentication Service by performing either of the following steps: ■ ■ Use the stop option in the Windows Service pane.

Table 2-18 provides the Windows clustering steps. For example. 3 Install OpsCenter 7. 2 Make sure that you have met all prerequisites. if the process ID of vxatd service is 203.Installing Symantec OpsCenter 7. on a Windows host. run the following command: kill 203 5 Run the following command to restart Symantec Product Authentication Service: /opt/VRTSat/bin/vxatd 6 Run the following command to restart all the OpsCenter Server services: /opt/SYMCOpsCenterServer/bin/opsadmin.1 and AT on a remote Windows host” on page 239. Limitations of Symantec OpsCenter cluster on Windows An OpsCenter cluster has the following limitations: .sh start Clustering Symantec OpsCenter on Windows This section provides information about installing Symantec OpsCenter in a clustered mode.1 Clustering Symantec OpsCenter 237 3 Stop all the OpsCenter Server services by entering the following command: /opt/SYMCOpsCenterServer/bin/opsadmin. See “Prerequisites for Symantec OpsCenter cluster on Windows” on page 238.sh stop 4 Stop Symantec Product Authentication Service by issuing kill command on the process ID of the vxatd service. Table 2-18 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 237.1. See “Installing Symantec OpsCenter Agent 7.

■ ■ ■ 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. Follow the steps in the Veritas Cluster Server Installation Guide.com Verify that the supported version of VCS is correctly installed and configured.2 versions. Also. OpsCenter cluster cannot co-exist with any other Symantec product running in secure mode using the Symantec Product Authentication Service. ensure that the patch available through Technote 278307 is installed before installing OpsCenter. OpsCenter does not support clustered AT. ping the IP address and verify that the IP address is not plumbed. For OpsCenter. Only use these for the OpsCenter resource. Note that an OpsCenter 7. Verify that you have the OpsCenter installation program and a valid license key. Verify that you have an IP address and host name (virtual host name) to be assigned to the OpsCenter resource in VCS. Verify that you can mount the disk.1 cluster can be upgraded to an OpsCenter 7.com/docs/278307 This Technote is applicable to OpsCenter.symantec. The SharedDisk must be configured and accessible to all cluster nodes where you want to install OpsCenter. ■ ■ ■ ■ ■ ■ ■ . Verify that no VCS resource group and resource exist with the same name as that which you intend to use for OpsCenter.238 Installing Symantec OpsCenter 7. visit the following Web site: http://entsupport.symantec. For a list of supported storage devices.0. The virtual host name must be the short name and less than 15 characters. ■ Verify that VCS and OpsCenter support your hardware.OpsCenter Agent and the OpsCenter View Builder cannot be clustered. For VCS Windows 4.1 Clustering Symantec OpsCenter ■ Only the OpsCenter Server can be clustered.1 cluster.0 or 7. The patch is available from the following URL: http://entsupport. on a Windows host. the supported VCS version starts from 4.2 RP2. Upgrades from previous versions of NOM or VBR to clustered OpsCenter Server is not supported.

1 Clustering Symantec OpsCenter 239 ■ For a Windows cluster. ■ ■ ■ AT must be installed separately (and not along with OpsCenter) on the remote host.1 DVD. Note the following points about installing OpsCenter Agent 7. Refer to theVeritas Storage Foundation Administrator’s Guide for details. you need to create a . Verify that OpsCenter installation is carried out with the domain admin account.1. AT must be installed in a non-clustered mode.1 and then install AT from the OpsCenter 7. see the Symanetc Infrastructure Core Services Installation Guide. Clustered OpsCenter Server uses this authentication broker.1 Agent.Installing Symantec OpsCenter 7. ■ Verify that authentication service and PBX components on the remote host are connected. To establish a connection between AT host and OpsCenter Server host. AT can be installed in Root + AB or AB mode on the remote host. Before installing OpsCenter Server. See “Connecting Symantec Product Authentication Service and Symantec Private Branch Exchange” on page 235.1 and AT on a remote Windows host OpsCenter Server requires that OpsCenter Agent 7. PBX is installed when you install OpsCenter 7.1 (PBX) and AT on the remote host: ■ ■ ■ ■ Symantec recommends that you first install OpsCenter Agent 7.1 DVD. You can either configure AT in root + authentication broker (Root + AB) mode or authentication broker (AB) mode.1 (PBX) and Symantec Product Authentication Service (AT) are installed on a standalone host. For more information about installing AT. You must install the version of AT Service that is shipped with OpsCenter 7. ensure that Symantec OpsCenter Agent 7. before OpsCenter can be clustered. Symantec recommends that you first install OpsCenter Agent 7. Symantec recommends that you configure AT in a 'Root+AB' mode. Installing Symantec OpsCenter Agent 7. verify that the cluster disk groups and dynamic volumes for OpsCenter are created on the shared storage.1 (PBX) and Symantec authentication service (AT) Server are installed separately on a remote host. Verify that all VCS services are up and running on all the nodes in the cluster.1 (PBX) and then install AT from the OpsCenter 7.

the Symantec OpsCenter Installation Wizard appears. 4 5 On the Symantec OpsCenter Installation Wizard. Use the credentials of this user when installing OpsCenter Server. in the Open text box.1.1. type ‘D:\Browser. If autorun is not enabled.1 on the remote host. see the following technote for the latest information: http://entsupport.symantec.com/docs/336967 The OpsCenter Agent 7.1 and AT. The Symantec OpsCenter Installation Wizard appears. See “Installing Symantec OpsCenter Agent on Windows” on page 109. On the Run dialog box. . click the Installation link.1 Clustering Symantec OpsCenter principal user on the AT host.240 Installing Symantec OpsCenter 7. Click Symantec Product Authentication Service. You must upgrade to the version of authentication service that is shipped with OpsCenter 7. Note: In case of updates made to AT for OpsCenter 7. Note: Symantec Product Authentication Service is installed when you install Veritas Cluster Server. To install Agent and AT on the remote Windows host 1 2 Log on to the remote host where you want to install OpsCenter Agent 7. ■ ■ If autorun is enabled.exe’ and press Enter: Where D is the DVD drive. Note: OpsCenter does not support clustered AT. Install OpsCenter Agent 7.1 DVD.1 and AT can be installed on the remote host using the following procedure. 3 Install AT from the OpsCenter 7. click Start > Run.

click Start > Run.Installing Symantec OpsCenter 7.exe. first install the OpsCenter Server on the active node and then on the passive nodes. the Symantec OpsCenter Installation Wizard appears. in the Open text box.exe’ and press Enter: Where D is the DVD drive. To install OpsCenter Server in a clustered mode on Windows 1 2 On an active cluster node where you want to install OpsCenter server. Note that you should not cluster the AT service. insert the OpsCenter DVD in the DVD drive. On the Run dialog box. Click the OpsCenter Server Installation link to install Symantec OpsCenter server.exe is executed.1 on a Windows cluster To cluster OpsCenter and make it highly available. The Symantec OpsCenter Installation Wizard appears. . you must install and configure OpsCenter in a clustered mode. If autorun is not enabled. you need to install OpsCenter Server manually on all the nodes.1 Clustering Symantec OpsCenter 241 6 Click Next. as OpsCenter does not support clustered AT. Also. Click Next. The VxSSVRTSatSetup. ■ ■ If autorun is enabled. See Symantec Infrstructure Core Services Installation Guide for more information about the VxSSVRTSatSetup. Note: To install OpsCenter Server in clustered mode. type ‘D:\Browser. 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 7. 3 4 5 On the Symantec OpsCenter Installation Wizard. 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. click the Installation link.

1 Clustering Symantec OpsCenter 6 7 Read the license agreement. 9 On the License Keys screen. The license keys that are already installed on the system are also displayed in the box that is shown on this screen. You need to install OpsCenter Server manually on each node of the cluster. Click Next. Also compare the space that is required for installation with the actual space available in the installation directory. Note: You can also add the license keys from the OpsCenter console. This option is enabled if you have Veritas Cluster Server (VCS) installed. Select Install a clustered OpsCenter Server to install OpsCenter Server in clustered mode. See “About the OpsCenter licensing model” on page 81. Note: Click Custom if you want to change the default settings and locations. enter the demo or permanent key that you have received with the purchase of OpsCenter and click Add Key.242 Installing Symantec OpsCenter 7. 8 In the Installation Method section. 10 Click Next. 11 On the Authentication Settings screen. The license type information is also shown along with the key. check ‘I accept the terms of the license agreement’ and click Next. More information about licenses is available. The Authentication Settings screen is displayed. click Typical to use the default settings and installation location. 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) . See “About managing licenses” on page 307.

You can select different public network for passive nodes. See “Installing Symantec OpsCenter Agent 7. only Public Network option is enabled. Z:\ Select LAN as a public network. The virtual host name must be the short name and less than 15 characters. . Virtual host Name Virtual IP address Subnet mask Path to Shared data Public Network Note: While installing OpsCenter on a passive node. enter the following information: Cluster Group Name Enter the name for the OpsCenter cluster. For example: 255. 14 Click Next.1 and AT on a remote Windows host” on page 239. Check Save Summary to field to save the installation summary.252.Installing Symantec OpsCenter 7. For example: OpsCenter_Server Enter the virtual host name that is assigned to the OpsCenter cluster. 13 On the Cluster Settings screen. For example. The installer shows the summary of the settings that you have selected for OpsCenter Server installation. Note: Ignore this step if you are installing OpsCenter on a passive node. Click Browse to save the installation summary in your preferred location. 12 Click Next. Enter the IP address that assigned to the OpsCenter cluster Enter the subnet mask . The Cluster Settings screen is displayed.0 Select the shared drive path that you have configured in VxVM.255.1 Clustering Symantec OpsCenter 243 Note: You must have this principal user created on the authentication broker (AB) host. For example: Oc_cluster.

244 Installing Symantec OpsCenter 7.0.0 (or 7.0. you need to install OpsCenter Server manually on all the nodes. Repeat this procedure for all the cluster nodes.1) cluster to OpsCenter 7.0 (or 7.1 Clustering Symantec OpsCenter 15 Click Install. You can bring the NetBackupOpsCenterVCS resource online from the CLI or by using the cluster GUI. first install the OpsCenter 7.1 on a Windows cluster and VCS is not configured properly. 16 After successful installation. you need to manually bring the NetBackupOpsCenterVCS resource online. When you click Next. . Note: After installing an OpsCenter cluster on Windows 2008 R2 x64 system. 17 Click Finish. the correct red icon is shown. then a green icon with the following error message is displayed on the Installation Status screen: "Pre install cluster configuration failed to complete" The green icon is misleading. Also. The installer starts installing the OpsCenter Server software.1 cluster on Windows. Note: To upgrade to OpsCenter 7. The icon should actually be red for an installation failure. In a clustered mode.1 Server on the active node and then on the passive nodes.1) cluster to OpsCenter 7. you can view the OpsCenter console or view installation logs. Use the following command: hares -online <resource name> -sys <Name of the active node> Example: hares -online newonelatest-OpsCenter -sys OPS-CLUSTER-1 Upgrading from OpsCenter 7. the default OpsCenter database location on Windows is the following location on the shared drive: OpsCenter\Server\db Note: When you install OpsCenter Server 7.1 cluster Use the following procedure to upgrade from OpsCenter 7.1 Server in a clustered mode.

Installing Symantec OpsCenter 7. Select Install a clustered OpsCenter Server to install OpsCenter Server in clustered mode. On the Run dialog box. click Start > Run.1) to OpsCenter 7.0 (or 7.0.1 Clustering Symantec OpsCenter 245 To upgrade to OpsCenter 7. Click Next. Click Next to continue.1) on the system. . Click the OpsCenter Server Installation link to install Symantec OpsCenter server. or port numbers while upgrading from OpsCenter 7. 7 8 Read the license agreement. You need to install OpsCenter Server manually on each node of the cluster.1) cluster that you want to upgrade.0 (or 7.0 In order to upgrade to a newer version. Click Next. the existing Symantec OpsCenter Server will be removed. insert the OpsCenter DVD in the DVD drive. The Symantec OpsCenter Installation Wizard appears. locations.0 (or 7. If autorun is not enabled.exe’ and press Enter: Where D is the DVD drive. This option is enabled if you have Veritas Cluster Server (VCS) installed. click the Installation link. the following message may be displayed on the Welcome screen: The Installation has detected that the following software is already installed on your system: Symantec OpsCenter Server: Version 7.0. in the Open text box. The Welcome Page of the Installation Wizard appears. Note: You cannot customize the default settings. Also compare the space that is required for installation with the actual space available in the installation directory. ■ ■ If autorun is enabled. The Installation Wizard detects an existing installation of OpsCenter Server 7. 9 In the Installation Method section.1. the Symantec OpsCenter Installation Wizard appears.0. click Typical to use the default settings and installation location. type ‘D:\Browser.1 Server in a clustered mode on Windows 1 2 From the active node of the OpsCenter 7. check ‘I accept the terms of the license agreement’ and click Next. 3 4 5 6 On the Symantec OpsCenter Installation Wizard. Depending on the installed version.

you are prompted to create it. 13 On the Cluster Settings screen. . You can select different public network for active and passive nodes. Note: You can also add the license keys from the OpsCenter console. The license type information is also shown along with the key. A green checkmark appears in the Required column if there is adequate disk space. The license keys that are already installed on the system are also displayed in the box that is shown on this screen. This option is disabled. enter the following information: Cluster Group Name Virtual host Name Virtual IP address Subnet mask Path to Shared data Public Network This option is disabled. Click Yes to create the directory. Select LAN as a public network. The default location is C:\Program Files\Symantec\OpsCenter_SavedData. enter the demo or permanent key that you have received with the purchase of OpsCenter and click Add Key. This option is disabled. This option is disabled. More information about licenses is available. 12 Click Next. See “About managing licenses” on page 307. This option is disabled. 11 On the License Keys screen. In case the directory C:\Program Files\Symantec\OpsCenter_SavedData does not exist. See “About the OpsCenter licensing model” on page 81.1 Clustering Symantec OpsCenter 10 Specify a location for saving the old OpsCenter database. Note: Ensure that the database location has adequate space by going through the Disk space requirements section on this page. Click Browse to specify a different location.246 Installing Symantec OpsCenter 7. The Cluster Settings screen is displayed.

. Right-click the selected cluster monitor panel and click Explorer View from the menu to access Cluster Explorer.1 Clustering Symantec OpsCenter 247 14 Click Next.1 from the Windows cluster Use the Windows Add/Remove Programs utility to uninstall OpsCenter Server from a Windows cluster. Click Next to continue and remove Symantec OpsCenter Server from your computer. 17 Click Finish. Click Yes to forcefully take the resource group offline. The installer shows the summary of the settings that you have selected for OpsCenter Server installation. you can view the OpsCenter console or view installation logs. Click Browse to save the installation summary in your preferred location. Note: In clustered mode. To unistall Symantec OpsCenter Server completely from the cluster 1 2 3 4 5 6 7 8 9 Log on to the active node as a user with administrator privileges. 15 Click Install.Installing Symantec OpsCenter 7. Check Save Summary to field to save the installation summary. Repeat this procedure for the passive nodes. In the Windows Control Panel. Log on to the cluster Web GUI. click Add/Remove Programs. Uninstalling Symantec OpsCenter 7. Click the Service Groups tab in the Cluster Explorer configuration tree. The installer starts installing the OpsCenter Server software. the default OpsCenter database location on Windows is the following location on the shared drive: OpsCenter\Server\db 16 After successful installation. Click Symantec OpsCenter Server and click Remove. Use the following procedure to uninstall OpsCenter from all the cluster nodes. Right-click the OpsCenter resource group and select Offline > All Systems.

1 Clustering Symantec OpsCenter 10 Uninstall OpsCenter software from all the nodes. Right-click the OpsCenter resource group and select Offline > All Systems. Right-click the selected cluster monitor panel and click Explorer View from the menu to access Cluster Explorer. 2 Make sure that you have met all prerequisites. Repeat steps 7 through 9 for all the passive nodes. Click Yes to delete the OpsCenter resource group. 11 Delete the OpsCenter resource groups manually. Note that the installer does not remove the OpsCenter resource groups. Deleting OpsCenter resource group from the cluster Use the following procedure to delete OpsCenter resource group from the cluster. Table 2-19 provides the Solaris clustering steps. Right-click the OpsCenter resource group and select Delete. See “Prerequisites for Symantec OpsCenter cluster on Solaris” on page 249.248 Installing Symantec OpsCenter 7. . See “Deleting OpsCenter resource group from the cluster” on page 248. Click Yes to forcefully take the resource group offline. Click the Service Groups tab in the Cluster Explorer configuration tree. To delete OpsCenter resource group from the cluster 1 2 3 4 5 6 7 Log on to the cluster Web GUI. a Symantec OpsCenter Server installation” on page 251. These must be removed manually. Table 2-19 Step 1 OpsCenter Server clustering steps Description Understand the limitations of an OpsCenter cluster Reference topic See “Limitations of Symantec OpsCenter cluster on Solaris” on page 249. 3 Make sure that your preinstallation See “Preinstallation checklist for checklist is complete. on a Solaris host. Clustering Symantec OpsCenter Server on Solaris This section provides information about installing OpsCenter Server in a clustered mode.

Only use these for the OpsCenter resource. Verify that you can mount the disk. For a list of supported storage devices.1. Follow the steps in the Veritas Cluster Server Installation Guide. ping the IP address and verify that the IP address is not plumbed. Limitations of Symantec OpsCenter cluster on Solaris An OpsCenter cluster has the following limitations: ■ Only the OpsCenter Server can be clustered.1) cluster to an OpsCenter 7. You can upgrade from OpsCenter 7.symantec.com Verify that the supported version of VCS is correctly installed and configured on Solaris. visit the following Web site: http://entsupport.OpsCenter Agent and OpsCenter View Builder cannot be clustered. Also. Verify that you have the OpsCenter installation program and a valid license key. ■ ■ ■ Prerequisites for Symantec OpsCenter cluster on Solaris The following requirements must be met before you install and configure a Symantec OpsCenter failover server: ■ Verify that VCS and OpsCenter support your hardware. Verify that no VCS resource group and resource exist with the same name as that which you intend to use for OpsCenter. OpsCenter does not support clustered AT. Reference topic See “Installing Symantec OpsCenter Server in a clustered mode on Solaris” on page 252. The SharedDisk must be configured and accessible to all cluster nodes where you want to install OpsCenter.0. OpsCenter cluster cannot co-exist with any other Symantec product running in secure mode using the Symantec Product Authentication Service. Upgrades from previous versions of NOM or VBR to clustered OpsCenter Server is not supported.0 (or 7. ■ ■ ■ ■ ■ ■ .1 Clustering Symantec OpsCenter 249 Table 2-19 Step 4 OpsCenter Server clustering steps (continued) Description Install OpsCenter 7.Installing Symantec OpsCenter 7.1 cluster. Verify that you have an IP address and host name (virtual name) to be assigned to the OpsCenter resource in VCS.

To establish a connection between AT host and OpsCenter Server host. PBX is installed when you install OpsCenter 7. you need to create a principal user on the AT host. See “Connecting Symantec Product Authentication Service and Symantec Private Branch Exchange” on page 235.1 (PBX) and AT on the remote host: ■ ■ Symantec recommends that you first install OpsCenter Agent 7.1 Agent.1 DVD.1 and AT on a remote host OpsCenter Server requires that OpsCenter Agent 7. Installing Symantec OpsCenter Agent 7.1. Symantec recommends that you configure AT in a 'Root+AB' mode. Note the following points about installing OpsCenter Agent 7. Note: Symantec Product Authentication Service is installed when you install Veritas Cluster Server.1 (PBX) and Symantec authentication service (AT) Server are installed separately on a remote host. . You must upgrade to the version of authentication service that is shipped with OpsCenter. Before installing OpsCenter Server. before OpsCenter can be clustered. ■ Verify that the authentication service and PBX components are connected.250 Installing Symantec OpsCenter 7. ensure that Symantec OpsCenter Agent 7. ■ ■ ■ AT must be installed separately (and not along with OpsCenter) on the remote host. You must install the version of AT Service that is shipped with OpsCenter 7. Use the credentials of this user when installing OpsCenter Server. AT must be installed in a non-clustered mode.1 DVD. see the Symanetc Infrastructure Core Services Installation Guide. Symantec recommends that you first install OpsCenter Agent 7.1 (PBX) and Symantec Product Authentication Service (AT) are installed on a standalone host.1 and then install AT from the OpsCenter 7.1 (PBX) and then install AT from the OpsCenter 7.1 Clustering Symantec OpsCenter ■ Verify that OpsCenter Server installation is carried out with the domain admin account. For more information about installing AT. AT can be installed in Root + AB or AB mode on the remote host. Clustered OpsCenter Server uses this authentication broker. You can either configure AT in root + authentication broker (Root + AB) mode or authentication broker (AB) mode.

3 To install AT. 5 Select 1 to install AT./installics script from the ICS directory.1 Clustering Symantec OpsCenter 251 Note: OpsCenter does not support clustered AT. Fill out the checklist before you begin installation. See “Installing Symantec OpsCenter Agent on UNIX” on page 114. See Symantec Infrstructure Core Services Installation Guide for more details on using the installics script. OpsCenter Agent 7. The following information is required for all VCS cluster configurations. The installics menu is displayed. Note: The configuration utility unless specified. Install OpsCenter Agent 7.1 and AT.Installing Symantec OpsCenter 7. Preinstallation checklist for a Symantec OpsCenter Server installation The OpsCenter Server requests certain cluster-related information during installation. Virtual Name for NetBackup: IP address : Subnet mask Node Name IP address ---------------------------------------------------------------------------------------------------------------------Network device name (NIC) . Navigate to the ICS directory: cd ICS 4 Invoke the . To install AT 1 2 Log on to the remote host where you want to install OpsCenter Agent 7.1 DVD.1 on the remote host using the OpsCenter 7.1 DVD. mount the OpsCenter 7. Answer y to enable Private Branch Exchange (PBX) support in authentication broker server. treats all attribute values globally. Note that you must enable PBX support for the authentication broker server.1 and AT can be installed on the remote host using the following procedure.

---------------------------------------- About installation of Symantec OpsCenter with VCS The following information is required if you use VCS.---------------------------------------. -y is also required) opsvol opsdg 0 or 1 0 or 1 Example Installing Symantec OpsCenter Server in a clustered mode on Solaris To cluster OpsCenter and make it highly available. . Scenario 1 . 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: ------------------------------------/opt/VRTSnbu /dev/vx/dsk/opsdg/opsvol vxfs (optional) (if you add other options. you must install and configure OpsCenter in a clustered mode.with VxVM” on page 252.252 Installing Symantec OpsCenter 7.with VxVM The following information is required if you use VCS with VxVM.---------------------------------------. Review the scenario that is described.1 Clustering Symantec OpsCenter ---------------------------------------.------------------------------------------------------------------------------.---------------------------------------.------------------------------------------------------------------------------. See “Scenario 1 .

To accept the default path (/opt). unmount the OpsCenter shared mount point. a confirmation prompt is displayed. If applicable. 5 Type the following command:. Select Server from the displayed options (Server and Agent). It prompts you in case OpsCenter is already installed. 10 Type y to confirm the directory path and press Enter. Review this list and press Enter to continue. Stop the volume the mount point is on and deport the disk group for that volume on all nodes of the cluster. The installer displays a list of components that are installed like PBX. To install OpsCenter Server in clustered mode on Solaris 1 Fill out the checklist for all configurations and the checklist for your specific environment. 2 3 4 Open a Solaris console and log on as root on the target host.1 Clustering Symantec OpsCenter 253 Note: To install OpsCenter Server in clustered mode. 11 When OpsCenter Server is installed on the clustered setup. you need to install OpsCenter Server manually on all the nodes. 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. Make sure that the shared disk is not mounted on any node in the cluster. . Also. The installer also examines the system for existing packages. The installer then checks if OpsCenter Server is installed on the system or not. first install the OpsCenter Server on the active node and then on the passive nodes. Press Enter. Press Enter to install OpsCenter Server. Press Enter to continue. Symantec Database etc.Installing Symantec OpsCenter 7. Symantec WebGUI Server. press Enter without typing a directory path. Mount the OpsCenter product DVD for the appropriate platform on which you are installing OpsCenter Server. 6 7 The Welcome message is displayed. See “Preinstallation checklist for a Symantec OpsCenter Server installation” on page 251./install.

the installed node is added to the cluster resource group. The following happens when OpsCenter Server is installed: ■ On the first node.1) cluster to OpsCenter 7. Note: To upgrade OpsCenter Server in a clustered mode. 2 Log on to the OpsCenter 7. you are prompted to confirm creation of an OpsCenter Server cluster. you need to install OpsCenter Server manually on all the nodes.1 Server on the active node and then on the passive nodes. On the other nodes. See “Preinstallation checklist for a Symantec OpsCenter Server installation” on page 251. refer to the checklist and provide details accordingly. ■ 12 When you are prompted for cluster-specific configuration details. 13 Allow OpsCenter to be installed in a cluster. To upgrade from OpsCenter 7.0. Caution: When you are prompted.1 Clustering Symantec OpsCenter ■ When you install OpsCenter Server on the first node. first install OpsCenter 7.1 cluster 1 Fill out the checklist for all configurations and the checklist for your specific environment. ■ Upgrading from OpsCenter 7. This name is case-sensitive and must be in the same format (FQDN/short) on all the nodes. You are prompted to join the group.0 cluster to OpsCenter 7.1 cluster on Solaris.1) cluster as root.0 (or 7.254 Installing Symantec OpsCenter 7. Also. you must provide the same virtual cluster name that you provided during the installation. Type Yes to set up OpsCenter in HA mode.0 (or 7. When you install OpsCenter Server on the subsequent nodes. a single node cluster resource group for OpsCenter is created and brought online. .0 cluster to OpsCenter 7.1 cluster Use the following steps to upgrade from an OpsCenter 7. Use the virtual name for the NetBackup server name.0. information of already created NetBackup OpsCenter cluster group is displayed.

press Enter. It prompts you in case OpsCenter Server is already installed. (/var/symantec/) Type the directory name in which the existing OpsCenter 7. 9 The Welcome message is displayed. unmount the OpsCenter shared mount point.1) cluster that you want to upgrade.1 software. AT. 4 Offline OpsCenter server resource by using the following command: hares -offline <opscenter server resource name> -sys <node> 5 Freeze OpsCenter group by using the following command: hagrp freeze <OpsCenter group name> -persistent sys 6 Stop NetBackup OpsCenter cluster agent on all nodes of the OpsCenter group using the following command: haagent -stop NetBackupOpsCenter -force -sys <node> 7 Log on to the active node and upgrade to OpsCenter Server 7. Review this list and press Enter to continue. OpsCenter Server. OpsCenter GUI etc. To accept the default directory path (/var/symantec).0 database and configuration files can be saved and then press Enter. The installer also examines the system for existing packages. Press Enter. Mount the OpsCenter product DVD on the OpsCenter 7./install. Press Enter to continue.0. 12 The installer displays a list of components that will be installed or upgraded like PBX. . not. Press Enter to install OpsCenter Server. 10 The installer then checks if OpsCenter Server is installed on the system or 11 The following prompt is displayed: Where should the existing Symantec OpsCenter database and configuration files be backed up? An 'OpsCenterServer_backup' directory will be created within the directory that you specify to store these files. 8 Type the following command: .1 Clustering Symantec OpsCenter 255 3 Make sure that the shared disk is not mounted on any node in the cluster.0 (or 7. If applicable.Installing Symantec OpsCenter 7. Stop the volume the mount point is on and deport the disk group for that volume on all nodes of the cluster. Select Server from the displayed options (Server and Agent).

256

Installing Symantec OpsCenter 7.1 Clustering Symantec OpsCenter

13 The installer prompts you with the following question:
installOpsCenterServer is now ready to upgrade OPSCENTERSERVER. Are you sure you want to upgrade OPSCENTERSERVER? [y,n,q] (y)

Press Enter to continue and upgrade to OpsCenter 7.1.

14 The installer displays the OpsCenter 7.0 (or 7.0.1) packages that are installed.
Depending on the installed packages, the following message may be displayed:
The following packages were found on the system. However the package versions are older than the ones required by OpsCenter. SYMCOpsCenterServer 7.0 was found on the system, but OpsCenter requires SYMCOpsCenterServer 7.1.0.0 SYMCOpsCenterGUI 7.0 was found on the system, but OpsCenter requires SYMCOpsCenterGUI 7.1.0.0 VRTSOpsCenterLegacyServer 7.0 was found on the system, but OpsCenter requires VRTSOpsCenterLegacyServer 7.1.0.0

The installer then uninstalls the older packages and installs OpsCenter 7.1 Server.

15 OpsCenter 7.1 Server is installed. Configuration changes are made to the
system.

16 The database upgrade process starts. In this process, data is migrated from
the OpsCenter 7.0 (or 7.0.1) database to the OpsCenter 7.1 database. The database process may take time depending on your database size. The following message is displayed:
The database upgrade is in progress. This may take some time based on the database size. To know the upgrade status, see dbManager_<timestamp>_.log file in the OpsCenter Server database logs directory (../db/log) after some time.

You can check the status of database upgrade. A file named dbManager_<timestamp>_.log is created after a few minutes in INSTALL_PATH/SYMCOpsCenterServer/db/log directory. You can view this file to check the database upgrade status.

17 All the OpsCenter processes are started. The following information is also
displayed:

Installing Symantec OpsCenter 7.1 Clustering Symantec OpsCenter

257

■ ■

Web URL to access OpsCenter console Location of install log and summary files.

18 After upgrading the active node to OpsCenter 7.1, install OpsCenter 7.1
software on all the passive nodes. Repeat steps 8 through 18 for all passive nodes.

19 After upgrading OpsCenter server on all nodes, run the following command
to start the NetBackupOpsCenter cluster agent on each node.
haagent -start NetBackupOpsCenter -force -sys <node>

20 Unfreeze the OpsCenter VCS group by using the following command:
hagrp -unfreeze <OpsCenter group name> -persistent sys <node>

Uninstalling OpsCenter Server completely from the Solaris cluster
Use the Uninstall Script, which resides in the root directory of the product DVD and also in /opt/VRTS/install directory, to uninstall OpsCenter completely from all the nodes on a Solaris host. To unistall OpsCenter Server completely from all the nodes

1 2

Open a Solaris cluster and log on as root. Offline OpsCenter group by following command from the active node:
hagrp -offline <OpsCenter group name> -sys node

3

Change to the following directory:
/opt/VRTS/install

4

Type the following command and press Enter:
./uninstallOpsCenterServer

The Uninstall script checks the components that are installed on the system.

5

When you are asked to confirm if you want to uninstall OpsCenter Server, do one of the following:

Type y. 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. Press Enter to cancel the uninstall procedure.

258

Installing Symantec OpsCenter 7.1 Clustering Symantec OpsCenter

6 7

Uninstall OpsCenter software from all the nodes. Repeat steps 3 through 5 for all nodes. Delete all resources by following command:
hagrp -delete <OpsCenter group name>

Chapter

3

Administering Symantec OpsCenter
This chapter includes the following topics:
■ ■ ■ ■ ■ ■ ■ ■

About OpsCenter services and processes used by OpsCenter OpsCenter server scripts on Windows and UNIX About OpsCenter database administration Configuring remote authentication service in OpsCenter About backup and restore of OpsCenter and OpsCenter Analytics About communication and firewall considerations Gathering troubleshooting data with the support script About OpsCenter log files

About OpsCenter services and processes used by OpsCenter
This section provides information about OpsCenter services and processes and how you can control these services. These topics assume you already installed OpsCenter on a server. If you have not installed OpsCenter, review the installation chapter. See “Services used by OpsCenter on Windows” on page 260. See “Controlling the OpsCenter services” on page 260. See “Processes used by OpsCenter on UNIX” on page 261.

260

Administering Symantec OpsCenter About OpsCenter services and processes used by OpsCenter

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

Symantec OpsCenter Agent java.exe Service

Symantec OpsCenter Server Service

java.exe

Symantec OpsCenter Database Server

dbsrv11.exe

Symantec OpsCenter Web java.exe server Service Symantec Private Branch Exchange pbx_exchange.exe

Symantec Product Authentication Service

vxatd.exe

Note: The processes that are listed in this table show the actual memory that is consumed by the respective OpsCenter service.

Controlling the OpsCenter services
Use the following procedure to verify if these services are running or not.

Administering Symantec OpsCenter About OpsCenter services and processes used by OpsCenter

261

To control these services

1 2 3

Use Start > Settings > Control Panel > Administrative Tools > Services. Check the Status column for each service. From the Status column, you can verify if a service is running or not. The Services panel can also be used to stop, start, and restart the OpsCenter services and Symantec shared services.

Processes used by OpsCenter on UNIX
After you install OpsCenter server and Agent on UNIX, the following processes should be active. Table 3-2 describes the processes that OpsCenter uses on UNIX. Table 3-2 Process Description
Symantec OpsCenter Agent

Processes used by OpsCenter on UNIX Detailed Description

Process

/opt/SYMCOpsCenterAgent/bin/.OpsCenterAgentd This process is for the Symantec OpsCenter Agent. By default, the OpsCenter Agent process starts whenever you boot your Agent host. /opt/SYMCOpsCenterServer/bin/.OpsCenterServerd The OpsCenter server interacts with the OpsCenter GUI and provides the data that the GUI requests from the OpsCenter database. It also interacts with NetBackup to get data regularly.

Symantec OpsCenter Server

Symantec /opt/SYMCOpsCenterServer/db/bin/OpsCenterDBd This process manages the OpsCenter OpsCenter Database databases. This process must be running Server on the OpsCenter server during all normal operations like viewing reports, running reports and so on. OpsCenter Database Server can fail to start in some scenarios. See “OpsCenter database service fails to start” on page 262. Symantec OpsCenter Web Server java This process is not an OpsCenter process. OpsCenter uses this process to host the OpsCenter Console. Many Symantec Web consoles share this component.

262

Administering Symantec OpsCenter About OpsCenter services and processes used by OpsCenter

Table 3-2 Process Description
Symantec Private Branch Exchange

Processes used by OpsCenter on UNIX (continued) Detailed Description
This process is not an OpsCenter process. but it is a component used by OpsCenter. PBX allows all socket communication to take place through a single port. This process is not an OpsCenter process. OpsCenter uses this process to authenticate users of OpsCenter.

Process
/opt/VRTSpbx/bin/pbx_exchange

Symantec Product Authentication Service

/opt/VRTSat/bin/vxatd

Note: The processes that are listed in this table show the actual memory consumed by the respective OpsCenter process.

OpsCenter database service fails to start
OpsCenter database service can fail to start on the AIX system in various scenarios. The service fails when the database size increases more than the file size mentioned. In a case where the database service fails to start, you get the following error message - Assertion failed: file system may be full or file size exceeded. You can check log details through - /opt/SYMCOpsCenterServer/db/log/dbserver.log. The problem can be overcome through a few checks, such as checking the ulimit size and size limit of the file system. To overcome database service failure

1

Check the ulimit size for the file system, enter the ulimit command -a and press Enter.Increase the file size. Note: The file size must be increased only if the database size is greater than the file system size. This information is displayed when you run the ulimit command -a. If the file size is not the maximum size that is supported by the file system, you must increase the file size to the maximum limit. To change file size, you must change the user-specific settings using SMIT or run the command edit /etc/security/limits.

2

Start the OpsCenter database after the changes are made.

See “Starting and stopping the OpsCenter database” on page 269.

Administering Symantec OpsCenter OpsCenter server scripts on Windows and UNIX

263

OpsCenter server scripts on Windows and UNIX
The following scripts are used within OpsCenter. The OpsCenter administrator may use many of these scripts. Use the -h option for help about these scripts. Table 3-3 lists the OpsCenter server scripts on Windows. Table 3-3 Script
startserver.bat and stopserver.bat dbbackup.bat 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

OpsCenter server scripts on Windows Function Invokes or Is Invoked by
Administrator

Location

INSTALL_PATH\OpsCenter\server\bin Starts or stops the OpsCenterServerd.

startdb.bat and stopdb.bat opsadmin.bat

OpsCenter Administrator

OpsCenter Administrator

dbdefrag.bat

INSTALL_PATH\OpsCenter\server\bin Defragments the OpsCenter OpsCenter Administrator database OpsCenter Administrator

changedbpassword.bat INSTALL_PATH\OpsCenter\server\bin Changes the OpsCenter database password runStoredQuery.bat

INSTALL_PATH\OpsCenter\server\bin Runs saved custom SQL and OpsCenter Administrator generates output in the desired format.

Table 3-4 lists the OpsCenter server scripts on UNIX. Table 3-4 Script Location OpsCenter server scripts on UNIX Function Invokes or Is Invoked by
OpsCenter Server

startserver and stopserver

/opt/SYMCOpsCenterServer/bin Starts or stops the OpsCenterServerd.

264

Administering Symantec OpsCenter OpsCenter server scripts on Windows and UNIX

Table 3-4 Script
startdb and stopdb

OpsCenter server scripts on UNIX (continued) Function Invokes or Is Invoked by

Location

/opt/SYMCOpsCenterServer/bin Starts or stops the OpsCenter OpsCenter Administrator database /opt/SYMCOpsCenterServer/bin Starts, stops, and monitors all OpsCenter Server processes Solaris: /etc/init.d OpsCenter Administrator

opsadmin.sh

OpsCenterServer

This script is used internally OpsCenter for clustering. The script Server starts, stops, or restarts the OpsCenter database, OpsCenter Server, and OpsCenter Web server (Tomcat). OpsCenter Administrator

dbbackup.sh

< I N S T A L L _ P A T H > / S Y M C O p s C e n t e r S e r v e r / b i n Backs up the OpsCenter database < I N S T A L L _ P A T H > / S Y M C O p s C e n t e r S e r v e r Defragments the OpsCenter database < I N S T A L L _ P A T H > / S Y M C O p s C e n t e r S e r v e r Changes the OpsCenter database password

dbdefrag

OpsCenter Administrator

changeDbPassword.sh

OpsCenter Administrator

runStoredQuery.sh

< I N S T A L L _ P A T H > / S Y M C O p s C e n t e r S e r v e r Runs saved custom SQL and OpsCenter Administrator generates output in the desired format.

Commands to control OpsCenter services and processes
This section provides information on how you can control the OpsCenter server services and OpsCenter Agent service. Table 3-5 Service
All Symantec OpsCenter server services

Start and stop commands on Windows Commands or Steps
To start all Symantec OpsCenter server services: INSTALL_PATH\OpsCenter\server\bin\opsadmin.bat start To stop all Symantec OpsCenter server services: INSTALL_PATH\OpsCenter\server\bin\opsadmin.bat stop

Administering Symantec OpsCenter OpsCenter server scripts on Windows and UNIX

265

Table 3-5 Service

Start and stop commands on Windows (continued) Commands or Steps
Select Control Panel > Administrative Tools > Services and start or stop the Symantec OpsCenter Database Server service.

Symantec OpsCenter database server service

Symantec OpsCenter Server Select Control Panel > Administrative Tools > Services Service and start or stop the Symantec OpsCenter Server Service. Symantec OpsCenter Web server Service Select Control Panel > Administrative Tools > Services and start or stop the Symantec OpsCenter Web Server Service. Select Control Panel > Administrative Tools > Services and start or stop the Symantec OpsCenter Agent Service.

Symantec OpsCenter Agent Service

Table 3-6 Process

Start and stop commands on UNIX Commands or Steps
To start all Symantec OpsCenter server processes: /opt/SYMCOpsCenterServer/bin/opsadmin.sh start To stop all Symantec OpsCenter server processes: /opt/SYMCOpsCenterServer/bin/opsadmin.sh stop To monitor all processes: /opt/SYMCOpsCenterServer/bin/opsadmin.sh monitor

All Symantec OpsCenter server processes

Symantec OpsCenter database server process

/opt/SYMCOpsCenterServer/bin/startdb /opt/SYMCOpsCenterServer/bin/stopdb

Symantec OpsCenter server /opt/SYMCOpsCenterServer/bin/startserver process /opt/SYMCOpsCenterServer/bin/stopserver

Symantec OpsCenter Web server process

/opt/SYMCOpsCenterGUI/bin/startgui.sh /opt/SYMCOpsCenterGUI/bin/stopgui.sh

266

Administering Symantec OpsCenter OpsCenter server scripts on Windows and UNIX

Table 3-6 Process

Start and stop commands on UNIX (continued) Commands or Steps
/opt/SYMCOpsCenterAgent/bin/startagent /opt/SYMCOpsCenterAgent/bin/stopagent

Symantec OpsCenter Agent process

About dependency of services
The Symantec OpsCenter server service requires that the following OpsCenter services (processes) are running:
■ ■ ■

Symantec OpsCenter Database Server Symantec Product Authentication Service Symantec Private Branch Exchange

If you stop any of these services, then the OpsCenter server also stops. Note: After a reboot, the OpsCenter processes do not start automatically on SUSE Linux systems. Symantec recommends that you start the OpsCenter processes after you perform a reboot. Also after you reboot a SUSE 11 Server, and even though OpsCenter Server services are running, an attempt to logon may not succeed. Occasionally, OpsCenter services may not start on reboot in case of SUSE 11. This issue may happen because of the PBX taking time to start.

About nbproxy processes on NetBackup master servers
When OpsCenter is connected to a master server, you may find one or more nbproxy processes running on the master server. You may also see nbproxy processes when NetBackup-Java GUI or NetBackup-Windows GUI request certain data from NetBackup (like LiveUpdate , storage lifecycle policies). Most of the nbproxy processes are started, managed, and removed by NBSL. This section talks about the nbproxy processes that NBSL manages. Note: Not all nbproxy processes on the master server are managed by NBSL. For example, some of the nbproxy processes are managed by nbjm and nbpem. An nbproxy process runs to retrieve the following NetBackup data for OpsCenter:

Administering Symantec OpsCenter About OpsCenter database administration

267

■ ■ ■ ■ ■

Policies Catalogs Storage lifecycle policies LiveUpdate Client details

Note the following points about the NBSL-managed nbproxy processes:

If the data collection for a master server is disabled or a master server is removed from the OpsCenter console, all nbproxy processes are stopped immediately. If OpsCenter crashes (or is abruptly closed), the nbproxy process is removed within an hour. If NetBackup is stopped (and NBSL is already killed), all nbproxy processes are stopped immediately. If NBSL crashes (or is abruptly closed), all nbproxy processes exit within 10 minutes.

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

OpsCenter database commands
OpsCenter provides some useful commands to help manage the OpsCenter database. In addition, a utility called changeVxATProperties has been included that lets you change the authentication server parameters. Table 3-7 lists some of the commands that are available. Table 3-7 Command
changeDbPassword

Commands available with OpsCenter Reference
See “Changing the OpsCenter database administrator password” on page 268.

268

Administering Symantec OpsCenter About OpsCenter database administration

Table 3-7 Command

Commands available with OpsCenter (continued) Reference
See “Starting and stopping the OpsCenter database” on page 269. See “About OpsCenter database defragmentation” on page 270. See “Backing up the OpsCenter database” on page 279. See “Restoring the OpsCenter database” on page 282.

startdb and stopdb

dbdefrag

dbbackup

changeVxATProperties

See “Configuring authentication server parameters” on page 272.

Note: For a clustered OpsCenter server, you must run commands on the active node.See “About running commands on the active node” on page 234.

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

Exceed 30 characters. Contain consecutive black slash characters. Contain any bracket [ ] characters.

Administering Symantec OpsCenter About OpsCenter database administration

269

Contain any of the following characters. These characters have special meaning in Windows or in shell scripts. ‘ ! $ % & . ; ^ | < > , { } $ " ~ [ ] \\ Contains the ASCII characters that are less than 32 or ASCII characters that are greater than 127. Begin with White space and a single quote character. End with White space.

■ ■

Note: Information about role-based access in Symantec OpsCenter is available. See “User access rights and UI functions in OpsCenter” on page 322. To change the database administrator password on Windows and UNIX

1

Enter the following command on Windows:
INSTALL_PATH\OpsCenter\server\bin\changeDbPassword.bat

Enter the following command on UNIX:
/opt/SYMCOpsCenterServer/bin/changeDbPassword.sh

2 3

You are prompted for the current database administrator password. Enter the current database password. You are prompted for a new database administrator password. Enter the new password.

Starting and stopping the OpsCenter database
The startdb script is used to start the OpsCenter database. The stopdb script is used to stop the OpsCenter database. To start the database server on Windows and UNIX

To start the OpsCenter database on Windows, run the following command:
INSTALL_PATH\OpsCenter\server\bin\startdb.bat

To start the OpsCenter database on UNIX, run the following command:
/opt/SYMCOpsCenterServer/bin/startdb

270

Administering Symantec OpsCenter About OpsCenter database administration

To stop the database server on Windows and UNIX

To stop the OpsCenter database on Windows, run the following command:
INSTALL_PATH\OpsCenter\server\bin\stopdb.bat

To stop the OpsCenter database on UNIX, run the following command:
/opt/SYMCOpsCenterServer/bin/stopdb

About OpsCenter database defragmentation
Fragmentation occurs naturally as you make changes to your database. Such changes may occur due to the deletion of data from the OpsCenter database. Some examples when data is deleted from the OpsCenter database are the following:

When data purging is enabled in OpsCenter. The purge settings can be viewed by clicking Settings > Configuration > Data Purge in the OpsCenter console. Data purging in OpsCenter is enabled by default. When you delete a master server from OpsCenter.

Symantec recommends that you should defragment the OpsCenter database once in a month. In addition, you should defragment the OpsCenter database if the disk fragment count in the server.log file on Windows or dbserver.log file on UNIX shows a large number. The following section describes how you can find the disk fragment count. See “Checking the disk fragment count” on page 270. See “Configuring authentication server parameters” on page 272.

Checking the disk fragment count
Use the following procedure to check the disk fragment count in the server.log file on Windows or dbserver.log file on UNIX.

See “Backing up the OpsCenter database” on page 279. Defragmenting the OpsCenter database You can defragment the OpsCenter database using the dbdefrag command.log. For optimum performance.db" consists Note: You may not find any results when you search for fragment. you may find the following line: Performance warning: Database file "G:\OpsCenter\db\vxpmdb. l o g /opt/SYMCOpsCenterServer/db/log/dbserver.bat To defragment the OpsCenter database on UNIX. run the following command: INSTALL_PATH\OpsCenter\server\bin\dbdefrag.log 2 Search for the word fragment in the file.sh . For example.log or dbserver.Administering Symantec OpsCenter About OpsCenter database administration 271 To check the disk fragment count 1 Open the following files on Windows and UNIX respectively: Windows UNIX I N S T A L L _ P A T H \ S y m a n t e c \ O p s C e n t e r \ s e r v e r \ d b \ l o g \ s e r v e r . 2 To defragment the OpsCenter database on Windows. Note: OpsCenter does not work during the time when the OpsCenter database is defragmented. To defragment the OpsCenter database on Windows and UNIX 1 Before you defragment the OpsCenter database. when you search for fragment in server. run the following command: /opt/SYMCOpsCenterServer/bin/dbdefrag. This result is completely fine. You may see such performance warnings when the disk fragment count is high. Defragmentation helps to increase data access and retrieval speed. Symantec recommends that you back up the OpsCenter database. defragment the OpsCenter databases once in a month and after a purge operation.

You can specify a custom location (non-default location) for the OpsCenter database during OpsCenter installation. OpsCenter database files and the log files that are associated with the OpsCenter database should be stored on separate hard disks. The current values of the parameters are specified in brackets. Symantec also recommends that you not store the database files on the hard disk that contains your operating system files. You must restart the OpsCenter services for these changes to be effective.sh The authentication server parameters appear one by one. The default location for the OpsCenter database can also be changed after OpsCenter has been installed. 2 3 Enter the new values next to the respective parameter. This procedure is not applicable when Symantec Product Authentication Service is installed on the local computer. the value of the parameter does not change. You can store the OpsCenter database files on one hard disk and the log files on another hard disk. To configure authentication server parameters 1 Enter the following command on Windows: INSTALL_PATH\OpsCenter\server\bin\changeVxATProperties. The first two procedures are for moving the OpsCenter database files on Windows or UNIX. Answer y to restart the OpsCenter services. Use the following procedures to move the OpsCenter database and log files to a different hard disk. . Moving the OpsCenter database and database logs to a different hard disk To improve OpsCenter performance. Note: This procedure is applicable only for OpsCenter clusters where the authentication broker is remote.272 Administering Symantec OpsCenter About OpsCenter database administration Configuring authentication server parameters The authentication server parameters can be configured using the changeVxATProperties utility. If you do not enter a new value for a parameter.bat Enter the following command on UNIX: /opt/SYMCOpsCenterServer/bin/changeVxATProperties. The last two procedures are for moving the database log files.

you can delete vxpmdb. !. enter the following command: INSTALL_PATH\OpsCenter\server\bin\opsadmin. . Copy vxpmdb. ~. replace the contents of the file with the following: "E:\Database\vxpmdb.db and symcOpscache. 3 To move the database to a custom location like E:\Database. &.Administering Symantec OpsCenter About OpsCenter database administration 273 To move the OpsCenter database to a different hard disk on Windows 1 Stop all OpsCenter services.db from INSTALL_PATH\OpsCenter\server\db\data to a location like E:\Database.bat stop 2 Open the databases.conf file with a text editor like notepad from the following directory: INSTALL_PATH\OpsCenter\server\db\conf This file has the following contents: "INSTALL_PATH\OpsCenter\server\db\data\vxpmdb. Restart all OpsCenter server services. ^. If OpsCenter works as expected. Also the directories in the specified path should not contain any special characters like %. # etc.db" This path specifies the default location of the OpsCenter database. Save the databases.db" Make sure that you specify the path in double quotes.db and symcOpscache. @. To restart all OpsCenter services.bat start 5 You should run and monitor OpsCenter for a certain period after moving the database.conf file. Enter the following command: INSTALL_PATH\OpsCenter\server\bin\opsadmin. 4 Copy the database files to the new location. For example. $. do not specify a path like E:\Database%.db from the default location (INSTALL_PATH\OpsCenter\server\db\data).

. first create the new directory by entering the following command: mkdir -p /usr/mydata 4 To move the database to a custom location like /usr/mydata. Back up the OpsCenter database (/opt/SYMCOpsCenterServer/db/data) to some other location.db from /backup/data. Enter the following command: unlink /opt/SYMCOpsCenterServer/db/data 6 Create a symbolic link to /usr/mydata in /opt/SYMCOpsCenterServer/db/data. enter the following command: mv /opt/SYMCOpsCenterServer/db/data/* /usr/mydata 5 Remove the symbolic link that exists for the OpsCenter database. Enter the following command: /opt/SYMCOpsCenterServer/bin/opsadmin. To create a symbolic link.sh stop 2 The default location of the OpsCenter database is /opt/SYMCOpsCenterServer/db/data. If OpsCenter works as expected.db and symcOpscache. you can delete vxpmdb. enter the following command: ln -s /opt/SYMCOpsCenterServer/db/data /usr/mydata 7 Restart all OpsCenter server processes by entering the following command: /opt/SYMCOpsCenterServer/bin/opsadmin. Enter the following command: cp –R /opt/SYMCOpsCenterServer/db/data /backup/data 3 To move the database to a custom location like /usr/mydata.sh start You should run and monitor OpsCenter for a certain period after moving the database.274 Administering Symantec OpsCenter About OpsCenter database administration To move the OpsCenter database to a different hard disk on UNIX 1 Stop all OpsCenter server processes.

Administering Symantec OpsCenter About OpsCenter database administration 275 To move the database log files to a different hard disk on Windows 1 Stop all OpsCenter server services. Enter the following command: /opt/SYMCOpsCenterServer/bin/opsadmin.log database_path\vxpmdb. enter the following command: INSTALL_PATH\OpsCenter\server\bin\opsadmin.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.bat stop 2 Navigate to the following location for 32-bit and 64-bit systems respectively: INSTALL_PATH\OpsCenter\server\db\WIN32 INSTALL_PATH\OpsCenter\server\db\WIN64 Enter the following commands: dblog -t directory_path\vxpmdb. It is recommended to use vxpmdb. Enter the following command: INSTALL_PATH\OpsCenter\server\bin\opsadmin.log as the name of the log file.bat start To move the database log files to a different hard disk on UNIX 1 Stop all OpsCenter server processes. To restart all OpsCenter services. This command moves the log file that is associated with the OpsCenter database to the new directory (directory_path).sh stop 2 Set the path of the LD_LIBRARY_PATH variable in the following manner: LD_LIBRARY_PATH=/opt/SYMCOpsCenterServer/db/lib:$LD_LIBRARY_PATH export LD_LIBRARY_PATH . 3 Restart all OpsCenter server services.

log as the name of the log file.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. you install the authentication server component on a remote computer in the network. See “About OpsCenter log files on UNIX servers” on page 298. 4 Restart all OpsCenter server processes by entering the following command: /opt/SYMCOpsCenterServer/bin/opsadmin. Use the following procedure to configure remote AT with OpsCenter.log database_path/vxpmdb. This command moves the log file that is associated with the OpsCenter database to the new directory (directory_path). When you are using the Symantec Product Authentication Service remotely./dblog -t directory_path/vxpmdb. you can configure the remote AT after upgrading to OpsCenter. . See “About OpsCenter log files on Windows servers” on page 296. Configuring remote authentication service in OpsCenter OpsCenter supports using Symantec Product Authentication Service (AT) remotely. It is recommended to use vxpmdb. See “About OpsCenter Web GUI/OpsCenter server to Sybase database communication” on page 290. Information about the log files on Windows and UNIX servers is available.276 Administering Symantec OpsCenter Configuring remote authentication service in OpsCenter 3 Navigate to the following location: /opt/SYMCOpsCenterServer/db/bin Enter the following commands: .sh start About database troubleshooting Security information about the OpsCenter database is available. If you were using a remote AT configuration in NOM and upgrade to OpsCenter.

.Administering Symantec OpsCenter Configuring remote authentication service in OpsCenter 277 To configure remote authentication service in OpsCenter 1 Enter the following command for Windows and UNIX platforms respectively: Windows UNIX INSTALL_PATH\OpsCenter\server\bin\changeVxATProperties. Authentication Service Port Number The port number of the server on which the authentication service server component is running. The default value is Vxadmin. The default value is admin. The default value is broker. The following authentication service parameters are displayed: Authentication Service Host Name The fully qualified host name (FQHN) of the server on which the authentication service server component is running. The default value is localhost if the authentication service is installed on the OpsCenter server. The default value is 2821. Authentication Service Password The password of the broker that the user used for initial authentication. The current values of the parameters are specified in brackets.sh 2 The authentication server parameters appear one by one. Authentication Service Domain Name The domain name of the broker.bat /opt/SYMCOpsCenterServer/bin/changeVxATProperties. Authentication Service User Name The name of the broker that the user used for initial authentication.

Answer y to restart the OpsCenter services. Authentication Service Port Number Authentication Service Domain Name Authentication Service User Name Authentication Service Password 4 You must restart the OpsCenter services for these changes to be effective. the value of the parameter does not change. Enter the port number of the remote server on which the authentication service server component is running. Authentication Service Host Name Enter the FQHN of the remote server on which the authentication service server component is running. enter the new values next to the respective parameter. Backing up OpsCenter in case of a disaster The sequence of steps gives an overview about the steps that need to be followed to back up OpsCenter. Enter the password of the broker that the user used for initial authentication. If you do not enter a new value for a parameter. Enter the name of the broker that the user used for initial authentication. . See “Restoring OpsCenter” on page 281. See “Backing up OpsCenter in case of a disaster” on page 278. Enter the domain name of the broker.278 Administering Symantec OpsCenter About backup and restore of OpsCenter and OpsCenter Analytics 3 To use a remote AT configuration. 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.

See the NetBackup Administrator’s Guide. The database files are as follows: vxpmdb. the user information that Symantec Product Authentication Service manages must be saved in a directory or by using a NetBackup backup policy.db. On UNIX as well as Windows platforms. You must schedule periodic hot backups for the OpsCenter database to avoid losing any important data.log. In this case. Note: Regular file system backups are not sufficient for backing up the OpsCenter database. symcOpscache. See “Backing up the OpsCenter database” on page 279. and vxpmdb. which is referred to as hot backup. 2 Along with the OpsCenter database. Note: You can also create schedules for taking regular database and authentication profile backups.db. NetBackup policies can be created to back up the specified directories that contain OpsCenter database snapshots and the authentication service user configuration files. the script overwrites existing database (db) files before backing up or restoring the database. you also need to back up the database password file. This script can be run whenever you need to back up your OpsCenter database.log file (if it exists).db) using the dbbackup script. See “Saving the OpsCenter user profiles managed by Symantec Product Authentication Service” on page 280.db and symcOpscache. 3 If you want to change the OpsCenter database password. The script backs up or restores the vxpmdb. Backing up the OpsCenter database OpsCenter is shipped with a database backup script that performs backup of the database without interrupting its operations. symcOpscache. and vxpmdb.Administering Symantec OpsCenter About backup and restore of OpsCenter and OpsCenter Analytics 279 To back up OpsCenter in case of a disaster 1 Take a hot backup of the OpsCenter database (vxpmdb.db.db. . Volume I for more information on how to configure a policy and schedule.

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. Saving the OpsCenter user profiles managed by Symantec Product Authentication Service Use the following procedures to save the authentication service profiles on Windows and UNIX servers. To save authentication service profiles on Windows servers ◆ Do one of the following to save the user profiles: ■ Copy the folder INSTALL_PATH\VERITAS\Security\Authentication\systemprofile to another folder. Run the backup script that is appropriate for your platform. Create a NetBackup job policy to back up the authentication service profile folder.sh /my_db_backup_dir UNIX The backup script creates vxpmdb. and vxpmdb. Specify one of the following backup directories depending on your platform: Windows INSTALL_PATH\OpsCenter\server\bin\dbbackup.280 Administering Symantec OpsCenter About backup and restore of OpsCenter and OpsCenter Analytics To back up the OpsCenter database 1 Log on to the OpsCenter database server host in one of the following ways: 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 systemprofile folder.db. .log (if it exists) in the backup directory that you specified. symcOpscache.db.bat C:\MyDbBackupFolder /opt/SYMCOpsCenterServer/bin/dbbackup.

This involves adding the OpsCenter hostname to the Server List of the NetBackup master servers. To restore OpsCenter in case of a disaster 1 2 Install OpsCenter on a server with the same name as the server where problems happened. To back up the OpsCenter database password file on UNIX ◆ Back up the db. Some of the reasons are the following: ■ The authentication service credentials (host name and IP address) are stored on the old OpsCenter server. To back up the OpsCenter database password file on Windows ◆ Back up the db. The sequence of steps gives an overview about the steps that need to be followed to restore OpsCenter. you need to back up the following password file (along with the backup of the OpsCenter database files and authentication service profile folders).conf file that is located in INSTALL_PATH/OpsCenter/server/config directory. ■ Note: The following procedures assume that you have OpsCenter database snapshots and the authentication service user profiles saved in folders. you must add the master servers to the OpsCenter console. . To enable data collection. See “Adding a master server in OpsCenter” on page 377.Administering Symantec OpsCenter About backup and restore of OpsCenter and OpsCenter Analytics 281 Backing up the OpsCenter database password file If you want to change the OpsCenter database password. This limitation is due to a couple of reasons. Stop all OpsCenter server services. 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. you must configure the master servers for data collection.conf file that is located in /opt/SYMCOpsCenterServer/config directory. Atter this.

282 Administering Symantec OpsCenter About backup and restore of OpsCenter and OpsCenter Analytics 3 Restore the OpsCenter database snapshot files and authentication service user profiles from the backup image. and vxpmdb. symcOpscache. 5 Restoring the OpsCenter database After you back up the database. copy the file to the corresponding location on the newly installed OpsCenter server. symcOpscache. restores the backup database files.db. The script backs up or restores the vxpmdb. See “Restoring the OpsCenter database” on page 282. and restarts the database. Copy the db. On Windows and UNIX hosts. The database files are as follows: vxpmdb. The dbbackup script overwrites existing database (db) files before backing up or restoring the database.log file (if it exists). . See “Restoring the OpsCenter user profiles managed by Symantec Product Authentication Service” on page 284.db.log.db. and vxpmdb. Restart all OpsCenter server services.conf file to INSTALL_PATH/OpsCenter/server/config directory on Windows or /opt/SYMCOpsCenterServer/config directory on UNIX. you can restore it. 4 If you saved a copy of the OpsCenter database password file. the restore operation automatically stops the database.db.

Administering Symantec OpsCenter About backup and restore of OpsCenter and OpsCenter Analytics 283 To restore a backed up OpsCenter database 1 On the OpsCenter server with backup data you want to restore. 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.bat <backupDir> -restore <restoreDir> UNIX Type the following command and press Enter. /opt/SYMCOpsCenterServer/bin/dbbackup. If not used. restoreDir is optional. UNIX All the paths that are shown in the steps that follow are the default database install paths. do one of the following: Windows Type the following command and press Enter. and <restoreDir> is the location of the current OpsCenter database. These paths may different for your site if the database was installed anywhere other than the default location. 2 To restore the backed up database. Windows Open a Windows command prompt and log on as an administrator or user in the Administrators group. you must specify the restoreDir option. Open a UNIX console and then log on as root. INSTALL_PATH\OpsCenter\server\bin\dbbackup.sh <backupDir> -restore <restoreDir> where backupDir is the directory where the backed up database resides. 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). Do you wish to continue ? [y/n] (n) . The script prompts you with a message similar to the following: WARNING: this operation will overwrite the active OpsCenter data on this host.

sh stop 2 3 Copy or overwrite the folder containing the authentication service user profiles to /var/VRTSat Start all OpsCenter server processes. type y on UNIX hosts.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. press Enter on Windows hosts. Enter the following command: INSTALL_PATH\OpsCenter\server\bin\opsadmin.284 Administering Symantec OpsCenter About communication and firewall considerations 3 To continue with the restore. Start all OpsCenter server services. Enter the following command: /opt/SYMCOpsCenterServer/bin/opsadmin. The dbbackup script automatically stops and restarts the database. Enter the following command: /opt/SYMCOpsCenterServer/bin/opsadmin. Restoring the OpsCenter user profiles managed by Symantec Product Authentication Service Use the following procedures to save the authentication service profiles on Windows and UNIX servers. To restore the authentication user profiles on Windows 1 Stop all OpsCenter server services.bat start To restore the authentication user profiles on UNIX 1 Stop all OpsCenter server processes. To continue with the restore.sh start About communication and firewall considerations Figure 3-1 shows the key OpsCenter components and the communication ports that are used. .

Administering Symantec OpsCenter About communication and firewall considerations 285 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 . Communication ports used by key OpsCenter components The following table shows the default port settings for OpsCenter. Port 8282 and Port 8553. are installed NetBackup Master Server without NBAC Possible Firewall Hosts where backup products like Backup Exec. PureDisk etc.are installed OpsCenter Agent See “Communication ports used by key OpsCenter components” on page 285. View Builder Console Web Browser Possible Firewall OpsCenter Web GUI Default Port 13786 OpsCenter Database PBX default port 1556 Possible Firewall OpsCenter Server SMTP email SNMP traps Port 162 Possible Firewall NetBackup Master Server with NBAC Hosts where backup products like Backup Exec. Port 8181 and Port 8443. .Port 80 and Port 443. PureDisk etc.. and.

NetBackup Master Server(s) 1556 Allow between source and destination (bi-directional). If these ports are changed then the appropriate hardware ports have to be opened. See “About OpsCenter Web GUI to OpsCenter server software communication” on page 289. See “About OpsCenter Web GUI to OpsCenter server software communication” on page 289. PBX port number configuration is supported. Table 3-8 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. Some hardened servers and firewall configurations may block this port.286 Administering Symantec OpsCenter About communication and firewall considerations SMTP recipient ports can be configured from the OpsCenter console (using Settings > Configuration > SMTP Server). OpsCenter Client OpsCenter Server 1556 PBX (pbx_exchange) Allow between source and destination. The SNMP trap recipient ports can also be configured from the OpsCenter console (using Settings > Recipients > SNMP). Table 3-8 lists the communication ports that are used by key OpsCenter components. PBX port number configuration is not supported. . Destination Port Number Host Mail server 25 SNMP Server 162 SNMP trap recipient PBX (pbx_exchange) Allow from source to destination.

Backup Exec. . Table 3-9 lists the ports that must be opened on OpsCenter Agent to collect data from various backup products. PureDisk. 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. Symantec Allow between source and destination in case Product NBAC is enabled on NetBackup master server. (dbsrv11) Some hardened servers and firewall configurations may block this port. TSM etc. Authentication Service (vxatd) 2 3 OpsCenter Server OpsCenter Server 13786 OpsCenter Server Host where 2821 Symantec Product Authentication Service (AT) Server is installed 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.Administering Symantec OpsCenter About communication and firewall considerations 287 Table 3-8 Communication ports used by key OpsCenter components (continued) Usage (Process Port Configuration Name) Allow from all hosts on network.

.exe bpimagelist.exe bpretlevel.288 Administering Symantec OpsCenter About communication and firewall considerations Table 3-9 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. 13782 port should be used to connect to the NetBackup master server and 13724 port should be used to respond to the Agent host. The response is sent on a port in the reserved port range 512-1023 if not configured to use vnetd The following processes are used for NetBackup data collection: ■ ■ ■ Port number 13782 & 13724 bperror.exe 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 OpsCenter (EMC data collector) communicates with EMC Server locally 1500 TSM EMC NetWorker A local host communication 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. For HTTP. These protocols use TCP/IP.

These HTTP and HTTPS ports are opened only for input and are configurable using the command lines.Administering Symantec OpsCenter About communication and firewall considerations 289 Table 3-10 lists how the default HTTP and HTTPS ports are selected. port 8181 is used as the default HTTP port and port 8443 is used as the default HTTPS port. 8282 8553 Port 8282 and Port 8553 are checked for availability. 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. ■ In case. port 80 is used as the default HTTP port and port 443 is used as the default HTTPS port. Default HTTP and HTTPS ports HTTPS port number 443 HTTP port number 80 Description Port 80 and Port 443 are checked for availability. 1. Table 3-10 Sr. ■ 2. . The PBX port is opened for input and output traffic. No. If port 80 and port 443 are available. then the next port combination is checked for availability. See configurePorts on page 745. ■ 3. If port 8181and port 8443 are available. some other application like a Web server uses one or both ports. then the next port combination is checked for availability. The default port is 1556. 8181 8443 Port 8181 and Port 8443 are checked for availability. ■ In case another application like VRTSWeb installed with VCS or any other product uses one or both ports.

the OpsCenter server software listens to the notifications that are sent by NBSL for any change in NetBackup data. The database is available only to resident OpsCenter components on the OpsCenter server. See “Adding a master server in OpsCenter” on page 377.290 Administering Symantec OpsCenter About communication and firewall considerations About OpsCenter server to NetBackup master server (NBSL) communication OpsCenter requires the NetBackup Service Layer (NBSL) to be present on all managed master servers. Symantec Private Branch Exchange (PBX) is used for communication and requires a port opened on the OpsCenter server and the NetBackup master server for input and output. The default PBX port that is used is 1556. About SNMP traps SNMP trap protocol is used for outbound UDP traffic and requires a port that opens for output. The Sybase database server port is closed to all inbound connections. 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 port number is 162. As soon as the initial data load is complete. The initial data load happens serially for each data type. Then OpsCenter updates the OpsCenter database. when data collection for a master server is enabled or when a master server is added to OpsCenter. If you change the PBX port on the NetBackup master server. the OpsCenter server starts collecting all the available data from NetBackup master server into the OpsCenter database using NBSL. you can configure the same in OpsCenter while adding or editing a master server. About OpsCenter Web GUI to OpsCenter server email communication SMTP email server protocol is used for outgoing mail. The port number is defined when the user specifies the SMTP server port (see Settings > Configuration > . 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.

Administering Symantec OpsCenter Gathering troubleshooting data with the support script 291 SMTP Server in the OpsCenter console to specify this port). The port is opened for output only. collects information about any data collection problems. captures the current Agent configuration. Gathering troubleshooting data with the support script If you are running OpsCenter on UNIX or Windows. To gather troubleshooting data for OpsCenter Server on Windows 1 Run the following command to execute the support script for OpsCenter Server: INSTALL_PATH\OpsCenter\server\bin\opsCenterSupport. do you want to collect installation logs Answer y or n based on your preferences. do you want to collect old database and If this is an install scenario. and compresses the results into a zip file. 2 The script then prompts the following questions: Do you want to collect configuration files? [y/n] y Do you want to collect application log files? [y/n] y Do you want to collect OpsCenter GUI <147> log files? [y/n] y Do you want to collect OpsCenter Server <148> log files? [y/n] y Do you want to collect db log files? [y/n] y Do you want to collect WebServer log files? [y/n] y Do you want to collect setEnv file? [y/n] y Do you want to collect database files? [y/n] y If this is an upgrade scenario. The script collects Server and Agent logs. you can use the support script to gather troubleshooting information for OpsCenter Server and OpsCenter Agent. . This file can serve as a first-level information for the Support team in case of an issue with OpsCenter.bat Note: The following is the default directory location on Windows computers.

zip file. This zip file is stored in the following directory: INSTALL_PATH\OpsCenter\Agent\temp\support 4 After the Support.zip file is created. . It then compresses all this information in a file that is called Support. the script starts the OpsCenter Agent service. It then collates this information in a Support.zip file is stored in the following directory: INSTALL_PATH\OpsCenter\server\temp\support To gather troubleshooting data for OpsCenter Agent on Windows 1 Run the following command to execute the support script for OpsCenter Agent: INSTALL_PATH\OpsCenter\Agent\bin\opsCenterAgentSupport. 4 The Support.292 Administering Symantec OpsCenter Gathering troubleshooting data with the support script 3 This script collects system information and OpsCenter configuration information based on your preferences.zip. You can use OpsCenter and run the support script in the background.bat Note: The following is the default directory location on Windows computers. Note: Adding log files and OpsCenter database files can increase the file size of the resulting Support. 2 3 The script stops the OpsCenter Agent service and then collects the OpsCenter Agent logs.zip file.

3 This script collects system information and OpsCenter configuration information based on your preferences. Note: Adding log files and OpsCenter database files can increase the file size of the resulting support. 4 The support.zip.zip file is stored in the following directory: /opt/SYMCOpsCenterServer/temp/support . do you want to collect installation logs Answer y or n based on your preferences. You can use OpsCenter and run the support script in the background.Administering Symantec OpsCenter Gathering troubleshooting data with the support script 293 To gather troubleshooting data for the OpsCenter Server on UNIX 1 Run the following commands to execute the support scripts for OpsCenter Server: /opt/SYMCOpsCenterServer/bin/opsCenterSupport. do you want to collect old database and If this is an install scenario. It then collates all this information in a support.sh 2 The script then prompts the following questions: Do you want to collect configuration files? [y/n] y Do you want to collect application log files? [y/n] y Do you want to collect OpsCenter GUI <147> log files? [y/n] y Do you want to collect OpsCenter Server <148> log files? [y/n] y Do you want to collect db log files? [y/n] y Do you want to collect WebServer log files? [y/n] y Do you want to collect setEnv file? [y/n] y Do you want to collect database files? [y/n] y If this is an upgrade scenario.zip file.

Table 3-11 VxUL IDs used by OpsCenter components Originator name Symantec Private Branch Exchange service (PBX) NetBackup Service Layer (NBSL) VxUL originator ID 103 132 . About OpsCenter log files OpsCenter creates log files that you can use to troubleshoot installation. About VxUL log files The VxUL log file creates log file names and messages in a format that is standardized across all Symantec components. 2 3 The script stops the OpsCenter Agent process and then collects the OpsCenter Agent logs. and other issues. Table 3-11 shows the originator IDs used by OpsCenter and key shared components. legacy.zip file is stored in the following directory: /opt/SYMCOpsCenterAgent/temp/support 4 After the zip file is created.zip file. performance.sh Note: The following are the default directory locations on UNIX machines.294 Administering Symantec OpsCenter About OpsCenter log files To gather troubleshooting data for the OpsCenter Agent on UNIX 1 Run the following command to execute the support script for OpsCenter Agent: /opt/SYMCOpsCenterAgent/bin/opsCenterAgentSupport. The support. See “About OpsCenter log files on Windows servers” on page 296. OpsCenter components create most log messages in VxUL format. OpsCenter writes log files using Veritas Unified Logging (VxUL). the script automatically starts the OpsCenter Agent process. and other log file formats. These messages use VxUL IDs (a product ID and an originator ID) that identify the component that wrote the log message. See “About OpsCenter log files on UNIX servers” on page 298. It then collates this information in a support.

OpsCenter\server\logs) To configure the verbosity level (default 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. Table 3-12 Control Logging Control logging on Windows Command To change the log directory destination INSTALL_PATH\OpsCenter\server\bin\vxlogcfg. OpsCenter Agent.exe value is 1) -a -p 58330 -o <OID> -s DebugLevel=1 To configure the diagnostic level (default value is 1) To configure the number of log files that are created (default value is 100) INSTALL_PATH\OpsCenter\server\bin\vxlogcfg. OpsCenter Server OpsCenter Agent OpsCenter Web GUI 148 146 147 Table 3-12 lists the commands by which you can control logging on Windows.exe -a -p 58330 -o <OID> -s NumberOfLogFiles=100 . and OpsCenter Web GUI.Administering Symantec OpsCenter About OpsCenter log files 295 Table 3-11 VxUL IDs used by OpsCenter components (continued) Originator name Symantec OpsCenter Agent Symantec OpsCenter Web GUI Symantec OpsCenter Server VxUL originator ID 146 147 148 In Windows.exe (default value is -a -p 58330 -o <OID> -s LogDirectory="<New log directory location>" <INSTALL_PATH>\ Note: 58330 is the OpsCenter product ID. OpsCenter writes VxUL logs to the following directory: INSTALL_PATH\OpsCenter\server\logs In UNIX.exe -a -p 58330 -o <OID> -s DiagnosticLevel=1 INSTALL_PATH\OpsCenter\server\bin\vxlogcfg. and the OpsCenter Web GUI. The following OID values must be used for OpsCenter Server. OpsCenter Agent.

1 installation log files Table 3-14 shows details about the installation log files for OpsCenter components. Table 3-13 Control logging Control logging on UNIX Command To change the log directory destination /opt/SYMCOpsCenterServer/bin/vxlogcfg -a -p (default value is <INSTALL_PATH>/ 58330 -o <OID> -s LogDirectory="<New log SYMCOpsCenterServer/logs) directory location>" Note: 58330 is the OpsCenter product ID.html %ALLUSERSPROFILE%\\Symantec\OpsCenter\INSTALLLOGS \OpsCenterAgentInstallLog. These log files can be used to troubleshoot installation issues of the respective OpsCenter component.1 installation log files OpsCenter Log file component OpsCenter Server OpsCenter Agent OpsCenter View Builder %ALLUSERSPROFILE%\Symantec\OpsCenter\INSTALLLOGS \OpsCenterServerInstallLog. Table 3-14 OpsCenter 7.html . About OpsCenter 7.html %ALLUSERSPROFILE%\\Symantec\OpsCenter\INSTALLLOGS \OpsCenterViewBuilderInstallLog. To configure the debug level (default value is 1) To configure the diagnostic 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> /opt/SYMCOpsCenterServer/bin/vxlogcfg -a -p 58330 -o <OID> -s NumberOfLogFiles=<New number> To configure the number of log files that are created (default value is 100) About OpsCenter log files on Windows servers OpsCenter creates the following log files using VxUL and legacy formats.296 Administering Symantec OpsCenter About OpsCenter log files Table 3-13 lists the commands by which you can control logging on UNIX.

err and system. About log files associated with Symantec Product Authentication Service Table 3-16 lists the log files that are associated with Symantec Product Authentication Service. Table 3-16 Log file directory Log files for Symantec Product Authentication Service Log file Troubleshooting purpose Authentication activity. vxpmdb. Table 3-15 Log file directory INSTALL_PATH\ OpsCenter\server\ logs\ OpsCenter log files Log file Troubleshooting purpose ServerService_timestamp.log Note: Do not change this log file.log platforms: %ProgramFiles% vssconfig.Administering Symantec OpsCenter About OpsCenter log files 297 About OpsCenter log files Table 3-15 shows details about the OpsCenter log files. OpsCenter Sybase database transaction files.log Troubleshooting purpose OpsCenter Sybase database activity.log These log files for system.out of OpsCenter server service. Table 3-17 Log file directory INSTALL_PATH\ OpsCenter\server\db\log\ INSTALL_PATH\ OpsCenter\server\db\data\ Log files associated with the OpsCenter database Log file server. .log \Veritas\Security \Authentication\bin On 64-bit Windows platforms: %ProgramFiles(x86)% \Veritas\Security \Authentication\bin About OpsCenter database log files Table 3-17 lists the log files that are associated with the OpsCenter database. On 32-bit Windows vxatd.

NBSL activity.log logs\ INSTALL_PATH\OpsCenter\Agent\logs 51216-146-*.log /var/VRTS/install/logs/ (directory) Provides a trace for any installation issues. OpsCenter server activity. OpsCenter Web GUI activity. Table 3-19 Log files for OpsCenter Troubleshooting purpose stdout and stderr for the OpsCenterServer daemon.log INSTALL_PATH\VERITAS\NetBackup\ 51216-132-*.log /opt/SYMCOpsCenterServer/logs/ purge-status.log About OpsCenter log files on UNIX servers OpsCenter creates the following log files by using VxUL and legacy formats. Shows the details of purge operations.log Agent activity. OpsCenter log file /opt/SYMCOpsCenterServer/logs/ OpsCenterServer_out. INSTALL_PATH\OpsCenter\server\logs 58330-148*. About VxUL log files for OpsCenter and the components that OpsCenter uses Table 3-18 lists the log files that are associated with VxUL and other components that OpsCenter uses.log INSTALL_PATH\OpsCenter\gui\logs\ 51216-147-*. About log files associated with OpsCenter Table 3-19 lists the log files for OpsCenter.298 Administering Symantec OpsCenter About OpsCenter log files About OpsCenter Web server log files The log files that are associated with the OpsCenter Web server are present in the INSTALL_PATH\OpsCenter\gui\webserver\logs directory. Table 3-18 Log file directory Log files associated with VxUL and other components Log file Troubleshooting purpose PBX activity. . INSTALL_PATH\VERITAS\VxPBX\bin\ 50936-103-*.

OpsCenter log file /opt/VRTSpbx/log/50936-103-*. NBSL activity.log Log files for Symantec Product Authentication Service Troubleshooting purpose Authentication activity. About log files associated with VxUL and other components Table 3-23 lists the log files that are associated with VxUL and other components. About log files associated with OpsCenter Web server Table 3-22 lists the log files that are associated with the OpsCenter Web server. Table 3-22 Log files associated with the OpsCenter Web server Troubleshooting purpose OpsCenter log directory /opt/SYMCOpsCenterGUI/webserver/logs OpsCenter Web GUI application activity (stdout).Administering Symantec OpsCenter About OpsCenter log files 299 About log files for Symantec Product Authentication Service Table 3-20 lists the log files that are associated with Symantec Product Authentication Service. About log files associated with OpsCenter database Table 3-21 lists the log files that are associated with the OpsCenter database.log . Table 3-23 Log files associated with VxUL and other components Troubleshooting purpose PBX activity.log /opt/openv/logs/51216-132-*. vxpmdb. OpsCenter log file /opt/SYMCOpsCenterServer/db/log/ dbserver.log Note: Do not change this log file. Table 3-21 Log files associated with OpsCenter database Troubleshooting purpose OpsCenter Sybase database activity.log /opt/SYMCOpsCenterServer/db/data/ OpsCenter Sybase database transaction files. Table 3-20 Log file /var/VRTSat/vxatd.

log /opt/SYMCOpsCenterGUI/logs/ 51216-147-*. . OpsCenter server activity.300 Administering Symantec OpsCenter About OpsCenter log files Table 3-23 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/SYMCOpsCenterServer/logs/ 558330-148*.

Chapter 4 Understanding OpsCenter settings This chapter includes the following topics: ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ OpsCenter settings Setting user preferences About managing licenses Configuring the data purge period on the OpsCenter Server Configuring SMTP server settings for OpsCenter Configuring Symantec ThreatCon feature in OpsCenter Adding host aliases in OpsCenter Merging objects (hosts) in OpsCenter Modifying tape library information in OpsCenter Copying a user profile in OpsCenter Setting report export location in OpsCenter About managing Object Types in OpsCenter About managing Symantec OpsCenter users About managing recipients in OpsCenter About managing cost analysis and chargeback for OpsCenter Analytics .

The Symantec ThreatCon feature is used to show how secure or vulnerable your network is. See “ Adding OpsCenter license keys” on page 308.. See “Configuring Symantec ThreatCon feature in OpsCenter” on page 312. You can configure the following settings in OpsCenter. An OpsCenter Admin can configure these settings using the OpsCenter console.302 Understanding OpsCenter settings OpsCenter settings OpsCenter settings This topic describes the various OpsCenter settings. Create Agent and Data Collectors to collect data from non-NetBackup products. Reference topic User Preferences Add user-specific details and create user See “Setting user profiles. purge period on the OpsCenter Server” on page 309. Configure the SMTP server details that See “Configuring SMTP you need while sending reports or alerts server settings for through emails. OpsCenter” on page 311. in OpsCenter” on page 315. Data Purge SMTP Sever ThreatCon Host Alias Add aliases for hosts. collection for NetBackup” on page 361. Configure Symantec ThreatCon feature in OpsCenter. The normal users can view or access the information that is relevant only to their profiles. preferences” on page 304. See “About managing OpsCenter Agents” on page 353. Specify when you want to purge the data See “Configuring the data that is collected from various products. Agent License Manage permanent or demo license keys.. See “Adding host aliases in OpsCenter” on page 313. NetBackup Add NetBackup master servers and their See “About configuring data properties to collect data from it. Object Merger Configure OpsCenter to merge the objects See “Merging objects (hosts) that represent the same backup client. Table 4-1 Setting Settings in OpsCenter Lets you. which the OpsCenter Administrator has set. but registered as separate objects .

See “Estimating chargeback costs using the OpsCenter Formula Modeling Tool” on page 344. Currency Settings Manage the currency settings that appear See “Setting the default in cost reports. See “Settings > Chargeback > Cost Formulae options” on page 343. See “About managing Symantec OpsCenter users ” on page 321. You can select a currency currency for OpsCenter cost from the global currency list and set it as reports” on page 337. Copy User Profile Configure OpsCenter to copy a user's profile to another user. . Users Manage users and user groups. Cost Estimation Manage cost estimation. Recipients Manage Email and SNMP recipients.. Cost Variables Cost Formulae Create cost formulae. Object Type Views Create and manage OpsCenter views.. default. location in OpsCenter” on page 318. See “About managing Object Types in OpsCenter” on page 319. See “Copying a user profile in OpsCenter” on page 317. Create cost variables. See “About managing recipients in OpsCenter” on page 330. See “About managing OpsCenter views” on page 414. Add new object types and attributes. Report Export Location Specify the location where the exported See “Setting report export reports are stored. Modify tape library information Reference topic See “Merging objects (hosts) in OpsCenter” on page 315. See “Settings > Chargeback > Cost Variable options” on page 339.Understanding OpsCenter settings OpsCenter settings 303 Table 4-1 Setting Tape Library Settings in OpsCenter (continued) Lets you.

and Email Address. Select a preferred time zone . if your user account belongs to the OpsCenterUsers domain. The user preferences options are organized in the General and My Profile tabs.304 Understanding OpsCenter settings Setting user preferences Setting user preferences In OpsCenter. Data Display Time Zone Start 24 Hour Day at Disable Auto Refresh . Start 24 Hour Day at. all OpsCenter GUI screens use English as a default language. Settings > User Preferences options Use the General tab options as follows: Table 4-2 Option Default Locale General options Description Select a locale of your choice from the drop-down list. Password. In General details. Click the My Profile tab to see or modify User Name. Auto Refresh Interval (Minutes). you can set your preferences. you can type in name and contact information for this user. the auto-refresh option is enabled.either OpsCenter Server time zone or any other time zone from the Other drop-down list. Data Display Time Zone. User Role. You can also change your password using the User Preferences tab. Click Save. Disable Auto Refresh. such as default locale or time zone and personal details. OpsCenter displays time on the GUI screens according to the selected time zone. if you select English as a default locale. 3 4 5 Click Save. Report data is grouped depending on this start time. Enter the time that is used as the start time of a day in reports. To set user preferences 1 2 In the OpsCenter console. Domain Name. and Allow Multiple Selection in View Pane. Select this check box if you do not want to automatically refresh the OpsCenter GUI. Click the General tab to set Default Locale. By default. such as email ID or name. For example. click Settings > User Preferences.

you can only select a single node or view object from the View Pane at a given time. For example. you check the corresponding check boxes and then click Apply Selection. you can click a master server in the View Pane to view data for the specific master server. the Group Component Summary table displays job summary for each master server. if you want to refresh the OpsCenter GUI to show updated data after every 5 minutes. More details about the Group Component Summary table are available. See “About making multiple or single-click selections in the View pane” on page 63. enter five in the Auto Refresh Interval text box. Auto Refresh Interval (Minutes) Allow Multiple Selection in Select this check box if you want to select multiple nodes View Pane or view objects in the View Pane. You can click a node or a view object to view data for the respective node or view object. It shows the immediate NetBackup constituents of the selected view or node (group) in the View pane. a Group Component Summary table is displayed when you click Monitor > Jobs and select Summary View from the drop-down list. When you uncheck the multiple-selection option. See “About the Group Component Summary table” on page 445. For example if you select the ALL MASTER SERVERS view. By default. the multiple-selection option is enabled.Understanding OpsCenter settings Setting user preferences 305 Table 4-2 Option General options (continued) Description Enter auto-refresh interval in minutes. You can make selections in the View pane in a similar manner as NetBackup Operations Manager (NOM). you can see a check box next to each master server or node in the View Pane. Each node or a view object is a link. . When you uncheck the multiple-selection option. The Group Component Summary table at the bottom of the view displays job summary information. When you check this option. For example. The Group Component Summary table was also displayed in NOM earlier. To view data for multiple master servers and nodes.

Mobile Number.1. Work Number. click the Change Password link. To change password. The email address of this user. ■ PDF Tabular Report Export Layout Read and use the My Profile tab options as follows: Table 4-3 Option User Name Password My Profile options Description Displays the user name. you can export a tabular report in various PDF formats. The users from other domains cannot change their passwords using this option. The users that belong to the OpsCenterUsers domain can change their passwords after logging on . Cost Center. The OpsCenter security admin sets a default password for each user when it creates the profiles.306 Understanding OpsCenter settings Setting user preferences Table 4-2 Option General options (continued) Description With OpsCenter 7. Department. The name of the domain to which this user belongs. and Pager Number. Last Name. ■ Portrait for less than eight headers Displays data in the Portrait format for data up to seven headers and Landscape format for more than seven headers. User Role Domain Name Email Address General Details The role of this user. ■ Landscape Displays a maximum of ten columns of data per page. ■ Expand to fit Displays the entire data across a single page. Select one of the following PDF formats in which you want to export the tabular reports: Portrait Displays a maximum of seven columns of data per page. . See “Changing your OpsCenter password” on page 307. Fill in the First Name.

click Settings > My Profile. Change the password at regular intervals thereafter. you need to use a license key and enable Symantec OpsCenter Analytics. EVALUATION etc. See “ Viewing OpsCenter license keys” on page 308. Licensed features that are associated with the key. See “ Adding OpsCenter license keys” on page 308. About managing licenses To use the advanced features that are not available in Symantec OpsCenter. Settings > Configuration > License options The License tab shows the current state of the following options: Table 4-4 Option Key Type Expiry Date Licensed Features License options Description License keys associated with OpsCenter. Type of license key like PERMANENT. In the My Profile dialog box. Passwords are case-sensitive and must contain at least five characters. In the Change Password dialog box. See “ Deleting OpsCenter license keys” on page 308. Expiry date that is associated with the license key. To change your OpsCenter password 1 2 3 In the OpsCenter console. do the following: ■ ■ Type the existing password in the Old Password field. . See “About Symantec OpsCenter” on page 23. ■ Type your new password again in the Confirm New Password text box. 4 Click Save.Understanding OpsCenter settings About managing licenses 307 Changing your OpsCenter password Change the administrator-assigned password the first time you logon to Symantec OpsCenter console. click Change Password. Type the new password in the New Password field.

Viewing OpsCenter license keys You can view the license keys that are installed on the OpsCenterserver host. Total licensed value that is associated for the specific licensed feature. In the OpsCenter console. click Settings > Configuration. Click the License tab. click Settings > Configuration.308 Understanding OpsCenter settings About managing licenses Table 4-4 Option Enabled License options (continued) Description This column tells whether the licensed feature is enabled or not. To view OpsCenter license keys 1 2 3 Log on to the OpsCenter console as admin. On the Add License Key pop-up screen. You can add one or more OpsCenter license keys. In the OpsCenter console. enter a license key and click OK. click Settings > Configuration. Click the License tab. Actual current usage of the licensed feature. Deleting OpsCenter license keys You can remove one or more Symantec OpsCenter Analytics license keys from the OpsCenter Server. Current Usage License Limit Adding OpsCenter 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 delete Symantec OpsCenter Analytics license keys 1 2 Log on to the OpsCenter console as admin. . To add OpsCenter license keys 1 2 3 4 5 Log on to the OpsCenter console as admin. In the OpsCenter console. on which you are connected as an administrator. Click Add.

Configuring the data purge period on the OpsCenter Server You can configure the OpsCenter Server retention periods for the data types that are logged. Settings > Configuration > Data Purge options By default. Edit the default data purge options as follows: . Note: The details of the purged data are stored in the purge-status. By default. Select the check box in front of the license key that you want to delete. Click Save. enter the time of day (in 24-hour clock format) when you want to purge the data. Click the Data Purge tab. such as Job. In the OpsCenter click Settings > Configuration. 5 6 In the Time of Purge text box. and Skipped Files. Click Delete. To configure the data purge period on the OpsCenter Server 1 2 3 Log on to the OpsCenter console as admin. data purge is enabled. data purge is enabled. 4 Edit the default data purge settings as necessary.Understanding OpsCenter settings Configuring the data purge period on the OpsCenter Server 309 3 4 5 Click the License tab. See “Settings > Configuration > Data Purge options” on page 309.log file. which is located in the OpsCenter server logs directory. Policy.

logs can be purged earlier than their respective jobs. The backup logs are purged after five days but the related jobs are still present. Since the data migration from NOM or VBR to the OpsCenter database has just started and is . the OpsCenter Server service and the data migration process start simultaneously. Number of days for which the SLP data should be retained. the logs of such jobs are collected again by the OpsCenter Agent. Because. or they can be purged at the same time. the backup jobs are set to be purged after 10 days.1.310 Understanding OpsCenter settings Configuring the data purge period on the OpsCenter Server Table 4-5 Option Backup Job Data Purge options Description Set the number of days after which you want to purge the backup jobs. Tape Drive History Media History Alert SLP Images Audit Trail Note: By default. The number of days set for backup logs should be less than or equal to the number of days set for backup jobs. Backup Log Set the number of days after which you want to purge the Backup logs. Set the number of days to retain Tape Drive History logs. Restarting the OpsCenter service after upgrading to Server 7. Set the number of days to retain Media History logs. data purge is set to 420 days. Note: If logs are purged but the respective jobs are not purged. Number of days for which you want to retain the audit trail records. the corresponding logs are collected again. For example: The data purge setting for backup jobs is set to 10 days and for Backup Logs are five days.1 While upgrading from NOM or VBR to OpsCenter Server 7. Enter the number of days for which you want to retain the alert data. Thus. Time of Purge Enter the time of day (in 24-hour clock format) when you want to purge the data. Alert data older than this number is purged from the OpsCenter database. In other words.

See “Settings > Configuration > SMTP Server options” on page 311. Settings > Configuration > SMTP Server options A description of the Settings > Configuration > SMTP Server options follows in the table. 5 Click Save. Select Control Panel > Administrative Tools > Services and start the Symantec OpsCenter Server Service. To restart the OpsCenter Server process on UNIX 1 Enter the following command to stop the OpsCenter Server process: /opt/SYMCOpsCenterServer/bin/stopserver 2 Enter the following command to start the OpsCenter Server process: /opt/SYMCOpsCenterServer/bin/startserver Configuring SMTP server settings for OpsCenter This section provides the procedure to configure the SMTP server that you can use for sending emails and alerts. 4 Enter the required information. To use the purge settings that you configured for NOM or VBR in OpsCenter 7. . Use the following procedure to restart OpsCenter Server service after the data migration is complete on Windows and UNIX platforms. OpsCenter uses these global server settings to send email notifications using the SMTP server that you specify. the purge settings in OpsCenter take default values and not the values that you configured in NOM or VBR.Understanding OpsCenter settings Configuring SMTP server settings for OpsCenter 311 not complete. In the OpsCenter console. Click SMTP Server. To restart the OpsCenter Server service on Windows 1 2 Select Control Panel > Administrative Tools > Services and stop the Symantec OpsCenter Server Service. To configure SMTP server settings for OpsCenter 1 2 3 Log on to the OpsCenter console as admin.1. you must restart the OpsCenter Server service after the data migration is complete. click Settings > Configuration.

Enter the user name. To configure Symantec ThreatCon feature in Windows for OpsCenter 1 2 3 Log on to the OpsCenter console with administrator privileges. Enter the password for this user account. To disable ThreatCon. In the OpsCenter.312 Understanding OpsCenter settings Configuring Symantec ThreatCon feature in OpsCenter Table 4-6 Option SMTP Server options Description Enter the SMTP (Simple Mail Transfer Protocol) Server host name. SMTP Server Name SMTP Server port Enter the SMTP (Simple Mail Transfer Protocol) Server port number. uncheck the box next to Enable ThreatCon Collection. Enter the name that is associated with the email ID. Configuring Symantec ThreatCon feature in OpsCenter This section provides information on how to configure the Symantec ThreatCon feature in OpsCenter. Notifications of the alerts that are generated in OpsCenter are sent using this SMTP server. Backup Reporting Department. Some SMTP servers may require user name and password credentials to send email. . See “About the Symantec ThreatCon pane” on page 65. click Settings > Configuration. Specify the email ID to receive any replies to the alerts or the reports that were sent by OpsCenter. The ThreatCon feature is enabled by default. Sender Display Name Sender Display Email Address Server User Name Server User Password Some SMTP servers may require user name and password credentials to send email. Use the following procedure to enable or disable the Symantec ThreatCon feature. For example. Click ThreatCon. The Symantec ThreatCon feature is used to show how secure or vulnerable your network is.

Enter the proxy server name. The host’s primary alias is displayed in all console functions and reports. Table 4-7 Option ThreatCon options Description EnableThreatConCollection Disable or enable the ThreatCon data collection using this check box. .Understanding OpsCenter settings Adding host aliases in OpsCenter 313 4 Edit the default information. 5 Click Save. See “Settings > Configuration > ThreatCon options” on page 313. if the default network is down. Other host aliases are used when you are search in OpsCenter or gather and collate data. Port User Name Password Enter the port number to connect to the proxy server. Settings > Configuration > ThreatCon options A description of the Settings > Configuration > ThreatCon options follows in the table. Polling Interval Server Name Set the minutes for Polling Interval. Adding host aliases in OpsCenter This section provides the procedures to add aliases for hosts. See “Configuring Symantec ThreatCon feature in OpsCenter” on page 312. Enter the user name of the proxy server. Set the password for the user account that you use to connect to the proxy server. Note: The proxy server configuration is not mandatory. Enter the following proxy server details if you want to use it for accessing the latest ThreatCon ratings.

Enter the alias name for the host that you have selected from the drop-down list. To add a host alias 1 2 In the OpsCenter console. Click Save. 3 4 5 Click Add Alias. Add Alias Click Add Alias to add aliases for the selected host. Settings > Configuration > Host Alias options A description of the Settings > Configuration > Host Alias options follows in the table. click Settings > Configuration > Host Alias. . A selected host can have one or more alias associated with it. Click Show Alias to display the aliases associated with the selected host. Instead the explorer attempts to collect data from a host with the alias name. Show Alias Alias 1. For example.314 Understanding OpsCenter settings Adding host aliases in OpsCenter Warning: Your alias names must be compatible with your hosts’ DNS names or with the names by which they are known to applications such as NetBackup and Backup Exec. if you use an alias that is unknown to OpsCenter. All the existing aliases are displayed. Table 4-8 Option Select Host Host Alias options Description From the drop-down list select a host name or type a host name. 2. the explorer stops collecting information from the OpsCenter host. From the drop-down list select a host name or type a host name and click Show Alias. 3. etc. You can clear and save the alias for removing the particular alias.

Click Validate Object Merging. Select the Host Type: Master Server. An auto-suggest feature is available. You can view the snapshot of the selection that you have made earlier. you can merge only one object into other.Understanding OpsCenter settings Merging objects (hosts) in OpsCenter 315 Merging objects (hosts) in OpsCenter OpsCenter provides a facility to merge objects (hosts) that represent the same media server. In the OpsCenter console. Select the Target Host from the drop-down list. To begin the merge. or Client. Using the OpsCenter UI. . Settings > Configuration > Object Merger options A description of the Settings > Configuration > Object Merger options follows in the table. An auto-suggest feature is available. but registered as separate objects (hosts). See “Settings > Configuration > Object Merger options” on page 315. click Settings > Configuration > Object merger. click Start Merge. Table 4-9 Option Host Type Object Merger options Description Select the Media Server. To merge two objects 1 2 3 Log on to the OpsCenter console with administrator privileges. or Client radio button to indicate Host Type. 4 5 6 7 Select the Source Host from the drop-down list. Repeat these steps if you want to merge more objects. Note: Object merger for master server is not supported. Caution: Object merging is not reversible. at a time. you can merge objects (hosts) representing the same backup client. Media Server. In OpsCenter. To modify the Source Host or Target Host click Back. backup client.

See “Settings > Configuration > Tape Libary options” on page 316. In the OpsCenter console. Target host is the host to which you want to merge the source host. you can edit the serial number. Target Host Select a target host from the drop-down list. 6 Click Save. click Settings > Configuration. Select the check box next to tape library. Source host is the host that you want to merge. To modify tape library information in OpsCenter 1 2 3 4 5 Log on to the OpsCenter console with administrator privileges. for which you want to edit the information. Modifying tape library information in OpsCenter OpsCenter provides a facility to monitor all the tapes that the data collector uses. Using the OpsCenter UI. Edit the information. . alias. An auto-suggest feature is available. Validate Object Merging Click Validate Object Merging to view a snapshot of the selection that you have made.316 Understanding OpsCenter settings Modifying tape library information in OpsCenter Table 4-9 Option Source Host Object Merger options (continued) Description Select a source host from the drop-down list. Click Tape Library. manufacturer. Settings > Configuration > Tape Libary options The following table provides a description of the Settings > Configuration > Tape Libary options. slot count of the tape drives the data collector uses. Target host is the resultant host after the object merger. An auto-suggest feature is available. You can view the list of the tape libraries in OpsCenter.

Understanding OpsCenter settings Copying a user profile in OpsCenter 317 Table 4-10 Option ID Tape Library options Description Displays the unique ID that is associated with the tape library. Select reports or cost rates and formulae to be copied to this user profile. is accessible only by the user who has created it. 8 Click Copy. In the OpsCenter console. the associated cost formula and variables are implicitly copied. See “Settings > Configuration > Copy User Profile options” on page 318. Select the type of tape library from the drop-down list. If you copy a cost report. Using the copy user profile functionality. select the items you want to copy. and cost formulas. To copy a user profile 1 2 3 Log on to the OpsCenter console with administrator privileges. for example reports or cost rates and formulae. If you copy a cost formula. click Settings > Configuration > Copy User Profile. Enter the serial number of the tape library. 4 5 6 7 Select the target user account from the To User drop-down list. Enter the alias for the tape library. such as reports. cost variables. Enter the manufacturer of the tape library. Host Name Type Serial Number Manufacturer Alias Slot Count Copying a user profile in OpsCenter Most user-definable content. Click Next. the associated cost variables are implicitly copied. Displays the media server to which the tape library is attached. In the Copy Items options. Enter the slot count for the tape library. you can copy information from one user account to another. Select the source user account from the From User drop-down list. .

318 Understanding OpsCenter settings Setting report export location in OpsCenter Settings > Configuration > Copy User Profile options A description of the Settings > Configuration > Copy User Profile options follows in the table. In the Report Export Location box type the directory where you want to save the reports. In the OpsCenter console. Data from exported reports is stored in a default directory. Select the items you want to copy: Reports or Cost Rates and Formulae. click Settings > Configuration > Report Export Location. if you have not defined any location. . Click Copy to copy the selected items to the selected user profile. Select reports to be copied to this user profile. Settings > Configuration > Report Export Location options A description of the Settings > Configuration > Report Export Location options follows in the table. To User Copy Items Reports Formaulae and Rates Copy option Setting report export location in OpsCenter In OpsCenter you can configure exporting of reports to a predefined location. Table 4-11 Option From User Copy User Profile options Description Select the source user account from the From User drop-down list. To set report export location 1 2 3 4 Log on to the OpsCenter console with administrator privileges. Select cost rates and formulae to be copied to this user profile. Click Save. Select the target user account from the To User drop-down list.

See “Modifying object types in OpsCenter” on page 320. See “Deleting object types in OpsCenter” on page 320. . Settings > Configuration > Object Type options A description of the Settings > Configuration > Object Type options follows in the table. See “Deleting attributes from object types in OpsCenter” on page 321. Located to the right of the Object Types drop-down list. Located above the Attributes check box. You can also add new object types and attributes for those new object types. See “Adding attributes to object types in OpsCenter” on page 320. Click to add.Understanding OpsCenter settings About managing Object Types in OpsCenter 319 Table 4-12 Option Report Export Location options Description Type the directory path where you want to save the reports. Add/Edit/Delete Add/Delete Attributes Adding object types in OpsCenter In OpsCenter you can add or edit attributes of predefined object types. See “Adding object types in OpsCenter” on page 319. Click to add or delete attributes. Report Export Location About managing Object Types in OpsCenter See the following sections for the procedures related to managing object types and their attributes in OpsCenter. Table 4-13 Option Object Types Object Type options Description Click the list box to select an object type that you want to configure. or delete object types. Attributes associated with the selected object type. edit.

Click OK. Click Add. 4 5 Click Add. You cannot modify the name of the predefined objects in the drop-down list. . To delete object types 1 2 3 4 Log on to the OpsCenter console with administrator privileges. Select the object type from the drop-down list. You cannot delete the predefined objects in the drop-down list. Modifying object types in OpsCenter 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 Type. Click Delete. You cannot rename the predefined object types. In the OpsCenter console. type a name for the object type and click OK. click Settings > Configuration > Object Types. click Settings > Configuration > Object Types. In the OpsCenter console. You cannot delete predefined object types. Adding attributes to object types in OpsCenter You can add attributes to all object types.320 Understanding OpsCenter settings About managing Object Types in OpsCenter To add an object type 1 2 3 4 5 Log on to the OpsCenter console with administrator privileges. You can delete the object types that you have created. Enter the name in the Add Object Type dialog box. Deleting object types in OpsCenter You can only delete an object type that you have created.. To modify an object type name 1 2 3 Log on to the OpsCenter console with administrator privileges. In the Add Object type dialog. Select the object type that you want to modify from the drop-down list. See “Adding object types in OpsCenter” on page 319. In the OpsCenter console.

About managing Symantec OpsCenter users After you install Symantec OpsCenter. See “User access rights and UI functions in OpsCenter” on page 322. See “Resetting a OpsCenter user password” on page 328. In the OpsCenter console. In the OpsCenter console. . you need to create user accounts. In the Attributes section. Deleting attributes from object types in OpsCenter You can delete the attributes that are added to an object type. The Symantec Product Authentication Service validates credentials of OpsCenter users based on Windows. Select the object type from the drop-down list and in Attributes section.Understanding OpsCenter settings About managing Symantec OpsCenter users 321 To add attributes to an object type 1 2 3 4 Log on to the OpsCenter console with administrator privileges. See “Adding OpsCenter user groups” on page 329. See “ Deleting OpsCenter users” on page 328. select the check box in front of the attribute you want to delete. See “ Adding new users to OpsCenter” on page 327. or private domains. See “Adding object types in OpsCenter” on page 319. click Settings > Configuration > Object Types. Click Delete. See “ Viewing OpsCenter user account information” on page 326. See “ Editing OpsCenter user information” on page 327. NIS. click Add. Enter the name of the attribute and click OK. See “ Adding new users to OpsCenter” on page 327. See “Resetting a OpsCenter user password” on page 328. click Settings > Configuration > Object Types. Select the object type from the drop-down list. To delete attributes from an object type 1 2 3 4 Log on to the OpsCenter console with administrator privileges.

delete user groups. delete users. Table 4-14 Option Add/Edit/Delete options Name Email address User Role Users options Description Click Add/Edit/Delete to add. Update. Delete Master Server Add. Role that is associated with the user. Create. OpsCenterManagement The OpsCenter Management function includes the following tasks: ■ ■ ■ Add. edit. Login name of the user. Update. SMTP server . update.322 Understanding OpsCenter settings About managing Symantec OpsCenter users Settings > Users > Users options A description of the Settings > Users > Users options follows in the table. remove roles to users and user groups. remove users from user groups. or delete users. Table 4-15 OpsCenter UI functions OpsCenterfunctions Tasks User Management The User Management function includes the following tasks: ■ ■ ■ ■ Create. Domain name (like OpsCenterUsers) that the user is a member of and also specified while adding the user . SNMP. Domain Name User access rights and UI functions in OpsCenter The following tables provide information on OpsCenter users and the functions that they can perform in the OpsCenter GUI. Assign. Delete OpsCenter Agents Set default currency. Table 4-15 provides details of the OpsCenter UI functions that you can perform. Add. Domain Type Domain type (like vx) that the user is a member of and also specified while adding the user. Email address that you provided while adding the user. update. See “User access rights and UI functions in OpsCenter” on page 322.

update Dashboard. Custom SQL Reports This function includes the following tasks: ■ Create. SQL Server. unfreeze ) Drives (Up/Down) Others Backup and Recovery The Backup and the Recovery function includes the following tasks: ■ ■ Execute manual backups. Report Execution This function includes the following tasks: ■ ■ ■ Execute report templates and public custom reports. Search and restore files. Schedule canned and public custom reports. update. Assign Read / Write permissions to users on OpsCenter views and nodes. delete NetBackup entities: Host Properties. All Views Read The NetBackup Operations function includes the following tasks: ■ View OpsCenter views and nodes. Media and Devices. update. delete OpsCenter views and nodes. and Exchange Server) Views Management The Views Management function includes the following tasks: ■ ■ Create. delete custom reports. Policy. update. private. 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. delete custom SQL reports. Custom Reports This function includes the following tasks: ■ ■ Create. folders. Create. Freeze.Understanding OpsCenter settings About managing Symantec OpsCenter users 323 Table 4-15 OpsCenter UI functions (continued) OpsCenterfunctions Tasks NetBackup Configuration Management The NetBackup Configuration Management function includes the following tasks: ■ Add. . application (Oracle. Make custom reports public. update. or both.

Drives. OpsCenter users are categorized as follows: Table 4-16 User Security Administrator User categories Description A Security Administrator is a super admin user who can perform all OpsCenter functions including user management. Others. and NetBackup configuration. The OpsCenter Administrator cannot create. Details): Job. .Create. update.324 Understanding OpsCenter settings About managing Symantec OpsCenter users Table 4-15 OpsCenter UI functions (continued) OpsCenterfunctions Tasks Monitoring Monitoring includes the following tasks: ■ View entities ( Dashboards. Note: A NOM user becomes an Administrator in OpsCenter. or delete users. delete alert policies. acknowledge. or delete users. Administrator This user can perform all OpsCenter functions except for user management. edit. edit. Alert Management The Alert Management function includes the following tasks: ■ ■ . Note: An Administrator in VBR (Veritas Backup Reporter) or NOM (NetBackup Operations Manager) is a Security Administrator in OpsCenter. Operator This user is not involved in the activities that are related to managing users. Policy. Alerts. The OpsCenter Security Administrator can create. Assign. Summary. Media. OpsCenter Server. clear alerts.

such as user management or backup & recovery. The Security Administrator. Table 4-17 OpsCenter function User Management OpsCenter Management NetBackup Configuration Management NetBackup Operations Backup and Recovery User roles Administrator N 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 .Understanding OpsCenter settings About managing Symantec OpsCenter users 325 Table 4-16 User Analyst User categories (continued) Description The role of this user is to mainly analyze the operational and business-level reports. The Analyst has the Read permission on all views. This user cannot perform functions. A VBR read-only admin becomes an Analyst in OpsCenter. Note: A NOM read-only user becomes an Analyst in OpsCenter. Note: A VBR user becomes a Reporter in OpsCenter. a reporter and analyst would be able to view only those schedules that they themselves create. Administrator.1 onwards. Reporter The role of this user is to mainly generate the operational and business-level reports for further analysis. and Operator would however be able to access all the schedules. A reporter would now have access to all the master servers. Note: From 7. Table 4-17 lists the OpsCenter user roles and the OpsCenter UI functions that these users can perform. irrespective of the access permissions.

authentication domain. In the Symantec OpsCenter console. user name. The user information is arranged in a tabular format. and so on. Click Users to view the list of users. You can sort the table by user attributes. which means that the users of this role cannot perform this particular OpsCenter function. name. To view OpsCenter user account information 1 2 3 Log on to the OpsCenter console with administrator privileges. access level. . See “About managing Symantec OpsCenter users ” on page 321. click Settings > Users.326 Understanding OpsCenter settings About managing Symantec OpsCenter users Table 4-17 OpsCenter function Views Management User roles (continued) Administrator Y Security Administrator Y Operator Y Analyst N (Restricted to only permitted entities through Java View Builder) Reporter N (Restricted to only permitted entities through Java View Builder) Restricted to only permitted entities Y All Views Read Report Execution Custom Reports Custom SQL Reports Monitoring Alert Management Y Y Y Restricted to only permitted entities Y Y Y Y Y Y Y Y Y Y Y Y N N Y Y Y Y Y Y Y Y Y Y “Y” represents “Yes”. Viewing OpsCenter user account information You can view a list of OpsCenter users and their information such as. “N” represents “No”. which means that the users of this role can perform this particular OpsCenter function.

Confirm Password. click the check box in front of the user that you want to edit. and contact details. cost center. specify the password. If you have selected the Existing Domain User option. first name. If you have selected the New User option. department. and enter it once again for confirmation. To add a new user to OpsCenter 1 2 3 4 5 Log on to the OpsCenter console with administrator privileges. click Add. . Click Edit. you do not have to enter Password and Confirm Password. user role. In the OpsCenter console. work number. In the OpsCenter console. domain name. The following user information is mandatory: User Name. Editing OpsCenter user information You can edit the existing users. 6 Click Save. Enter the following general and demographic details of the user: User name. mobile number. Select the user creation type: New User or Existing Domain User. and User Role See “User access rights and UI functions in OpsCenter” on page 322. email ID. last name. To edit an existing user in OpsCenter 1 2 3 4 Log on to the OpsCenter console with administrator privileges. click Settings > Users. On the Users tab. Password.Understanding OpsCenter settings About managing Symantec OpsCenter users 327 Adding new users to OpsCenter You can either add the existing users that are discovered from various domains to OpsCenter or create users in the private “OpsCenterUsers” domain. On the Users tab. click Settings > Users.

In the OpsCenter console. 6 Click Save. In the OpsCenter console. click Reset Password. Click Save. To reset a user password 1 2 3 4 5 6 7 Log on to the OpsCenter console with administrator privileges. You can also reset passwords of the OpsCenter users using this page. See “Resetting a OpsCenter user password” on page 328. The Reset Password functionality is applicable only for OpsCenter users. On the Users tab. Resetting a OpsCenter user password This section describes how to reset a user password. click the check box in front of the user for whom you want to reset the password. click Settings > Users.328 Understanding OpsCenter settings About managing Symantec OpsCenter users 5 Modify the user information. Deleting OpsCenter users You can delete the user accounts that do not need to be maintained. You cannot modify the domain of the user. In the General Details pane. See “About managing Symantec OpsCenter users ” on page 321. Click Edit. Click Users. Warning: Do not inadvertently delete all your administrator accounts. . To delete a OpsCenter user 1 2 3 Log on to the OpsCenter console with administrator privileges. Note: The default OpsCenter user admin cannot be deleted. enter the new password and confirm password for the selected user. click Settings > Users. On the Reset Password page.

Viewing OpsCenter user groups This section provides the procedure to view the existing user groups. enter the name of the group and description. To create an OpsCenter user group 1 2 3 4 5 6 Log on to the OpsCenter console with administrator privileges. Click Delete. Enter a name for the user group that you add. To view a user group 1 2 3 Log on to the OpsCenter console with administrator privileges.Understanding OpsCenter settings About managing Symantec OpsCenter users 329 4 5 Check the box next to the user account you want to delete. Table 4-18 Option Add/Edit/Delete options User Groups options Description Click Add to add user groups. click Add to open the Add Users pop-up screen. Settings > Users > User Groups options A description of the Settings > Users > User Groups options follows in the table. In the OpsCenter console. Click User Groups. click Settings > Users. add them to a single user group. Click Add. Name Description Adding OpsCenter user groups If you want to give the same privileges to multiple users. In the OpsCenter console. The same access rights on views are attributed to all users in the user group . Click Delete to delete the user groups. Enter a description for the user group that you add. In the List of Users pane. click Settings > Users. On the User Groups tab. Click Edit to add or delete users to the existing user group. . Click User Groups to view the list of user groups.

select the users that you want to add to this user group. Click OK. click Save. In the OpsCenter console. Select the check box in front of the user group that you want to edit. . Deleting OpsCenter user groups You can delete a user group that you no longer need. Click Delete.330 Understanding OpsCenter settings About managing recipients in OpsCenter 7 8 9 On the Add Users dialog box. Editing OpsCenter user groups You can modify an existing user group. To edit a Symantec OpsCenter user group 1 2 3 4 5 6 7 8 Log on to the OpsCenter console with administrator privileges. On the User Group tab. Add or delete the users using the List of Users pane and Add Users pop-up screen. About managing recipients in OpsCenter You can specify the recipients to whom you want to send alert notifications or email reports. Click User Groups. Modify the user group name or description. Click User Groups . Select the check box next to the user groups that you want to delete. Click Edit. Click Save. In the OpsCenter console. click Settings > Users. click Settings > Users. To delete a Symantec OpsCenter user group 1 2 3 4 5 Log on to the OpsCenter console with administrator privileges.

and deleting email and SNMP trap recipient information. The following sections provide procedures for viewing. See “Settings > Recipients > Email options” on page 331. See “Viewing SNMP trap recipients in OpsCenter” on page 332. See “Configuring SMTP server settings for OpsCenter” on page 311. By default. In the OpsCenter console.Understanding OpsCenter settings About managing recipients in OpsCenter 331 Note: Make sure that the mail server is configured to send emails. Viewing email recipients in OpsCenter This section provides the procedure to view the available email recipients. See “Modifying OpsCenter Email or SNMP recipient information” on page 336. click Settings > Recipients. To view the email recipients 1 2 Log on to the OpsCenter console. See “Creating OpsCenter SNMP trap recipients” on page 334. All email recipients are displayed on this tab. See “Viewing email recipients in OpsCenter” on page 331. See “Creating OpsCenter email recipients” on page 333. Settings > Recipients > Email options A description of the Settings > Recipients > Email options follows in the table. Table 4-19 Option Recipient Name Email Address Email recipient options Description Name of the email recipient Email ID of the recipient . the Email tab is selected. See “About managing recipients in OpsCenter” on page 330. creating. 3 Modify recipients and recipient details as needed. modifying. See “Deleting OpsCenter Email or SNMP trap recipient” on page 336.

when emails are sent. In the OpsCenter console. If a recipient is not active. Modify recipients and recipient details as needed. Settings > Recipients > SNMP trap recipient options A description of the Settings > Recipients > SNMP trap recipient options follows in the table. The status of the trap recipient that states whether it is active or not. Active Description Description about the trap recipient. when alert policies are configured. Name of the SNMP host. . To view the SNMP trap recipients 1 2 3 4 Log on to the OpsCenter console. Port number on the SNMP host where you want to send traps. Click SNMP. it is not available for selection on the Adding Trap Recipients pop-up screen. click Settings > Recipients. it is not available for selection on the Adding Email Recipients pop-up screen. Description Description about the email recipient Viewing SNMP trap recipients in OpsCenter This section provides the procedure to view the available SNMP trap recipients.332 Understanding OpsCenter settings About managing recipients in OpsCenter Table 4-19 Option Active Email recipient options (continued) Description The status of the email recipient that states whether it is active or not If a recipient is not active. Table 4-20 Option Recipient Name SNMP Host Port SNMP trap recipient options Description Name of the SNMP trap recipient.

Select this check box if you want the recipient to receive alert notifications and reports by emails. Enter a short description about the alert or report so that recipients can understand. to which alert notifications or reports are sent. click Add to create new email recipients. In the OpsCenter console. Enter the maximum number of notifications that you want to receive within the specified Delivery Time Span. 5 Click Save. Table 4-21 Option Email Recipient Name Add Email Recipient options Description Enter the name of the official whom you want to notify about an alert or send reports. See “ Settings > Recipients > Email > Add Email Recipient options” on page 333. Delivery Time Span. In the Email tab. and Reset Message Count After Time are not taken into account when notifications are sent. Maximum Number of Messages. To create email recipients 1 2 3 4 Log on to the OpsCenter console with administrator privileges. Settings > Recipients > Email > Add Email Recipient options A description of the Settings > Recipients > Email > Add Email Recipient options follows in the table. Select this check box to activate the Alert Notification Delivery Limit settings. Enter the email ID of the official. Email Address Active Description Activate Delivery Limit Maximum Number of Messages .Understanding OpsCenter settings About managing recipients in OpsCenter 333 Creating OpsCenter email recipients This section describes how to create email recipients. click Settings > Recipients. If you do not select this check box. Enter the required information.

minutes. assume Maximum Number of Messages = 10. In OpsCenter. during which notifications are sent. Creating OpsCenter SNMP trap recipients Traps or interrupts are signals sent to inform the programs that an event has occurred. To create SNMP recipients 1 2 3 4 Log on to the OpsCenter Server host with administrator privileges. Once the message count reaches Maximum Number of Messages. Once it has sent 10 messages. Click SNMP. For more details. Delivery Time Span = 30 Minutes. click Settings > Recipients. refer to the About using SNMP with OpsCenter section.334 Understanding OpsCenter settings About managing recipients in OpsCenter Table 4-21 Option Add Email Recipient options (continued) Description Enter the time duration in hours. Delivery Time Span Reset Message Count After Enter the time period in hours. traps are the notifications that are sent to a specified SNMP host or group of hosts when a condition is met. In the OpsCenter console. Click Add. For example. minutes. Once this time period is over. A trap recipient is a host that receives notifications in the form of SNMP traps when an alert condition is met. or seconds. Alert Manager once again starts sending messages until message count reaches 10. it blocks the delivery of new messages for next two Hours. In this case. After two hours. or seconds. 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. Alert Manager sends messages until message count reaches 10 in 30 Minutes. during Time which notifications are blocked if the message count has reached Maximum Number of Messages. Maximum Number of Messages is reset and the Notification Manager starts sending notifications for the specified Delivery Time Span. a trap is sent after an alert was generated as a result of failure of communication between the OpsCenter Agent and Server. Note: For example. and Reset Message Count After Time = 2 Hours. .

Select this check box to activate the Alert Notification Delivery Limit Settings. Delivery Time Span. Active Description Activate Delivery Limit Maximum Number of Messages Delivery Time Span . Enter the port number on the SNMP host where you want to send traps. minutes. Enter a maximum number of notifications that can be sent within the specified Delivery Time Span. See “Settings > Recipients > SNMP > Add SNMP trap recipient options” on page 335.Understanding OpsCenter settings About managing recipients in OpsCenter 335 5 In the SNMP Attributes page enter the required information. 6 Click Save. The notifications are sent as soon as alerts are generated. during which notifications are sent. Maximum Number of Messages. or seconds. Select this check box if you want the recipient to receive notifications by SNMP traps. If you do not select this check box. Settings > Recipients > SNMP > Add SNMP trap recipient options A description of the Settings > Recipients > SNMP > Add SNMP trap recipient options follows in the table. Once the message count reaches Maximum Number of Messages. Enter an SNMP host. Enter a short description about the traps. to which you want to send traps. Table 4-22 Option Recipient Name SNMP Host SNMP Port Add SNMP trap recipient options Description Enter the name of the SNMP trap recipient. Alert Manager blocks the delivery of any new notifications to the associated recipient for the time period that is specified for Reset Message Count After Time. Enter the time duration in hours. and Reset Message Count After Time are not taken into account when notifications are sent.

click Settings > Recipients. In the Email Recipients tab or SNMP Recipients tab. Click Save. . change Email Recipient or SNMP Trap Recipient attributes and Alert Notification Delivery Limit Settings. minutes. Deleting OpsCenter Email or SNMP trap recipient Only OpsCenter administrator can delete email or trap recipient. See “Creating OpsCenter SNMP trap recipients” on page 334. On the modify email or trap recipient page. Click Delete. Once this time period is over. Click Edit. or seconds.336 Understanding OpsCenter settings About managing recipients in OpsCenter Table 4-22 Option Add SNMP trap recipient options (continued) Description Reset Message Count After Enter the time period in hours. Modifying OpsCenter Email or SNMP recipient information Only OpsCenter administrators can modify email or trap recipient information. To delete Email or SNMP trap recipient 1 2 3 4 In the OpsCenter console. Click Save. click Settings > Recipients. select the email or trap recipient(s) from the table that you want to delete. select the email or trap recipient that you want to edit. See “Creating OpsCenter email recipients” on page 333. Maximum Number of Messages is reset and Alert Manager starts sending notifications for the specified Delivery Time Span. during Time which notifications are blocked if the message count has reached Maximum Number of Messages. To modify email or SNMP trap recipient information 1 2 3 4 5 In the OpsCenter console. See “Creating OpsCenter email recipients” on page 333. In the Email Recipients tab or SNMP Recipients tab.

all global currencies that are set by the administrator are available for selection. You cannot access the Settings > Chargeback feature if you do not have Symantec 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. However. one of which can be set as default currency.Understanding OpsCenter settings About managing cost analysis and chargeback for OpsCenter Analytics 337 About managing cost analysis and chargeback for OpsCenter Analytics This feature is accessible only to Symantec OpsCenter Analytics users. This feature is disabled for unlicensed OpsCenter version. you can set multiple global currencies. in the Default Currency drop-down list. See “Settings > Chargeback > Cost Variable options” on page 339. cost formulae. In the OpsCenter console. You can set the cost variable. OpsCenter does not support conversion of currencies. To set the default currency for cost reports 1 2 Log on to the OpsCenter console with administrator privileges. See “Settings > Chargeback > Cost Formulae options” on page 343. . In OpsCenter Analytics. Setting the default currency for OpsCenter cost reports This section provides the procedure to set the default currency that you want to be displayed on OpsCenter cost reports. 3 On the Currency Settings tab. you can choose the currency that you want to be displayed on cost reports. The following sections provide procedures for managing cost analysis and chargeback. You cannot access the Settings > Chargeback feature if you do not have Symantec OpsCenter Analytics. See “Editing the OpsCenter global currency list” on page 338. click Settings > Chargeback. See “Editing the OpsCenter global currency list” on page 338. Select a currency from the drop-down list. If you have OpsCenter administrator privilege. and cost estimation that you want to run the cost reports. See “Setting the default currency for OpsCenter cost reports” on page 337.

Table 4-23 Option Default Currency Currency Settings options Description Select a currency from the drop-down list. for US dollar currency you can either select a currency code USD or symbol $. For example. All global currencies that are set by the administrator are available for selection.338 Understanding OpsCenter settings About managing cost analysis and chargeback for OpsCenter Analytics 4 Select the Currency Display Mode: Currency Code or Currency Symbol. To edit the global currency list 1 2 Log on to the OpsCenter console with administrator privileges. Select the Currency Display Mode: Currency Code or Currency Symbol. . 3 On the Currency Settings tab. Click Save. This feature is disabled for unlicensed OpsCenter version. for US dollar currency you can either select a currency code USD or symbol $. click Edit Currency List. In the OpsCenter console. Editing the OpsCenter global currency list This section provides the procedure to edit the global currency list. Edit Currency List Currency Display Mode Display Currency Option in Select the Display Currency Option in Cost Reports check Cost Reports box to show the default currency on the cost reports. If you have not entered the Symantec OpsCenter Analytics license key. This list is available when a default currency is selected to be displayed on OpsCenter cost reports. 5 6 Settings > Chargeback > Currency Settings options A description of the Settings > Chargeback > Currency Settings options follows in the table. which appears on chargeback reports. Click this option to change the list of currencies available for selection. which appears on chargeback reports. Select the Display Currency Option in Cost Reports check box to show the default currency on the cost reports. you cannot access the Settings > Chargeback feature. For example. click Settings > Chargeback.

It is the default currency list and lists the currencies that you select. A description of the Settings > Chargeback > Cost Variable options follows in the table. Table 4-25 Option Name Metric Cost Variable options Description Displays the name of the cost variable that you add.Understanding OpsCenter settings About managing cost analysis and chargeback for OpsCenter Analytics 339 4 On the Edit Currency List pop-up screen. 6 Click OK. Remove. Add/Remove/Add All/Remove All Settings > Chargeback > Cost Variable options You can create cost variables based on various parameters to determine cost of various services. You can use Add. select currencies from the Global Currency list which you want to make available for selection in the Currency Settings > Default Currency drop-down list. See “Setting the default currency for OpsCenter cost reports” on page 337. . You can use these options to alter the User Currency list. 5 Click Add to add the selected currencies to the User Currency list. Settings > Chargeback > Currency Settings > Edit Currency List options A description of the Settings > Chargeback > Currency Settings > Edit Currency List options follows in the table. Table 4-24 Option Global Currency User Currency Edit Currency List options Description Lists the available global currencies. Add All. Total Date Ranges and Rates Displays the date ranges and rate in units for the date range that you select. Displays the metric that you select for the cost variable. and Remove All options to alter the User Currency list.

Sybase. Add an associated rate to the cost variable. However. The default option is All. the types of backups that can be performed on the clients. when a cost variable is created. tape or disk. Typically.00 per backup job. 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 . each service is represented by one variable that reflects the cost of the service. Select a variable metric from the drop-down list for the cost variable that you add. Table 4-26 Option Variable Name Variable Metric Add Cost Variable options Description Enter a name for the cost variable that you want to add. Examples include DB2. Measure cost for a specific transport type for example. Measure costs for the jobs that use a specific policy type.340 Understanding OpsCenter settings About managing cost analysis and chargeback for OpsCenter Analytics And if you click the Add option. The default option is All. OpsCenter supports NetBackup's disk-based data protection feature. Select to add a end date to the cost variable. Measure cost for a specific storage type for example. which enables you to select disk as a storage type. for example $1. Select to add more date ranges. LAN (local area network) or SAN (storage area network ). a page with the following settings appears. You can also select Never as the end date. Job Type Job Policy Type Job Transport Type Job Storage Type Date Range Starts Date Range Ends Rate Add New Range Creating cost variables in OpsCenter Cost reports in OpsCenter Analytics are based on the user-defined variables that define the cost of various services. the policy type determines the type of clients that can be part of the policy and. in some cases. The default option is All. Select to add a start date to the cost variable. The default policy type is All. In NetBackup. for example Backup or Restore. and MS Exchange Server. Measure costs for a specific type of job.

See “Settings > Chargeback > Cost Variable options” on page 339. and Protected Job Size select the Job Type. Note: To generate deduplication savings reports. and Job Storage Type. Add at least one date range. Job Policy Type. Day. a single variable can incorporate the rate of $1. Job Transport Type. select additional parameters to refine the metric you selected. click Add. .00 per backup job until 31 December 2004 and the rate of $1. For example. you need to create the variables that define the cost of various services. Add an associated rate by typing a cost per service unit (such as backup jobs or backed-up GB) in the Rate field. Enter the variable name. Year. In the OpsCenter console. 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 Cost Variable. and Time.Understanding OpsCenter settings About managing cost analysis and chargeback for OpsCenter Analytics 341 a single variable. To create a cost variable 1 2 Log on to the OpsCenter console with administrator privileges. you must create a cost variable with the Protected Job Size (GB) metric. click Settings > Chargeback.25 per backup job starting on 1 January 2005. 3 4 5 On the Cost Variable tab. For Job Count. 7 Add one or more date ranges using the drop-down lists for Month. To set up OpsCenter to run cost reports. Note: These fields are not applicable for the Daily Occupancy variable metric.

you must recreate the variable manually. To restore a deleted variable. Deleting a cost variable removes it permanently from the database. click Settings > Chargeback. 3 4 5 6 Select the check box in front of the variable name that you want to modify. To modify a cost variable 1 2 Log on to the OpsCenter console with administrator privileges. click Settings > Chargeback. Deleting cost variables in OpsCenter You can variables you no longer need. You can now use the variable you created to build the formulas that form the basis for cost reports. Modify the cost variable details. Click Cost Variables. You can also modify the variable later to add or delete date ranges as costs change.342 Understanding OpsCenter settings About managing cost analysis and chargeback for OpsCenter Analytics 8 Optionally. 9 Click OK . Click OK. Click Cost Variables. and you must update any formulas that use the variable. Select the check box in front of the cost variable that you want to delete. In the OpsCenter console. date ranges and rates of a variable to reflect changing conditions in your enterprise. click Add New Range. to add more date ranges. For example. In the OpsCenter console. you can modify the name. To delete a cost variable 1 2 3 4 5 Log on to the OpsCenter console with administrator privileges. Click Edit. Click Delete. . This can be useful for defining multiple date ranges to represent historical or future changes in service costs. See “Creating cost formulae in OpsCenter” on page 343. Modifying cost variables in OpsCenter You can update cost variables and formulas without having to recreate the reports that rely on them.

Understanding OpsCenter settings About managing cost analysis and chargeback for OpsCenter Analytics 343 Settings > Chargeback > Cost Formulae options Based on cost variables you can create the cost formulas that you can use to generate cost reports. Select a cost variable from the drop-down list. You need to select at least one cost variable. Select a different variable from the drop-down list. click Add new cost variable. 6 Optionally. You now can use the formula to create cost reports. These reports help you evaluate the cost of services and make decisions about what to charge for performing those services. To create a cost formula 1 2 Log on to the OpsCenter console with administrator privileges. create the formula that define the cost of various services to run cost reports. Modifying cost formulae in OpsCenter You can modify the name and variables of a cost formula that you have created. click Settings > Chargeback. A description of the Settings > Chargeback > Cost Formulae options follows in the table. Table 4-27 Option Name Total Cost Variables Cost Formulae options Description Displays the name of the cost formulae added. 3 4 5 On the Cost Formulae tab. You can also modify the formulae later to add or delete variables. 7 Click OK. . Creating cost formulae in OpsCenter After you create cost variables. click Add. to define formulae containing more than one variable. Enter the name of the formula. Click Cost Formulae. Displays the number of cost variables added to the cost formulae. In the OpsCenter console.

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. Click Edit.000 over the next year to provide backup services throughout your enterprise. Using historical data. In the OpsCenter console. you can obtain an estimate per kilobyte that is based on the backup activity you performed last year.344 Understanding OpsCenter settings About managing cost analysis and chargeback for OpsCenter Analytics You can update chargeback formulas without having to recreate the reports that rely on them. Click Cost Formulae.000. Modify the details of the cost formula. 3 4 5 6 On the Cost Formulae tab. select the cost formulae that you want to modify. it provides you with an estimate of how much it costs your organization to provide a specific kind of service. click OK. select the cost formulae that you want to delete. To modify a cost formulae 1 2 Log on to the OpsCenter console with administrator privileges. To delete cost formulae 1 2 Log on to the OpsCenter console with administrator privileges. For example. By inserting the metric Daily Occupancy into the tool. See “Creating cost variables in OpsCenter” on page 340. . along with the amount $500. For example. Deleting a cost formulae in OpsCenter You can also delete formulae that you no longer need. suppose you anticipate spending $500. 3 4 5 On the Cost Formulae tab. Deleting a cost formula removes it permanently from the database. Click OK. click Settings > Chargeback. On the confirmation dialog box. Estimating chargeback costs using the OpsCenter Formula Modeling Tool The Formula Modeling Tool offers an easy way to estimate baseline rates for the IT services you provide. In the OpsCenter console. Click Delete. Click Cost Formulae. click Settings > Chargeback.

Settings > Chargeback > Cost Estimation options A description of the Settings > Chargeback > Cost Estimation options follows in the table. in dollars. Examples: $50000. 5 6 Use the following Time Frame parameters to define the time intervals for which data is modeled.Understanding OpsCenter settings About managing cost analysis and chargeback for OpsCenter Analytics 345 See “Creating cost formulae in OpsCenter” on page 343. Click Cost Estimation. In the OpsCenter console.00 . To estimate baseline (chargeback) costs using the Formula Modeling Tool 1 2 Log on to the OpsCenter console with administrator privileges. 3 4 Select a Report Grouping parameter to define the model’s scope. or $10000. $10000. Table 4-28 Option Report Grouping Cost Estimation options Description Select a report grouping parameter to define the model's scope. Example: Daily Occupancy Amount Specify the total amount of money. Examples: All Master Servers or User Metric Select a metric or category of service. Use the Metric Selection parameters to specify the metric whose rate you want to estimate: See “Settings > Chargeback > Cost Estimation options” on page 345. Click Run Model to input different values into the model. you expect to charge for service within that category in a given time frame. click Settings > Chargeback. or to run a new model.

year. The estimate reflects the data that is collected within the specified time period. Choose absolute dates if you want the estimate’s contents to remain static whenever you display it. Select a start time (month. The estimate reflects data from the time period between the start and the end dates.M. Then select a time interval using the Last drop-down lists.M. day. up to the current time. ■ Click Relative to configure a relative time frame. Choose relative dates if you want the estimate to reflect data that was collected over the most recent time interval. Such estimates always reflect the data that is collected over the most recent time interval.346 Understanding OpsCenter settings About managing cost analysis and chargeback for OpsCenter Analytics Table 4-28 Option Time Frame Cost Estimation options (continued) Description Defines the beginning and end of the time interval the estimate must cover. to APR 30 2004 12:00 A. ■ 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. and time of day) using the From drop-down lists. Select one of the following: Click Absolute to configure an absolute time frame. Example: From MAR 1 2004 12:00 A. and a stop time using the To drop-down lists. You can choose either absolute or relative dates. .

Chapter 5 Understanding data collection This chapter includes the following topics: ■ ■ ■ ■ ■ ■ ■ ■ ■ About data collection in OpsCenter About managing OpsCenter Agents About managing OpsCenter Data Collectors About configuring data collection for NetBackup Configuring Backup Exec data collector Collecting data from PureDisk About collecting data from Enterprise Vault IBM Tivoli Storage Manager data collector variables and details EMC NetWorker data collector variables About data collection in OpsCenter OpsCenter provides extensive reporting on the data that is collected from backup and archiving products. . An OpsCenter Agent comprises product-specific data collectors that collect data from point products and return it to the OpsCenter Server. Note: Only one OpsCenter Agent can be installed on a single host.

OpsCenter Integrated Agent is also installed and configured. See “Backup and archiving products supported by Symantec OpsCenter 7. About OpsCenter Agents The OpsCenter Agent collects data from various Symantec and third-party backup and archiving products. which you can use to collect only PureDisk data. . For more details on OpsCenter Agent installation and deployment scenarios. These products can reside on the OpsCenter Agent host or on remote hosts. Note: When you install the OpsCenter Server. IBM Tivoli Storage Manager (TSM) EMC NetWorker ■ ■ ■ ■ See “About configuring data collection for NetBackup” on page 361. Symantec NetBackup PureDisk Symantec Enterprise Vault (Windows only) Note: To collect archive data from Enterprise Vault.348 Understanding data collection About data collection in OpsCenter An OpsCenter Agent consists of the data collectors that can collect data from the following backup and archiving products: ■ Symantec Backup Exec (Windows only) Note: To collect data from Backup Exec Server host. you need to install the OpsCenter Agent on a Windows host. you do not need to manually install or configure OpsCenter Agent. See “OpsCenter Data Collector types” on page 349.1” on page 351. To collect PureDisk data. You can collect PureDisk data only through the OpsCenter Integrated Agent. You cannot delete the Integrated Agent. you need to install the OpsCenter Agent on a Windows host. See “About OpsCenter Agents” on page 348. refer to the Installing Symantec OpsCenter chapter.

Policy and Schedule.Understanding data collection About data collection in OpsCenter 349 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. Media. You can configure multiple data collectors on a single OpsCenter Agent host. Enterprise Vault. Each data collector collects data from a single product host. Note: Error logs and skipped files are collected as part of job data. You can create data collectors to communicate with the various products. For example. By default the InstallPath is: C:\Program Files Naming convention for the OpsCenter Agent log file: 5*-146-*. such as Backup Exec. or Image. You can enable or disable a data collector. Table 5-1 Data collector types Description Data Collector type Symantec Backup Exec Data Create this data collector to collect data from Backup Exec. Backup Exec data collector can collect Tape Drive Usage. Collector (Windows only) See “Configuring Backup Exec data collector” on page 388. or EMC NetWorker. Table 5-1 lists the data collectors that you can configure in OpsCenter. .log An example of the OpsCenter Agent log file name: 58330-146-2567491850-091129-0000000000. collect data from backup and archiving product hosts. These data collectors collect the specified data type as specified in the configuration. Job. You can specify to collect all or some of the data types for that product.log OpsCenter Data Collector types The OpsCenter data collectors.

2A. 6.x. 6.4. Data Collector type NetBackup PureDisk Data Collector Note: You can collect the PureDisk data only through the OpsCenter Integrated Agent that is installed with the OpsCenter server.5.x.6. 6. See “Collecting data from PureDisk” on page 389.5 8. 5. 12. EMC NetWorker Data Collector Create this data collector to collect data from EMC NetWorker. 6. 5.3) 7. (5.x.2.0MP7.350 Understanding data collection About data collection in OpsCenter Table 5-1 Data collector types (continued) Description Create this data collector to collect data from NetBackup PureDisk. 6.0. 6.0. 7. Table 5-2 Data Types Data types collected NetBackup Backup Enterprise Vault Exec Symantec IBM EMC NetBackup Tivoli NetWorker PureDisk Storage Manager (6.6.x.0 Y N N Y Y Y . See “EMC NetWorker data collector variables” on page 406.1) Job Y (10. 6.5.5) 6.5.5. 11.1 from various backup and archiving products. See “IBM Tivoli Storage Manager data collector variables and details” on page 405.1. TSM Data Collector Table 5-2 lists the data types that are collected by OpsCenter 7.0. 7.3.2. 7. 6. Symantec Enterprise Vault Data Collector (Windows only) Create this data collector to collect archive data from Symantec Enterprise Vault database See “About collecting data from Enterprise Vault” on page 392.3 (6. 2010) 7.0. To collect PureDisk data. you need to create a data collector for the Integrated Agent.0.5.6.1. Create this data collector to collect data from TSM.4.6.5.x.

you can do advanced reporting from the data that is collected from all of these products. you cannot collect data from third-party products like IBM Tivoli Storage Manager (TSM) and EMC NetWorker. .Understanding data collection About data collection in OpsCenter 351 Table 5-2 Data Types Data types collected (continued) NetBackup Backup Enterprise Vault Exec Symantec IBM EMC NetBackup Tivoli NetWorker PureDisk Storage Manager Y Y Y Policy Y and Schedules Tape Drive Image Error Logs Y Y N N Y N N N Y Y Y Y N Y N N N N N N N Y N N Schedule Y Jobs Media Skipped Files Target Archive Vault Vault Store Y Y N N N N N N Y Y N N N N N N Y Y Y N N N N N N N N N Y Y Y Y N N Y Y N N N N N N N N N N N N Backup and archiving products supported by Symantec OpsCenter 7.1 This section lists the backup and archiving products that OpsCenter 7.1 supports. Table 5-3 lists the backup and archiving products that OpsCenter supports. Note that with the licensed version of OpsCenter. With the unlicensed version.

6. All supported Symantec Backup 2010 R2 Exec platforms by remote agent. 7.1) by remote agent Note: NBU 7.0. Symantec Backup Exec 10d. 6.1 PureDisk supported platform (PDOS) by the OpsCenter integrated Agent.3 Native agent on backup servers on Windows 2003 (SP2 & R2).6.5.2. 6. 2008 (SP2 & R2) and Solaris 9/10 Data collection is possible only with a licensed version of OpsCenter. 2008 Exec running on NetWare. EMC NetWorker 7.5 and higher versions. 6. 10 Symantec NetBackup PureDisk 6.0.0. 6.1 Versions 6.352 Understanding data collection About data collection in OpsCenter Table 5-3 Backup and archiving products supported by Symantec OpsCenter 7. 11d. 12.0 MP7 and higher versions.5. select the Agent that is installed as Integrated Agent. 6. 6.6. 7.1 Backup or Archiving product Symantec NetBackup Support level All supported NetBackup platforms (except 7.0. 6. 2008 (SP2 & R2).6. 6. 12. You do not need a separate Agent to collect data from PureDisk.0. and Solaris 9.1 does not require any Agent.1.0. Native agent for Windows 2003 (SP2 & R2). (SP2 & R2) Symantec Enterprise Vault 7.6.2.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).5. 2010.2.5.2. 6. To create or configure the data collector. 7.1.3.1. . You can use the inbuilt Agent of the OpsCenter Server for data collection. Note: OpsCenter does not Native agent on backup servers on support Symantec Backup Windows 2003 (SP2 & R2). Windows 2008 (SP2 & R2). 8.

NetBackup master server. For example if the OpsCenter server and the managed host show 8 pm CST and 9 pm PST respectively. For example.3. 5. then 8 pm (CST) and 9 pm (PST) must translate to the same GMT time. . A backup or archive product host means a supported product host that is connected to OpsCenter.5 Backup or Archiving product IBM Tivoli Storage Manager (TSM) Support level All supported TSM platforms by remote agent Native agent for backup server on Windows 2003 (SP2 & R2). If the OpsCenter server and the product host are in the same time zone (like CST). Examples of a backup or archive product host (product host) are PureDisk host. creating. If the OpsCenter server and product host are in different time zones like CST and PST.1 (continued) Versions 5. and deleting an OpsCenter Agent configuration. 2008 (SP2 & R2) and Solaris 9/10 Data collection is possible only with a licensed version of OpsCenter. Backup Exec host.Understanding data collection About managing OpsCenter Agents 353 Table 5-3 Backup and archiving products supported by Symantec OpsCenter 7. but show different time like 8 pm and 10 pm. See “Configuring an OpsCenter Agent” on page 355. See “Viewing OpsCenter Agent status” on page 355. About managing OpsCenter Agents The following topics provide more information about viewing. then ensure that both the CST and the PST time convert to the same GMT time. both OpsCenter server and the product host must show the same time. then OpsCenter may not display accurate data in the reports and also Monitor and Manage tabs of the OpsCenter console. Enterprise Vault host etc. See “About the OpsCenter Agent” on page 35. Note: Ensure that the time on the OpsCenter Server and the backup or archive product host is in sync based on the time zone they are deployed in. if the OpsCenter server and the product host are in CST time zone.4. See “Modifying an OpsCenter Agent” on page 356. modifying. 5.

Settings > Configuration > Agent options A description of the Settings > Configuration > Agent options follows in the table. This field is specific to Enterprise Vault hosts. Data collection status for policy and schedule on the product host. Data collection status for jobs on the product host. Data collection status for media on the product host. Host from where data is collected by the Agent like Backup Exec server . Create/Edit/Delete Data Collector Select the Create Data Collector or Edit Data Collector option to create an agent or modify the details of an agent using the Data Collector Wizard.354 Understanding data collection About managing OpsCenter Agents See “Deleting OpsCenter Agents” on page 357. Table 5-4 Option Create/Edit/Delete Agent Settings > Configuration > Agent options Description Select the Create Agent or Edit Agent option to create an agent or modify the details of an agent. This field is specific to EMC NetWorker. See “Data Collector Wizard settings” on page 359. Select Delete Agent to delete the selected agent. Data collection status for tapes on the product host. This field is specific to Enterprise Vault hosts. Policy and Schedule Tape Drive Information Media Job Archive Archive Policy Images Target . PureDisk server etc. This field is specific to Enterprise Vault hosts. See “Settings > Configuration > Agent > Create Agent or Edit Agent options” on page 356. Select Delete Data Collector to delete the selected agent. Name Product Host Name of the Agent host.

Agent Summary by Data Type Status. . select an Agent to view its status at the bottom of the page. On the Agent list. By default the General tab is selected. 3 Click the Agent Summary by Data Collector Status. To view Agent status 1 2 In the OpsCenter console. See “Configuring an OpsCenter Agent” on page 355. or Agent Summary by Data Collector Count tab to view the relevant details. The tab displays the parameters which you have specified when you created this Agent. Configuring an OpsCenter Agent This section provides the procedure to configure an OpsCenter Agent. Table 5-5 Property Agent Host PBX Port General tab properties Description 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 Viewing OpsCenter Agent status Use this section to view general details and status of an OpsCenter Agent that you have configured in OpsCenter. click Settings > Configuration > Agent.Understanding data collection About managing OpsCenter Agents 355 Table 5-4 Option Vault Store Settings > Configuration > Agent options (continued) Description This field is specific to Enterprise Vault hosts. See “Settings > Configuration > Agent options” on page 354.

you can only configure an Agent for IBM Tivoli Storage Manager and EMC NetWorker. PBX Port Enter the port number that the OpsCenter Agent requires to connect to the PBX on the OpsCenter Server Option Agent Host Agent Operating System Family OpsCenter Server Network Select the network address from the drop-down list. using Address which you want to connect to the OpsCenter Server Modifying an OpsCenter Agent This section provides the procedure to modify an OpsCenter Agent information.356 Understanding data collection About managing OpsCenter Agents To configure an OpsCenter Agent 1 2 In the OpsCenter console. See “Settings > Configuration > Agent > Create Agent or Edit Agent options” on page 356. Click Create Agent and complete the fields. select the check box in front of the Agent that you want to modify. the Create Agent pane options must be completed as follows: Table 5-6 Settings > Configuration > Agent > Create Agent or Edit Agent options Description 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. Click Edit Agent. 3 Click Save. To modify an OpsCenter Agent 1 2 3 In the OpsCenter console. you can configure an Agent for all supported backup and archiving products. For example: Solaris Family or Windows Family For Windows hosts. From the list of agents. Settings > Configuration > Agent > Create Agent or Edit Agent options To create an Agent. click Settings > Configuration > Agent. . click Settings > Configuration > Agent. For Solaris hosts.

Click Save. Viewing OpsCenter Data Collector status Use this section to view general details and status of a Data Collector that you have configured for an Agent. About managing OpsCenter Data Collectors The following topics provide more information about viewing. select the check box in front of the Agent that you want to delete. modify PBX port or OpsCenter Server Network Address. Deleting OpsCenter Agents This section provides the procedure to delete an OpsCenter Agent. click Settings > Configuration > Agent. modifying. click Settings > Configuration > Agent. . See “ Configuring an OpsCenter Data Collector” on page 358. See “ Deleting OpsCenter Data Collectors” on page 361.Understanding data collection About managing OpsCenter Data Collectors 357 4 5 On the Edit Agent page. Click Delete. expand an Agent to view the Data Collectors that are configured for this Agent. or deleting a data collector. See “ Modifying an OpsCenter Data Collector configuration” on page 360. On the Agent list. To view data collector status 1 2 In the OpsCenter console. To delete an OpsCenter Agent 1 2 3 In the OpsCenter console. configuring. From the list of agents. See “Viewing OpsCenter Data Collector status” on page 357.

which you have specified when you created this Data Collector. See “ Configuring an OpsCenter Data Collector” on page 358. which this Data Collector collects data from. for which you want to configure a Data Collector. OpsCenter consists of Server. click Settings > Configuration > Agent. For example: Symantec Backup Exec Product Host Status Displays the name of the target host. By default the General tab is selected displaying the following Data Collector details. Complete the fields on the Create Data Collector: Product Selection page. Product Displays the name of the product type. 4 Select the Data Collection Status tab. After you install and configure an OpsCenter Agent.358 Understanding data collection About managing OpsCenter Data Collectors 3 Select a Data Collector to view its details and status at the bottom of the page. On the Agent list. See “Configuring an OpsCenter Agent” on page 355. Agent. If the Data Collector status is disabled. Click Create Data Collector. and a console. You can generate various business reports on this backup data or archiving data. See “Data collection status of a master server” on page 373. Displays the status of the Data Collector as Enabled or Disabled that you have set. Configuring an OpsCenter Data Collector OpsCenter is designed to provide extensive reporting on the data that is received from backup and archiving products. select a check box in front of the Agent. The OpsCenter Agent contains product-specific data collectors collecting data from the products and returning it to the OpsCenter Server. . Java View Builder. configure the data collectors. To configure a data collector 1 2 3 4 In the OpsCenter console. There is more information about the parameters displayed on this tab. for which this Data Collector is configured. the data is not collected from the target host.

Symantec Backup Exec. refer to the respective data collector settings. the Target Details. See “IBM Tivoli Storage Manager data collector variables and details” on page 405. 8 9 Enter the Data Collection Settings. Target host name Enter the name of the product host from which you want to collect backup or archiving data. See “Configuring Backup Exec data collector” on page 388.Understanding data collection About managing OpsCenter Data Collectors 359 5 Click Next. 6 Verify or modify the default Target Details: See “Data Collector Wizard settings” on page 359. See “EMC NetWorker data collector variables” on page 406. Configuration Settings. These settings vary depending on the data collector type you configure. Complete the Data Collector: Details fields as follows: . See “About collecting data from Enterprise Vault” on page 392. 7 Enter the data collector ConfigurationSettings. On the Create Data Collector: Details page. Click Save. For example. For product specific configuration settings. and Data Collection details are displayed. Data Collector Wizard settings Complete the Product Selection fields as follows: Table 5-7 Setting Select Product Product Selection settings Description Select the name of the product from which you want to collect data. 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.

after 15-minutes interval . Configuration Status Collectible Data Type Modifying an OpsCenter Data Collector configuration This section provides procedure to modify configuration of a Data Collector. You can disable the data collection by changing the status.M. Lists the data types that can be collected from a product host. Blackout Period End Time Select the end time of a blackout period.360 Understanding data collection About managing OpsCenter Data Collectors Table 5-8 Setting Product Data Collector: Details settings Description Displays the name of the product from which this data collector collects data. Target host name Data Collector Status Blackout Period Start Time Select the start time of a blackout period. The next data collection starts at 11:15 A. . the data collector status is Enabled. Last Successful Data Load States whether last data load was successful or not. hours. The first data collection starts at say 9:00 A. till all archive records are collected and ends at 11:00 A.M. Select this check box to collect the associated data type. You need to specify the product name when you create the data collector. Collection Interval (sec) Enter the Collection Interval in minutes. Displays the name of the product host from which this data collector collects data. See “Viewing OpsCenter Agent status” on page 355. By default. and days. The data types vary depending on the product that you are collect data from. Collection interval is the time interval that you want to set between the two consecutive data collections. For example: Symantec Backup Exec. You need to specify the product name when you create the data collector. See “OpsCenter Data Collector types” on page 349. For example: You have set the Collection Interval to 15 Minutes. The data is not collected during the time that is specified in Blackout Period Start Time and Blackout Period End Time. The data is not collected during the time that is specified in Blackout Period Start Time and Blackout Period End Time.M.

Modify data collection configuration settings. click Settings > Configuration > Agent. On the Agent list. To delete a Data Collector configuration 1 2 3 4 5 Log on to the OpsCenter Server. Select a check box in front of the Data Collector that you want to modify. modify the Target Details. expand an Agent to view Data Collectors that are configured for this Agent. delete. On the Agent list. Modify collection interval. 10 Click Save. Select check boxes in front of the Data Collectors that you want to delete..Understanding data collection About configuring data collection for NetBackup 361 To modify a Data Collector configuration 1 2 3 4 5 6 7 8 9 Log on to the OpsCenter console. and control data collection for a master server. edit. The following sections describe the NetBackup data collection in detail: ■ ■ NetBackup data collection view How OpsCenter collects data from NetBackup . These settings vary depending on the product. On the Edit Data Collector: Details page. In the OpsCenter console. which this data collector collects data from. expand an Agent to view Data Collectors that are configured for this Agent. It also describes how you can add. About configuring data collection for NetBackup This section describes how OpsCenter collects data from NetBackup. Deleting OpsCenter Data Collectors This section provides procedure for deleting Data Collector configurations from an Agent. In the OpsCenter console. Click Delete Data Collector. click Settings > Configuration > Agent. Modify blackout period settings. Click Edit Data Collector.

Name or IP address of the master server that is configured. Table 5-9 Option Add/Edit/Delete NetBackup options Description Select Add to add a NetBackup master server to the OpsCenter console. Network Name Display Name Operating System Product . The Network Name of a master server cannot be edited. Select Delete to delete one or more master servers from the OpsCenter console. you must add this server to the OpsCenter console so that it can be monitored.362 Understanding data collection About configuring data collection for NetBackup ■ ■ ■ ■ ■ ■ About the Breakup Jobs option Viewing master server details and data collection status Adding a master server in OpsCenter Editing a master server in OpsCenter Deleting a master server in OpsCenter Controlling data collection for a master server in OpsCenter Settings > Configuration > NetBackup options A description of the Settings > Configuration > NetBackup options follows in the table. Backup product and version from where the data is collected. Disable/Enable Data Collection Select Disable Data Collection or Enable Data Collection to disable or enable data collection from one or more NetBackup master servers. After configuring the master server. Select Edit to edit the properties of a master server. Operating system of the master server. The display name that you have chosen for the master server. Deleting a master server removes all the data that is associated with the master server from the OpsCenter database. Note that you must first configure the master server to allow server access and data collection by OpsCenter. See “Adding a master server in OpsCenter” on page 377.

The last time that OpsCenter successfully initiated contact with the particular master server. Operating system of the master server. The display name that you have chosen for the master server. The Last Contact column does not necessarily represent the last time that OpsCenter collected information from the master server. The master server can show any of the following states: ■ ■ ■ ■ State Connected Partially Connected Not Connected Disabled See “Master server states in OpsCenter” on page 376. The table that appears in this view shows the following columns: Network Name Name or IP address of the master server that is configured.Understanding data collection About configuring data collection for NetBackup 363 Table 5-9 Option Last Contact NetBackup options (continued) Description The last time that OpsCenter successfully initiated contact with the particular master server. NetBackup data collection view This view is displayed when you select Settings > Configuration > NetBackup from the OpsCenter console. Display Name Operating System Product Last Contact . Backup product and version from where the data is collected. This view shows details of master servers. The Last Contact column does not necessarily represent the last time that OpsCenter collected information from the master server.

OpsCenter may not capture any changes that were made to the NetBackup configuration. but no local database. OpsCenter collects data from the NetBackup master servers. NBSL provides a single point of access to key NetBackup data. The NetBackup data collection and management logic that OpsCenter uses is built into NetBackup master servers. and reporting functions. manage. Note: OpsCenter only uses the NBSL on master servers for data collection.0 release of NetBackup. OpsCenter correctly recaptures the latest state. Though NBSL is also included on media servers. . This logic is included in the NetBackup Service Layer (NBSL). objects. See “Data collection status of a master server” on page 373. and policies. Starting with the 6. NetBackup Service Layer (NBSL) components are included as a part of NetBackup on master and media servers.364 Understanding data collection About configuring data collection for NetBackup State The master server can show any of the following states: ■ ■ ■ ■ Connected Partially Connected Not Connected Disabled See “Master server states in OpsCenter” on page 376. The NetBackup UI also uses NBSL. You must add only master servers to the OpsCenter console. OpsCenter does not use it. You must not add any media servers to the OpsCenter console. and control functions. clients. OpsCenter uses NBSL for all NetBackup monitoring. management. managing. How OpsCenter collects data from NetBackup OpsCenter is used to monitor. OpsCenter gets affected. When NBSL restarts. To perform the monitoring. If NBSL stops. NBSL runs as a service or daemon and has local configuration information. and change events. and report on NetBackup master and media servers. If NBSL service stops running on a managed NetBackup server.

If you change the PBX . jobs. scheduled jobs.0 MP7 master server.x master servers. For 7. As soon as the initial data load is complete.x master servers. or when the data collection for a master server is enabled after a long time. See “Adding a master server in the OpsCenter console” on page 385. In this case. and breakup jobs data). images.Understanding data collection About configuring data collection for NetBackup 365 Note: A NetBackup 7. The OpsCenter server software collects data from NBSL in the following ways: ■ ■ Initial data load Listening for change notifications Whenever OpsCenter server software starts. you cannot collect scheduled jobs and breakup jobs data. the OpsCenter server can start collecting data from the master server.0 MP7 master server. 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. 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. and you uninstall and then reinstall NetBackup on the master server. drives etc. The initial data load happens serially for each data type. To begin data collection from the master server. OpsCenter server software listens to the notifications from NBSL for any change in NetBackup data. error log. you must delete the master server from the OpsCenter console and then add the master server again.0. Hence for a 6.1 master server does not require any OpsCenter Agent or data collector for data collection. an Agent must be installed only if you want to collect specific data (image. the OpsCenter server starts collecting all the available data from NetBackup master server into the OpsCenter database using NBSL. an Agent must be installed only if you want to collect image data and error logs data. For 6. Once you add the master server in the OpsCenter console. an Agent must be installed only if you want to collect breakup jobs data. For 6. Consider a scenario where a master server is already added on the OpsCenter console. it may take some time for the OpsCenter server to collect all data (such as media. and updates the OpsCenter database.5. when data collection for a master server is enabled or when a master server is added to OpsCenter. Note: Consider a scenario when you add a master server or when OpsCenter Server software starts after a long time.) from the NetBackup master server and insert it into the OpsCenter database. The default PBX port that is used is 1556. In this case.

1 master servers is available. You can enable or disable the Breakup Jobs functionality for master server versions earlier than 7. the load on the Agent (applicable for master servers earlier than 7.1 is available. you can configure the same in OpsCenter while adding or editing a master server. See “Settings > Configuration > NetBackup > Add Master Server options” on page 381. About the Breakup Jobs option This section describes the NetBackup-specific Breakup Jobs option that you can set in Symantec OpsCenter Analytics while adding a master server. you must configure the scl. . More information on how you can enable the Breakup Jobs functionality for 7. The Breakup Jobs functionality was earlier available in Veritas Backup Reporter (VBR).1 master servers. More information on how to enable or disable the Breakup Jobs functionality for master server versions earlier than 7. file count. Note: Enabling the Breakup Jobs option increases the load on the master server. detailed file-level information like size and backup file count for each backup selection (associated with a NetBackup job) is collected and displayed as a part of custom reports in Symantec OpsCenter Analytics.1 master servers.366 Understanding data collection About configuring data collection for NetBackup port on the NetBackup master server. See “ Configuring the Breakup Jobs option for master servers” on page 368.1).1. and the time it takes to gather and load data in OpsCenter. In addition to other job attributes. you can see how much data was backed up per file system. To enable the Breakup Jobs functionality for master server versions earlier than 7. select the Enable Breakup Job data collection option from the Advanced Data Collection Properties section.1. The Breakup Jobs functionality is most effective if you have multiple backup selection lists in the NetBackup policy.conf file. When the Breakup Jobs option is enabled. You can either enable or disable the breakup job option for master servers. With the Breakup Jobs option. The Breakup Jobs functionality is disabled by default for 7. when the Breakup Jobs option is enabled. To enable the Breakup Jobs functionality for 7. OpsCenter collects a greater level of job detail at a file-system level. The Breakup Jobs option can be enabled or disabled while adding a master server from Settings > Configuration > NetBackup. For example. OpsCenter collects job attributes like size. and directory name from the master server.

) and want to collect breakup jobs data for the master server.Understanding data collection About configuring data collection for NetBackup 367 You can also configure the jobs for which you want to collect breakup job information. you can enable image data collection while adding a master server.1 master servers.1 (like 7.0. 7. By default.1. Review the following considerations with respect to the Breakup Jobs functionality: ■ The Breakup Jobs functionality is specific to NetBackup and does not apply to any other product. More information about deploying the OpsCenter Agent is available. For 7.1.1 etc.5. For NetBackup master servers earlier than 7. the OpsCenter Agent collects the breakup jobs data from the NetBackup master server. See “About OpsCenter Agent deployment” on page 95.0. Hence if you have a master server version earlier than 7.0. This includes NetBackup 6. and 7. the breakup jobs data is collected directly from the master server by NBSL.0 MP7.1. For NetBackup master servers before 7. The Breakup Jobs option is only valid for the backup jobs and Archive jobs whose Job State is Done. See “Adding a master server in the OpsCenter console” on page 385.0 MP5 etc. The breakup jobs data is not collected for the jobs that already exist in the OpsCenter database.1 master servers. 7. The Breakup Jobs data collection happens through image ID's. Note that the Breakup Jobs functionality is not supported for NetBackup 6. For NetBackup 7.5. 7.). 6.0 MPx master servers (like 6. Symantec recommends that you enable image data collection for the master server if you want to collect the breakup jobs data. breakup job information is not collected for jobs whose file count is greater than 1000000. 6. See “ Configuring the Breakup Jobs option for master servers” on page 368. The OpsCenter Agent uses the bplist command to collect data from the NetBackup master server.*. The Breakup Jobs data collection only happens for the jobs that are collected after you upgrade to Symantec OpsCenter Analytics 7. ■ ■ ■ ■ ■ ■ . Data for the breakup jobs is collected from NetBackup after every 15 minutes. you must install the OpsCenter Agent. The job selection is based on the maximum number of files that a job backs up. This applies to all master server versions.0. The Breakup Jobs functionality supports the NetBackup master server versions starting from 6.5.1. the image data collection happens automatically by NBSL.1 master servers.

bat stop UNIX /opt/SYMCOpsCenterServer/bin/opsadmin. By default. You can configure the scl.conf file to enable the Breakup Jobs option for 7. To enable the Breakup Jobs option for 7. See “About breakup jobs considerations” on page 371.conf file. the breakup job information from VBR is migrated to the OpsCenter database.1.1 master servers only.1 master servers 1 Log on to the OpsCenter Server host. Configuring the Breakup Jobs option for master servers You can configure the Breakup Jobs option for master servers from the scl. You can also configure the jobs for which you want to collect breakup job information.368 Understanding data collection About configuring data collection for NetBackup ■ The Breakup Jobs functionality applies to Symantec OpsCenter Analytics only. Stop all OpsCenter Server services on Windows and UNIX: Windows INSTALL_PATH\OpsCenter\server\bin\opsadmin.sh stop 2 Open scl.conf applies to 7. If you upgrade from VBR to Symantec OpsCenter Analytics 7. Note that enabling or disabling the Breakup Jobs option using scl.1 master servers (disabled by default).conf file from the following directory on Windows and UNIX: Windows INSTALL_PATH\OpsCenter\Server\config\scl. The job selection is based on the maximum number of files that a job backs up.conf UNIX /opt/SYMCOpsCenterServer/config . ■ See “Viewing the data collection status for breakup jobs” on page 370. See “About viewing breakup jobs data in custom reports” on page 370. The Breakup Jobs functionality cannot be used with Symantec OpsCenter (free version). breakup job information is not collected for jobs whose file count is greater than 1000000. Note: Enabling the Breakup Jobs option increases the load on the master server and the time it takes to gather and load data in OpsCenter. This applies to all master server versions.

bat start UNIX /opt/SYMCOpsCenterServer/bin/opsadmin. Stop all OpsCenter Server services on Windows and UNIX: Windows INSTALL_PATH\OpsCenter\server\bin\opsadmin.collector. add the following text to scl.1 master servers. add the following text to scl.scl.conf file: #nbu.bat stop UNIX /opt/SYMCOpsCenterServer/bin/opsadmin.conf UNIX /opt/SYMCOpsCenterServer/config .collector.conf file: nbu. To enable the Breakup Jobs option for 7.Understanding data collection About configuring data collection for NetBackup 369 3 The Breakup Jobs option is disabled by default.scl.1 master servers. Restart all OpsCenter Server services on Windows and UNIX: Windows INSTALL_PATH\OpsCenter\server\bin\opsadmin.enableBreakupJobDataCollection=false 4 5 Save scl.conf file.conf file from the following directory on Windows and UNIX: Windows INSTALL_PATH\OpsCenter\Server\config\scl.enableBreakupJobDataCollection=true Note: To disable the Breakup Jobs option for 7.sh stop 2 Open scl.sh start To specify the maximum file size of jobs for Breakup Job data collection 1 Go to theOpsCenter Server host.

check the status for the SubJobs data type.bat start UNIX /opt/SYMCOpsCenterServer/bin/opsadmin. However. add the following text to the scl.000 files. To view breakup jobs data in Symantec OpsCenter Analytics.scl. Click the master server from the Network Name column and then click the Data Collection Status tab.conf file: nbu.sh start Viewing the data collection status for breakup jobs You can also view the data collection status for breakup jobs data for a specific master server. 4 5 Save scl. ensure that the Breakup Jobs option is enabled in OpsCenter and then create a custom report of category Backup/Recovery and subcategory BackupJob/Image/Media in a tabular format. breakup job information is not collected for jobs that back up more than 1000000 files. To view the breakup jobs data collection status.collector. you can configure the jobs for which you want to collect breakup job information based on maximum number of files that a job backs up. This applies to all master servers. Restart all OpsCenter Server services on Windows and UNIX: Windows INSTALL_PATH\OpsCenter\server\bin\opsadmin. if you do not want to collect breakup job information for jobs that back up more than 20. To view the breakup job data collection status for a master server 1 2 3 Go to the Settings > Configuration > NetBackup view in the OpsCenter console.370 Understanding data collection About configuring data collection for NetBackup 3 By default.breakupJobMaxFileCountPerJob=20000 Once you complete this procedure. You can see the breakup jobs data by creating custom reports in Symantec OpsCenter Analytics. . About viewing breakup jobs data in custom reports The Breakup Jobs option provides more granular-level reporting on the files that are backed up by NetBackup. For example.conf file. This applies to all master server versions. breakup job information is not collected for jobs whose file count is greater than 20000.

Backup Sub Job Size) is available only for 50 job directories. The Other job directory exists in cases when the total backup size that we get from the primary job is different from the summation of the sizes of the individual files in the file list. breakup jobs data for only 50 backup selections is available with NetBackup. you may notice some job directories named Other in addition to the actual job directories from NetBackup. the breakup jobs are tightly coupled with jobs and are purged along with the jobs. When a NetBackup policy or job has more than 50 backup selections. Hence you see some additional file system objects named “Other” in OpsCenter other than the actual list that comes from NetBackup. To keep the total backup size consistent. Figure 5-1 Sample custom report that shows breakup jobs data In this example. The NetBackup GUI truncates data for the subsequent backup selections (greater than 50). This report helps you to know how much data was backed up per job directory. For a specific job ID in an OpsCenter custom report. About breakup jobs considerations Review the following considerations with respect to the Breakup Jobs functionality: ■ Unlike VBR. breakup job data (like Backup Sub Job File Count. a new job directory named Other is shown to make up the difference. In OpsCenter.Understanding data collection About configuring data collection for NetBackup 371 The custom report shows the following additional columns: ■ ■ Backup Sub Job File Count Backup Sub Job Size Figure 5-1 is a sample custom report that shows the breakup jobs data for each job directory. ■ . OpsCenter does not provide the option to purge breakup jobs.

About NetBackup versions that OpsCenter 7. The NetBackup master servers that OpsCenter manages are referred to as managed NetBackup servers. The details for the master server are shown at the bottom of the Settings > Configuration > NetBackup view under the following tabs: General This tab displays the contents of many of the columns that are displayed in the table. See NetBackup High Availability Administrator's Guide for more details on setting up a NetBackup cluster environment.1 can monitor and manage all NetBackup versions between 6.1. The OpsCenter Server must be at an equal or higher version than the NetBackup master server version that it monitors.1 can monitor and manage OpsCenter 7. OpsCenter can also be used to monitor a NetBackup cluster.0 MP7 and 7. This information is displayed as data is collected by using CLI's and not NBSL. Starting with the 6. NetBackup Service Layer (NBSL) components are included as a part of NetBackup on master servers.372 Understanding data collection About configuring data collection for NetBackup With VBR you can view breakup job information for all job directories for a job or policy. These managed NetBackup servers harvest pertinent NetBackup data and store it in the OpsCenter database. Each managed NetBackup master server that OpsCenter manages must have NBSL present and in operation. ■ OpsCenter Analytics does not show deduplication or snap duplication data for a specific job directory in the custom reports. OpsCenter Analytics does not show deduplication or snap duplication data because deduplication or snap duplication data for a backup selection is not available with NetBackup. Also review the OpsCenter sections of the NetBackup release notes before using OpsCenter for monitoring NetBackup clusters.0 release of NetBackup. . Viewing master server details and data collection status Use the following procedure to view the details for a master server.

It also lists details like the time when the data load was last successful. Table 5-10 Column Data Type Data Collection Status view Description The type of data that is collected from NetBackup. 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. when data collection last happened. See “NetBackup data types and collection status” on page 374. See “Data collection status of a master server” on page 373. To view master server details and data collection status for a master server 1 2 In the OpsCenter console. The details for the master server are shown at the bottom of this view. and the exception message if the data collection failed for any of the data types. . Figure 5-2 shows a sample data collection status view for a master server. Click the name of the master server (link) from the Network Name column.Understanding data collection About configuring data collection for NetBackup 373 Data Collection Status This tab displays the collection status for each of the data types. Figure 5-2 Sample Data Collection Status view Table 5-10 gives a description of the contents in the Data Collection Status tab. select Settings > Configurations > NetBackup.

This column provides the status of each data load activity that OpsCenter requests. service. services.374 Understanding data collection About configuring data collection for NetBackup Table 5-10 Column Data Collection Status view (continued) Description This column lists the date and time when the last successful data load happened for the specific data type. and devices. For most operations and changes in NetBackup.) by using NBSL. Last Successful Data Load Last Run Time Collection Status Last Exception Message NetBackup data types and collection status OpsCenter collects data for many NetBackup data types (such as jobs. The following are the collection statuses for the different data types and their description: . This column lists the date and time when data collection was attempted. policy. the notification also contains the changed data. policy. media server. This data is stored in the OpsCenter database. This column lists the last exception message if data collection failed for a data type. storage unit etc. For changes such as job. NBSL sends notifications to OpsCenter.

and then start after some time. The data collection for the specific data type is queued. FT data types. The data collection for the specific data type is complete.Understanding data collection About configuring data collection for NetBackup 375 Table 5-11 Collection status Not Applicable Collection statuses Description This status may come when the master server version does not support the specific data type. Queued Running Completed Failed Note: Data collection can fail. you can see the exception message from the Last Exception Message column.1 and you have not configured data collection for the following data types: ■ ■ ■ ■ Error Logs Scheduled jobs Image Breakup Jobs You can enable data collection for these data types while adding or editing a master server under Advanced Data Collection Properties section. The data collection for the specific data type has failed. When the data collection fails. NetBackup 6. . For example. it should be automatically started again within 10 minutes. If data collection for a particular data type fails. This is normal behavior. All the functionality other than the functionality of the failed data type can be used normally while collection for a data type fails.0 does not support disk. Not Started The data collection for the specific data type has not started. This may happen when you initially add a master server or when you start the OpsCenter server. The data collection for the specific data type is in progress. See “Master server states in OpsCenter” on page 376. This status also comes when your master server version is lower than 7. See “Editing a master server in OpsCenter” on page 386. Not Licensed This status is seen when the specific data type like FT is not licensed in NetBackup. See “Adding a master server in the OpsCenter console” on page 385.

and then start after some time. The master server can have any of the following states: Table 5-12 Master server states Description The master server is Connected when the data collection status for all data types is not Failed. Disabled The master server is Disabled when the data collection for the selected master server is disabled. Master server states in OpsCenter This section lists the different states that can exist for a master server and what they mean.376 Understanding data collection About configuring data collection for NetBackup See “Data collection status of a master server” on page 373. All the functionality other than the functionality of the failed data type can be used normally while collection for a data type fails. disk etc. fails. data collection for catalog data type is Completed but data collection for client. If data collection for a particular data type fails. Master servers may show as Partially Connected temporarily for some time. If data collection for a particular data type fails. Not Connected The master server is Not Connected when the data collection for all data types fails. it should be automatically started again within 10 minutes. and then start after 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. This means that the collection status for all the data types must be any other status except Failed. This may be when there is a network issue because of which OpsCenter is not able to connect and collect data from NetBackup. device. This is normal behavior. For example. This is normal behavior. 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. it should be automatically started again within 10 minutes. This is because data collection can fail. . Master server state Connected Partially Connected Note: Data collection can fail.

This procedure can be used for both NBAC and non-NBAC servers. Note that you must first configure the master server to allow server access and data collection by OpsCenter.0. . Note: Symantec recommends that any NetBackup master server be monitored by only one OpsCenter server. See “Adding a NetBackup 7. After configuring the master server. or 7.0 or later master server” on page 377. OpsCenter can monitor the master servers which have NetBackup Access Control (NBAC) configured and also those servers that do not have NBAC configured. This procedure can be used for both NBAC and non-NBAC servers. See “Configuring a master server for server access and data collection by OpsCenter” on page 379.1. Note: You can use an alternate procedure to add a NetBackup 7. you must add the master server to the OpsCenter console so that it can be monitored.0 or later master server to OpsCenter. In case of a clustered NetBackup setup.0. 7.0 or later master server Use the following procedure to add a NetBackup 7. Use the following steps to add a master server. To add a master server 1 Configure your managed master server to allow server access and data collection by OpsCenter. you must add this server to the OpsCenter console so that it can be monitored.Understanding data collection About configuring data collection for NetBackup 377 Adding a master server in OpsCenter To allow OpsCenter to communicate with a managed NetBackup server and collect data requires some security configuration. use this procedure for each node of the cluster.1 master server to the OpsCenter console. See “Adding a master server in the OpsCenter console” on page 385. Adding a NetBackup 7. 2 After configuring the master server.

.0 or later master 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. a command that is called nbregopsc has been added to NetBackup 7.0 and later versions. a new entry that is called OPS_CENTER_SERVER_NAME has been added to the bp. This command also establishes a trust relationship from the authentication broker of NetBackup master server to the authentication broker of OpsCenter server. The nbregopsc command registers OpsCenter with the current master server and adds this master server to OpsCenter.378 Understanding data collection About configuring data collection for NetBackup To add a NetBackup 7. In addition. 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.conf file.

1 master server 7. Note: In case running the nbregopsc command fails. you must manually add the master server to the OpsCenter console. However if the master server is NBAC-enabled. . 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. the master server is automatically added to the OpsCenter console. See “Adding a master server in the OpsCenter console” on page 385. OpsCenter cannot monitor NetBackup servers if the trust relationship has not been set up between OpsCenter and NetBackup server.1 or later master server vssat setuptrust --broker <MasterServerhost:2821> --securitylevel high vssat setuptrust --broker <MasterServerhost:13783> --securitylevel high Note that <MasterServerhost> is the name of the master server. a trust relationship must be established from the authentication broker of the OpsCenter server to the authentication broker (AB) of the NetBackup master server. run the following command depending on your specific master server version: 7.0 and 7. 5 Restart all the NetBackup services (processes).Understanding data collection About configuring data collection for NetBackup 379 4 Ignore this step for master servers for which NBAC is not configured. To establish the trust relationship. log on as Administrator or root on the OpsCenter server host and navigate to the following location: Windows %Program Files%\Veritas\Security\Authentication\bin /opt/VRTSat/bin UNIX On the OpsCenter server host. This procedure applies to both NBAC and non-NBAC master servers.0. Once you perform this procedure.

x. The Add a New Server Entry dialog box appears.1. However. To add the OpsCenter server to the server list. it is recommended that the following procedure be used for NetBackup 7. use this procedure on each node of the cluster. Start the NetBackup Administration Console.0 and later servers. 8 9 Click Close. select the Servers tab to display the server list. The Master Server Properties dialog box appears. 7. Note: This procedure applies to all master server versions including 7. Ensure that the OpsCenter server name that you add is reachable from the NetBackup server. Expand NetBackup Management > Host Properties > Master Servers. . See “Adding a master server in the OpsCenter console” on page 385. In the Master Server Properties dialog box.380 Understanding data collection About configuring data collection for NetBackup In case of a clustered NetBackup setup.0. From the Master Server Properties dialog box. click Add. To configure a master server for server access and data collection 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. Type the OpsCenter server name in the field and click Add to add the server to the list. click OK. Double-click the master server name to view its properties.

Similarly. run the following command: vssat setuptrust --broker <OpsCenterABhost:2821> --securitylevel high where <OpsCenterABhost> is same as the host where OpsCenter server is installed. On the NetBackup master server host. Settings > Configuration > NetBackup > Add Master Server options Enter the following detailsforthemasterserverunder GeneralProperties and AdvancedProperties sections: . However if the master server is NBAC-enabled. To set up these trust relationships. use the vssat command in Symantec Product Authentication Service.1 or later master server vssat setuptrust --broker <MasterServerhost:2821> --securitylevel high vssat setuptrust --broker <MasterServerhost:13783> --securitylevel high where <MasterServerhost> is the name of the master server. log on as Administrator or root on the OpsCenter server host and run the following command depending on your specific master server version: 7. See “Adding a master server in the OpsCenter console” on page 385.0. Run this command from %Program Files%\Veritas\Security\Authentication\bin directory in Windows or /opt/VRTSat/bin in UNIX.Understanding data collection About configuring data collection for NetBackup 381 10 Ignore this step for master servers on which NBAC is not configured. then <OpscenterAB> is the host name that is provided as the remote authentication broker host during the OpsCenter installation.1 master server 7. 11 Restart all the NetBackup services. 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. However if OpsCenter is installed in a clustered mode. 12 Add this master server to the OpsCenter console so that it can be monitored.0 and 7. OpsCenter cannot monitor NetBackup servers if the trust relationship has not been set up between OpsCenter and NetBackup server (NBAC enabled).

The OpsCenter server tries to connect to the master server. Display Name Enter an alternate name for the server. Install an Agent if you want to collect data for breakup jobs.1: NetBackup version 6. In case the master server is clustered.1 master server. all data is collected automatically by NBSL and OpsCenter Agents do not need to be installed on the 7. NetBackup PBX port The NetBackup PBX port allows all socket communication to take place while connecting through a single port. or breakup jobs.1. For NetBackup 7. Locate option The Advanced Data Collection Properties section is applicable if your NetBackup master server version is lower than 7. click Locate to locate the master server. You can select a preferred network address from the drop-down list. Note that this field is required.x . OpsCenter's Preferred network address The OpsCenter server may have multiple network interface cards (NIC).x Data Collection Install an Agent if you want to collect data for image or error logs.x 7.0.1. Note that this field is required.0. OpsCenter uses the address that you select to connect to the master server. The default NetBackup PBX port is 1556. 6. scheduled jobs.5.382 Understanding data collection About configuring data collection for NetBackup Table 5-13 Option Network Name General Properties and Advanced Properties options Description Enter a host name or an IP address. enter the virtual name of the master server. error log. This field is required. After entering the above details. Install an Agent if you want to collect data for image. You can configure an Agent to collect the following data from master server versions below 7. The display name is used for the master server on all views of the OpsCenter console.

select the appropriate master server version manually from the drop-down list. You can create an OpsCenter Agent from Settings > Configuration > Agent > Create Agent.0.x 7. You can select from the following versions: ■ ■ ■ ■ 6. error log. scheduled jobs.x Agent Select an agent from the drop-down list. the appropriate NatBackup version is automatically selected in the NetBackup version drop-down list. no agent is configured.5.. 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. Enter the following details under Advanced Data Collection Properties section: Table 5-14 Option NetBackup version Advanced Data Collection Properties options Description When you click Locate and OpsCenter server can successfully connect to the master server. In case of remote data collection. In case the Locate operation fails and OpsCenter fails to connect to the master server.x 6.x 7.1.Understanding data collection About configuring data collection for NetBackup 383 Note: The data for image.0. In case. this is the path on the OpsCenter Agent host where RAC (Remote Admin Console) is installed. Install Directory The directory path on the OpsCenter Agent host where the NetBackup application is installed. See “Configuring an OpsCenter Agent” on page 355. click Configure Agent. 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 . and breakup jobs is used in OpsCenter reports.

x or 6. Enable Breakup Job Data Collection Click the checkbox if you want to break up a job (using data from the NetBackup's catalog) so that the size and backup file count have finer granularity. This option appears only when you add 6. For 6.0 MP7 master servers.1 master servers. For 6. you cannot collect scheduled jobs data.0 MP7 master servers. This option appears only when you add 6. The breakup jobs data is automatically collected for 7.x master servers.5. This option appears only when you add 6.5.0. Note that you must enter the value in Username and Password fields so that scheduled job data can be collected.5.384 Understanding data collection About configuring data collection for NetBackup Table 5-14 Option Advanced Data Collection Properties options (continued) Description Click the checkbox if you want to enable image data collection from the master server. This feature is most effective if you have multiple paths in your backup selection lists in NetBackup.x master servers. and the time it takes to collect and load data in OpsCenter.x master servers. Enable Image Data Collection Enable Error Log data Collection Click the checkbox if you want to enable error log data collection from the master server.x or 6.5.x. you cannot collect breakup jobs data.0. Note: Enabling this option increases the load on the OpsCenter Agent.x master servers. This option appears only when you add 6. . or 7.0. Enable Scheduled Job Data Collection Click the checkbox if you want to enable scheduled job data collection from the master server. the master server.

This is required if you enable scheduled job data collection. and specify valid NetBackup admin credentials. Note: The Password field is disabled if Enable Scheduled Job Data checkbox is unchecked. To add a master server 1 2 In the OpsCenter console. Click Add. Save / Cancel options Click Save to add the master server. Note: Username and Password is not needed if the agent is installed on NBU master server. Adding a master server in the OpsCenter console You must add a master server to the OpsCenter console so that it can be monitored. Click Cancel to exit and go back to the Settings > Configuration > NetBackup page.Understanding data collection About configuring data collection for NetBackup 385 Table 5-14 Option Username Advanced Data Collection Properties options (continued) Description Enter the user name to access the NetBackup master server. Password Enter the password of the NetBackup user account. . Note: The Username field is disabled if Enable Scheduled Job Data checkbox is unchecked. Use the following procedure to add a master server. select Settings > Configurations > NetBackup . 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. If you want to collect the scheduled jobs data remotely. A user name is required if you enable scheduled job data collection. using the nbpemreq CLI.

For NetBackup 7. The data for image. Click Edit. this data is collected automatically by NBSL and OpsCenter Agents do not need to be installed on the 7. 5 Editing a master server in OpsCenter Use the following procedure to change the configuration information for a NetBackup master server To edit a master server 1 2 3 In the OpsCenter console. and breakup jobs is used in OpsCenter reports. scheduled jobs. Alternately.1. Enter the details under Advanced Data Collection Properties section. error log. Click Save to add the master server.386 Understanding data collection About configuring data collection for NetBackup 3 Enter the detailsforthemasterserverunder GeneralProperties and AdvancedProperties sections . you can click Cancel to exit. scheduled jobs. . error log. you must install an Agent to collect the data for image. See “Settings > Configuration > NetBackup > Add Master Server options” on page 381. An error appears if OpsCenter cannot connect to the NetBackup master server on the network. select Settings > Configurations > NetBackup. The Advanced Data Collection Properties section is applicable if your NetBackup master server version is lower than 7. 4 Click Locate to check if OpsCenter can connect to the master server. or breakup jobs as per the master server version. See “Settings > Configuration > NetBackup > Add Master Server options” on page 381. if applicable.1. Use the checkbox to select a master server from the Network Name column.1 master server. For master server versions below 7.1.

5 Click Save. Advanced Properties. Use the checkbox to select one or more master servers from the Network Name column. Click Delete. Deleting a master server in OpsCenter You can delete one or more master servers using the following procedure. Controlling data collection for a master server in OpsCenter You can disable or enable OpsCenter data collection for a particular managed NetBackup master server depending on your needs. Note that you cannot edit the Network Name for the master server. For example. a drive may have the same status until you enable OpsCenter data collection again. . To delete a master server 1 2 3 4 In the OpsCenter console. The following warning message appears: Deletion of the selected master server(s) will delete all related data. and Advanced Data Collection Properties sections. Note that deleting a master server deletes all the data that is associated with the master server. You can change the data that is shown for General Properties. Do you want to proceed? Click OK. The Network Name field falls under the General Properties section. A description of the fields present in these sections is available. See “Adding a master server in the OpsCenter console” on page 385. Note: Deleting a master server may take some time.Understanding data collection About configuring data collection for NetBackup 387 4 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.

Click Enable Data Collection. for which you want to configure a Data Collector.exe VC Redistributable Package is available at: http://www. Use the checkbox to select one or more master servers from the Network Name column.aspx?familyid=200B2FD9-AE1A-4A14-984D-389C36F85647&displaylang=en Once you install this component on the Agent host.com/downloads/details. To configure Backup Exec data collector 1 2 3 4 5 6 Click Settings > Configuration > Agent. On the Agent list. Use the checkbox to select one or more master servers from the Network Name column. select Settings > Configurations > NetBackup. select a check box in front of the Agent. Click Create Data Collector. to collect data properly. On the CreateDataCollector:ProductSelection page. configure the Backup Exec data collector as described in the following section.388 Understanding data collection Configuring Backup Exec data collector To disable data collection for a master server 1 2 3 In the OpsCenter console. select Symantec Backup Exec from the Select Product drop-down list. Click Next. Microsoft Visual C++ 2005 SP1 Redistributable Package (x86) that is vcredist_x86. enter the Backup Exec Server host name. Configuring Backup Exec data collector This section describes data collection from Backup Exec. In the Target Host Name text box. Click Disable Data Collection. To enable data collection for a master server 1 2 3 In the OpsCenter console. Caution: The Backup Exec data collector requires the following component to be installed on the OpsCenter Agent host. .microsoft. from which you want to collect data. select Settings > Configurations > NetBackup .

x. data types to be collected. 9 Click Save. or 12. Enter the password of this user account. refer to the following section: See “ Configuring an OpsCenter Data Collector” on page 358. Collecting data from PureDisk OpsCenter supports collection of data from Symantec NetBackup PureDisk. and other data collector settings.x . refer to the Symantec NetBackup PureDisk documentation. While backing up a file. By using the deduplication technology.10. such as name and date of modification can vary. PureDisk identifies files and the data segments that contain identical data and treats them as a single instance of a file. which it backs up only once. including remote hosts. Select the version of the Symantec Backup Exec server . This lets you save storage space. PureDisk SPA and its components that run on the PureDisk operating system (PDOS). The Single Instance Storage (SIS) or deduplication technology of NetBackup PureDisk is unique in storage and backup industry. PureDisk determines whether multiple instances of the file are present on hosts across the network.x. The collected data is stored in the OpsCenter database. Password Version 8 Select blackout period details. For more details on collection interval. For more details on PureDisk. . PureDisk stores only one instance of the file. Table 5-15 describes the steps that you need to carry out to collect data from PureDisk. and collection interval.Understanding data collection Collecting data from PureDisk 389 7 On the Create Data Collector: Details page.from which you want to collect data. Attributes of identical files. 11. 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 . based on which you can generate reports. OpsCenter can collect Policy & Schedule and Job data types from PureDisk Storage Pool Authority (PureDisk SPA).

This is a pre-requisite for PureDisk data collection from OpsCenter. Step number Step Step 1 Install OpsCenter server. SPA host and OpsCenter AB host” This is a pre-requisite for PureDisk data collection on page 390.390 Understanding data collection Collecting data from PureDisk Table 5-15 Steps to collect data from PureDisk Reference topic See “Installing Symantec OpsCenter on Windows and UNIX” on page 106. Step 3 See “Setting up a trust between the PureDisk SPA host and OpsCenter AB host” on page 390. from OpsCenter. Note: You can collect PureDisk data only through the OpsCenter Integrated Agent. Step 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. See “Configuring PureDisk data collector” on page 391. you do not need to manually install or configure OpsCenter Agent.OpsCenter Integrated Agent is also installed and configured. . configure PureDisk See “Configuring data collector for the Integrated Agent. Using the OpsCenter console. You cannot delete the Integrated Agent. Note: When you install OpsCenter server. PureDisk data collector” on page 391. To collect PureDisk data. which you can use to collect only PureDisk data. 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.

The OpsCenter AB hostname is stored in the vxss. To set up a trust between PureDisk SPA host and OpsCenter AB host 1 On the PureDisk SPA host. run the following command: /opt/VRTSat/bin/vssat setuptrust --broker OpsCenterABhost:2821 --securitylevel low After successfully setting up a trust between the PureDisk SPA host and OpsCenter AB host. logon as root and run the following command: su www-data 2 As a “www-data” user.conf This section provides the manual steps that you need to carry out on the PureDisk SPA host. if OpsCenter is installed in a clustered mode. the following message is displayed: setuptrust ------------------------------------------Setup Trust With Broker: OpsCenterABhost Note: Setting up a trust between the OpsCenter AB host and PureDisk SPA host from the OpsCenter AB host is accomplished automatically after the PureDisk data collector is configured. Configuring PureDisk data collector This section provides the procedure to configure NetBackup PureDisk data collector on the OpsCenter UI.Understanding data collection Collecting data from PureDisk 391 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. .conf On UNIX: /opt/SYMCOpsCenterServer/config/security. However.hostname parameter in the following file: On Windows: C:\Program Files\Symantec\OpsCenter\server\config\security. then the OpsCenter AB host is the host name that was provided as the remote authentication broker host during the OpsCenter installation.

6.2.OpsCenter Integrated Agent is also installed and configured. To collect PureDisk data.1. select Symantec NetBackup PureDisk from the Select Product drop-down list. About collecting data from Enterprise Vault The following topics provide information about Enterprise Vault Data Collector configuration. 8 Click Save.0. 6. 6. 6. you do not need to manually install or configure OpsCenter Agent.6.6. Setting up a trust between the OpsCenter authentication broker host and PureDisk SPA host is accomplished automatically after PureDisk data collector is configured.1. from which you want to collect data. Refer to Setting up a trust between the OpsCenter AB host and PureDisk SPA host in the OpsCenter Administrator's Guide. which you can use to collect only PureDisk data. you need to do it manually. 3 4 5 6 7 Click Create Data Collector. On the Create Data Collector: Details page. 6. refer to the following section: See “ Configuring an OpsCenter Data Collector” on page 358.2.2. If it is not successful. See “About Enterprise Vault” on page 393. 6.5.2. When you install OpsCenter server. On the Create Data Collector: Product Selection page.3 For more details on collection interval. specify the following PureDisk configuration settings: Product Version Select any of the following Symantec NetBackup PureDisk versions from the drop-down list: 6. 6.0. enter the PureDisk SPA Server host name. 6.5. Click Next.6.0. .2. select a check box in front of the Integrated Agent. You can collect PureDisk data only through the OpsCenter Integrated Agent. On the Agent list.6.0.1.1.392 Understanding data collection About collecting data from Enterprise Vault To configure NetBackup PureDisk data collector 1 2 Click Settings > Configuration > Agent. and other data collector settings. 6. In the Target Host Name text box.5.

refer to Enterprise Vault documentation. About data collected from Enterprise Vault OpsCenter categorizes the data that is collected from Enterprise Vault database into various data types. See “OpsCenter Agent deployment modes” on page 398. For example. Table 5-16 lists the data types in OpsCenter that represent type of data that is collected from Enterprise Vault. See “Accessing MS SQL Server host” on page 398. OpsCenter collects Policy and Retention Category data from Enterprise Vault database and stores it as Archive Policy data type. 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. See “About creating a user for integrated logon” on page 399. About Enterprise Vault Symantec Enterprise Vault software application provides a flexible framework for archiving emails. See “Configuring Enterprise Vault data collector” on page 403. See “Configuring the OpsCenter Agent properties for integrated logon” on page 401. . See “Planning the Enterprise Vault data collector deployment” on page 396. and collaborative environments. See “Versions supported by OpsCenter” on page 396. It is supported only on Windows platform. file systems. See “Installing MS SQL Server JDBC driver” on page 402.Understanding data collection About collecting data from Enterprise Vault 393 See “About data collected from Enterprise Vault” on page 393.

The data collector collects the information from Enterprise Vault that is associated with the selected data types. Vault Store. See “Configuring Enterprise Vault data collector” on page 403.394 Understanding data collection About collecting data from Enterprise Vault Table 5-16 Enterprise Vault data types Data in Enterprise Vault Policy and Retention Category Vault Store Groups. and Vault Store Partition Mailbox. Figure 5-3 shows the hierarchy of archive data in Enterprise Vault. . Public Folder. . as per the specified schedule. 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.

vault stores.Understanding data collection About collecting data from Enterprise Vault 395 Figure 5-3 Representation of Enterprise Vault data in OpsCenter reports Archive Site Exchange Server Enterprise Vault Server Vault Store Group Vault Store Group Provisioning Group Vault Store Vault Store Vault Store Vault Store Vault Partition Vault Partition Vault Partition Vault Partition ------------------------Archives----------------------- ------------------------Archive Storage----------------------- An archive site is a logical group of hosts that need to be archived (Exchange Servers. Using OpsCenter archive reports you can . storage media (vault store groups. It is at the highest level in the Enterprise Vault data hierarchy. vault partitions). and Enterprise Vault Servers. Provisioning Groups).

and so on. and so on. OpsCenter Agent and MS SQL Server are installed on different hosts. Note: Mailboxes are referred to as targets and an individual email is referred to as an item. Versions supported by OpsCenter OpsCenter supports the following versions of Enterprise Vault. Storage of archived data A few archive reports show details about the storage of archived data. See “About OpsCenter reports” on page 579. depending on which path you follow to drill down the site information. the number of mailboxes that exceed their warning limits per Exchange Server or Provisioning Group. OpsCenter archive reports show only Exchange Server data. For example: details of vault stores and vault partitions where the archive data has been stored.0 2005. These archiving activity reports are available in the Exchange report folder of Archive reports.396 Understanding data collection About collecting data from Enterprise Vault determine the details about both archiving activities and archival storage. In the remote data collection method. OpsCenter reports present archive data in the following two ways: Archiving activities A few archive reports show details about archiving activities. . which you can view reports for. Table 5-17 lists the steps that you need to carry out before configuring the Enterprise Vault data collector for archive-data collection in the OpsCenter console. For example: Details of mailboxes to be archived. It supports all versions of Microsoft SQL Server that the Enterprise Vault supports. you need to configure OpsCenter Agent and data collector using the OpsCenter console. OpsCenter supports local as well as remote archive-data collection. original size of data that has been archived. These are all archiving activities. 8. Enterprise Vault Microsoft SQL Server 7. 2008 Planning the Enterprise Vault data collector deployment Enterprise Vault stores archive metadata in the directory and the Vault Store database.5. To collect the archive metadata from Microsoft SQL Server. or how many emails were archived per Enterprise Vault Server.

See “Installing MS SQL Server JDBC driver” on page 402. which you want to use for integrated logon between Agent host and MS SQL Server host. See “ About creating a user in multi-domain deployment mode” on page 400. You need to configure the Enterprise Vault data collector using the OpsCenter console and schedule data collection. . where the Enterprise Vault data resides. See “About creating a user in standalone deployment mode” on page 400. ■ Single-domain mode ■ ■ Multi-domain mode Standalone mode Step 2 Make sure that the user whose credentials you See “Accessing MS SQL use for the integrated logon has required access Server host” on page 398. where the archive data resides. depending on the OpsCenter Agent deployment mode. See “Configuring Enterprise Vault data collector” on page 403. Step 3 Depending on the deployment mode of the OpsCenter Agent. Step 5 For integrated logon. configure the OpsCenter Agent to run in the context of the user or group that has access to MS SQL Server. Step 4 Install MS SQL Server JDBC driver on the OpsCenter Agent host.Understanding data collection About collecting data from Enterprise Vault 397 Table 5-17 Planning and deployment steps Reference topic Step number Step Step 1 Deploy OpsCenter Agent in any of the following See “OpsCenter Agent ways. rights on the MS SQL Server. add a user in the appropriate domain or workgroup. See “ About creating a user in single-domain deployment mode” on page 399. See “Configuring the OpsCenter Agent properties for integrated logon” on page 401. or you can create a new user in MS SQL Server and give required access rights. to collect archive data remotely: deployment modes” on page 398. This can be an existing user.

This section mainly talks about the remote agent deployment modes. For example. using SQL Server Management Studio Express or any other MS SQL Server client. The OpsCenter Agent host is in a domain different than the SQL Server domain. In addition to single-domain mode. 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. create a user with credentials of username: localadmin and password: pass. However. Table 5-18 Agent deployment modes Description In a single-domain deployment mode. you can deploy the OpsCenter Agent in multi-domain mode. the OpsCenter Agent host and the MS SQL Server host (Enterprise Vault database instance) do not share the same Windows domain. Open the MS SQL Server admin console. To access MS SQL Server host 1 2 Create a Windows domain user on the MS SQL Server host. Deployment mode Single-domain deployment mode Multi-domain deployment mode Standalone deployment mode Accessing MS SQL Server host This section describes how to give the required rights to a user to access MS SQL Server. The OpsCenter Agent host is installed on a standalone host. In this deployment mode. You can deploy the OpsCenter Agent on MS SQL Server host or OpsCenter Server host. In this deployment mode. depending on your setup. the OpsCenter Agent host and the MS SQL Server host (Enterprise Vault database instance) do not share the same Windows domain.398 Understanding data collection About collecting data from Enterprise Vault OpsCenter Agent deployment modes This section describes various deployment modes in which you can deploy OpsCenter Agent. . Add this Windows domain user (local admin) to the MS SQL Server.

Depending on the OpsCenter Agent deployment mode. In the right-hand Server roles pane. in the Object Explorer. expand the Security folder. See “About creating a user in standalone deployment mode” on page 400. in the Select a page pane. The user local admin in the OpsDomain (OpsDomain\localadmin) now has the rights to access MS SQL Server. Note: To report on Enterprise Vault / archive data. where the archive data resides. User name: localadmin and Password: pass) you use for the integrated logon has required access rights on the MS SQL Server. on which you want the access rights. Right-click the user name . On the logon Properties screen. Click Properties.with which you want to perform integrated logon on the Agent host and MS SQL Server host. About creating a user in single-domain deployment mode Make sure that the user whose credentials (for example. select the public check box. 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. 7 8 9 10 Additionally. the procedure to create a logon user varies. See “ About creating a user in multi-domain deployment mode” on page 400. See “ About creating a user in single-domain deployment mode” on page 399.Understanding data collection About collecting data from Enterprise Vault 399 3 Add this user (local admin) to the Enterprise Vault databases. Expand the logons folder.for example username: OpsDomain\localadmin with the password: pass . OpsCenter Agent needs access to the Enterprise Vault directory and storage databases. make sure that the user has datareader rights to access the desired database. select Server Roles. 4 5 6 In the MS SQL Server admin console. where the archive data resides. You need to add the user to these databases and give the required access rights on these databases. .

Use credentials of this user (User name: localadmin and Password: pass) when you configure the Agent properties for integrated logon. If you have deployed the OpsCenter Agent in the single-domain mode. About creating a user in multi-domain deployment mode Make sure that the user whose credentials (for example. See “Configuring the OpsCenter Agent properties for integrated logon” on page 401. If the Agent host is on a different domain as compared to the EV host. See “OpsCenter Agent deployment modes” on page 398. (User name: localadmin and Password: pass) in the Agent host domain that is the Windows domain. or you can create a new user with these credentials in MS SQL Server and give required access rights. See “OpsCenter Agent deployment modes” on page 398. then the user must be created as a local Administrator. create a user. User name: localadmin and Password: pass) you use for the integrated logon has required access rights on the MS SQL Server. . About creating a user in standalone deployment mode Make sure that the user whose credentials (for example. create a user (User name: localadmin and Password: pass) in the Agent host domain. See “Accessing MS SQL Server host” on page 398. or you can create a new user with these credentials in MS SQL Server and give required access rights. where the archive data resides. See “Accessing MS SQL Server host” on page 398. See “Accessing MS SQL Server host” on page 398. 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. See “Configuring the OpsCenter Agent properties for integrated logon” on page 401. If you have deployed the OpsCenter Agent in the multi-domain mode. This is because the Agent domain is not visible to the EV host.400 Understanding data collection About collecting data from Enterprise Vault The user localadmin can be an existing user. where the archive data resides. 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.

click Properties. 4 5 6 7 On the Services screen.who has the rights to access the MS SQL Server. 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. click Browse. However.Understanding data collection About collecting data from Enterprise Vault 401 If you have deployed the OpsCenter Agent in the standalone mode.for example localadmin with the password: pass . 8 Enter a user name in the text box. Use credentials of this user (User name: localadmin and Password: pass) when you configure the Agent properties for integrated logon. select the This account option. This user should have access rights on MS SQL Server. Click Check Names to check whether the user name that is specified is present in the Windows domain or not. in the Open text box. Enter the credentials of the user . 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.msc. . See “Configuring the OpsCenter Agent properties for integrated logon” on page 401. right-click the Symantec OpsCenter Agent service. On the right-click menu. The Windows Services screen is displayed. See “OpsCenter Agent deployment modes” on page 398. Note: Make sure that this user has required rights to access MS SQL Server See “Accessing MS SQL Server host” on page 398. on the services list. click Start > Run. This opens the Select User dialog box. In the Run dialog box. on the Log On tab. Alternatively. enter services. Click Enter. create a user for example (User name: localadmin and Password: pass) in the Administrator workgroup. On the Symantec OpsCenter Agent Properties screen. where the Enterprise Vault archive data resides. To configure OpsCenter Agent properties 1 2 3 On the OpsCenter Agent host (Windows system).

402 Understanding data collection About collecting data from Enterprise Vault 9 Click OK. Click Open to access the end-user license agreement. The SQL Server JDBC Driver 2. To install MS SQL Server JDBC driver 1 Click the following link: Download Microsoft SQL Server JDBC Driver 2.exe file to a desired location.0. SQL Server 2005.0 page. 10 Click OK on the LogOn tab. The File Download dialog box is displayed.0 2 3 On the Microsoft SQL Server JDBC Driver 2. Microsoft provides a Java Database Connectivity (JDBC) driver for use with SQL Server.100_enu. Unzip the sqljdbc_2. The Agent requires the JDBC driver to communicate with the MS SQL Server.100_enu. select the following: I Accept the above agreement and I want to download the Microsoft Windows version The File Download dialog box is displayed. 5 6 Click Save to save the sqljdbc_2. click Download.0. application server. 4 On the MICROSOFT SOFTWARE LICENSE TERMS page. Enterprise Edition 5.0 is available to all SQL Server users at no additional charge. and provides access to SQL Server 2000.1803. you require the SQL Server JDBC driver that is installed on the OpsCenter Agent host. Installing MS SQL Server JDBC driver To collect the Enterprise Vault data residing on Microsoft SQL Server (or MS SQL Server or SQL Server). .1803.exe file. This is a Type 4 JDBC driver that provides database connectivity through the standard JDBC application program interfaces (APIs) available in Java Platform. and SQL Server 2008 from any Java application. or Java-enabled applet.

click Settings > Configuration > Agent .dll and sqljdbc_2. 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.Understanding data collection About collecting data from Enterprise Vault 403 7 Copy sqljdbc_2. To configure Enterprise Vault data collector 1 2 3 4 5 6 7 In the OpsCenter console. Enter the name of the host. Microsoft SQL Server JDBC Driver 8 Restart the Agent service.0\enu\auth\x86\sqljdbc_auth. select Symantec Enterprise Vault from the Select Product drop-down list. The default port number is 1433. Install Dir\Symantec\OpsCenter\Agent\lib where Install Dir is the location where you have installed OpsCenter. See “Configuring the OpsCenter Agent properties for integrated logon” on page 401.jar files to the following location on the Agent host. This data collector collects archive data from MS SQL Server where the Enterprise Vault database resides.0\enu\sqljdbc4. Configuring Enterprise Vault data collector This section provides the procedure to configure the Enterprise Vault data collector in the OpsCenter console. . Click Next. To collect archive data. Click the following link for more information and frequently asked questions on the JDBC driver. By default this field is left blank. On the Create Data Collector: Product Selection page. from where you want to collect the archive data. Click Create Data Collector. Databaseportnumber Enter the port number that is used to connect to the MS SQL Server. On the Agent list. select a check box in front of the Agent for which you want to configure the Data Collector. Enter the following Configuration Settings: Database Instance Name This is the directory database instance name.

See “Enterprise Vault data collection checklist” on page 404. Vault Store.404 Understanding data collection About collecting data from Enterprise Vault 8 9 Specify blackout period details. Archive Policy. refer to the following section: See “ Configuring an OpsCenter Data Collector” on page 358. and Archive. You have specified the collection interval within which you want to collect the archive data. You have selected the data types and events to be collected from the Enterprise Vault database. 11 Click Save. that is the MS SQL Server. You can collect the following data types from an Enterprise Vault set up: Target. The OpsCenter Agent service is running. For more details on collection interval. 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. and other data collector settings. You have entered the appropriate information for Enterprise Vault data collector variables. 10 Select collection interval. 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 402. The SQL Server services are running. See “Configuring the OpsCenter Agent properties for integrated logon” on page 401. Select the data types that you want to collect. See “Configuring Enterprise Vault data collector” on page 403. ■ ■ ■ ■ ■ ■ .

(The default is admin. Specify the TSM server host (also called product host) value for the TSM data collector in the following manner: . (This variable can be left blank.opt file. dsmConfig dsmDir dsmadmc Location The path to the dsm. The path of TSM administrative client (dsmadmc).) (Windows only) The TCP port on the TSM server through which the data collector establishes a connection. (The default password is admin.) The password for the account (specified in tsmId) for connecting to the TSM server.sys (Solaris and AIX). The path where files to be run dsmadmc reside. For more information.) An administrator-level logon that is used to connect to the Tivoli Storage Manager server. refer to your TSM documentation.opt and dsm. The Solaris data collector uses only product host settings. The TSM Server Port has no effect on Solaris.Understanding data collection IBM Tivoli Storage Manager data collector variables and details 405 IBM Tivoli Storage Manager data collector variables and details 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: Home Directory The home directory for the Tivoli Storage Manager installation. TSM ID TSM Password TSM Server Port Note: The TSM product environment variables DSM_CONFIG and DSM_SYS point to the dsmadmc required files dsm.

255.406 Understanding data collection EMC NetWorker data collector variables Windows Use the fully qualified host name.mycompany.sys file: ***************************************** SErvername server_a COMMmethod CoMMmethod TCPPort TCPip 1500 TCPServeraddress 255. refer to the following section: See “ Configuring an OpsCenter Data Collector” on page 358. Solaris and AIX The product host must be the value that is specified in the dsm.COM TCPSERVERADDRESS 255.com Host assuming that Host can be fully qualified. product host is the value that you can use with the dsmadmc -se option. .255.domain.255. for tag SErvername (note the case). product host is the value that you can use with the dsmadmc -tcpserveraddress option.255 SERVERNAME MYHOST.sample. The following is a sample dsm.255. For example.sys file. In short. EMC NetWorker data collector variables The variables to configure for the EMC NetWorker data collector are as follows: Home Directory The home directory for the EMC NetWorker installation. In short.255 NODENAME myhost. and other data collector settings.com ****************************************** For more details on collection interval. the following entries are valid for product host: Host.Veritas.

The default file name is messages. This path may be absolute or relative to homeDirectory. refer to the following section: See “ Configuring an OpsCenter Data Collector” on page 358. and mminfoFile even though these variables are optional and only advanced users must set them. .exe The directory path of the mminfo command-line interface (CLI). or relative to homeDirectory 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. and other data collector settings. To increase the efficiency of the NetWorker data collector. configure NetWorker to create a log that contains only group complete messages. and point messagesFile to this log Location of mminfo.exe Location of nsrres file Location of nsr file Location of mminfo file Output of mminfo(Optional) For more details on collection interval. or relative to homeDirectory The directory path of the nsradmin CLI. Location of nsradmin. absolute. nsrFile. absolute.Understanding data collection EMC NetWorker data collector variables 407 Location of messages file The directory path for the log file containing group-complete messages.

408 Understanding data collection EMC NetWorker data collector variables .

Figure 6-1 shows the details that are displayed on the Views tab in the OpsCenter console.Chapter 6 Managing OpsCenter views This chapter includes the following topics: ■ ■ ■ ■ ■ ■ ■ ■ ■ About OpsCenter views About managing OpsCenter views About managing nodes and objects in OpsCenter Adding nodes to a view in OpsCenter Modifying node details in OpsCenter Deleting nodes in OpsCenter Adding objects to a view node in OpsCenter Deleting objects from a view node in OpsCenter View filters in OpsCenter About OpsCenter views Symantec OpsCenter views are logical groups of IT assets (master servers or clients) organized in a hierarchical manner. . You can create views in Java View Builder and make them available in the OpsCenter console.

an OpsCenter Analyst and Reporter need to have the required rights assigned to them through Java View Builder. However. you cannot modify its attributes because you do not have the write permissions for that view. In a OpsCenter view. or delete . Note: To manage views.create. IT assets that are scattered across organization can be arranged according to their locations. With these reports. you can identify the locations or departments with hosts storing business critical data. . they cannot manage . You can generate various OpsCenter reports that are filtered by views.views using the OpsCenter GUI. or applications. business units. An OpsCenter Analyst has the Read permissions on all views. See “User access rights and UI functions in OpsCenter” on page 322. If they do not have these rights.410 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. edit. An OpsCenter Reporter has the Read permissions on the views only if it has the required permissions.

it cannot have hosts and file systems in the same tree. In a view hierarchy. which are then stored in the database. Select to view the objects on the node and unassigned objects. Displays the alias levels for the selected view. Table 6-1 Option View Type Views tab options Description Select the type of view from the drop-down list. Displays the role of the user who created the view. Client. See “OpsCenter view types” on page 412. Displays the name of the view. or to edit and delete the available views. Master Server. Settings > Views options A description of the Views tab options follows in the table. Edit View Level Alias Manage Nodes and Objects Name Created On Owner View Level Alias . Displays the date and time when the view was created. between top and bottom levels you can create a number of user-defined levels. and Policy. Select to edit the view level aliases.Managing OpsCenter views About OpsCenter views 411 After you install and run the OpsCenter Server and the OpsCenter Agent. Add/Edit/Delete Select to add new views. The options are All Views. you need Java Runtime Environment (JRE) installed on the host. An OpsCenter view is a homogeneous one. The Java View Builder makes these IT assets available when a view is created. Note: To run the Java View Builder. 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 “About collecting data from Enterprise Vault” on page 392. OpsCenter detects the IT assets.

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 See “About OpsCenter views” on page 409. You can modify the view level aliases. Note: All Veritas Backup Reporter (VBR) views are migrated to OpsCenter as Client views. and so on. Default view level aliases are as follows: Level 1. objects are made available for assigning to that view. You can create views of the following types: . Two tabs appear in the Details pane of the Settings > Views page. description. you need to recreate the Master Server views to run the Media reports with views. if you have not added any nodes or objects to the selected view. After you upgrade from VBR. date and time of creation. OpsCenter view types In OpsCenter. Media reports run only on Master Server view. Level 2. The Alias View Levels tab does not contain any data. See “Modifying alias view levels in OpsCenter” on page 416. and owners role. each view is associated with a view type. Depending on the type of the view. Table 6-2 Option Alias View Levels tab Settings > Views Details pane tabs Description This tab shows the details of view level aliases of the selected view.412 Managing OpsCenter views About OpsCenter views Table 6-1 Option General Views tab options (continued) Description Displays the basic information about the selected view such as name.

only file systems are available to be assigned to the view. You can add multiple nodes to a view at different levels. If you create a view of type Vault. only Master Servers are available to be assigned to the view. Master server hosts. only vaults are available to be assigned to the view. If you create a view of type Policy. If you create a view of type File System. only EV servers are available to be assigned to the view. only policies are available to be assigned to the view. Between the top level and the bottom level. About OpsCenter view levels A newly created view has only one level. If you create a view of type Enterprise Vault server. you can create multiple intermediate . If you create a view of type Exchange server. A view can either be public or private.Managing OpsCenter views About OpsCenter views 413 Client If you create a view of type Client. You can add alias for each of these view levels. or policies are always at the lowest levels in a view. Only view owner and OpsCenter admin can access private views. If you create a view of type Master Server. only backup clients are available to be assigned to the view. clients. See “Modifying alias view levels in OpsCenter” on page 416. Master server Policy Enterprise Vault server Exchange server Vault File System About accessing OpsCenter views While creating an OpsCenter view. you can specify the access rights for that view. Public view Private view All OpsCenter users can access public views. only Exchange servers are available to be assigned to the view. See “Creating OpsCenter views” on page 415.

creating a hierarchical structure in the view. edit. you can add multiple nodes. Settings > Views > Manage Nodes and Objects options A description of the Settings > Views > Manage Nodes and Objects options follows in the table.414 Managing OpsCenter views About managing OpsCenter views levels to organize view objects into logical groups. About nodes and objects An OpsCenter view comprises nodes and view objects. . A node is a logical entity that you add to create a hierarchical structure of a view. See “Deleting OpsCenter views” on page 416. See “Creating OpsCenter views” on page 415. Figure 6-2 View nodes and objects About managing OpsCenter views The following topics provide procedures to add. Figure 6-2 shows an example of a view comprising multiple nodes and objects. See “Viewing OpsCenter views and their details” on page 415. See “Modifying alias view levels in OpsCenter” on page 416. Between the first level (the view name itself) and the last level (actual view object). See “Modifying OpsCenter views” on page 415. or delete OpsCenter views.

only client hosts are available on the Unassigned Objects tab for selection. Objects on Node tab Unassigned Objects tab Viewing OpsCenter views and their details This topic provides the procedure to view OpsCenter views. See “Creating OpsCenter views” on page 415. The View Level Alias and General details are displayed in the lower section of the page. . The Unassigned Objects tab contains all objects that have not yet been assigned to the selected view or view node. See “Settings > Views options” on page 411. Modifying OpsCenter views This topic provides the procedure to modify view details. See “About OpsCenter views” on page 409. To create a OpsCenter view 1 2 3 4 In the OpsCenter console. select the view from the views list.Managing OpsCenter views About managing OpsCenter views 415 Table 6-3 Option Settings > Views > Manage Nodes and Objects options Description The objects that are assigned to the current view or view node are displayed on the Objects on Node tab. The available objects list varies depending on the view type. 2 To check the details of a view. click Settings > Views. On the Add View dialog box. A list of views that you have already created is displayed. specify the view details. To view OpsCenter views 1 In the OpsCenter console. click Settings > Views. Click Add. See “Modifying OpsCenter views” on page 415. Click OK. For example: If the view is of type Client. Creating OpsCenter views This topic provides the procedure to create a view using OpsCenter.

See “Adding nodes to a view in OpsCenter” on page 417. you can modify the view details. click Settings > Views. Modifying alias view levels in OpsCenter This topic provides the procedure to modify alias of view levels.416 Managing OpsCenter views About managing OpsCenter views To modify OpsCenter views 1 2 3 4 5 In the OpsCenter console. select a view that you want to modify. To delete OpsCenter views 1 2 3 In the OpsCenter console. On the Edit View dialog box. If you delete a view. . Deleting OpsCenter views This topic provides the procedure to delete views. From the list of views. click Settings > Views. From the list of views. select a view that you want to delete. Click Delete. Note: Once you have deleted a view. From the list of views. See “About managing nodes and objects in OpsCenter” on page 417. Click Edit. click Settings > Views. it cannot be recovered. Click Edit Alias View Levels. all its nodes are deleted and the objects are moved to the unassigned tree. select a view for which you want to modify view level alias. To modify alias view levels in OpsCenter 1 2 3 In the OpsCenter console. Click OK.

you can rename the levels as follows: rename Alias Level 1 as Geography. See “Adding nodes to a view in OpsCenter” on page 417. modify. and Alias Level 3 as Region. From the list of views. See “Deleting objects from a view node in OpsCenter” on page 419. For example. See “View filters in OpsCenter” on page 420. For example. See “Adding objects to a view node in OpsCenter” on page 419. the Alias View Levels dialog box appears as follows: 5 Rename the available levels. select a view to which you want to add nodes and objects. Click Manage Nodes and Objects. . if the selected view has three levels. Alias Level 2 as Country. See “Deleting nodes in OpsCenter” on page 418. 6 About managing nodes and objects in OpsCenter The following topics provide procedures to create. See “Modifying node details in OpsCenter” on page 418. To add nodes to a view 1 2 3 In the OpsCenter console. click Settings > Views. if the selected view has only one level.Managing OpsCenter views About managing nodes and objects in OpsCenter 417 4 On the Alias View Levels dialog box. Adding nodes to a view in OpsCenter This topic provides the procedure to add a node to a view. text boxes for entering aliases for all available view levels appear. Click OK. and delete nodes and objects related to a view. See “About nodes and objects” on page 414.

Click Delete. On the Add dialog box. Click Manage Nodes and Objects.418 Managing OpsCenter views Modifying node details in OpsCenter 4 5 6 7 On the view tree. Deleting nodes in OpsCenter This topic provides the procedure to delete the nodes from a view. From the list of views. On the view tree. Click OK. Click Add. Click Edit. See “Adding nodes to a view in OpsCenter” on page 417. Select the node that you want to modify. To delete a node 1 2 3 4 5 6 7 In the OpsCenter console. Select the node that you want to delete. On the confirmation dialog box. Click OK. expand the view to see the associated nodes. click Settings > Views. click OK. Click Manage Nodes and Objects. select a view from which you want to delete nodes. On the view tree. To modify node information 1 2 3 4 5 6 7 8 In the OpsCenter console. modify the name of the node. enter the node name. Modifying node details in OpsCenter This topic provides the procedure to modify the information of a view node. See “Adding nodes to a view in OpsCenter” on page 417. From the list of views. select a view to modify the information of associated nodes. select the view to which you want to add a node. On the Edit dialog box. . expand the view to see the associated nodes. click Settings > Views.

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

Connected Servers. You can also create your own filters and apply them to view the required list of view objects. Not Connected Servers.420 Managing OpsCenter views View filters in OpsCenter 4 On the view tree. Catalog Policies. modifying. . Standard Policies. Click Delete from Node. 5 6 7 Select the check boxes in front of the view objects that you want to delete. From the list of views. On the confirmation dialog box. Table 6-4 View type Client Default filters Default filters All Clients. The default set of filters varies depending on the view type. The objects that are assigned to this view or the view node are displayed on the Objects on Node tab. Solaris Clients. View filters in OpsCenter OpsCenter provides a set of default filters using which you can filter the view objects that you need to add to a view. Linux Servers. Linux Clients. Creating a view object filter in OpsCenter This topic provides the procedure to create user-defined view object filters. select the view name or a view node from which you want to delete an object. Windows Policies. Windows Clients. select the view to which you want to assign objects. Other Clients All Servers. click Settings > Views. Other Policies Master Server Policy See the following topics for information about creating. and deleting view object filters. Windows Servers. See “View filters in OpsCenter” on page 420. Active Policies. To create a view object filter 1 2 In the OpsCenter console. Inactive Policies. Solaris Servers. Partially Connected Servers. Other Servers All Policies. click OK. Table 6-4 lists the default filters available for various view types.

The following figure shows an example of creating a filter. Modifying view object filters in OpsCenter You can modify definition of user-defined view object filters. Click Manage Nodes and Objects. In the Add Filter dialog box. 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 assign view objects. specify the filter details. See “Deleting view object filters in OpsCenter” on page 422. select the Unassigned Objects tab. which you can modify or delete. In the right pane. click Settings > Views. From the list of views. For example: If the view is of type Client. You cannot modify the default filters. On the view tree. The list of objects that is displayed varies depending on the view type. This user-defined filter is now added in the Filter drop-down list on the Unassigned Objects tab. select the view to which you want to assign objects. To modify view object filters 1 2 3 4 In the OpsCenter console. . See “Modifying view object filters in OpsCenter” on page 421. 6 7 Click the Create Filter icon. On the view tree. select the view name or the view node to which you want to assign view objects. See “Creating a view object filter in OpsCenter” on page 420. 8 Click OK.Managing OpsCenter views View filters in OpsCenter 421 3 4 5 Click Manage Nodes and Objects.

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

Chapter 7 Monitoring NetBackup using Symantec OpsCenter This chapter includes the following topics: ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ About the Monitor views Controlling the scope of Monitor views About monitoring NetBackup using the Overview tab About monitoring NetBackup jobs Monitor > Services view About using the List View to monitor NetBackup media Viewing the details for NetBackup media Viewing the details for a master server associated with the media Filtering on NetBackup media type Controlling media Monitor > Media Summary View options About using the Hierarchical View by Volume Pool for monitoring media Viewing the details for volume pool Viewing the details for media Controlling media About using the Hierarchical View by Volume Group for monitoring media .

424 Monitoring NetBackup using Symantec OpsCenter ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Viewing the details for a volume group Viewing the details for media Controlling media in OpsCenter Monitoring NetBackup devices Monitor > Devices > Drives List View options About using the List View for monitoring drives Viewing the details for a single drive Viewing the details for a master server associated with a drive Filtering on NetBackup drive category Controlling drives Monitor > Devices > Drives Summary View Viewing the Drive Summary by Status Monitor > Devices > Disk Pools options Viewing the details for a single disk pool About monitoring NetBackup hosts Monitor > Hosts > Master Servers view Filtering by NetBackup master server type and status Monitor > Hosts > Media Servers view Viewing the details of a master server that is associated with a media server Monitor > Hosts > Clients view Viewing the details for a single master server About monitoring NetBackup alerts Monitor > Alerts List View About using the List View to monitor NetBackup alerts Viewing the details for a single alert Viewing the details of the alert policy associated with an alert Filtering by alert type .

policies. 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. and alerts. you can create a view like Geography to view details about master servers in a particular region like Europe. Controlling the scope of Monitor views The content that is shown in the Monitor views is based on your current View pane selection. It cannot monitor or manage other products like Symantec NetBackup PureDisk. Symantec Enterprise Vault etc. More information about how to create views by using the Settings > Views control is available. services. Use the following procedure to view details of all master servers or specific master servers.Monitoring NetBackup using Symantec OpsCenter About the Monitor views 425 ■ ■ ■ ■ Responding to alerts About using the Summary View for monitoring NetBackup alerts Viewing alerts by severity Monitoring Audit Trails About the Monitor views From the Monitor tab and associated subtabs. hosts. For example. media. you can also create your own views from Settings > Views or by using Java View Builder. Note that OpsCenter or OpsCenter Analytics can only monitor and manage NetBackup. . See “About OpsCenter views” on page 409. devices. In addition to using the default view i. you can view detailed information about your NetBackup environment including jobs. See the online Symantec OpsCenter Java View Builder Help to know how you can create views using Java View Builder.e.

426 Monitoring NetBackup using Symantec OpsCenter Controlling the scope of Monitor views To view details of all master servers ◆ In the OpsCenter console. select ALL MASTER SERVERS from the drop-down list in the View pane. Click Last 24 Hours. Last 48 Hours. Using the Customize option. The Customize option is located on the top-right corner of specific Monitor views. you can also customize the time frame selection by clicking Customize and specifying an absolute time frame or relative time frame. you can view data for any time frame. Top 7 Policies by Failed Jobs. These options are located on the top-right corner of specific Monitor views. Note that by default. You can control time frame selection for the following Monitor views: ■ Monitor > Overview (Job Summary by State. Deselect the checkbox next to ALL MASTER SERVERS and select the specific master servers from the list of master servers. or 72 hours for some of the Monitor views. Click Apply Selection. 48. and Alert Summary by Severity sections) Monitor > Jobs Monitor > Alerts Monitor > Policies (Summary View) ■ ■ ■ In addition. Ensure that other master servers are unchecked. Job Summary by Exit Status. You can customize the time frame selection for the following Monitor views: ■ ■ Monitor > Jobs (List View and Hierarchical View) Monitor > Alerts (List View) See “Controlling the scope of Monitor views” on page 425. data for the last 24 hours is shown in these views. . Top 7 Job Error Log Summary. To view details of specific master servers 1 2 In the OpsCenter console. or Last 72 Hours respectively. select ALL MASTER SERVERS from the drop-down list in the View pane. 3 See “About time frame selection” on page 426. About time frame selection You can also view data for the last 24.

Pie charts for most monitoring categories appear. Pointing on the pie chart gives the number and percentage of jobs in a particular job state in your NetBackup environment. A pie chart with different colors represents the job distribution. . You can also view the color code summary in this section to know the colors that represent different job states. Data for the last 24 hours is shown by default. The pie segments are also links to more details for the monitoring category. 22 jobs. or 42% jobs in your environment are in a queued state. From this view. you can use links to drill down and access detailed information about many aspects of your NetBackup environment. The following sections describe the Overview subtab in detail: ■ ■ ■ ■ ■ ■ ■ ■ ■ Viewing the Job Summary by State Viewing the Media Summary by Status About Top 7 Job Error Log Summary Viewing the Services Summary Viewing the Master Server Summary Viewing the Job Summary by Exit Status Viewing the Drive Summary by Status About Top 7 Policies by Failed Jobs section Viewing the Alert Summary by Severity Viewing the Job Summary by State The Job Summary by State section shows an overall distribution of jobs by job state for the current selection in the View pane and time frame selection. This information is shown in a pie chart as well as a table. See “Controlling the scope of Monitor views” on page 425. For example. You can also view data for the last 48 hours or 72 hours. Each color of the pie chart represents how jobs are distributed in your environment as per the job state in the selected time frame. pointing on the yellow color in the pie chart shows that in the last 24 hours. This view gives an overview of your NetBackup environment.Monitoring NetBackup using Symantec OpsCenter About monitoring NetBackup using the Overview tab 427 About monitoring NetBackup using the Overview tab This view is displayed when you select Monitor > Overview (default view). This view contains the different sections which display specific information about your NetBackup environment.

To view the Job Summary by job state 1 2 In the OpsCenter console. In the Media Summary by Status section. In the Job Summary by State section. For example. click the yellow section of the pie chart to view details for Queued jobs. click the number that is shown for Done jobs. ■ Viewing the Media Summary by Status The Media Summary by Status section shows an overall distribution of media by media status for the current selection in the View pane. click the red section of the pie chart to view details for Frozen media. Moving your pointer over the pie chart triggers the appearance of the number and percentage of media with a particular media status in your NetBackup environment. ■ . Each color of the pie chart represents how media are distributed in your environment as per the media status. do either of the following: ■ Click the number of jobs (link) for a particular job state from the table. incomplete.428 Monitoring NetBackup using Symantec OpsCenter About monitoring NetBackup using the Overview tab You can drill down from this section to see details for failed. do either of the following: ■ Click the number of media (link) for a particular media status from the table. select Monitor > Overview. You can drill down from this section to see details for media with different status like details for frozen and active media. Or Click a colored section of the pie chart that corresponds to a particular job state. A pie chart with different colors represents media distribution in this section. For example. 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 media status. active jobs etc. For example. For example. You can also view the color code summary in this section to know the colors that represent different media status. To view media by media status 1 2 In the OpsCenter console. select Monitor > Overview. pointing on the red color in the pie chart shows that four media or 2% media in your environment are frozen. click the number for Frozen media. queued.

You can drill down from the links in this table to see details for running or stopped services. In the Service Summary section. 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 ■ ■ . To view running or stopped services 1 2 In the OpsCenter console. The table that appears in the section lists the top seven exit status codes responsible for maximum job failure. Data for the last 24 hours is shown by default.Monitoring NetBackup using Symantec OpsCenter About monitoring NetBackup using the Overview tab 429 About Top 7 Job Error Log Summary The Top 7 Job Error Log Summary section lists seven exit status codes responsible for maximum failed jobs in your environment. Viewing the Services Summary The Services Summary section provides a high-level view that shows the total number of running and stopped NetBackup services for the current View pane selection. The total number of running and stopped NetBackup services are shown in a table. select Monitor > Overview. click the number that is shown in the Service Count column of the table. By viewing this section. Note that the failed jobs that are shown in the Failed Job Count column are arranged in descending order in the table. you can quickly analyze the reasons behind maximum job failures in your environment. The content that is shown in this section is based on the current View pane selection. click the number that is shown for Running services to view details for the services that are running. The table also lists the number of failed jobs for each exit status in the selected time frame. You can also view data for the last 48 hours or 72 hours. For example. See “Controlling the scope of Monitor views” on page 425. Viewing the Master Server Summary The Master Server Summary section provides the specific information about the master servers based on the current View pane selection.

or 42% jobs in your environment failed. To view the master servers that are connected 1 2 In the OpsCenter console. select Monitor > Overview. In the Master Server Summary section. See “Controlling the scope of Monitor views” on page 425. Putting your pointer over the pie chart shows the total number and percentage of successful. 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 Clients at Risk column. click the number that is shown in the Total column. In the Master Server Summary section. For example. Each color of the pie chart represents how jobs are distributed in your environment as per the exit status. select Monitor > Overview. select Monitor > Overview. Viewing the Job Summary by Exit Status The Job Summary by Exit Status section shows an overall distribution of jobs by exit status based on the current View pane and time frame selection. pointing to the red color in the pie chart shows that in the last 24 hours. select Monitor > Overview. You can also view data for the last 48 hours or 72 hours. and failed jobs in your NetBackup environment. click the number that is shown in the Not Connected column. You can also view the color code summary in this section to know the colors that represent different exit status. In the Master Server Summary section. You can also see details of the clients that do not have a backup policy configured for them. This information is shown in a pie chart as well as a table. partially successful. To view all master servers 1 2 In the OpsCenter console. A pie chart with different colors represents the job distribution by exit status in the selected time frame.430 Monitoring NetBackup using Symantec OpsCenter About monitoring NetBackup using the Overview tab You can drill down from this section to see details for all the master servers in your environment or the master servers that appear as connected or not connected. In the Master Server Summary section. Data for the last 24 hours is shown by default. click the number that is shown in the Connected column. This . 72 jobs. To view details of the clients that are at risk 1 2 In the OpsCenter console.

a table also shows the amount of data that has been backed up for the selected view and time frame. select Monitor > Overview. successful. do either of the following: . do either of the following: ■ Click the number of jobs (link) corresponding to a particular exit status from the table. down. Note that the drop-down list is located on the top-right corner of the page. or partially successful jobs. pointing to the green color in the pie chart shows that 5 drives or 100% drives in your environment are up. the Drive Summary by Status section does not show the drives that are disabled or unreachable. To view drives by drive status 1 2 In the OpsCenter console. You can drill down from this section to see details of all drives including up. Putting your pointer over the pie chart shows the number and percentage of drives with up or down status in your NetBackup environment. For example. ■ Viewing the Drive Summary by Status The Drive Summary by Status section shows an overall distribution of drives by drive status for the current View pane selection. click the red section of the pie chart to view details for failed jobs. select Monitor > Overview.0. Each color of the pie chart represents how drives are distributed in your environment as per the drive status. Note: For 7. or mixed drives. To view jobs by exit status 1 2 3 In the OpsCenter console. You can also view the color code summary in this section to know the colors that represent different exit status. In addition. A pie chart with different colors represents the distribution of drives by drive status in the selected time frame.1 and 7.Monitoring NetBackup using Symantec OpsCenter About monitoring NetBackup using the Overview tab 431 information is also listed in a tabular format. You can drill down from this section to see details for failed. In the Job Summary by Exit Status section. Select Summary View from the drop-down list. This information is shown in a pie chart as well as a table. For example.1 master servers. In the Drive Summary by Status section. Or Click a colored section of the pie chart that corresponds to a particular exit status.

. For example. pointing to the green color in the pie chart shows that in the last 24 hours.432 Monitoring NetBackup using Symantec OpsCenter About monitoring NetBackup using the Overview tab ■ Click the number of drives (link) for a particular drive status from the table. click the green section of the pie chart to view details for the drives that are up. From this section you can quickly view the policies which have the maximum failed jobs associated with them. For example. See “Controlling the scope of Monitor views” on page 425. You can also view data for the last 48 hours or 72 hours. Viewing the Alert Summary by Severity The Alert Summary by Severity section shows an overall distribution of alerts by severity for the current View pane and time frame selection. A pie chart with different colors represents the alert distribution by severity in this section. 200 alerts. You can also view the color code summary in this section to know the colors that represent different severity. ■ 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 time frame selection. This information is shown in a pie chart as well as a table. See “Controlling the scope of Monitor views” on page 425. You can also view data for the last 48 hours or 72 hours. Data for the last 24 hours is shown by default. The table also shows the number of failed jobs for each policy. Each color of the pie chart represents how alerts are distributed in your environment as per the alert severity. Moving your pointer over the pie chart gives the number and percentage of alerts with a particular severity in your NetBackup environment. click the number for Up drives Or Click a colored section of the pie chart that corresponds to a particular drive status. For example. Note that the failed jobs (shown in Total Number of Failed Jobs column) are arranged in descending order in the table. or 17% alerts in your environment are critical. Data for the last 24 hours is shown by default. The table that is shown in the section lists the top seven policies which have maximum failed jobs associated with them. You can drill down from this section to see details for alert categories.

click the red section of the pie chart to view details for Critical alerts. . select Monitor > Overview. Note: You can only view jobs data for the last 30 days from the List View. This view displays detailed information about jobs based on the current View pane and time frame selection. click the number that is shown for Critical alerts. You can use the following views to see NetBackup job information: List View This view is shown by default when you select Monitor > Jobs. Or Click a colored section of the pie chart that corresponds to a particular alert severity. do either of the following: ■ Click the number of alerts (link) for a particular alert severity from the table. Summary View The Summary View contains the different sections which show the NetBackup job distribution by exit status. In the Alert Summary by Severity section. For example. job state. See “Monitor > Jobs List View options” on page 434. See “About using the Summary View for monitoring jobs” on page 442. ■ About monitoring NetBackup jobs The Monitor > Jobs view provides details of NetBackup jobs. and job type based on the current View pane and time frame selection. This information is shown in pie charts and tables. For example.Monitoring NetBackup using Symantec OpsCenter About monitoring NetBackup jobs 433 To view alerts by severity 1 2 In the OpsCenter console.

The table that appears in this view shows the following columns by default: Table 7-1 Option Job ID Monitor > Jobs List View options Description This column shows the unique ID associated with the job (link). This view displays detailed information for jobs for the current View Pane and time frame selection. Note: You can only view jobs data for the last 30 days from the Hierarchical View. Done etc. Master Server Type State Status . The link provides status description and details on troubleshooting in case it failed. The drop-down list is located at the top-right corner of the page. The List View is shown by default.434 Monitoring NetBackup using Symantec OpsCenter About monitoring NetBackup jobs Hierarchical View The Hierarchical View shows all parent-child jobs in a hierarchical fashion based on the current View pane and time frame selection. You can also view data for the last 48 hours or 72 hours. You can click the link to view details for the master server. Note: You can select these views from the drop-down list. This column lists the current NetBackup job state like whether the job is Queued. See “About using the Hierarchical View for monitoring jobs” on page 447. Exit status of the job. Waiting for Retry. This column shows the name of the master server (link) associated with the job. Note: You can only view jobs data for the last 30 days from the List View. This column lists the job type like whether the job is a DB Backup or an Image Cleanup job. Data for the last 24 hours is shown by default. Monitor > Jobs List View options This view is displayed when you select Monitor > Jobs. See “Controlling the scope of Monitor views” on page 425.

The Table Settings icon is located on the top-right corner of the table. This column lists the percentage of job that has been completed. Elapsed Time is the difference between the current time and Start time. Client Start Time Elapsed Time Note: The contents of the Elapsed Time column cannot be sorted in ascending or descending order (when you click the column name. and year when the job started. For a running job. time. More columns can be added to your view by clicking the Table Settings icon. This column lists the time that is taken by the job. time. The following columns are not displayed in the table by default:. This column lists the name of the client on which the job is run. ■ ■ ■ ■ ■ ■ ■ Schedule Source Media Server Destination Media Server Destination Storage Unit Attempt Operation PID . Job Size Files % Complete Not all columns are displayed in the table by default. This column lists the number of files that have been backed up by this job. and year when the job ended.) End Time This column lists the date. The Elapsed Time is the difference between End Time and Start Time values. This column lists the size of the job. This column lists the date.Monitoring NetBackup using Symantec OpsCenter About monitoring NetBackup jobs 435 Table 7-1 Option Policy Monitor > Jobs List View options (continued) Description This column lists the name of the policy that is associated with the job.

The Details pane has the following tabs: . More information about how to customize tables and view specific columns is available. The Details pane is located at the bottom of the Monitor > Jobs view. All the details that are associated with a job can be viewed from the Details pane.436 Monitoring NetBackup using Symantec OpsCenter About monitoring NetBackup jobs ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ 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 Reconciliation Reason Data Reduction Savings (%) Priority State Details See the online NetBackup Administration Console Help for a detailed description of these fields. See “About using tables” on page 71.

See “Viewing the details for a master server associated with a job” on page 438. The Details pane is located at the bottom of the Monitor > Jobs view. The Attempts tab shows details of the attempts that have been made to complete a job. See “Exporting NetBackup job logs” on page 442. The File List tab shows the files that have been backed up by the job and also their location. See “Viewing the details for a single NetBackup job” on page 437.Monitoring NetBackup using Symantec OpsCenter About monitoring NetBackup jobs 437 Table 7-2 Tab General Monitor > Jobs Details pane tabs Description The General tab of the Details pane displays all information available for the job. See “Controlling NetBackup jobs” on page 439. See “Filtering on NetBackup job state” on page 438. It also includes the contents of all the available columns that can be viewed from the table. See “Reconciling NetBackup jobs” on page 440. Viewing the details for a single NetBackup job All the details that are associated with a job can be viewed from the Details pane. . See “Changing the job priority” on page 441. See “Viewing policy information for a job” on page 438. It also includes the contents of all the available columns that can be viewed from the table. Attempts File List About monitoring jobs using the List View The following topics provide more information about monitoring jobs using the List View. The Details pane has the following tabs: General The General tab of the Details pane displays all information available for the job.

Click the server name (link) associated with the job in the Master Server column of the table. The File List tab shows the files that have been backed up by the job and also their location. To view details for the master server that is associated with a job 1 2 In the OpsCenter console. Filtering on NetBackup job state You can filter by using any of the built-in job filters. To view policy information for a job 1 2 3 In the OpsCenter console. The built-in job filters are the following: . Viewing policy information for a job Use the following procedure to view the details for the policy that is associated with a job. You can also enable or disable data collection for the master server from this page.438 Monitoring NetBackup using Symantec OpsCenter About monitoring NetBackup jobs Attempts The Attempts tab shows details of the attempts that have been made to complete a 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. select Monitor > Jobs. Click the policy name (link) for the job in the Policy column of the table. The details of the master server are shown on a separate page. select Monitor > Jobs. select Monitor > Jobs. See “Monitor > Policies page” on page 457. These filters are available from the drop-down list which is present on top of the table. Click the ID (link) for a job from the Job ID column of the table. A separate page appears that shows policy information on four tabs. File List To view details for a single NetBackup job 1 2 In the OpsCenter console.

Select this filter to view the jobs that failed. Select this filter to view the jobs that are incomplete. suspend. manually refresh your Web browser to obtain an updated view for all jobs. Before you perform these tasks. resume. Note: These tasks are not visible if you log on with an Analyst or a Reporter role. Controlling NetBackup jobs Use the following procedure to cancel. Select this filter to view only active jobs Select this filter to view only queued jobs. Select this filter to view only Done jobs. Select this filter to view the jobs that have been canceled. you can also create your own custom filters. . See “Using filters to customize your views” on page 74. Note that the drop-down list is located on top of the table. Select this filter to view the jobs that have been suspended. Select this filter to view the jobs that are successful. Select a filter from the drop-down list. Select this filter to view the jobs that are waiting for retry.Monitoring NetBackup using Symantec OpsCenter About monitoring NetBackup jobs 439 All Jobs (default filter) Active Jobs Queued Jobs Done Jobs Suspended Jobs Select this filter to view details of all the jobs. or restart a job. To filter details by job state 1 2 Select Monitor > 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 the jobs that are undefined. Select this filter to view the jobs that are partially successful.

Ensure that List View is selected in the drop-down list. From the More drop-down list. In the Reconcile Jobs dialog box. select Reconcile. Resume. By using the Reconcile option and selecting a reason. 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. 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 let your service provider know not to bill you for these jobs as these jobs failed due to specific issues at your end. 6 Click OK. Restart. . Select a job from the table.440 Monitoring NetBackup using Symantec OpsCenter About 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. Suspend. Note that the drop-down list is located on the top-right corner of the page. Note: The Reconcile option is disabled in the unlicensed version (Symantec OpsCenter). Click Cancel. The OpsCenter console may take some time to show the updated status once you perform the tasks. select a reason for reconciling the job from the drop-down list. select Monitor > Jobs. You can select one or more jobs. from being billed. Select a job from the table. You may select one or more jobs. host cannot be reached etc. select Monitor > Jobs. Reconciling NetBackup jobs You can use the Reconcile option to prevent the jobs that failed due to reasons like user terminating a job. These options are located on top of the table. Before you perform this task.

From the More drop-down list. To change the job priority 1 2 3 4 5 6 7 In the OpsCenter console. Note that the drop-down list is located on the top-right corner of the page. Select an active job or a queued job from the table. Click Finish. Click OK. Table 7-3 Option Set the job priority to Increment the job priority by Decrement the job priority by Change Job Priority dialog box options Description Enter a value to set the job priority. set the job priority to a particular value. Priority can be changed only for jobs from the master servers that are running NetBackup 6.Monitoring NetBackup using Symantec OpsCenter About monitoring NetBackup jobs 441 Changing the job priority You can change the priority that is associated with a job. Review the following points before changing the job priority: ■ ■ Priority can be changed only for the jobs that are in Active or Queued state. select Change Job Priority. Select a value from the drop down list to increment the job priority. Select a value from the drop down list to decrement the job priority. You can also increment or decrement the job priority. Change Job Priority dialog box options A description of the Change Job Priority dialog box options follows in the table. Ensure that List View is selected in the drop-down list. select Monitor > Jobs.5. In the Change Priority dialog box. . The OpsCenter console may take some time to show the updated status once you perform this task. See “Changing the job priority” on page 441.2 or higher versions.

Note: The Export Job Logs option is not visible if you log on with an Analyst or a Reporter role. ensure that the NetBackup master server is Connected and the selected job logs are enabled. Select a job from the table. The content that is shown in the Summary View is based on the current View Pane and time frame selection. select Export Job Logs. The Summary View contains the different sections which display specific information about NetBackup jobs. You can export only one job log at a time. See “Controlling the scope of Monitor views” on page 425. The drop-down list is located at the top-right corner of the page. Ensure that List View is selected in the drop-down list. Click Open or Save from the dialog box to view or save the log file in an Excel format. The table and the pie charts include links to filtered detail views. These sections show NetBackup job information in a table as well as a pie chart. To export the NetBackup log files for a job 1 2 3 In the OpsCenter console. About 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.442 Monitoring NetBackup using Symantec OpsCenter About monitoring NetBackup jobs Exporting NetBackup job logs You can export the log files that are associated with a job. You can also view data for the last 48 hours or 72 hours. You can view or save the exported log files in an Excel format. Note that the drop-down list is located on the top-right corner of the page. Note: Logs are not available for all job types. Before exporting a log file. select Monitor > Jobs. You can use these links to drill down and access detailed information about NetBackup jobs. Data for the last 24 hours is shown by default. 4 5 From the More drop-down list. .

You can also view data for the last 48 hours or 72 hours. This information is shown in a pie chart as well as a table. 72 jobs. pointing your cursor to the red color in the pie chart shows that in the last 24 hours. partially successful. Each color of the pie chart represents how jobs are distributed in your environment as per the exit status. To view jobs by exit status 1 2 3 In the OpsCenter console. Moving your pointer over the pie chart gives the number and percentage of jobs with a particular exit status in your NetBackup environment. a Group Component Summary table is displayed when you access the Summary View for Monitor > Jobs. or 42% jobs in your environment failed. You can uncheck the Allow Multiple Selection in View Pane option from Settings > User Preferences > General. The following sections describe this view in detail: ■ ■ ■ ■ Viewing the Job Summary by Exit Status Viewing the Job Summary by State Viewing the Job Summary by Type About the Group Component Summary table Viewing the Job Summary by Exit Status The Job Summary by Exit Status section shows an overall distribution of jobs by exit status. See “Controlling the scope of Monitor views” on page 425. The data that is shown in this view is based on the current View pane and time frame selection. Data for the last 24 hours is shown by default. Note that the drop-down list is located on the top-right corner of the page. select Monitor > Jobs.Monitoring NetBackup using Symantec OpsCenter About monitoring NetBackup jobs 443 Note: If you uncheck the Allow Multiple Selection In View Pane option. You can drill down from this section to see details for successful. A pie chart with different colors represents the job distribution by exit status in this section. Select Summary View from the drop-down list. The Group Component Summary table displays information about immediate NetBackup constituents of the view or node (group) that you selected in the View pane. In the Job Summary by Exit Status section. For example. You can also view the color code summary in this section to know the colors that represent different exit status. and failed jobs. do either of the following: .

click the red section of the pie chart to view details for failed jobs. 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. Select Summary View from the drop-down list. select Monitor > Jobs. the jobs that are waiting for retry. click the yellow section of the pie chart to view details for Queued jobs. To view jobs by job state 1 2 3 In the OpsCenter console. Each color of the pie chart represents how jobs are distributed in your environment as per the job state. You can also view data for the last 48 hours or 72 hours. A pie chart with different colors represents the job distribution by job state. ■ Viewing the Job Summary by State The Job Summary by State section shows an overall distribution of jobs by the NetBackup job state based on the current View pane and time frame selection. For example. In the Job Summary by State section.444 Monitoring NetBackup using Symantec OpsCenter About monitoring NetBackup jobs ■ Click the number of jobs (link) corresponding to a particular exit status from the table. For example. and so on. Or Click a colored section of the pie chart that corresponds to a particular job state. queued or active jobs. ■ . For example. You can also view the color code summary in this section to know the colors that represent different job states. You can drill down from this section to see details for the jobs that failed. do either of the following: ■ Click the number of jobs (link) in a particular job state from the table. Data for the last 24 hours is shown by default. For example. This information is shown in a pie chart as well as a table. Moving your cursor over the pie chart gives the number and percentage of jobs in a particular job state in your NetBackup environment. click the number that is shown for Done jobs. 22 jobs. Note that the drop-down list is located on the top-right corner of the page. pointing to the yellow color in the pie chart shows that in the last 24 hours. See “Controlling the scope of Monitor views” on page 425.

For example. You can drill down from this section to see details for different job types like DBBackup. click the number that is shown for DBBackup jobs. ■ About the Group Component Summary table When you uncheck the Allow Multiple Selection In View Pane option under Settings > User Preferences > General view in the OpsCenter console. You must select a group (view or node) from the View pane to see data in the Group Component Summary table. This information is shown in a pie chart as well as a table. pointing to the red color in the pie chart shows that in the last 24 hours. Each color of the pie chart represents how jobs are distributed in your environment as per the job type. Image Cleanup etc. Select Summary View from the drop-down list. For example. Moving your cursor over the pie chart gives the number and percentage of jobs of a particular job type in your NetBackup environment. See “Controlling the scope of Monitor views” on page 425. select Monitor > Jobs. You do not see any data in the Group . You can also view data for the last 48 hours or 72 hours. or 42% jobs in your environment are DBBackup jobs. 22 jobs. You can also view the color code summary in this section to know the colors that represent different job types. you can view the Group Component Summary table in the Summary View for Monitor > Jobs. do either of the following: ■ Click the number of jobs (link) corresponding to a particular job type from the table. Note that the drop-down list is located on the top-right corner of the page. click the red section of the pie chart to view details for DBBackup jobs.Monitoring NetBackup using Symantec OpsCenter About monitoring NetBackup jobs 445 Viewing the Job Summary by Type The Job Summary by Type section shows an overall distribution of jobs by the job type based on the current View pane and time frame selection. The Group Component Summary table was also displayed in NOM earlier. The Group Component Summary table is displayed at the bottom of the Summary View for Monitor > Jobs. Or Click a colored section of the pie chart that corresponds to a particular job type. For example. To view jobs by job type 1 2 3 In the OpsCenter console. A pie chart with different colors represents the job distribution by job type in this section. Data for the last 24 hours is shown by default. In the Job Summary by Type section.

a job summary of the nodes (and not the view objects for each node) is displayed. Table 7-4 explains the information that is displayed in the Group Component Summary table.446 Monitoring NetBackup using Symantec OpsCenter About monitoring NetBackup jobs Component Summary table if you select a specific view object (master server) in the View pane. If you select a view that contains multiple nodes. Click the link to view detailed information about the partially successful jobs. or TSM servers) do not appear in the Group Component Summary table. The information that is displayed in the Group Component Summary table is based on the current View pane and time frame selection. Successful Partially Successful . See “Controlling the scope of Monitor views” on page 425. Hence any other servers (like BE. Table 7-4 Column Name Total Columns and descriptions in the Group Component Summary table Description Name of the node or view object. More details about nodes and view objects is available. For example if you select the ALL MASTER SERVERS view. Total number of jobs (link) for the specific node or view object in the selected time frame. Click the link to view detailed information about successful jobs. Data for the last 24 hours is shown by default. Click the link to view detailed information about all the jobs. See “About nodes and objects” on page 414. Number of partially successful jobs (link) for the specific node or view object in the selected time frame. You can also view data for the last 48 hours or 72 hours. PD. the Group Component Summary table displays job summary for each master server. Number of successful jobs (link) for the specific node or view object in the selected time frame. The Group Component Summary table displays job summary information about the immediate NetBackup constituents of the selected view or node (group) in the View pane. Note: OpsCenter or OpsCenter Analytics monitors only NetBackup.

Number of active jobs (link) for the specific node or view object in the selected time frame. Click the link to view detailed information about the jobs that are waiting for retry. Number of queued jobs (link) for the specific node or view object in the selected time frame. Data that is backed up for the specific node or view object in the selected time frame. Click the link to view detailed information about the undefined jobs. Click the link to view detailed information about the suspended jobs. Click the link to view detailed information about the failed jobs. Click the link to view detailed information about the active jobs. Number of undefined jobs (link) for the specific node or view object in the selected time frame. Click the link to view detailed information about the queued jobs. Number of suspended jobs (link) for the specific node or view object in the selected time frame. Number of incomplete jobs (link) for the specific node or view object in the selected time frame. The data that is shown in this view is based on the .Monitoring NetBackup using Symantec OpsCenter About monitoring NetBackup jobs 447 Table 7-4 Columns and descriptions in the Group Component Summary table (continued) Description Number of failed jobs (link) for the specific node or view object in the selected time frame. Column Failed Data Backup up Active Queued Suspended Incomplete Undefined Waiting for Retry About 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. Number of the jobs that are waiting for retry (link) for the specific node or view object in the selected time frame. Click the link to view detailed information about the incomplete jobs.

See “Controlling the scope of Monitor views” on page 425. Data for the last 24 hours is shown by default. A child job is indented to the right-hand side in the Job ID column. all related jobs can be grouped and you can see all parent-child jobs in a hierarchical fashion. For example. Note the following things about the related jobs that are shown in the Hierarchical View: ■ The filters are applied only to parent jobs. You can click the + sign to see all child jobs. child jobs are not considered at all. the current selected sort order is applied to child jobs. The Hierarchical View shows details of all jobs and also highlights the parent-child relationship between jobs wherever applicable. it is represented only by its job ID in the Job ID column. ■ ■ Viewing the details for a single NetBackup job All the details that are associated with a job can be viewed from the Details pane. However.448 Monitoring NetBackup using Symantec OpsCenter About monitoring NetBackup jobs current View pane and time frame selection. The Details pane is located at the bottom of the Monitor > Jobs view. Neither is there a + sign before the job ID of such a job nor this job is indented to the right-hand side. . The Details pane has the following tabs: General The General tab of the Details pane displays all information available for the job. In the Hierarchical View. It also includes the contents of all the available columns that can be viewed from the table. then + sign also appears before the job ID of the child job. You can also view data for the last 48 hours or 72 hours. When you expand a parent job. The filters are not applied to child jobs. All parent jobs have a +sign before the job ID. Only parent jobs or unrelated jobs (jobs that are not related to any other job) with partially successful status are considered. parent job in this view with the ability to expand and drill into the details of child jobs if there are failures. if a job does not have a relationship with any other job (it is neither a parent nor a child job). You can view details of only the top level. If some of the child jobs are parent jobs. All tasks that apply to the parent job are also applicable to its child jobs. if you apply the Partially Successful Jobs filter. Note: You can only view jobs data for the last 30 days from the Hierarchical View. The sorting feature in the Hierarchical View applies to both parent jobs and child jobs.

File List To view details for a single NetBackup job 1 2 3 4 In the OpsCenter console. select Monitor > Jobs. The drop-down list is located at the top-right corner of the view. You can also enable or disable data collection for the master server from this page. The File List tab shows the files that have been backed up by the job and also their location. Note: You can also view policy information from the List View. To view the details for the master server that is associated with a job 1 2 3 In the OpsCenter console. The drop-down list is located at the top-right corner of the view. Click the ID (link) for a job from the Job ID column of the table. Select Hierarchical View from the drop-down list. Select Hierarchical View from the drop-down list. select Monitor > Jobs. View the job details in the Details pane. Select Hierarchical View from the drop-down list. . The drop-down list is located at the top-right corner of the view. Viewing policy information for a job Use the following procedure to view the details for the policy that is associated with a job. To view policy information for a job 1 2 In the OpsCenter console. Click the server name (link) associated with the job in the Master Server column of the table. select Monitor > Jobs. The details of the master server are shown on a separate page.Monitoring NetBackup using Symantec OpsCenter About monitoring NetBackup jobs 449 Attempts 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.

See “Using filters to customize your views” on page 74.450 Monitoring NetBackup using Symantec OpsCenter About monitoring NetBackup jobs 3 4 Click the policy name (link) for the job in the Policy column of the table. Select this filter to view only Done jobs. Select this filter to view the jobs that are waiting for retry. . See “Monitor > Policies page” on page 457. Select this filter to view the jobs that failed. Select this filter to view only active jobs Select this filter to view only queued jobs. Select this filter to view the jobs that are successful. Select this filter to view the jobs that are undefined. you can also create your own custom filters. Waiting for Retry Jobs Incomplete Jobs Undefined Jobs Canceled Jobs Successful Jobs Partially Successful Jobs Failed Jobs In addition to using the built-in filters. A separate page appears that shows policy information on four tabs. These filters are available from the drop-down list which is present on top of the table. Filtering on NetBackup job state You can filter by using any of the following built-in job filters. Select this filter to view the jobs that have been canceled. Select this filter to view the jobs that have been suspended. The built-in job filters are the following: All Jobs (default filter) Active Jobs Queued Jobs Done Jobs Suspended Jobs Select this filter to view details of all the jobs. Select this filter to view the jobs that are incomplete. Select this filter to view the jobs that are partially successful.

This view contains detailed information for services. The table that appears in this view has the following columns: Name Host Name This column lists the name of the service. select Monitor > Jobs. Stop Pending. Other can be Not Installed. Device Manager. See “Controlling the scope of Monitor views” on page 425. Example: Vault Manager. Not Licensed. Monitor > Services view This view is displayed when you select Monitor > Services.Monitoring NetBackup using Symantec OpsCenter Monitor > Services view 451 To filter details by job state 1 2 3 In the OpsCenter console. You can perform the following tasks from this view: . Failed. The drop-down list is located at the top-right corner of the view. The data that is shown in this view is based on the current View pane selection. Service Type Note: The status for some services may show as Stopped on the Monitor > Services page in the OpsCenter console. Restart Pending. Select a filter from the drop-down list. Select Hierarchical View from the drop-down list. or Unknown. Note that the drop-down list is located on top of the table. Status The operational status of the service or daemon. or Service Layer. The license for these services is either not installed or configured for a specific media or master server. Start Pending. This status can be Stopped. Running. This column lists the name of the master server or media server where the service or daemon is present. or Other. This column lists the NetBackup service type.

Controlling NetBackup services Under certain circumstances there may be issues among multiple OpsCenter users. or Not Applicable (some services may not be applicable to earlier versions). you can also create your own custom filters. Control NetBackup services Filtering on NetBackup service type You can filter by using any of the four built-in filters. Note that the drop-down list is located on top of the table. Stopped Services Running Services Other Services In addition to using the built-in filters. Unknown (not recognized by OpsCenter). 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. For instance. The built-in filters are the following: All Services (default filter) Select this filter to view details of all the services. select Monitor > Services. one OpsCenter user stops a service while another user tries to start the same service. Select this filter to view details of the services that have been stopped. Select this filter to view details of running services. To view details by type of service 1 2 In the OpsCenter console.452 Monitoring NetBackup using Symantec OpsCenter Monitor > Services view Use filters to view specific services See “Filtering on NetBackup service type” on page 452. Select this filter to view details of all other services like Not Licensed. Use the following procedure to view details by type of service. See “Controlling NetBackup services” on page 452. See “Using filters to customize your views” on page 74.

Stop. or Restart Pending appears in the Status column until the selected action completes. Note that these tasks are located on top of the table. In the OpsCenter console.Monitoring NetBackup using Symantec OpsCenter Monitor > Services view 453 Note: NetBackup service layer (nbsl) cannot be controlled from OpsCenter. This view shows detailed information about NetBackup policies based on the current View pane selection. See “Monitor > Policies List View” on page 454. . Stop. The OpsCenter console may take some time to show the updated status once you perform these tasks. Note: These tasks are not visible if you log on with an Analyst or a Reporter role. or Restart. Running. If you start or stop a service that has a dependency on another service. Summary View The Summary View contains the different sections that display specific information about NetBackup policies based on the current View pane and time frame selection. Select a service from the table. You can select one or more services. See “Monitor > Policies Summary View” on page 460. To control a service 1 2 3 4 Refresh your Web browser to obtain an updated state for all services. These sections show specific policy information in a table as well as a pie chart. select Monitor > Services. NetBackup ensures that any dependent services are also started or stopped. You can use the following views to see NetBackup policy information: List View The List View is shown by default when you select Monitor > Policies. Click Start. About monitoring NetBackup policies The Monitor > Policies view provides details of NetBackup policies.

This view contains detailed information about policies. Master Server Type Storage Volume Pool . Monitor > Policies List View This view is displayed when you select Monitor > Policies. See “Filtering on NetBackup policy type” on page 456. The table that appears in this view has the following columns: Name Name of the policy. See “Viewing details for a single NetBackup policy” on page 458. Sybase. Oracle. See “Viewing details for a single NetBackup policy” on page 458. See “Viewing details for a single NetBackup policy” on page 458. See “Controlling the scope of Monitor views” on page 425. See “Viewing details for a single NetBackup policy” on page 458. See “About using the List View to monitor NetBackup policies” on page 456. See “Viewing details for a single NetBackup policy” on page 458. Click the link to view details of master server. Name of the master server that is associated with the policy. Example: DB2. Click the link to view details for storage. See “Viewing details for a single NetBackup policy” on page 458. Volume pool that is associated with the policy. The data that is shown in this view is based on the current View pane selection. Click the link to view details of volume pool. This column is the policy type. Click the link to view details about the policy. Vault etc. NBU-Catalog. Storage that is associated with the policy. Usually. the Policy type determines the type of clients that can be backed up by this policy. The drop-down list is located at the top-right corner of the page.454 Monitoring NetBackup using Symantec OpsCenter Monitor > Services view Note: You can select these views from the drop-down list.

The total number of jobs that are associated with the policy. Priority that you have defined for the policy. The following columns do not appear. Jobs/Policy Priority Active Not all of the available columns appear initially in this view. 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 Keyword Phrase Policy Domain Name .Monitoring NetBackup using Symantec OpsCenter Monitor > Services view 455 CheckPoint Interval Interval (in minutes) between two checkpoints in NetBackup. This column determines whether the policy is Active or not. Zero means the lowest priority.

See “Starting a manual backup” on page 459. Select this filter to view details of the policies that are active. More information about how to customize tables and view specific columns is available.456 Monitoring NetBackup using Symantec OpsCenter Monitor > Services view See the online NetBackup Administration Console Help for a detailed description of these fields. See “Viewing the details for a volume pool associated with a policy” on page 458. View the details for a single NetBackup policy View the details for a master server associated with a policy 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 “Monitor > Policies Summary View” on page 460. Filtering on NetBackup policy type You can filter by using any of the seven built-in filters. See “Activating or deactivating a job policy” on page 459. These filters are available from the drop-down list which is present on top of the table. About using the List View to monitor NetBackup policies You can perform the following tasks from this view: Use filters to view specific policies See “Filtering on NetBackup policy type” on page 456. Active Policies . See “Viewing details for a single NetBackup policy” on page 458. See “Viewing the history for a single job policy ” on page 460. The built-in filters are the following: All Policies (default filter) Select this filter to view details of all NetBackup policies. See “Viewing the details for a master server associated with a policy” on page 458. See “About using tables” on page 71.

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 74. Table 7-5 Tab General Monitor > Policies page tabs Description The General tab of the Details pane displays all information available for the policy. Monitor > Policies page There are four tabs in the Details pane on the Monitor > Policies page. To filters details by type of policy 1 2 In the OpsCenter console. Select a filter from the drop-down list. Schedules The Schedules tab displays details of the schedules that are associated with the policy. You can also click the master server name (link) to get details of the master server. The Clients tab shows details of clients to be backed up by the policy. Use the following procedure to view details by type of policy. It also includes contents of all the columns that can be viewed from the table. Select this filter to view details of Standard policies. Clients .Monitoring NetBackup using Symantec OpsCenter Monitor > Services view 457 Inactive Policies Select this filter to view details of the policies that are inactive. 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 Monitor > Policies. SAP policies. Note that the drop-down list is located on top of the table. you can also create your own custom filters. Select this filter to view details of catalog policies. OS2 policies etc.

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. The details of the master server are shown on a separate page. To view the details for a volume pool that is associated with a policy 1 2 In the OpsCenter console. Click the server name (link) associated with the policy from the Master Server column of the table. select Monitor > Policies. The details of the volume pool are shown on a separate page. See “Monitor > Policies page” on page 457. select Monitor > Policies. Viewing details for a single NetBackup policy All the details that are associated with a policy can be viewed from the Details pane. To view details for a single NetBackup policy 1 2 3 In the OpsCenter console. Click the name (link) for a policy from the Name column of the table.458 Monitoring NetBackup using Symantec OpsCenter Monitor > Services view Table 7-5 Tab Selections Monitor > Policies page tabs (continued) Description The Selections tab shows the files that have been backed up by the policy and also their location. The Details pane is located at the bottom of the Monitor > Jobs view. 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. You can also enable or disable data collection for the master server from this page. To view the details for a master server 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. The Details pane has four tabs. View the policy details in the Details pane.

To start a manual backup 1 2 3 4 In the OpsCenter console. Note: This task is not visible if you log on with an Analyst or a Reporter role. You can select a schedule and a client from the drop-down lists for the backup. The OpsCenter console may take some time to show the updated status once you perform these tasks. or only select a schedule or a client. Select a job policy from the table. If you do not select a client. NetBackup uses the schedule with the highest retention level. Select a policy from the table. select Monitor > Policies. Click Manual Backup. Note that these options are located on top of the table. Before you perform these tasks. Note: These tasks are not visible if you log on with an Analyst or a Reporter role. The OpsCenter console may take some time to show the updated status once you perform this task. Starting a manual backup Use the following procedure to start a manual backup. Note that this option is located on top of the table. To activate or deactivate a policy 1 2 3 In the OpsCenter console. You can select only one policy and it must be an active policy. . Click Activate or Deactivate. select Monitor > Policies. manually refresh your Web browser to obtain an updated view of all policies. NetBackup backs up all scheduled clients. If you do not select a schedule.Monitoring NetBackup using Symantec OpsCenter Monitor > Services view 459 Activating or deactivating a job policy Use the following procedure to activate or deactivate a policy. manually refresh your Web browser to obtain an updated view of all policies. Before you perform this task.

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. Note: This task is not visible if you log on with an Analyst or a Reporter role. Select a job policy from the table. Monitor > Policies Summary View This view is displayed when you select Monitor > Policies and then select Summary View from the drop-down list. of Jobs section . Note that this option is located on top of the table. Data for the last 24 hours is shown by default. You can also view data for the last 48 hours or 72 hours. The content that is shown in the Summary View is based on the current View pane and time frame selection. To view only the differences between the versions. The drop-down list is located at the top-right corner of the page. To view the history for a policy 1 2 3 4 In the OpsCenter console. The table and the pie charts include links to filtered detail views. The Compare Policies tab displays the policy versions. These sections show specific policy information in a table as well as a pie chart. Click View History. The changes are highlighted in red color. You must select two versions from the Retirement Date column to compare versions. This view contains detailed information about policies.460 Monitoring NetBackup using Symantec OpsCenter Monitor > Services view Viewing the history for a single job policy Use the following procedure to view the history for a policy. You can use these links to drill down and access detailed information about NetBackup policies. See “Controlling the scope of Monitor views” on page 425. select Monitor > Policies. click the View Differences tab. The Summary View contains the different sections which display specific information about NetBackup policies.

See “Controlling the scope of Monitor views” on page 425. See “About Top 7 Policies by No. This data is based on the current View pane and time frame selection. . of Jobs section lists seven policies which have the maximum number of jobs. You can also view data for the last 48 hours or 72 hours.Monitoring NetBackup using Symantec OpsCenter Monitor > Services view 461 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 time frame selection. The table that is shown in the section lists the top seven policies which have maximum failed jobs associated with them. See “About Top 5 Policies by Data Backed up section” on page 461. 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 time frame selection. The table also shows the data that is backed up for each policy. See “About Top 7 Policies by Failed Jobs section” on page 461. of Jobs section The Top 7 Policies by No. Data for the last 24 hours is shown by default. Data for the last 24 hours is shown by default. About Top 7 Policies by No. you can quickly view the policies which have the maximum data backed up. From this section. You can also view data for the last 48 hours or 72 hours. The table also shows the total number of failed jobs for each policy. You can also view data for the last 48 hours or 72 hours. Data for the last 24 hours is shown by default. Note: This section can also be viewed from Monitor > Overview. of Jobs section” on page 461. See “Controlling the scope of Monitor views” on page 425. The table that is shown in the section lists the top five policies which have maximum data backed up. you can quickly view the policies which have the maximum failed jobs associated with them. From this section. See “About Top 7 Policies by No. Note that the data that is backed up (shown in Volume (Bytes) column) is arranged in descending order in the table. Note that the failed jobs (shown in Total Number of Jobs column) are arranged in descending order in the table. of Jobs section” on page 461.

This view shows detailed information about NetBackup media for the current View pane selection. The table that is shown in the section lists the policies which have maximum number of jobs. 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. See “About Top 5 Policies by Data Backed up section” on page 461. The table also shows the total number of jobs for each policy. About monitoring NetBackup media The Monitor > Media view provides details of NetBackup media. It also shows other media details that are associated with the master server like Frozen Media Count. Hierarchical View by Volume Pool The Hierarchical View by Volume Pool shows details of all media and also groups media by volume pool for the current View pane selection. See “About Top 7 Policies by Failed Jobs section” on page 461. you can quickly view the policies which have the maximum number of jobs associated with them. See “Monitor > Media List View options” on page 463. See “Monitor > Media Summary View options” on page 468. From this section. Summary View The Summary View displays the volume pool available for each master server for the current View pane selection. .462 Monitoring NetBackup using Symantec OpsCenter Monitor > Services view See “Controlling the scope of Monitor views” on page 425. 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. See “About using the Hierarchical View by Volume Pool for monitoring media” on page 468.

Click the link to view details about the media. The drop-down list is located at the top-right corner of the page. Unique. The date when the volume was assigned for use. See “Controlling the scope of Monitor views” on page 425. This data is based on the current View pane selection. Click the link to view details of master server. tl8 etc. Example: tl4. See “About using the Hierarchical View by Volume Group for monitoring media” on page 470. Specifies the robot type of the robot to inventory. 4mm etc. Name of the master server that is associated with the media. The table that appears in this view has the following columns: Table 7-6 Media List View options Description Unique ID associated with a media. Note: You can select these views from the drop-down list.Monitoring NetBackup using Symantec OpsCenter Monitor > Services view 463 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. Monitor > Media List View options This view is displayed when you select Monitor > Media. This view contains detailed information for media. logical identification number for the robot to inventory. Column Head/Option Media ID Master Server Media Type Robot Type Robot Number Slot Mounts Time Assigned . Type of media like 8mm. Slot in the robot that contains the volume. The number of times that the volume has been mounted.

Current media status like Frozen. Active etc. Mounts Data Expiration Last Written Media Status Used Capacity Not all of the available columns appear initially in this view. Date when the images on the volume expire. Zero (0) indicates unlimited mounts. The most recent time NetBackup used the volume for backups. The following columns do not appear. Capacity that has been used. Column Head/Option Max.464 Monitoring NetBackup using Symantec OpsCenter Monitor > Services view Table 7-6 Media List View options (continued) Description The maximum number of mounts (or cleanings) that are allowed for the volume. but can be added to your view by clicking the Table Settings icon: ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Last Write Host Side Partner First Mount Last Mount Cleanings Remaining Created Description Vault Name Date Vaulted Return Date Vault Slot Session ID Vault Container ID Last Read Images Valid Images Number of Restores .

Control media Viewing the details for NetBackup media All the details that are associated with a media can be viewed from the Details pane. About using the List View to monitor NetBackup media 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 465. 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 466. See “About using tables” on page 71. . More information about how to customize tables and view specific columns is available. See “Controlling media” on page 467. See “Filtering on NetBackup media type” on page 466. The Details pane is located at the bottom of the view.Monitoring NetBackup using Symantec OpsCenter About using the List View to monitor NetBackup media 465 ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ 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.

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. Click the server name (link) associated with the media in the Master Server column of the table.466 Monitoring NetBackup using Symantec OpsCenter Viewing the details for a master server associated with the media 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. The details of the master server are shown on a separate page. View the media properties from the Details pane. 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. These filters are available from the drop-down list which is present on top of the table. select Monitor > Media. The built-in filters are the following: All Media (default filter) Assigned Media Select this filter to view details of all media. Select this filter to view details of the media that have been assigned to an individual for further action. Click a drilldown link from the Media ID column. Unassigned Media Frozen Media Full Media . From the Details pane. you can also click the master server link to see details about the master server that is associated with the media. Select this filter to view details of the media that are frozen. Select this filter to view details of the media that are unassigned. you can create and apply a filter that displays full media only. select Monitor > Media. Select this filter to view details of the media that are full. You can filter by using any of the built-in filters. For example.

Unfreeze. Controlling media Use the following procedure to freeze. Use the following procedure to view details by type of media. unfreeze. suspend. The media is assigned if there is a date in the Time Assigned column. To perform media tasks 1 2 3 In the OpsCenter console. Select a media ID from the table (use the check box).Monitoring NetBackup using Symantec OpsCenter Controlling media 467 Suspended Media Select this filter to view details of the media that are suspended. or Unsuspend. Note that to perform these tasks the media must be assigned to NetBackup. . Select a filter from the drop-down list. To filter details by type of media 1 2 In the OpsCenter console. select Monitor > Media. select Monitor > Media. Select this filter to view details of media with Active status. BE media etc. Select this filter to view details of cleaning media. or unsuspend specific media. Note that the drop-down list is located on top of the table. See “Using filters to customize your views” on page 74. Other Media Active Media Cleaning Media In addition to the built-in filters. Click Freeze. The OpsCenter console may take some time to show the updated status once you perform these tasks. Select this filter to view details of all other media like Multi Retention Level media. you can create your own custom filters. Suspend. Note that these options are present on top of the table. Note: These tasks are not visible if you log on with an Analyst or a Reporter role.

Suspended Media Count etc. Total number of all other media like Multi Retention Level media. The drop-down list . It also shows other media details that are associated with the master server like Frozen Media Count. Total number of the media that are available for the master server. See “Controlling the scope of Monitor views” on page 425. The table that appears in this view displays the volume pool available for each master server. The drop-down list is located at the top-right corner of the page.468 Monitoring NetBackup using Symantec OpsCenter Monitor > Media Summary View options Monitor > Media Summary View options This view is displayed when you select Monitor > Media and then select Summary View from the drop-down list. Total number of active media that are associated with the master server. Total number of the full media that are associated with the master server. Total number of the suspended media that is associated with the master server. that are associated with the master server . The data that is shown in this view is based on the current View pane selection. BE media etc. The following columns are shown in the table: Table 7-7 Media Summary View options Description 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. Option/Column Head Master Server Volume Pool name Frozen Media Count Suspended Media Count Full Media Count Active Media Count Other Media Count Available Media Count About 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.

Monitoring NetBackup using Symantec OpsCenter Viewing the details for volume pool 469 is located at the top-right corner of the page. select Monitor > Media. Select Hierarchical View by Volume Pool from the drop-down list. The data that is shown in this view is based on the current View pane selection. Note that a volume pool has a + sign on the left side. . The drop-down list is located at the top-right corner of the page. Control media See “Controlling media” on page 470. The Hierarchical View by Volume Pool shows details of all media and also groups media by volume pool. the current selected sort order is applied to media in the pool. Click a volume pool (link) from the Media ID column. To view details for a volume pool 1 2 3 In the OpsCenter console. The following tasks can be performed from this view: View the details for volume pool See “Viewing the details for volume pool” on page 469. Viewing the details for volume pool Use the following procedure to view the details for a volume pool. Note that the media are indented to the right-hand side in the Media ID column. You can expand a volume pool to see all media that are a part of this volume pool. See “Controlling the scope of Monitor views” on page 425. When you expand a volume pool. View details for the media that are a part of See “Viewing the details for media” a specific volume pool on page 469. The details for the volume pool are shown in the General tab at the bottom of this view. The sorting feature in this view applies only to media in the volume pool. Each volume pool that is shown in the Media ID column has a +sign before it. Viewing the details for media Use the following procedure to view details for the media that are part of a specific volume pool.

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

You can expand a volume group to see all media that are a part of this volume group. Viewing the details for a volume group Use the following procedure to view the details for a specific volume group. select Monitor > Media. Control media See “Controlling media in OpsCenter” on page 472. The sorting feature in this view applies to media in the volume group. When you expand a volume group. Note that the media are indented to the right-hand side in the Media ID column. The details for the volume group are shown in the General tab at the bottom of this view. the current selected sort order is applied to media in that group.Monitoring NetBackup using Symantec OpsCenter Viewing the details for a volume group 471 list is located at the top-right corner of the page. Each volume group shown in the Media ID column has a +sign before it. Note that a volume group has a + sign on the left side. Click a volume group (link) from the Media ID column. See “Controlling the scope of Monitor views” on page 425. 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. 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 471. View details for the media that are part of a See “Viewing the details for media” specific volume group on page 471. Viewing the details for media Use the following procedure to view details for media that are part of a specific volume group. . The data that is shown in this view is based on the current View pane selection. Select Hierarchical View by Volume Group from the drop-down list. The Hierarchical View by Volume Group shows details of all media and also groups media by volume group.

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

This view shows the current drive status information. The contents of the Drives tab are shown by default. it is not shown in the Paths tab that appears in the List View. 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. Monitor > Devices > Drives List View options This view is displayed when you select Monitor > Devices > Drives. See “Monitor > Devices > Drives List View options” on page 473.1 master servers. This view displays the current drive status information based on the current View pane selection. The table that appears in this view shows the following information: Table 7-8 Drives List View options Description The name that is assigned to the drive when it was added to NetBackup. Similarly if one of the paths for a drive is unreachable or disabled. See “Monitor > Devices > Disk Pools options” on page 478. Option/Column Head Drive Name Device Host Master Server Drive Type . 8mm etc. Name of the master server that is associated with the drive. See “Monitor > Devices > Drives Summary View” on page 477.1 and 7. Note: For 7. Type of drive like 4mm. See “Controlling the scope of Monitor views” on page 425. The data that is shown in this view is based on the current View pane selection.Monitoring NetBackup using Symantec OpsCenter Monitor > Devices > Drives List View options 473 Drives This tab is shown by default when you select Monitor > Devices. the List View does not show a drive that is unreachable or disabled. The name of the device host where the drive is connected.0.

The following columns do not appear. Option/Column Head Robot Type Not all of the available columns appear initially in this view. 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 .474 Monitoring NetBackup using Symantec OpsCenter Monitor > Devices > Drives List View options Table 7-8 Drives List View options (continued) Description The type of robot that contains this drive.

. See “Filtering on NetBackup drive category” on page 476. See “Controlling drives” on page 477. From the General tab. The List View is shown by default. you can also click the master server link to see details about the master server that is associated with the drive. More information about how to customize tables and view specific columns is available. The drive information can be viewed from the General and Paths tab of the Details pane. The Details pane is located at the bottom of the view. About using the List View for monitoring drives 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 475.Monitoring NetBackup using Symantec OpsCenter About using the List View for monitoring drives 475 ■ ■ ■ ■ ■ ■ Opr Comment Ready Request ID Scan Host VM Host Write Enabled See the online NetBackup Administration Console Help for a detailed description of these fields. 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 476. See “About using tables” on page 71. 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.

all drive paths are down. you can apply a filter that displays only those drives that are up. 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. The following built-in filters are available: All Drives The All Drives filter is the default filter. Click the drilldown link from the Master Server column. The master server information can be viewed from a separate page. Select this filter to view only those drives that are down. For mixed drives. The List View is shown by default. Select this filter to view only those drives that are up. all drive paths are up. These filters are available from the drop-down list which is present on top of the table. . For example. You can filter by using any of the built-in filters. some drive paths are up and some drive paths are down. Select this filter to view all drives. Use the following procedure to view details by type of drives. To view the details for a master server associated with a drive 1 2 Select Monitor > Devices > Drives. Select this filter to view mixed drives. For up drives. For down drives. Up Drives Down Drives Mixed Drives In addition to the built-in filters. See “Using filters to customize your views” on page 74.476 Monitoring NetBackup using Symantec OpsCenter Viewing the details for a master server associated with a drive Viewing the details for a master server associated with a drive Use the following procedure to view details for a master server that is associated with a drive. you can create your own custom filters.

To control drives 1 2 3 In the OpsCenter console. Note that the drop-down list is located on top of the table. Note: These tasks are not visible if you log on with an Analyst or a Reporter role. select Monitor > Devices > Drives. Click Up. The OpsCenter console may take some time to show the updated status once you perform these tasks. Note that these options are located on top of the drive details table. Controlling drives See the NetBackup Administrator's Guide. . or Reset. Before you perform these tasks. Select a drive from the Drive Name column in the table. Monitor > Devices > Drives Summary View This view is displayed when you select Monitor > Devices > Drives and then select Summary View from the drop-down list. select Monitor > Devices > Drives. you also ensure that the drive is not involved in any tasks by other users. Ensure that List View is selected in the drop-down list. The drop-down list is located at the top-right corner of the page. The List View is displayed by default.Monitoring NetBackup using Symantec OpsCenter Controlling drives 477 To filter details by type of drives 1 2 In the OpsCenter console. When you refresh. Down. The Summary view contains the following section: See “Viewing the Drive Summary by Status” on page 478. manually refresh your Web browser to obtain an updated view of all drives. Volume I for information on drive states and how to control drives. Select a filter from the drop-down list.

■ Monitor > Devices > Disk Pools options This view is displayed when you select Monitor > Devices > Disk Pools. click the green section of the pie chart to view details for the drives that are up. For example. You can also view the color code summary in this section to know the colors that represent different exit status. click the number for Up drives Or Click a colored section of the pie chart that corresponds to a particular drive status. Select Summary View from the drop-down list. This information is shown in a pie chart as well as a table. pointing to the green color in the pie chart shows that 5 drives or 100% drives in your environment are up. the Drive Summary by Status section does not show the drives that are disabled or unreachable.478 Monitoring NetBackup using Symantec OpsCenter Viewing the Drive Summary by Status Viewing the Drive Summary by Status The Drive Summary by Status section shows an overall distribution of drives by drive status for the current View pane selection. Note: The Drive Summary by Status section can also be viewed from Monitor > Overview. select Monitor > Jobs. do either of the following: ■ Click the number of drives (link) for a particular drive status from the table. The drop-down list is located at the top-right corner of the page.0.1 and 7. You can drill down from this section to see details of the drives that are up or down. For example. This view displays detailed information about the disk pools that are configured for use by . For example. Moving your mouse over the pie chart shows the number and percentage of drives with up or down status in your NetBackup environment. Note: For 7. 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.1 master servers. To view drives by drive status 1 2 3 In the OpsCenter console.

See “Controlling the scope of Monitor views” on page 425. You can perform the following task from 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. Number of Volumes Used Capacity Raw Size Usable Size Low Watermark (%) Not all of the available columns appear initially in this view.Monitoring NetBackup using Symantec OpsCenter Monitor > Devices > Disk Pools options 479 NetBackup.) When the capacity of the disk pool returns to the low water mark. The low water mark for the disk pool. Number of disk volumes in the disk pool. (The default is 80%. NetBackup again assigns jobs to the storage unit. The total raw. For OpenStorage. 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. More information about how to customize tables and view specific columns is available. the server type depends on the vendor name. The following columns do not appear. The amount of storage space in use. The table that appears in this view shows the following information: Name Server Type Name of the disk pool The storage server type. See “About using tables” on page 71. unformatted size of the storage in the disk pool.

See “Monitor > Hosts > Clients view” on page 483. From the General tab. 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. Click the drilldown link from the Name column. you can also click the master server link to see details about the master server that is associated with the disk pool. 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. About monitoring NetBackup hosts This view is displayed when you select Monitor > Hosts. This view displays detailed information about NetBackup master servers based on the current View pane selection. Media Server This view displays detailed information about NetBackup media servers based on the current View pane selection. .480 Monitoring NetBackup using Symantec OpsCenter Viewing the details for a single disk pool View the details for a single disk pool See “Viewing the details for a single disk pool” on page 480. select Monitor > Devices > Disk Pools. This view contains the following subtabs: Master Server This tab is shown by default when you select Monitor > Hosts. See “Monitor > Hosts > Media Servers view” on page 482. The disk pool information can be viewed from the General and Disk Volume tab of the Details pane. Client This view displays detailed information about NetBackup clients based on the current View pane selection. See “Monitor > Hosts > Master Servers view” on page 481.

The built-in filters are the following: . The table that appears in this view shows the following columns: Table 7-9 Master Servers view options Description Fully qualified domain name or IP address of the master server that is configured. This does not necessarily represent the last time that OpsCenter collected information from the master server. Option/Column Head Network Name Display Name Operating System Product Last Contact State 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 481. The data that is shown in this view is based on the current View pane selection. 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. The display name that you have chosen for the master server.Monitoring NetBackup using Symantec OpsCenter Monitor > Hosts > Master Servers view 481 Monitor > Hosts > Master Servers view This view shows details of master servers. Backup Exec etc. Shows the current state of the master server like Connected. These filters are available from the drop-down list which is present on top of the table. The last time when OpsCenter successfully initiated contact with the master server. you can apply a filter that displays Windows servers only. Not Connected etc. Operating system of the master server. Back up product from where the data is being collected like PureDisk. See “Controlling the scope of Monitor views” on page 425. For example.

select Monitor > Hosts > Master Server. Select this filter to view details of Linux servers. Select this filter to view details of Solaris servers. Connected Servers Partially Connected Servers Not Connected Servers Windows Servers Solaris Servers Linux Servers Other Servers In addition to the built-in filters. Select a filter from the drop-down list. Select this filter to view details of those master servers that are connected. Note that the drop-down list is located on top of the table. Select this filter to view details of those master servers that appear as not connected. See “Controlling the scope of Monitor views” on page 425. Select this filter to view details of Windows servers.482 Monitoring NetBackup using Symantec OpsCenter Monitor > Hosts > Media Servers view All Servers (default filter) Select this filter to view details of all master servers. To filter details by type of master server 1 2 In the OpsCenter console. HP-UX servers etc. Use the following procedure to view details by type of master server. Select this filter to view details of those master servers that are partially connected. The table that appears in this view shows the following columns: . The data that is shown in this view is based on the current View pane selection. Monitor > Hosts > Media Servers view This view shows details of media servers. you can create your own custom filters. See “Using filters to customize your views” on page 74. Select this filter to view details of all other servers like AIX servers.

Name of the master server that is associated with the client. 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. Hardware of the client computer like PC. select Monitor > Hosts > Media Servers. Operating system on the client like Linux. To view the details of a master server that is associated with a media server 1 2 In the OpsCenter console. HP-UX etc. The table that appears in this view shows the following columns: Table 7-11 Option Client Name Master Server OS Type Hardware Clients view options Description Name of the client that is to be backed up.Monitoring NetBackup using Symantec OpsCenter Viewing the details of a master server that is associated with a media server 483 Table 7-10 Option Name Master Server Media Servers view options Description Name of the media server. Name of the master server that is associated with the media server. . Click the drilldown link from the Master Server column. See “Controlling the scope of Monitor views” on page 425. The data that is shown in this view is based on the current View pane selection. 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 483. Monitor > Hosts > Clients view This view shows details of NetBackup clients.

select Monitor > Hosts > Client. To view the details for a single master server 1 2 In the OpsCenter console. Click the drilldown link in the Master Server column. See “Controlling the scope of Monitor views” on page 425. The data that is shown in this view is based on the current View pane and time frame selection. See “Monitor > Alerts List View” on page 485.484 Monitoring NetBackup using Symantec OpsCenter Viewing the details for a single master server You can click Search Client to search for specific clients on the page. 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. The List View shows active alerts by default. About monitoring NetBackup alerts The Monitor > Alerts view provides details of NetBackup alerts. You can use the following views to see NetBackup alert information: List View The List View is shown by default when you select Monitor > Alerts. This view also lets you view detailed information about all NetBackup alerts and also filter. . Note: The OpsCenter console displays active alerts by default (these are the alerts that have not been cleared). Data for the last 24 hours is shown by default. 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 484. You can search for clients using absolute host names or substrings. You can also view data for the last 48 hours or 72 hours. respond to alerts.

Name of the policy that is associated with the alert. date. and year when the alert was modified. The alert condition that is used for the alert. date. Time. and to track user responses to alerts. This view contains detailed information for alerts. See “About using the Summary View for monitoring NetBackup alerts” on page 491. Data for the last 24 hours is shown by default. Note: The List View displays active alerts by default (these are the alerts that have not been cleared). Name of the individual to whom the alert has been assigned. and year when the alert was raised. See “Controlling the scope of Monitor views” on page 425. The data that is shown in this view is based on the current View pane and time frame selection. The severity of the alert. Monitor > Alerts List View The List view is displayed when you select Monitor > Alerts. Time. Current status of the alert like Active. The table that appears in this view shows the following information: Table 7-12 Option Alert ID Severity Alerts List View options Description Unique ID associated with each NetBackup alert.Monitoring NetBackup using Symantec OpsCenter Monitor > Alerts List View 485 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. The Summary View shows how active alerts are distributed in your environment as per the alert severity. You can also view data for the last 48 hours or 72 hours. Alert Policy Alert Condition Status Assigned To Time Raised Last Update Time . This information is shown in a pie chart as well as a table. This view provides tools to view and filter alerts. Cleared etc.

the time these comments were given and the individual who last updated the alert. job ID. About using the List View to monitor NetBackup alerts 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 486. but can be added to your view by clicking the Table Settings icon. See “Filtering by alert type” on page 487. The Comments tab shows comments on the alert (if any). 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. policy name. . See “Filtering by alert type” on page 487. See “Responding to alerts ” on page 488.486 Monitoring NetBackup using Symantec OpsCenter About using the List View to monitor NetBackup alerts Table 7-12 Option Updated by Alerts List View options (continued) Description Name of the individual who last modified the alert. the General tab also shows master server. Not all of the available columns appear initially in this view. The Details pane is located at the bottom of the view. The Assignment State column does not appear. In addition to the information that is shown in the table. Click a drill-down link from the Alert ID column. and exit status information. The alert details are shown under General and Comments tabs of the Details pane. See “Viewing the details of the alert policy associated with an alert” on page 487. select Monitor > Alerts. See “About using tables” on page 71. See “Viewing the details of the alert policy associated with an alert” on page 487. To view the details of a single alert 1 2 In the OpsCenter console. More information about how to customize tables and view specific columns is available.

You can use this filter to limit the types of alerts that appear. Select this filter to only view the alerts whose severity is Critical. You can filter using any of the following nine built-in alert filters. a filter is available. See “Viewing the details for a single alert” on page 486. You can filter on various severity levels or status settings. For example. which lets you focus on only the specific alerts that interest you. 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. Select this filter to only view the alerts whose severity is Major. Active (default filter) Select this filter to view Active alerts. Select this filter to only view the alerts whose severity is Informational. Select this filter to only view the alerts whose severity is Warning. select Monitor > Alerts. you can create and apply a filter that only displays the alerts that are acknowledged.Monitoring NetBackup using Symantec OpsCenter Viewing the details of the alert policy associated with an alert 487 See “Responding to alerts ” on page 488. Click the drill-down link from the Alert Policy column. This filter does not include the alerts that have been cleared. Critical Major Warning Informational . See “Filtering by alert type” on page 487. 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. See “Responding to alerts ” on page 488. To view the details of alert policy associated with the alert 1 2 In the OpsCenter console.

See “Viewing the details for a single alert” on page 486. More information on cleared alerts is available. Select this filter to only view the alerts that have been assigned to other OpsCenter users. See “Responding to alerts ” on page 488. you can create your own custom filters. If you clear 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. Use the following procedure to view details by type of alerts. This filter includes both active alerts and cleared alerts. select Monitor > Alerts.488 Monitoring NetBackup using Symantec OpsCenter Responding to alerts Unassigned Select this filter to only view the alerts that have not been assigned to anybody. See “Responding to alerts ” on page 488. In addition to the built-in filters. Cleared alerts do not appear in the alert view by default. . Assigned Acknowledged Cleared All Alerts Select this filter to view the details of all alerts. See “Viewing the details of the alert policy associated with an alert” on page 487. you cannot perform any further activity on the alert (for example. select All Alerts to view details of both active alerts and cleared alerts. When you acknowledge an alert. See “Using filters to customize your views” on page 74. assign or acknowledge). You can also clear or acknowledge an alert. To filter details by type of alert 1 2 In the OpsCenter console. For example. Select a filter using the Filter drop-down list. OpsCenter allows multiple users to process or take action on an alert. Select this filter to only view the alerts that have been cleared. you inform other users who see the alert that action on the alert occurred. Select this filter to only view the alerts that have been acknowledged by an OpsCenter user.

an OpsCenter user comments on an alert while another OpsCenter user tries to clear the same alert. Some alerts (for example. The OpsCenter console displays active alerts by default (these are the alerts that have not been cleared). See “Filtering by alert type” on page 487. Drive is Down) are cleared automatically when the condition is resolved. For instance. 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 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.Monitoring NetBackup using Symantec OpsCenter Responding to alerts 489 Note: Under certain circumstances there may be issues among multiple OpsCenter users.

Any purged data is deleted permanently. Select an alert from the table. This option is useful if you see OpsCenter performance degrade when there is a high number of alerts in the OpsCenter database. select Monitor > Alerts. Click Assign. See “Configuring the data purge period on the OpsCenter Server” on page 309. Select an alert from the table. Select an alert from the table. To clear an alert 1 2 3 In the OpsCenter console. Click More and then select Clear from the drop-down list. 4 5 Select a user to whom you want to assign the alert. 3 Click More and then select Edit Policy from the drop-down list. The Alert Policy Wizard is also used to create a policy. Click Add Comment. You can add a comment as a reminder to yourself or for other users. select Monitor > Alerts. select Monitor > Alerts. . To acknowledge an alert 1 2 3 In the OpsCenter console. Click Acknowledge or Clear. select Monitor > Alerts. 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. You can assign an alert to a user for their action or information. Click OK. Select an alert from the table. To change the policy that is associated with an alert 1 2 In the OpsCenter console. Select an alert from the table.490 Monitoring NetBackup using Symantec OpsCenter Responding to alerts 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.

Note: The Summary View only displays active alerts (these are the alerts that have not been cleared). or 17% alerts in your environment are critical. Data for the last 24 hours is shown by default. See “Viewing alerts by severity” on page 491. Viewing alerts by severity You can drill down to see details for alert categories. See “Viewing the details for a single alert” on page 486. Note: The Alert Summary by Severity section can also be viewed from Monitor > Overview. A pie chart with different colors represents the alert distribution by severity in this section. See “Viewing the details of the alert policy associated with an alert” on page 487. About using the Summary View for monitoring NetBackup alerts The Summary View gives an overall summary of alerts by severity. Moving your mouse over the pie chart displays the number and percentage of alerts with a particular severity in your NetBackup environment. Each color of the pie chart represents how alerts are distributed in your environment as per the alert severity. pointing to the green color in the pie chart shows that in the last 24 hours. For example. It contains the Alert Summary by Severity section which shows an overall distribution of alerts by severity for the current View pane and time frame selection. You can also view the color code summary in this section to know the colors that represent different severity. See “About understanding alert counts in the Monitor view” on page 516.Monitoring NetBackup using Symantec OpsCenter About using the Summary View for monitoring NetBackup alerts 491 See “About understanding alert counts in the Monitor view” on page 516. See “Filtering by alert type” on page 487. You can drill down from this section to see details for alert categories. See “Controlling the scope of Monitor views” on page 425. This information is shown in a pie chart as well as a table. 200 alerts. . You can also view data for the last 48 hours or 72 hours.

■ See “About using the Summary View for monitoring NetBackup alerts” on page 491. For example. changes such as creating a policy. About Audit Trails Audit trails is a record of all the user initiated activities. Through OpsCenter. and storage server. Monitoring Audit Trails You can manage and monitor audit trails using the OpsCenter features. click the number that is shown for Critical alerts. The audit trails feature in OpsCenter lets you enable audit trail logging for NetBackup. For example. such as whether a policy is modified. do either of the following: ■ Click the number of alerts (link) for a particular alert severity from the table. The drop-down list is located at the top-right corner of the page.1 or later. or deleted. deactivating a policy. or modifying a policy. For example. You can control the audit settings and generate an Audit Trails Report. select Monitor > Alerts. An audit trail consists of the changes that are made in the NetBackup environment. pool. jobs. and manages audit trails for the NetBackup master servers for the version 7. For example. Note: OpsCenter monitors. click the red section of the pie chart to view details for critical alerts. reports . audit configuration. or a storage server is deleted. Audit trails display the following information in the form of columns: ■ Category: Displays the changes that are made to policies. Or Click a colored section of the pie chart that corresponds to a particular alert severity. you can set the audit logs retention period and also enable or disable audit trail logging. In the Alert Summary by Severity section.492 Monitoring NetBackup using Symantec OpsCenter Monitoring Audit Trails To view alerts by severity 1 2 3 In the OpsCenter console. modified. ■ . audit service. Select Summary View from the drop-down list. storage units. Action: Displays the action performed. when a storage unit is added. a storage unit is created.

Some of the categories are Policy. Reason: Displays the reason for the change that is made. policies modified. To view the details of the audit trails report in a tabular form. For example. You can view the report in a Distribution chart or Historical chart format The chart displays the count of audit records for each category. and policies deleted. you can: ■ ■ ■ Manage the audit settings of the NetBackup master server. The report is displayed in the form of a chart. By default. Some of the attributes that are modified are Clients. Audit Configuration. It also gives the identity of the category. . if you click the Policy section. the column is hidden. Generate alerts if audit service goes down. and Storage Server. ■ ■ ■ ■ ■ About the Audit Trails report The Audit Trails report is a high-level summary report that is added to the reports tree. and Percentage. You can view the count of changes for each action for the selected category. Audit service.Monitoring NetBackup using Symantec OpsCenter Monitoring Audit Trails 493 ■ Description: Gives a brief information about the category and the action performed. Pool. click the link Show Chart as Table. The table displays information about the Audit Category. Timestamp: Displays the time when the action was performed. Monitor audit trails. Through OpsCenter. and Policy Generation. Storage unit. You can hover the mouse on each colored section of the chart to know the count and the percent changes for each category. Job. Total Audit Count. This report displays the number of changes that are made in the NetBackup environment. User: Gives the information about the user who initiated the action. Operating System (OS). Hardware. About OpsCenter features for Audit Trails OpsCenter helps you to configure audit logging and generate the Audit report. The table also displays the information about Audit Action when you drill down the chart. You can drill down the report by clicking any colored section of the chart. Details: Displays the old and new values of the attributes that are modified. if given by the user who makes the change. Master Server: Displays the name of the master server on which the action is performed. the chart displays the total audit count for policies created.

From the Operator drop-down list. Domain Name. See “Managing Audit Trails settings” on page 535. . Time Stamp. If you select Time Stamp as the column. User Name. Object Name. and set the retention period of the logs. Action. You can enable or disable the audit settings. The Edit Audit filter dialog box is displayed. Monitoring Audit Trails OpsCenter helps you to monitor the audit trails. In the Value text box. Domain Type. Enter a name for the filter in the Name field. Click the calendar icon to choose the required date and click OK. and Master Server. Use != if you do not want to match a specific value. You can use predefined filters based on category and action to display the contents of the Audit trails and also create custom filters. You can view information about predefined and custom filters. You can set OpsCenter to generate alerts when the NetBackup Audit manager services are turned on or off. To create a custom filter to view audit trail data 1 2 3 Select the Create Filter icon. 4 Select And or Or from the drop-down list to build the filter query. a calendar icon appears for value. You can also set the retention period for the audit logs. enter or select a value. Object Name is filtered based on the entity names present in the description. Select the column name that you want to filter from the drop-down list. See “Using filters to customize your views” on page 74. To monitor them. Use the various features of OpsCenter and generate the Audit report. Managing Audit Trails settings You can manage the settings to enable the auditing for the selected master server through OpsCenter. You must have Admin privileges to configure the audit settings. select the operator =.494 Monitoring NetBackup using Symantec OpsCenter Monitoring Audit Trails ■ Configure audit trail retention period in OpsCenter. select Monitor > Audit Trails. The options available are Category.

click Add and select the required column name. Once you are done adding the required columns to the filter.Monitoring NetBackup using Symantec OpsCenter Monitoring Audit Trails 495 5 6 To add more columns to the query. select Remove. editing the filter. click OK. . The new view filter is displayed in the filter drop-down list. To remove the column that is created. You can view more information about applying the filter. and deleting the filter. See “View filters in OpsCenter” on page 420.

496 Monitoring NetBackup using Symantec OpsCenter Monitoring Audit Trails .

you can view and manage your NetBackup environment. Most of the data is sent by NetBackup and appears almost instantaneously after it changes. or browser refresh settings can affect how quickly it appears). and displays it on demand. (Network. system delays. storage. It cannot monitor or manage other products like Symantec NetBackup PureDisk.Chapter 8 Managing NetBackup using Symantec OpsCenter This chapter includes the following topics: ■ ■ ■ ■ ■ ■ ■ About the Manage views Controlling the scope of Manage views About managing alert policies About managing NetBackup storage About managing NetBackup devices About managing NetBackup Hosts About managing NetBackup Deployment Analysis About the Manage views From the Manage tab and associated subtabs. stores it in a database. This data is collected . The OpsCenter server collects data from NetBackup master servers. Symantec Enterprise Vault etc. Note that OpsCenter or OpsCenter Analytics can only monitor and manage NetBackup. and devices. which also includes OpsCenter alert policies.

See “How OpsCenter collects data from NetBackup” on page 364. select ALL MASTER SERVERS from the drop-down list in the View pane. Use the following procedure to view details of all master servers or specific master servers. you can create a view like Geography to view details about master servers in a particular region like Europe. For example. Deselect the checkbox next to ALL MASTER SERVERS and select specific master servers from the list of master servers. 3 .498 Managing NetBackup using Symantec OpsCenter Controlling the scope of Manage views mainly using notifications. you can also create your own views from Settings > Views or by using Java View Builder. See the online Symantec OpsCenter Java View Builder Help to know how you can create views using Java View Builder. More information about how to create views using Settings > Views is available. For most operations and changes in NetBackup. ALL MASTER SERVERS.e. In addition to using the default view i. 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 “About OpsCenter views” on page 409. Controlling the scope of Manage views The content that is shown in the Manage views is based on your current View pane selection. To view details of all master servers ◆ In the OpsCenter console. NBSL sends a notification to OpsCenter. Ensure that other master servers are unchecked. select ALL MASTER SERVERS from the drop-down list in the View pane. Click Apply Selection. To view details of specific master servers 1 2 In the OpsCenter console.

Explains how you can view the alerts that are associated with an alert policy. Explains how to create an alert policy using the Alert Policy Wizard. activating. . When a NetBackup system event triggers an alert (based on your alert policies).Managing NetBackup using Symantec OpsCenter About managing alert policies 499 About managing alert policies Table 8-1 lists the topics that describe how to manage alert policies. Alert policies help you manage your NetBackup environment by providing constant monitoring of your NetBackup systems. or deactivating an alert policy. See “About creating (or changing) an alert policy” on page 501. deleting. Administrators do not need to monitor a terminal continuously. the following occurs: ■ OpsCenter sends email or SNMP notices to any recipients that are configured in the policy. Explains how to view the details for an alert policy. ■ You can specify email or SNMP notification in response to an alert. which lets administrators focus on other job responsibilities. See “Filtering on type of alert policy” on page 500. Explains the tasks that are available for managing a single alert policy. Topic contents and description Description Explains the concept of alert policies. See “Viewing the alerts associated with an alert policy” on page 518. See “Viewing the details for a single alert policy” on page 500. Management includes tasks like editing. About OpsCenter alert policies OpsCenter provides tools to create and manage alert policies and handle any resulting alerts that the policies generate. The OpsCenter console displays views to help you track and manage these alerts. Explains how to filter and view the alert policies that are of interest to you. OpsCenter helps you manage your NetBackup server network by generating alerts or sending email and trap notifications (or both). See “Managing an alert policy ” on page 517. copying. When certain events or conditions occur in your environment. Table 8-1 Topic See “About OpsCenter alert policies” on page 499.

warning. All Alert Policies Enabled Alert Policies Select this filter to view all alert policies. The General tab displays all the details that are shown in the table. select Manage > Alert Policies. The alert policy details are shown at the bottom of this view under the General tab. Disabled Alert Policies You can also create your own filters which let you focus on only the specific alert policies that interest you. select Manage > Alert Policies. To view the details for a single alert policy 1 2 In the OpsCenter console. an OpsCenter user changes a policy while another user tries to remove the same policy. or critical. major. See “Using filters to customize your views” on page 74. . Note that the drop-down list is located on top of the table. Select this filter to view the alert policies that are disabled. These filters are available from the drop-down list which is present on top of the table. For instance. To filter on type of alert policy 1 2 In the OpsCenter console. Click a drill-down link from the Name column. You can filter using any of the following three built-in filters. Select a filter from the drop-down list. Select this filter to view the alert policies that are enabled. 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.500 Managing NetBackup using Symantec OpsCenter About managing alert policies Alert policies are defined as informational. 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. Under certain circumstances there may be issues among multiple OpsCenter users.

and also by email or SNMP traps. See “About understanding alert counts in the Monitor view” on page 516. The alerts help you to anticipate and handle problems before they occur. You can specify email and SNMP recipients while creating an alert policy.Managing NetBackup using Symantec OpsCenter About managing alert policies 501 About creating (or changing) an alert policy You can create alert policies to detect when something goes wrong with NetBackup and troubleshoot it. You can receive these alerts by logging on to OpsCenter. alert category. and descriptions. OpsCenter periodically retrieves data from NetBackup based on notifications and a wait time (of up to 15 minutes). OpsCenter Alert conditions OpsCenter comes with a set of predefined alert conditions. Periodic alert conditions Table 8-2 lists the alert conditions. This time delay between the NetBackup Activity Monitor and the OpsCenter console can mean that many intermediate job states may be lost. . OpsCenter retrieves data from NetBackup based on a wait time (of up to 15 minutes). You can then take corrective action. Alert conditions can be divided into the following categories: Event-based alert conditions For these alert conditions. For example. The following topics provide more information about alerts. See “Adding an alert policy” on page 509. See “Additional information on job policy change condition” on page 508. For these 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. See “OpsCenter Alert conditions” on page 501. OpsCenter retrieves data from NetBackup based on notifications from NBSL. You can create policies to automate responses to key events in your enterprise. you can create a policy to alert you when a job fails on a specific master server. You can monitor for frozen media and email the operator when the number of frozen media exceeds a threshold value.

Periodic .502 Managing NetBackup using Symantec OpsCenter About managing alert policies 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.

If a job starts at 4 minutes after a first check. If you configure OpsCenter to ignore the queued time for a job. Due to unavailability of resources. an alert may not occur. and the job completes (job duration = 33) before the fourth check.Managing NetBackup using Symantec OpsCenter About managing alert policies 503 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. was running less than the threshold during the second (job duration = 5 minutes) and third checks (job duration = 20 minutes). The job was not yet started during the first check. For example. In this case. a job may first be in a queued state before it becomes active. This time is a total execution of 33 (5 + 15 + 13) minutes. OpsCenter considers the start time of a job by default. For Hung Job alert. A job starts 10 minutes after a first check cycle and ends 13 minutes after the third check cycle is done. you can configure OpsCenter to ignore the time for which a job is in a queued state. While checking the Hung Job condition. This also includes the time for which a job is in a queued state. an alert is raised at the third check. but an alert is not raised. Alert condition Job finalized Events-based . OpsCenter considers the time when a job becomes active while checking the Hung Job condition. since the job has executed for 26 minutes (11 + 15 minutes). The Hung Job condition is checked every 15 minutes. Note that the active start time of the first attempt is considered. Depending upon when a job starts within a check cycle. the policy is checked four times. suppose a policy is created with a job threshold of 25 minutes. A job may not always be in an active state after it starts.

Alert condition Incomplete Job Events-based An alert is generated when a job of a specified type of the specified policy or client moves to an Incomplete state. of the specified policy or client ended in the specified status. Events-based An alert is generated when a restore operation requires media.504 Managing NetBackup using Symantec OpsCenter About managing alert policies 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. Media Frozen media 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. An alert is generated when the percentage of suspended media exceeds the predefined threshold value. Low available media High suspended media Periodic High frozen media Periodic . Events-based An alert is generated when any of the selected media is frozen. Exceeded max media mounts Media required for restore Events-based An alert is generated when a media exceeds the threshold number of mounts. The restore operation may require a specific media which contains the specific image to be restored.

gigabytes (GB). This does not necessarily mean that if you do not receive this alert. No Cleaning Tape Periodic Zero Cleaning Left Events-based An alert is generated when a cleaning tape has zero cleaning left. you can specify the threshold value for a particular policy in percentage. . Tape Mount Request Events-based An alert is generated on a media mount request. bytes. the catalog backup was successful. The generated alert can also show available catalog space using these units. terabytes (TB) or petabytes (PB) and generate alerts. kilobytes (KB). 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. If the policy has been defined for a server group.Managing NetBackup using Symantec OpsCenter About managing alert policies 505 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. For Catalog Space low condition. megabytes (MB). An alert is generated when catalog backup does not take place for a predefined time period. 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. The alert is not generated if no catalog backup policy exists for a master server.

An alert is generated when the percentage of down drives exceeds the predefined threshold value. An alert policy based on Disk Pool Full condition generates an alert only when the used capacity of the disk pool reaches the high water mark. Events-based An alert is generated when the selected disk volume(s) is down. High Down Drives Periodic .506 Managing NetBackup using Symantec OpsCenter About managing alert policies Table 8-2 Alert Type Disk 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. An alert is generated when a disk volume capacity is running below the threshold limit. Disk Volume Down Low Disk Volume Periodic Capacity Drive is Down Events-based An alert is generated when a drive in a specified robot or media server in the selected server context goes down.

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

only the selected job policy is monitored for change.508 Managing NetBackup using Symantec OpsCenter About managing alert policies 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. Alert condition Additional information on job policy change condition Review the following text for job policy alert condition. Multiple alerts are generated if multiple attributes are changed for a job policy See “Additional information on job policy change condition” on page 508. If you do not select any job policy. all the job policies are monitored for changes. 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 Check point 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 select a particular job policy.

select Manage > Alert Policies. Note: The Alert Policy Wizard is also used when you edit an alert policy. You may click Cancel to exit the wizard at any stage. Click Next to continue. 3 Enter a Name. Click Add. See “OpsCenter Alert conditions” on page 501. The Alert Policy Wizard appears. The required information and the required number of screens vary depending on the alert condition you choose. For some alert conditions. you can skip the optional screens.Managing NetBackup using Symantec OpsCenter About managing alert policies 509 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. To add an alert policy 1 2 In the OpsCenter console. Description. and Alert Condition on the General panel. See “Alert Policy Wizard” on page 511. .

the alert is still displayed in the Monitor > Alerts view. Click Next. Note that you can also view and select additional attributes like policies. Note that if you create an alert policy and do not define any recipients.) . You can select a view and a node that contains a group of master servers and also specific objects. For many alert conditions (for example. for the Job Finalized condition). do the following: ■ Select a severity level from the Alert Severity drop-down list. media servers etc. To select a specific master server. Click Next to continue. first deselect the view or node that contains the master server and then select the master server. node. 5 On the Scope panel. Note: This page is not shown if you have selected the Symantec ThreatCon alert condition. (If this alert occurs. 6 Optionally. on the Actions panel. or view from this page. select the view that should be verified for the alert condition. on expanding the views and nodes from this page (wherever applicable). in the Email Recipients and Trap Recipients sections. You must select at least one object. This is because the Symantec ThreatCon alert condition does not depend on any views or master servers. See “Adding SNMP trap recipients” on page 516.510 Managing NetBackup using Symantec OpsCenter About managing alert policies 4 On the Alert Condition Properties panel. you can select email or SNMP recipients (or both) to receive the alert notification. clients. the alert is displayed in the Monitor > Alerts view. These attributes define and limit the alert. You may also select only specific objects of a particular view or node to be checked for the alert condition. You may also deselect a specific master server from a view by selecting the view and then deselecting the specific master server. See “Adding email recipients” on page 515. you may need to enter threshold attributes and other required or optional attributes. In the Severity section. See “Alert Policy Wizard” on page 511. The attributes differ for each alert condition. specify attributes for the alert condition that you selected. These attributes are located under the applicable views or nodes for specific alert conditions.

you may need to enter threshold attributes and other required or optional attributes. These attributes define and limit the alert. Click Finish once the policy is successfully created. ■ 7 8 Click Save to save the alert policy. The Activate Condition option is checked by default. You can always activate or deactivate the policy later from the OpsCenter console.Managing NetBackup using Symantec OpsCenter About managing alert policies 511 ■ Select an appropriate severity level from the Severity of email/trap sent for cleared alert drop-down list. you can configure the severity for an email or trap that is sent when an alert is cleared. Deselect the Activate Condition option if you want to deactivate the policy. See “OpsCenter Alert conditions” on page 501. Select an alert condition from the list of alert conditions that are available. By default. The name must be unique. Table 8-4 Setting Alert Policy Wizard Alert Condition Properties Panel Description Specify attributes for the alert condition that you selected. With Severity of email/trap sent for cleared alert option. Specify properties for the selected alert condition . Alert Policy Wizard The Alert Policy Wizard consists of four panels. the policy will be active once you create it. The default severity level is Informational. The attributes differ for each alert condition. For many alert conditions (for example. Table 8-3 Setting Name Alert Policy Wizard General Panel Description Enter a name for the alert policy. This is a required field. Description Alert Condition Enter a description for the alert policy. See “Managing an alert policy ” on page 517. for the Job Finalized condition).

512 Managing NetBackup using Symantec OpsCenter About managing alert policies Table 8-5 Setting View Alert Policy Wizard Scope Panel Description .

In addition. you may select only a specific master server(s) under the default view ALL MASTER SERVERS to be checked for the alert condition.Managing NetBackup using Symantec OpsCenter About managing alert policies 513 Table 8-5 Setting Alert Policy Wizard Scope Panel (continued) Description Select the view that should be verified for the alert condition. first deselect the view or node that contains the master server and then select the master server. For example. For example. When you select a view like ALL MASTER SERVERS or a node that contains a group of master servers. master servers that you may add later to this view or node will also be automatically selected and hence verified for the alert condition. In case. all the master servers that are currently in the view or node are automatically selected. You can select a view and a node that contains a group of master servers and also specific objects. These attributes are located under the applicable views or nodes for specific alert conditions. you can select the default view ALL MASTER SERVERS to be checked for the alert condition. When you specifically deselect a master server from a view. it is recommended that you do not repeat a master server across groups. the deselection or exclusion is given a higher priority because of which the master server is not verified for the alert condition. server B will not be verified for the alert condition even though it is a part of the selected view or node. for the Job . You may also select only specific objects of a particular view or node to be checked for the alert condition. Note that you can also view and select additional attributes like policies. you have selected the ALL MASTER SERVERS view and then specifically deselected server B . You may also deselect a specific master server from a view by selecting the view and then deselecting the specific master server. clients. This is because you have specifically deselected server B from the ALL MASTER SERVER view. For example. on expanding the views and nodes from this page (wherever applicable). To select a specific master server. For this reason. Consider a scenario where there are two objects server A and server B in a particular view like ALL MASTER SERVERS. media servers etc. and in addition if you have selected a view or node that also contains server B. which is also part of another selected view.

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.) . or view from this page. Select a severity level from the Alert Severity drop-down list. node.514 Managing NetBackup using Symantec OpsCenter About managing alert policies Table 8-5 Setting Alert Policy Wizard Scope Panel (continued) Description Finalized alert condition. This is because the Symantec ThreatCon alert condition does not depend on any views or master servers. the alert is displayed in the Monitor > Alerts view. media server name. You can view the applicable attributes like policy name. robot number. client name. You must select at least one object. (If this alert occurs. Table 8-6 Setting Email Recipients Trap Recipients Alert Severity Alert Policy Wizard Actions Panel Description Select email recipients to receive the alert notification. Select SNMP recipients to receive the alert notification. drive IDs etc.

the policy will be active once you create it. Adding email recipients Follow this procedure to add email recipients to an Alert Policy. an alert is raised with the severity specified in the alert policy. This email or trap also has a Critical severity. For example. To add email recipients 1 2 While creating an alert policy using the Alert Policy Wizard. In OpsCenter. This is the default behavior. You can now configure the severity for this email or trap from Critical to some other severity like “Informational” while creating the alert policy.Managing NetBackup using Symantec OpsCenter About managing alert policies 515 Table 8-6 Setting Alert Policy Wizard Actions Panel (continued) Description Select an appropriate severity level from the Severity of email/trap sent for cleared alert drop-down list. Cc. See “Managing an alert policy ” on page 517. See “Adding an alert policy” on page 509. . you may have created an alert policy for a Hung Job alert condition with a Critical severity. Note that you can configure the severity only for email or trap. With Severity of email/trap sent for cleared alert option. By default. go to the Actions screen. Whenever this alert is cleared. an email or trap informing the user that the alert is cleared is sent with the same severity that is defined in the alert policy. or Bcc from the Email Recipients section. you receive Hung Job alert with Critical severity. you can configure the severity for an email or trap that is sent when an alert is cleared. Severity of email/trap sent for cleared alert Activate the Policy The Activate Condition option is checked by default. You can always activate or deactivate the policy later from the OpsCenter console. click To. The default severity level is Informational. On the Actions screen. When this Hung Job alert gets cleared. you receive an email or trap that informs you that the alert has been cleared. Deselect the Activate Condition option if you want to deactivate the policy. As a result.

About understanding alert counts in the Monitor view Alerts apply only to the object (master server) where the corresponding alert policy is created. For example. go to the Actions screen. For creating the policy. jobs from all of the master servers in the selected group are used to calculate the job failure rate. In the Add Trap Recipients dialog box. Click OK. 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.516 Managing NetBackup using Symantec OpsCenter About managing alert policies 3 In the Add Email Recipients dialog box. Since this master server is present in the view. the alert is listed only when you select the server group on which alert policy is created (or a parent group of that group). . for example High Job Failure Rate apply across groups. select the specific recipients from the Recipient Name column and click To. Click OK. Add Trap Recipients dialog box In the Add Trap Recipients dialog box. click To from the Trap Recipients section. or Bcc based on your requirements. Consider a case where you create an alert policy for a selected view that contains two master servers. a Frozen Media alert occurs when any of the selected media on the selected master server (object) are frozen. select the specific recipients from the Recipient Name column and click To. 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. When alerts are raised for that policy they are raised on the selected object. On the Actions screen. 4 Adding SNMP trap recipients Follow this procedure to add SNMP trap recipients to an Alert Policy. Cc. To add SNMP trap recipients 1 2 3 4 While creating an alert policy using the Alert Policy Wizard. But some types of alerts. the alert is listed when you select the specific server as well as the specific view from the View Pane. An alert is not generated for every master server that is a part of the group. In this case. Therefore. you select an alert condition of type of Frozen Media. select the specific recipients from the Recipient Name column and click To.

activate.Managing NetBackup using Symantec OpsCenter About managing alert policies 517 If you create this type of alert policy for a single managed server. To copy an alert policy 1 2 3 In the OpsCenter console. select Manage > Alert Policies. Select an alert policy from the Name column in the table. the alert is raised on the server since the server is the selected object. When you edit an alert policy. The copy of the alert policy is available in the alert policy details table where you can make changes to it. Click Edit. delete. The alert can also be viewed if all the nodes or views that contain the master server are selected. Select an alert policy from the Name column in the table. . You cannot select a different alert condition while editing an alert policy. To edit an alert policy 1 2 3 In the OpsCenter console. Select an alert policy from the Name column in the table. select Manage > Alert Policies. 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 Managing an alert policy Use the following procedure to edit. You can copy and use an alert policy on another managed master server. or deactivate an alert policy. select Manage > Alert Policies. copy. See “Adding an alert policy” on page 509. Click More and then click Copy from the drop-down list. The Alert Policy Wizard is used to create or edit a policy. the alert condition specific to the policy is selected by default in the Alert Policy Wizard. Click Delete. To delete an alert policy 1 2 3 In the OpsCenter console.

Select an alert policy from the Name column in the table. Using these subtabs you can view detailed information about NetBackup storage for the current View pane selection. Click More and then select View Alerts from the drop-down list. Table 8-7 lists the topics on how to manage NetBackup storage. Table 8-7 Topic Topic contents and descriptions Description See “Manage > Storage > Storage Unit view” Explains the capabilities that are available on page 519. enter the new name for the alert policy. Click More and then click Enable or Disable from the drop-down list. The copy of the alert policy is available in the alert policy details table where you can make changes to it. See “Manage > Storage > Storage Unit Group Explains the capabilities that are available view” on page 521. using the Manage > Storage > Storage Unit view. select Manage > Alert Policies. To view the alerts associated with an alert policy 1 2 3 In the OpsCenter console. To enable or disable an alert policy 1 2 3 In the OpsCenter console. using the Manage > Storage > Storage Unit Group view. About managing NetBackup storage This view is displayed when you select Manage > Storage. and Storage Lifecycle Policy. Included in this view are subtabs for Storage Unit. Select an alert policy from the Name column in the table. select Manage > Alert Policies. Viewing the alerts associated with an alert policy Use the following procedure to view the alerts that are associated with an alert policy. Click OK. See “Controlling the scope of Manage views” on page 498.518 Managing NetBackup using Symantec OpsCenter About managing NetBackup storage 4 5 In the Copy Alert Policy dialog box. . Storage Unit Group.

This column specifies the type of robot (if any) that the storage unit contains. Click the link to view details about the storage unit. This column specifies a unique. This view shows the details for a storage unit for the current View pane selection. Robot Type Robot Number Density On Demand Path Not all of the available columns appear initially in this view. logical identification number for the robotic library. . See “Manage > Storage > Storage Lifecycle Policy view” on page 522. The following columns do not appear.Managing NetBackup using Symantec OpsCenter About managing NetBackup storage 519 Table 8-7 Topic Topic contents and descriptions (continued) Description Explains the capabilities that are available using the Manage > Storage > Storage Lifecycle Policy view. The table that appears in this view shows the following columns by default: Table 8-8 Column Heading Name Manage > Storage > Storage Unit view Description This column lists the name of the storage unit. This column lists the density of the storage unit. See “Controlling the scope of Manage views” on page 498. This column specifies whether the storage unit is available exclusively on demand. There is one row in the table for each storage unit for the current selection in the View pane. Manage > Storage > Storage Unit view This view is displayed when you select Manage > Storage > Storage Unit. This happens only when a policy or schedule is explicitly configured to use this storage unit. This column specifies the absolute path to a file system or a volume available for disk backups. but can be added to your view by clicking the Table Settings icon: ■ ■ ■ Storage Unit Type Capacity Free Space .

Concurrent Jobs Staging Low Water Mark Can Exist On Root NDMP Host Enable Block Sharing Transfer Throttle Master Server Last Seen Time Host 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. . See “About using tables” on page 71. Viewing the details for a single storage unit Use the following procedure to view the details for a single storage unit. More information about how to customize tables and view specific columns is available.520 Managing NetBackup using Symantec OpsCenter About managing NetBackup storage ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ High Water Mark Max. 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 520.

The storage unit details are shown at the bottom of this view under the General tab. This view shows the details for a storage unit group for the current View pane selection. 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 521. The table that appears in this view shows the following columns by default: Table 8-9 Column Heading Name Manage > Storage > Storage Unit Group view Description This column lists the name of the storage unit group. See “Controlling the scope of Manage views” on page 498. The storage unit group details are shown at the bottom of this view under the following tabs: . This column specifies the date and time when the storage unit group was last seen. Manage > Storage > Storage Unit Group view This view is displayed when you select Manage > Storage > 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.Managing NetBackup using Symantec OpsCenter About managing NetBackup storage 521 To view details for a single storage unit 1 2 In the OpsCenter console. Click the link to view details about the storage unit group. . This column specifies the order that storage units are selected when they are included in a group. Click a storage unit name (drilldown link) from the Name column in the table. The table contains one row for each storage unit group for the current selection in the View pane. This tab displays many of the available columns of the table. select Manage > Storage > Storage Unit.

which applies to all of the storage units in the lifecycle. Any policy with a priority greater than zero has priority over the default setting. the data might be classified as gold or silver.522 Managing NetBackup using Symantec OpsCenter About managing NetBackup storage General This tab shows the details of the storage unit group that are also shown in the table. . See “Controlling the scope of Manage views” on page 498. Click the link to view more details about the master server. Storage Unit To view details for a single storage unit group 1 2 In the OpsCenter console. The table that appears in this view shows the following columns by default: Table 8-10 Column Heading Name Manage > Storage > Storage Lifecycle Policy view Description 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: . Click the name of a storage unit group (drilldown link) from the Name column in the table. Manage > Storage > Storage Lifecycle Policy view This view is displayed when you select Manage > Storage > Storage Lifecycle Policy. This column specifies the priority that a policy has for backup resources. The default for all policies is 0. select Manage > Storage > Storage Unit Group. A storage lifecycle consists of one or more storage units. Click the link to view details about the storage lifecycle Policy. For example. This column lists the data classification that has been selected for the storage lifecycle. the lowest priority possible. This column lists the master server that is associated with the storage lifecycle Policy. The table contains one row for each Storage lifecycle policy for the current selection in the View pane. This view shows the storage lifecycle policy details for the current View pane selection. This tab shows the details of the storage units that are a part of the storage unit group.

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. . a user brings a drive down while another user tries to bring up the same drive. For instance. 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. To view the details for a master server associated with a storage lifecycle Policy 1 2 In the OpsCenter console. The details are shown on a separate page. Click the name of a storage lifecycle policy (drilldown link) from the Name column in the table. select Manage > Storage > Storage Lifecycle Policy. 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 523. About managing NetBackup devices Under certain circumstances there may be issues among multiple OpsCenter users managing devices.Managing NetBackup using Symantec OpsCenter About managing NetBackup devices 523 View the details of a single storage lifecycle See “Viewing the details for a single storage policy lifecycle policy ” on page 523. Storage Destinations To view the details for a storage lifecycle policy 1 2 In the OpsCenter console. Click the name of the master server (drilldown link) from the Master Server column in the table. This tab shows the details of the storage destinations that are a part of the storage lifecycle policy. Viewing the details for a single storage lifecycle policy Use the following procedure to view the details for a single storage lifecycle Policy. select Manage > Storage > Storage Lifecycle Policy. Table 8-11 lists the topics on how to manage NetBackup devices.

See “Manage > Devices > SAN Client view” on page 532. This view shows information about all the drives and also includes disabled or unreachable drives.524 Managing NetBackup using Symantec OpsCenter About managing NetBackup devices Table 8-11 Topic Topic contents and descriptions Description Explains the capabilities that are available using the Manage > Devices > Drive view. this column contains Multiple. Click the link to view details about the drive. If the drive is configured as a shared drive (SSO). Explains the capabilities that are available using the Manage > Devices > Disk Pool view. See “Manage > Devices > FT Server view” on page 533. See “Controlling the scope of Manage views” on page 498. This view shows details for the drives that are configured for use by NetBackup for the current View pane selection. Explains the capabilities that are available using the Manage > Devices > Robot view. This column lists the name of the device host (media server) where this drive is attached. this column contains Multiple. Explains the capabilities that are available using the Manage > Devices > SAN Client view. See “Manage > Devices > Robot view” on page 528. This column lists the name of the master server that is associated with the drive. Manage > Devices > Drive view This view is displayed when you select Manage > Devices > Drive. The table that appears in this view shows the following columns by default: Table 8-12 Column Heading Drive Name Manage > Devices > Drive view Description This column lists the configured name of the drive. See “Manage > Devices > Disk Pool view” on page 530. See “Manage > Devices > Drive view” on page 524. If multiple drive paths are configured. Device Host Master Server . Explains the capabilities that are available using the Manage > Devices > FT Server view.

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 Assigned Host Control Host Name Evsn Last Clean Time Local Control . TLD.Managing NetBackup using Symantec OpsCenter About managing NetBackup devices 525 Table 8-12 Column Heading Drive Type Manage > Devices > Drive view (continued) Description This column specifies the type of drive. Not all of the available columns appear initially in this view. Enabled This column contains Yes if the path is enabled. Robot Type This column specifies the type of robot that contains this drive. The column contains No if the path is not enabled. The following columns do not appear. this column contains Multiple. Example: hcart2. 4MM. If multiple drive paths are configured. Example: TL4. hcart3.

See “Viewing the details for a master server associated with a drive” on page 527. More information about how to customize tables and view specific columns is available.526 Managing NetBackup using Symantec OpsCenter About managing NetBackup devices ■ ■ ■ ■ ■ ■ ■ ■ ■ Mounted Time NDMP Occupy Index Opr Comment Ready Request ID Scan Host VM Host Write Enabled See the online NetBackup Administration Console Help for a detailed description of these fields. To view the details for a single drive 1 2 In the OpsCenter console. View the details of a master server that is associated with a drive Use filters to view specific drives Viewing the details for a single drive Use the following procedure to view the details of a single drive. See “About using tables” on page 71. . See “Filtering on NetBackup drive category” on page 527. select Manage > Devices > Drive. The Paths tab shows the paths that were configured for the drive. Click the name of the drive (drilldown link) from the Drive Name column in the table. Detailed properties and status for the drive are shown at the bottom of the view under the General tab. The 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 526.

Select this filter to view mixed drives. For down drives. select Manage > Devices > Drive. some drive paths are up and some drive paths are down. 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 filter by using any of the built-in filters. To view the details for a master server 1 2 In the OpsCenter console. To filter details by type of drive 1 2 In the OpsCenter console. Select this filter to view all drives. For example. Select this filter to view only those drives that are down. For up drives. all drive paths are down. Select a filter from the drop-down list. .Managing NetBackup using Symantec OpsCenter About managing NetBackup devices 527 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. See “Using filters to customize your views” on page 74. all drive paths are up. Up Drives Down Drives Mixed Drives In addition to using the built-in filters. 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 this filter to view only those drives that are up. you can apply a filter that displays only those drives that are up. For mixed drives. The following built-in filters are available: All Drives All Drives is the default filter. you can also create your own custom filters. select Manage > Devices > Drive. Details for the specific master server are shown on a separate page. Click the name of the drive (drilldown link) from the Master Server column in the table.

Device Host This column lists the name of the device host where this robot is attached. 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 Remote ID . this column contains the name of the host that controls the robot. This column lists the master server that is associated with the robot. Not all of the available columns appear initially in this view. If the robot is controlled by a remote host.528 Managing NetBackup using Symantec OpsCenter About managing NetBackup devices Manage > Devices > Robot view This view is displayed when you select Manage > Devices > Robot. Click the link to view details about the robot. for example TLD(3). See “Controlling the scope of Manage views” on page 498. The following columns do not appear. Click the link to view details about the master server. Serial Number Robot Control Host Master Server Media Server This column lists the media server that is associated with the robot. This column contains the robot serial number. The table that appears in this view shows the following columns by default: Table 8-13 Column Heading Robot Name Manage > Devices > Robot view Description 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. Click the link to view details about the media server.

To view the details for a master server associated with a robot 1 2 In the OpsCenter console. Detailed properties for the robot are shown at the bottom of the view under the General tab. The Paths tab shows the paths that were configured for the robot. See “Viewing the details for a media server associated with a robot” on page 530. .Managing NetBackup using Symantec OpsCenter About managing NetBackup devices 529 ■ VM Host See the online NetBackup Administration Console Help for a detailed description of these fields. 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. 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 529. Click the name of the master server (drilldown link) from the Master Server column in the table. select Manage > Devices > Robot. See “Viewing the details for a master server associated with a robot” on page 529. More information about how to customize tables and view specific columns is available. See “About using tables” on page 71. Detailed properties for the master server are shown on a separate page. To view the details for a single robot 1 2 In the OpsCenter console. 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. select Manage > Devices > Robot. Click the name of the robot (drilldown link) from the Robot Name column in the table.

NetBackup again assigns jobs to the storage unit.530 Managing NetBackup using Symantec OpsCenter About 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.) When the capacity of the disk pool returns to the low water mark. This column lists the amount of storage space in use. This column lists the low water mark for the disk pool. Manage > Devices > Disk Pool view This view is displayed when you select Manage > Devices > Disk Pool. select Manage > Devices > Robot. The table that appears in this view shows the following columns by default: Table 8-14 Column Heading Name Server Type Manage > Devices > Disk Pool view Description This column lists the name of the disk pool This column lists the storage server type. This column lists the number of disk volumes in the disk pool. Detailed properties for the media server are shown on a separate page. This column lists the estimated amount of disk space available for storage after file metadata overhead is taken into account. (The default is 80%. the server type depends on the vendor name. Number of Volumes Used Capacity Raw Size Usable Size Low Watermark (%) . Click the name of the media server (drilldown link) from the Media Server column in the table. This view shows details for the disk pools that are configured for use by NetBackup in the current View pane selection. For OpenStorage. This column lists the total raw. unformatted size of the storage in the disk pool. To view the details for a media server associated with a robot 1 2 In the OpsCenter console. See “Controlling the scope of Manage views” on page 498.

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. Viewing the details for a disk pool Use the following procedure to view the details for a disk pool. select Manage > Devices > Disk Pool.Managing NetBackup using Symantec OpsCenter About managing NetBackup devices 531 Not all of the available columns appear initially in this view. The following columns do not appear. but can be added to your view by clicking the Table Settings icon: ■ ■ ■ ■ High Water Mark (%) Master Server State Imported See the online NetBackup Administration Console Help for a detailed description of these fields. . See “About using tables” on page 71. The details are shown at the bottom of this view. This tab shows details about the storage servers that are associated with the disk pool. Click the name of the disk pool (drilldown link) from the Name column in the table. 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 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 531. More information about how to customize tables and view specific columns is available. Click the master server link to view details about the master server that is associated with the disk pool.

The number of minutes to wait for an FT media server for a restore operation. Usage Preference No.532 Managing NetBackup using Symantec OpsCenter About managing NetBackup devices Manage > Devices > SAN Client view This view is displayed when you select Manage > Devices > SAN Client. disabled etc. View the details of a master server that is associated with a SAN client . This view shows details for the SAN clients that are configured for use by NetBackup in the current View pane selection. This column lists the state of the FT device on the SAN client. Backup Wait Period Restore Wait Period Master Server The Version column does not appear. See “Controlling the scope of Manage views” on page 498. See “Viewing the details for a master server associated with a SAN client” on page 533. 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 533. 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. of FT Media Servers This column determines when to use the FT media server. The number of minutes to wait for an FT media server for a backup operation. This column lists the master server that is associated with the SAN client. but can be added to your view by clicking the Table Settings icon. The table that appears in this view shows the following columns by default: Table 8-15 Column Heading Name State Manage > Devices > SAN Client view Description This column lists the name of the SAN client. The different states can be active.

select Manage > Devices > SAN Client. See “Controlling the scope of Manage views” on page 498. 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. 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. The table that appears in this view shows the following columns by default: . 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. FT device To view the details for a SAN client 1 2 In the OpsCenter console. Manage > Devices > FT Server view This view is displayed when you select Manage > Devices > FT Server. This view shows details for the FT media servers that are configured for use by NetBackup for the current View pane selection. The details are shown at the bottom of this view. Click the name of the SAN client (drilldown link) from the Name column in the table. select Manage > Devices > SAN Client. Click the master server link to view details about the master server that is associated with the SAN client.Managing NetBackup using Symantec OpsCenter About managing NetBackup devices 533 Viewing the details for a SAN client Use the following procedure to view the details of a SAN client. This tab shows the FT target devices information for the selected SAN client. To view the details for a master server associated with a SAN client 1 2 In the OpsCenter console.

This tab shows the FT target devices information for the selected FT server. . Click the link to view details about the robot.534 Managing NetBackup using Symantec OpsCenter About managing NetBackup devices Table 8-16 Column Heading Name Manage > Devices > FT Server view Description This column contains the name of the FT media server. FT device To view the details for an FT server 1 2 In the OpsCenter console. 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. This column specifies the number of FT connections to allow to a media server. select Manage > Devices > 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. See “Viewing the details for a master server associated with an FT server” on page 535. 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 534. 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. State Master Server This column lists the state of the FT media server. This column lists the master server that is associated with the FT server.

You can disable audit logging by clearing this check box. To view the details for a master server associated with an FT server 1 2 In the OpsCenter console. This view displays detailed information for OpsCenter audit reports. the retention period is set to 90 days. 5 . You must have Admin privileges to configure the audit settings. the Enable audit trail logging with NetBackup Environment check box appears as selected. Click Save to save the settings. select the required master server and click Edit Audit Settings. To enable the Audit trail logging 1 2 3 Log on to OpsCenter server host with administrator privileges. select Manage > Devices > FT Server. Note: If audit logging is initiated in NetBackup. Click Manage and click Hosts. About managing NetBackup Hosts This view is displayed when you select Manage>Hosts. From the Master Server tab. enter the value in the Retain audit logs for days text box. To retain logs for a specific period of time. Select the Enable audit trail logging with NetBackup Environment check box to enable the audit logging process. select the Always retain all audit trail logs option to retain the logs forever.Managing NetBackup using Symantec OpsCenter About managing NetBackup Hosts 535 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. Managing Audit Trails settings You can manage the settings to enable the auditing for the selected master server through OpsCenter. Detailed properties for the master server are shown on a separate page. for the current Master server selection. 4 Under Retention period. Click the name of the master server (drilldown link) from the Master Server column in the table. By default.

The report gives capacity totals for each client. and RealTime. PureDisk. A log file is also created. The report displays the amount of data with the licensed amount for the Capacity Totals for Enterprise Disk. This view gives detailed information about the OpsCenter Capacity Licensing report for all or selected master servers. PureDisk. The report displays totals on the basis of the number of policies and subtotals for each capacity tier.536 Managing NetBackup using Symantec OpsCenter About managing NetBackup Deployment Analysis About managing NetBackup Deployment Analysis This view is displayed when you select Manage > Deployment Analysis. The report is classified by the options Enterprise Disk. The report displays details such as number of policies per client and their name and the total kilobytes backed up. The report contains information about capacity totals backed up for each client. . which gives information about how the totals are calculated. thus making it easier to verify capacity totals for each client. About Capacity License report A Capacity Licensing report gives a summary of the amount of data that is protected. The report is generated in the form of an Excel sheet. and RealTime. You can thus ensure that the data that is backed up is within the permitted license amount. The report also gives information about the terabytes stored on: ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ BasicDisk Physical Tape OpenStorage Visual Tape Library Flexible Disk Enterprise Disk Subtotal NDMP NASSnapVault PureDisk RealTime Using the details of the Capacity Licensing report you can compare the actual amount of data that is backed up with the licensed amount.

Select the required master server and click Edit. The NetBackup Deployment Analyzer examines the image headers in the NetBackup catalog to determine the amount of data that NetBackup protects. The Settings tab helps you to enable them. The analyzer uses the size of the last full backup for the last 30 days. The data can either be on the clients or the devices where the software is installed. The Deployment Analyzer calculates the total data that needs to be protected. The data can also be on the software that is used to provide the backup functionality. The analyzer sums all backups that started within that period. To generate the Capacity Licensing report 1 To generate the Capacity Licensing report it is mandatory to enable License Deployment data collection and to configure an agent.Managing NetBackup using Symantec OpsCenter About managing NetBackup Deployment Analysis 537 Compiling data for the report Capacity Licensing is a way of determining the total terabytes of data NetBackup protects. Generating a Capacity Licensing report The Capacity Licensing report is generated in the form of an Excel sheet. The final total is the sum of terabytes for each client and policy combination that the analyzer examines. 2 . the analyzer considers the day with the largest total volume of protected data as an estimate of the approximate size of active data under protection for the client and policy. A day is defined as the 24 hour period from midnight to midnight. For some policy types. Determining the capacity licensing The bpimagelist command is used to obtain image and fragment information for all backups for the past 30 days. The data is measured in terabytes. The Edit Master Server page is displayed. This report can be emailed or exported in the XLS format to the required email address or location. Select Settings > Configuration > NetBackup.

Select the Enable License Deployment Data Collection check box as shown in the following figure.538 Managing NetBackup using Symantec OpsCenter About managing NetBackup Deployment Analysis 3 Select the Configure agent link to configure an agent. .

See “About the Capacity Licensing page” on page 541. You can view the previously generated report with the available link under the Last Successful Report Date header. The Capacity Licensing page is displayed as shown in the following figure. The Create Capacity Licensing Report page is displayed.Managing NetBackup using Symantec OpsCenter About managing NetBackup Deployment Analysis 539 4 In the OpsCenter console. log file. 5 Click New Report to generate a new report. . A log file is generated when the Capacity License report is generated. The Capacity Licensing page contains details about the previously created report. You can view the log file with the View Log link. and data collection. click Manage > Deployment Analysis.

The Subject field displays the default text Capacity Licensing Report. 9 . Enter a message in the Message field. Enter the recipients email address in the To and CC fields. Select the required master servers from the list. The Report Options page is displayed. the following image displays both the options.540 Managing NetBackup using Symantec OpsCenter About managing NetBackup Deployment Analysis 6 Select the Collect data and run report on all Master Servers option to generate a report for all the master servers. 7 8 Click Next. Select the Collect data and run report on specific Master Servers option to generate a report for only the required master servers. you can change the subject line if required.

If the report generation fails. select the Export report (XLS format) check box. this column shows a blank. 11 Select Run Report to initiate the data collection. You can change the export location path from the Settings > Configuration > Report Export Location tab. ■ ■ ■ .xls file or save the file for later viewing. When report generation is complete.Managing NetBackup using Symantec OpsCenter About managing NetBackup Deployment Analysis 541 10 To export the report to the required location. About the Capacity Licensing page The Capacity Licensing page contains information about the Capacity License report and the data collection status. An example exception detail message can be. The status shows as Failed when the report is not generated. The log file is very useful in analyzing the Capacity Licensing report. this column shows a blank. The headers are: ■ Last Successful Report Date: Displays a link to the previously generated report. The report section contains details about the report in the form of a table. The link itself contains information about the date and time of the last successful report. Note: Re-running the report when report generation is in progress is not possible as it displays errors in thne report. It is advisable to wait till the report is generated.Data collection failed for selected master servers. Status: Displays the report status as the name suggests. you can open the . If the report generation is successful. Last Successful Report Log: Displays a link to the log file that is generated when the report is generated. See “Setting report export location in OpsCenter” on page 318. A message to show that report generation has started is flashed. Exceptions: Displays the reasons for the report generation failure.

Prerequisites can be. The column shows a blank when data collection fails. The last successful backup report is located at SERVER_INSTALL_DIR/fsdb/fetb/backup. Exceptions: Displays the reason for data collection failure. The output of bpimagelist for each server is located at SERVER_INSTALL_DIR/fsdb/fetb/data. Data Collection Status: Displays the status of data collection. If you select the Collect data and run report on specific Master Serversoption. or data status collection is not enabled for a master server. Last Licensing Data Collection Date: Displays the date and time when the last licensing data is collected.SERVER_INSTALL_DIR/fsdb/fetb/log. an agent not configured.542 Managing NetBackup using Symantec OpsCenter About managing NetBackup Deployment Analysis The Capacity Licensing page also contains details about data collection in the form of a table. ■ ■ ■ ■ Final location of the reports and logs The reports and log files are located at the following locations: ■ ■ ■ The final report is located at . ■ . An example is OpsCenter Agent is not connected. then the columnn displays only those master servers that you select. Click the link to know the details about the prerequisites that need to be completed. The log file is located at . The headers are: ■ Master Server: Displays the list of master servers for which the report is generated. Prerequisites Status: Displays a link when the prerequisites have not been completed.SERVER_INSTALL_DIR/fsdb/fetb/report.

Capacity License report issues. You can also initialize the agent explicitly by first disabling the master server and then enabling it.Managing NetBackup using Symantec OpsCenter About managing NetBackup Deployment Analysis 543 About possible Capacity License report issues The Capacity Licensing report requires a user to enable master servers and configure agents to generate the correct report. Table 8-17 Error and cause Agent is in disconnected state Agent is not connected as it could be down or there could be a network issue. server and then enabling it. If the agent is down OpsCenter will try to automatically connect to the agent after every 10 minutes. If the agent is disconnected. the report is not generated and shows errors. You can also initialize the agent explicitly by first disabling the master server and then enabling it. If the agent is not connected OpsCenter will try to automatically connect to the agent after every 10 minutes. Server side exception unknown oid Confirm that the agent is connected. Table 8-17 describes the possible Capacity License report issues and their solution. Make sure that the you have network connectivity. Confirm that the master server is connected. causes. Master server not connected or it might be disabled Master server is not connected or disabled Agent is not connected Agent is not connected as it could be down or there could be a network issue. Retries exceeded cannot connect on opscenter_agent Connection to the Agent service is lost Confirm that the agent is connected. You can also initialize the agent explicitly by first disabling the master server and then enabling it. . wait for 10 minutes This error is displayed when the agent gets for it to reconnect. You can also initialize the agent explicitly by first disabling the master server and then enabling it. wait for 10 minutes for it to reconnect. When the master server is not enabled or when the agents are not configured. If the agent is disconnected. Another cause of errors whena report is not generated is the network connectivity issue. and solution Solution If the agent is down OpsCenter will try to automatically connect to the agent after every 10 minutes. Failed to initialize agent Agent is not connected or there could be a network issue. You can also initialize the disconnected while data collection is in agent explicitly by first disabling the master progress.

544 Managing NetBackup using Symantec OpsCenter About managing NetBackup Deployment Analysis .

Chapter 9 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. making the operation easier to perform. .

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 ■ On Windows systems. ■ Set up all destination file paths before you run the cloning operation. You do not need access to the original database to perform the cloning operation.txt): ORACLE_METADATA=YES Then send this newly created configuration file to the client host by using the following bpsetconfig command on the master or media server: # bpsetconfig -h myoracleclient new_config. Metadata cataloging must occur during the backup from the Oracle database to be cloned. new_config. Ensure that the user has write access to these paths. Do the following before you perform a Guided Recovery cloning operation: ■ On UNIX and Linux systems. first place the following text into a text file (for example. ensure that the Oracle metadata parameter in the client's bp. which enables database information to display in OpsCenter.546 Guided Recovery Setting up for cloning ■ OpsCenter retrieves information for you such as databases and control files. ■ ■ Setting up for cloning Oracle uses metadata cataloging.txt bpsetconfig is located in the install_path\NetBackup\bin\admincmd directory. because the operation does not create new file paths during the process. . A validation process increases the rate of successfully completing the cloning operation. shortening the Oracle clone setup time. The collected metadata displays within the OpsCenter interface to guide the clone operation to enable metadata collection on the client host.

To perform a cloning operation on an Oracle database in OpsCenter 1 2 When you log onto OpsCenter. run the Oracle service under the Oracle user account. Otherwise. use the drop-down menu to select the master server that you want to work with. See “Select Master Server screen” on page 549. On Windows systems. The cloning operation does not support Oracle Automatic Storage Management (ASM). Add the 'BKUP_IMAGE_PERM=ANY' to the send commands during the backup of the source database. To use a different user or a different group for the clone. an error indicating the database cannot be mounted in exclusive mode appears. then click Go. perform an alternate restore procedure. On Oracle 10G systems and later. shut down the source database to successfully complete the operation. the user must have write access to some directories such as DBS. On the Select Master Server screen. The cloning operation does not support offline tablespaces or raw tablespaces. By default. On UNIX and Linux systems. On Windows systems. Along the top of the screen. the first screen that appears is the Monitor Overview screen. ■ ■ ■ ■ ■ ■ ■ ■ Performing a cloning operation You need to log onto OpsCenter. click Manage > Oracle Cloning. . if the NetBackup client service runs as the Oracle user.Guided Recovery Pre-operation checks 547 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. you must change what the permissions of the backup image are to be at backup time. to perform a cloning operation. OpsCenter is the Web GUI that you use to perform all guided recovery operations. if you are cloning to the same system. Examples are Solaris 9 to Solaris 10 and Oracle 11 to Oracle 11. it runs under the local system. you can run under the local system. if the cloning user shares an existing Oracle home. If the destination client is different than the source client. then that user needs to be granted the right to "Replace a process level token". On Oracle 9 for Windows.

the destination paths of control files. Enter the destination host name in the text box that is provided or click Browse and select from a list of available hosts. Note the following prerequisites concerning the destination host: ■ ■ ■ The platform type of the source and destination must be the same. and redo logs. and restore options. The default is the latest backup selected. For operating system authentication. After you have changed the destination parameters. The lower left corner of the screen lists three links. See “Destination host and login screen” on page 550. and domain (Windows). click Next>. . The Select Control File Backup screen shows a timeline view of the control file backups. Then click Next>. A NetBackup client must be installed. A compatible version of Oracle must be installed. The five tabs on this screen are used to change database attributes. and date.548 Guided Recovery Performing a cloning operation 3 The Select Source Database screen lets you filter the list of databases by database name. 5 6 The Destination Host and Login screen contains parameters for the destination of the clone to be created. Select the icon for the desired control file backup from the timeline view. Click on the icon of the control file backup you want to restore for the clone of the selected database. Click Show Databases. More information is available about these links. 4 The databases appear under the filtering part of the same screen. The default condition is to display all databases that are backed up in the default date range. See “Select Control File Backup screen” on page 549. data files. You can hover over the icon to display the control file details. Then click Next>. Then click Next>. See “Select Source Database screen” on page 549. Additional information is available to verify that you have selected the correct control file. See “Destination Parameters screen” on page 551. password (Windows). platform. 7 The Define Destination Parameters screen appears. you can hover over the icon to display all versions of the backup for that time periods. database version. host name. enter a user name. If the icon represents multiple backups. More information is available on this screen. Select the database on which you want to perform a cloning operation by clicking option at the left side of the desired database entry.

If a directory path does not already exist. 9 The Pre-clone Check screen lets you validate the database attributes and the file paths. select the NetBackup master server that collected the backup information to be used for the cloning operation. 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. See “Selection summary screen” on page 552. host name. click the underlined word here. When you are ready to launch the cloning operation. click Next>. select Solaris from the Platform: pulldown menu. the validation check flags the error. Select Control File Backup screen The Select Control File Backup screen is a timeline view of all the control files that are backed up for the selected database. The timeline displays an icon for each control file that is associated with the backed up database. The upper portion of the screen shows parameters for filtering the list of databases. Links to the recovery sets and destination database attributes let you view and verify any changes you have made. to show only the Solaris databases that are backed up between 11/05/2009 and 11/12/2009. the validation check also flags the error. database version.Guided Recovery Select Master Server screen 549 8 The SelectionSummary screen lets you scan the information you have entered on the previous screens. Then click Show Databases to display the new filtered list of databases. so that the cloning operation does not overwrite the file. Multiple filter parameters can be used at the same time. Select Source Database screen When the Select Source Database screen first appears. If the list is long. you can filter what databases appear by database name. Select Master Server screen From the pulldown menu. the latest backup control file is already selected . . When you first enter this screen. To validate. For example. and date range. A display appears that is similar to the NetBackup Activity Monitor. If a file already exists. Then select the dates from the calendar icons. When you are satisfied with the summary information. See “Pre-clone check screen” on page 552. click Launch Cloning Process.

If multiple control files were backed up during a single timeline unit. a different icon appears representing more than one control file (for example. hover over the icon. etc. To select from among these files.550 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. To view all the instances of control files. and password. It shows several items including the backup name and the type of media. you are asked only for the user name. View Datafiles Recovery Set shows the data file backups to be used for the restore process. It also shows the backup and image information that is displayed for each data file. ■ ■ Destination host and login screen The Select Destination Parameters screen lets you enter the destination host and the Oracle logon information. Click option next to the desired control file. only the first media is shown in the list. weeks. Multiple control files may be displayed on the timeline. ■ View Database Schema shows the schema of the selected control file. A popup lists each control file in table format. For UNIX and Linux. You can display the timeline in days. the clone still completes successfully. A compatible version of Oracle must be installed. and its size. the clone still completes successfully. 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. 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. For Windows. If the image spans media. tablespace name. if the database was backed up twice in an hour). . you are asked for the domain name. 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. the size of the backup. Even though files that are backed up as part of a full backup do not appear in this list. type of media. The data file recovery set is generated only for the files that are backed up as part of an incremental strategy. you may need to increase the scope of the timeline. It shows how the database is laid out by listing each data file name. A NetBackup client must be installed. or years. Even though files that are backed up as part of a full backup do not appear in this list. This set is generated only for the files that are backed up as part of an incremental strategy. months. user name.

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

if the cloning operation fails. On UNIX and Linux systems. To validate. The database recovery set and the archived log recovery set. do the following cleanup: ■ ■ ■ If the database is active. from the <$ORACLE_HOME>/DBS directory. You can also specify an email address. If a file already exists. .ora. Job Details screen The Job Details screen is intended to reflect the NetBackup Activity Monitor. ■ ■ Pre-clone check screen The Pre-clone Check screen lets you validate the database attributes and the file paths. click the underlined word here. See the NetBackup Administrator's Guide. and any other files associated with the SID being used. update the oratab file with the appropriate instance information. If a file path does not already exist.552 Guided Recovery Selection summary screen Selection summary screen The following information appears on this screen: ■ ■ The selected master server and the source database attributes. the validation check flags the error. so when the cloning process completes. so that the cloning operation does not overwrite the file. the validation check also flags the error. The destination database attributes selected in the previous screen and the database initialization parameters to be used for the cloning operation. an email is sent to you that gives you the status of the cloning operation along with other pertinent information. Remove init<SID>. More information is available on the Activity Monitor. spfile<SID>.ora. The date and time of the selected control file backup. Post-clone operations Perform the following after the cloning operation has completed: ■ On UNIX and Linux systems. and the backup media type. shut down the database. Volume I.

you must make them read-write before RMAN backs them up. 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. New Client Framework Oracle Plugin ■ ■ ■ . You may revert to read-only if you want. ■ ■ Troubleshooting Guided Recovery Guided Recovery operations are in addition to the normal NetBackup for Oracle operations. and Database=5. On Windows systems. OID 360. or RMAN cannot restore them. New Client Framework ncforautil unified logs.Guided Recovery Troubleshooting Guided Recovery 553 ■ ■ Remove all data files. All unified logs should be gathered at DebugLevel=6 and DiagnosticlLevel=6. On Windows systems. On UNIX and Linux systems. dbca sometimes removes directories. If a cloned Oracle database contains read-only tablespaces or datafiles. if the cloning operation fails. all previously used troubleshooting steps and evidence are also relevant. The following shows an example of the sequence of steps in the process: ■ ■ ■ ■ Back up Oracle database A which contains read-only tablespace TABLE1. gather them at General=2.) ncf unified logs. OID 348. use the dbca utility to delete the database. Back up database B. After the backup (cloning operation). Use RMAN to restore database B. If problems are encountered. The following sections detail the additional key information that is required to troubleshoot Guided Recovery when it fails. OID 309. you can return the items to read-only. gather all legacy logs at VERBOSE=5. Clone database A to database B. so verify before retrying the operation. Use the Oracle alter tablespace command to make tablespace TABLE1 read-write. Verbose=5. New Client Framework Oracle Utility ncforaclepi.

OID 363.) netbackup/logs/bpdbsbora legacy logs ■ . OID 309. NetBackup Agent Request Service dars unified logs. NetBackup Agent Request Service dars unified logs. OID 363. OID 362. Database Agent Request Service From the Symantec OpsCenter server: ■ ■ <SYMCOpsCenterServer>/config/log. OID 366.554 Guided Recovery Troubleshooting Guided Recovery From the NetBackup media server: netbackup/logs/bpbrm legacy logs From the NetBackup master server: ■ ■ ■ netbackup/logs/bprd legacy logs nbars unified logs. 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. OID 148 (The default location is <SYMCOpsCenterServer >/logs) opscentergui unified log. OID 362.conf file opscenterserver unified logs. NetBackup Agent Request Service dars unified logs. New Client Framework ncfnbcs unified logs. New Client Framework NetBackup Client Services From the NetBackup master server: ■ ■ ■ netbackup/logs/vnetd legacy logs nbars unified logs. OID 363. Database Agent Request Service From the NetBackup master server: ■ ■ ■ netbackup/logs/bprd legacy logs nbars unified logs. Database Agent Request Service Troubleshooting files for Guided Recovery validation operations From the Oracle client host: ■ ■ ■ netbackup/logs/vnetd legacy logs ncf unified logs. OID 362.

conf file opscenterserver unified logs. OID 362. OID 363. OID 148 (The default location is <SYMCOpsCenterServer >/logs) opscentergui unified log. OID 147 (The default location is <SYMCOpsCenterGUI>/logs) ■ . Database Agent Request Service From the Symantec OpsCenter server: ■ ■ <SYMCOpsCenterServer>/config/log.) 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.Guided Recovery Troubleshooting Guided Recovery 555 ■ netbackup/logs/dbclient legacy logs (The directory must be writable by the Oracle users. NetBackup Agent Request Service dars unified logs.

556 Guided Recovery Troubleshooting Guided Recovery .

See “Configuring the SNMP version for sending SNMP traps” on page 575. See “ SNMP versions supported in OpsCenter” on page 559. See “About SNMP versions” on page 558. See “About the Management Information Base (MIB) and OpsCenter support” on page 559.50/7.Chapter 10 Understanding and configuring OpsCenter alerts This chapter includes the following topics: ■ ■ About using SNMP with OpsCenter About managing OpsCenter alerts using Microsoft System Center Operations Manager 2007 About managing OpsCenter alerts using HP OpenView Network Node Manager 7. . See “Configuring the SNMP trap community name for OpsCenter” on page 574. See “Alert configuration settings in OpsCenter” on page 576. See “Frequently asked SNMP and OpsCenter questions” on page 577.51 on Windows ■ About using SNMP with OpsCenter This section provides information about SNMP and how OpsCenter uses SNMP. See “About SNMP” on page 558.

a database of management information. The key enhancements to SNMPv2 are focused on the SMI. SNMPv2c combines the Community-based approach of SNMPv1 with the protocol operation of SNMPv2 and omits all SNMPv2 security features. This document replaces the earlier versions that were published as RFC 1067 and RFC 1098. This model consists of a manager. ■ ■ ■ ■ ■ The original SNMPv2 (SNMPv2p) Community-based SNMPv2 (SNMPv2c) User-based SNMPv2 (SNMPv2u) SNMPv2 star (SNMPv2*). Security is based on community strings. and plan for network growth. The manager provides the interface between the human network manager and the management system. SNMPv2 It was created as an update of SNMPv1 adding several features. and the network protocol. SNMP enables network administrators to manage network performance. The MIB is organized in a tree structure with individual variables. The agent provides the interface between the manager and the physical devices being managed. find and solve network problems. A numeric tag or object identifier (OID) is used to distinguish each variable uniquely in the MIB and in SNMP messages. About SNMP versions Many versions of SNMP are available. being represented as leaves on the branches. It is part of the Transmission Control Protocol/Internet Protocol (TCP/IP) protocol suite. The versions of SNMP protocol are as follows: ■ SNMPv1 The SNMPv1 version is the first version of the protocol and is defined by RFC 1157.558 Understanding and configuring OpsCenter alerts About using SNMP with OpsCenter About SNMP The Simple Network Management Protocol (SNMP) is an application layer protocol that facilitates the exchange of management information between network devices. The manager and agent use a Management Information Base (MIB) and a relatively small set of commands to exchange information. SNMP is based on the manager model and agent model. an agent. ■ SNMPv3 . and protocol operations. manager-to-manager capability. managed objects. such as point status or description.

Table 10-1 shows the name-value pairs that the traps pass to the SNMP manager. See “Alert descriptions in OpsCenter” on page 562. RFC 1905. RFC 2262. and support for proxies.1. See “SNMP traps” on page 559. Each OID consists of the numbers that are separated by decimal points (for example. 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 associates each OID with a readable label and various other parameters that are related to the object. and RFC 2265 define this protocol. Each binding associates a particular Management Information Base (MIB) object instance with its current value.6. . RFC 2261. Each OpsCenter trap contains 2 standard object identifiers and 12 OpsCenter-specific object identifiers.1).3.2682. Each object and characteristic has a unique object identifier (OID) that is associated with it.4. The MIB then serves as a data dictionary that is used to assemble and interpret SNMP messages.1. These OIDs form a tree. The security is based on that found in SNMPv2u and SNMPv2*. SNMP traps This section explains the content of an SNMP trap that is sent from Symantec OpsCenter. 1. A total of 14 bindings (or 14 name-value pairs) are present in each trap that is sent from OpsCenter. An object identifier (or OID) is a numeric string that is used to uniquely identify an object. RFC 2264. RFC 1906. The following table shows the contents of a trap that is sent from OpsCenter. RFC 2263.Understanding and configuring OpsCenter alerts About using SNMP with OpsCenter 559 This version of the protocol is a combination of user-based security and the protocol operations and data types from SNMPv2p.

ccTrapDefinitionsBranch.3 (iso.6. See Request for Comment (RFC) 1905 and 2576 for a detailed definition.1.ietf.veritascc. alert status.txt http://www.3.12.org/rfc/rfc2576. http://www.4.3.ietf.1.private. and alert summary in the (iso.1.private.org.3.txt Example: 1.p following format: roducts. .1.internet.3. See RFC 1905 and RFC 2576 for a detailed definition.3.veritascc.10.ccTrapDefinitionsBranc Alert ID (Alert Status) Alert Summary h.2.ccTrapVarsBran ch.3.12.dod.10.4.12.dod.1.1.3.2.ccTrapVarsBran ch.1302.1.alertDescription) This field is the alert description.6.6.6.org.12. http://www.10.4.0 This field is the unique identifier for this trap.txt http://www.3.ietf.org/rfc/rfc2576.6.internet.1.560 Understanding and configuring OpsCenter alerts About using SNMP with OpsCenter Table 10-1 Name 1.private.alertRecipients) 1.org/rfc/rfc1905.1302.p Example: Nancy Nieters roducts.1.org/rfc/rfc1905.1.4.1.1302.6. See “Alert descriptions in OpsCenter” on page 562.10.0.enterprises.3.1302.1.org.2 This value specifies the alert ID.3.3.p roducts.3.1. ccTrapDefinitionsBranch.ietf. (iso.txt Example: 1173792454 1.1.alertSummary) Example: 100 (Active) Job Completed with Exit Status 0 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.4 1.veritascc.4.1.enterprises. Examples for each alert condition are available.enterprises.1.ccTrapVarsBranch.1.dod.1.1 This field is the alert recipient name.6.internet.

enterprises.v eritas.v eritas.1.ccTrapVarsBranch.v eritas.dod.veritascc.4.12.products.4 (iso.6.policyName) 1.products. .10 (iso.ccTrapVarsBranch.1302.3.1302. 1.veritascc.10.products.3.ccTrapDefinition sBranch.ccTrapVarsBranch.collectorNam e) 1.1. (iso.internet.1302.internet.1.dod.enterprises.internet.ccTrapDefinition sBranch.v eritas.3.veritascc.3.12.enterprises.9 (iso.ccTrapDefinition sBranch.products.ccTrapVarsBranch.ccTrapVarsBranch.private.org.private.3.10.v eritas.products.3.org.internet.1.12.1.ccObject) 1.10.ccTrapDefinition Example: 10.6.enterprises.org.1.p roducts.private.12.8 (iso.dod.veritascc.4.6.3.10.4.1.dod.enterprises.1302.6.ccTrapDefinition sBranch.org.ccTrapVarsBran ch.5 (iso.1.1.1302.ccTrapDefinition sBranch.ccHost) 1.ccTrapVarsBranch.4.12.212.sourceId) 1.1.1.dod.org.10.3.products.org.1.1.3.veritascc.internet.internet.veritascc.3. This field is blank and not used.12.3.veritascc.1.private.enterprises.1.1.7 This field is blank and not used. ccTrapDefinitionsBranch.1302.10.1.10.1.6.1.6.private.3.objectType) 1.4.148 sBranch.6.12.1302.4. This field is blank and not used.Understanding and configuring OpsCenter alerts About using SNMP with OpsCenter 561 Table 10-1 Name OpsCenter trap binding (continued) Value This field is blank and not used.internet.dod.12.dod.v eritas.sampleData) This field is the IP address of the OpsCenter server.4.3.enterprises.3. This field is blank and not used.org.private.private.1. This field is blank and not used.6 (iso.1.

12.3.6.private.internet.1 to 1.1.1302.12.6.internet.1.10.1.dod.3.products.1.1.3. The first two OIDs listed in the table are standard SNMP OIDs. However.3 represents iso.1.1302.ccTrapVarsBranch.10.1302.1.veritascc.10.6.4.private.org.10.4.10.veritascc.3.3.1.v eritas.12.1.private.1. Table 10-2 shows the content that each OpsCenter alert sends as OID 1.3.1.4.3.12 (iso.3.ccTrapVarsBranch. the two standard SNMP OIDs must be present as part of every trap.internet.6. Most of the alert information in OpsCenter is sent as OID 1. Alert descriptions in OpsCenter This section shows the content that is sent for each OpsCenter alert as OID 1.enterprises.10.enterprises.4.3. Note: 1.1.1302.11 (iso.1302. As per SNMPv2c trap definition.ccAlertSeveri ty) 1.dod.1.1. the two standard OIDs are not defined in the OpsCenter MIB files.ccTrapDefinition Example: 13-10-2008 06:57:34 00 sBranch. .org.org.3.1.12. ccTrapDefinitionsBranch. All the 12 OpsCenter OIDs are defined in the OpsCenter MIB files.4.1.alertDescription.veritascc.6.4.12. 1.v eritas.3.ccTrapDefinition Example: Informational sBranch.12.12 are OpsCenter OIDs.1.ccAlertTime) This field shows the time when the alert gets cleared.3.3. The other OIDs starting from 1.1.1302.12.4.3.3.1.ccTrapVarsBranch.1.4.10.6.1.1.12.1.1302.products.1302.3.dod.3.products.10.6.enterprises.562 Understanding and configuring OpsCenter alerts About using SNMP with OpsCenter Table 10-1 Name OpsCenter trap binding (continued) Value This field shows the alert severity level.6.1.3.3.

2009 2:21 PM Job: 25888 Tree Type : Policy Nodes : ccs-win-qe-5 Job Policy: ccsqasol1 Client: ccs-win-qe-5 Alert Policy: Hung Job OpsCenter Server: ccs-sol-qe-17 Severity: Warning Job finalized Alert Raised on: September 9. 2009 4:54 PM Job: 26356 Tree Type : Policy Nodes : node1 Job Policy: sample_policy Exit Status: 150 (termination requested by administrator) Client: ccs-win-qe-5 New State: Done Alert Policy: Job Finalized OpsCenter Server: ccs-sol-qe-11 Severity: Warning Incomplete Job .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 5:00 PM Tree Type : Policy Nodes : Root Node % Failed Jobs: 100.Understanding and configuring OpsCenter alerts About using SNMP with OpsCenter 563 Table 10-2 Alert type Job Alert conditions in OpsCenter Alert condition High job failure rate Description (Example) Alert Raised on: September 5.

2009 4:54 PM Job: 26356 Tree Type : Policy Nodes : node1 Job Policy: sample_policy Client: ccs-win-qe-5 Alert Policy: Incomplete Job OpsCenter Server: ccs-sol-qe-11 Severity: Warning .564 Understanding and configuring OpsCenter alerts About using SNMP with OpsCenter Table 10-2 Alert type Alert conditions in OpsCenter (continued) Alert condition Description (Example) Alert Raised on: September 9.

Understanding and configuring OpsCenter alerts About using SNMP with OpsCenter 565 Table 10-2 Alert type Media Alert conditions in OpsCenter (continued) Alert condition Frozen media Description (Example) Alert Raised on: August 17. 2009 3:36 PM Suspended Media Name: 0122L2 Tree Type : Server Nodes: node1 Media server : ccs-win-qe-13 Alert Policy: Suspended media policy OpsCenter Server: localhost Severity: Informational Exceeded max media mounts Alert Raised on: August 12. 2009 3:27 PM Media Name: A00009 Tree Type : Server 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 12:24 PM Tree Type : Server Nodes: node1 Frozen Media Name: A00004 Media server : ranjan Alert Policy: frozen media policy OpsCenter Server: localhost Severity: Warning Suspended media Alert Raised on: August 12.

2008 4:39 PM Tree Type : Server Nodes: node1 Media: 000_00000_TL4 Required for restore Master server: omwin12(omwin12) Client: omwin12 Media server: macy Restore Job ID: 615 Alert Policy: Media Required for Restore_root OpsCenter Server: ccs-sol-qe-10 Severity: Warning Low available media Alert Raised on: August 12.0 Alert Policy: high percentage suspended media OpsCenter Server: localhost Severity: Warning High frozen media . 2009 11:54 AM Tree Type: Server Nodes: node1 Available Media: 4 Alert Policy: low available media OpsCenter Server: localhost Severity: Warning High suspended media Alert Raised on: August 12. 2009 11:40 AM Tree Type : Server Nodes: node1 Suspended Media: 1 % Suspended Media: 25.566 Understanding and configuring OpsCenter 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.

Understanding and configuring OpsCenter alerts About using SNMP with OpsCenter 567 Table 10-2 Alert type Alert conditions in OpsCenter (continued) Alert condition Description (Example) Alert Raised on: December 8. 2008 10:24 AM Tree Type : Server Nodes: node1 Frozen media: 6 % Frozen Media: 66 Alert Policy: highfrozenmedia OpsCenter Server: winfor11 Severity: Warning .

2008 10:08 AM Master server : sargam(sargam) Tree Type : Server Nodes: node1 Available Catalog Space: 6480880 KB Threshold Catalog Space: 102400 TB Alert Policy: test_catalogspacelow OpsCenter Server: winfor11 Severity: Warning Catalog not Backed up Alert Raised on: September 7. 2009 5:21 PM Alert Policy: Catalog not Backed up OpsCenter Server: ccs-sol-qe-17 Severity: Warning Catalog Backup Disabled Alert Raised on: September 5. 2009 9:54 AM Tree Type : Server Nodes : ccs-sol-qe-13 Threshold: 10 Minute(s) Last Catalog BackUp Time: September 6. 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 .568 Understanding and configuring OpsCenter 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.

Volume Group: 000_00000_TLD Request Time: February 4.Understanding and configuring OpsCenter alerts About using SNMP with OpsCenter 569 Table 10-2 Alert type Tape Alert conditions in OpsCenter (continued) Alert condition Mount Request Description (Example) Alert Raised on: September 7. 2009 6:52 PM Tree Type : Server Nodes : ccs-win-qe-1 Barcode: 000014 Density: dlt evsn: 000014 Mode: 82 Request ID: 120 rvsn: 000014 User: . 1991 12:56 AM Alert Policy: Mount Request OpsCenter Server: ccs-sol-qe-12 Severity: Warning No Cleaning Tape Alert Raised on: August 17. 2009 12:30 PM Tree Type : Server Nodes : ccs-win-qe-1 Media server : ranjan Robot Number: 0 Alert Policy: no cleaning tape left OpsCenter Server: localhost Severity: Warning Zero Cleaning Left .

2008 12:02 PM Tree Type : Server Nodes : ccs-win-qe-1 Master server : ORLP-SPEECH01 Media server : ORLP-SPEECH01 Robot Number: 0 Cleaning Tape: CLN084 Alert Policy: test_zerocleaningleft_public OpsCenter Server: winfor11 Severity: Warning .570 Understanding and configuring OpsCenter alerts About using SNMP with OpsCenter Table 10-2 Alert type Alert conditions in OpsCenter (continued) Alert condition Description (Example) Alert Raised on: December 13.

2009 5:08 PM Tree Type : Server Nodes : ccs-win-qe-1 Disk Volume ID: /vol/luns/nbusd_sun10 Disk Pool ID: SSOD_Pool Alert Policy: disk volume down pol OpsCenter Server: localhost Severity: Informational Low Disk Volume Capacity Alert Raised on: August 26. 2009 10:35 AM Tree Type : Server Nodes : ccs-win-qe-1 Disk Volume Free Capacity: 106 MB Threshold: 20 % OpsCenter Server: localhost Severity: Major Drive is Down . 2009 5:25 PM Tree Type : Server Nodes : ccs-win-qe-1 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.Understanding and configuring OpsCenter alerts About using SNMP with OpsCenter 571 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 3:13 PM Tree Type : Server Nodes : ccs-win-qe-1 Drive Number: 1 % Down Drive Paths: 100.0 Alert Policy: high down drives OpsCenter Server: localhost Severity: Major .572 Understanding and configuring OpsCenter alerts About using SNMP with OpsCenter Table 10-2 Alert type Alert conditions in OpsCenter (continued) Alert condition Description (Example) Alert Raised on: August 12.000 Drive Number: 1 Robot Number: 0 Alert Policy: drive down-individual alert Device Path: /dev/nst0 OpsCenter Server: localhost Severity: Critical High Down Drives Alert Raised on: August 12. 2009 10:39 AM Tree Type : Server Nodes : ccs-win-qe-1 Media server : omlinux2 Drive Name: BNCHMARK.

2009 12:20 AM Alert Policy: MasterServer Unreachable OpsCenter Server: CCSQAWINSP1 Severity: Major Lost Contact with Media Server Alert Raised on: February 18.Understanding and configuring OpsCenter alerts About using SNMP with OpsCenter 573 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. 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 . 2008 1:33 PM Master server : pmsun22 Media server : pmsun22 Alert Policy: lcm OpsCenter Server: pmwin9 Severity: Warning Service Stopped Alert Raised on: August 31.

stop all the OpsCenter server services.conf file after making the changes. The file shows the following entry: nm.bat stop 2 Navigate to INSTALL_PATH\OpsCenter\server\config directory and open the nm. Symantec OpsCenter uses a public community named OpsCenter. Restart all OpsCenter services.trapCommunity=OpsCenter Modify the value of nm. INSTALL_PATH\OpsCenter\server\bin\opsadmin. 2009 12:29 PM Tree Type : Server Nodes : ccs-win-qe-5 Changed Policy Name: BMRPolicy Alert Policy: job policy_change OpsCenter Server: ccs-sol-qe-17 Modified Policy Attributes : Severity: Warning Configuring the SNMP trap community name for OpsCenter For OpsCenter traps.trapCommunity from OpsCenter to some other name. Use the following procedures to configure the SNMP trap community name on Windows and UNIX.574 Understanding and configuring OpsCenter alerts About using SNMP with OpsCenter Table 10-2 Alert type Alert conditions in OpsCenter (continued) Alert condition Description (Example) Alert Raised on: September 7. 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.conf file. the SNMP trap community name is OpsCenter (by default).bat start . INSTALL_PATH\OpsCenter\server\bin\opsadmin. 3 4 Save the nm.

trapVersion=v2c Modify the value of nm. The following procedure explains how to configure the default SNMP version on Windows and UNIX. However.trapVersion from v2c to v1 (for SNMPv1) or v3 (for SNMPv3). /opt/SYMCOpsCenterServer/bin/opsadmin. The file shows the following entry: nm. Restart all OpsCenter services: INSTALL_PATH\OpsCenter\server\bin\opsadmin. To configure the SNMP version for sending SNMP traps on Windows 1 On the OpsCenter server host.bat stop 2 Navigate to INSTALL_PATH\OpsCenter\server\config directory and open the nm.trapCommunity from OpsCenter to some other name. /opt/SYMCOpsCenterServer/bin/opsadmin. Restart all OpsCenter services. 3 4 Save the nm. INSTALL_PATH\server\bin\opsadmin.conf file. The file shows the following entry: nm. this SNMP version can be changed by modifying a configuration file.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. stop all the OpsCenter services.sh stop 2 Navigate to /opt/SYMCOpsCenterServer/config directory and open the nm. stop all the OpsCenter services.conf file after making the changes.trapCommunity=OpsCenter Modify the value of nm. 3 4 Save the nm.bat start .Understanding and configuring OpsCenter alerts About using SNMP with OpsCenter 575 To configure the SNMP trap community name for OpsCenter traps on UNIX 1 On the OpsCenter server host.conf file.

conf configuration file is located at the following default location: Windows UNIX <INSTALL_DIR>\OpsCenter\server\config\am.sh stop 2 Navigate to the OpsCenter configuration directory: cd /opt/SYMCOpsCenterServer/config 3 Open the nm.conf file. am. if you want to send notification after an alert was automatically cleared.autoClear Set this parameter to true. you can customize a few alert settings using the am. if you want to automatically clear the alerts.trapVersion from v2c to v1 (for SNMPv1) or v3 (for SNMPv3). The file shows the following entry: nm. stop all the OpsCenter services: /opt/SYMCOpsCenterServer/bin/opsadmin.conf The alert configuration settings are described as follows: Note: By default all alert configuration parameters are set to true. Restart all OpsCenter services: /opt/SYMCOpsCenterServer/bin/opsadmin. to apply the change in the am. 4 5 Save the nm.conf configuration file.notifyOnAutoClear parameter setting. Set this parameter to true.trapVersion="v2c" Modify the value of nm.sh start Alert configuration settings in OpsCenter In OpsCenter.autoClear parameter is set to true. Make sure that the am.576 Understanding and configuring OpsCenter alerts About using SNMP with OpsCenter To configure the SNMP version for sending SNMP traps on UNIX 1 On the OpsCenter server host.conf <INSTALL_DIR>/SYMCOpsCenterServer/config/am.conf file after making the changes.notifyOnAutoClear . am. The am.

if you want to send notifications after manually clearing alerts. About managing OpsCenter alerts using Microsoft System Center Operations Manager 2007 Microsoft System Center Operations Manager 2007 (SCOM). See “Configuring the SNMP trap community name for OpsCenter” on page 574.Understanding and configuring OpsCenter alerts About managing OpsCenter alerts using Microsoft System Center Operations Manager 2007 577 am. and SNMPv3. By detecting and alerting you on critical conditions. The SCOM Management Pack for NetBackup and the documentation is available for download on the Symantec Support Web site. attributes? Public community means read-only access to SNMP traps. SNMPv2? Is the OpsCenter SNMP community name configurable? Yes. SNMPv2c. the "default read community but still considered public because of certain string" for the public community is "public". OpsCenter assumes it as false. is a next-generation performance and event-monitoring product from Microsoft. Generally. 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). but the community name is maintained as "OpsCenter". Note: If you set an alert configuration parameter to a value other than true or false. . this Management Pack helps prevent possible service outages.notifyOnManualClear Set this parameter to true. Frequently asked SNMP and OpsCenter questions Question Answer What are the default versions of SNMP that SNMPv1. are supported in OpsCenter? What is SNMPv2c? How it is different from See “About SNMP versions” on page 558. How is the OpsCenter community related to The "OpsCenter" community used by the public community? OpsCenter is public. Is the default community name of "OpsCenter" just a name for the community. formerly Microsoft Operations Manager (MOM).

NNM can be used for the centralized management of NetBackup alerts. By detecting and alerting you on critical conditions.symantec.578 Understanding and configuring OpsCenter alerts About managing OpsCenter alerts using HP OpenView Network Node Manager 7.conf file and the documentation is available for download on the support site. Note: The term HP OpenView Network Node Manager (NNM) in this section refers specifically to HP OpenView Network Node Manager 7.51. NNM can receive the SNMP traps that have been configured in OpsCenter. . http://entsupport.51 on Windows http://www.50 or 7.50 or 7.conf file and configuring NNM and OpsCenter.com/docs/295154 More information about OpsCenter alerts is available.conf file to monitor and manage NetBackup alerts using HP OpenView Network Node Manager 7.51.50 or 7. As a result. nom_trapd.50/7.51 on Windows You can monitor and manage NetBackup alerts using HP OpenView Network Node Manager 7.51 on Windows.50/7. By using nom_trapd. HP OpenView Network Node Manager (NNM) can help you to prevent possible service outages. You can download and use the nom_trapd. See “OpsCenter Alert conditions” on page 501.symantec.com/docs/TECH139344 About managing OpsCenter alerts using HP OpenView Network Node Manager 7.

By using OpsCenter. you can track the effectiveness of data backup and archive operations by generating comprehensive business-level reports. .Chapter 11 Reporting in OpsCenter This chapter includes the following topics: ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ About OpsCenter reports Report Templates in OpsCenter About managing reports in OpsCenter Creating a custom report in OpsCenter Creating an OpsCenter report using SQL query About managing My Reports About managing My Dashboard About managing reports folders in OpsCenter Using report schedules in OpsCenter Reports > Schedules options About managing report schedules in OpsCenter About managing time schedules in OpsCenter 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.

See “Saving an OpsCenter report” on page 588. You can select multiple reports and add them in the same dashboard section. . See “Using report schedules in OpsCenter” on page 601. See “About managing My Reports” on page 593. IT finance teams. external customers. Schedules tab This tab contains all report schedules. line-of-business managers. application owners. Use this section to view the saved reports or modify the parameters of the saved reports and generate new reports out of them. See “Reports > Report Templates” on page 581. which you can select and publish on My Dashboard tab. use the existing Backups > Client Count Report Template. multi-level views of backup and archive resources and customizable reports for tracking service usage and expenditures.580 Reporting in OpsCenter About OpsCenter reports OpsCenter displays customizable. change the relative timeframe to four weeks (default timeframe is two weeks) and generate a new Client Count report. These saved reports are stored in the My Reports tab. you can create multiple dashboard section containing a number of reports. For example. IT architects. legal teams. OpsCenter reports UI The OpsCenter reports UI consists of the following components: Report Templates tab This tab lists all Report Templates (or standard or canned reports) that are available in OpsCenter. You can see all clients that are backed up over the last four weeks. or delete schedules using this tab. My Reports tab You can save generated reports for your future use. See “About managing My Dashboard” on page 596. Thus. and capacity planning teams. 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